> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/knowledge-hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.security.gallagher.com/knowledge-hub/products/integrations/elevators/thyssenkrupp/thyssenkrupp-integration-reference.md).

# ThyssenKrupp integration reference

Reference ThyssenKrupp integration versions, licensing, features, network ports, and data flow.

Use this reference to plan a ThyssenKrupp elevator integration and confirm its technical requirements.

### Integration versions

| Version           | Command Centre requirement | Architecture                                      |
| ----------------- | -------------------------- | ------------------------------------------------- |
| 7.10              | 7.10 and later             | Serial connection from Controller 6000            |
| 8.10 through 8.30 | 8.10 through 8.30          | ThyssenKruppEthernet service                      |
| 8.40 and later    | 8.40 and later             | ThyssenKrupp Insight through the Elevator Service |

Command Centre 8.40 and later replaces the earlier Ethernet service. Do not retain the `Gallagher ThyssenKrupp Ethernet 8.20.2` package on these deployments.

### Licensing

ThyssenKrupp Insight requires the `ThyssenKruppInsight` license feature.

### Supported features

ThyssenKrupp Insight supports kiosk and elevator car terminals, Gallagher-controlled readers, and front and rear elevator-car doors. Controller 6000 makes access decisions.

Command Centre 8.40 supports Extended Time/Assistance for accessibility prompts or extended door-open time. Version 8.50 adds default floors, passenger types, and ThyssenKrupp embedded-reader credentials.

### Data flow

Cardholder data remains on Command Centre controllers. The Elevator Service does not send card numbers or personal data to the ThyssenKrupp system.

The Elevator Service receives Card Swipe or RegisterCall messages. It converts them into the ThyssenKrupp format. Command Centre also uses the service for device discovery.

### Network ports

| Network                              | Port              | Protocol | Purpose                    |
| ------------------------------------ | ----------------- | -------- | -------------------------- |
| Controller network                   | 8906              | TCP      | Controllers                |
| Controller network                   | 65000             | TCP      | Command Centre Service     |
| ThyssenKrupp Elevator System network | 8039 through 8041 | UDP      | ThyssenKrupp communication |

For serial interface limits and vendor comparisons, see [Elevator integration interfaces and limits](/knowledge-hub/products/integrations/elevators/hli-reference.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.security.gallagher.com/knowledge-hub/products/integrations/elevators/thyssenkrupp/thyssenkrupp-integration-reference.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.