> 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/configuring-an-elevator-car-hli.md).

# Configuring an Elevator Car HLI

### Introduction

This procedure enables an operator with "Edit Site" privilege to configure an Elevator Car HLI. Use this procedure if the elevator system associated with this elevator car connects to Command Centre via a high level interface. Use the Configuring Elevator Cars procedure instead, if the elevator car floor select buttons will be controlled via outputs.

***

### Considerations

Each combination of an Elevator HLI, Group number and Car number must be unique. If they are not unique, you can still save the new Elevator Car HLI, but it will fail to come online.

***

### Configuration

To configure a High Level Elevator Interface, perform the following procedures in Gallagher Configuration Client:

1. Click **Configure** from the menu bar, then **Elevator Cars**.

   The **Elevator Car** List Window opens (in [grid view](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/list-windows/grid-view.md)).
2. **Right click** and select **New\...Elevator Car HLI**.

   By default the **General** tab displays.
3. Complete the fields as required.

   For further detail see [General tab](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/generic-properties-configuration/general-tab.md).
4. Click each tab in turn and configure the High Level Elevator Interface properties as required:

<details>

<summary>Connections tab</summary>

1. Click the **Connections** tab.

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

   * the Controller that will be making access decisions for this elevator car,
   * the Elevator HLI that will provide the communication interface to the elevator system,
   * the Group number that this elevator car belongs to, and
   * the Car number.

   **Note:** The Group number and Car number are the numbers defined within the elevator control system that together reference a specific elevator car. 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 details regarding the Group number and Car number configuration for your third party elevator system.

</details>

<details>

<summary>Readers tab</summary>

1. Click the **Readers** tab.
2. Enter the Readers installed in the elevator car.

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

   **Notes:**

   * Readers installed in the elevator car HLI function similar to the elevator reader at which the Cardholder badges. E.g. An elevator car HLI has readers A and B. The Cardholder badges at reader A. If the Cardholder is prompted to select a floor, reader B will also prompt for an input simultaneously. Therefore, floor selection can be made from either readers' location.
   * If any of the floor’s access zone is in 'PIN' mode, we recommend to use PIN compatible readers only, (i.e. T-20 readers). This allows a Cardholder to get continuous feedback, and enter a PIN when required. A Cardholder without a PIN will still be able to select floors which are not in 'PIN' mode.
3. Check the **Disable reader feedback** checkbox if required.

   If this option is checked, then the elevator cars reader will not display prompts, icons, LEDs, or make access granted or access denied sounds when access attempts are made at the reader.

   **Note:** When checked, this option has the effect of disabling any feature that requires reader feedback, (e.g. PINs, Code or Card mode, local overrides).

</details>

<details>

<summary>Floors tab</summary>

1. Click the **Floors** tab.

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

   **Note:** All Elevator Car HLIs that are assigned to the same Elevator HLI must be assigned the same number of floors, whether this number be determined by **Floor Arrangement** or by **Number of floors**. If you have Elevator Car HLIs that need different numbers of floors from each other, they must be assigned to separate Elevator HLIs.
2. Has a Floor Arrangement been configured?

   If **yes**, go to Step 3.

   If **no**, go to Step 4.
3. Select the Floor Arrangement for this Elelvator Car HLI from the **Floor Arrangement** drop-down list. Go to the next tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-4657e37e4f5f57d3dc05a9927aa3bcd2d7bd2f65%2Felevatorcarhli_floors_arrangement.png?alt=media)
4. Enter or select the Number of floors accessed by the elevator group.

   This automatically populates the table with the required number of Floors.

   **Notes:**

   * The Floor column refers to the number used by the elevator group controller (and within the HLI protocol) to refer to this floor. It is not the floor number by which the level is commonly known (i.e. what is embossed on the elevator button in the elevator car). Floor numbers used within the HLI can also differ between elevator groups within the same elevator system.
   * Whenever a change to a Cardholder’s access is made, all access for the Cardholder is sent to the Controller. If the access for a large number of Cardholders is changed at one time, (e.g. the Floors within an Elevator Car HLI are changed), this will result in a large number of messages being sent to the Controller. The messages pending can be viewed on the **Status and Overrides** tab in the Controller properties. It is recommended that a large change to Cardholder access, be done at a time when the Controller is at its least busiest, (i.e. after hours).
5. Click on a row (or Floor) to select it. Select the [Access Zone](https://help.security.gallagher.com/knowledge-hub/configuration-client/glossary-of-terms.md#access-zone) that represents the area outside the elevator on this particular floor, from the drop-down list immediately below the table.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-02c69b896f4b076f5da8d0565d4307737be6b5ce%2Fhli-lc-floors2.png?alt=media)
6. Repeat Step 5. until an Access Zone has been selected for each Floor to which access is controlled by the Command Centre system.

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

   **Notes:**

   * If you do not select an Access Zone for a Floor, this means the associated floor is in free access mode.
   * To configure rear doors for elevator cars that have front and rear doors that lead to different Access Zones, refer to “Rear doors” below.

   **Rear doors**

   The Otis Compass and Kone ELI elevator system integrations currently support rear doors on elevator cars. If you are not using one of these integrations, ignore the following.

   You can manage access to both front and rear elevator doors. In the floor arrangement, you must create double the amount of floors specified in elevator HLI configuration. For instance, if you have 4 floors, in the floor arrangement, you would need to configure 8 floors (4 for front and 4 for rear). In the floor arrangement, the fifth floor represents the first floor's rear door and the sixth floor is the second floor's rear door and so on. If you have a floor that only has one door (either a front or rear door), you still need to configure two floors for it (one with access and the other without access). Ten Floors and Access Zones are configured below, to represent five physical floors with front and rear doors:

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

   You also need to refer to [Troubleshooting - Supported elevator systems](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 integration-specific rear door configuration (e.g. configuration specific to Otis Compass).

</details>

<details>

<summary>Advanced tab</summary>

1. Click the **Advanced** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-0528fc8e9b5dd3e8e8d35456ba1330897de24d1a%2Felevatorcarhli_advanced.png?alt=media)
2. Change the Advanced Settings as required.

   <table><thead><tr><th width="138">Option</th><th>Meaning</th></tr></thead><tbody><tr><td>Floor select timeout</td><td>Time from when floor select buttons are enabled in an elevator car, following a cardholder being granted access at the elevator car reader, to when the floor select buttons are returned to the default access state.</td></tr><tr><td>PIN entry timeout</td><td>Maximum time allowed for a cardholder to enter their PIN. Measured from card badge.<br>If PINs functionality is allowed in the elevator cars, this timeout should be set to as long as possible and preferably the same length of time as the “Floor select timeout” to avoid confusion.</td></tr><tr><td>Card swipe timeout</td><td>Maximum time allowed between card swipes when performing a double-card override or between pressing a function key on a keypad reader then swiping a card. Configure this timeout if the elevator car will support local overrides by either of these methods.</td></tr><tr><td>Additional configuration</td><td>An optional field used if you are configuring this Elevator Car HLI for a Kone DOP terminal (outside an elevator). When this field contains the string SendDenial=1, the Gallagher Controller will also inform Kone controllers when access is denied at this DOP's readers.</td></tr></tbody></table>

</details>

5. Click the **Cameras** tab if you want to associate a DVR Camera(s) with this Elevator Car HLI.

   For further details see [Cameras tab](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/generic-properties-configuration/cameras-tab.md).
6. Click the **Icons** tab if you want to change the Icon Set for this Elevator Car HLI.

   For further details regarding the **Icons** tab, see [Icons](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/server-properties/icons.md).
7. Click the **Custom Fields** tab if you want to add and assign a custom field value to this Elevator Car HLI.

   For further details regarding the **Custom Fields** tab, see [Custom Fields](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/server-properties/custom-fields.md).
8. Click the **Notes** tab if you want to add a note(s) about this Elevator Car HLI.

   For further details regarding the **Notes** tab, see [Notes](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/server-properties/notes.md).
9. Click **OK** to exit and save your changes.

   Click **Cancel** to exit without saving your changes.

   Click **Apply** to save your changes and stay in this window.

### Result

An Elevator Car HLI is configured and assigned to an Elevator HLI. The Controller that supports the Elevator HLI will begin polling the elevator system.

***

### Editing and Deleting Elevator Car HLIs

Refer to [Editing items](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/generic-properties-configuration/editing-items.md) and [Deleting items](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/generic-properties-configuration/deleting-items.md) for procedures on how to edit and delete Elevator Car HLIs.


---

# 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/configuring-an-elevator-car-hli.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.
