> 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/elevator-cars/high-level-interface-elevator-cars/understanding-the-high-level-elevator-interface.md).

# Understanding the High Level Elevator Interface

### Introduction

Communication with the elevator system is via an RS232 serial communications link between the Controller and the elevator system. The Elevator HLI item represents this link. When access to a floor changes, due to a time schedule or an access event at an elevator car reader, a message is sent from the Controller to the elevator system instructing it to enable or disable specific elevator floor select buttons. There is individual control by floor (or access zone) and by elevator car.

The following diagram shows the system configuration for interfacing to a Kone elevator system.

![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-2b7245a161a51c7b437848b383e94aa5ae008370%2Foveralldiagram.png?alt=media)

### How it Works

An access zone is assigned to each floor that an elevator car travels to. The access zone represents the area immediately outside the elevator on that floor. By default, the floor select buttons in the elevator car are enabled if the corresponding access zone is in free access, or disabled if the corresponding access zone is secure. Every cardholder has access to floors that are not controlled by Gallagher.

When a cardholder makes a valid access attempt at the elevator car reader, the Controller sends a message to the elevator system instructing it to enable the floor select buttons for those floors (or zones) to which the cardholder has access. After the cardholder selects a floor, or a specified timeout period has expired, the floor select buttons in the elevator car return to the default state.

The Controller polls the elevator system at regular intervals, ensuring that if connection to the elevator system is lost, it is detected and an alarm is raised. Gallagher sends a message to the elevator system each time access to any floor changes. The elevator system replies to each poll.

### Communication Interface

As the Controller has only one serial port, each serial connection to the elevator system requires a separate Controller. A Controller 6000 or 7000 can be used to provide the high level communications interface to the elevator system.

### Lost Connection to the Elevator System

When the connection between the Controller and the elevator system is lost, the elevator system determines what access is allowed from elevator cars. Normally, this means all floors are set to free access until the connection is re-established. The Controller continues to poll the elevator system. Communication is re-established automatically and the floors re-secured as soon as the elevator system responds to a poll from the Controller.

### Supported elevator systems

Gallagher has been tested with and supports a number of elevator system protocols via the Elevator HLI. As the protocol that is used is specific to each manufacturer, variations may be required to support other elevator systems. Gallagher has been designed with the ability to customise manufacturer specific variables without requiring a new version of Controller. For information regarding the support of other manufacturers' elevator systems contact your local Gallagher dealer.

**Note:** Some of the supported elevator system protocols may have limitations. Refer to [Supported elevator systems - Additional Configuration and Troubleshooting](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/elevator-cars/high-level-interface-elevator-cars/supported-elevator-systems-additional-configuration-and-troubleshooting.md) for further information.

### Configuration

Each Elevator Car HLI must be associated with an Elevator HLI item. For further detail refer to [Configuring High Level Elevator Interfaces](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/elevator-cars/high-level-interface-elevator-cars/configuring-high-level-elevator-interfaces.md). The following diagram shows the items that must be configured for each high level elevator interface.

![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-f5758a558b2cf130b349f1e06904398932b2e00a%2Flifthliinft.png?alt=media)

### Readers and Access

Elevator control requires one card reader for each elevator car. Elevator car card readers can be connected to any Controller within the system. If a cardholder badges their card at an elevator car reader before the previous cardholder has completed their floor button selection, the second cardholder's access will supercede the first. This means the first cardholder will need to badge their card again to select the floor they require. This behaviour ensures that where a cardholder badges their card and then leaves the elevator car without selecting a floor, the access attempt of the next cardholder entering the elevator car isn't affected (or delayed).

Where entry to specific floors requires a PIN, the corresponding floor select buttons in the elevator car will not be enabled unless the cardholder correctly enters their PIN. Access to other floors, that do not require PIN entry, is allowed.

### Floor Select Reporting

Where it is supported by the elevator system manufacturer Gallagher will report the floor that was selected following an access granted event at an elevator car.

### System Limits

The Elevator HLI protocol determines the following system limits:

<table><thead><tr><th width="193">HLI</th><th>Controller 6000/7000</th></tr></thead><tbody><tr><td>Levels per Elevator Car</td><td>256</td></tr><tr><td>Elevator Cars per Controller</td><td>8* This number describes the size of the configuration that is able to be hosted on the Controller.</td></tr><tr><td>Transactions per second</td><td>2* This is the number of cardholder access decisions that are able to be made with a high number of floors/elevator cars.</td></tr></tbody></table>


---

# 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/elevator-cars/high-level-interface-elevator-cars/understanding-the-high-level-elevator-interface.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.
