PLC Error Codes

PANEL & PLC APPENDIX
ERROR CODE TABLES

A
In This Appendix...
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A–2
C-more Touch Panel Error Code Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A–3
DirectLOGIC – Panel Error Code PLC-499 Explanation . . . . . . . . . . . . . . . . . . . . . .A–5
DirectLOGIC K-Sequence Protocol – PLC Error Code Table . . . . . . . . . . . . . . . . . .A–5
DirectLOGIC DirectNET Protocol – PLC Error Codes . . . . . . . . . . . . . . . . . . . . . . . .A–5
Modbus Protocols Error Code P499 Explanation . . . . . . . . . . . . . . . . . . . . . . . . . .A–6
AutomationDirect CLICK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A–6
AutomationDirect DirectLOGIC - Modbus (Koyo) . . . . . . . . . . . . . . . . . . . . . . . . . .A–6
Modicon Modbus RTU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A–6
Entivity Modbus RTU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A–6
DirectLOGIC ECOM Protocol – PLC Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . .A–6
Productivity3000 Error Code P499 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A–7
Allen-Bradley – Panel Error Code PLC-499 Explanation . . . . . . . . . . . . . . . . . . . . .A–8
Allen-Bradley DF1 & DH485 Protocols – PLC Error Code Tables . . . . . . . . . . . . . .A–9
Allen-Bradley EtherNet/IP Protocol –Panel Error Code PLC-496, 497 and 498
Explanation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A–11
Allen-Bradley – EtherNet/IP Protocol – PLC Error Code TablesControlLogix,
CompactLogix, & FlexLogix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A–12
Allen-Bradley – EtherNet/IP Protocol – PLC Error Code TablesMicroLogix 1100, 1400
& SLC 5/05, both via native Ethernet port;MicroLogix 1000, 1100, 1200, 1400, 1500,
SLC 5/03/04/05, all via ENI Adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A–16
Generic EtherNet IP Protocol – PLC Error Codes . . . . . . . . . . . . . . . . . . . . . . . . .A–21
GE 90-30 – Panel Error Code PLC-499 Explanation . . . . . . . . . . . . . . . . . . . . . . . .A–22
GE 90-30 SNPX Protocol – PLC Error Code Tables . . . . . . . . . . . . . . . . . . . . . . . .A–23
PANEL & PLC APPENDIX
ERROR CODE TABLES
A
Mitsubishi FX Protocol – PLC Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A–32
Omron – Panel Error Code PLC-499 Explanation . . . . . . . . . . . . . . . . . . . . . . . . .A–32
Omron Host Link Protocol – PLC Error Code Table . . . . . . . . . . . . . . . . . . . . . . . .A–33
Omron FINS Protocol – PLC Error Code Table . . . . . . . . . . . . . . . . . . . . . . . . . . . .A–34
Omron – Panel Error Code P495 Explanation . . . . . . . . . . . . . . . . . . . . . . . . . . . .A–37
Omron CS/CJ FINS Ethernet Protocol – PLC Error Code Table . . . . . . . . . . . . . . .A–38
Siemens – Panel Error Code P499 Explanation . . . . . . . . . . . . . . . . . . . . . . . . . . .A–39
Siemens PPI Protocol – PLC Error Code Table . . . . . . . . . . . . . . . . . . . . . . . . . . . .A–40
Siemens ISO over TCP Protocol – PLC Error Code Table . . . . . . . . . . . . . . . . . . .A–41
This page intentionally left blank
Appendix A: Panel & PLC Error Code Tables
Introduction
A The C-more family of touch panels is capable of communicating with a wide variety of
Programmable Logic Controllers. C-more is capable of communicating over RS232, RS422 and
2 RS485 serial networks as well as Ethernet networks. It communicates with all
AutomationDirect PLCs utilizing various protocols. C-more also communicates with other
brands of PLCs by their different protocols. For a complete list of PLCs and protocols, see the
3 table on page 16 of Chapter 1: Getting Started.
As with any network communications, errors will occur. To make it more simple for the user to
4 identify the cause of the possible error, we have provided a error code table for all of the possible
errors that C-more can detect.
5 If a C-more communications error does occur, the error message will appear across the top of
the screen. The C-more touch panel also monitors any errors that are generated by the various
PLCs that are connected to it. If any of the PLC generated errors are detected, they are displayed
6 across the top of the panel’s display embedded as a hexadecimal value in error code P499’s
message. An explanation of how the specific PLC error is identified in the panel error code P499
7 is shown proceeding the specific manufacturer’s PLC error tables. How the hexadecimal error
code value is interrupted is slightly different between manufacturers, so it is important to check
the explanation at the beginning of each manufacturer’s tables.
8
Note: These PLC error codes are provided by the manufacturer of the related PLC and are subject to change
9 by the PLC manufacturer. Please refer to the manufacturers documentation for a more complete and up-to-
date list of error codes.
10 All errors are also logged into the panel’s Error log under the
Information tab in the panel’s System Setup Screens and are
identified by the error code number. See Chapter 5: System
11 Setup Screens for additional details.
STX is not found
If you have difficulty determining the cause of the error,

12 please refer to Chapter 8: Troubleshooting for some
troubleshooting tips or contact our technical support group
13 at 770-844-4200 or the 3rd party PLC manufacturer.
Stride™
14 Ethernet Switch
10/100 Base-T
(such as SE-SW5U)
C-more Error Message
A
H0-ECOM/H0-ECOM100
C-more
B Ethernet Module
1
Ethernet
Touch Panel Port
C
(Bottom View)
D DL06 PLC
Ethernet CAT5
Cable - Straight-thru
A–2 ® EA-USER-M Hardware User Manual, 2nd Ed. Rev. G, 08/14

C-more Touch Panel Error Code Table

The following table includes all of the error codes and error messages that the panel will display A
if the listed cause is detected. All of these errors involve problems that could result with the
panel communicating with the connected PLC. Be aware that not all of the panel errors are used
with each type of PLC that can be connected to the panel.
2
C-more Touch Panel Error Code Table
Error Code Error Message Cause
3
PLC Communication Timeout (for single A timeout occurred after sending a request to the PLC %Device%.
PLC-001 PLC)
%Device% PLC Communication Timeout
%Device% indicates the device name, such as DEV001.
Example error message for multiple PLCs: DEV001 PLC Communication
4
(for multiple PLCs, such as RS-422/485) Timeout.
PLC-002 NAK received from PLC A negative acknowledgement (NAK) control code has been generated
during a read/write request.
5
PLC-003 EOT received from PLC An End of Transmission (EOT) control code is sent by the PLC in response
PLC-004 STX is not found

to a Read/Write/SetBit request..
A Start of Text (STX) control code was not found in the data packet
6
received from the PLC.
PLC-005 ETX or ETB is not found Neither an End of Text (ETX) nor an End of Transmission Block (ETB)
control code was found in the data packet received from the PLC. 7
There was an incorrect Longitudinal Redundancy Check (LRC) control
PLC-006 LRC does not match code in the communications packet received from the PLC. This is an
indication that the data in the packet is corrupted. 8
There was an incorrect Cyclic Redundancy Check (CRC) control code in the
PLC-007 CRC does not match communications packet received from the PLC. This is an indication that
the data in the packet is corrupted. 9
PLC-008 Address does not match The address value returned in the data packet from the PLC is incorrect.
PLC-009 Different function code received from PLC The function code returned in the data packet from the PLC is incorrect. 10
PLC-010 Data size does not match There are an incorrect number of bytes found in the data packet returned
PLC-011 Invalid value in function code

from the PLC.
There is an invalid value in the function code.
11
PLC-012 Invalid command sent to PLC There was an invalid command sent to the PLC that wasn’t recognized by
the PLC.
If the data packet does not include a negative acknowledgement (NAK -
12
PLC-013 ENQ received from PLC 0x15 value) in the defined packet field, then an enquiry (ENQ) control code
PLC-014 Transaction ID does not match

error will be displayed.
This error will be displayed if after checking the Transaction ID Bytes in
13
the data packet, there is no match to what was requested.
PLC-015
PLC-016
%Device% No device found
Data byte communication error
A PLC device designated as %Device% could not be found.
0 byte of data is recieved
14
PLC-017
PLC-018
Out of address range
Panel communication timeout
The touch panel requested a file number larger than 255.
The server panel did not respond when using the Panel Pass Through.
A
PLC-019 Found in parity error by hardware An error detected in the PLC memory.
PLC-020 Can’t open serial port Cannot open the Serial Port. If this error shows on the panel, it indicates B
a hardware problem.
PLC-021
PLC-022
PLC number does not match
Can’t reset DCB
The PLC number does not match the PLC number configured.
Unable to reset the data communication bit.
C
PLC-023 Cable not connected properly Communication cable incorrectly installed.
C-more Touch Panel Error Code Table continued on the next page.
D
® EA-USER-M Hardware User Manual, 2nd Ed. Rev. G, 08/14 A–3

C-more Touch Panel Error Code Table (cont’d)

A C-more Touch Panel Error Code Table (cont’d)
Error Code Error Message Cause
2 PLC-024 Cannot detect other devices on network The panel is not communicating with other devices on the network.
PLC-025 Panel not in polling list
3 PLC-026 PLC connection timeout A timeout occured after sending a request to the PLC.
PLC-027 Memory type incorrect
4 PLC-028 PLC failed to respond The PLC failed to respond after sending a request to the PLC.
An error code specific to Omron Ethernet with a Value of XXXX has
PLC-495 Omron Ethernet Error been returned from the PLC. See the explanation for error code
5 PLC-495 proceeding the Omron CS/CJ FINS Ethernet error code tables.
Allen-Bradley EtherNET/IP specific. Encapsulation Error.
PLC-496 Error code 0xaaaaaaaa returned from PLC See the explanation for error code PLC-496 proceeding the Allen-
6 Bradley EtherNet/IP error code tables.
Allen-Bradley EtherNET/IP specific. CIP Error.
Allen-Bradley EtherNET/IP specific. Service Packet Error.
An error code with a value of XXXX has been returned from the PLC.
PLC-499 Error code XXXX returned from PLC See the explanation for error code PLC-499 below for Direct LOGIC and
proceeding each set of PLC error code tables that use this error code.
9 Data cannot write to the Serial port.
PLC-500 Cannot write to Serial Port Data was sent to the PLC via the Serial Port.
If this error shows on the Panel, it indicates a Hardware Problem.
10 PLC-700 Not enough buffer memory There was an error while allocating memory for the read buffer.
When this error is displayed, a memory leak may have occurred.
Request to inaccessible memory from the HMI layer to the PLC protocol
11 PLC-701 Access to inaccessible PLC memory layer. This error is an indication that there is a problem in the HMI layer.
A Read/Write/SetBit request has been sent to an invalid memory area.
PLC-702 Cannot access by different function code This error is an indication that there is a problem in the HMI layer.
12 PLC-703 Write request to PLC Read Only Memory
A PLC Write request was made to the PLC’s Read-Only memory area.This
error is an indication that there is a problem in the HMI layer or the PLC
protocol layer.
13 PLC-704 Bad device-access No device (PLC) exists in the server panel or the device name does not
match between the server and client when using the Panel Pass Through.
PLC-705 Protocol does not match The protocol for the device does Not match between the server and client
14 when using the panel pass through.
A
B
C
D

DirectLOGIC – Panel Error Code PLC-499 Explanation

The PLC-499 error code is used to show any errors that are generated by the connected PLC. A
The PLC-499 error message includes a four digit hexadecimal value embedded in the message.
This value can be looked up in the specific PLC’s error tables to determine the cause of the error.
The possible PLC generated error codes for the DirectLOGIC communication protocol are
2
represented by a hexadecimal value as shown in the following message example.
Direct LOGIC Error Code PLC-499 Message Example: 3
4
Error code 0003 returned from
PLC
5
6
Panel error code PLC-499
showing a hexadecimal value
of 0003 indicates an “Illegal
7
data value dependent upon
the request.” PLC error. 8
9
DirectLOGIC K-Sequence Protocol – PLC Error Code Table 10
The following table lists the errors that can be generated by the DirectLOGIC PLC when using
the K-Sequence protocol. 11
PLC Error Codes for Direct LOGIC – K-Sequence
Panel Error Code
12
Description
PLC-499 Hex Value
01F8
020D
Error setting value.
Error in key mode.
13
021C Password protected.
14
Note: The following errors can be generated from the designated PLC, are monitored by the C-more touch
panel, and displayed on the touch panel’s screen as a hexadecimal value in panel error code PLC-499 A
message, if active. Please refer to the PLC manufacturer’s documentation for additional information.
B
DirectLOGIC DirectNET Protocol – PLC Error Codes
Only errors as listed in the Touch Panel Error Code Table shown on page A-3 can occur when C
using the DirectLOGIC DirectNET protocol, there are no PLC generated errors.
DirectLOGIC error code tables continued on the next page.

D

Modbus Protocols Error Code P499 Explanation

A The following table lists the errors that can be generated by the Modbus protocols:
AutomationDirect CLICK
2 AutomationDirect DirectLOGIC - Modbus (Koyo)
3 Modicon Modbus RTU
Entivity Modbus RTU
4
5 panel, and displayed on the touch panel’s screen as a hexadecimal value in panel error code PLC-499
6
PLC Error Codes Modbus Protocols
7 Panel
Code
Error
Name Meaning
P499 Hex Value
8 The function code received in the query is not an allowable action for the server (or slave). This
may be because the function code is only applicable to newer devices and was not
0x0001 ILLEGAL implemented in the unit selected. It could also indicate that the server (or slave) is in the wrong
FUNCTION
9 state to process a request of this type, for example because it is unconfigured and is being
asked to return registered values.
The data address received in the query is not an allowable address for the server (or slave).
10 More specifically, the combination of reference number and transfer length is invalid. For a
controller with 100 registers, the PDU addresses the first register as 0, and the last one as 99.
0x0002 ILLEGAL DATA If a request is submitted with a starting register address of 96 and a quantity of registers of 4,
ADDRESS then the request will successfully operate (address-wise at least) on registers 96, 97, 98, 99. If
11 a request is submitted with a starting register of 96 and a quantity of registers of 5, then the
request will fail with Exception code 0x02 "Illegal Data Address" since it attempts to operate on
registers 96, 97, 98, 99 and 100, and there is no register with address 100.
12 A value contained in the query data field is not an allowable value for server (or slave). This
ILLEGAL DATA indicates a fault in the structure of the remainder of a complex request, such as that the implied
0x0003 VALUE length is incorrect. It specifically does NOT mean that a data item submitted for storage in a
13 register has a value outside the expectation of the application program, since the Modbus
protocol is unaware of the significance of any particular value of any particular register.
0x0004 SLAVE DEVICE An unrecoverable error occurred while the server (or slave) was attempting to perform the
FAILURE requested action.
14
DirectLOGIC ECOM Protocol – PLC Error Codes
A Only errors as listed in the Touch Panel Error Code Table shown on page A-3 can occur when
using the DirectLOGIC ECOM protocol, there are no PLC generated errors.
B
C
D

Productivity3000 Error Code P499

A
panel, and displayed on the touch panel’s screen as a hexadecimal value in panel error code PLC-499
message, if active. Please refer to the PLC manufacturer’s documentation for additional information. 2
Panel Error
PLC Error Codes for Productivity3000 3
Code Meaning
P499 Hex Value 4
The function code received in the query is not an allowable action for the server (or slave). This may be because
0x0001 the function code is only applicable to newer devices and was not implemented in the unit selected. It could also
indicate that the server (or slave) is in the wrong state to process a request of this type, for example because it is 5
unconfigured and is being asked to return registered values.
0x0002
Address out of range. Check to make sure that the C-more tag and System ID match the Productivity3000
Programming Software Tag Name and System ID. The project file in the Productivity3000 system and the
6
imported CSV into C-more must be in sync with each other.
A value contained in the query data field is not an allowable value for the server (or slave). This indicates a fault 7
in the structure of the remainder of a complex request, such as that the implied length is incorrect. It specifically
0x0003 does NOT mean that a data item submitted for storage in a register has a value outside the expectation of the
application program, since the Modbus protocol is unaware of the significance of any particular value of any
particular register.
8
0x0004 An unrecoverable error occurred while the server (or slave) was attempting to perform the requested action.
9
10
11
12
13
14
A
B
C
D

Allen-Bradley – Panel Error Code PLC-499 Explanation

A The PLC-499 error code is used to show any errors that are generated by the connected PLC.
2 This value can be looked up in the specific PLC’s error tables to determine the cause of the error.
The possible PLC generated error codes for the Allen-Bradley DF1 and DH485
communication protocols are represented by a hexadecimal value as shown in the following
3 diagram. Please note that the error code is broken down into three sections. It is possible for
more than one type of PLC error to be displayed in this value.
4 Allen-Bradley Error Code PLC-499 Message Example:
5 AB DF1 and DH485 Protocol Error Code PLC-499 Breakdown

Remote Local EXT STS
AB DF1 and DH485 Protocol – Multiple Error Code Examples
Example 1 Example 2 Example 3
4-7 bits 0-3 bits byte
Remote
6 16-bit
Word
1 1 1 1 0 0 0 0 0 0 0 1 0 1 1 1
4-7 bits
Local
F x
x 0 x
+
x x
x
1 x
x 1 x
+
x x
x
F x
x 1 x
+
x x
x
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 0-3 bits
+ + +
7 EXT STS
byte x x 0 9
=
x x 0 0
=
x x 0 9
=
Example of an EXT STS error Error PLC-499
PLC-499 Error Code Message for a “Type mismatch.” Value Displayed F 0 0 9 1 1 0 0 F 1 0 9
F 0 1 7
8 Displayed Hexadecimal Value hex
9
10
PLC
11
12
13 Panel error code PLC-499
of 1700 indicates “Illegal
14 command or format.”and
“Station is offline.” PLC errors.
A
B
C
D

Allen-Bradley DF1 & DH485 Protocols – PLC Error Code Tables

The following PLC error code tables cover possible errors that are detected by the panel from A
Allen-Bradley PLCs using the DF1 and DH485 protocols. DF1 includes full and half duplex
communications for the MicroLogix 1000, 1100. 1200, 1400, 1500, SLC 5/03, /04, /05,
ControlLogix, CompactLogix and FlexLogix, and full duplex communications for the PLC5.
2
DH485 includes all MicroLogix and SLC500 PLC’s and any communication connection using
an Allen-Bradley AIC device using the DH485 protocol. 3
panel, and displayed on the touch panel’s screen as a hexadecimal value in panel error code PLC-499 4
PLC Errors for Allen-Bradley DF1 and DH485 Protocols, Local STS Errors (0-3 bits) 5
Panel Error Code
PLC-499 Hex Value
0x0 Success; no error.
Description
6
0x1 DST node is out of buffer space.
0x2 Cannot guarantee delivery; link layer. 7
(The remote node specified does not ACK command.)
0x3
0x4
Duplicate token holder detected.
Local port is disconnected.
8
0x5 Application layer timed out waiting for response.
0x6 Duplicate node detected. 9
0x7 Station is offline.
0x8 Hardware fault.
10
PLC Errors for Allen-Bradley DF1 and DH485 Protocols, Remote STS Errors (4-7 bits)
Panel Error Code
PLC-499 Hex Value
Description 11
0x0 Success; no error.
0x10 Illegal command or format. 12
0x20 Host has a problem and will not communicate.
0x30
0x40
Remote node host is missing, disconnected, or shut down.
Host could not complete function due to hardware fault.
13
0x50 Addressing problem or memory protect rungs.
0x60 Function not allowed due to command protection selection. 14
0x70 Processor is in Program Mode.
0x80
0x90
Compatibility mode file missing or communication zone problem.
Remote node cannot buffer command.
A
0xA0 Wait ACK (1775 KA buffer full).
0xB0 Remote node problem due to download. B
0xC0 Wait ACK (1775 KA buffer full).
0xD0
0xE0
not used
not used
C
0xF0 Error code in the EXT STS byte. See the error code table on the next page.
(PLC generated error codes for the Allen-Bradley DF1 protocol continued on the next page.)
D

Allen-Bradley DF1 & DH485 Protocols – PLC Error Code Tables

A PLC Errors for Allen-Bradley DF1 and DH485 Protocols, EXT STS Command Code for F0 Command
Panel Error Code Description
2 PLC-499 Hex Value
0x0 not used
0x1 A field has an illegal value.
3 0x2 Fewer levels specified in address than minimum for any address.
0x3 More levels specified in address than system supports.
4 0x4
0x5
Symbol not found.
Symbol is of improper format.
0x6 Address does not point to something usable.
5 0x7 File is wrong size.
0x8 Cannot complete request; situation has changed since start of the command.
6 0x9
0xA
Data or file size is too large.
Transaction size plus word address is too large.
0xB Access denied; improper privilege.
7 0xC Condition cannot be generated; resource is not available.
0xD Condition already exists; resource is readily available.
8 0xE
0xF
Command cannot be executed.
Histogram overflow.
0x10 No access.
9 0x11 Illegal data type.
0x12 Invalid parameter or invalid data.
10 0x13 Address reference exists to deleted area.
Command execution failure for unknown reason;
0x14 possible PLC 3 histogram overflow.
11 0x15
0x16
Data conversion error.
Scanner not able to communicate with 1771 rack adapter.
0x17 Type mismatch.
12 0x18 1771 module response was not valid.
0x19 Duplicated label.
13 0x22
0x23
Remote rack fault.
Timeout.
0x24 Unknown error.
14 0x1A File is open; another node owns it.
0x1B Another node is the program owner.
A 0x1C
0x1D
Disk File is write protectid or otherwise unavailable
Disk File is being used by another application. Update not performed (offline only).
0x1E Data table element protection violation.
B 0x1F Temporary internal problem.
C
D

Allen-Bradley EtherNet/IP Protocol –

Panel Error Code PLC-496, 497 and 498 Explanation A
The PLC-496, PLC-497, and PLC-498 error codes are used to show any errors that are
generated by the connected PLC. These error messages include an eight digit hexadecimal value
2
displayed embedded in the message. This value can be looked up in the specific PLC’s error
tables to determine the cause of the error. The possible PLC generated error codes for the Allen- 3
Bradley EtherNet/IP communication protocol is represented by a hexadecimal value as shown
in the following message example. 4
Allen-Bradley Error Code PLC-496, 497, 498 Message Example:
5
Error code 00000065 returned
from PLC 6
7
8
of 00000065 indicates an “The 9
target received a message of
invalid length.” PLC error.
10
11
12
13
14
A
B
C
D

Allen-Bradley – EtherNet/IP Protocol– PLC Error Code Tables

A ControlLogix, CompactLogix, & FlexLogix
2 The following PLC error code tables cover possible errors that are detected by the panel from
Allen-Bradley PLCs using the EtherNet/IP protocol. This includes all ControlLogix,
CompactLogix and FlexLogix PLCs.
3 Note: The following errors can be generated from the designated PLC, are monitored by the C-more touch
4 message, if active. Please refer to the PLC manufacturer’s documentation for additional information.
5 PLC Errors for Allen-Bradley EtherNet/IP Protocol –Encapsulation Errors

(Error code 0xaaaaaaaa returned from the PLC.)
Panel Error Code
6 PLC-496 Hex Value Description
0x00000001 The sender issued an invalid or unsupported encapsulation command.
7 0x00000002 Insufficient memory resources in the receiver to handle the command. You can get this error if the 1761-
NET-ENI cannot connect to the PLC serially.
0x00000003 Poorly formed or incorrect data in the data portion of the encapsulation message.
8 0x00000004 -
0x00000063 Reserved for legacy (Rockwell Automation).
0x00000064 An orginator used an invalid session handle when sending an encapsulation message to the target.
9 0x00000065
0x00000066 -
The target received a message of invalid length.

10 0x00000069
0x0000006a -
Unsupported encapsulation protocol revision.
0x0000ffff Reserved for future expansion.

11
PLC Errors for Allen-Bradley EtherNet/IP Protocol – CIP Errors
12 Panel Error Code
Description
PLC-497 Hex Value
13 0x010100 Connection Manager: Connection in Use or Duplicate Forward Open.
0x010103 Connection Manager: Transport Class and Trigger combination not supported.
14 0x010106
0x010107
Connection Manager: Ownership Conflict.
Connection Manager: Connection not found at target application.
0x010108 Connection Manager: Invalid connection type (problem with type or priority).
A 0x010109 Connection Manager: Invalid connection size.
0x010110 Connection Manager: Device not configured.
B 0x010111
0x010113
Connection Manager: RPI not supported. Could also be problem with inactivity timeout.
Connection Manager: Connection Manager cannot support any more connections.
0x010114 Connection Manager: Either the vendor ID or the Product Code in the key segment did not match the
C 0x010115
device.
Connection Manager: Product Type in the key segment did not match the device.
0x010116 Connection Manager: Major or minor revision information in the key segment did not match the device.
D (PLC generated error codes for the Allen-Bradley EtherNet/IP protocol for ControlLogix,
CompactLogix, and FlexLogix continued on the next page.)

Allen-Bradley – EtherNet/IP Protocol – PLC Error Code Tables

ControlLogix, CompactLogix, & FlexLogix (cont’d) A
2
Panel Error Code
PLC-497 Hex Value Description 3
0x010117 Connection Manager: Invalid connection point.
0x010118
0x010119
Connection Manager: Invalid configuration format.
Connection Manager: Connection request fails since there is no controlling connection currently open.
4
0x01011a Connection Manager: Target application cannot support any more connections.
0x01011b Connection Manager: RPI is smaller than the Production Inhibit Time. 5
0x010203 Connection Manager: Connection cannot be closed since the connection has timed out.
0x010204
0x010205
Connection Manager: Unconnected Send timed out waiting for a response.
Connection Manager: Parameter error in Unconnected send service.
6
0x010206 Connection Manager: Message too large for Unconnected message service.
0x010207 Connection Manager: Unconnected acknowledge without reply. 7
0x010301 Connection Manager: No buffer memory available.
0x010302
0x010303
Connection Manager: Network Bandwidth not available for data.
Connection Manager: No Tag filters available.
8
0x010304 Connection Manager: Not configured to send real-time data.
0x010311 Connection Manager: Port specified in Port segment not available. 9
0x010312 Connection Manager: Link address specified in port segment not available.
0x010315
0x010316
Connection Manager: invalid segment type or segment value in path.
Connection Manager: Path and Connection not equal in close.
10
0x010317 Connection Manager: Ether Segment not present or Encoded Value in Network Segment is invalid.
0x010318 Connection Manager: Link address to self invalid. 11
0x010319 Connection Manager: Resources on Secondary unavailable.
0x01031a
0x01031b
Connection Manager: Connection already established.
Connection Manager: Direct connection already established.
12
0x01031c Connection Manager: Miscellaneous.
0x01031d Connection Manager: Redundant connection mismatch. 13
0x01031e Connection Manager: No more consumer resources available in the producing module.
0x01031f
0x010320 -
Connection Manager: No connection resources exist for target path. 14
0x0107ff Connection Manager: Vendor specific.
0x020000
0x030000
Resource unavailable: Connection Manager resources are unavailable to handle service request.
Invalid parameter value.
A
Path segment error: The path segment identifier or the segment syntax was not understood by the
0x040000 processing node.
Path destination unknown: The path is referencing an object class, instance or structure element that is not
B
0x050000 known or is not contained in the processing node.
0x060000 Partial transfer: Only part of the expected data was transferred. C
0x070000 Connection lost: The messaging connection was lost.
(PLC generated error codes for the Allen-Bradley EtherNet/IP protocol for ControlLogix, D
CompactLogix, and FlexLogix continued on the next page.)


A ControlLogix, CompactLogix, & FlexLogix (cont’d)
2 PLC Errors for Allen-Bradley EtherNet/IP Protocol – CIP Errors
Panel Error Code
3 PLC-497 Hex Value Description
0x080000 Service not supported: The requested service was not implemented or was not defined for this Object
4 0x090000
Class/Instance.
Invalid attribute value: Invalid attribute data detected.
0x0a0000 Attribute list error: An attribute in the Get_Attribute_List or Set_Attribute_List response has a non-zero
5 0x0b0000
status.
Already in requested mode/state: The object is already in the mode/state being requested by the service.
0x0c0000 Object state conflict: The object cannot perform the requested service in its current mode/state.
6 0x0d0000
0x0e0000
Object already exists: The requested instance of object to be created already exists.
Attribute not settable: A request to modify non-modifiable attribute was received.
7 0x0f0000
0x100000
Privilege violation: A permission/privilege check failed.
Device state conflict: The device's current mode/state prohibits the execution of the requested service.
0x110000 Reply data too large: The data to be transmitted in the response buffer is larger than the allocated response
8 0x120000
buffer.
Fragmentation of a primitive value: The service specified an operation that is going to fragment a primitive
data value. For example, trying to send a 2 byte value to a REAL data type (4 byte).
9 0x130000
0x140000
Not enough data: The service did not supply enough data to perform the specified operation.
Attribute not supported: The attribute specified in the request is not supported.
0x150000 Too much data: The service supplied more data than was expected.
10 0x160000 Object does not exist: The object specified does not exist in the device.
0x170000 Service fragmentation sequence not in progress: The fragmentation sequence for this service is not
currently active for this data.
11 0x180000 No stored attribute data: The attribute data of this object was no saved prior to the requested service.
0x190000 Store operation failure: The attribute data of this object was not saved due to a failure during the attempt.
12 0x1a0000 Routing failure, request packet too large: The service request packet was too large for transmission on a
network in the path to the destination.
0x1b0000 Routing failure, response packet too large: The service reponse packet was too large for transmission on a
13 0x1c0000
network in the path from the destination.
Missing attribute list entry data: The service did not supply an attribute in a list of attributes that was
needed by the service to perform the requested behavior.
14 0x1d0000 Invalid attribute value list: The service is returning the list of attributes supplied with status information for
those attributes that were invalid.
0x1e0000 Embedded service error: See Service Packet error list (PLC-498 Error codes) below:
A 0x1f0000 Vendor specific error: A vendor specific error has been encountered. This occurs when none of the
specified errors relate to the error in the device.
0x200000 Invalid parameter: A parameter associated with the request was invalid. This code is used when a
B 0x210000
parameter does meet the requirements defined in an Application Object specification.
Write-once value or medium already written: An attempt was made to write to a write-once-medium that
has already been written or to modify a value that cannot be change once established.
C 0x220000 Invalid Reply Received: An invalid reply is received (example: service code sent doesn't match service code
received.).
(PLC generated error codes for the Allen-Bradley EtherNet/IP protocol for ControlLogix,
D CompactLogix and FlexLogix continued on the next page.)


ControlLogix, CompactLogix, & FlexLogix (cont’d) A
2
Panel Error Code
0x230000 Reserved by CIP for future extensions.
Key failure in path: The key segment was included as the first segment in the path does not match the
4
0x250000 destination module. The object specific status shall indicate which part of the key check failed.
0x260000 Path Size Invalid: The size of the path which was sent with the Service Request is either not large enough
to allow the Request to be routed to an object or too much routing data was included.
5
0x270000 Unexpected attribute in list: An attempt was made to set an attribute that is not able to be set at this time.
0x280000 Invalid Member ID: The Member ID specified in the request does not exist in the specified
Class/Instance/Attribute.
6
0x290000 Member not settable: A request to modify a non-modifiable member was received.
0x2a0000
Group 2 only server general failure: This error code may only be reported by DeviceNet group 2 only
servers with 4K or less code space and only in place of Service not supported, Attribute not supported and
7
Attribute not settable.
0x2b0000 -
0xcf0000 Reserved by CIP for future extensions. 8
Reserved for Object Class and service errors: This range of error codes is to be used to indicate Object
0xd00000 -
0xff0000 Class specific errors. Use of this range should only be used when errors in this table don't accurately
reflect the error encountered.
9
PLC Errors for Allen-Bradley EtherNet/IP Protocol – Service Packet Errors
10
11
PLC-498 Hex Value
0x040000 This general status codes that the tag name could not be deciphered. This could mean that the tag name
was entered incorrectly or does not exist in the PLC. 12
0x050000 The particular item referenced (usually instance) could not be found.
0x060000
0x0a0000
The amount of data requested would not fit into the response buffer. Partial data transfer has occurred.
An error has occurred trying to process one of the attributes.
13
0x130000 Not enough command data/parameters were supplied in the command to execute the service requested.
0x1c0000 An insufficient number of attributes were provided compared to the attribute count. 14
0x260000 The tag name length specified did not match what was in the message.
0xff0521
0xff0721
You have tried to access beyond the end of the data object.
The abbreviated type does not match the data type of the data object.
A
0xff0421 The beginning offset was beyond the end of the template.
B
C
D

Allen-Bradley–EtherNet/IPProtocol–PLCErrorCodeTables
A MicroLogix1100,1400&SLC5/05,bothvianativeEthernetport;
2 MicroLogix1000,1100,1200,1400,1500,SLC5/03/04/05,allviaENI
Adapter
3 The following PLC error code tables cover possible errors that are detected by the panel from
Allen-Bradley PLCs using the EtherNet/IP protocol. This includes MicroLogix 1100, 1400 &
4 SLC 5/05, both using their native Ethernet port, and MicroLogix 1000, 1100, 1200, 1400,
1500, SLC 5/03, 5/04 and 5/05 using an Allen-Bradly ENI Adapter.
6 PLC Errors for Allen-Bradley EtherNet/IP Protocol –Encapsulation Errors
7 Panel Error Code Description
PLC-496 Hex Value
8 0x00000001 The sender issued an invalid or unsupported encapsulation command.
Insufficient memory resources in the receiver to handle the command. You can get this error if the 1761-
0x00000002 NET-ENI cannot connect to the PLC serially.
9 0x00000003
0x00000004 -
Poorly formed or incorrect data in the data portion of the encapsulation message.

10 0x00000064
0x00000065
An orginator used an invalid session handle when sending an encapsulation message to the target.
The target received a message of invalid length.
11 0x00000066 -
0x00000069 Unsupported encapsulation protocol revision.
12 0x0000006a -
0x0000ffff Reserved for future expansion.

13 (Error code 0xaabbbb returned from the PLC.)
14 PLC-497 Hex Value
0x010100 Connection Manager: Connection in Use or Duplicate Forward Open.
0x010103 Connection Manager: Transport Class and Trigger combination not supported.
A 0x010106 Connection Manager: Ownership Conflict.
0x010107 Connection Manager: Connection not found at target application.
B 0x010108
0x010109
Connection Manager: Invalid connection type (problem with type or priority).
Connection Manager: Invalid connection size.
0x010110 Connection Manager: Device not configured.
C 0x010111 Connection Manager: RPI not supported. Could also be problem with inactivity timeout.
D (PLC generated error codes for the Allen-Bradley EtherNet/IP protocol for MicroLogix 1100,
1400, SLC 5/05, or ENI Adapter continued on the next page.)

MicroLogix1100,1400&SLC5/05,bothvianativeEthernetport; A
MicroLogix1000,1100,1200, 1400,1500,SLC5/03/04/05,allviaENI 2
Adapter
PLC Errors for Allen-Bradley EtherNet/IP Protocol – CIP Errors 3
(Error code 0xaabbbb returned from the PLC.)
Panel Error Code
0x010113 Connection Manager: Connection Manager cannot support any more connections.
0x010114 Connection Manager: Either the vendor ID or the Product Code in the key segment did not match the
device.
5
0x010115 Connection Manager: Product Type in the key segment did not match the device.
0x010116 Connection Manager: Major or minor revision information in the key segment did not match the device. 6
0x010117 Connection Manager: Invalid connection point.
0x010118
0x010119
Connection Manager: Invalid configuration format.
Connection Manager: Connection request fails since there is no controlling connection currently open.
7
0x01011a Connection Manager: Target application cannot support any more connections.
0x01011b Connection Manager: RPI is smaller than the Production Inhibit Time. 8
0x010203 Connection Manager: Connection cannot be closed since the connection has timed out.
0x010204
0x010205
Connection Manager: Unconnected Send timed out waiting for a response.
Connection Manager: Parameter error in Unconnected send service.
9
0x010206 Connection Manager: Message too large for Unconnected message service.
0x010207 Connection Manager: Unconnected acknowledge without reply. 10
0x010301 Connection Manager: No buffer memory available.
0x010302
0x010303
Connection Manager: Network Bandwidth not available for data.
Connection Manager: No Tag filters available.
11
0x010304 Connection Manager: Not configured to send real-time data.
0x010311 Connection Manager: Port specified in Port segment not available. 12
0x010312 Connection Manager: Link address specified in port segment not available.
0x010315
0x010316
Connection Manager: invalid segment type or segment value in path.
Connection Manager: Path and Connection not equal in close.
13
0x010317 Connection Manager: Ether Segment not present or Encoded Value in Network Segment is invalid.
0x010318 Connection Manager: Link address to self invalid. 14
0x010319 Connection Manager: Resources on Secondary unavailable.
0x01031a
0x01031b
Connection Manager: Connection already established.
Connection Manager: Direct connection already established.
A
0x01031c Connection Manager: Miscellaneous.
0x01031d Connection Manager: Redundant connection mismatch. B
0x01031e Connection Manager: No more consumer resources available in the producing module.
0x01031f
0x010320 -
Connection Manager: No connection resources exist for target path.
Connection Manager: Vendor specific.
C
0x0107ff
(PLC generated error codes for the Allen-Bradley EtherNet/IP protocol for MicroLogix 1100, D

2 MicroLogix1000,1100,1200, 1400,1500,SLC5/03/04/05,allviaENI
Adapter
3 PLC Errors for Allen-Bradley EtherNet/IP Protocol – CIP Errors
4 Panel Error Code
PLC-497 Hex Value Description
0x020000 Resource unavailable: Connection Manager resources are unavailable to handle service request.
5 0x030000 Invalid parameter value.
0x040000 Path segment error: The path segment identifier or the segment syntax was not understood by the
6 0x050000
processing node.
Path destination unknown: The path is referencing an object class, instance or structure element that is not
known or is not contained in the processing node.
7 0x060000
0x070000
Partial transfer: Only part of the expected data was transferred.
Connection lost: The messaging connection was lost.
0x080000 Service not supported: The requested service was not implemented or was not defined for this Object
8 0x090000
Class/Instance.
Invalid attribute value: Invalid attribute data detected.
0x0a0000 Attribute list error: An attribute in the Get_Attribute_List or Set_Attribute_List response has a non-zero
9 0x0b0000
status.
Already in requested mode/state: The object is already in the mode/state being requested by the service.
0x0c0000 Object state conflict: The object cannot perform the requested service in its current mode/state.
10 0x0d0000 Object already exists: The requested instance of object to be created already exists.
0x0e0000 Attribute not settable: A request to modify non-modifiable attribute was received.
11 0x0f0000
0x100000
Privilege violation: A permission/privilege check failed.
Device state conflict: The device's current mode/state prohibits the execution of the requested service.
Reply data too large: The data to be transmitted in the response buffer is larger than the allocated response
12 0x110000 buffer.
Fragmentation of a primitive value: The service specified an operation that is going to fragment a primitive
0x120000 data value. For example, trying to send a 2 byte value to a REAL data type (4 byte).
13 0x130000
0x140000
Not enough data: The service did not supply enough data to perform the specified operation.
Attribute not supported: The attribute specified in the request is not supported.
0x150000 Too much data: The service supplied more data than was expected.
14 0x160000 Object does not exist: The object specified does not exist in the device.
0x170000 Service fragmentation sequence not in progress: The fragmentation sequence for this service is not
A 0x180000
currently active for this data.
No stored attribute data: The attribute data of this object was no saved prior to the requested service.
0x190000 Store operation failure: The attribute data of this object was not saved due to a failure during the attempt.
B 0x1a0000 Routing failure, request packet too large: The service request packet was too large for transmission on a
network in the path to the destination.
0x1b0000 Routing failure, response packet too large: The service reponse packet was too large for transmission on a
C 0x1c0000
network in the path from the destination.
Missing attribute list entry data: The service did not supply an attribute in a list of attributes that was
needed by the service to perform the requested behavior.

MicroLogix1000,1100,1200, 1400,1500,SLC5/03/04/05,allviaENI 2
Adapter
PLC Errors for Allen-Bradley EtherNet/IP Protocol – CIP Errors 3
4
PLC-497 Hex Value
0x1d0000 Invalid attribute value list: The service is returning the list of attributes supplied with status information for
those attributes that were invalid. 5
0x1e0000 Embedded service error: See Service Packet error list (PLC-498 Error codes) below:
0x1f0000 Vendor specific error: A vendor specific error has been encountered. This occurs when none of the
specified errors relate to the error in the device. 6
0x200000 Invalid parameter: A parameter associated with the request was invalid. This code is used when a
parameter does meet the requirements defined in an Application Object specification.
0x210000 Write-once value or medium already written: An attempt was made to write to a write-once-medium that
has already been written or to modify a value that cannot be change once established.
7
Invalid Reply Received: An invalid reply is received (example: service code sent doesn't match service code
0x220000 received.). 8
0x240000
0x250000
Reserved by CIP for future extensions.
Key failure in path: The key segment was included as the first segment in the path does not match the
9
destination module. The object specific status shall indicate which part of the key check failed.
0x260000 Path Size Invalid: The size of the path which was sent with the Service Request is either not large enough
to allow the Request to be routed to an object or too much routing data was included. 10
0x270000 Unexpected attribute in list: An attempt was made to set an attribute that is not able to be set at this time.
0x280000 Invalid Member ID: The Member ID specified in the request does not exist in the specified
Class/Instance/Attribute. 11
0x290000 Member not settable: A request to modify a non-modifiable member was received.
0x2a0000
Group 2 only server general failure: This error code may only be reported by DeviceNet group 2 only
servers with 4K or less code space and only in place of Service not supported, Attribute not supported and
12
Attribute not settable.
0x2b0000 -
0xcf0000 Reserved by CIP for future extensions. 13
0xd00000 - Reserved for Object Class and service errors: This range of error codes is to be used to indicate Object
0xff0000 Class specific errors. Use of this range should only be used when errors in this table don't accurately
reflect the error encountered. 14
(PLC generated error codes for the Allen-Bradley EtherNet/IP protocol for MicroLogix 1100,
SLC 5/05, or ENI Adapter continued on the next page.)
A
B
C
D

2 MicroLogix1000,1100,1200, 1400,1500,SLC5/03/04/05,allviaENI
Adapter
3 PLC Errors for Allen-Bradley EtherNet/IP Protocol – Service Packet Errors
4 Panel Error Code
0x010000 DST Node is out of buffer space.
5 0x020000
0x030000
Cannot guarantee delivery; link layer (The remote node specified does not ACK command).
Duplicate token holder detected.
6 0x040000
0x050000
Local port is disconnected.
Application layer timed out waiting for response.
0x060000 Duplicate node detected.
7 0x070000
0x080000
Station is offline.
Hardware fault.
Illegal command or format. Typical error received from PLC when addressed requested to the PLC does not
8 0x100000 exist. Usually occurs if memory map has not been expanded in PLC to the range requested from panel.
0x200000 Host has a problem and will not communicate.
9 0x300000
0x400000
Remote node host is missing, disconnected, or shut down.
Host could not complete function due to hardware fault.
0x500000 Addressing problem or memory protected rungs.
10 0x600000 Function not allowed due to command protection selection.
0x700000 Processor is in Program Mode.
11 0x800000
0x900000
Compatibility mode file missing or communication zone problem.
Remote node cannot buffer command.
0xA00000 Wait ACK (1775 KA buffer full).
12 0xB00000 Not used.
0xC00000 Not used.
13 0xD00000
0xE00000
Error code in the EXT STS byte. See the error code table below.
Fewer levels specified in address than minimum for any address.
0xF00300 More levels specified in address than system supports.
14 0xF00400 Symbol not found.
0xF00500 Symbol is of improper format.
A 0xF00600
0xF00700
Address does not point to something usable.
File is wrong size.
0xF00800 Cannot complete request, situation has changed since start of the command.
B 0xF00900 Data or file size is too large.
0xF00900 Transaction size plus word address is too large.
C 0xF00B00
0xF00C00
Access denied; improper privilege. This will occur if data file is set to constant or protected.
Condition cannot be generated; resource is not available.
0xF00D00 Condition already exists; resource is readily available.

MicroLogix1000,1100,1200,1400,1500,SLC5/03/04/05,allviaENI 2
Adapter
PLC Errors for Allen-Bradley EtherNet/IP Protocol – Service Packet Errors 3
Panel Error Code
4
0xF00E00
0xF00F00
Command cannot be executed.
Histogram overflow.
5
0xF01000 No access.
0xF01100
0xF01200
Illegal data type.
Invalid parameter or invalid data.
6
0xF01300
0xF01400
Address reference exists to deleted area.
Command execution failure for unknown reason; possible histogram overflow.
7
0xF01500 Data conversion error.
0xF01600
0xF01700
Scanner not able to communicate with 1771 rack adapter.
Type mismatch.
8
0xF01800
0xF01900
1771 module response was not valid.
Duplicated label.
9
0xF02200 Remote rack fault.
0xF02300
0xF02400
Timeout.
Unknown error.
10
0xF01A00
0xF01B00
File is open; another node owns it.
Another node is the program owner.
11
0xF01C00 Reserved.
0xF01D00
0xF01E00
Reserved.
Data table element protection violation.
12
0xF01F00 Temporary internal problem.
13
14
Generic EtherNet IP Protocol – PLC Error Codes A
Only errors as listed in the Touch Panel Error Code Table shown on page A-3 can occur when
using the Generic Ethernet IP protocol, there are no PLC generated errors. B
C
D

GE 90-30 – Panel Error Code PLC-499 Explanation

A The PLC-499 error code is used to show any errors that are generated by the connected PLC.
2 This value can be looked up in the specific PLC’s error tables to determine the cause of the
error.The possible PLC generated error codes for the GE 90-30 communication protocol are
represented by a hexadecimal value as shown in the following message example.
3 GE 90-30 Error Code PLC-499 Message Example:
4
5 PLC
6
7
9 of 0013 indicates an “Port
configurator error.” PLC error.
10
11
12
13
14
A
B
C
D

GE 90-30 SNPX Protocol – PLC Error Code Tables

The following table lists the errors that can be generated by the GE 90-30 PLC when using the A
SNPX protocol.
Note: The following errors can be generated from the designated PLC, are monitored by the C-more touch 2
3
PLC Errors for GE 90-30 SNPX Protocol (Major)
4
PLC-499 Hex Value
No error Successful completion. (This is the expected completion value in the COMMREQ Status Word.)
Insufficient Privilege. For Series 90-70 PLC, the minor error code contains the privilege level required for
5
0x0002 the service request.
0x0004
0x0005
Protocol Sequence Error. The CPU has received a message that is out of order.
Service Request Error, the minor error code contains the specific error code.
6
0x0006 Illegal Mailbox Type. Service request mailbox type is either undefined or unexpected.
0x0007 The PLC CPU’s Service Request Queue is full. The master should retry later. It is recommended that the 7
master wait a minimum of 10 msec before sending another service request.
0x000A SNP DOS Driver Error. The minor error code contains the specific error code.
Illegal Service Request. The requested service is either not defined or not supported. (This value is
8
0x000B returned in lieu of the actual 01h value passed in the SNP error message, to avoid confusion with the
normal successful COMMREQ completion.)
Local SNP/SNP-X Error. An error occurred within the SNP task in the CMM module in this PLC. 9
0x000C This error may occur in either an SNP master or an SNP slave. The minor error code contains the specific
error code.
0x000D Remote SNP Error. An error occurred within the SNP slave task in the CMM module in the remote PLC.
The minor error code contains the specific error code.
10
Autodial Error. An error occurred while attempting to send a command string to an attached external
0x000E modem. The minor error code contains the specific error code.
SNP-X slave error. An error occurred within the SNPX task in the remote slave device. The minor error
11
0x000F code contains the specific error code.
0x0013 Port configurator error. 12
0x0050 Problem with sending mail to the slave Service Request task.
(Series 90-70 PLC CPUs only)
0x0051 Problem with getting mail from the slave Service Request task.
13
Slave SNP task timed out before receiving an SRP response.
0x0055 (Series 90-70 PLC CPUs only)
Slave SNP task could not find the requested datagram connection.
14
0x0056 (Series 90-70 PLC CPUs only)
0x0057 Slave SNP task encountered an error in trying to write the datagram.
A
0x0058 Slave SNP task encountered an error in trying to update the datagram.
(Series 90-70 PLC CPUs only) B
(PLC generated error codes for the GE 90-30 SNPX protocol continued on the next page.)
C
D

GE 90-30 SNPX Protocol – PLC Error Code Tables (cont’d)

A PLC Errors for GE 90-30 SNPX Protocol (Minor-Major) (cont’d)
2 PLC-499 Hex Value
PLC Error 0x010C WAIT-type COMMREQ is not permitted; must use NOW AIT-type.
PLC Error 0x010E Not used
3 PLC Error 0x010F The service request code in an X-Request message is unsupported or invalid at this time. This error may
occur if an SNP-X communication session has not been success fully established at the slave device.
4 PLC Error 0x020C

PLC Error 0x020E
COMMREQ command is not supported.
The modem command string length exceeds 250 characters.
Insufficient privilege level in the slave PLC CPU for the requested SNP-X service.
5 PLC Error 0x020F Password protection at PLC CPU may be preventing the requested service.
Unsupported COMMREQ. These errors are only generated when there is no protocol currently being run on
PLC Error 0x0213 a port, and the port receives a COMMREQ.
6 (The port may be disabled or an error has occurred in processing a new configuration).
SNP communication is not active. Must initiate a new SNP communication by sending an Attach or Long
PLC Error 0x030C Attach COMMREQ.
7 PLC Error 0x030E COMMREQ Data Block Length is too small.
Output command string data is missing or incomplete.
PLC Error 0x030F Invalid slave memory type in X-Request message.
8 PLC Error 0x0313 Invalid COMMREQ length.
PLC Error 0x040C SNP slave did not respond to Attach message from master.
9 PLC Error 0x040E Serial output timeout. The CMM module was unable to transmit the modem autodial output from the serial
port. (May be due to missing CTS signal when the CMM is configured to use hardware flow control.)
10 PLC Error 0x040F

PLC Error 0x0413
Invalid slave memory address or range in X-Request message.
Invalid COMMREQ status word location.
PLC Error 0x050C Unable to write SNP Status Word to local PLC memory;
11 PLC Error 0x050E
may be due to invalid Status Word memory type or address.
Response was not received from modem. Check modem and cable.
Invalid data length in X-Request message.
12 PLC Error 0x050F
PLC Error 0x0513
Data length must be non-zero, and may not exceed decimal 1000 bytes.
Invalid COMMREQ data.
PLC Error 0x060C Master device memory type is not valid in this PLC.
13 PLC Error 0x060E
Modem responded with BUSY.
Modem is unable to complete the requested connection. The remote modem is already in use; retry the
connection request at a later time.
14 PLC Error 0x060F
X-Buffer data length does not match the service request in X-Request message.
The X-Buffer message length is obtained from the Next Message Length field in the X-Request message;
the length of the data within the buffer message is always the message length.
A PLC Error 0x070C Master device memory address or length is zero.
Modem responded with NO CARRIER.
PLC Error 0x070E Modem is unable to complete the requested connection.
B Check the local and remote modems and the telephone line.
Queue Full indication from Service Request Processor in slave PLC CPU.
The slave is temporarily unable to complete the service request.
C PLC Error 0x070F The master should try again later. It is recommended that the master wait at least 10 msec before
repeating the X-Request.
D


PLC Errors for GE 90-30 SNPX Protocol (Minor-Major) (cont’d) A
PLC-499 Hex Value
0x080C Unable to read or write master device memory locations specified in COMMREQ. Usually caused by invalid
2
memory address for this PLC. SNP message exchange may have taken place.
0x080E Modem responded with NO DIALTONE. Modem is unable to complete the requested connection. Check the
modem connections and the telephone line. 3
Service Request Processor response exceeds 1000 bytes;
0x080F the SNP-X slave device cannot return the data in an X-Response message.
(This error applies to CMM module only.) 4
0x090C Master device memory data length exceeds maximum data size of CMM module (2048 bytes). Must use a
smaller data length. Use multiple COMMREQs if total data length exceeds this maximum value.
Modem responded with ERROR. Modem is unable to complete the requested command. Check the
5
0x090E modem command string and modem.
0x0A0C Slave device memory type is missing or not valid. 6
0x0A0E Modem responded with RING, indicating that the modem is being called by another modem. Modem is
unable to complete the requested command. Retry the modem command at a later time.
0x0B0C Slave device memory address is missing or zero. 7
An unknown response was received from the modem. Modem is unable to complete the requested
0x0B0E command. Check the modem command string and modem. The modem response is expected to be either
CONNECT or OK. 8
COMMREQ Data Block Length is too small.
0x0C0C (When expected COMMREQ length is 6 words or less. An improper length may cause other minor error
codes 6-11.) 9
0x0D0C Invalid Diagnostic Status Word (DSW) starting word or length.
0x0E0C Invalid maximum SNP message data size.
Must be an even value from 42 to 2048. 10
0x0F0C Invalid Privilege Level. Must be 0 through 4 or -1.
0x100C Invalid Fault Table selector.
Must be 1 for I/O Fault Table, or 2 for PLC Fault Table. 11
Unexpected Service Request Processor error.
0x100F (This error applies to CMM module only; the unexpected SRP error code is saved in the Diagnostic Status
Words in the CMM module.) 12
0x110C Invalid Fault Table starting index.
Must be 1-32 for I/O Fault Table, or 1-16 for PLC.
0x120C Invalid fault count. Must be 1-32 for I/O Fault Table, or 1-16 for PLC Fault Table. 13
0x130C Invalid Set PLC Date/Time mode. Must be 1-4.
0x140C
0x150C
Invalid Set PLC Date/Time date, time, or day-of-week value.
Unable to retrieve master device PLC time/date from PLC CPU.
14
Requested service is not permitted in a Broadcast request. The master must direct the X-Request message
0x150F to a specific SNP-X slave device.
Invalid slave PLC type.
A
0x160C Must be 0 for Series 90-70, or 1 for Series 90-30 or Series 90-20.
0x170C Invalid datagram type.
Must be 01h for normal datagram, or 81h (129) for permanent datagram.
B
0x180C Missing or too many datagram point formats. Must be 1-32.
0x190C Invalid datagram point format data. C
D


2 PLC-499 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.
3 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.
4 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
5 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.
6 0x200C
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’
time interval.
7 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.
8 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
9 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
10 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’.
11 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
12 0x240C
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
Datagram message was required. Communications have not been established.
13 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
14 0x270C
Datagram was required. Communications have not been established.
Another Break was received while SNP slave was waiting for an Attach or Update Realtime Datagram
message.
A 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.
A received SNP message has been NAKed the maximum number of two times.
B 0x290C The NAKed message may be retransmitted a maximum of two times.
C
D


PLC-499 Hex Value
0x2A0C An unknown message was received when an acknowledge (ACK or NAK) was required.
2
0x2B0C Sequence Error. An unexpected SNP message type was received.
0x2C0C Received SNP message contains bad next message length value.
Acknowledge timeout. An acknowledge (ACK or NAK) was not received within the configured T2 time
3
0x2D0C interval. A slave device may generate this error if the master device has aborted after maximum response
NAKs and does not NAK the next response retry.
Response timeout. The SNP Master did not receive an SNP Response message within the configured T5’
4
0x2E0C time interval.
0x2F0C Buffer message timeout. An expected Text Buffer or Connection Data message was not received within the
configured T5’’ time interval.
5
Serial output timeout. The CMM module was unable to transmit a Break, an SNP message, or SNP
0x300C acknowledge (ACK or NAK) from the serial port. (May be due to missing CTS signal when the CMM
module is configured to use hardware flow control.)
6
0x310C SNP slave did not receive a response from the Service Request Processor in the PLC CPU.
0x320C COMMREQ timeout.
The COMMREQ did not complete within the configured time interval.
7
0x330C An SNP Request or Response was aborted prior to completion due to reception of a Break.
0x340C PLC backplane communications error 8
0x350C Invalid Piggyback Status data memory type or address.
0x360C Invalid SNP Slave SNP ID. Must be a 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 slave device.
9
The SNP master has received a response message containing an unexpected data length. Usually indicates
0x370C a problem with the remote SNP slave device. May occur when Series 90-70 commands (Task Memory or
Program Block Memory Read/Write) are issued to a Series 90-30 slave device.
10
Response code in received SNP-X response message does not match expected value. (Response code
0x380C must equal the request code +80h.)
SNP-X Response message exceeds maximum data size (decimal 1000 bytes).
11
0x390C Data in the Response is ignored.
0x400C A parity error has occurred on an X-Attach Response message when establishing a new SNP-X
communication session. Communications have not been established.
12
0x400D The requested service is not supported by the SNP slave.
0x400F Serial output timeout. The slave was unable to transmit an SNP-X message from the serial port. (May be
due to missing CTS signal when the CMM module is configured to use hardware flow control.)
13
(PLC generated error codes for the GE 90-30 SNPX protocol continued on the next page.) 14
A
B
C
D


PLC-499 Hex Value
2 A framing or overrun error has occurred on an X-Attach Response message when establishing a new SNP-
0x410C X communication session.
3 0x410D SNP slave on CMM module requires PLC CPU privilege level 2 to operate. The SNP slave has rejected a
request to change to a higher or lower privilege level.
4 0x410F An SNP-X request was aborted prior to completion due to reception of a Break.
A BCC (Block Check Code) error has occurred on an X-Attach Response message when establishing a new
0x420C SNP-X communication session.
5 SNP Request or Response message exceeds maximum data length of the CMM module. (Total data length
0x420D for Mailbox and all following Buffer messages is 2048 bytes.) The master must use a smaller data length.
Use multiple requests if total data length exceeds the maximum value.
6 0x420F An X-Buffer message was received containing greater than 1000 bytes of data. The data is ignored.
An invalid message type was received when an X-Attach Response was required when establishing a new
7 0x430C SNP-X communication session.
Improper Write Datagram message format. Series 90-70 slave devices use a different format for this
8 0x430D
message than Series 90-30 or Series 90-20 slave devices. The master must use the proper message
format for this SNP slave device. (The SNP master in the CMMmodule sends this message as part of the
Establish Datagram COMMREQ command. The datagram has been partially established, but is not usable;
the datagram should be cancelled by using the Datagram ID returned by the COMMREQ.)
9 0x430F The SNP-X slave did not receive a response from the Service Request Processor in the PLC CPU.
An invalid next message type value was detected in an X-Attach Response message when establishing a
0x440C new SNP-X communication session.
10 Communications have not been established.
0x440D A datagram error occurred in a Series 90-70 slave device (dual-port error).
11 0x440F PLC backplane communications error.

An invalid response code was detected in an X-Attach Response message when establishing a new SNP-X
0x450C communication session.
An expected X-Attach Response message was not received within the response timeout interval when
0x460C establishing a new SNP-X communication session. The master has retried the X-Attach message twice
13 without receiving a response.
A parity error has occurred on an X-Attach Response message when re-establishing an existing SNP-X
0x500C communication session.
0x500F A parity error has occurred in a received X-Attach message.
A 0x510C
A framing or overrun error has occurred on an X-Attach Response message when re-establishing an
existing SNP-X communication session.
B 0x510F A framing or overrun error has occurred in a received X-Attach message.

A BCC (Block Check Code) error has occurred on an X-Attach Response message when re-establishing an
0x520C existing SNP-X communication session.
C 0x520F A BCC (Block Check Code) error has occurred in a received X-Attach message.
D


PLC-499 Hex Value
An invalid message type was received when an X-Attach Response was required when re-establishing an 2
0x530C existing SNP-X communication session.
0x530F An invalid Message Type was received when an X-Attach message was required. (For an X-Attach 3
message, the message type must be 58h = ’T’.)
0x540C
An invalid Next Message Type value was detected in an X-Attach Response message when re-establishing
an existing SNP-X communication session.
4
An invalid Next Message Type value was detected in a received X-Attach message. (For an X-Attach
0x540F message, the Next Message Length must be zero.)
An invalid response code was detected in an X-Attach Response message when re-establishing an existing
5
0x550C SNP-X communication session.
0x550F
An invalid request code was detected in a received X-Attach message.
6
An expected X-Attach Response message was not received within the response timeout interval when re-
0x560C establishing an existing SNP-X communication session. The master has retried the X-Attach message
twice without receiving a response. Communications have not been established.
7
0x600C A parity error has occurred on an X-Response message.
0x600F A parity error has occurred in a received X-Request message. 8
0x610C A framing or overrun error has occurred on an X-Response message.
0x610F
0x620C
A framing or overrun error has occurred in a received X-Request message.
A BCC (Block Check Code) error has occurred on an X-Response message.
9
0x620F A BCC (Block Check Code) error has occurred in a received X-Request message.
0x630C An invalid message type was received when an X-Response message was required. 10
0x640C An invalid next message type value was detected in an X-Response message.
0x650C
0x660C
An invalid response code was detected in an X-Response message.
An expected X-Response message was not received within the response time.
11
0x700C A parity error has occurred on an Intermediate Response message.
0x700F A parity error has occurred in a received X-Buffer message. 12
0x710C A framing or overrun error has occurred on an Intermediate Response message.
0x710F
0x720C
A framing or overrun error has occurred in a received X-Buffer message.
A BCC (Block Check Code) error has occurred on an Intermediate Response message.
13
0x720F A BCC(Block Check Code) error has occurred in a received X-Buffer message.
0x730C An invalid message type was received when an Intermediate Response message was required. 14
0x730F An expected X-Buffer message was not received.
0x740C
0x750C
An invalid next message type value was detected in an Intermediate Response message.
An invalid response code was detected in an Intermediate Response message.
A
0x760C An expected Intermediate Response message was not received within the response timeout interval.
B
C
D


2 PLC-499 Hex Value
0x8D0A Bad DOS Version. Must have DOS 2.0, or later, to support the SNP DOS Driver.
0x8E0A PC Serial port configured for SNP Master driver is not open; no communication can take place.
3 0x8F0A Out–of–Sequence SNP message. SNP message type received was not the type expected.
Bad SNP BCC encountered. Transmission was aborted after maximum retries due to a bad Block Check
0x900A Code.
4 0x910A Bad SNP communication. Transmission was aborted after maximum retries due to serial errors (that is,
parity, overrun, or framing errors).
No SNP communication. Either communication has been lost or a communication session has not been
5 0x920A
0xC105
established.
Invalid block state transition.
0xC205 The OEM key is NULL (inactive).
6 0xC305 Text length does not match traffic type.
0xC405 Verify with FA Card or EEPROM failed.
7 0xC505
0xC605
No task–level Rack/Slot configuration to read or delete.
Control Program (CP) tasks exist but requestor not logged into main CP.
0xC705 Passwords are set to inactive and cannot be enabled or disabled.
8 0xC805 Password(s) already enabled and can not be forced inactive.
0xC905 Login using non–zero buffer size required for block commands.
9 0xCA05
0xCB05
Device is write–protected.
A comm or write verify error occurred during save or restore.
0xCC05 Data stored on device has been corrupted and is no longer reliable.
10 0xCD05 Attempt was made to read a device but no data has been stored on it.
0xCE05 Specified device has insufficient memory to handle request.
11 0xCF05
0xD005
Specified device is not available in the system (not present).
One or more PLC modules configured have unsupported revision.
0xD105 Packet size or total program size does not match input.
12 0xD205 Invalid write mode parameter.
0xD305 User Program Module (UPM) read or write exceeded block end.
13 0xD405
0xD505
Mismatch of configuration checksum.
Invalid block name specified in datagram.
0xD605 Total datagram connection memory exceeded.
14 0xD705 Invalid datagram type specified.
0xD805 Point length not allowed.
A 0xD905
0xDA05
Transfer type invalid for this Memory Type selector.
Null pointer to data in Memory Type selector.
0xDB05 Invalid Memory Type selector in datagram.
B 0xDC05 Unable to find connection address.
0xDD05 Unable to locate given datagram connection ID.
C 0xDE05
0xDF05
Size of datagram connection invalid.
Invalid datagram connection address.
D (PLC generated error codes for the GE 90-30 SNPX protocol continued on the next page.)


PLC-499 Hex Value
0xE005 Service in process cannot login.
2
0xE105 No I/O configuration to read or delete.
0xE205
0xE305
IOS could not delete configuration, or bad type.
CPU revision number does not match.
3
0xE405
0xE505
Memory Type for this selector does not exist.
DOS file area not formatted.
4
0xE605 CPU model number does not match.
0xE705
0xE805
Configuration is not valid.
No user memory is available to allocate.
5
0xE905
0xEA05
Memory Type selector not valid in context.
Not logged in to process service request.
6
0xEB05 Task unable to be deleted.
0xEC05
0xED05
Task unable to be created.
VME bus error encountered.
7
0xEE05
0xEF05
Could not return block sizes.
Programmer is already attached.
8
0xF005 Request only valid in stop mode.
0xF105
0xF205
Request only valid from programmer.
Invalid program cannot log in.
9
0xF305
0xF405
I/O configuration mismatch.
Invalid input parameter in request.
10
0xF505 Invalid password.
0xF605
0xF705
Invalid sweep state to set.
Required to log in to a task for service.
11
0xF805
0xF905
Invalid Task Name referenced.
Task address out of range.
12
0xFA05 Cannot replace I/O module.
0xFB05
0xFC05
Cannot clear I/O configuration.
I/O configuration is invalid.
13
0xFD05
0xFE05
Unable to perform auto configuration.
No privilege for attempted operation.
14
0xFF05 Service Request Error has been aborted.
A
B
C
D

Mitsubishi FX Protocol – PLC Error Codes

A Only errors as listed in the Touch Panel Error Code Table shown on page A-3 can occur when
using the Mitsubishi FX protocol, there are no PLC generated errors.
2
3 Omron – Panel Error Code PLC-499 Explanation
The PLC-499 error code is used to show any errors that are generated by the connected PLC.
4 The PLC-499 error message includes a four digit hexadecimal value embedded in the message.
5 The possible PLC generated error codes for the Omron Host Link and FINS communication
protocol are represented by a hexadecimal value as shown in the following message example.
6 Omron Error Code PLC-499 Message Example:
7 Error code 0011 returned from

PLC
8
9
10
of 0011 indicates an “Framing
12 error.” PLC error when using
the Omron Host Link protocol.
13
14
A
B
C
D

Omron Host Link Protocol – PLC Error Code Table

The following table lists the errors that can be generated by the Omron PLC when using the A
Host Link protocol.
Note: The following errors can be generated from the designated PLC, are monitored by the C-more touch 2
3
PLC Error Codes for Omron Host Link
4
PLC-499 Hex Value
0x0000
0x0001
Normal Completion.
Not executable in RUN mode.
5
0x0002 Not executable in MONITOR mode.
0x0003 Not executable with PROM mounted. 6
0x0004 Address over (data overflow).
0x000B
0x000C
Not executable in PROGRAM mode.
Not executable in DEBUG mode.
7
0x000D Not executable in LOCAL mode.
0x0010 Parity error. 8
0x0011 Framing error.
0x0012
0x0013
Overrun.
FCS error.
9
0x0014 Format error (parameter length error).
0x0015 Entry number data error (parameter error, data code error, data length error). 10
0x0016 Instruction not found.
0x0018
0x0019
Frame length error.
Not executable (due to Un-executable error clear, non-registration of I/O table, etc.).
11
I/O table generation impossible (unrecognized remote I/O unit, channel over, duplication of optical
0x0020
0x00A0
transmitting I/O unit).
Abort due to parity error in transmit data under process.
12
0x00A1 Abort due to framing error in transmit data under process.
0x00A2 Abort due to overrun in transmit data under process. 13
0x00A3 Abort due to FCS error in transmit data under process.
0x00A4
0x00A5
Abort due to format error in transmit data under process.
Abort due to frame length error in transmit data under process.
14
0x00A8 Abort due to entry number data error in transmit data under process.
0x00B0 Un-executable due to program area capacity other than 16k bytes. A
B
C
D

Omron FINS Protocol – PLC Error Code Table

A The following table lists the errors that can be generated by the Omron PLC when using the
FINS protocol.
PLC Error Codes for Omron FINS

PLC-499 Hex Value
5 0x0000
0x0001
Normal Completion.
Service Canceled.
0x0101 Local Error: Local node not in network.
6 0x0102 Local Error: Token Timeout.
0x0103 Local Error: Retries Failed.
7 0x0104
0x0105
Local Error: Too many send frames.
Local Error: Node address range error.
0x0106 Local Error: Node Address Duplication.
8 0x0201 Destination Node Error: Destination Node not in network.
0x0202 Destination Node Error: Unit Missing.
9 0x0203
0x0204
Destination Node Error: Third Node missing.
Destination Node Error: Destination Node busy.
0x0205 Destination Node Error: Response Timeout.
10 0x0301 Controller Error: Communications Controller Error.
0x0302 Controller Error: CPU Unit Error.
11 0x0303
0x0304
Controller Error: Controller Error.
Controller Error: Unit number Error.
0x0401 Service Unsupported: Undefined Command.
12 0x0402 Service Unsupported: Not supported by Model/Version.
0x0501 Routing Table Error: Destination address setting error.
13 0x0502
0x0503
Routing Table Error: No routing tables.
Routing Table Error: Routing table error.
0x0504 Routing Table Error: Too many delays.
14 0x1001 Command Format Error: Command too long.
0x1002 Command Format Error: Command too short.
A 0x1003
0x1004
Command Format Error: Elements/Data don't match.
Command Format Error: Command format error.
0x1005 Command Format Error: Header Error.
B 0x1101 Parameter Error: Area classification missing.
0x1102 Parameter Error: Access Size Error.
C 0x1103 Parameter Error: Address range error.
(PLC generated error codes for the Omron FINS protocol continued on the next page.)
D

Omron FINS Protocol – PLC Error Code Table (cont’d)

PLC Error Codes for Omron FINS A
PLC-499 Hex Value
0x1104 Parameter Error: Address range exceeded.
2
0x1106 Parameter Error: Program Missing.
0x1109
0x110A
Parameter Error: Relational Error.
Parameter Error: Duplicate Data Access.
3
0x110B
0x110C
Parameter Error: Response too long.
Parameter Error: Parameter Error.
4
0x2002 Read Not Possible: Protected.
0x2003
0x2004
Read Not Possible: Table missing.
Read Not Possible: Data missing.
5
0x2005
0x2006
Read Not Possible: Program missing.
Read Not Possible: File missing.
6
0x2007 Read Not Possible: Data mismatch.
0x2101
0x2102
Write Not Possible: Read Only.
Write Not Possible: Protected - cannot write data link table.
7
0x2103
0x2105
Write Not Possible: Cannot register.
Write Not Possible: Program missing.
8
0x2106 Write Not Possible: File missing.
0x2107
0x2108
Write Not Possible: File name already exists.
Write Not Possible: Cannot change.
9
0x2201
0x2202
Not executable in current mode: Not possible during execution.
Not executable in current mode: Not possible while running.
10
0x2203 Not executable in current mode: Wrong PLC mode (Program).
0x2204
0x2205
Not executable in current mode: Wrong PLC mode (Debug).
Not executable in current mode: Wrong PLC mode (Monitor).
11
0x2206
0x2207
Not executable in current mode: Wrong PLC mode (Run).
Not executable in current mode: Specified node not polling node.
12
0x2208 Not executable in current mode: Step cannot be executed.
0x2301
0x2302
No such device: File device missing.
No such device: Missing memory.
13
0x2303
0x2401
No such device: Clock missing.
Cannot Start/Stop: Table missing.
14
0x2502 Unit Error: Memory Error.
0x2503
0x2504
Unit Error: I/O setting Error.
Unit Error: Too many I/O points.
A
0x2505
0x2506
Unit Error: CPU bus error.
Unit Error: I/O Duplication.
B
(PLC generated error codes for the Omron FINS protocol continued on the next page.) C
D

Omron FINS Protocol – PLC Error Code Table (cont’d)

A PLC Error Codes for Omron FINS
2 PLC-499 Hex Value
0x2507 Unit Error: I/O bus error.
0x2509 Unit Error: SYSMAC BUS/2 error.
3 0x250A
0x250D
Unit Error: CPU Bus Unit Error.
Unit Error: SYSMAC BUS No. duplication.
4 0x250F
0x2510
Unit Error: Memory Error.
Unit Error: SYSMAC BUS terminator missing.
0x2601 Command Error: No protection.
5 0x2602
0x2604
Command Error: Incorrect password.
Command Error: Protected.
6 0x2605
0x2606
Command Error: Service already executing.
Command Error: Service stopped.
0x2607 Command Error: No execution right.
7 0x2608
0x2609
Command Error: Settings not complete.
Command Error: Necessary items not set.
8 0x260A
0x260B
Command Error: Number already defined.
Command Error: Error will not clear.
0x3001 Access Right Error: No access right.
9 0x4001 Abort: Service aborted.
10
11
12
13
14
A
B
C
D

Omron – Panel Error Code P495 Explanation

The possible PLC generated error codes for the Omron CS/CJ FINS ethernet communication
2
protocol are represented by a hexadecimal value as shown in the following message example.
3
4
PLC
5
6
7
Panel error code PLC-495 showing
8
a hexadecimal value of 0504
indicates a “Routing table error:
Too many relays” PLC error.
9
10
11
12
13
14
A
B
C
D

Omron CS/CJ FINS Ethernet Protocol – PLC Error Code Table

A The following table lists the errors that can be generated by the Omron PLC when using the
CS/CJ FINS Ethernet protocol.
PLC Error Codes for Omron CS/CJ FINS Ethernet

PLC-495 Hex Value
5 0103
0201
Local Error: Send Error from lack of buffer space. Try reducing Ethernet load to the module.
Destination Node Error: IP address of remote node not set correctly.
0202 Destination Node Error: No node with the specified unit address found.
6 0205 Destination Node Error: Packet corrupted or Response timeout. Try increasing timeout.
0301 Controller Error: Communications controller error.
7 0302
0304
Controller Error: CPU Unit error. Check error LEDs on PLC. Refer to documentation for that CPU.
Controller Error: Unit number error. Make sure Unit number is not used twice.
0401 Service unsupported: Undefined command.
8 0501 Routing table error: Destination address setting error. Routing table incorrect.
0502 Routing table error: No routing tables.
9 0503
0504
Routing table error: Routing table error.
Routing table error: Too many relays.
1001 Command format error: Command too long. Bad packet: check for electrical noise and grounding.
10 1002 Command format error: Command too short. Bad packet: check for electrical noise and grounding.
1003 Command format error: Elements/data don't match. Bad packet: check for electrical noise and grounding.
11 1005 Command format error: Header error. This is the error received when station # set in the command does
not match the station # of the Ethernet module.
1100 Parameter error: UDP socket number bad.
12 1101
1103
Parameter error: Address requested does not exist in PLC.
Parameter error: Address area requested in not accessible.
220F Status error: Duplicate Socket error.
13 2210 Status error: Specified socket not open.
2305 Environment Error: IP address conversion failed. Only encountered when using routing tables.
14 2307
2503
Environment Error: IP address conversion set for automatic.
Unit error: I/O setting error.
2505 Unit error: CPU bus error.
A 250A Unit error: CPU Bus Unit error.
B
C
D

Siemens – Panel Error Code P499 Explanation

The PLC-499 error message includes a four digit hexadecimal value displayed at the end of the
message. This value can be looked up in the specific PLC’s error tables to determine the cause
of the error. The possible PLC generated error codes for the Siemens PPI communication
2
protocols breakdown into a four digit hexadecimal value as shown in the following message
example. 3
Siemens Error Code PLC-499 Message Example:
4
Error code 0x8702 returned
from PLC
5
6
7
8
showing a hexadecimal value of 9
0x8702 indicates an “Address is
invalid.” PLC error.
10
11
12
13
14
A
B
C
D

Siemens PPI Protocol – PLC Error Code Table

A PLC PDU Header Errors for S7-200 PPI
2 PLC-499 Hex Value
0x0001 Hardware Fault.
0x0003 Object access not allowed: Occurs when access to Timer and Counter data type is set to Signed Integer
3 0x0004
and not BCD.
Context not supported.
Address out of range: Occurs when requesting an address within a Data Block that does not exist or is out
4 0x0005
0x0006
of range.
Address out of range.
5 0x0007
0x000A
Write Data size mismatch.
Object does not exist: Occurs when trying to request a Data Block that does not exist.
0x8000 Function being used.
6 0x8001 Action is not allowed in current mode.
0x8101 Hardware fault.
7 0x8103
0x8104
Access not allowed.
Function not supported.
0x8105 Address invalid.
8 0x8106 Data Type not supported.
0x8107 Data Type is not consistent with size.
9 0x810A
0x8500
Object does not exist.
PDU Size is incorrect.
0x8702 Address is invalid.
10 0xD201 Block name syntax error.
0xD202 Error with function parameter.
11 0xD203
0xD204
Error with block type.
No linked block.
12 0xD205
0xD206
Object already exists.
0xD207 Block already used in EPROM.
13 0xD209 Block does not exist.
0xD20E No Block does not exist.
14 0xD210 Block number incorrect.
A
B
C
D

Siemens ISO over TCP Protocol – PLC Error Code Table

PLC PDU Header Errors for S7-200 CPU, S7-300, S7-1200 Ethernet A
PLC-499 Hex Value
0x0001 Hardware Fault.
2
0x0003 Object access not allowed: Occurs when access to Timer and Counter data type is set to Signed Integer
0x0004
and not BCD.
Context not supported.
3
Address out of range: Occurs when requesting an address within a Data Block that does not exist or is out
0x0005
0x0006
of range.
Address out of range.
4
0x0007
0x000A
Write Data size mismatch.
Object does not exist: Occurs when trying to request a Data Block that does not exist.
5
0x8000 Function being used.
0x8001 Action is not allowed in current mode. 6
0x8101 Hardware fault.
0x8103
0x8104
Access not allowed.
Function not supported.
7
0x8105 Address invalid.
0x8106 Data Type not supported. 8
0x8107 Data Type is not consistent with size.
0x810A
0x8500
Object does not exist.
PDU Size is incorrect.
9
0x8702 Address is invalid.
0xD201 Block name syntax error. 10
0xD202 Error with function parameter.
0xD203
0xD204
Error with block type.
No linked block.
11
0xD205
0xD206
12
0xD207 Block already used in EPROM.
0xD209 Block does not exist. 13
0xD20E No Block does not exist.
0xD210 Block number incorrect.
14
A
B
C
D

PLC Error Codes

Uploaded by

PLC Error Codes

Uploaded by

PANEL & PLC APPENDIX

ERROR CODE TABLES

If you have difficulty determining the cause of the error,

A–2 ® EA-USER-M Hardware User Manual, 2nd Ed. Rev. G, 08/14

C-more Touch Panel Error Code Table

PLC-004 STX is not found

PLC-011 Invalid value in function code

PLC-014 Transaction ID does not match

® EA-USER-M Hardware User Manual, 2nd Ed. Rev. G, 08/14 A–3

C-more Touch Panel Error Code Table (cont’d)

A–4 ® EA-USER-M Hardware User Manual, 2nd Ed. Rev. G, 08/14

DirectLOGIC – Panel Error Code PLC-499 Explanation

DirectLOGIC error code tables continued on the next page.

® EA-USER-M Hardware User Manual, 2nd Ed. Rev. G, 08/14 A–5

Modbus Protocols Error Code P499 Explanation

A–6 ® EA-USER-M Hardware User Manual, 2nd Ed. Rev. G, 08/14

Productivity3000 Error Code P499

® EA-USER-M Hardware User Manual, 2nd Ed. Rev. G, 08/14 A–7

Allen-Bradley – Panel Error Code PLC-499 Explanation

5 AB DF1 and DH485 Protocol Error Code PLC-499 Breakdown

A–8 ® EA-USER-M Hardware User Manual, 2nd Ed. Rev. G, 08/14

Allen-Bradley DF1 & DH485 Protocols – PLC Error Code Tables

® EA-USER-M Hardware User Manual, 2nd Ed. Rev. G, 08/14 A–9

Allen-Bradley DF1 & DH485 Protocols – PLC Error Code Tables

A–10 ® EA-USER-M Hardware User Manual, 2nd Ed. Rev. G, 08/14

Allen-Bradley EtherNet/IP Protocol –

® EA-USER-M Hardware User Manual, 2nd Ed. Rev. G, 08/14 A–11

Allen-Bradley – EtherNet/IP Protocol– PLC Error Code Tables

5 PLC Errors for Allen-Bradley EtherNet/IP Protocol –Encapsulation Errors

0x00000068 Reserved for legacy (Rockwell Automation).

0x0000ffff Reserved for future expansion.

A–12 ® EA-USER-M Hardware User Manual, 2nd Ed. Rev. G, 08/14

Allen-Bradley – EtherNet/IP Protocol – PLC Error Code Tables

® EA-USER-M Hardware User Manual, 2nd Ed. Rev. G, 08/14 A–13

Allen-Bradley – EtherNet/IP Protocol – PLC Error Code Tables

A–14 ® EA-USER-M Hardware User Manual, 2nd Ed. Rev. G, 08/14

Allen-Bradley – EtherNet/IP Protocol – PLC Error Code Tables

® EA-USER-M Hardware User Manual, 2nd Ed. Rev. G, 08/14 A–15

0x00000063 Reserved for legacy (Rockwell Automation).

PLC Errors for Allen-Bradley EtherNet/IP Protocol – CIP Errors

A–16 ® EA-USER-M Hardware User Manual, 2nd Ed. Rev. G, 08/14

® EA-USER-M Hardware User Manual, 2nd Ed. Rev. G, 08/14 A–17

A–18 ® EA-USER-M Hardware User Manual, 2nd Ed. Rev. G, 08/14

® EA-USER-M Hardware User Manual, 2nd Ed. Rev. G, 08/14 A–19

A–20 ® EA-USER-M Hardware User Manual, 2nd Ed. Rev. G, 08/14

® EA-USER-M Hardware User Manual, 2nd Ed. Rev. G, 08/14 A–21

GE 90-30 – Panel Error Code PLC-499 Explanation

A–22 ® EA-USER-M Hardware User Manual, 2nd Ed. Rev. G, 08/14

GE 90-30 SNPX Protocol – PLC Error Code Tables

® EA-USER-M Hardware User Manual, 2nd Ed. Rev. G, 08/14 A–23

GE 90-30 SNPX Protocol – PLC Error Code Tables (cont’d)

4 PLC Error 0x020C

10 PLC Error 0x040F

A–24 ® EA-USER-M Hardware User Manual, 2nd Ed. Rev. G, 08/14

GE 90-30 SNPX Protocol – PLC Error Code Tables (cont’d)

® EA-USER-M Hardware User Manual, 2nd Ed. Rev. G, 08/14 A–25

GE 90-30 SNPX Protocol – PLC Error Code Tables (cont’d)

A–26 ® EA-USER-M Hardware User Manual, 2nd Ed. Rev. G, 08/14

GE 90-30 SNPX Protocol – PLC Error Code Tables (cont’d)

® EA-USER-M Hardware User Manual, 2nd Ed. Rev. G, 08/14 A–27

GE 90-30 SNPX Protocol – PLC Error Code Tables (cont’d)

11 0x440F PLC backplane communications error.

B 0x510F A framing or overrun error has occurred in a received X-Attach message.

A–28 ® EA-USER-M Hardware User Manual, 2nd Ed. Rev. G, 08/14

GE 90-30 SNPX Protocol – PLC Error Code Tables (cont’d)

® EA-USER-M Hardware User Manual, 2nd Ed. Rev. G, 08/14 A–29

GE 90-30 SNPX Protocol – PLC Error Code Tables (cont’d)

A–30 ® EA-USER-M Hardware User Manual, 2nd Ed. Rev. G, 08/14

GE 90-30 SNPX Protocol – PLC Error Code Tables (cont’d)

® EA-USER-M Hardware User Manual, 2nd Ed. Rev. G, 08/14 A–31

Mitsubishi FX Protocol – PLC Error Codes

6 Omron Error Code PLC-499 Message Example:

7 Error code 0011 returned from

A–32 ® EA-USER-M Hardware User Manual, 2nd Ed. Rev. G, 08/14

Omron Host Link Protocol – PLC Error Code Table

® EA-USER-M Hardware User Manual, 2nd Ed. Rev. G, 08/14 A–33