IGS-NT Communication Guide
150
Note: The MODE< and MODE> commands have not been implemented to the register oriented modbus
commands.
10.4 Error list
If the controller encounters an error when processing the query, it returns the exceptional response instead of
the normal one to the terminal. An exception has always the value 2 (Illegal Data Address). After receiving the
exceptional response, the terminal should read the communication object 24523 containing the last error
specification. The meaning of an error can be found out from the following table.
MSB1
(*)
LSB1
(*)
MSB2
(*)
LSB2
(*)
Meaning
0 0 0 0 No error.
0 0 2 6 Comm. Object nonexistent.
0 0 1 6
Illegal access:
Read (write) of the communication object. Object intended only for write
(read).
255 0 0 8 Controller application isn’t active.
254 0 0 8 Inexpectant message.
253 0 0 8 No more unread records in event history.
252 0 0 8 Setpoint not defined in controller configuration.
251 0 0 8 Bad write data length.
250 0 0 8 Invalid password.
249 0 0 8 No more free space in front for EEPROM.
248 0 0 8 Too long parameter.
247 0 0 8 Invalid controller configuration.
246 0 0 8 Undefined command.
245 0 0 8 Command can’t be done.
244 0 0 8 Too long data answer form peripheries (max. 4B).
243 0 0 8 Too long data for peripheries (max. 4B).
242 0 0 8 Unavailable peripheries.
241 0 0 8 Required operation isn’t available in peripheries.
240 0 0 8
Operation cannot be performed now, the terminal has to repeat the
request. This error can occur when an operation with EEPROM memory
(setpoint write, history record read) is required at the same time while an
internal EEPROM write cycle takes place.
239 0 0 8 Controller programming can’t be carry out.
238 0 0 8 Write cannot be performed – power supply failure detected.
237 0 0 8
Another active call request is present.
This error code can be returned by the controller as the response to the
communication object. Object 24540 write – active call termination.
236 0 0 8 Programming error.
To Next Page
Loading...
Need help?
General
