IR WIKI

Lift Interfacing (EMS)

5 min read

Lift Interfacing (EMS)

Overview

The Lift Interfacing (EMS) communications task enables high-level integration between an Integriti controller and elevator/lift systems from multiple vendors. It supports communication via RS232 (using a UniBus UART module) or IP (TCP/UDP), depending on the lift manufacturer’s interface.

Supported lift vendors and interface types:

Lift VendorInterface TypeDSCHome Floor CallingSoftware Floor Release
SchindlerIP/PortYesYesYes
KONEIPYesYesYes
KONEIP/PortYesYesNo
KONERS232YesYesYes
Otis CompassIPYesNoYes
OtisRS232YesNoYes
ThyssenKruppRS232NoNoYes
ThyssenKruppIPNoNoYes
New LiftIPYesYesYes
MitsubishiIPYesYesYes
IR Low LevelExpander ModuleNoNoYes

Only one EMS communications task can exist per controller. Only one lift interface type is supported per controller.

Hardware Limitations

  • Up to 594 readers (99 reader modules + 99 intelligent reader modules)
  • 10,000 Floor lists
  • 2,000 Lift Lists
  • 250 Floors
  • 250 Lifts
  • 250 Lift Types
  • 250 Qualified Lift Types
  • 128 Lift Groups

Prerequisites

  • Integriti controller with smart card
  • Integriti controller EMS communications task license
  • Integriti UniBus UART module (for RS232 connections only)
  • Integriti management software
  • Reader module(s)
  • Expander module(s) and UniBus Lift Interface Board (for low-level only)
  • Button Feedback UniBus module(s) (for low-level button feedback only)
  • Network configured to lift manufacturer’s specifications (for IP connections)

Note: Inner Range recommends all systems be installed and maintained by Factory Certified Technicians.

Step-by-Step

1. Controller Configuration Overview

Configure in this order:

  1. Add modules, UniBus UART module, and license smart card to the controller
  2. Connect to Integriti management software
  3. Program Lift Floors
  4. Program Lift Groups
  5. Program Lift Cars
  6. Program Communications Task (the EMS task)
  7. Program Modules (reader modules for lift control)
  8. Program Users
  9. Test

2. Lift Floor Programming

Access via: Floors tab → lift floor editor.

  • Create a Lift Floor record for each physical floor.
  • If lift cars have front and rear doors, create separate floor records for front and rear.
  • Lift floors can be associated with more than one lift car (e.g., a “Ground Floor” record mapped across all cars).

3. Lift Type Programming

Access via: Lift Types tab.

  1. Expand Properties → Entry
  2. Set Credential Mode to the desired credential entry method
  3. Configure Dual User, Anti-Passback, and Entry Button options as needed
  4. Save and close

4. Lift Group Programming

Access via: Lift Groups tab.

Lift Groups map Logical Floor entities in Integriti to physical floors accessible by lift cars. Required for high-level interfaces only.

For each Lift Group:

  1. Create the group and give it a name
  2. Add EMS Floor Mappings — map each EMS floor to the Integriti Lift Floor record
  3. Enter the EMS Floor number
  4. Tick Is Rear Door if the floor record is for a rear door
  5. Set EMS Group (must be ≥ 1)
  6. Set Number of Floors (0 = auto-detect from mappings)
  7. Save

5. Lift Car Programming

Access via: Lift Cars tab.

  1. Expand Lift Configuration:

    • Set Lift Mode: Low Level (No Button Feedback), Low Level (Button Feedback), or High Level / EMS
    • Select Lift Type created earlier
    • Select Lift Floors this car can reach
    • Set Button On Time (total time user has to select a floor after presenting credential)
    • Set Handicapped Button On Time
    • Optionally configure a Valid Auxiliary to activate on valid credential

  2. For High Level lifts, expand High Level:

    • Set EMS Type
    • Select Lift Group for floor mapping
    • Program EMS Lift ID
    • Program EMS Floor Number (for DOPs and Home Floor Callers)

  3. For Low Level lifts, expand Low Level:

    • Select the Module used for the low-level interface
    • Optionally select an Error Aux output
    • Configure Add Floors, Button Enable Hold Time, etc.

  4. Optionally add Restricted Floors to limit which floors this car can access.

6. Reader Module Programming

Access via: Reader Modules or Intelligent Reader Modules tab.

  1. Expand Readers under Properties
  2. Set Reader Purpose to “Control a Lift”
  3. Under Access Control, assign the reader to a lift car
  4. Save

7. Communications Task Programming

Access via: Communications Tasks tab.

  1. Create a new communications task
  2. Set Type to EMS
  3. Leave Mode and Backup Task blank
  4. Select the EMS Protocol matching your lift system
  5. Optionally set an Online Input to reflect task status

For RS232 connections:

  • Expand RS-232 Serial Interface
  • Select the port
  • Set Baud, Data bits, Stop bits, and Parity to match the lift system

For IP connections:

  • Expand Primary Ethernet Connection
  • Enter Primary Server IP Address (or host name if DNS is present)
  • Enter TCP Port
  • Repeat for Secondary Ethernet Connection if a backup controller is available

For KONE IP only:

  • Expand Kone IP Options
  • Configure Car Panel Offline Mask and Destination Panel Offline Mask
  • Set Offline Lift Group for offline mask mappings

8. Otis HLI Specific Configuration

For Otis IP interfaces, only two options are required:

  1. Set EMS Protocol to “Otis (IP)”
  2. Set Otis Version to match the lift system

The controller’s network interface must be configured according to the Otis Contract Parameters document. Access via the controller terminal:

  1. Log in: [0], [1], [Ok]
  2. NIC programming: [Menu], [7], [3], [4]
  3. Enter IP address
  4. Enter Gateway
  5. Enter Subnet Mask
  6. Skip primary and secondary DNS
  7. Disable DHCP: [5], [Ok], then [End]

9. Schindler HLI

For Schindler HLI configuration, refer to the separate Schindler Lift Interface guide. EMS configuration options for Schindler are otherwise covered in this document.

Verification

  1. Confirm the communications task shows as Online in the management software
  2. Verify the Online Input (if configured) is sealed and not in alarm
  3. Present valid credentials at a lift reader and confirm floor buttons activate for the correct duration
  4. Select floors and verify the lift system responds correctly
  5. Test restricted floors — users without access should not be able to select those floors
  6. Test DSC (Destination Selection Control) if supported by your lift vendor
  7. Test Home Floor Calling if supported
  8. For low-level interfaces, verify button feedback works correctly

Troubleshooting

SymptomPossible CauseAction
HLI Buffer Overrun — controller cannot communicate with lift systemPhysical connection issueCheck physical connection between controller and lift system
Continual online/offline messagesConfiguration mismatchVerify controller lift configuration matches the lift system; check physical connection
Continual online/offline messages (TCP/UDP)Network issueCheck TCP/UDP connectivity to lift interface
Floors not respondingWrong EMS ProtocolVerify EMS Protocol matches lift manufacturer
Reader not controlling liftReader Purpose not setSet Reader Purpose to “Control a Lift”

Graph View

Backlinks