C-more RS232, RS422, RS485 User Manual

Appendix

Panel & PlC error Code Tables

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 Error Code PLC-499 Message Example: ............................................... A-8

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

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

Allen-Bradley EtherNet/IP Protocol –

Panel Error Code PLC-496, 497 and 498 Explanation ............................................ A-11

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

ControlLogix, CompactLogix, & FlexLogix ............................................................. A-12

Allen-Bradley – EtherNet/IP Protocol – PLC Error Code Tables MicroLogix 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

Appendix

Panel & PlC error Code Tables

GE 90-30 – Panel Error Code PLC-499 Explanation ................................................ A-22

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

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 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 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 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.

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 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 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.

Note: These PLC error codes are provided by the manufacturer of the related PLC and are subject to change by the PLC manufacturer. Please refer to the manufacturers documentation for a more complete and up-todate list of error codes.

A-2

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 Setup Screens for additional details.

If you have difficulty determining the cause of the error, please refer to Chapter 8: Troubleshooting for some troubleshooting tips or contact our technical support group at 770-844-4200 or the 3rd party PLC manufacturer.

Stride™

Ethernet Switch

10/100 Base-T

(such as SE-SW5U)

H0-ECOM/H0-ECOM100

Ethernet Module

DL06 PLC

EA-USER-M Hardware User Manual, 3rd Ed, Rev A, 06/20

Ethernet CAT5

Cable - Straight-thru

C-more

Touch Panel

(Bottom View)

STX is not found

C-more Error Message

Ethernet

Port

Appendix A: Panel & PLC Error Code Tables

C-more Touch Panel Error Code Table

The following table includes all of the error codes and error messages that the panel will display 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.

C-more Touch Panel Error Code Table

Error Code Error Message Cause

PLC Communication Timeout (for single

PLC-001

PLC-002 NAK received from PLC

PLC-003 EOT received from PLC

PLC-004 STX is not found

PLC-005 ETX or ETB is not found

PLC-006 LRC does not match

PLC-007 CRC does not match

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.

PLC-010 Data size does not match

PLC-011 Invalid value in function code There is an invalid value in the function code.

PLC-012 Invalid command sent to PLC

PLC-013 ENQ received from PLC

PLC-014 Transaction ID does not match

PLC-015 %Device% No device found A PLC device designated as %Device% could not be found. PLC-016 Data byte communication error 0 byte of data is recieved PLC-017 Out of address range The touch panel requested a file number larger than 255. PLC-018 Panel communication timeout The server panel did not respond when using the Panel Pass Through. PLC-019 Found in parity error by hardware An error detected in the PLC memory.

PLC-020 Can’t open serial port

PLC-021 PLC number does not match The PLC number does not match the PLC number configured. PLC-022 Can’t reset DCB Unable to reset the data communication bit.

PLC-023 Cable not connected properly Communication cable incorrectly installed.

PLC) %Device% PLC Communication Timeout (for multiple PLCs, such as RS-422/485)

C-more Touch Panel Error Code Table continued on the next page.

A timeout occurred after sending a request to the PLC %Device%. %Device% indicates the device name, such as DEV001.

Example error message for multiple PLCs: DEV001 PLC Communication Timeout.

A negative acknowledgement (NAK) control code has been generated during a read/write request.

An End of Transmission (EOT) control code is sent by the PLC in response to a Read/Write/SetBit request..

A Start of Text (STX) control code was not found in the data packet received from the PLC.

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.

There was an incorrect Longitudinal Redundancy Check (LRC) control code in the communications packet received from the PLC. This is an indication that the data in the packet is corrupted.

There was an incorrect Cyclic Redundancy Check (CRC) control code in the communications packet received from the PLC. This is an indication that the data in the packet is corrupted.

There are an incorrect number of bytes found in the data packet returned from the 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 0x15 value) in the defined packet field, then an enquiry (ENQ) control code error will be displayed.

This error will be displayed if after checking the Transaction ID Bytes in the data packet, there is no match to what was requested.

Cannot open the Serial Port. If this error shows on the panel, it indicates a hardware problem.

EA-USER-M Hardware User Manual, 3rd Ed, Rev A, 06/20

A-3

Appendix A: Panel & PLC Error Code Tables

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

Error Code Error Message Cause

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

PLC-026 PLC connection timeout A timeout occured after sending a request to the PLC.

PLC-027 Memory type incorrect

PLC-028 PLC failed to respond The PLC failed to respond after sending a request to the PLC.

PLC-495 Omron Ethernet Error

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

PLC-496 Error code 0xaaaaaaaa returned from PLC

PLC-497 Error code 0xaaaaaaaa returned from PLC

PLC-498 Error code 0xaaaaaaaa returned from PLC

PLC-499 Error code XXXX returned from PLC

PLC-500 Cannot write to Serial Port

PLC-700 Not enough buffer memory

PLC-701 Access to inaccessible PLC memory

PLC-702 Cannot access by different function code

PLC-703 Write request to PLC Read Only Memory

PLC-704 Bad device-access

PLC-705 Protocol does not match

An error code specific to Omron Ethernet with a Value of XXXX has been returned from the PLC. See the explanation for error code PLC-495 proceeding the Omron CS/CJ FINS Ethernet error code tables.

Allen-Bradley EtherNET/IP specific. Encapsulation Error. See the explanation for error code PLC-496 proceeding the AllenBradley EtherNet/IP error code tables.

Allen-Bradley EtherNET/IP specific. CIP Error. See the explanation for error code PLC-497 proceeding the AllenBradley EtherNet/IP error code tables.

Allen-Bradley EtherNET/IP specific. Service Packet Error. See the explanation for error code PLC-498 proceeding the AllenBradley EtherNet/IP error code tables.

An error code with a value of XXXX has been returned from the 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.

Data cannot write to the Serial port. Data was sent to the PLC via the Serial Port. If this error shows on the Panel, it indicates a Hardware Problem.

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 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. This error is an indication that there is a problem in the HMI layer.

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.

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.

The protocol for the device does Not match between the server and client when using the panel pass through.

A-4

EA-USER-M Hardware User Manual, 3rd Ed, Rev A, 06/20

Appendix A: Panel & PLC Error Code Tables

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. 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 represented by a hexadecimal value as shown in the following message example.

Direct LOGIC Error Code PLC-499 Message Example:

Error code 0003 returned from PLC

Panel error code PLC-499

showing a hexadecimal value

of 0003 indicates an “Illegal

data value dependent upon

the request.” PLC error.

DirectLOGIC K-Sequence Protocol – PLC Error Code Table

The following table lists the errors that can be generated by the DirectLOGIC PLC when using the K-Sequence protocol.

PLC Error Codes for Direct LOGIC – K-Sequence

Panel Error Code

PLC-499 Hex Value

01F8 Error setting value. 020D Error in key mode. 021C Password protected.

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 message, if active. Please refer to the PLC manufacturer’s documentation for additional information.

Description

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 using the DirectLOGIC DirectNET protocol, there are no PLC generated errors.

DirectLOGIC error code tables continued on the next page.

EA-USER-M Hardware User Manual, 3rd Ed, Rev A, 06/20

A-5

Appendix A: Panel & PLC Error Code Tables

Modbus Protocols Error Code P499 Explanation

The following table lists the errors that can be generated by the Modbus protocols:

AutomationDirect CLICK

AutomationDirect DirectLOGIC - Modbus (Koyo)

Modicon Modbus RTU

Entivity Modbus RTU

PLC Error Codes Modbus Protocols

Panel Error Code

P499 Hex Value

0x0001

0x0002

0x0003

0x0004

Name Meaning

The function code received in the query is not an allowable action for the server (or slave). This

ILLEGAL FUNCTION

ILLEGAL DATA ADDRESS

ILLEGAL DATA VALUE

SLAVE DEVICE FAILURE

may be because 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 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). 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. If a request is submitted with a starting register address of 96 and a quantity of registers of 4, then the request will successfully operate (address-wise at least) on registers 96, 97, 98, 99. If 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.

A value contained in the query data field is not an allowable value for server (or slave). This indicates a fault in the structure of the remainder of a complex request, such as that the implied length is incorrect. It specifically 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.

An unrecoverable error occurred while the server (or slave) was attempting to perform the requested action.

DirectLOGIC ECOM Protocol – PLC Error Codes

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.

A-6

EA-USER-M Hardware User Manual, 3rd Ed, Rev A, 06/20

Appendix A: Panel & PLC Error Code Tables

Productivity3000 Error Code P499

PLC Error Codes for Productivity3000

Panel Error Code

P499 Hex Value

The function code received in the query is not an allowable action for the server (or slave). This may be because

0x0001

0x0002

0x0003

0x0004 An unrecoverable error occurred while the server (or slave) was attempting to perform the requested action.

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 unconfigured and is being asked to return registered values.

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 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 in the structure of the remainder of a complex request, such as that the implied length is incorrect. It specifically 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.

Meaning

EA-USER-M Hardware User Manual, 3rd Ed, Rev A, 06/20

A-7

Appendix A: Panel & PLC Error Code Tables

AB DF1 and DH485 Protocol Error Code PLC-499 Breakdown

Appendix A: Panel & PLC Error Code Tables

Allen-Bradley – Panel Error Code PLC-499 Explanation

The PLC-499 error code is used to show any errors that are generated by the connected PLC. 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 Allen-Bradley DF1 and DH485 communication protocols are represented by a hexadecimal value as shown in the following 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.

Allen-Bradley Error Code PLC-499 Message Example:

Remote 4-7 bits

16-bit Word

PLC-499 Error Code Message Displayed Hexadecimal Value

Local

0-3 bits

EXT STS

byte

Example of an EXT STS error

1 7 F 0

hex

1 1 1 0 1 0 0 0 0 0 0 0 1 1 1 1 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15

for a “Type mismatch.”

Error code 1700 returned from PLC

AB DF1 and DH485 Protocol – Multiple Error Code Examples

Remote 4-7 bits

Local

0-3 bits

EXT STS

byte

Error PLC-499

Value Displayed

Example 1 Example 2 Example 3

x x x F

x x 0 x

9 0 x x

9 0 0 F

Panel error code PLC-499

showing a hexadecimal value

of 1700 indicates “Illegal command or format.”and

“Station is offline.” PLC errors.

x x x 1

x x 1 x

0 0 x x

0 0 1 1

x x x F

x x 1 x

9 0 x x

9 0 1 F

A-8

EA-USER-M Hardware User Manual, 3rd Ed, Rev A, 06/20

Appendix A: Panel & PLC Error Code Tables

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 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. DH485 includes all MicroLogix and SLC500 PLC’s and any communication connection using an Allen-Bradley AIC device using the DH485 protocol.

PLC Errors for Allen-Bradley DF1 and DH485 Protocols, Local STS Errors (0-3 bits)

Panel Error Code

PLC-499 Hex Value

0x0 Success; no error. 0x1 DST node is out of buffer space.

0x2

0x3 Duplicate token holder detected. 0x4 Local port is disconnected. 0x5 Application layer timed out waiting for response. 0x6 Duplicate node detected. 0x7 Station is offline. 0x8 Hardware fault.

PLC Errors for Allen-Bradley DF1 and DH485 Protocols, Remote STS Errors (4-7 bits)

Panel Error Code

PLC-499 Hex Value

0x0 Success; no error. 0x10 Illegal command or format. 0x20 Host has a problem and will not communicate. 0x30 Remote node host is missing, disconnected, or shut down. 0x40 Host could not complete function due to hardware fault. 0x50 Addressing problem or memory protect rungs. 0x60 Function not allowed due to command protection selection. 0x70 Processor is in Program Mode. 0x80 Compatibility mode file missing or communication zone problem. 0x90 Remote node cannot buffer command. 0xA0 Wait ACK (1775 KA buffer full). 0xB0 Remote node problem due to download. 0xC0 Wait ACK (1775 KA buffer full). 0xD0 not used 0xE0 not used

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.)

Cannot guarantee delivery; link layer. (The remote node specified does not ACK command.)

Description

EA-USER-M Hardware User Manual, 3rd Ed, Rev A, 06/20

A-9

Appendix A: Panel & PLC Error Code Tables

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

PLC Errors for Allen-Bradley DF1 and DH485 Protocols, EXT STS Command Code for F0 Command

Panel Error Code

PLC-499 Hex Value

0x0 not used 0x1 A field has an illegal value. 0x2 Fewer levels specified in address than minimum for any address. 0x3 More levels specified in address than system supports. 0x4 Symbol not found. 0x5 Symbol is of improper format. 0x6 Address does not point to something usable. 0x7 File is wrong size. 0x8 Cannot complete request; situation has changed since start of the command. 0x9 Data or file size is too large. 0xA Transaction size plus word address is too large. 0xB Access denied; improper privilege. 0xC Condition cannot be generated; resource is not available. 0xD Condition already exists; resource is readily available. 0xE Command cannot be executed.

0xF Histogram overflow. 0x10 No access. 0x11 Illegal data type. 0x12 Invalid parameter or invalid data. 0x13 Address reference exists to deleted area.

0x14

0x15 Data conversion error. 0x16 Scanner not able to communicate with 1771 rack adapter. 0x17 Type mismatch. 0x18 1771 module response was not valid. 0x19 Duplicated label. 0x22 Remote rack fault. 0x23 Timeout. 0x24 Unknown error. 0x1A File is open; another node owns it. 0x1B Another node is the program owner. 0x1C Disk File is write protectid or otherwise unavailable 0x1D Disk File is being used by another application. Update not performed (offline only). 0x1E Data table element protection violation. 0x1F Temporary internal problem.

Command execution failure for unknown reason; possible PLC 3 histogram overflow.

Description

A-10

EA-USER-M Hardware User Manual, 3rd Ed, Rev A, 06/20

Appendix A: Panel & PLC Error Code Tables

Allen-Bradley EtherNet/IP Protocol – Panel Error Code PLC-496, 497 and 498 Explanation

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 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-Bradley EtherNet/IP communication protocol is represented by a hexadecimal value as shown in the following message example.

Allen-Bradley Error Code PLC-496, 497, 498 Message Example:

Error code 00000065 returned from PLC

Panel error code PLC-496

showing a hexadecimal value

of 00000065 indicates an “The

target received a message of

invalid length.” PLC error.

EA-USER-M Hardware User Manual, 3rd Ed, Rev A, 06/20

A-11

+ 30 hidden pages