> 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/configuration-client/site-installation/external-systems/schindlerid/troubleshooting.md).

# Troubleshooting

* Where Gallagher readers on a Controller are connected to the elevator terminals it is recommended that the maximum Controller loading is no more than 2 card events per second. This is the sum of the card events for all connected readers.
* A Schindler Call Manager can handle only one connection. Several Call Managers can be created in Schindler. Command Centre is able to connect to several Schindler systems. In such a case several External Systems (Call Interfaces) are created in Command Centre. Command Centre is not supposed to connect to several Call Managers of the one Schindler system. Another Call Manager in the Schindler system would be needed, if there is yet another system besides Command Centre that is going to call the lifts.
* When a terminal is processing a request, the terminal will not accept any other requests until such time as the original request is processed.
* If a Time Pattern is deleted you will also need to delete the SOM related to it. When creating the Time Pattern again, you will need to create a new SOM. If you don't do this, you may find that the behaviour of the SOM is inconsistent.
* If a Time Pattern is deleted, an alarm is raised advising the operator that one of the Time Patterns is not defined. If the alarm is acknowledged it will not be raised again, (e.g. When an override is performed on the Output the alarm is not raised again).
* If the middleware services or the Schindler system are disconnected from the network and both Time Patterns are deleted from a floor, then Command Centre will not report the Time Pattern deletion.


---

# 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/configuration-client/site-installation/external-systems/schindlerid/troubleshooting.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.
