Appendix. Panel & PLC. Error Code Tables. In this Appendix...

Transcription

1 Panel & PL Error ode Tables ppendix In this ppendix... Introduction more Micro-Graphic Panel Error ode Table... - Modbus Protocols Error ode P Explanation... - Productivity000 Error ode P Explanation... - o-more Error ode P Explanation... - irectlogi Error ode P Explanation... - irectlogi K-Sequence PL Error ode Table... - irectlogi irectnet PL Error odes... - llen-radley Error ode P Explanation... - llen-radley F1 Protocol PL Error ode Tables... - llen-radley H Protocol PL Error ode Tables... - GE Error ode P Explanation GE SNPX Protocol PL Error ode Tables Mitsubishi FX Protocol PL Error odes... - Mitsubishi Q / Qn Series PL Error odes... - Omron Error ode P Explanation... - Omron Host Link Protocol PL Error ode Table... - Omron FINS Protocol PL Error ode Table... - Siemens Error ode P Explanation Siemens PPI Protocol PL Error ode Table... -1

2 ppendix : Panel & PL Error ode Tables Introduction The -more Micro-Graphic panels are capable of communicating over RS, RS and RS serial networks. They communicate with Productivity Series P s, o-more PL s, LIK PL s, all controllers in the irect LOGI family of PLs utilizing various protocols, and certain rd party PLs. For a complete list of the supported PLs and protocols, see the PL rivers table in hapter : PL ommunications. s with any network communications, errors may occur. To simplify identification of the possible cause of the error, we have provided tables listing these errors. If a -more Micro- Graphic panel communications error, or other related data exchange error does occur, the error message will appear across the top of the display screen as shown in the example below. complete table of the panel generated errors, with their respective error codes, error messages, and the possible causes of the error follows. The -more Micro-Graphic panel also monitors any errors that are generated by the PL that is 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. n explanation of how the specific PL error is identified in the panel error code P is shown preceeding the specific manufacturer s PL error tables. How the hexadecimal error code value is interpreted is slightly different between manufacturers, so it is important to check the explanation at the beginning of each manufacturer s tables. Since these errors are generated by the PL, refer to the PL manufacturers documentation for further explanation. If you have difficulty determining the cause of the error, please refer to hapter : Troubleshooting for some troubleshooting tips or contact our technical support group at more Micro-Graphic Panel Error Example P001: PL OM Time Out Start Stop - E1-TL-M Hardware User Manual, nd Ed. Rev., 0/1

3 ppendix : Panel & PL Error ode Tables -more Micro-Graphic 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. -more Micro-Graphic Panel Error Table Error ode Error Message ause P001 PL om Time Out timeout occurred after sending a request to the PL. P00 NK Received negative acknowledgement (NK) control code has been generated during a read/write request. P00 EOT Received n end of transmission has been sent by PL in response to a read/write/setbit request. P00 STX is Not Found Start of Text (STX) control code was not found in the data packet received from the PL. P00 ETX/ET NotFound 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. P00 LR Not Match 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. P00 R Not Match 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. P00 ddress NotMatch The address value returned in the data packet from the PL is incorrect. P00 Re.INV.FUN.ode The function code returned in the data packet from the PL is incorrect. P0 atasizenotmatch There are an incorrect number of bytes found in the data packet returned from the PL. P0 INV.Val.FUN.ode There is an invalid value in the function code. P01 INVLI OMMN There was an invalid command sent to the PL that wasn t recognized by the PL. P01 ENQ Received 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. P01 TransI NotMatch This error will be displayed if after checking the Transaction I yte in the data packet, there is no match to what was requested. P01 evice Not Found PL device designated as evice could not be found. P01 atayte om.err The data part of the packet received contains 0 bytes of data. P01 Out of dd.range The touch panel requested a file number larger than. P01 Parity Error Parity error occurred. P00 an topens.port an t open serial port P01 PL# Not Match PL Number does not match P0 an t Reset Unable to reset the ata ommunications it P0 Not onnected able not connected properly P0 No Other ev. annot detect other devices P0 PollingListErr. Panel not in polling list P0 PL onn. Time Out PL onnection Time Out P0 Memory Error Memory Type Incorrect P0 No Response PL failed to Respond: %PL Node#%?? -more Micro-Graphic Panel Error ode Table continues on the next page E1-TL-M Hardware User Manual, nd Ed. Rev., 0/1 -

4 ppendix : Panel & PL Error ode Tables more Micro-Graphic Panel Error ode Table (cont d) -more Micro-Graphic Panel Error Table (cont d) Error ode Error Message ause P* Errode Received -> Recv.Err ode XXXX PL generated error code with a hexadecimal value of XXXX has been returned from the PL. * See the explanation for error code P proceeding each set of PL error code tables. P00 an twrites.port ata cannot be written 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. P00 R.uff.MEM Full There was an error while allocating memory for the read buffer. When this error is displayed, a memory leak may have occurred. P01 INV.PL ddress 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. P0 P0 INV.FUN.ode 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. 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 WRT.PL.ReadOnly 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. NOTE: The following errors can be generated from the designated PL, are monitored by the -more Micro- Graphic panel, and displayed on the panel s screen as a hexadecimal value in panel error code P, if active. 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. - E1-TL-M Hardware User Manual, nd Ed. Rev., 0/1

5 ppendix : Panel & PL Error ode Tables Productivity000 Error ode P Explanation 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 Productivity000 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 Micro Graphic tag and System I match the Productivity000 Programming Software Tag Name and System I. The project file in the Productivity000 system and the imported SV into -more Micro Graphic 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 E1-TL-M Hardware User Manual, nd Ed. Rev., 0/1 -

6 ppendix : Panel & PL Error ode Tables o-more Error ode P Explanation NOTE: The following errors can be generated from the designated PL, are monitored by the -more Micro- Graphic panel, and displayed on the panel s screen as a hexadecimal value in panel error code P, if active. PL Errors for o-more Error ode escription Resolution 0x01 Unknown ommand Occurs when a 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 the 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 0x0 Invalid Session Out of Range Session number does match for sending device. Re-establish connection by power cycling or sending updated project. 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. Wait until program update is complete. 0x0 Program Update ctive 0x0 No Token Occurs when client attempts to update the project without first acquiring the program update token. Program Update 0x0 Occurs when client attempts to update the project while ST1 is true. This allows the customer Inhibited to use the program to prevent the project from being updated. System onfiguration 0x0 Wait until System onfiguration update is complete to continue communications. Update ctive 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 Micro 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. Shared RM write 0x01 Occurs when attempting to read or write to a module s shared RM and it fails. Usually occurs failed when the module has gone bad. - E1-TL-M Hardware User Manual, nd Ed. Rev., 0/1

7 ppendix : Panel & PL Error ode Tables irectlogi Error ode P Explanation The P error code is used to show any errors that are generated by the connected PL. The P error message includes a four digit hexadecimal value displayed at the end of the message. This value can be found in the specific PL s error tables to determine the cause of the error. The possible PL generated error codes for the various irect LOGI communication protocols breakdown into a four digit hexadecimal value. irectlogi K-Sequence PL Error ode Table The following table lists the errors that can be generated by the irectlogi PL when using the K-Sequence protocol. Panel Error ode P Hex Value 01F irect LOGI PL Error ode isplayed Example: P: Recv. Err ode 000 Start NOTE: The following errors can be generated from the designated PL, are monitored by the -more Micro- Graphic panel, and displayed on the panel s screen as a hexadecimal value in panel error code P, if active. Please refer to the PL users manual for additional information. irectlogi irectnet PL Error odes There are no PL generated errors that occur when using the irectnet protocol. Stop PL Error odes for irect LOGI K-Sequence Error setting value. Error in key mode. Password protected. escription E1-TL-M Hardware User Manual, nd Ed. Rev., 0/1 -

8 ppendix : Panel & PL Error ode Tables llen-radley Error ode P Explanation The P error code is used to show any errors that are generated by the connected PL. The P error message includes a four digit hexadecimal value displayed at the end of 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 protocol is 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. 1-bit Word F1 Protocol Error ode P reakdown Remote - bits Local 0- bits EXT STS byte P Error ode Message isplayed Hexadecimal Value F 0 1 Example of an EXT STS error for a Type mismatch. hex llen-radley PL Error ode isplayed Example Error Recieved = P: Recv. Err ode 00 Remote = 0x000 = Remote node host is missing, disconnected or shut down. Local - 0x000 = annot Guarantee elivery; Link Layer. The remote node specified does not K ommand EXT STS = 0000 = None P: Recv. Err ode F01 Start Stop F1 Protocol Multiple Error ode Examples Example 1 Example Example F x x x 1 x x x F x x x x 0 x x x 1 x x x 1 x x x x 0 x x 0 0 x x 0 = = = F F 1 0 Remote - bits Local 0- bits EXT STS byte Error P Value isplayed Remote - bits Local 0- bits EXT STS byte Error P Value isplayed x x x + x x x + x x 0 0 = E1-TL-M Hardware User Manual, nd Ed. Rev., 0/1

9 ppendix : Panel & PL Error ode Tables llen-radley F1 Protocol PL Error ode Tables The following PL error tables cover possible errors that are detected by the panel from llen- radley PLs using the F1 protocol. This includes full and half duplex communications for the MicroLogix 00, , 100 & 100, SL /0, /0, /0, ontrollogix, ompactlogix and FlexLogix, and full duplex communications for the PL. NOTE: The following errors can be generated from the designated PL, are monitored by the -more Micro- Graphic panel, and displayed on the panel s screen as a hexadecimal value in panel error code P, if active. Please refer to the PL users manual for additional information. PL Errors for llen-radley F1 Protocol, Remote STS Errors (- bits) Panel Error ode P 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 Errors for llen-radley F1 Protocol, Local STS Errors (0- bits) Panel Error ode P 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 generated error code for the llen-radley F1 Protocol continue on the next page E1-TL-M Hardware User Manual, nd Ed. Rev., 0/1 -

10 ppendix : Panel & PL Error ode Tables llen-radley F1 Protocol PL Error ode Tables (cont d) PL Errors for llen-radley F1 Protocol, EXT STS ommand ode for F0 ommand Panel Error ode P 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 Reserved 0x1 Reserved 0x1E ata table element protection violation. 0x1F Temporary internal problem. - E1-TL-M Hardware User Manual, nd Ed. Rev., 0/1

11 ppendix : Panel & PL Error ode Tables llen-radley H 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 H protocol. This includes all MicroLogix and SL00 PLs, 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 Micro- Graphic panel, and displayed on the panel s screen as a hexadecimal value in panel error code P, if active. Please refer to the PL users manual for additional information. PL Errors for llen-radley H Protocol, Remote STS Errors (- bits) Panel Error ode P 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 Errors for llen-radley H Protocol, Local STS Errors (0- bits) Panel Error ode P 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 generated error codes for the llen-radley H protocol continue on the next page E1-TL-M Hardware User Manual, nd Ed. Rev., 0/1 -

12 ppendix : Panel & PL Error ode Tables llen-radley H Protocol PL Error ode Tables (cont d) PL Errors for llen-radley H Protocol, EXT STS ommand ode for F0 ommand Panel Error ode P Hex Value escription 0x Insufficient memory module size (0000h is returned). 0x ccess denied; privilege violation. 0x Resource not available or cannot do. 0xE M cannot be executed. 0x1 Invalid parameter. 0x1 Failure during processing. 0x1 uplicate label. 0x1 File open by another node + owner s local node address, 1 byte. 0x1 Program owned by another node + program owner s local node address, 1 byte. -1 E1-TL-M Hardware User Manual, nd Ed. Rev., 0/1

13 ppendix : Panel & PL Error ode Tables GE Error ode P Explanation The P error code is used to show any errors that are generated by the connected PL. The P error message includes a four digit hexadecimal value displayed at the end of 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 GE 0-0, 0-0, Micro 0 and VersaMax Micro SNPX communication protocols breakdown into a four digit hexadecimal value. P: Recv. Err ode 00 Start Stop GE Error ode P Message Example: E1-TL-M Hardware User Manual, nd Ed. Rev., 0/1-1

14 ppendix : Panel & PL Error ode Tables GE SNPX Protocol PL Error ode Tables The following table lists the errors that can be generated by the GE 0-0, 0-0 and VersaMax PL when using the SNPX protocol. NOTE: The following errors can be generated from the designated PL, are monitored by the -more Micro- Graphic panel, and displayed on the panel s screen as a hexadecimal value in panel error code P, if active. Please refer to the PL users manual for additional information. PL Errors for GE SNPX Protocol (Major) Panel Error ode P Hex Value escription No error Successful completion. (This is the expected completion value in the OMMREQ Status Word.) 0x000 Insufficient Privilege. For Series 0-0 PL, the minor error code contains the privilege level required for the service request. 0x000 Protocol Sequence Error. The PU has received a message that is out of order. 0x000 Service Request Error, the minor error code contains the specific error code. 0x000 Illegal Mailbox Type. Service request mailbox type is either undefined or unexpected. 0x000 The PL PU s Service Request Queue is full. The master should retry later. It is recommended that the master wait a minimum of msec before sending another service request. 0x000 SNP OS river 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 returned 0x000 in lieu of the actual 01h value passed in the SNP error message, to avoid confusion with the normal successful OMMREQ completion.) Local SNP/SNP-X Error. n error occurred within the SNP task in the MM module in this PL. 0x000 This error may occur in either an SNP master or an SNP slave. The minor error code contains the specific error code. 0x000 Remote SNP Error. n error occurred within the SNP slave task in the MM module in the remote PL. The minor error code contains the specific error code. 0x000E utodial Error. n error occurred while attempting to send a command string to an attached external modem. The minor error code contains the specific error code. 0x000F SNP-X slave error. n error occurred within the SNPX task in the remote slave device. The minor error code contains the specific error code. 0x001 Port configurator error. 0x000 Problem with sending mail to the slave Service Request task. (Series 0-0 PL PUs only) 0x001 Problem with getting mail from the slave Service Request task. (Series 0-0 PL PUs only) 0x00 Slave SNP task timed out before receiving an SRP response. (Series 0-0 PL PUs only) 0x00 Slave SNP task could not find the requested datagram connection. (Series 0-0 PL PUs only) 0x00 Slave SNP task encountered an error in trying to write the datagram. (Series 0-0 PL PUs only) 0x00 Slave SNP task encountered an error in trying to update the datagram. (Series 0-0 PL PUs only) PL generated error codes for the GE 0-0, 0-0 and VersaMax SNPX protocol continue on the next page. -1 E1-TL-M Hardware User Manual, nd Ed. Rev., 0/1

15 ppendix : Panel & PL Error ode Tables GE SNPX Protocol PL Error ode Tables (cont d) Panel Error ode P Hex Value PL Error 0x0 PL Error 0x0E PL Error 0x0F PL Error 0x00 PL Error 0x00E PL Error 0x00F PL Error 0x01 PL Error 0x00 PL Error 0x00E PL Error 0x00F PL Error 0x01 PL Error 0x00 PL Error 0x00E PL Error 0x00F PL Error 0x01 PL Error 0x00 PL Error 0x00E PL Error 0x00F PL Error 0x01 PL Error 0x00 PL Error 0x00E PL Error 0x00F PL Error 0x00 PL Error 0x00E PL Errors for GE SNPX Protocol (Minor-Major) (cont d) escription WIT-type OMMREQ is not permitted; must use NOW IT-type. Not used 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. OMMREQ command is not supported. The modem command string length exceeds 0 characters. Insufficient privilege level in the slave PL PU for the requested SNP-X service. Password protection at PL PU may be preventing the requested service. Unsupported OMMREQ. These errors are only generated when there is no protocol currently being run on a port, and the port receives a OMMREQ. (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 ttach or Long ttach OMMREQ. OMMREQ ata lock Length is too small. Output command string data is missing or incomplete. Invalid slave memory type in X-Request message. Invalid OMMREQ length. SNP slave did not respond to ttach message from master. Serial output timeout. The MM module was unable to transmit the modem autodial output from the serial port. (May be due to missing TS signal when the MM is configured to use hardware flow control.) Invalid slave memory address or range in X-Request message. Invalid OMMREQ status word location. Unable to write SNP Status Word to local PL memory; may be due to invalid Status Word memory type or address. Response was not received from modem. heck modem and cable. Invalid data length in X-Request message. ata length must be non-zero, and may not exceed decimal 00 bytes. Invalid OMMREQ data. Master device memory type is not valid in this PL. Modem responded with USY. Modem is unable to complete the requested connection. The remote modem is already in use; retry the connection request at a later time. X-uffer data length does not match the service request in X-Request message. The X-uffer 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. Master device memory address or length is zero. Modem responded with NO RRIER. Modem is unable to complete the requested connection. heck the local and remote modems and the telephone line. Queue Full indication from Service Request Processor in slave PL PU. PL Error 0x00F The slave is temporarily unable to complete the service request. The master should try again later. It is recommended that the master wait at least msec before repeating the X-Request. PL generated error codes for the GE 0-0, 0-0 and VersaMax SNPX protocol continued on the next page E1-TL-M Hardware User Manual, nd Ed. Rev., 0/1-1

16 ppendix : Panel & PL Error ode Tables GE SNPX Protocol PL Error ode Tables (cont d) Panel Error ode P Hex Value 0x00 0x00E 0x00F 0x00 PL Errors for GE SNPX Protocol (Minor-Major) (cont d) escription Unable to read or write master device memory locations specified in OMMREQ. Usually caused by invalid memory address for this PL. SNP message exchange may have taken place. Modem responded with NO ILTONE. Modem is unable to complete the requested connection. heck the modem connections and the telephone line. Service Request Processor response exceeds 00 bytes; the SNP-X slave device cannot return the data in an X-Response message. (This error applies to MM module only.) Master device memory data length exceeds maximum data size of MM module (0 bytes). Must use a smaller data length. Use multiple OMMREQs if total data length exceeds this maximum value. 0x00E Modem responded with ERROR. Modem is unable to complete the requested command. heck the modem command string and modem. 0x00 Slave device memory type is missing or not valid. 0x00E 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. 0x00 Slave device memory address is missing or zero. n unknown response was received from the modem. Modem is unable to complete the requested 0x00E command. heck the modem command string and modem. The modem response is expected to be either ONNET or OK. OMMREQ ata lock Length is too small. 0x00 (When expected OMMREQ length is words or less. n improper length may cause other minor error codes -.) 0x00 Invalid iagnostic Status Word (SW) starting word or length. 0x0E0 Invalid maximum SNP message data size. Must be an even value from to 0. 0x0F0 Invalid Privilege Level. Must be 0 through or -1. 0x0 Invalid Fault Table selector. Must be 1 for I/O Fault Table, or for PL Fault Table. Unexpected Service Request Processor error. 0x0F (This error applies to MM module only; the unexpected SRP error code is saved in the iagnostic Status Words in the MM module.) 0x1 Invalid Fault Table starting index. Must be 1- for I/O Fault Table, or 1-1 for PL. 0x10 Invalid fault count. Must be 1- for I/O Fault Table, or 1-1 for PL Fault Table. 0x10 Invalid Set PL ate/time mode. Must be 1-. 0x10 Invalid Set PL ate/time date, time, or day-of-week value. 0x10 Unable to retrieve master device PL time/date from PL PU. 0x10F Requested service is not permitted in a roadcast request. The master must direct the X-Request message to a specific SNP-X slave device. 0x Invalid slave PL type. Must be 0 for Series 0-0, or 1 for Series 0-0 or Series x Invalid datagram type. Must be 01h for normal datagram, or 1h (1) for permanent datagram. 0x Missing or too many datagram point formats. Must be 1-. 0x10 Invalid datagram point format data. PL generated error codes for the GE 0-0, 0-0 and VersaMax SNPX protocol continue on the next page. -1 E1-TL-M Hardware User Manual, nd Ed. Rev., 0/1

17 ppendix : Panel & PL Error ode Tables GE SNPX Protocol PL Error ode Tables (cont d) PL Errors for GE SNPX Protocol (Minor-Major) (cont d) Panel Error ode P Hex Value escription 0x atagram area size is too small to include data for all specified point formats. 0x10 Invalid number of ontrol Program Names. Must be 1-. 0x10 SNP-X Request exceeds maximum data size (00 bytes). Must use a smaller data length. Use multiple OMMREQs if necessary. 0x10 Invalid SNP-X communication session type. Must be 0 for a single slave device, or 1 for multiple slave devices. Illegal destination SNP I specified for SNP-X slave. Must be 0- SII characters, plus a terminating 0x1E0 null character (00h). The Null SNP I (eight bytes of 00h) may be used to specify any single device. The roadcast SNP I (eight bytes of FFh) may be use to specify all slave devices on the serial link. estination SNP I does not match SNP-X session type. 0x1F0 The roadcast SNP I is not permitted in a single-slave SNP-X session. The Null SNP I is not permitted in a multiple-slave SNP-X session. 0x00 Inactivity timeout (T ). The SNP slave has not received any new SNP messages within the configured T time interval. 0x00F Invalid Message Type field in a received X-Request message. The message type of an X-Request message must be h = X. 0x Parity error has occurred on an ttach, ttach Response, or Update Real time atagram message. ommunications have not been established. Invalid Next Message Type or Next Message Length field in a received X Request message. If this request does not use a buffer (0- bytes of data), the Next Message Type must be zero. If this request will be 0xF followed with a buffer message (more than byte.)), the Next Message Type must be h = T, and the Next Message Length must specify the length of the X-uffer message. Valid X-uffer message lengths are -0 bytes (data length plus bytes). 0x0 (lock heck ode) error has occurred on an ttach, ttach Response, or Update Realtime atagram message. ommunications have not been established. 0x0F Invalid Message Type field in a received X-uffer message. The message type of an X-uffer message must be h = T. 0x0 Framing or Overrun serial error has occurred on an ttach, ttach Response, or Update Realtime atagram message. ommunications have not been established. 0x0F Invalid Next Message Type field in a received X-uffer message. Since an X-uffer message is never followed by another message, the Next Message Type must always be zero. 0x0 n invalid SNP message type was received when an ttach, ttach Response, or Update Realtime atagram message was required. ommunications have not been established. 0x0 n invalid next message length value was specified in an ttach, ttach Response, or Update Realtime atagram message. ommunications have not been established. 0x0 n unexpected SNP message type was received when an ttach, ttach Response, or Update Realtime atagram was required. ommunications have not been established. 0x0 nother reak was received while SNP slave was waiting for an ttach or Update Realtime atagram message. n SNP message has been sent and retried the maximum number of times. 0x0 maximum of two retries are permitted. retry is caused by a NK from from the remote SNP device. 0x0 received SNP message has been NKed the maximum number of two times. The NKed message may be retransmitted a maximum of two times. PL generated error codes for the GE 0-0, 0-0 and VersaMax SNPX protocol continue on the next page E1-TL-M Hardware User Manual, nd Ed. Rev., 0/1-1

18 ppendix : Panel & PL Error ode Tables GE SNPX Protocol PL Error ode Tables (cont d) Panel Error ode P Hex Value 0x0 0x0 0x0 0x0 0xE0 0xF0 0x00 0x 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x00 0x00 0x00F PL Errors for GE SNPX Protocol (Minor-Major) (cont d) escription n unknown message was received when an acknowledge (K or NK) was required. Sequence Error. n unexpected SNP message type was received. Received SNP message contains bad next message length value. cknowledge timeout. n acknowledge (K or NK) was not received within the configured T time interval. slave device may generate this error if the master device has aborted after maximum response NKs and does not NK the next response retry. Response timeout. The SNP Master did not receive an SNP Response message within the configured T time interval. uffer message timeout. n expected Text uffer or onnection ata message was not received within the configured T time interval. Serial output timeout. The MM module was unable to transmit a reak, an SNP message, or SNP acknowledge (K or NK) from the serial port. (May be due to missing TS signal when the MM module is configured to use hardware flow control.) SNP slave did not receive a response from the Service Request Processor in the PL PU. OMMREQ timeout. The OMMREQ did not complete within the configured time interval. n SNP Request or Response was aborted prior to completion due to reception of a reak. PL backplane communications error Invalid Piggyback Status data memory type or address. ommunications have not been established. Invalid SNP Slave SNP I. Must be a 0- SII characters, plus a terminating null character (00h). The Null SNP I (eight bytes of 00h) may be used to specify any single slave device. The SNP master has received a response message containing an unexpected data length. Usually indicates a problem with the remote SNP slave device. May occur when Series 0-0 commands (Task Memory or Program lock Memory Read/Write) are issued to a Series 0-0 slave device. Response code in received SNP-X response message does not match expected value. (Response code must equal the request code +0h.) SNP-X Response message exceeds maximum data size (decimal 00 bytes). ata in the Response is ignored. parity error has occurred on an X-ttach Response message when establishing a new SNP-X communication session. ommunications have not been established. The requested service is not supported by the SNP slave. Serial output timeout. The slave was unable to transmit an SNP-X message from the serial port. (May be due to missing TS signal when the MM module is configured to use hardware flow control.) PL generated error codes for the GE Fanuc 0-0, 0-0 and VersaMax SNPX protocol continue on the next page. -1 E1-TL-M Hardware User Manual, nd Ed. Rev., 0/1

19 ppendix : Panel & PL Error ode Tables GE SNPX Protocol PL Error ode Tables (cont d) PL Errors for GE SNPX Protocol (Minor-Major) (cont d) Panel Error ode P Hex Value escription framing or overrun error has occurred on an X-ttach Response message when establishing a new 0x SNP-X communication session. ommunications have not been established. 0x SNP slave on MM module requires PL PU privilege level to operate. The SNP slave has rejected a request to change to a higher or lower privilege level. 0xF n SNP-X request was aborted prior to completion due to reception of a reak. (lock heck ode) error has occurred on an X-ttach Response message when establishing a new 0x0 SNP-X communication session. ommunications have not been established. SNP Request or Response message exceeds maximum data length of the MM module. (Total data length 0x0 for Mailbox and all following uffer messages is 0 bytes.) The master must use a smaller data length. Use multiple requests if total data length exceeds the maximum value. 0x0F n X-uffer message was received containing greater than 00 bytes of data. The data is ignored. n invalid message type was received when an X-ttach Response was required when establishing a new 0x0 SNP-X communication session. ommunications have not been established. Improper Write atagram message format. Series 0-0 slave devices use a different format for this message than Series 0-0 or Series 0-0 slave devices. The master must use the proper message format 0x0 for this SNP slave device. (The SNP master in the MMmodule sends this message as part of the Establish atagram OMMREQ command. The datagram has been partially established, but is not usable; the datagram should be cancelled by using the atagram I returned by the OMMREQ.) 0x0F The SNP-X slave did not receive a response from the Service Request Processor in the PL PU. n invalid next message type value was detected in an X-ttach Response message when establishing a 0x0 new SNP-X communication session. ommunications have not been established. 0x0 datagram error occurred in a Series 0-0 slave device (dual-port error). 0x0F PL backplane communications error. n invalid response code was detected in an X-ttach Response message when establishing a new SNP-X 0x0 communication session. ommunications have not been established. n expected X-ttach Response message was not received within the response timeout interval when 0x0 establishing a new SNP-X communication session. The master has retried the X-ttach message twice without receiving a response. ommunications have not been established. parity error has occurred on an X-ttach Response message when re-establishing an existing SNP-X 0x00 communication session. ommunications have not been established. 0x00F parity error has occurred in a received X-ttach message. framing or overrun error has occurred on an X-ttach Response message when re-establishing an 0x existing SNP-X communication session. ommunications have not been established. 0xF framing or overrun error has occurred in a received X-ttach message. (lock heck ode) error has occurred on an X-ttach Response message when re-establishing an 0x0 existing SNP-X communication session. ommunications have not been established. 0x0F (lock heck ode) error has occurred in a received X-ttach message. PL generated error codes for the GE Fanuc 0-0, 0-0 and VersaMax SNPX protocol continue on the next page E1-TL-M Hardware User Manual, nd Ed. Rev., 0/1-1

20 ppendix : Panel & PL Error ode Tables GE SNPX Protocol PL Error ode Tables (cont d) Panel Error ode P Hex Value 0x0 0x0F 0x0 0x0F 0x0 0x0F 0x0 0x00 0x00F 0x 0xF 0x0 0x0F 0x0 0x0 0x0 0x0 0x00 0x00F 0x 0xF 0x0 0x0F 0x0 0x0F 0x0 0x0 0x0 PL Errors for GE SNPX Protocol (Minor-Major) (cont d) escription n invalid message type was received when an X-ttach Response was required when re-establishing an existing SNP-X communication session. ommunications have not been established. n invalid Message Type was received when an X-ttach message was required. (For an X-ttach message, the message type must be h = T.) n invalid Next Message Type value was detected in an X-ttach Response message when re-establishing an existing SNP-X communication session. ommunications have not been established. n invalid Next Message Type value was detected in a received X-ttach message. (For an X-ttach message, the Next Message Length must be zero.) n invalid response code was detected in an X-ttach Response message when re-establishing an existing SNP-X communication session. ommunications have not been established. n invalid request code was detected in a received X-ttach message. n expected X-ttach Response message was not received within the response timeout interval when re-establishing an existing SNP-X communication session. The master has retried the X-ttach message twice without receiving a response. ommunications have not been established. parity error has occurred on an X-Response message. parity error has occurred in a received X-Request message. framing or overrun error has occurred on an X-Response message. framing or overrun error has occurred in a received X-Request message. (lock heck ode) error has occurred on an X-Response message. (lock heck ode) error has occurred in a received X-Request message. n invalid message type was received when an X-Response message was required. n invalid next message type value was detected in an X-Response message. n invalid response code was detected in an X-Response message. n expected X-Response message was not received within the response time. parity error has occurred on an Intermediate Response message. parity error has occurred in a received X-uffer message. framing or overrun error has occurred on an Intermediate Response message. framing or overrun error has occurred in a received X-uffer message. (lock heck ode) error has occurred on an Intermediate Response message. (lock heck ode) error has occurred in a received X-uffer message. n invalid message type was received when an Intermediate Response message was required. n expected X-uffer message was not received. n invalid next message type value was detected in an Intermediate Response message. n invalid response code was detected in an Intermediate Response message. n expected Intermediate Response message was not received within the response timeout interval. PL generated error codes for the GE Fanuc 0-0, 0-0 and VersaMax SNPX protocol continue on the next page. -0 E1-TL-M Hardware User Manual, nd Ed. Rev., 0/1

21 ppendix : Panel & PL Error ode Tables GE SNPX Protocol PL Error ode Tables (cont d) Panel Error ode P Hex Value 0x0 0xE0 0xF0 0x00 0x 0x0 0x 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0xE0 0xF0 0x00 0x 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0xE0 0xF0 PL Errors for GE SNPX Protocol (Minor-Major) (cont d) escription ad OS Version. Must have OS.0, or later, to support the SNP OS river. P Serial port configured for SNP Master driver is not open; no communication can take place. Out of Sequence SNP message. SNP message type received was not the type expected. ad SNP encountered. Transmission was aborted after maximum retries due to a bad lock heck ode. ad 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 established. Invalid block state transition. The OEM key is NULL (inactive). Text length does not match traffic type. Verify with F ard or EEPROM failed. No task level Rack/Slot configuration to read or delete. ontrol Program (P) tasks exist but requestor not logged into main P. Passwords are set to inactive and cannot be enabled or disabled. Password(s) already enabled and can not be forced inactive. Login using non zero buffer size required for block commands. evice is write protected. comm or write verify error occurred during save or restore. ata stored on device has been corrupted and is no longer reliable. ttempt was made to read a device but no data has been stored on it. Specified device has insufficient memory to handle request. Specified device is not available in the system (not present). One or more PL modules configured have unsupported revision. Packet size or total program size does not match input. Invalid write mode parameter. User Program Module (UPM) read or write exceeded block end. Mismatch of configuration checksum. Invalid block name specified in datagram. Total datagram connection memory exceeded. Invalid datagram type specified. Point length not allowed. Transfer type invalid for this Memory Type selector. Null pointer to data in Memory Type selector. Invalid Memory Type selector in datagram. Unable to find connection address. Unable to locate given datagram connection I. Size of datagram connection invalid. Invalid datagram connection address. PL generated error codes for the GE Fanuc 0-0, 0-0 and VersaMax SNPX protocol continue on the next page E1-TL-M Hardware User Manual, nd Ed. Rev., 0/1-1

22 ppendix : Panel & PL Error ode Tables GE SNPX Protocol PL Error ode Tables (cont d) PL Errors for GE SNPX Protocol (Minor-Major) (cont d) Panel Error ode P Hex Value escription 0xE00 Service in process cannot login. 0xE No I/O configuration to read or delete. 0xE0 IOS could not delete configuration, or bad type. 0xE0 PU revision number does not match. 0xE0 Memory Type for this selector does not exist. 0xE0 OS file area not formatted. 0xE0 PU model number does not match. 0xE0 onfiguration is not valid. 0xE0 No user memory is available to allocate. 0xE0 Memory Type selector not valid in context. 0xE0 Not logged in to process service request. 0xE0 Task unable to be deleted. 0xE0 Task unable to be created. 0xE0 VME bus error encountered. 0xEE0 ould not return block sizes. 0xEF0 Programmer is already attached. 0xF00 Request only valid in stop mode. 0xF Request only valid from programmer. 0xF0 Invalid program cannot log in. 0xF0 I/O configuration mismatch. 0xF0 Invalid input parameter in request. 0xF0 Invalid password. 0xF0 Invalid sweep state to set. 0xF0 Required to log in to a task for service. 0xF0 Invalid Task Name referenced. 0xF0 Task address out of range. 0xF0 annot replace I/O module. 0xF0 annot clear I/O configuration. 0xF0 I/O configuration is invalid. 0xF0 Unable to perform auto configuration. 0xFE0 No privilege for attempted operation. 0xFF0 Service Request Error has been aborted. - E1-TL-M Hardware User Manual, nd Ed. Rev., 0/1

23 ppendix : Panel & PL Error ode Tables Mitsubishi FX Protocol PL Error odes Only errors as listed in the -more Micro-Graphic Panel Error ode Table shown on page - can occur when using the Mitsubishi FX protocol, there are no PL generated errors. Mitsubishi Q / Qn Series PL Error odes The following table lists the errors that can be generated by the Mitsubisht Q / Qn Series PL when using the Q / Qn protocol. NOTE: The following errors can be generated from the designated PL, are monitored by the -more Micro- Graphic panel, and displayed on the panel s screen as a hexadecimal value in panel error code P, if active. Please refer to the PL users manual for additional information. PL Error odes for Mitsubishi Q / Qn and Q Series Panel Error ode P Hex Value escription 0x000 Serial communications checksum error. heck cable and grounding. 0x001 Unsupported request sent to PL. 0x00 Unsupported request sent to PL. 0x00 Global request sent to PL that cannot be executed. 0x00 System protect switch is on and request was sent that cannot be executed. lso PL, may still be booting up. 0x00 Packet sent is too large according to size request in header. 0x00 Serial communications could not be initialized. 0x00 PU busy or buffer full. 0x0 Request cannot be serviced while PU is running. PU must be stopped. 0x01 Request cannot be serviced while PU is running. PU must be stopped. 0x01 rive memory does not exist. 0x0 File (ZR memory) does not exist. 0x0 File (ZR memory) name and File (ZR memory) number do not match. 0x0 File (ZR memory) inaccessible by user. 0x0 File (ZR memory) is locked by another device. 0x0 File (ZR memory) password required. 0x0 Specified range is out of File (ZR memory) range. 0x0 File (ZR memory) already exist. 0x0 Specified File (ZR memory) capacity cannot be retrieved. 0x0 Specified File (ZR memory) is abnormal. 0x0 The requested data cannot be executed in the specified drive memory. 0x0 The requested operation cannot be executed presently. 0x00 The specified data type does not exist. heck the PUs allowable data types. 0x01 The specified address is out of range. The data type requested may need to be expanded in GX developer. The PU may not allow this data type. 0x0 ddress qualification is incorrect. 0x0 annot write to system area. 0x0 Request cannot be executed because completion address for an instruction cannot be turned on. PL generated error codes for the Mitsubishi Q / Qn protocol continue on the next page E1-TL-M Hardware User Manual, nd Ed. Rev., 0/1 -

24 ppendix : Panel & PL Error ode Tables Mitsubishi Q / Qn Series PL Error odes (cont d) PL Error odes for Mitsubishi Q / Qn and Q Series Panel Error ode P Hex Value escription 0x00 Module doesn t support request. 0x01 Request is out of module s range. 0x0 Module cannot be accessed. 0x0 ddress for specified module is incorrect. 0x0 Hardware problem exist for specified module. 0x00 Request cannot be executed because memory card protect switch is on. 0x01 Specified memory cannot be accessed. 0x0 Specified memory attribute is read only and cannot be written to. 0x0 Error occurred when writing to specified memory location. 0x00 Request data error. heck cabling and electrical noise. 0x0 Specified request is already being executed. 0x0 The remote request cannot be performed. 0x00 block number out of range was specified. 0x01 The number of blocks requested exceeds the range of the PL. 0x0 step number was specified out of range. 0x0 Step range limit exceeded. 0x0 Specified sequence step number is out of range. 0x0 Specified SF device is out of range. 0x0 lock specification and step specification are incorrect. 0x0 PU module hardware fault. 0x1 Serial communication connection incorrect. 0x PU module internal memory fault. ad PU. 0x PU is in initialization. Wait until PU is booted up. 0x Specified function not supported by this PU. heck memory types for that PU. 0x1 Specified function not supported because PU is in Stop. Put PU in Run. 0x1 System is not up yet. Wait until system is up before performing request. 0x01 The network number specified does not exist. Routing not supported in -more. 0x0 Station number specified does not exist. Routing not supported in -more. - E1-TL-M Hardware User Manual, nd Ed. Rev., 0/1

25 ppendix : Panel & PL Error ode Tables Omron Error ode P Explanation The P error code is used to show any errors that are generated by the connected PL. The P error message includes a four digit hexadecimal value displayed at the end of 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 Omron Host Link communication protocols breakdown into a four digit hexadecimal value. Omron Error ode P Message Example: P: Recv. Err ode 001 Start Stop E1-TL-M Hardware User Manual, nd Ed. Rev., 0/1 -

26 ppendix : Panel & PL Error ode Tables Omron Host Link Protocol PL Error ode Table The following table lists the errors that can be generated by the Omron PL when using the Host Link protocol. Panel Error ode P Hex Value 0x00 0x01 0x0 0x0 0x0 0x0 0x0 0x0 0x 0x 0x1 0x1 0x1 0x1 0x1 0x1 0x1 0x0 0x0 0x1 0x 0x 0x 0x 0x 0x0 NOTE: The following errors can be generated from the designated PL, are monitored by the -more Micro- Graphic panel, and displayed on the panel s screen as a hexadecimal value in panel error code P, if active. Please refer to the PL manufacturer s documentation for additional information. PL Error odes for Omron Host Link escription Normal ompletion. Not executable in RUN mode. Not executable in MONITOR mode. Not executable with PROM mounted. ddress over (data overflow). Not executable in PROGRM mode. Not executable in EUG mode. Not executable in LOL mode. Parity error. Framing error. Overrun. FS error. Format error (parameter length error). Entry number data error (parameter error, data code error, data length error). Instruction not found. Frame length error. Not executable (due to Un-executable error clear, non-registration of I/O table, etc.). I/O table generation impossible (unrecognized remote I/O unit, channel over, duplication of optical transmitting I/O unit). bort due to parity error in transmit data under process. bort due to framing error in transmit data under process. bort due to overrun in transmit data under process. bort due to FS error in transmit data under process. bort due to format error in transmit data under process. bort due to frame length error in transmit data under process. bort due to entry number data error in transmit data under process. Un-executable due to program area capacity other than 1k bytes. - E1-TL-M Hardware User Manual, nd Ed. Rev., 0/1

27 ppendix : Panel & PL Error ode Tables Omron FINS Protocol PL Error ode Table The following table lists the errors that can be generated by the Omron PL when using the FINS protocol. Panel Error ode P Hex Value 0x0000 0x0001 0x01 0x0 0x0 0x0 0x0 0x0 0x001 0x00 0x00 0x00 0x00 0x001 0x00 0x00 0x00 0x001 0x00 0x001 0x00 0x00 0x00 0x01 0x0 0x0 0x0 0x0 0x 0x1 0x1 NOTE: The following errors can be generated from the designated PL, are monitored by the -more Micro- Graphic panel, and displayed on the panel s screen as a hexadecimal value in panel error code P, if active. Please refer to the PL manufacturer s documentation for additional information. PL Error odes for Omron FINS escription Normal ompletion. Service anceled. Local Error: Local node not in network. Local Error: Token Timeout. Local Error: Retries Failed. Local Error: Too many send frames. Local Error: Node address range error. Local Error: Node ddress uplication. estination Node Error: estination Node not in network. estination Node Error: Unit Missing. estination Node Error: Third Node missing. estination Node Error: estination Node busy. estination Node Error: Response Timeout. ontroller Error: ommunications ontroller Error. ontroller Error: PU Unit Error. ontroller Error: ontroller Error. ontroller Error: Unit number Error. Service Unsupported: Undefined ommand. Service Unsupported: Not supported by Model/Version. Routing Table Error: estination address setting error. Routing Table Error: No routing tables. Routing Table Error: Routing table error. Routing Table Error: Too many delays. ommand Format Error: ommand too long. ommand Format Error: ommand too short. ommand Format Error: Elements/ata don t match. ommand Format Error: ommand format error. ommand Format Error: Header Error. Parameter Error: rea classification missing. Parameter Error: ccess Size Error. Parameter Error: ddress range error. PL generated error codes for the Omron FINS protocol continue on the next page E1-TL-M Hardware User Manual, nd Ed. Rev., 0/1 -