> 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/supported-elevator-systems-additional-configuration-and-troubleshooting.md).

# Supported elevator systems - Additional Configuration and Troubleshooting

This topic describes the additional configuration options and any limitations for the elevator systems supported by Command Centre.

**Note:** Additional elevator systems are provided as licensed customisations of Command Centre. For a list of all Elevator HLI customisations, contact Gallagher Security Technical Support.

<details>

<summary>Otis Compass</summary>

The Otis Compass Destination Management System integrates with Command Centre via the Otis Compass Plus protocol.

The following parameters can be entered in the **Additional configuration** field (on the **Advanced** tab of the Elevator HLI):

<table><thead><tr><th width="192">Parameter</th><th>Description</th></tr></thead><tbody><tr><td><em>ip=nnn.nnn.nnn.nnn</em></td><td>This is the IP address of the 'FT Otis Compass HLI Service' PC <strong>as seen from the Gallagher Controller</strong>. The default is 192.168.50.250, but will be different if the Controller is not on the same subnet as the Otis hardware.</td></tr><tr><td><em>port=nnnn</em></td><td>Where <em>nnnn</em> is the destination TCP port the Elevator HLI sends data to (defaults to 9898).<br>If this parameter is changed, you will need to ensure this parameter is also changed in the 'FT Otis Compass HLI Service' configuration 'OtisCompassHli.conf' file.</td></tr><tr><td><em>poll_due_timeout=nn</em></td><td>Where <em>nn</em> is the time interval between two default access mask polls or heartbeat during idle time (defaults to 15 seconds).</td></tr><tr><td><em>floor_offset=nn</em></td><td>Where <em>nn</em> is a number between -127 and 127 that will set the lowest floor of the Gallagher elevator cars to the lowest floor of the Otis Compass installation (defaults to 0). 127 negative floors, 1 ground floor, and 127 positive floors, which provides a sum of 255 floors.</td></tr><tr><td><em>reverse_csn=n</em></td><td>Where <em>n</em> is either 0 or 1. The default is 1 which reverses the CSN. Command Centre uses the reversed CSN for its card numbers.<br>This value need only be set to 0 if using a 32 or 56 bit Wiegand format.</td></tr><tr><td><em>first_rear_floor=n</em></td><td>Where <em>n</em> is the first rear door floor configured in the Floor Arrangement/Elevator Car HLI. Valid range is 1 to 128 (for supporting up to 127 building floors with both front and rear doors).<br>If n is valid, then floors before n are front door floors; floors at and above n are rear door floors.</td></tr><tr><td><em>enable_periodic_update=n</em></td><td>Where <em>n</em> is either 0 or 1. The default is 0, meaning a heartbeat poll is sent from the Gallagher Controller to the 'Otis Compass HLI Service' as specified by the poll_due_timeout configuration parameter.<br>If the value is set to 1, an access mask for all Elevator Car HLIs (DECs) is sent periodically from the Gallagher Controller to the 'Otis Compass HLI Service' as specified by the <em>poll_due_timeout</em> configuration parameter.<br>The default heartbeat messaging method is multicast. You can change to unicast heartbeat messaging by editing the 'OtisCompassHli.conf' file<strong>*</strong> stored in <em>C:\Program Files (x86)\Gallagher\Gallagher OTIS Compass High Level Integration\Otis Compass Service</em>, and changing the &#x3C;UseMulticastForHeartbeat> number value. 1 = multicast, 0 = unicast.</td></tr><tr><td><em>max_session=nnnnnnnn</em></td><td>Where <em>n</em> is the maximum TCP session time in seconds. Default is 31536000 seconds (365 days). When the session expires, messages from the 'FT Otis Compass HLI Service' will be rejected.</td></tr><tr><td>op_mode=<em>n</em></td><td>Where <em>n</em> is the basic operational mode. Valid range 1-4. Default operational mode is 3. Only operational modes 1 or 4 support the Default Floor functionality. Individual Elevator Car HLIs can be configured with their own operational mode.</td></tr></tbody></table>

For example, the following example shows the format to be used: *ip=192.168.50.250; port=9898; poll\_due\_timeout=15; floor\_offset=0; reverse\_csn=1; first\_rear\_floor=5; enable\_periodic\_update=0; max\_session=31536000; op\_mode=1*

**\* Configuration file:** To create the 'OtisCompassHli.conf' file in *C:\Program Files (x86)\Gallagher\Gallagher OTIS Compass High Level Integration\Otis Compass Service*, copy and paste the 'OtisCompassHli.conf.sample' file and rename it to 'OtisCompassHli.conf'.

**Notes:**

* By default with no floor offset, (i.e. *floor\_offset=0*) then Floor '1' in Command Centre refers to Floor '0' in Otis.
* If a floor offset has been configured, (i.e. *floor\_offset=1*) then Floor '1' in Command Centre refers to Floor '1' in Otis.

### Logging

The Otis Compass integration log files (OtisCompassHliService.log) are located in *C:\ProgramData\Gallagher\Command Centre\OtisCompass*.

To enable more detailed logging (e.g. when debugging an issue), edit the 'OtisCompassHliService.exe.config' file stored in *C:\Program Files (x86)\Gallagher\Gallagher OTIS Compass High Level Integration\Otis Compass Service*, and set the **minlevel** to **"Trace"**. For example:

**\<logger name="\*" minlevel="Trace" writeTo="OtisCompassHliServiceLog" />**

After changing the **minlevel**, you must restart the 'FT Otis Compass HLI Service' service for the change to take effect.

</details>

<details>

<summary>Kone</summary>

The Kone Elevator HLI integration supports the Kone Protocol v2.5

The following parameters can be entered in the **Additional configuration** field (on the **Advanced** tab of the Elevator HLI):

<table><thead><tr><th width="192">Parameter</th><th>Description</th></tr></thead><tbody><tr><td><em>baud=9600</em></td><td>For Kone Protocol v2.5 to communicate at 9600 baud, enter the parameter as shown. Perform a ‘Reset’ override on the Controller used to host this Elevator HLI for the change to take effect.<br>Appropriate values 1200 and 9600.</td></tr><tr><td><em>parity=n</em></td><td>Specify the parity to be used by entering "parity=n" where ‘n’ is one of:<br>N = No parity<br>O = Odd parity<br>E = Even parity<br>M = Mark parity<br>S = Space parity</td></tr><tr><td><em>poll_due_timeout=nnn</em></td><td>This is the time (in seconds) between sending the default access masks for each floor. Default = 15. Appropriate values are between 15 and 900.</td></tr><tr><td><em>retry_timeout=nnn</em></td><td>This is the time (in milliseconds) between retrying a message that has not had a response from the Kone elevator system.</td></tr><tr><td><em>log_raw_data=1</em></td><td>This is used to log outgoing and incoming packets in hexadecimal format.</td></tr><tr><td><em>raise_debug_event=n</em></td><td>This is used to raise additional debugging alarms (where <em>n</em> is a number indicating the debugging level).</td></tr></tbody></table>

For example, the following example shows the format to be used: *baud =9600; parity =O*

**Notes:**

* The Kone protocol requires that all Elevator Car HLIs in a group must be configured in Command Centre with the same number of floors as the Elevator Car HLI that has the most floors. The additional floors for each Elevator Car HLI should either be left with no Access Zone assigned, or with a default Access Zone that no one has access to, depending on the level of security.
* Should a Kone Group Controller be replaced or reset to factory defaults, the connection between the Gallagher and Kone systems must be re-initiated via a restart of the Controller hosting the Kone Elevator HLI.
* On a Kone Elevator Car HLI, groups are numbered 1-8 and the elevator cars associated with each group are numbered 1-8. Each unique group and car number combination identifies a particular elevator car.

</details>

<details>

<summary>Otis</summary>

The following parameters can be entered in the **Additional configuration** field (on the **Advanced** tab of the Elevator HLI):

<table><thead><tr><th width="192">Parameter</th><th>Description</th></tr></thead><tbody><tr><td><em>poll_due_timeout=nnn</em></td><td>This is the time (in seconds) between sending the default access masks for each floor. Default = 15. Appropriate values are between 15 and 900.</td></tr><tr><td><em>retry_timeout=nnn</em></td><td>This is the time (in milliseconds) between retrying a message that has not had a response from the Otis elevator system.</td></tr><tr><td><em>log_raw_data=1</em></td><td>This is used to log outgoing and incoming packets in hexadecimal format.</td></tr><tr><td><em>raise_debug_event=n</em></td><td>This is used to raise additional debugging alarms (where <em>n</em> is a number indicating the debugging level).</td></tr></tbody></table>

For example, the following example shows the format to be used: *poll\_due\_timeout=15; log\_raw\_data=1*

**Note:** The Otis protocol requires that all Elevator Car HLIs in a group must be configured in Command Centre with the same number of floors as the Elevator Car HLI that has the most floors. The additional floors for each Elevator Car HLI should either be left with no Access Zone assigned, or with a default Access Zone that no one has access to, depending on the level of security.

</details>

<details>

<summary>ThyssenKrupp</summary>

**Note:** The recommended method of configuring ThyssenKrupp is via the ThyssenKrupp integration. See [ThyssenKrupp Elevator Systems](https://help.security.gallagher.com/knowledge-hub/configuration-client/integrated-systems/thyssenkrupp-insight-elevator-systems.md) for further detail.

A Gallagher reader is located near each ThyssenKrupp Destination Selection Control (DSC) terminal. When a Cardholder presents their card at the reader, Command Centre instructs the ThyssenKrupp elevator system which levels the Cardholder has access to. The Cardholder then selects a destination limited to those floors.

The following parameters can be entered in the **Additional configuration** field (on the **Advanced** tab of the Elevator HLI):

<table><thead><tr><th width="192">Parameter</th><th>Description</th></tr></thead><tbody><tr><td><em>poll_due_timeout=nnn</em></td><td>This is the time (in seconds) between sending the default access masks for each floor.<br>(Default = 15. Appropriate values are between 15 and 900.)</td></tr><tr><td><em>retry_timeout=nnn</em></td><td>This is the time (in milliseconds) between retrying a message that has not had a response from the ThyssenKrupp elevator system.</td></tr><tr><td><em>log_raw_data=1</em></td><td>This is used to log outgoing and incoming packets in hexadecimal format.</td></tr><tr><td><em>raise_debug_event=n</em></td><td>This is used to raise additional debugging alarms (where <em>n</em> is a number indicating the debugging level).</td></tr><tr><td><em>firmware_reports_dest=n</em></td><td>Disabled = 0. Enabled = 1.<br>If you have the string 'ThyssenKruppHLI=1' in your licence file, floor destination reporting is enabled by default.<br>If your ThyssenKrupp firmware does not support destination reporting and you have installed this feature, enter “firmware_reports_dest=0” to disable floor destination reporting. Command Centre will log an access granted event to the first floor regardless of which floor is selected, and whether a floor is selected or not.</td></tr><tr><td><em>floor_offset=n</em></td><td>Default = 0. Range 0–32. By default the destination floor 0 reported by ThyssenKrupp will correspond to the first floor configured in Command Centre.</td></tr><tr><td><em>broadcast_default_masks=n</em></td><td>To turn on access masks to all terminals, add "broadcast_default_masks=1". To leave this capability off, the parameter can have a value of 0 or be omitted from the string.</td></tr></tbody></table>

For example, the following example shows the format to be used: *poll\_due\_timeout=15; log\_raw\_data=1*

**Limitations:**

* The ThyssenKrupp Elevator HLI integration supports up to 32 floors only.
* The ThyssenKrupp Elevator HLI integration does not support the use of a rear door in an elevator car.
* If an individual elevator car is offline, an offline message is not generated in Command Centre. Hence it is unknown which elevator car is currently offline. The operator will need to physically observe the status of the ThyssenKrupp elevator system to see which elevator car is currently offline.
* Destination Reporting is supported for up to 32 floors only.

**Notes:**

* A Command Centre operator will need to configure an Elevator Car HLI for each ThyssenKrupp DSC terminal.
* On a ThyssenKrupp Elevator Car HLI, the Group number is the ThyssenKrupp Destination Selection Control terminal number. The terminals are numbered from 1-94. The Car number is the associated ThyssenKrupp lift number. Lifts 1-63 are addressable.

</details>

<details>

<summary>Schindler</summary>

The following parameters can be entered in the **Additional configuration** field (on the **Advanced** tab of the Elevator HLI):

<table><thead><tr><th width="192">Parameter</th><th>Description</th></tr></thead><tbody><tr><td><em>poll_due_timeout=nnn</em></td><td>This is the time (in seconds) between sending the default access masks for each floor. Default = 15. Appropriate values are between 15 and 900.</td></tr><tr><td><em>retry_timeout=nnn</em></td><td>This is the time (in milliseconds) between retrying a message that has not had a response from the Schindler elevator system.</td></tr><tr><td><em>log_raw_data=1</em></td><td>This is used to log outgoing and incoming packets in hexadecimal format.</td></tr><tr><td><em>raise_debug_event=n</em></td><td>This is used to raise additional debugging alarms (where <em>n</em> is a number indicating the debugging level).</td></tr></tbody></table>

For example, the following example shows the format to be used: *poll\_due\_timeout=15; log\_raw\_data=1*

**Limitation:** The Schindler lift control box supports up to 64 floors.

**Note:** The Elevator HLI only supports one Elevator Car HLI. The Car number must be 1, the Group number is ignored.

</details>

<details>

<summary>Otis Modbus</summary>

The following parameters can be entered in the **Additional configuration** field (on the **Advanced** tab of the Elevator HLI):

<table><thead><tr><th width="192">Parameter</th><th>Description</th></tr></thead><tbody><tr><td><em>poll_due_timeout=nnn</em></td><td><p>This is the time (in seconds) between sending the default access masks for each floor. Default = 15. Appropriate values are between 15 and 900.<br>This number should be set to:</p><ul><li>less than the maximum temporary floor button enabled time the Otis lift control box can be configured.</li><li>more than the <strong>Floor select timeout</strong> (as configured on the <strong>Advanced</strong> tab of the Elevator Car HLI), otherwise Command Centre may have problems logging Cardholders floor selections.</li></ul></td></tr><tr><td><em>retry_timeout=nnn</em></td><td>This is the time (in milliseconds) between retrying a message that has not had a response from the Otis Modbus elevator system.</td></tr><tr><td><em>cttl_start_addr=nnnnn</em></td><td>The first address of the CTTL discrete input is set to 10009.</td></tr><tr><td><em>log_raw_data=1</em></td><td>This is used to log outgoing and incoming packets in hexadecimal format.</td></tr><tr><td><em>raise_debug_event=n</em></td><td>This is used to raise additional debugging alarms (where <em>n</em> is a number indicating the debugging level).</td></tr></tbody></table>

For example, the following example shows the format to be used: *poll\_due\_timeout=15; log\_raw\_data=1*

**Limitations:**

* The Otis Modbus lift control box supports up to 36 floors.
* If an individual elevator car is offline, an offline message is not generated in Command Centre. Hence it is unknown which elevator car is currently offline. The operator will need to physically observe the status of the Otis Modbus elevator system to see which elevator car is currently offline.
* If multiple Elevator Car HLIs are attached to the same Elevator HLI and some of the cars are offline, the other cars will still function as expected, (e.g. Cardholders can badge cards and select floors, and operators can perform overrides). However, there is no guarantee that the override will reach the Otis Modbus lift control box. If this occurs, re-send the override.
* On an Otis Modbus Elevator Car HLI, Group number and Car number must be configured as the same number as the child device ID of the Otis Modbus lift control box. Valid numbers are from 1-247.

</details>

<details>

<summary>Kone ELI</summary>

The Kone ELI Elevator HLI feature has been implemented according to "Group Controller Access Control Interface Specification" document, Rev 1.8, provided by Kone.

The Kone ELI Elevator HLI feature supports Kone DOPs (Destination Operation Panels) on some floors as well as COPs (Car Operation Panels inside the elevators), with a Gallagher reader positioned at each DOP or COP. When a Cardholder presents their card at the reader, Command Centre instructs the Kone system which levels the Cardholder has access to. The Cardholder can then select a destination limited to those floors. If the Cardholder is using a DOP, the DOP then instructs the Cardholder on which elevator car to use, alleviating the need for floor selection within the elevator car itself.

Using the 'Gallagher Advanced Global Default Mask' parameters, you can configure an operation panel to use either a Global Default Mask (GDM) or a Specific Default Mask (SDM) mask to communicate with the Gallagher Controller. You can also specify what mask an operation panel must use when it’s connected or disconnected from the Gallagher Controller. Other parameters are used to change the state of another mask.

**Global and specific mask override rules**

* If a GDM is in an open state (F), then it can't be secured/Locked (S) by an SDM.
* If a GDM is in a secure state (S), then it can be freed/opened (F) by an SDM.
* The SDM inherits any new configuration added to the GDM (i.e. new floors or lifts).

**Warning:** If a Cardholder presents a card at a reader associated to a Kone terminal (DOP or COP) and then walks away without selecting a floor, another user may select a floor based upon that Cardholder’s access privileges until the configured floor selection timeout is reached. If any Cardholder attempts to present another card during this time, their card read will be ignored. Any floor selection made will be subject to the first Cardholder’s access privileges. The floor selection will be reported as belonging to the first Cardholder.

The following parameters can be entered in the **Additional configuration** field (on the Advanced tab of the Elevator HLI):

<table><thead><tr><th width="225.99993896484375">Parameter</th><th>Description</th></tr></thead><tbody><tr><td><em>Ip</em></td><td>Provide the IP address of the Kone Group Controller.<br><br><strong>Note:</strong> This parameter is overridden if any controllers are specified as [KCEGC] parameters.</td></tr><tr><td><em>Port</em></td><td>Provide the IP port of the Kone Group Controller.<br><br><strong>Note:</strong> This parameter is overridden if any controllers are specified as [KCEGC] parameters.</td></tr><tr><td><em>Backuplp</em></td><td>Provide the IP address of the backup Kone Group Controller.<br><br><strong>Note:</strong> This parameter is overridden if any controllers are specified as [KCEGC] parameters.</td></tr><tr><td><em>BackupPort</em></td><td>Provide the port of the backup Kone Group Controller.<br><br><strong>Note:</strong> This parameter is overridden if any controllers are specified as [KCEGC] parameters.</td></tr><tr><td><em>Floors</em></td><td>Provide the number of floors configured for the building. (This will be used to create global default access masks.)</td></tr><tr><td><em>Poll</em></td><td>Provide the time between sending the default access masks (in seconds). If the value is not included then the default of 20 seconds will be used.</td></tr><tr><td><em>PollLimit</em></td><td>Provide the number of default access masks that this Gallagher Controller will have in transit with the Kone Group Controller.</td></tr><tr><td><em>FloorSelectTimeout</em></td><td>Used to notify Kone of the amount of time that a DOP will be open for a Cardholder to select a floor (in seconds). If the value is not included then the Kone Group Controller value will be used.<br>If this value is set, then the Floor select timeout on the <strong>Advanced</strong> tab of each Elevator Car HLI should be set to this value plus a bit extra to allow for network delay.</td></tr><tr><td><em>DisconnectedState</em></td><td>Used to notify Kone of what it should do if the connection between the Gallagher Controller and the Kone Group Controller is lost. Options are: Same, Free or Secure.<br><strong>Same:</strong> The current free floors remain free, other floors will be inaccessible.<br><strong>Free:</strong> Anyone can travel from any floor to any floor using an elevator.<br><strong>Secure:</strong> All floors will be inaccessible.<br>If the value is not included then the default "Same" will be used. If this setting is changed the Controller must be re-started for the new Disconnected State to take effect.</td></tr><tr><td><em>poll_due_timeout=nnn</em></td><td>This is the time (in seconds) between sending the default access masks for each floor. Default = 15. Appropriate values are between 15 and 900.</td></tr><tr><td><em>retry_timeout=nnn</em></td><td>This is the time (in milliseconds) between retrying a message that has not had a response from the Kone elevator system.</td></tr><tr><td><em>log_raw_data=1</em></td><td>This is used to log outgoing and incoming packets in hexadecimal format.</td></tr><tr><td><em>raise_debug_event=n</em></td><td>This is used to raise additional debugging alarms (where <em>n</em> is a number indicating the debugging level).</td></tr><tr><td><em>GlobalDefaultAccessMaskOption=&#x3C;operating panels></em></td><td>This is used to set the default access mask. Options are COPsOnly, DOPsOnly, or both. If it is set to COPsOnly, only COP_GLOBAL_DEFAULT_MASK messages will be sent. If it is set to DOPsOnly, only DOP_GLOBAL_DEFAULT_MASK messages will be sent. If it is set to both (or if it is not included or set), both COP_GLOBAL_DEFAULT_MASK and DOP_GLOBAL_DEFAULT_MASK messages will be sent.</td></tr><tr><td colspan="2"><em><strong>Kone Control &#x26; Electrification Group Controller parameters:</strong></em></td></tr><tr><td><em>Address</em></td><td>Provide the IP address and port number of each Kone Control &#x26; Electrification Group Controller (KCEGC). You do not need to specify which are primary and which are backup controllers. Type an IP address, followed by a colon (:), then the port number. Separate listed controllers with a line break (no semicolon). A maximum of five KCEGCs can be listed.<br><br><strong>Note:</strong> Controllers specified here override any controllers specified by the Ip, Port, BackupIp, and BackupPort parameters mentioned above. If controllers are listed as [KCEGC] paramters, those other specified controllers are ignored.</td></tr><tr><td colspan="2"><em><strong>Call Type parameters:</strong></em></td></tr><tr><td><em>[CALL_nnn]</em></td><td>Used to specify the call type number. The call type number can be between 0-200. The word 'CALL' must be capitalised.</td></tr><tr><td><em>Name</em></td><td>Used to specify the name of the Call Type. The names provided here will be displayed under the Call Type column in the Cardholder Kone ELI properties tile.</td></tr><tr><td><em>Lifts</em></td><td>Used to specify the lifts that will be used for a Call Type.<br><br><strong>Notes:</strong><br>Any lifts specified here that do not exist in the Kone ELI system, the lifts will be ignored and the available lifts will be used for the Call Type.<br>The maximum number of lifts you can specify for a Call Type is eight.<br>Each value entered for a lift must be >=1.</td></tr><tr><td colspan="2"><em><strong>Gallagher Advanced Global Default Mask parameters:</strong></em></td></tr><tr><td><em>DOP_GDM_C</em></td><td>DOP Global Default Mask (Connected)</td></tr><tr><td><em>DOP_GDM_D</em></td><td>DOP Global Default Mask (Disconnected)</td></tr><tr><td><em>COP_GDM_C</em></td><td>COP Global Default Mask (Connected)</td></tr><tr><td><em>COP_GDM_D</em></td><td>COP Global Default Mask (Disconnected)</td></tr><tr><td><em>DOP_SDM_C</em></td><td>DOP Specific Default Mask (Connected)</td></tr><tr><td><em>DOP_SDM_D</em></td><td>DOP Specific Default Mask (Disconnected)</td></tr><tr><td><em>COP_SDM_C</em></td><td>COP Specific Default Mask (Connected)</td></tr><tr><td><em>COP_SDM_D</em></td><td>COP Specific Default Mask (Disconnected)</td></tr><tr><td><em>DOP_GDM_DEL</em></td><td>DOP Global Default Mask delete</td></tr><tr><td><em>COP_GDM_DEL</em></td><td>COP Global Default Mask delete</td></tr><tr><td><em>DOP_SDM_DEL</em></td><td>DOP Specific Default Mask delete</td></tr><tr><td><em>COP_SDM_DEL</em></td><td>COP Specific Default Mask delete</td></tr><tr><td><em>GDM_ONLY_OPS</em></td><td>Specifies Operation Panels (OPs) that only use GDM.</td></tr><tr><td><em>DD</em></td><td>Destination Default (Secure or Free). By default, it is set to ‘Secure or Locked’ (S).</td></tr><tr><td><em>DE</em></td><td>Destination Exceptions ( destination floors that are configured differently compared to the DD mask configuration).</td></tr><tr><td><em>GN</em></td><td>Group Number. Numbers 1-100 represent a COP, numbers higher than 100 represent a DOP.</td></tr><tr><td><em>CN</em></td><td>Car Number</td></tr><tr><td><em>SD</em></td><td>Source Default (open or locked)</td></tr><tr><td><em>SE</em></td><td>Source Exceptions (source floors that are configured differently compared to the SD configuration).</td></tr><tr><td><em>S</em></td><td>Secure or Locked. ‘S’ is the default for DD.</td></tr><tr><td><em>F</em></td><td>Free or Open. ‘F’ is the default for SD.</td></tr><tr><td><em>n,m,…</em></td><td>Floor numbers. Index starts from 1 and corresponds to the floor in your Floor Arrangement in the Command Centre. If you have rear floor(s), in the Floor arrangement, you need to create double the number of floors specified in elevator HLI configuration. For instance, if you have 4 floors, in the Floor Arrangement, you need to configure 8 floors (front and 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.</td></tr><tr><td><em>SendMessage</em></td><td>Sends a single specific mask message to Kone Group Controller</td></tr></tbody></table>

<figure><img src="https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-33fc62988ecf8c982c4c89b1c7c71d34072e7aa2%2Fkoneparameters.png?alt=media" alt=""><figcaption></figcaption></figure>

**For example:**

* The following example shows the format to be used: `Ip=192.168.1.1; Port=2005; BackupIp=192.168.1.2; BackupPort=2005; Floors=40; Poll=36000; PollLimit=10; FloorSelectTimeout=5; DisconnectedState=Free;GlobalDefaultAccessMaskOption=DOPsOnly`
* The following example shows the parameters used to specify one primary and two backup Kone Control & Electrification Group Controllers (KCEGCs):

  `[KCEGC]`\
  `Address=192.168.1.1:2005`\
  `Address=192.168.1.2:2005`\
  `Address=192.168.1.3:2005`
* The following example shows the parameters used to create a Call Type:

  `[CALL_0]`\
  `name= Priority`\
  `lifts=1,2,3,4`
* The Following example shows some of the Gallagher Advanced Global Default Mask parameters used for configuration:

  `[Gallagher]`\
  `DOP_GDM_C=DD=S; DE=5,25; SD=S;`\
  `DOP_GDM_D=DD=F; SD=F;`\
  `COP_GDM_C=DD=S; DE=5,25;`

  <table><thead><tr><th width="269.77777099609375">Configuration</th><th>Explanation</th></tr></thead><tbody><tr><td><em>DOP_GDM_C=DD=S; DE=5,25; SD=S;</em></td><td>DOP Global Default Mask connected state is set to Destination Default (secure or locked). Destination Exception mask applies to floors 5 and 25. Source Default floors are set to secure or Locked.</td></tr><tr><td><em>DOP_GDM_D=DD=F; SD=F;</em></td><td>DOP Global Default Mask disconnected state is to Destination Default (free). Source Default floors are set to free or open.</td></tr><tr><td><em>COP_GDM_C=DD=S; DE=5,25;</em></td><td>COP Global Default Mask connected state is set to Destination Default (secure or locked), Destination Exception mask applies to floors 5 and 25.</td></tr><tr><td><em>COP_GDM_D=DD=F;</em></td><td>COP Global Default Mask disconnected state is set to Destination Default (free or open).</td></tr><tr><td><em>COP_SDM_D=DD=F;</em></td><td>COP Specific Default Mask disconnected state is set to Destination Default (free or open).</td></tr><tr><td><em>DOP_SDM_D=DD=F;</em></td><td>DOP Specific Default Mask disconnected state is set to Destination Default (free or open).</td></tr><tr><td><em>GDM_ONLY_OPS=(101,1),(105,1),(111,1),(1,1)</em></td><td>Operation Panels that are using only Global Default Mask are DOP1, DOP 2, DOP 3 and COP 1. The second value following a comma is the Car number (i.e. (101,1) means: DOP 1, Car 1).</td></tr></tbody></table>

**Configuration example**

`Floors=20; Ip=192.89.159.2; Port=2005;`\
`BackupIp=192.89.159.3; BackupPort=2005;`\
`Poll=36000;FloorSelectTimeout=5;`\
`DisconnectedState=Free;`

`[KCEGC]`\
`Address=192.168.1.1:2005`\
`Address=192.168.1.2:2005`\
`Address=192.168.1.3:2005`

`[CALL_0]`\
`name = Normal Call`\
`lifts = 1,2,3`

`[CALL_1]`\
`name = Handicapped call`\
`lifts = 1,2`

`[CALL_2]`\
`name = Priority call`\
`lifts = 1,5,7`

`[CALL_3]`\
`name = Empty car call`\
`lifts = 1,2`

`[CALL_4]`\
`name = Space allocation call`\
`lifts = 3,4,5`

`[Gallagher]`\
`DOP_GDM_C=DD=S; DE=5,25; SD=S;`\
`DOP_GDM_D=DD=F; SD=F;`\
`COP_GDM_C=DD=S; DE=5,25;`\
`COP_GDM_D=DD=F;`\
`COP_SDM_D=DD=F;`\
`DOP_SDM_D=DD=F;`\
`GDM_ONLY_OPS=(101,1),(105,1),(111,1),(1,1)`

**Notes:**

* The Ip, Port, BackupIp, and BackupPort parameters would not be specified as well as \[KCEGC] parameters in a real configuration. The \[KCEGC] parameters override the Ip, Port, BackupIP, and BackupPort parameters.
* One Elevator Car HLI needs to be created per DOP or COP.
* If using a KIC leave the *BackupIp* field as 0.0.0.0 Kone default port is 2005.
* When configuring multiple Elevator Car HLIs, the configured (hosting) Elevator HLI should be removed from the Controller as each update of an Elevator Car HLI will queue multiple messages for the Elevator HLI. Once all Elevator Car HLIs are configured then the ELI can be reattached to the Controller and a smaller subset of configuration will be sent.
* When configuring the Group number, make sure that all the terminals belonging to one group are of the same type, (i.e. either they are all DOPs, or they are all COPs. Mixed groups are not currently possible).

  <table><thead><tr><th width="142">If configuring...</th><th>then...</th></tr></thead><tbody><tr><td>COPs</td><td>configure the Group number to match the Kone Group ID, and the Car number to match the Kone Elevator ID.</td></tr><tr><td>DOPs</td><td><ul><li>configure the Group number to match the Kone DOP floor ID, plus an offset of 100. Make sure it matches the actual DOP configuration. See Example next. All DOPs on the same floor are in the same group.</li><li>configure the Car number to match the Kone DOP ID. Each DOP on a floor has a unique identifier.</li></ul></td></tr></tbody></table>

  **Example:**

  <table><thead><tr><th width="162"></th><th width="180">COPs</th><th>DOPs</th></tr></thead><tbody><tr><td rowspan="2"><strong>Kone</strong></td><td>Elevator ID 1</td><td>DOP ID 1</td></tr><tr><td>Group ID 1</td><td>DOP Floor ID 1</td></tr><tr><td rowspan="2"><strong>Gallagher</strong></td><td>Car number 1</td><td>Car number 1</td></tr><tr><td>Group number 1</td><td>Group number 101</td></tr></tbody></table>
* When configuring a DOP, you can configure access denied messages to be sent to the Kone system, by entering the following string in the **Additional configuration** field on the **Advanced** tab of that DOP's Elevator Car HLI: `SendDenial= 1`

**Initialisation**

To initialise the connection between each Elevator HLI and Kone, perform the following procedure:

1. Change the poll value in the Additional configuration string, located within the Advanced tab of each Elevator HLI to ‘300’, (e.g. Poll=300).
2. Wait for the Elevator HLI’s to show that they are online.
3. Change the poll value in the Additional configuration string, located within the Advanced tab of each Elevator HLI to ‘36000’, (e.g. Poll=36000) or an appropriate figure for your site.

**Troubleshooting**

* There may be a period during schedule changes and polling where there may be a delay in Cardholder badging messages being passed to Kone and the floor selections being returned to Command Centre. This usually has no effect on a Cardholders usage of the system but can affect the destination reporting during that time.
* After the first badge, any bad replies from terminals may indicate poor configuration of the panel (on Kone side) or poor Gallagher reader hardware installation.
* In a Polaris hybrid configuration (that implements both DOPs and COPs) COPs will not be active when the elevator reaches a floor that uses DOPs for destination control.
* If a DOP does not receive a Specific Mask (the default access for the DOP) during a schedule change, then the only way to send this message is going to be:
  * the next schedule change
  * a poll, or
  * by an operator performing an Access Zone Override, for one of the floors serviced by the DOP in question.
* If you are experiencing problems during schedule change or during polling then the Poll Limit can be altered:
  * A large number means the mask messages will be sent faster, however this places more load on the HLI Controller and Cardholder Mask messages may be lost.
  * A small number means that it will take longer to send all mask messages, however there will be more bandwidth available for the Cardholder Mask messages. An unwelcome side effect is that if the configured amount of mask messages are waiting for replies that are not returning then no other mask messages will be sent until those messages expire (Specific Mask messages only - Cardholder messages are still sent).
* Should a Kone Group Controller be replaced or reset to factory defaults, the connection between the Gallagher and Kone systems must be re-initiated via a restart of the Controller hosting the HLI/ELI.
* This feature was not designed for multi-server. Although it may work, it will leave pending changes for the Floor Arrangement item.

</details>


---

# 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/supported-elevator-systems-additional-configuration-and-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.
