Raco Verbatim, Owner'S Manual

Page: 149 / 246

MODBUS Interface
Verbatim Owner's Manual F-23
F.17.2 Diagnostic & Communications Error Codes
The diagnostic and communications error codes are registered whenever the
scan for a particular RC fails. When such an event occurs, the code is pushed
onto the diagnostic history stack (see code 49406) and copied into the RC status
word (see code 4941zz). These may be interrogated at any time.
If the problem occurs during selftesting or configuration, the code is reported
immediately. During normal scanning, the problem must continue for the
COMALARM trip delay period before a communications alarm for that RC is
triggered. The report for that alarm will then mention the code. The network
status code is then updated appropriately. See table on next page.
The table below lists the values and interpretations for the most common error
situations. Note that some codes are derived directly from standard error codes
supported by specific protocols. The documentation for those products is then
necessary for interpretation.
0 no error condition detected
352 specified net is invalid
354 protocol doesn't support the net address format
356 request timed out with no feedback
357 node address is invalid for selected protocol
359 node/driver incompatible with address mode
360 miscellaneous error parsing address string
361 some field was duplicated in address string
362 file type specifier in address string not supported
363 couldn't parse file number field in address string
364 couldn't map the I/O slot specified in address string
365 couldn't parse element field in address string
366 couldn't parse subelement field in address string
367 couldn't parse bit field in address string
368 too many routing nodes specified in address string
369 some routing node has illegal syntax
370 transaction aborted at user request
390 source channel data not available for RC link
410 no traffic received from the net
430 timeout with no recognizable response
431 timeout with no response at all
501 transaction took too long to transmit
601- 608 AEG/MODICON exception codes.
That code can be determined by subtracting 600 from this code.
Refer to F.5, "General Modbus Reauirements," for details.
Continued on next page . . .