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

# Configure KONE RCGIF Plugin

Configure KONE RCGIF turnstile calls and multi-controller KCEGC deployments.

| Attribute    | Value                                                                                               |
| ------------ | --------------------------------------------------------------------------------------------------- |
| Status       | Current, optional extension of Kone ELI                                                             |
| Relationship | **Extends Kone ELI.** KCEGC is the base Kone integration in CC core; RCGIF adds a Middleware plugin |
| Purpose      | Automate elevator calls from turnstiles (RCGIF) and support multi-controller Kone Groups (KCEGC1)   |

## Overview - KCEGC vs RCGIF

**KCEGC** is the base Kone integration in Command Centre core and supports regular lift operations.

**RCGIF Plugin** adds support for **calling an elevator**, ready to take a cardholder to their home floor, when they enter the building through a **turnstile**. Both KCEGC and RCGIF are in the core; RCGIF adds a Middleware plugin on top.

## Multi-controller support (KCEGC1)

The existing Gallagher Kone ELI HLI integration allowed one **primary Kone Group Controller (KGC)** and one backup KGC.

The newer **Kone KCEGC1** setup expands this:

* Up to **5 KCEGCs** allowed in one Kone Group.
* At any given time, **one master KCEGC** is active; the others are backups.
* When the master KCEGC fails, a **backup KCEGC** detects the situation and becomes the new master.
* The protocols stay the same: **Kone ELI + Kone RCGIF plugin**.

The Gallagher Kone KCEGC integration allows Command Centre to support the Kone ELI protocol in a KCEGC setup. That is, it supports more than 2 KCEGCs in one Kone Group.

## Important: Turnstile DOP event response

By default, the **Turnstile DOP External System Items'** event response **Group 0** is set to **not log an event**.

> ⚠️ **You must change this to log an event** via an Action Plan on each of the Turnstile DOP items. Otherwise the response log will not be visible, and troubleshooting becomes very difficult.

This is one of the most common gotchas during RCGIF deployment.


---

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