Modbus Interface

This article describes the Modbus interface available in Exigo.

 The Modbus Interface is not official implemented.

The Exigo Controller implements a Modbus TCP slave (server) interface on the standard Modbus port, TCP port 502. The Modbus interface in Exigo has two main features:

• Status about amplifiers and panels connected to the Controller can be read from Modbus 16 bit input registers
• Pre-programmed PA calls and announcements can be triggered by writing to Modbus coil registers.

Exigo status to Modbus

Selected Exigo failure statuses are exported to Modbus 16 bit input registers. The allocation of registers and bits is fixed.
There is no configuration of this feature (except for opening up Modbus in firewall). SCADA must poll these registers. A range of input registers can be read using Modbus function code 2.

There is one 16 bit register for each panel, amplifier and amplifier line. Physical devices like panels and amplifier have one 16 bit register describing the device level status.
Amplifiers have in addition one 16 bit register for each audio line. The index of each device and line is displayed in the Exigo Management Tool (EMT) in the "StInd" field.

The 16 bit device/line statuses is interpreted as a bitmap:

• Bit 0 is set in all registers that represent a configured item. Unused registers read as zero.
  • Remaining bits may be set to indicate a fault situation.
• Bit 1 on device level statuses means the controller has lost contact with the device.
• Bit 2 on speaker line mean that the speaker line is faulty (voltage test).

Availability

The Modbus functionality is not yet official implemented.
Please contact AlphaSupport if you are interested in the Modbus functionality.