C-MORE EA1-TCL-M Hardware User Manual - A–15
GE SNPX Protocol – PLC Error Code Tables (cont’d)
PLC generated error codes for the GE 90-30, 90-70 and VersaMax SNPX protocol continue
on the next page.
®
PLC Errors for GE SNPX Protocol (Minor-Major) (cont’d)
Panel Error Code
P499 Hex Value
Description
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.
0x1C0C
SNP-X Request exceeds maximum data size (1000 bytes).
Must use a smaller data length. Use multiple COMMREQs if necessary.
0x1D0C
Invalid SNP-X communication session type.
Must be 0 for a single slave device, or 1 for multiple slave devices.
0x1E0C
Illegal destination SNP ID specified for SNP-X slave. Must be 0-7 ASCII characters, plus a terminating null
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.
0x1F0C
Destination SNP ID does not match SNP-X session type.
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.
0x200C
Inactivity timeout (T3’). The SNP slave has not received any new SNP messages within the configured T3’
time interval.
0x200F
Invalid Message Type field in a received X-Request message.
The message type of an X-Request message must be 58h = ’X’.
0x210C
A Parity error has occurred on an Attach, Attach Response, or Update Real–time Datagram message.
Communications have not been established.
0x210F
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
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).
0x220C
A BCC (Block Check Code) error has occurred on an Attach, Attach Response, or Update Realtime
Datagram message. Communications have not been established.
0x220F
Invalid Message Type field in a received X-Buffer message.
The message type of an X-Buffer message must be 54h = ’T’.
0x230C
A Framing or Overrun serial error has occurred on an Attach, Attach Response, or Update Realtime
Datagram message. Communications have not been established.
0x230F
Invalid Next Message Type field in a received X-Buffer message. Since an X-Buffer message is never
followed by another message, the Next Message Type must always be zero.
0x240C
An invalid SNP message type was received when an Attach, Attach Response, or Update Realtime
Datagram message was required. Communications have not been established.
0x250C
An invalid next message length value was specified in an Attach, Attach Response, or Update Realtime
Datagram message. Communications have not been established.
0x260C
An unexpected SNP message type was received when an Attach, Attach Response, or Update Realtime
Datagram was required. Communications have not been established.
0x270C
Another Break was received while SNP slave was waiting for an Attach or Update Realtime Datagram
message.
0x280C
An SNP message has been sent and retried the maximum number of times.
A maximum of two retries are permitted.
A retry is caused by a NAK from from the remote SNP device.
0x290C
A received SNP message has been NAKed the maximum number of two times.
The NAKed message may be retransmitted a maximum of two times.
EA1-TCL-M Hardware User Manual, 1st Ed., 12/09
A
Appendix A: Panel & PLC Error Code Tables