C-more micro EA1-S6ML Hardware User Manual page 163

GE SNPX Protocol– PLC Error Code Tables (cont' d )
Panel Error Code
P499 Hex Value
0x1A0C Datagram area size is too small to include data for all specified point formats.
0x1B0C Invalid number of Control Program Names. Must be 1-8.
SNP-X Request exceeds maximum data size (1000 bytes).
0x1C0C
Must use a smaller data length. Use multiple COMMREQs if necessary.
Invalid SNP-X communication session type.
0x1D0C
Must be 0 for a single slave device, or 1 for multiple slave devices.
Illegal destination SNP ID specified for SNP-X slave. Must be 0-7 ASCII characters, plus a terminating null
0x1E0C character (00h). The Null SNP ID (eight bytes of 00h) may be used to specify any single device. The
Broadcast SNP ID (eight bytes of FFh) may be use to specify all slave devices on the serial link.
Destination SNP ID does not match SNP-X session type.
0x1F0C The Broadcast SNP ID is not permitted in a single-slave SNP-X session.
The Null SNP ID is not permitted in a multiple-slave SNP-X session.
Inactivity timeout (T3'). The SNP slave has not received any new SNP messages within the configured T3'
0x200C
time interval.
Invalid Message Type field in a received X-Request message.
0x200F
The message type of an X-Request message must be 58h = 'X'.
A Parity error has occurred on an Attach, Attach Response, or Update Real–time Datagram message.
0x210C
Communications have not been established.
Invalid Next Message Type or Next Message Length field in a received X Request message. If this request
does not use a buffer (0-2 bytes of data), the Next Message Type must be zero. If this request will be
0x210F followed with a buffer message (more than 2 byte.)), the Next Message Type must be 54h = 'T', and the
Next Message Length must specify the length of the X-Buffer message. Valid X-Buffer message lengths are
9-1008 bytes (data length plus 8 bytes).
A BCC (Block Check Code) error has occurred on an Attach, Attach Response, or Update Realtime
0x220C
Datagram message. Communications have not been established.
Invalid Message Type field in a received X-Buffer message.
0x220F
The message type of an X-Buffer message must be 54h = 'T'.
A Framing or Overrun serial error has occurred on an Attach, Attach Response, or Update Realtime
0x230C
Datagram message. Communications have not been established.
Invalid Next Message Type field in a received X-Buffer message. Since an X-Buffer message is never
0x230F
followed by another message, the Next Message Type must always be zero.
An invalid SNP message type was received when an Attach, Attach Response, or Update Realtime
0x240C
Datagram message was required. Communications have not been established.
An invalid next message length value was specified in an Attach, Attach Response, or Update Realtime
0x250C
Datagram message. Communications have not been established.
An unexpected SNP message type was received when an Attach, Attach Response, or Update Realtime
0x260C
Datagram was required. Communications have not been established.
Another Break was received while SNP slave was waiting for an Attach or Update Realtime Datagram
0x270C
message.
An SNP message has been sent and retried the maximum number of times.
0x280C A maximum of two retries are permitted.
A retry is caused by a NAK from from the remote SNP device.
A received SNP message has been NAKed the maximum number of two times.
0x290C
The NAKed message may be retransmitted a maximum of two times.
(PLC generated error codes for the GE 90-30, 90-70 and VersaMax SNPX protocol
continued on the next page.)
®
PLC Errors for GE SNPX Protocol (Minor-Major) (cont'd)
EA1-MG6-USER-M Hardware User Manual, 1st Ed. Rev C, 09/10
Appendix A: Panel & PLC Error Code Tables
Description
A
A–15