Skip to content
For the complete documentation index, see llms.txt. This page is also available as Markdown.

KONE

Choose a KONE integration method for elevator access control or cardholder synchronization.

Gallagher integrates with Kone elevator systems through three distinct methods. The correct method depends on the site's Kone infrastructure and the Command Centre version in use.

Note: There are two versions of Kone HLI. Which version applies depends on the Command Centre version. Confirm the CC version before configuring.

Variants

Variant
Status
Architecture
Licensing
Use case

Current, legacy / serial

RS232 from C6000 to Kone Controller (Kone Protocol v2.5)

Non-licensed

Older Kone systems with Conventional Dispatching

Current, IP-based

TCP/IP per Kone Group Controller Access Control Interface Spec

Licensed

Current Ethernet-based integration; supports Destination Control

Current, data sync only

Service-based sync to KONE Office Flow

Licensed (Kone Access=1)

Cardholder sync only, NOT for elevator access control

Add-ons / extensions to Kone ELI

Extension
Status
Purpose

Current

Automates turnstile-triggered elevator calls; supports multi-controller (KCEGC1) setups

At a glance

Kone Serial (Standard)

Serial-based integration using Kone Protocol v2.5, intended for older Kone elevator systems. An RS232 cable runs directly from a Controller 6000 to the Kone Controller. Non-licensed.

  • One serial connection per C6000 (single RS232 port).

  • Up to 8 Elevator Shafts/Cars per Controller (RS232); 2 per Controller (TCP/IP).

  • See Kone Serial (Standard) for full details.

Kone ELI (IP-based)

IP-based integration implemented per Kone's Group Controller Access Control Interface Specification Rev 1.8, the current Ethernet-based method.

The Kone ELI integration creates four item types in Command Centre:

Kone ELI HLI 2 highlighted in the Hardware panel under Controller 7000, visible in the Alarm Viewer - the HLI item sits directly under the controller in the hardware hierarchy
  • Kone ELI HLI - Hardware item under the assigned controller. Visible in the Alarm Viewer.

  • Floor Arrangement - defines which floors a cardholder is permitted to reach; assigned to cardholders or access groups.

  • DOP (Door Operating Panel) - represents the call panel at each floor landing (outside the elevator car).

  • COP (Car Operating Panel) - represents the button panel inside the elevator car.

The three remaining item types as they appear in the Elevator Car master list (Configuration Client):

Floor Arrangement 1 highlighted in the Elevator Car master list - the Floor Arrangement item sits alongside the DOP and COP panel items
Kone DOP in 5th Floor / Panel 1 highlighted in the Elevator Car master list - the Door Operating Panel (landing call panel) item
Kone COP Panel 1 highlighted in the Elevator Car master list - the Car Operating Panel (in-car buttons) item

For deep configuration reference, see Kone ELI, Kone ELI Configuration, and Kone ELI Troubleshooting.

For turnstile-triggered calls and multi-controller deployments, see Kone ELI - RCGIF Plugin.

Kone Office Flow

Synchronises Command Centre cardholder records with the KONE Office Flow system on a regular basis.

  • Not for elevator access control - data synchronisation only.

  • Operates independently of Kone Serial and Kone ELI.

  • See Kone Office Flow for licensing, configuration items (Kone Service, Kone Validity Time, Kone Elevator Access), and release-note reference.

Choosing between variants

  • Site has older Kone equipment using Conventional Dispatching and Kone Protocol v2.5? Use Kone Serial (Standard).

  • Site has a modern Kone Group Controller (KGC/KCEGC) supporting TCP/IP? Use Kone ELI.

  • Site wants turnstile-triggered elevator calls, or has multiple KCEGCs in one Kone Group? Use Kone ELI - RCGIF Plugin (extends Kone ELI).

  • Customer wants to sync cardholders to KONE Office Flow (a separate building/people management system)? Use Kone Office Flow (this is data sync, not access control).

Kone Office Flow can run alongside Kone ELI or Kone Serial, because they serve different purposes. Kone Serial and Kone ELI are typically not deployed together at the same elevator system.


🔗 Related

  • HLI Reference. Cross-vendor interface types and system limits.

  • Schindler. The other destination-control vendor integration.

Last updated

Was this helpful?