
http://www2.merrick-inc.com/mct/GCMModbus.pdf Page 11 2014-05-18/Lars
Counter for ModBus RTU and UISServer telegrams who have had the end condition
determined by absence of incoming characters for enddl (see below) 5 ms ticks.
Min wait in in 5 ms ticks for absence of incoming characters to determine end
condition.
Note 1. Rxlfm indicates what kind of format error occurred last, as rxfme increments. In some
cases, a NAK response is sent back to the master/client. This is indicated in the
following table with a numerical value. An “x” indicates that the telegram will be ignored
for the format error. An empty field indicates that the specific format error does not
apply for this protocol.
Illegal receiver buffer length
Illegal characters in telegram – Modbus ASCII only
Function 3 telegram not 8 bytes
Unknown/Unsupported Function
Byte count disagrees with buffer length Function 16
Byte count disagrees with length field Function 16
Illegal end sequence: LF not following CR – Modbus ASCII only
ISR Receiver buffer overrun
ISR Transmitter buffer overrun
ISR Characters received after end of message, before reply sent
ISR Illegal (default) receiver state (COMrxsta)
Outside CIT legal read space on CIT read or write
Unsupported subfunction for function 8 telegram
Function 8 telegram not 8 bytes
Write to read-only space in CIT
Transmitter length rollover – Should never happen
Receiving characters while transmitting
Use the integrity bit.
In the PLC, toggle the integrity bits (Word 44, bit 7) every 2 seconds. Monitor the integrity echo bit
(Word 16 bit 7). If they stop toggling, communications has failed, and appropriate steps can be
taken. The integrity bit can be monitored in the TCMI CIT Diagnostic Screen (P1), and the GCM
can be set up to monitor the activity of the integrity bit, potentially generating a Warning or Fault if
the bit stops toggling.
PLC Program examples.
There are plenty of PLC example programs available in the Merrick MCT web site. See
http://www2.merrick-inc.com/mct/.
Comentarios a estos manuales