IGS-NT Communication Guide
149
Communication object number:
Bit 1 Invalid controller software (based on CRC).
Bit 2 Invalid controller configuration (based on CRC).
Bit 3 In the event history is present at least one unread record.
Bit 4
P type setpoints are invalid. P type setpoints are representing the controller setpoints. Values
of these setpoints can be set from connected terminals. If these setpoints are invalid, the
application functions are blocked. Setpoints recovery is needed.
Bit 5
R type setpoints are invalid. R type setpoints are representing the data, that is only initialized
from connected terminals, but its updating is made by the controller itself (e.g. statistic or time
and date). If these setpoints are invalid, their change from the controller is blocked. Setpoints
recovery is needed.
Bit 6 The event history was cleared.
Bit 7 The event history was filled up at least once.
Bit 8 P type setpoint change occurred (reading resets this bit).
Bit 9 R type setpoint change occurred (reading resets this bit).
Bit 10 Controller type – see the table below.
Bit 11 Alarm list not empty.
Bit 12 Alarm list change (reading resets this bit).
Bit 13 New item added into alarm list (reading resets this bit).
Bit 14 Internal controller terminal is locked up for setpoint change.
Bit 15 Invalid configuration format.
Bit 16 Diagnostic codes change (reading resets this bit, only for IL-NT /ID controllers).
Bits 20 Controller type (*).
Bit 21-17 Reserve (= 0).
Bits 22-21 Password level for Setpoints and Commands write (only for IL-NT /ID controllers).
Bit 23 Controller was initiated.
Bits 28-24 Communication module version.
Bits 29 Remote terminal is connected.
Bits 30 Controller type – see the table below.
Bits 31 Reserve (= 0)
(*) Controller type
Bit 20 Bit 30 Bit 10 Controller
0 0 0 InteliSys
0 0 1 InteliGen
0 1 0 IL-NT
0 1 1 InteliDrive
1 0 0 IG/IS-NT
1 0 1 Reserve
1 1 0 Reserve
1 1 1 Reserve
To Next Page
Loading...
Need help?
General
