> 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.md).

# KONE ELI

Understand KONE ELI architecture, licensing, access behavior, and optional RCGIF calls.

Kone ELI (Elevator Link Interface) is the **IP-based** integration method between Gallagher Command Centre and the Kone elevator system. It is implemented per Kone's **Socket Based Destination Call Giving Interface Specification Rev 1.5.1 (829390)**.

Optionally, the **Kone RCGIF Plugin** enables automated lift calls after access is granted.

{% hint style="info" %}
For the three Kone integration types and when to use ELI vs Serial vs Office Flow, see [Kone Integration](/knowledge-hub/products/integrations/elevators/kone.md).
{% endhint %}

## Architecture

![Kone ELI architecture - CC Server and Workstation connected via Ethernet TCP/IP to Gallagher C6000 controllers (each supporting 2 lifts) and directly to Elevator Group Controller supporting up to 8 lifts](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-20e7d8f856f11d9e60c0ddad6a5f8e862c192486%2FSECHUB-kone-eli-01-architecture.png?alt=media)

* TCP/IP connection required between the Gallagher controller and the **primary and backup** Kone Group Controllers.
* Each C6000 supports up to **2 elevator lifts**.
* The Kone Elevator Group Controller supports up to **8 lifts**.

## How it works

An **access zone** is assigned to each floor the elevator travels to, representing the area immediately outside the elevator on that floor.

* **Free access zone** - floor select button enabled by default.
* **Secure zone** - floor select button disabled by default.
* Every cardholder has access to floors that Gallagher does not control.

**Access sequence:**

1. Cardholder presents credential at the elevator car reader.
2. Controller sends a message to the elevator system enabling floor buttons for permitted floors.
3. Cardholder selects a floor.
4. After floor selection or timeout, buttons return to the default state.

**Connection polling:** the controller polls the elevator system at regular intervals. If the connection is lost, an alarm is raised. Each time floor access changes, Gallagher sends a message to the elevator system, and the elevator replies to each poll.

## Licensing

```
[Features]
KoneELI=1
```

**If the RCGIF plugin is also required:**

```
[Limits]
Event Source=n

[Plugin]
PluginX=KoneRCGIF
```

## Lost connection behaviour

When the connection between the controller and the elevator system is lost:

* The elevator system determines access. Normally all floors revert to **free access**.
* The controller continues polling.
* Communication re-establishes automatically, and floors re-secure as soon as the elevator system responds.

## Reader and access behaviour

* **Second cardholder supersedes first:** if a second cardholder badges before the first has selected a floor, the second access supersedes the first, and the first cardholder must badge again. This also prevents access from a previous cardholder blocking the next.
* **PIN-required floors:** floor buttons will not enable unless the cardholder correctly enters their PIN. Non-PIN floors are unaffected.

### Kone reader compatibility

| Reader type                                                 | Supported?   |
| ----------------------------------------------------------- | ------------ |
| Kone-controlled reader, **not wired** to a Gallagher C6000  | **No**       |
| Kone-branded Wiegand reader, **wired** to a Gallagher C6000 | **May work** |

### Rear door access

Kone ELI supports both **Front** and **Rear** door access. Refer to the Elevator HLI and Floor Arrangement configuration pages for setup details.

## Kone RCGIF Plugin

An external system Plugin that sends lift calls via the **FTCAPI middleware service**. It automates calling the lift to a cardholder's location after they badge at an entry reader. It also supports automatic or manual destination floor selection from a turnstile, kiosk, or panel. Refer to the RCGIF Release Notes for full plugin configuration detail.

### Plugin API string

The most common configuration uses a personalised action to trigger a virtual output, which sends an API string to the Kone Group Controller:

```
SrcFloor=1; DstFloor=5; SrcSide=0; DstCallType=0
```

| Parameter     | Values  | Description                                                       |
| ------------- | ------- | ----------------------------------------------------------------- |
| `SrcFloor`    | Integer | Source (pickup) floor number                                      |
| `DstFloor`    | Integer | Destination floor number                                          |
| `SrcSide`     | 0 / 1   | Door side: 0 = Front, 1 = Rear                                    |
| `DstCallType` | 0-30    | Call priority type (for example 0 = standard, VIP = higher value) |

## Burst traffic caution

> **Caution (applies to all Kone ELI deployments, not only RCGIF):** the Kone system is sensitive to burst traffic and may develop intermittent connection issues. Set **Poll=36000** and **PollLimit=1** to mitigate. On vEL8.90.1318+ sites, omit `Poll` entirely and set only `PollLimit=1`.

***

🔗 **Related**

* [Kone ELI Configuration](/knowledge-hub/products/integrations/elevators/kone/kone-eli/kone-eli-configuration.md). Elevator HLI, DOP, COP and Floor Arrangement setup.
* [Kone ELI Troubleshooting](/knowledge-hub/products/integrations/elevators/kone/kone-eli/kone-eli-troubleshooting.md). Polling, default masks, and known issues.
* [Kone ELI - RCGIF Plugin](/knowledge-hub/products/integrations/elevators/kone/kone-eli/kone-eli-rcgif-plugin.md). Turnstile-triggered calls and multi-controller setups.


---

# 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.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.