InteliLite Global Guide
153
SNMP notifications
Except the request-response communication model, in which the communication is controlled by the Manager,
there are also messages that the Agent sends without any requests. These messages are called „Notifications“
and inform the Manager about significant events occurred in the Agent.
The controller can send notifications to two different SNMP Managers (two different IP addresses). The
addresses are to be adjusted in the CM-Ethernet setpoint group by the setpoints SNMP Traps IP Address 1
(page 382) and SNMP Traps IP Address 2 (page 383). If the Manager address is not adjusted the particular
notification channel is off. The controller will send the notifications in format adjusted by the setpoint SNMP
Trap Format.
Each notification (kind of event) is identified by an unique identifier (Trap ID in SNMPv1 or Notification OID
in SNMPv2). This unique identifier gives the specific meaning to the notification message, e.g. Protection 1.
level - Fuel Level - alarm activated.
All possible notifications and their identifiers are listed in the MIB table.
The notification message also contains controller name, serial number and textual description of the event.
6.2.2 MODBUS-RTU, MODBUS/TCP
MODBUS protocol is used for integration of the controller into a building management system or for remote
monitoring via 3rd party monitoring tools.
MODBUS-RTU can be used on serial interfaces (CM-RS232-485 module is required). The MODBUS-RTU
server must be activated by switching the setpoint COM1 Mode (page 343) or COM2 Mode (page 345)
into the Modbus position. The serial speed for MODBUS-RTU communication is to be adjusted by the
setpoint COM1 MODBUS Communication Speed (page 344) or COM2 MODBUS Communication
Speed (page 346).
MODBUS/TCP can be used on the ethernet interface (CM-Ethernet module is required). Up to 2 clients can
be connected simultaneously. The MODBUS/TCP server must be activated by the setpoint MODBUS
Server (page 381).
MODBUS, MODBUS/TCP protocol can be used simultaneously with Web connection and direct
ethernet/AirGate connection.
IMPORTANT: Do not write setpoint repeatedly(e.g. power control form a PLC repeated writing of
baseload setpoint via Modbus). The setpoints are stored in EEPROM memory. which can be
overwritten up to 10
5
times without risk of damage or data loss, but may become damaged, when
the allowed number of writing cycles is exceeded!
Note: Modbus-RTU serial communication mode is 8-N-1 - startbit 1, 8 data bits, no parity and 1 stopbit.
Address space
The object address space is separated into several areas as described in the table below. The actual mapping of
specific controller data objects to specific MODBUS addresses, which depends on configuration, can be
exported into a text file from the appropriate controller archive using InteliConfig. There are several special
registers with fixed meaning (reserved registers) which are listed in a separate table in this chapter.
To Next Page
Loading...
Need help?
General
