Appendix. Panel and PLC. Error Code Tables. In This Appendix...

Transcription

1 Panel and PL Error ode Tables ppendix In This ppendix... Introduction more Touch Panel Error ode Table... - irectlogi Panel Error ode PL- Explanation... - irectlogi K-Sequence Protocol PL Error ode Table... - irectlogi irectnet Protocol PL Error odes... - Modbus Protocols Error ode P Explanation... - utomationirect LIK... - utomationirect irectlogi - Modbus (Koyo)... - Modicon Modbus RTU... - Entivity Modbus RTU... - irectlogi EOM Protocol PL Error odes... - Productivity Error ode P... - utomationirect o-more Error odes... - llen-radley Panel Error ode PL- Explanation... - llen-radley F1 & H Protocols PL Error ode Tables... - llen-radley EtherNet/IP Protocol Panel Error ode PL-, and Explanation llen-radley EtherNet/IP Protocol PL Error ode Tables ontrollogix, ompactlogix, & FlexLogix llen-radley EtherNet/IP Protocol PL Error ode Tables Generic EtherNet IP Protocol PL Error odes... - GE 0-0 Panel Error ode PL- Explanation... - GE 0-0 SNPX Protocol PL Error ode Tables... - Mitsubishi FX Protocol PL Error odes... -

2 Panel and PL Error ode Tables ppendix Omron Panel Error ode PL- Explanation...- Omron Host Link Protocol PL Error ode Table...- Omron FINS Protocol PL Error ode Table...- Omron Panel Error ode P Explanation...- Omron S/J FINS Ethernet Protocol PL Error ode Table...- Siemens Panel Error ode P Explanation...-0 Siemens PPI Protocol PL Error ode Table...-1 Siemens ISO over TP Protocol PL Error ode Table...-

3 Panel and PL Error ode Tables ppendix This page intentionally left blank

4 ppendix - Panel and PL Error ode Tables Introduction The -more family of touch panels is capable of communicating with a wide variety of Programmable Logic ontrollers. -more is capable of communicating over RS, RS and RS serial networks as well as Ethernet networks. It communicates with all utomationirect PLs utilizing various protocols. -more also communicates with other brands of PLs by their different protocols. For a complete list of PLs and protocols, see Step onnect Touch Panel to PL in hapter 1: Getting Started. s 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 -more can detect. If a -more communications error does occur, the error message will appear across the top of the screen. The -more touch panel also monitors any errors that are generated by the various PLs that are connected to it. If any of the PL generated errors are detected, they are displayed across the top of the panel s display embedded as a hexadecimal value in error code P s message. n explanation of how the specific PL error is identified in the panel error code P is shown proceeding the specific manufacturer s PL 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 PL error codes are provided by the manufacturer of the related PL and are subject to change by the PL manufacturer. Please refer to the manufacturers documentation for a more complete and up-to-date list of error codes. ll 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 hapter : System Setup Screens for additional details. If you have difficulty determining the cause of the error, please refer to hapter : Troubleshooting for some troubleshooting tips or contact our technical support H0-EOM/H0-EOM0 Ethernet Module L0 PL Stride Ethernet Switch /0 ase-t (such as SE-SWU) Ethernet T able STX is not found -more Touch Panel -more Error Message uto MI / MI-X Ethernet Port - E-USER-M Hardware User Manual, 1st Ed. Rev. F

5 ppendix - Panel and PL Error ode Tables -more Touch Panel Error ode Table The following table includes all of the error codes and error messages that the panel will display if the listed cause is detected. ll of these errors involve problems that could result with the panel communicating with the connected PL. e aware that not all of the panel errors are used with each type of PL that can be connected to the panel. Error ode Error Message PL-001 PL-00 PL-00 PL-00 PL-00 PL-00 PL-00 PL ommunication Timeout (for single PL) %evice% PL ommunication Timeout (for multiple PLs, such as RS-/) NK received from PL EOT received from PL STX is not found ETX or ET is not found LR does not match R does not match -more Touch Panel Error ode Table ause timeout occurred after sending a request to the PL %evice%. %evice% indicates the device name, such as EV001. Example error message for multiple PLs: EV001 PL ommunication Timeout. negative acknowledgement (NK) control code has been generated during a read/write request. n End of Transmission (EOT) control code is sent by the PL in response to a Read/Write/Setit request.. Start of Text (STX) control code was not found in the data packet received from the PL. Neither an End of Text (ETX) nor an End of Transmission lock (ET) control code was found in the data packet received from the PL. There was an incorrect Longitudinal Redundancy heck (LR) control code in the communications packet received from the PL. This is an indication that the data in the packet is corrupted. There was an incorrect yclic Redundancy heck (R) control code in the communications packet received from the PL. This is an indication that the data in the packet is corrupted. PL-00 ddress does not match The address value returned in the data packet from the PL is incorrect. PL-00 ifferent function code received from PL The function code returned in the data packet from the PL is incorrect. PL-0 ata size does not match There are an incorrect number of bytes found in the data packet returned from the PL. PL-0 Invalid value in function code There is an invalid value in the function code. PL-01 Invalid command sent to PL There was an invalid command sent to the PL that wasn t recognized by the PL. PL-01 ENQ received from PL If the data packet does not include a negative acknowledgement (NK - 0x1 value) in the defined packet field, then an enquiry (ENQ) control code error will be displayed. PL-01 Transaction I does not match This error will be displayed if after checking the Transaction I ytes in the data packet, there is no match to what was requested. PL-01 %evice% No device found PL device designated as %evice% could not be found. PL-01 ata byte communication error 0 byte of data is recieved PL-01 Out of address range The touch panel requested a file number larger than. PL-01 Panel communication timeout The server panel did not respond when using the Panel Pass Through. PL-01 Found in parity error by hardware n error detected in the PL memory. PL-00 an t open serial port annot open the Serial Port. If this error shows on the panel, it indicates a hardware problem. PL-01 PL number does not match The PL number does not match the PL number configured. PL-0 an t reset Unable to reset the data communication bit. PL-0 able not connected properly ommunication cable incorrectly installed. -more Touch Panel Error ode Table continued on the next page E-USER-M Hardware User Manual, 1st Ed. Rev. F -

6 ppendix - Panel and PL Error ode Tables more Touch Panel Error ode Table (cont d) -more Touch Panel Error ode Table (cont d) Error ode Error Message ause PL-0 annot detect other devices on network The panel is not communicating with other devices on the network. PL-0 Panel not in polling list PL-0 PL connection timeout timeout occured after sending a request to the PL. PL-0 Memory type incorrect PL-0 PL failed to respond The PL failed to respond after sending a request to the PL. PL-0 MemVer ERR HMI x PLy When connected to a o-more PL the PL memory version must match the -more project PL memory version. Make sure that the PL project does not write into the memory version address. PL- Omron Ethernet Error n error code specific to Omron Ethernet with a Value of XXXX has been returned from the PL. See the explanation for error code PL- proceeding the Omron S/J FINS Ethernet error code tables. PL- Error code 0xaaaaaaaa returned from PL llen-radley EtherNET/IP specific. Encapsulation Error. See the explanation for error code PL- proceeding the llen- radley EtherNet/IP error code tables. PL- Error code 0xaaaaaaaa returned from PL llen-radley EtherNET/IP specific. IP Error. See the explanation for error code PL- proceeding the llen- radley EtherNet/IP error code tables. PL- Error code 0xaaaaaaaa returned from PL llen-radley EtherNET/IP specific. Service Packet Error. See the explanation for error code PL- proceeding the llen- radley EtherNet/IP error code tables. PL- Error code XXXX returned from PL n error code with a value of XXXX has been returned from the PL. See the explanation for error code PL- below for irect LOGI and proceeding each set of PL error code tables that use this error code. PL-00 annot write to Serial Port ata cannot write to the Serial port. ata was sent to the PL via the Serial Port. If this error shows on the Panel, it indicates a Hardware Problem. PL-00 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. PL-01 ccess to inaccessible PL memory Request to inaccessible memory from the HMI layer to the PL protocol layer. This error is an indication that there is a problem in the HMI layer. PL-0 annot access by different function code Read/Write/Setit request has been sent to an invalid memory area. This error is an indication that there is a problem in the HMI layer. PL-0 Write request to PL Read Only Memory PL Write request was made to the PL s Read-Only memory area.this error is an indication that there is a problem in the HMI layer or the PL protocol layer. PL-0 ad device-access No device (PL) exists in the server panel or the device name does not match between the server and client when using the Panel Pass Through. PL-0 Protocol does not match The protocol for the device does Not match between the server and client when using the panel pass through. - E-USER-M Hardware User Manual, 1st Ed. Rev. F

7 ppendix - Panel and PL Error ode Tables irectlogi Panel Error ode PL- Explanation The PL- error code is used to show any errors that are generated by the connected PL. The PL- error message includes a four digit hexadecimal value embedded in the message. This value can be looked up in the specific PL s error tables to determine the cause of the error. The possible PL generated error codes for the irectlogi communication protocol are represented by a hexadecimal value as shown in the following message example. irect LOGI Error ode PL- Message Example: Error code 000 returned from PL Panel error code PL- showing a hexadecimal value of 000 indicates an Illegal data value dependent upon the request. PL error. irectlogi K-Sequence Protocol PL Error ode Table Panel Error ode PL- Hex Value 01F The following table lists the errors that can be generated by the irectlogi PL when using the K-Sequence protocol. PL Error odes for irect LOGI K-Sequence escription Error setting value. Error in key mode - Set switch on PL PU to Term Password protected. NOTE: The following errors can be generated from the designated PL, are monitored by the -more touch panel, and displayed on the touch panel s screen as a hexadecimal value in panel error code PL- message, if active. Please refer to the PL manufacturer s documentation for additional information. irectlogi irectnet Protocol PL Error odes Only errors as listed in the Touch Panel Error ode Table shown on page - can occur when using the irectlogi irectnet protocol, there are no PL generated errors. irectlogi error code tables continued on the next page E-USER-M Hardware User Manual, 1st Ed. Rev. F -

8 ppendix - Panel and PL Error ode Tables Modbus Protocols Error ode P Explanation The following table lists the errors that can be generated by the Modbus protocols: utomationirect LIK utomationirect irectlogi - Modbus (Koyo) Modicon Modbus RTU Entivity Modbus RTU Panel Error ode P Hex Value 0x0001 0x000 0x000 0x000 NOTE: The following errors can be generated from the designated PL, are monitored by the -more touch panel, and displayed on the touch panel s screen as a hexadecimal value in panel error code PL- message, if active. Please refer to the PL manufacturer s documentation for additional information. Name ILLEGL FUNTION ILLEGL T RESS ILLEGL T VLUE SLVE EVIE FILURE PL Error odes Modbus Protocols Meaning 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 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 0 registers, the PU addresses the first register as 0, and the last one as. If a request is submitted with a starting register address of and a quantity of registers of, then the request will successfully operate (address-wise at least) on registers,,,. If a request is submitted with a starting register of and a quantity of registers of, then the request will fail with Exception code 0x0 Illegal ata ddress since it attempts to operate on registers,,, and 0, and there is no register with address 0. 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. n unrecoverable error occurred while the server (or slave) was attempting to perform the requested action. irectlogi EOM Protocol PL Error odes Only errors as listed in the Touch Panel Error ode Table shown previously in this ppendix can occur when using the irectlogi EOM protocol, there are no PL generated errors. - E-USER-M Hardware User Manual, 1st Ed. Rev. F

9 ppendix - Panel and PL Error ode Tables Productivity Error ode P Panel Error ode P Hex Value 0x0001 0x000 0x000 0x000 NOTE: The following errors can be generated from the designated PL, are monitored by the -more touch panel, and displayed on the touch panel s screen as a hexadecimal value in panel error code PL- message, if active. Please refer to the PL manufacturer s documentation for additional information. PL Error odes for Productivity Meaning 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 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. ddress out of range. heck to make sure that the -more tag and System I match the Productivity Programming Software Tag Name and System I. The project file in the Productivity system and the imported SV into -more must be in sync with each other. 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. n unrecoverable error occurred while the server (or slave) was attempting to perform the requested action E-USER-M Hardware User Manual, 1st Ed. Rev. F -

10 ppendix - Panel and PL Error ode Tables utomationirect o-more Error odes PL Errors for o-more Error ode escription Resolution 0x01 Unknown ommand Should only occur if message has been corrupted or protocol version is mismatched. heck versions and update appropriately. If versions are correct, check cabling, routing and switches for bad packets. 0x0 Out of Sessions Too many devices connected to the PU. Reduce number of devices connected. 0x0 Illegal Operation Occurs when permission level is not sufficient for the operation performed by the panel. Increase the permission level to correct the problem. 0x0 Invalid Session Session number does match for sending device. Re-establish connection by power cycling or sending updated project. 0x0 Out of Range Invalid address exists. Ensure that address range is expanded and load configuration to the PU. 0x0 Invalid rgument Occurs when message cannot be parsed correctly. ould occur from noise or faulty wiring. 0x0 Program Update ctive Wait until program update is complete. 0x0 No Token Occurs when client attempts to update the project without first acquiring the program update token. 0x0 Program Update Inhibited Occurs when client attempts to update the project while ST1 is true. This allows the customer to programmatically prevent the project from being updated. 0x0 System onfiguration Update ctive Wait until System onfiguration update is complete to continue communications. 0x0 Invalid Mode Ensure that the switch on the PU is in Term mode. 0x0 Mode hange ctive Occurs when a PL mode change is attempted while a mode change is in progress. In some cases it takes several scans for a mode change. 0x0 Mode Locked Occurs when mode change is attempted and keyswitch is not in Term. 0x0E Invalid Password Enter o-more password in Password field of -more Panel Manager for this device. 0x0F Resource Locked Occurs when trying to update a tag that is forced. Force must be removed in order to update the tag. 0x0 oc Update ctive Occurs when someone attempts to access the documentation file while it is being written back to ROM. 0x0 Invalid river Occurs when attempting to read driver data from a driver that doesn t exist. 0x01 Invalid river ata Occurs when attempting to read a driver data type that isn t valid. 0x01 Shared RM write failed Occurs when attempting to read or write to a module s shared RM and it fails. Usually occurs when the module has gone bad. - E-USER-M Hardware User Manual, 1st Ed. Rev. F

11 ppendix - Panel and PL Error ode Tables llen-radley Panel Error ode PL- Explanation The PL- error code is used to show any errors that are generated by the connected PL. The PL- error message includes a four digit hexadecimal value embedded in the message. This value can be looked up in the specific PL s error tables to determine the cause of the error. The possible PL generated error codes for the llen-radley F1 and H 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 PL error to be displayed in this value. llen-radley Error ode PL- Message Example: F1 and H Protocol Error ode PL- reakdown 1-bit Word Remote - bits Local 0- bits EXT STS byte PL- Error ode Message isplayed Hexadecimal Value F 0 1 Example of an EXT STS error for a Type mismatch. hex Error code 0 returned from PL F1 and H Protocol Multiple Error ode Examples Example 1 Example Example Remote - bits F x x x 1 x x x F x x x Local 0- bits x 0 x x x 1 x x x 1 x x EXT STS byte x x 0 x x 0 0 x x 0 = = = Error PL- Value isplayed F F 1 0 Panel error code PL- showing a hexadecimal value of 0 indicates Illegal command or format. and Station is offline. PL errors E-USER-M Hardware User Manual, 1st Ed. Rev. F -

12 ppendix - Panel and PL Error ode Tables llen-radley F1 & H Protocols PL Error ode Tables The following PL error code tables cover possible errors that are detected by the panel from llen-radley PLs using the F1 and H protocols. F1 includes full and half duplex communications for the MicroLogix 00, 10. 0, 0, 100, SL /0, /0, /0, ontrollogix, ompactlogix and FlexLogix, and full duplex communications for the PL. H includes all MicroLogix and SL00 PL s and any communication connection using an llen-radley I device using the H protocol. NOTE: The following errors can be generated from the designated PL, are monitored by the -more touch panel, and displayed on the touch panel s screen as a hexadecimal value in panel error code PL- message, if active. Please refer to the PL manufacturer s documentation for additional information. PL Errors for llen-radley F1 and H Protocols, Local STS Errors (0- bits) Panel Error ode PL- Hex Value escription 0x0 Success; no error. 0x1 ST node is out of buffer space. 0x annot guarantee delivery; link layer. (The remote node specified does not K command.) 0x uplicate token holder detected. 0x Local port is disconnected. 0x pplication layer timed out waiting for response. 0x uplicate node detected. 0x Station is offline. 0x Hardware fault. PL Errors for llen-radley F1 and H Protocols, Remote STS Errors (- bits) Panel Error ode PL- Hex Value escription 0x0 Success; no error. 0x Illegal command or format. 0x0 Host has a problem and will not communicate. 0x0 Remote node host is missing, disconnected, or shut down. 0x0 Host could not complete function due to hardware fault. 0x0 ddressing problem or memory protect rungs. 0x0 Function not allowed due to command protection selection. 0x0 Processor is in Program Mode. 0x0 ompatibility mode file missing or communication zone problem. 0x0 Remote node cannot buffer command. 0x0 Wait K (1 K buffer full). 0x0 Remote node problem due to download. 0x0 Wait K (1 K buffer full). 0x0 not used 0xE0 not used 0xF0 Error code in the EXT STS byte. See the error code table on the next page. (PL generated error codes for the llen-radley F1 protocol continued on the next page.) - E-USER-M Hardware User Manual, 1st Ed. Rev. F

13 ppendix - Panel and PL Error ode Tables llen-radley F1 & H Protocols PL Error ode Tables (cont d) PL Errors for llen-radley F1 and H Protocols, EXT STS ommand ode for F0 ommand Panel Error ode PL- Hex Value escription 0x0 not used 0x1 field has an illegal value. 0x Fewer levels specified in address than minimum for any address. 0x More levels specified in address than system supports. 0x Symbol not found. 0x Symbol is of improper format. 0x ddress does not point to something usable. 0x File is wrong size. 0x annot complete request; situation has changed since start of the command. 0x ata or file size is too large. 0x Transaction size plus word address is too large. 0x ccess denied; improper privilege. 0x ondition cannot be generated; resource is not available. 0x ondition already exists; resource is readily available. 0xE ommand cannot be executed. 0xF Histogram overflow. 0x No access. 0x Illegal data type. 0x1 Invalid parameter or invalid data. 0x1 ddress reference exists to deleted area. 0x1 ommand execution failure for unknown reason; possible PL histogram overflow. 0x1 ata conversion error. 0x1 Scanner not able to communicate with rack adapter. 0x1 Type mismatch. 0x1 module response was not valid. 0x1 uplicated label. 0x Remote rack fault. 0x Timeout. 0x Unknown error. 0x1 File is open; another node owns it. 0x1 nother node is the program owner. 0x1 isk File is write protectid or otherwise unavailable 0x1 isk File is being used by another application. Update not performed (offline only). 0x1E ata table element protection violation. 0x1F Temporary internal problem E-USER-M Hardware User Manual, 1st Ed. Rev. F -

14 ppendix - Panel and PL Error ode Tables llen-radley EtherNet/IP Protocol Panel Error ode PL-, and Explanation The PL-, PL-, and PL- error codes are used to show any errors that are generated by the connected PL. These error messages include an eight digit hexadecimal value displayed embedded in the message. This value can be looked up in the specific PL s error tables to determine the cause of the error. The possible PL generated error codes for the llen-radley EtherNet/IP communication protocol is represented by a hexadecimal value as shown in the following message example. llen-radley Error ode PL-,, Message Example: Error code returned from PL Panel error code PL- showing a hexadecimal value of indicates an The target received a message of invalid length. PL error. -1 E-USER-M Hardware User Manual, 1st Ed. Rev. F

15 ppendix - Panel and PL Error ode Tables llen-radley EtherNet/IP Protocol PL Error ode Tables ontrollogix, ompactlogix, & FlexLogix The following PL error code tables cover possible errors that are detected by the panel from llen-radley PLs using the EtherNet/IP protocol. This includes all ontrollogix, ompactlogix and FlexLogix PLs. NOTE: The following errors can be generated from the designated PL, are monitored by the -more touch panel, and displayed on the touch panel s screen as a hexadecimal value in panel error code PL- message, if active. Please refer to the PL manufacturer s documentation for additional information. PL Errors for llen-radley EtherNet/IP Protocol Encapsulation Errors (Error code 0xaaaaaaaa returned from the PL.) Panel Error ode PL- Hex Value escription 0x The sender issued an invalid or unsupported encapsulation command. 0x Insufficient memory resources in the receiver to handle the command. You can get this error if the -NET-ENI cannot connect to the PL serially. 0x Poorly formed or incorrect data in the data portion of the encapsulation message. 0x x Reserved for legacy (Rockwell utomation). 0x n orginator used an invalid session handle when sending an encapsulation message to the target. 0x The target received a message of invalid length. 0x x Reserved for legacy (Rockwell utomation). 0x Unsupported encapsulation protocol revision. 0x000000a - 0x0000ffff Reserved for future expansion. Panel Error ode PL- Hex Value 0x00 0x0 0x0 0x0 0x0 0x0 0x01 0x01 0x0 0x0 0x0 0x0 PL Errors for llen-radley EtherNet/IP Protocol IP Errors (Error code 0xaaaaaaaa returned from the PL.) escription onnection Manager: onnection in Use or uplicate Forward Open. onnection Manager: Transport lass and Trigger combination not supported. onnection Manager: Ownership onflict. onnection Manager: onnection not found at target application. onnection Manager: Invalid connection type (problem with type or priority). onnection Manager: Invalid connection size. onnection Manager: evice not configured. onnection Manager: RPI not supported. ould also be problem with inactivity timeout. onnection Manager: onnection Manager cannot support any more connections. onnection Manager: Either the vendor I or the Product ode in the key segment did not match the device. onnection Manager: Product Type in the key segment did not match the device. onnection Manager: Major or minor revision information in the key segment did not match the device. (PL generated error codes for the llen-radley EtherNet/IP protocol for ontrollogix, ompactlogix, and FlexLogix continued on the next page.) E-USER-M Hardware User Manual, 1st Ed. Rev. F -1

16 ppendix - Panel and PL Error ode Tables llen-radley EtherNet/IP Protocol PL Error ode Tables ontrollogix, ompactlogix, & FlexLogix (cont d) Panel Error ode PL- Hex Value 0x0 0x0 0x0 0x0a 0x0b 0x00 0x00 0x00 0x00 0x00 0x001 0x00 0x00 0x00 0x0 0x01 0x01 0x01 0x01 0x01 0x01 0x01a 0x01b 0x01c 0x01d 0x01e 0x01f 0x00-0x0ff 0x x x x x x00000 PL Errors for llen-radley EtherNet/IP Protocol IP Errors (Error code 0xaaaaaaaa returned from the PL.) escription onnection Manager: Invalid connection point. onnection Manager: Invalid configuration format. onnection Manager: onnection request fails since there is no controlling connection currently open. onnection Manager: Target application cannot support any more connections. onnection Manager: RPI is smaller than the Production Inhibit Time. onnection Manager: onnection cannot be closed since the connection has timed out. onnection Manager: Unconnected Send timed out waiting for a response. onnection Manager: Parameter error in Unconnected send service. onnection Manager: Message too large for Unconnected message service. onnection Manager: Unconnected acknowledge without reply. onnection Manager: No buffer memory available. onnection Manager: Network andwidth not available for data. onnection Manager: No Tag filters available. onnection Manager: Not configured to send real-time data. onnection Manager: Port specified in Port segment not available. onnection Manager: Link address specified in port segment not available. onnection Manager: invalid segment type or segment value in path. onnection Manager: Path and onnection not equal in close. onnection Manager: Ether Segment not present or Encoded Value in Network Segment is invalid. onnection Manager: Link address to self invalid. onnection Manager: Resources on Secondary unavailable. onnection Manager: onnection already established. onnection Manager: irect connection already established. onnection Manager: Miscellaneous. onnection Manager: Redundant connection mismatch. onnection Manager: No more consumer resources available in the producing module. onnection Manager: No connection resources exist for target path. onnection Manager: Vendor specific. Resource unavailable: onnection Manager resources are unavailable to handle service request. Invalid parameter value. Path segment error: The path segment identifier or the segment syntax was not understood by the 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. Partial transfer: Only part of the expected data was transferred. onnection lost: The messaging connection was lost. (PL generated error codes for the llen-radley EtherNet/IP protocol for ontrollogix, ompactlogix, and FlexLogix continued on the next page.) -1 E-USER-M Hardware User Manual, 1st Ed. Rev. F

17 ppendix - Panel and PL Error ode Tables llen-radley EtherNet/IP Protocol PL Error ode Tables ontrollogix, ompactlogix, & FlexLogix (cont d) Panel Error ode PL- Hex Value 0x x x0a0000 0x0b0000 0x0c0000 0x0d0000 0x0e0000 0x0f0000 0x0000 0x1000 0x000 0x000 0x000 0x x000 0x000 0x000 0x000 0x1a0000 0x1b0000 0x1c0000 0x1d0000 0x1e0000 0x1f0000 0x x000 0x0000 PL Errors for llen-radley EtherNet/IP Protocol IP Errors (Error code 0xaaaaaaaa returned from the PL.) escription Service not supported: The requested service was not implemented or was not defined for this Object lass/instance. Invalid attribute value: Invalid attribute data detected. ttribute list error: n attribute in the Get_ttribute_List or Set_ttribute_List response has a non-zero status. lready in requested mode/state: The object is already in the mode/state being requested by the service. Object state conflict: The object cannot perform the requested service in its current mode/state. Object already exists: The requested instance of object to be created already exists. ttribute not settable: request to modify non-modifiable attribute was received. Privilege violation: permission/privilege check failed. evice 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 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 byte value to a REL data type ( byte). Not enough data: The service did not supply enough data to perform the specified operation. ttribute not supported: The attribute specified in the request is not supported. Too much data: The service supplied more data than was expected. Object does not exist: The object specified does not exist in the device. Service fragmentation sequence not in progress: The fragmentation sequence for this service is not currently active for this data. No stored attribute data: The attribute data of this object was no saved prior to the requested service. Store operation failure: The attribute data of this object was not saved due to a failure during the attempt. Routing failure, request packet too large: The service request packet was too large for transmission on a network in the path to the destination. Routing failure, response packet too large: The service reponse packet was too large for transmission on a 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. Invalid attribute value list: The service is returning the list of attributes supplied with status information for those attributes that were invalid. Embedded service error: See Service Packet error list (PL- Error codes) below: Vendor specific error: vendor specific error has been encountered. This occurs when none of the specified errors relate to the error in the device. Invalid parameter: parameter associated with the request was invalid. This code is used when a parameter does meet the requirements defined in an pplication Object specification. Write-once value or medium already written: n 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. Invalid Reply Received: n invalid reply is received (example: service code sent doesn t match service code received.). (PL generated error codes for the llen-radley EtherNet/IP protocol for ontrollogix, ompactlogix and FlexLogix continued on the next page.) E-USER-M Hardware User Manual, 1st Ed. Rev. F -1

18 ppendix - Panel and PL Error ode Tables llen-radley EtherNet/IP Protocol PL Error ode Tables ontrollogix, ompactlogix, & FlexLogix (cont d) Panel Error ode PL- Hex Value 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0xa0000 0xb0000-0xcf0000 0xd xff0000 Panel Error ode PL- Hex Value 0x x x x0a0000 0x000 0x1c0000 0x0000 0xff01 0xff01 0xff01 PL Errors for llen-radley EtherNet/IP Protocol IP Errors (Error code 0xaaaaaaaa returned from the PL.) escription Reserved by IP for future extensions. Reserved by IP for future extensions. Key failure in path: The key segment was included as the first segment in the path does not match the destination module. The object specific status shall indicate which part of the key check failed. 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. Unexpected attribute in list: n attempt was made to set an attribute that is not able to be set at this time. Invalid Member I: The Member I specified in the request does not exist in the specified lass/instance/ ttribute. Member not settable: request to modify a non-modifiable member was received. Group only server general failure: This error code may only be reported by evicenet group only servers with K or less code space and only in place of Service not supported, ttribute not supported and ttribute not settable. Reserved by IP for future extensions. Reserved for Object lass and service errors: This range of error codes is to be used to indicate Object lass specific errors. Use of this range should only be used when errors in this table don t accurately reflect the error encountered. PL Errors for llen-radley EtherNet/IP Protocol Service Packet Errors (Error code 0xaaaaaaaa returned from the PL.) escription 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 PL. The particular item referenced (usually instance) could not be found. The amount of data requested would not fit into the response buffer. Partial data transfer has occurred. n error has occurred trying to process one of the attributes. Not enough command data/parameters were supplied in the command to execute the service requested. n insufficient number of attributes were provided compared to the attribute count. The tag name length specified did not match what was in the message. 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. The beginning offset was beyond the end of the template. -1 E-USER-M Hardware User Manual, 1st Ed. Rev. F

19 ppendix - Panel and PL Error ode Tables llen-radley EtherNet/IP Protocol PL Error ode Tables The following PL error code tables cover possible errors that are detected by the panel from llen-radley PLs using the EtherNet/IP protocol. This includes MicroLogix 10, 0 & SL /0, both using their native Ethernet port, and MicroLogix 00, 10, 0, 0, 100, SL /0, /0 and /0 using an llen-radly ENI dapter. NOTE: The following errors can be generated from the designated PL, are monitored by the -more touch panel, and displayed on the touch panel s screen as a hexadecimal value in panel error code PL- message, if active. Please refer to the PL manufacturer s documentation for additional information. PL Errors for llen-radley EtherNet/IP Protocol Encapsulation Errors (Error code 0xaaaaaaaa returned from the PL.) Panel Error ode PL- Hex Value escription 0x The sender issued an invalid or unsupported encapsulation command. 0x Insufficient memory resources in the receiver to handle the command. You can get this error if the -NET-ENI cannot connect to the PL serially. 0x Poorly formed or incorrect data in the data portion of the encapsulation message. 0x x Reserved for legacy (Rockwell utomation). 0x n orginator used an invalid session handle when sending an encapsulation message to the target. 0x The target received a message of invalid length. 0x x Reserved for legacy (Rockwell utomation). 0x Unsupported encapsulation protocol revision. 0x000000a - 0x0000ffff Reserved for future expansion. Panel Error ode PL- Hex Value 0x00 0x0 0x0 0x0 0x0 0x0 0x01 0x01 PL Errors for llen-radley EtherNet/IP Protocol IP Errors (Error code 0xaabbbb returned from the PL.) escription onnection Manager: onnection in Use or uplicate Forward Open. onnection Manager: Transport lass and Trigger combination not supported. onnection Manager: Ownership onflict. onnection Manager: onnection not found at target application. onnection Manager: Invalid connection type (problem with type or priority). onnection Manager: Invalid connection size. onnection Manager: evice not configured. onnection Manager: RPI not supported. ould also be problem with inactivity timeout. (PL generated error codes for the llen-radley EtherNet/IP protocol continued on the next page.) E-USER-M Hardware User Manual, 1st Ed. Rev. F -1

20 ppendix - Panel and PL Error ode Tables llen-radley EtherNet/IP Protocol PL Error ode Tables (cont d) Panel Error ode PL- Hex Value 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0a 0x0b 0x00 0x00 0x00 0x00 0x00 0x001 0x00 0x00 0x00 0x0 0x01 0x01 0x01 0x01 0x01 0x01 0x01a 0x01b 0x01c 0x01d 0x01e 0x01f 0x00-0x0ff PL Errors for llen-radley EtherNet/IP Protocol IP Errors (Error code 0xaabbbb returned from the PL.) escription onnection Manager: onnection Manager cannot support any more connections. onnection Manager: Either the vendor I or the Product ode in the key segment did not match the device. onnection Manager: Product Type in the key segment did not match the device. onnection Manager: Major or minor revision information in the key segment did not match the device. onnection Manager: Invalid connection point. onnection Manager: Invalid configuration format. onnection Manager: onnection request fails since there is no controlling connection currently open. onnection Manager: Target application cannot support any more connections. onnection Manager: RPI is smaller than the Production Inhibit Time. onnection Manager: onnection cannot be closed since the connection has timed out. onnection Manager: Unconnected Send timed out waiting for a response. onnection Manager: Parameter error in Unconnected send service. onnection Manager: Message too large for Unconnected message service. onnection Manager: Unconnected acknowledge without reply. onnection Manager: No buffer memory available. onnection Manager: Network andwidth not available for data. onnection Manager: No Tag filters available. onnection Manager: Not configured to send real-time data. onnection Manager: Port specified in Port segment not available. onnection Manager: Link address specified in port segment not available. onnection Manager: invalid segment type or segment value in path. onnection Manager: Path and onnection not equal in close. onnection Manager: Ether Segment not present or Encoded Value in Network Segment is invalid. onnection Manager: Link address to self invalid. onnection Manager: Resources on Secondary unavailable. onnection Manager: onnection already established. onnection Manager: irect connection already established. onnection Manager: Miscellaneous. onnection Manager: Redundant connection mismatch. onnection Manager: No more consumer resources available in the producing module. onnection Manager: No connection resources exist for target path. onnection Manager: Vendor specific. (PL generated error codes for the llen-radley EtherNet/IP protocol continued on the next page.) -1 E-USER-M Hardware User Manual, 1st Ed. Rev. F

21 ppendix - Panel and PL Error ode Tables llen-radley EtherNet/IP Protocol PL Error ode Tables (cont d) Panel Error ode PL- Hex Value 0x x x x x x x x x0a0000 0x0b0000 0x0c0000 0x0d0000 0x0e0000 0x0f0000 0x0000 0x1000 0x000 0x000 0x000 0x x000 0x000 0x000 0x000 0x1a0000 0x1b0000 0x1c0000 PL Errors for llen-radley EtherNet/IP Protocol IP Errors (Error code 0xaabbbb returned from the PL.) escription Resource unavailable: onnection Manager resources are unavailable to handle service request. Invalid parameter value. Path segment error: The path segment identifier or the segment syntax was not understood by the 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. Partial transfer: Only part of the expected data was transferred. onnection lost: The messaging connection was lost. Service not supported: The requested service was not implemented or was not defined for this Object lass/instance. Invalid attribute value: Invalid attribute data detected. ttribute list error: n attribute in the Get_ttribute_List or Set_ttribute_List response has a non-zero status. lready in requested mode/state: The object is already in the mode/state being requested by the service. Object state conflict: The object cannot perform the requested service in its current mode/state. Object already exists: The requested instance of object to be created already exists. ttribute not settable: request to modify non-modifiable attribute was received. Privilege violation: permission/privilege check failed. evice 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 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 byte value to a REL data type ( byte). Not enough data: The service did not supply enough data to perform the specified operation. ttribute not supported: The attribute specified in the request is not supported. Too much data: The service supplied more data than was expected. Object does not exist: The object specified does not exist in the device. Service fragmentation sequence not in progress: The fragmentation sequence for this service is not currently active for this data. No stored attribute data: The attribute data of this object was no saved prior to the requested service. Store operation failure: The attribute data of this object was not saved due to a failure during the attempt. Routing failure, request packet too large: The service request packet was too large for transmission on a network in the path to the destination. Routing failure, response packet too large: The service reponse packet was too large for transmission on a 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. (PL generated error codes for the llen-radley EtherNet/IP protocol continued on the next page.) E-USER-M Hardware User Manual, 1st Ed. Rev. F -1

22 ppendix - Panel and PL Error ode Tables llen-radley EtherNet/IP Protocol PL Error ode Tables (cont d) Panel Error ode PL- Hex Value 0x1d0000 0x1e0000 0x1f0000 0x x000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0xa0000 0xb0000-0xcf0000 0xd xff0000 PL Errors for llen-radley EtherNet/IP Protocol IP Errors (Error code 0xaabbbb returned from the PL.) escription Invalid attribute value list: The service is returning the list of attributes supplied with status information for those attributes that were invalid. Embedded service error: See Service Packet error list (PL- Error codes) below: Vendor specific error: vendor specific error has been encountered. This occurs when none of the specified errors relate to the error in the device. Invalid parameter: parameter associated with the request was invalid. This code is used when a parameter does meet the requirements defined in an pplication Object specification. Write-once value or medium already written: n 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. Invalid Reply Received: n invalid reply is received (example: service code sent doesn t match service code received.). Reserved by IP for future extensions. Reserved by IP for future extensions. Key failure in path: The key segment was included as the first segment in the path does not match the destination module. The object specific status shall indicate which part of the key check failed. 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. Unexpected attribute in list: n attempt was made to set an attribute that is not able to be set at this time. Invalid Member I: The Member I specified in the request does not exist in the specified lass/instance/ ttribute. Member not settable: request to modify a non-modifiable member was received. Group only server general failure: This error code may only be reported by evicenet group only servers with K or less code space and only in place of Service not supported, ttribute not supported and ttribute not settable. Reserved by IP for future extensions. Reserved for Object lass and service errors: This range of error codes is to be used to indicate Object lass specific errors. Use of this range should only be used when errors in this table don t accurately reflect the error encountered. (PL generated error codes for the llen-radley EtherNet/IP protocol continued on the next page.) -0 E-USER-M Hardware User Manual, 1st Ed. Rev. F

23 ppendix - Panel and PL Error ode Tables llen-radley EtherNet/IP Protocol PL Error ode Tables (cont d) PL Errors for llen-radley EtherNet/IP Protocol Service Packet Errors (Error code 0xaabbbb returned from the PL.) Panel Error ode PL- Hex Value escription 0x0000 ST Node is out of buffer space. 0x00000 annot guarantee delivery; link layer (The remote node specified does not K command). 0x00000 uplicate token holder detected. 0x00000 Local port is disconnected. 0x00000 pplication layer timed out waiting for response. 0x00000 uplicate node detected. 0x00000 Station is offline. 0x00000 Hardware fault. 0x0000 Illegal command or format. Typical error received from PL when addressed requested to the PL does not exist. Usually occurs if memory map has not been expanded in PL to the range requested from panel. 0x00000 Host has a problem and will not communicate. 0x00000 Remote node host is missing, disconnected, or shut down. 0x00000 Host could not complete function due to hardware fault. 0x00000 ddressing problem or memory protected rungs. 0x00000 Function not allowed due to command protection selection. 0x00000 Processor is in Program Mode. 0x00000 ompatibility mode file missing or communication zone problem. 0x00000 Remote node cannot buffer command. 0x00000 Wait K (1 K buffer full). 0x00000 Not used. 0x00000 Not used. 0x00000 Error code in the EXT STS byte. See the error code table below. 0xE00000 Fewer levels specified in address than minimum for any address. 0xF0000 More levels specified in address than system supports. 0xF0000 Symbol not found. 0xF0000 Symbol is of improper format. 0xF0000 ddress does not point to something usable. 0xF0000 File is wrong size. 0xF0000 annot complete request, situation has changed since start of the command. 0xF0000 ata or file size is too large. 0xF0000 Transaction size plus word address is too large. 0xF0000 ccess denied; improper privilege. This will occur if data file is set to constant or protected. 0xF0000 ondition cannot be generated; resource is not available. 0xF0000 ondition already exists; resource is readily available. (PL generated error codes for the llen-radley EtherNet/IP protocol continued on the next page.) E-USER-M Hardware User Manual, 1st Ed. Rev. F -1