Communication Guide, ©ComAp – March 2014 129
IGS-NT Communication Guide 03-2014.pdf
MSB1 = BCD(hour)
LSB1 = BCD(minute)
MSB2 = BCD(second)
LSB2 = 0
example:
MSB1 = 20 (HEX)
LSB1 = 24 (HEX)
MSB2 = 02 (HEX)
LSB2 = 0
Time = 20:24:02
Field n bytes
C-declaratione: unsigned char x[n]
MSB1 = x[0]
LSB1 = x[1]
MSB2 = x[2]
LSB2 = x[3]
…
n is even number:
MSBm-1 = x[n-2]
LSBm = x[n-1]
n is odd number:
MSBm-1 = x[n-1]
LSBm = 0
String
(Zero terminated string)
depends on
register
number
string characters coding depends on
chosen language (8bit coding, EUC)
Communication status
Communication object number:
24571
Operation:
Read only
Data type:
Binary32
Meaning:
Bit 0 Internal terminal in InteliSys does not work (0 for other controllers)
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.
To Next Page
Loading...
Need help?
General
