> 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/kone/kone-eli/kone-eli-configuration.md).

# Configure KONE ELI

Configure KONE ELI connection settings, panels, floor arrangements, and simulator tests.

Configuration reference for all four Command Centre item types in a Kone ELI deployment.

{% hint style="info" %}
For architecture, licensing, reader behaviour, and the RCGIF Plugin overview, see [Kone ELI](/knowledge-hub/products/integrations/elevators/kone/kone-eli.md).
{% endhint %}

## Pre-configuration: information required from the Kone Technician

Do not begin configuration until all of the following have been confirmed with the Kone Technician. These values come entirely from the Kone system and cannot be derived from the CC side.

| Required item                                                          | Used in CC                                               |
| ---------------------------------------------------------------------- | -------------------------------------------------------- |
| Kone Group ID (1-100) per elevator group                               | Elevator Car HLI (COP), Group field                      |
| Kone Elevator ID per lift car                                          | Elevator Car HLI (COP), Car field                        |
| Kone DOP Floor ID per floor                                            | Elevator Car HLI (DOP), Group field (+ 99 offset)        |
| Kone DOP Terminal ID per DOP panel                                     | Elevator Car HLI (DOP), Car field                        |
| Physical floor count (front doors only, do not count rear-door floors) | Elevator HLI, `Floors=` parameter                        |
| Primary and backup Group Controller IPs and ports                      | Elevator HLI, `Ip=`, `Port=`, `BackupIp=`, `BackupPort=` |

## Item types summary

| Item type         | Represents                                    | One per                                    |
| ----------------- | --------------------------------------------- | ------------------------------------------ |
| Elevator HLI      | IP connection to Kone Group Controller        | Site (one per Kone group)                  |
| Elevator Car HLI  | Individual DOP or COP panel                   | Each physical DOP panel and each COP panel |
| Floor Arrangement | Set of floors a cardholder can access         | Access profile                             |
| DOP               | Destination-Operating Panel (outside the car) | Floor landing                              |
| COP               | Car-Operating Panel (inside the car)          | Elevator car                               |

## Elevator HLI

The main communication item between CC and the Kone Group Controller. Located in Configuration Client under **Elevator** item types.

![Kone ELI Properties dialog - Advanced tab showing the additional config string fields including Ip, Port, BackupIp, BackupPort, Floors, PollLimit, FloorSelectTimeout, and other parameters](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-4bbb1f7d234d3f045ac68b2b53c5f7f8db15928e%2FSECHUB-kone-eli-config-02-elevator-hli-dialog.png?alt=media)

### Additional config string (Advanced tab)

> **Version note:** the example below reflects vEL8.90.1318+ format. Sites on vEL8.80 or earlier use different parameters. Read the version notes under each parameter before applying to a pre-8.90 site.

```
Ip=xxx.xxx.xxx.xxx;Port=2005;BackupIp=xxx.xxx.xxx.xxx;
BackupPort=2006;Floors=5;PollLimit=1;
FloorSelectTimeout=5;DisconnectedState=Free;
GlobalDefaultAccessMaskOption=Both;
DefaultMaskTrackOption=SendTrack;
KoneStateTransferMode=2
```

### Parameters

| Parameter                       | Notes                                                                                                                                                                                                                                                                                                                    |
| ------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| `Ip`                            | Primary Kone Group Controller IP address                                                                                                                                                                                                                                                                                 |
| `Port`                          | Primary controller port (typically 2005)                                                                                                                                                                                                                                                                                 |
| `BackupIp`                      | Backup controller IP address                                                                                                                                                                                                                                                                                             |
| `BackupPort`                    | Backup controller port (typically 2006)                                                                                                                                                                                                                                                                                  |
| `Floors`                        | Number of **physical** floors only, do not count rear-door floors                                                                                                                                                                                                                                                        |
| `Poll`                          | Seconds between sending default access masks in idle state. Default if omitted: **20 seconds**. **Deprecated from vEL8.90.1318+, do not set on supported versions.**                                                                                                                                                     |
| `PollLimit`                     | Maximum number of default access masks the controller will have **in transit simultaneously** with the Kone Group Controller. Changed from default 10 to 1 in vEL8.90.1318+; set to **1**. On the Limited Release builds it no longer needs to be set, as it already defaults to 1 (see the Limited Release note below). |
| `FloorSelectTimeout`            | Seconds before floor buttons return to default state after access. **When set here, also set the equivalent timeout on the Advanced tab of each Elevator Car HLI to this value plus a small buffer for network delay.**                                                                                                  |
| `GlobalDefaultAccessMaskOption` | `COPsOnly` / `DOPsOnly` / `Both`, controls which panel types receive global default access masks. Must be set explicitly in vEL8.90.1318+. See detail below.                                                                                                                                                             |
| `DisconnectedState`             | `Same` / `Free` / `Secure`, floor state when connection to Kone is lost. **A Controller restart is required after changing this setting.**                                                                                                                                                                               |
| `DefaultMaskTrackOption`        | `SendNoTrack` / `SendSpecific` / `SendTrack`, tracking behaviour for default mask messages. Introduced in vEL8.90.1318+. Default: `SendTrack`. See detail below.                                                                                                                                                         |
| `KoneStateTransferMode`         | `0` / `1` / `2`, state transfer method. Available from vEL8.90 MR2 (introduced in vEL8.90.1318+ per the Elevator HLI source, vEL8.90.1620+ per the Perceived Issues source, use 1620+ as the safe minimum). Recommended: `2`. See detail below.                                                                          |

> **Limited Release note - "Optimised Communication with Kone":** on the Limited Release builds **vCR9.00.251212a, vCR9.10.251209a, vCR9.20.251209a, vCR9.30.251209a, vCR9.40.251209a, and vCR9.50.251209a**, three parameters no longer need to be set, as they are already defaulted to their optimal values: `PollLimit` to **1**, `DefaultMaskTrackOption` to **SendTrack**, `KoneStateTransferMode` to **2**. `GlobalDefaultAccessMaskOption` is **not** part of this optimisation, and must still be set explicitly (see its detail above).

#### `DisconnectedState` - behaviour by value

| Value    | Behaviour when connection is lost                                               |
| -------- | ------------------------------------------------------------------------------- |
| `Free`   | All floors revert to free access                                                |
| `Secure` | All floors revert to secured (no access)                                        |
| `Same`   | Floors that were already free remain free; all other floors become inaccessible |

> **Controller restart required** when changing `DisconnectedState`. The new value does not take effect until the Controller is restarted.

#### `GlobalDefaultAccessMaskOption` - what the global default masks are and why this matters

Every time the Kone ELI Lift HLI comes online, it sends global default access masks to define the default floor state per panel type and connection state:

| Mask | Panel type | Connection state |
| ---- | ---------- | ---------------- |
| GD1  | DOPs       | Connected        |
| GD2  | COPs       | Connected        |
| GD3  | DOPs       | Disconnected     |
| GD4  | COPs       | Disconnected     |

**Pre-vEL8.90 bug:** CC sent all four masks (GD1-GD4) regardless of which panel types were actually installed. Sending COP masks to a DOP-only site (or vice versa) caused the Kone system to lock out floors that should have been accessible.

**vEL8.90.1318+ fix:** `GlobalDefaultAccessMaskOption` controls which subset of masks is sent. In vEL8.90.1318+, no masks are sent automatically by default; you must set this parameter explicitly to match what is installed:

| Value      | Masks sent            | When to use                      |
| ---------- | --------------------- | -------------------------------- |
| `COPsOnly` | GD2 + GD4             | Only COPs are installed on-site  |
| `DOPsOnly` | GD1 + GD3             | Only DOPs are installed on-site  |
| `Both`     | GD1 + GD2 + GD3 + GD4 | Both COPs and DOPs are installed |

#### `DefaultMaskTrackOption` - values and when to use each

| Value          | Config string equivalent | Recommendation            | Behaviour                                                                                                                                                                                                                        |
| -------------- | ------------------------ | ------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `SendNoTrack`  | `dmtoSendNoTrack`        | Backward compatibility    | Sends both global and specific masks without acknowledgement tracking. Consistent with pre-vEL8.90 behaviour. A safe choice for sites that were working before the vEL8.90 upgrade, and will not break them.                     |
| `SendSpecific` | `dmtoSendSpecific`       | **Not recommended**       | Sends only specific default masks; no global masks during initialisation. Only use if the Kone system has been confirmed to function correctly without global masks. **Monitor the system closely after selecting this option.** |
| `SendTrack`    | `dmtoSendTrack`          | **Recommended (default)** | Sends masks with active response tracking per Kone Group Controller. The controller retries until all masks are acknowledged. If there is no response within the Offline timeout, it raises an alarm.                            |

#### `KoneStateTransferMode` - values, log confirmation, and failure mode addressed

> **Requires vEL8.90 MR2 controller software.** There is a discrepancy between source pages on the minimum version: the Elevator HLI page states vEL8.90.1318+; the Perceived Issues page states vEL8.90.1620+. Treat **vEL8.90.1620+** as the safe minimum.

**Problem it solves:** without this parameter, the C6000 running the Kone ELI lift HLI can get stuck in a state where it stops sending packets entirely, until a card is badged or default access masks change. `KoneStateTransferMode=2` prevents this by keeping the controller active in polling state.

| Value | Behaviour                                                                                  | Log string confirming active                                             |
| ----- | ------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------ |
| `0`   | Default prior to vEL8.90 MR2 (kstmSAME\_STATE), no protection                              | -                                                                        |
| `1`   | Recommended, transfers current state                                                       | `NextStateFromTopState() -> kstmCURRENT_STATECall Type 0, lift mask = 7` |
| `2`   | **Recommended (preferred)**, processes messages in polling state while states have changed | `NextStateFromTopState() -> kstmPOLLING_STATECall Type 0, lift mask = 7` |

The log strings appear in the Controller logs and confirm the mode is active. If you do not see them, the parameter is not applied or the controller software does not meet the MR2 minimum.

### Troubleshooting parameters

| Parameter             | Values          | Purpose                                        |
| --------------------- | --------------- | ---------------------------------------------- |
| `raise_debug_event=1` | -               | Enables debug events to the CC event log       |
| `log_raw_data`        | Bitwise integer | Logs raw Kone protocol data to controller logs |

**`log_raw_data` bit values:**

| Value | What is logged              |
| ----- | --------------------------- |
| `0`   | Nothing                     |
| `1`   | All messages                |
| `2`   | Connect/disconnect messages |
| `4`   | Default masks               |
| `8`   | Granted access              |
| `16`  | Kone responses              |
| `32`  | Heartbeats                  |

Values are **bitwise-additive**, so sum the values you want to combine. Examples:

* Default masks + Kone responses: `4 + 16 = 20`, giving `log_raw_data=20`
* All messages including heartbeats: `1 + 32 = 33`, giving `log_raw_data=33`

> **Source discrepancy:** the HLI Logs and Essentials page states "set `log_raw_data=2` for heartbeats". This is an error in the source. Value `2` logs connect/disconnect messages; heartbeats require value `32`. Use `log_raw_data=32` for heartbeats only, or `log_raw_data=33` for all messages plus heartbeats.

> Remove all debug parameters (`raise_debug_event`, `log_raw_data`) when fault-finding is complete, as they impact system performance. Also reset `GeneralOn=0` in the registry.

## Elevator Car HLI

One **Elevator Car HLI** item is created for each physical DOP panel and each COP panel.

> **Mixed groups not supported:** all terminals belonging to one Kone Group must be the same panel type, either all COPs or all DOPs. Mixed groups are not currently possible. Confirm panel types per group with the Kone Technician before configuration.

### Creation procedure

1. In Configuration Client, go to **Configure > Elevator Cars**.
2. Right-click in the list, then **New > Elevator Car HLI**.
3. Enter **Name**, **Description**, and **Division**.
4. **Event Response tab** - assign an Alarm Zone for elevator events from this panel.
5. **Connections tab** - assign the **Controller**, **Reader**, and parent **Elevator HLI**.
6. Set **Group** and **Car** numbers per the mapping below.
7. **Floor tab** - select the **Floor Arrangement** for this panel.
8. **Advanced tab** - if `FloorSelectTimeout` is set on the Elevator HLI, set the timeout here to the same value **plus a small buffer** to allow for network delay.
9. Complete **Cameras**, **Icons**, and **Notes** tabs as required.
10. Click **OK**.

![Elevator Car HLI - Connections tab showing Controller 6000 1 assigned, HBUS Reader 1 selected, Group 1 and Car 1 configured for a COP panel](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-426f254034d6bb16711ba72a140539778925ec58%2FSECHUB-kone-eli-config-03-elevator-car-hli-01.png?alt=media)

![Elevator Car HLI - Connections tab (second view) showing the same Group/Car mapping configuration for a COP panel on Controller 6000 1](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-46f3e5b864a63e867436cc5be55dc3799a436e76%2FSECHUB-kone-eli-config-04-elevator-car-hli-02.png?alt=media)

### Group and car number mapping

> **COP and DOP use entirely different numbering systems.** Do not apply DOP offsets to COPs or vice versa.

**For COPs (panel inside the elevator car):**

| CC field | Kone value            |
| -------- | --------------------- |
| Group    | Kone Group ID (1-100) |
| Car      | Kone Elevator ID      |

**For DOPs (landing panel outside the car):**

| CC field | Kone value                                                              |
| -------- | ----------------------------------------------------------------------- |
| Group    | Kone DOP Floor ID **+ 99** (for example DOP Floor ID 2 gives Group 101) |
| Car      | Kone DOP Terminal ID                                                    |

> **Offset clarification:** the two Kone source pages use inconsistent wording, one says "+100 offset", the other says "+99 offset". The correct formula is **DOP Floor ID + 99**, which gives Group 100 for the first floor (Floor ID 1), Group 101 for the second (Floor ID 2), and so on. This is confirmed by the worked example in the source: Floor 2, DOP Floor ID 2, Group = 2 + 99 = 101.

> The +99 offset places DOP groups at 100+, distinguishing DOPs from COPs (which use Group IDs 1-100).

## Floor Arrangement

Defines which floors a cardholder profile can access. Each floor in the arrangement is mapped to an access zone.

![Floor Arrangement Properties dialog - 8 floors configured (4 front + 4 rear), floor designators DM01-DM04, showing floor-to-access-zone mapping](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-045769eba6a1af5e4c9bc6b7c0759b45f25ffd45%2FSECHUB-kone-eli-config-05-floor-arrangement-diagram.png?alt=media)

* **No access zone assigned** means that floor is free access for all cardholders.
* **Secure zone assigned** means the cardholder must have access rights to that zone to enable the floor button.

> **Floor numbers are protocol numbers, not button labels.** The Floor column in the arrangement refers to the floor number used within the HLI protocol, not the number embossed on the elevator button. These can differ. Floor numbers can also differ between elevator groups within the same site. Confirm the protocol floor numbers with the Kone Technician before building the arrangement.

> **Number of floors supported is protocol-dependent.** Confirm with the Kone Technician.

> **Performance note:** when a Floor Arrangement item is modified, CC sends updated access data for every affected cardholder to the Controller. A large change (for example modifying a Floor Arrangement used by thousands of cardholders) generates a large message queue, visible on the Controller's Status and Overrides tab. Schedule large access changes during off-peak hours.

### Rear-door lifts

For lifts with both front and rear doors, the Floor Arrangement must include **double the physical floor count**:

* Floors 1-4 (physical) means rear-door floors are represented as floors 5-8 in the arrangement.
* Floor N (front) corresponds to Floor N + {physical floor count} (rear).

**Floors with only one door within a rear-door lift:** even if a specific floor only has a front door or only a rear door, both floor slots must still be defined in the arrangement. The unused door direction gets no access zone assigned (treated as free access).

**Mixed front/rear-door buildings:** if the building has elevators where some serve rear-door floors and some do not, create separate Floor Arrangements for each configuration, then assign DOPs the arrangement that matches the doors they physically serve. Example:

* DOP 1 and 4 (serving Lift 1, all floors front and rear, except Ground and Level 2 rear) means Floor Arrangement A.
* DOP 2 and 5 (serving Lifts 2 and 3, all floors, except Ground and Level 2 front) means Floor Arrangement B.
* DOP 3 and 6 (serving Lift 4 only) means Floor Arrangement C.

![Mixed front/rear building DOP assignment diagram - 4 lifts, DOP panels 1-6 each assigned a Floor Arrangement that matches the physical doors they serve](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-0d0f6a67f8f9d390c0ab3cc6079fd89249bce0a8%2FSECHUB-kone-eli-config-floor-01.png?alt=media)

![Floor Arrangement configuration screenshot - showing floor rows, access zone assignments, and front/rear door columns](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-60b2e9b6933fba406bd2deacc8f45bc4d63e76b1%2FSECHUB-kone-eli-config-floor-02.png?alt=media)

![Floor Arrangement configuration screenshot - example with multiple floors and mixed access zone assignments](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-007d042cdfa183f71fe5306986150bf093e59327%2FSECHUB-kone-eli-config-floor-03.png?alt=media)

![Floor Arrangement configuration screenshot - additional example showing floor number to zone mapping](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-642e8fcdbc2dcba63f4eaedff40adfe4a64d8740%2FSECHUB-kone-eli-config-floor-04.png?alt=media)

## COP (Car-Operating Panel)

The button panel **inside the elevator car**.

![Elevator interior diagram - front and rear COP panels highlighted in red, showing both front-door and rear-door button panels inside the car](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-752206f461365ed58a505514de96c46807ef5158%2FSECHUB-kone-eli-config-cop-01.png?alt=media)

![Panel/Terminal grouping diagram - Cars 1&2, 3&4, 5&6 each paired with 4 floor levels, illustrating how COP Group IDs map to elevator groups](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-654b1cebe51bc1069d454a979d0d4181fed371b5%2FSECHUB-kone-eli-config-cop-02.png?alt=media)

| CC field | Value                                |
| -------- | ------------------------------------ |
| Group    | Kone Panel/Terminal/Group ID (1-100) |
| Car      | Kone Elevator/Shaft/Lift ID          |

One COP item per elevator car. Both values are provided by the Kone Technician.

![COP Elevator Car HLI Properties - Connections tab showing Group and Car configuration for a COP panel](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-7d9dbf9cc9f31dc8d34f35a140c890ba9295f5ee%2FSECHUB-kone-eli-config-cop-03.png?alt=media)

![COP Elevator Car HLI Properties - additional configuration view showing completed COP item setup](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-7c9f51f33d9ee030b7be91613e3edd4c7e1fae72%2FSECHUB-kone-eli-config-cop-04.png?alt=media)

## DOP (Destination-Operating Panel)

The call panel **outside the elevator car**, at each floor landing.

![Floor landing diagram - two elevator doors (A and B) at a landing, with the DOP pedestal reader highlighted showing where the Kone DOP panel is positioned](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-594b04a69fa9b169802b8614c76374f8acc50dd0%2FSECHUB-kone-eli-config-dop-01.png?alt=media)

| CC field | Value                                                                                 |
| -------- | ------------------------------------------------------------------------------------- |
| Group    | Kone DOP Floor ID + 99 (Group 100 = first floor, Group 101 = second floor, and so on) |
| Car      | Kone DOP Terminal ID                                                                  |

**All DOPs on the same floor share the same Group number** (same DOP Floor ID) and differ only in their Car number (different DOP Terminal IDs).

**Number of DOP items to configure = number of physical Kone DOP panels**, not the number of lifts. The Kone system handles grouping of lifts to DOPs internally; CC must simply mirror the physical DOP count.

> **Do not use the \[Gallagher] section** in DOP configuration, even if the Kone Technician recommends it. The vast majority of DOP access issues are caused by an incorrect Floor Arrangement assignment or incorrect Group/Car mapping. Resolve those first before touching the \[Gallagher] section.

![DOP Elevator Car HLI Properties - Connections tab showing Group and Car configuration for a DOP panel](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-bec53eb196bed7d01153fa0ab1665e1e8b9a2ad3%2FSECHUB-kone-eli-config-dop-02.png?alt=media)

![DOP configuration screenshot - example showing completed DOP item with Group 101 (DOP Floor ID 2 + 99) and Car (Terminal ID) assigned](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-7130d2cfb330fb47f20baa67e656875155805c08%2FSECHUB-kone-eli-config-dop-03.png?alt=media)

![DOP configuration screenshot - Floor tab showing the Floor Arrangement assignment for this DOP panel](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-dfd8c4be8e9c6aa6e57aee25e07469ee17abb238%2FSECHUB-kone-eli-config-dop-04.png?alt=media)

![DOP configuration screenshot - additional view of DOP item properties](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-73b7f1084e23f7448080af46e087802185e63dd2%2FSECHUB-kone-eli-config-dop-05.png?alt=media)

![DOP configuration screenshot - final DOP setup example with all fields completed](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-e1360d0a3ce87811bedddb52be2a633f1032ec31%2FSECHUB-kone-eli-config-dop-06.png?alt=media)

## Kone ACS Msg Receiver Simulator

The **Kone ACS Msg Receiver Simulator v1.5** can be used to test the Elevator HLI connection and verify CC is sending correct messages without a live Kone system.

![Kone ACS Msg Receiver Simulator v1.5 interface - showing group and car configuration fields, connection status, and message log](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-43e0c19486998e452eea4af510f00bae7b59db6a%2FSECHUB-kone-eli-config-simulator-01.png?alt=media)

> **After changing any parameter in the Kone Simulator, stop and restart the TCP/IP connection** for the change to take effect.

There may be multiple elevator cars per elevator group in the simulator, depending on how the Kone system has assigned cars to groups.

### DOP simulator field mapping

| Simulator field     | Maps to CC value                            |
| ------------------- | ------------------------------------------- |
| `dop_id`            | Car # (DOP Terminal ID)                     |
| `dop_Floor_id`      | Group # (100+, the DOP Floor ID + 99 value) |
| `destination_floor` | Floor number                                |

![DOP HLI Kone Properties - Connections tab showing Group 102 and Car 1 configured for DOP simulation (Group 102 = DOP Floor ID 3 + 99)](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-14782dfdff7221c61c04340c7d84829eee91b714%2FSECHUB-kone-eli-config-simulator-02.png?alt=media)

### COP simulator field mapping

| Simulator field | Maps to CC value               |
| --------------- | ------------------------------ |
| `elevator_id`   | Car # (Elevator/Shaft/Lift ID) |
| `group_id`      | Group # (1-100, Kone Group ID) |

![Simulator configuration screenshot - additional example showing COP group and car ID mapping in the simulator interface](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-19a1036c1fb2e6f7bda5c9e679998de95f99df93%2FSECHUB-kone-eli-config-simulator-03.png?alt=media)


---

# 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/kone/kone-eli/kone-eli-configuration.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.