Appendix. Error Codes and System Locations. In This Appendix...

Transcription

1 odes and System s ppendix In This ppendix... o-more! esigner s and System s... - Memory s with System-ssigned Nicknames... -

2 ppendix : odes and System s 0 o-more! esigner s and System s s in o-more! esigner are typically found in the Output Window. To get to the Output Window, Go to Windows -> Output Window and a new pane will open. Typically the Output window will open automatically when an error is found when accepting rungs or when downloading to the PL. For errors that are not program check errors, there may be an error reporting field in the evice Structure that can provide information on the error and what it means. For these sorts of errors, the best place to find more information is in the Software Help file for the operation that you are attempting. System memory locations can also help with finding errors. There is a chart later in this appendix for reference. For more information see o-more! esigner help topic M0. Program heck Rules lass Number escription Message M00 isconnected Module is being downloaded as part of the System onfiguration. Warning E0 W0 Support for feature added in o-more! Technology Version, but this PL is currently running older o-more! Technology Version Support for feature added in o-more! Technology Version, but this PL is currently running older o-more! Technology Version Warning W0 Rung is missing input logic, power flow state will be based on previous rung's power flow state E0 Multiple instructions exist; only one is allowed E0 o-more! Technology Version in PU does not support the new instruction; remove the instruction or upgrade firmware E Instruction validation error Message M Program contains Unassigned Nicknames E Program contains Unassigned Nicknames E isconnected Module evice used by instruction Warning W irectlogi Stub instruction needs attention before downloading to PL E irectlogi Stub instruction needs attention before downloading to PL E rray reference found within differential/delta contact inside a loop Warning W Writing to Raw nalog Output WY or to Scaled nalog Input RX when that analog channel has a pre-defined scale in the System onfiguration Warning W0 Writing to High Speed Y that is bound to High Speed Output Function (instruction has no effect) Warning W ccessing a bit unipolar analog without the Unsigned cast :U Warning W0 <Primary-instruction> <element> in <secondary-instruction> does not exist Warning W0 <Resource-parameter> in instruction used multiple times E0 <Resource-parameter> in instruction used multiple times Message M0 ode-block exists without any invocation-instruction to execute it Warning W OUT <element> coil duplicated multiple times Message M OUT <element> coil duplicated multiple times Message M0 ommon Modbus/TP lient evice used for multiple Servers E0 uplicate LEL at address E0 GOTO missing corresponding LEL E0 annot GOTO a LEL in a different Stage Message M0 LEL missing corresponding GOTO E0 annot GOTO a LEL in a different code-block E End-of-loop instruction is missing start-of-loop or is paired with incorrect start-of-loop instruction E Start-of-loop missing corresponding end-of-loop - RX User Manual, rd Edition, Rev.

3 ppendix : odes and System s Program heck Rules (continued) lass Number escription E Instruction not allowed within a loop Message M Instruction found within loop Message M locked/edged instruction used within loop E annot GOTO a LEL into or out of a loop Warning W synchronous instruction found within loop E Instruction must exist within a loop Message M synchronous instruction used in code-block with yielding instructions Warning W0 SUSPEN not recommended within its own code-block (no easy way to un-suspen self) Warning W0 Found <code-block-invoking-instruction> within its own code-block Warning W0 Using HLT on a code-block that utilizes fully-asynchronous instruction(s) E Instruction can only exist in $Main code-block E <Instruction> found in <non-program> code-block; can only exist in a PROGRM code-block E Instruction not permitted in $Main code-block E Stage bit cannot be modified by logic in a different PROGRM code-block E Instruction cannot be in a Stage E Instruction must be within a Stage Warning W Using retentive element in coil within a non-retentive stage Warning W Time-based instruction used in edge-enabled task Warning W Time-based instruction used in a continuously-enabled task with a non-zero interval Warning W Fully-asynchronous instruction used in edge-enabled task Warning W Fully-asynchronous instruction used in a continuously-enabled task with a non-zero interval Message M Partial-asynchronous instruction used in edge-enabled task Message M Partial-asynchronous instruction used in a continuously-enabled task with a non-zero interval Message M locked/edged instruction used in edge-enabled task Message M locked/edged instruction used in a continuously-enabled task with a non-zero interval Warning W Edge-Enabled ENTSK instructions exist with Interval-Enabled ENTSK instructions Warning W0 Other continuous / interval ENTSK instructions exist Warning W Full OFF-to-ON Transition Input Leg counting instruction used in edge-enabled task E0 Subroutine missing unconditional RET at end of code-block Message M High Speed iscrete Output set within non-immediate instruction in Interrupt-Service-Routine Message M Immediate I/O instruction inside NON-Interrupt-Service-Routine Warning E0 E0 E0 E0 E0 E0 E0 W0 o-more! Technology Version in PU only supports Edge-Triggered Input-Leg (not Power-Flow- Enabled) in instruction; modify instruction or upgrade firmware o-more! Technology Version in PU does not support ONLY Swap ytes or ONLY Swap Words on Word sized memory in PULISH/SUSRI instruction; modify instruction, or upgrade firmware o-more! Technology Version in PU does not support clearing bit-sized elements in MEMLER instruction; modify instruction, use RSTR, or upgrade firmware o-more! Technology Version in PU does not support variable Modbus parameter in MRX/MWX instruction; use only constant, or upgrade firmware o-more! Technology Version in PU does not support variable parameter in NETTIME instruction; use only a constant value, or upgrade firmware o-more! Technology Version in PU does not support a variable networking parameter in LRX/ LWX instruction; use only constant, or upgrade firmware o-more! Technology Version in PU does not support "ipaddr" format in "FmtInt()" print script command in instruction; modify instruction or upgrade firmware o-more! Technology Version in PU does not support register in EVRE/EVWRITE instruction; modify instruction or upgrade firmware 0 E0 TRIO's file system does not contain a file at file number compatible with the instruction RX User Manual, rd Edition, Rev. -

4 ppendix : odes and System s 0 Memory s with System-ssigned Nicknames The o-more! PUs are pre-configured with several bit and numeric locations that have system-assigned Nicknames. Some of these locations are outputs that report Status information, some of them are inputs used to provide configuration selections to the PU, and some of them are input & output locations. This list can be found in Help topic M00. it s with System-ssigned Nicknames it Nickname Type escription ST0 $FirstScan Status ST $On Status lways ON. ST $Off Status lways OFF. ST $Minute Status ST $Second Status ST $00ms Status ST $0ms Status ST $ScanToggle Status Will be ON for alternate scans. ST $LastScan Status Will be ON for the duration of the first PU scan after a STOP mode -to- RUN mode transition. While the PU is in RUN mode this bit location will be set ON once a minute with a 0% duty cycle, that is, it will be ON for 0 seconds then OFF for 0 seconds. While the PU is in RUN mode this bit location will be set ON once a second with a 0% duty cycle, that is, it will be ON for / second then OFF for / second. While the PU is in RUN mode this bit location will be set ON once every 00ms with a 0% duty cycle, that is, it will be ON for 0 milliseconds then OFF for 0 milliseconds. While the PU is in RUN mode this bit location will be set ON once every 0ms with a 0% duty cycle, that is, it will be ON for milliseconds then OFF for milliseconds. Will be ON for the duration of the last PU scan before a RUN mode -to- STOP mode transition. ST0 $Hass Status Will be ON any time the PU is reporting any runtime errors. ST $HasWarnings Status Will be ON any time the PU is reporting any runtime warnings. ST $HasInfo Status Will be ON any time the PU is reporting any runtime informational messages. ST $WatchdogReboot Status Will be ON after a Hardware Watchdog Reboot has occurred. ST $ModuleFailed Status Will be ON when any installed module fails validation, which generally means that its module I doesn t match the module I discovered at power up. - RX User Manual, rd Edition, Rev.

5 ppendix : odes and System s it s with System-ssigned Nicknames (continued) it Nickname Type escription ST $PgmModeRestart onfiguration ST $TermRunMode Status ST $SerFifoOverflow onfiguration Will be ON after a Program mode -to- Run mode transition (because of a o-more! esigner mode change operation or because the front panel mode switch was used). Non-retentive memory has been cleared, retentive memory has not been changed, but the state information of all Programs (including their Stage bits) and Tasks have been reset even if the Program or Task has been configured as retentive. Will be OFF in Run mode after a power-up, or a restart after a Watchdog Timer event, or after a REOOT instruction is executed. Non-retentive memory has been cleared, retentive memory has been preserved. The state information for Programs and Tasks marked as retentive has been preserved, those NOT marked as retentive has been cleared. y default, user created Programs are Tasks are non-retentive, but they can be made retentive if required through the ode-block onfiguration dialog. ll System (built-in) Programs and Tasks are retentive and that cannot be changed. The one exception is that all Stages in $Main will be disabled and the Initial Stage will be enabled if the PU powers up in Run mode, or on a Program -to- Run transition. Note: the ifference etween Two ate / Times (TIFF) instruction with ST ($SysShutdown) and ST ($SysStartup) can be used to determine how long a PU has NOT been in Run mode. The result of this calculation can be used to help decide what (if anything) needs to be manually reset based on the amount of time the PL was not in control of the machine or process. Will be ON if the PU is in RUN mode and the switch is in TERM position. Will be OFF if the PU is in STOP (PGM) mode and the switch is in TERM position, or if the if the mode switch is NOT in TERM position (regardless of the PU mode). Will be ON if the input buffer for the on-board serial port contains 0 bytes of data. ST $RetErrOnadReq onfiguration Will be ON if there is a bad array reference in a ata View. ST $InhPgmUpdate onfiguration Set to ON to prevent program from being updated. ST $TimeSynced Status Will be ON if the TimeSync operation is successful. ST $HwWatchdogMode onfiguration Specifies the action to take in the event of a Hardware Watchdog Timeout. ST $isablehwwdog onfiguration Set ON to disable the Hardware Watchdog Timer. ST $Enableebug onfiguration Set ON by the ebug View to put the PU in debug mode. ST $EnablePowerFlow onfiguration Reserved. ST $EnableNScan onfiguration Set ON by the ebug View to put the PU into N-Scan Mode. ST $EnableMsgump onfiguration Set ON to send all ERR and MSG values to o-more! Logger, see the Send (EMIL) Instruction. ST $isableswwdog onfiguration Set ON to disable the software watchdog timer. ST $WatchdogTimeout Status Will be ON when a software watchdog occurs. ST $Index Status Will be ON when an array reference is out of range. ST $InvalidInstr Status Will be ON if an invalid instruction was downloaded to the PU. User generally should never see this. 0 RX User Manual, rd Edition, Rev. -

6 ppendix : odes and System s 0 it s with System-ssigned Nicknames (continued) it Nickname Type escription ST $OutOfRange Status ST $Overflow Status ST $InstIOhanged Status Will be ON when a parameter that isn t an index error, or an overflow, or a divide-by-zero is out of range. The Status tab of System Info will also display " comm client attempted to read a data address that was out of range. Zero data was returned." in the ERR field. Two common examples (assume the normal range of is 0 0): If V0 =, then trying to reference [V0] = would fail because is outside the range of configured locations. If an external communication client creates a tag that references. gain, is outside the range of configured locations. To correct this, the external communication client should import the memory configuration from the o-more! esigner project so that the only the correct ranges are available for its tags. Will be ON when certain math operators (POW, IN, E, etc.) overflow their calculation. o-more! PUs keep a copy of the last known good I/O onfiguration data stored in their battery-backed memory. While the system is powered down, if an I/O module is removed, or an I/O module is added, or an existing I/O module is moved to a different slot, or an existing I/O module is replaced with a different one, the collection of I/O modules will not match the collection that is in the battery-backed memory when the system is powered back on. Will be ON at power-up any time the collection of installed I/O modules has changed from the last time the PL was powered on. ST $IOonfig Status Will be ON when there is an error in the manual I/O configuration. ST $IOMap Status Will be ON when there is an error in the manual I/O map. ST $LoopTuning Status Will be ON while a PI loop is being uto-tuned. ST $MathStackOverflw Status Will be ON when a math operation has caused a stack overflow. ST $FileSystem Status Reserved. ST0 $ufferoverflow Status Will be ON if the result of a string operation is larger than the string element can hold. ST $ivideyzero Status Will be ON when a math operation has a divide by zero operation. ST $riverload Status Will be ON if any device driver failed to load. ST $river Status ST $SystemStopped Status ST $QueuesFlushed Status ST $ommstackoverrn Status ST $InstrTerminated Status ST $riticalio Status ST $atterylow Status ST0 $LoginLockedOut Status Will be ON if any device is reporting a runtime error, use the evice List to see the specific device in error. Will be ON when a Switch to Program Mode (STOP) instruction has executed and put the PU in Stop mode. Will be ON when Ethernet queues were forcibly cleared, possibly due to an open Ethernet device which isn t being serviced. Will be ON when the Ethernet stack was unable to allocate a packet buffer for an incoming packet. Will be ON when a evice instruction was terminated before normal completion. Will be ON when one or more modules failed to verify for longer than the verify filter time, and the system is in a permanent I/O shutdown. Power cycle or Re-Initialize I/O required to return to RUN mode. Will be ON if the battery voltage is below the minimum threshold, see the help section on attery ackup for more information. Will be ON when PL isn t accepting session passwords due to excessive password failures. See the help topic for Failed Login ttempts. - RX User Manual, rd Edition, Rev.

7 ppendix : odes and System s it s with System-ssigned Nicknames (continued) it Nickname Type escription ST $IndexRealigned Status ST $IO Status ST $EthMaster Status ST $EthSlaveOffline Status ST $PgmSwitchctive Status ST $urpgmuffer Status Will be ON if the PU adjusted a misaligned array index. Occurs when incorrectly indexing memory cast to a larger size...as in X[V0]:, where V0 isn t 0,,, etc. Will be ON an I/O Master is in a warning state, this can go from ON to OFF as module issues arise and are resolved. Will be ON when the Ethernet I/O Master detects an error with one of its Ethernet I/O Slaves - most likely an Ethernet I/O Slave is offline. Will be ON when the Ethernet I/O Master detects one of its Ethernet I/O Slaves that is marked as Not Required to Go TO Run Mode is offline. Will be ON when system is swapping program buffers during run mode program update. Indicates active program buffer. Toggles when new program is downloaded. ST $SysonfigUpdate Status Will be ON when system is updating system configuration. ST00 $PgmROMUpdate Status Will be ON when system is writing program to ROM. ST0 $SysfgROMUpdate Status Will be ON when system is writing system configuration to ROM. ST0 $ocromupdate Status Will be ON when system is writing project documentation to ROM. ST0 $SysSetROMUpdate Status Will be ON when system is writing system setup to ROM. ST0 $UserROMUpdate Status Will be ON when system is writing to user ROM ll bit locations starting at ST are retentive; they will hold their value through a power cycle. ST $SummerTime onfiguration Numeric s with System-ssigned Nicknames Set this bit ON to add one hour to $LocalTime calculation to account for aylight Savings Time. Numeric Nickname Type escription ST0 $Scanounter Status ontains the number of scans since the last STOP mode to RUN mode transition. ST $ScanTime Status ontains a filtered average of the $ElapsedTicks. ST $MinScanTime Status ST $MaxScanTime Status ontains the length of time (in microseconds) of the shortest scan since the last STOP mode to RUN mode transition. ontains the length of time (in microseconds) of the longest scan since the last STOP mode to RUN mode transition. ST $ElapsedTicks Status ontains the number of microseconds for the last scan. ST $s Status ompilation of bit flags from (ST... ST) which are considered to be errors. urrently contains the following: WTHOGTIMEOUT MEMORYERROR IOONFIGERROR IOMPERROR MTHSTKOVERFLOW STOPPE OMM_STK_OVERRUN PERMIOFILURE 0 RX User Manual, rd Edition, Rev. -

8 ppendix : odes and System s 0 Numeric s w/system-ssigned Nicknames (continued) Numeric Nickname Type escription ST $Warnings Status ST $Info Status ST $InvalidInstrddr Status ST0 $PLMode Status ompilation of bit flags from (ST...) which are considered to be warnings. urrently contains the following: INEXERROR OUTOFRNGE INVLIINSTRUTION OVERFLOW FILESYSERROR UFFEROVERFLOW IVIEYZERO RIVERLOERROR RIVERERROR QUEUES_FLUSHE TTERYLOW ompilation of bit flags from (ST...) which are considered to be info. urrently contains the following: INSTLLEIOHNGE, LOOPTUNING, and LOGINLOKEOUT ontains address of invalid instruction on failed program validation: - = no invalid instruction address ontains a value that reflects the current operational mode of the PL: = STOP mode = RUN mode. ST $PLStatus Status ontains the PSTT_XXX bits from ST-. ST $FirmwareRev Status The revision number of the PU's firmware in the form MMmmbbbb. ST $mrev Status The revision number of the PU's o-more! library in the form MMmmbbbb. ST $HardwareRev Status The revision number of the PU's PW n the form 0000MMaa. ST $ooterrev Status The revision number of the PU's boot loader in the form MMmmbbbb. ST $FPGRev Status The revision number of the PU's FPG code in the form MMMMmmmm. ST $NodeNumber Status The Node Number assigned to the PL. ST $IPddress Status ST $NetMask Status ST0 $Gateway Status ST $UT Status ST $LocalTime Status The IP ddress assigned to the PL. Use the IP ddress format of the ata View to see the value in the traditional dotted-decimal form. The Subnet Mask assigned to the PL. Use the IP ddress format of the ata View to see the value in the traditional dotted-decimal form. The Gateway IP ddress assigned to the PL. Use the IP ddress format of the ata View to see the value in the traditional dotted-decimal form. ontains the current UT value (the number of seconds that have elapsed since Jan, 0). The current time calculated from the UT value after adjustments for Time Zone and aylight Savings. ST $WatchdogTimeVal Status ontains the maximum number of milliseconds to allow for a single scan. ST $efaultlockver Status Used by -More panels to enforce protocol compatibility. ST $efaultheapver Status Used by -More panels to enforce protocol compatibility. ST $IOVerifyTimeout Status ontains the minimum amount of time for a module to fail verification before a permanent IO failure shutdown. ST $IOVerifyLastTO Status ontains the amount of time accrued during the last failure verification. ST $IOMasters Status ST $PLType Status ontains one bit per I/O Master, that bit will be ON if that I/O Master is reporting a Module, can go from ON to OFF as module errors arise and are resolved. Values that indicate the PL type: 0: Unknown : M-SIM (o-more! Simulator) : H-M (irectlogi 0 Series) : H-ME (irectlogi 0 Series with on-board Ethernet) : TH-M (Terminator I/O Series) : TH-ME (Terminator I/O Series with on-board Ethernet) : RX-M (RX series) : RX-ME (RX Series with on-board Ethernet) see ST for RX Series PL Sub-types - RX User Manual, rd Edition, Rev.

9 ppendix : odes and System s Numeric s w/system-ssigned Nicknames (continued) Numeric Nickname Type escription The following locations serve as a x stack that contains the last error codes and the address of the instruction that reported that error. To locate the instruction that reported the error, Open Search -> Goto -> Goto ddress or Rung Number (or press trl+g), then enter the value in the associated Lastddr location in the ddress / Rung Number field and make sure to select bsolute ddress then click OK. This will move the edit cursor to the code-block that contains the rung that has the instruction that reported the error code. ST0 $Last Status ontains the code of the most recently reported error. ST $Lastddr Status ontains the address of the most recently reported error. ST $Last Status ontains the code of the nd most recently reported error. ST $Lastddr Status ontains the address of the nd most recently reported error. ST $Last Status ontains the code of the rd most recently reported error. ST $Lastddr Status ontains the address of the rd most recently reported error. ST $Last Status ontains the code of the th most recently reported error. ST $Lastddr Status ontains the address of the th most recently reported error. The following is a list of the possible error codes that appear in the $Last locations (ST0, ST, ST, ST). - - UNKNOWN ERROR n unexpected error occurred. This can be an attempted operation on a POM that is not installed or a POM that does not support that operation. - - RESERVE Reserved NO_ERROR No error. 0 - TIMEOUT Operation timed out. - RXWX_NK The target device NKed a LRX or LWX request. - UNKNOWN_RESPONSE Unknown response. - MOULE_NOT_INSTLLE n ttempt was made to access an I/O module that isn t installed. - MOULE_ESS_FILE Unable to access I/O module. - EVIE_LREY_OPEN n attempt was made to open a evice that is already open. - EVIE_NOT_OPEN n attempt was made to use a evice that hasn t been opened. - INVLI_T Invalid data in response. - EXEPTION_RESPONSE Exception response from MRX or MWX request. - INVLI_R Invalid R in MRX or MWX request. 0 - ONNETION_FILE ouldn t open TP connection with specified device. - UNEXPETE_SMTP_RESP Unexpected response from SMTP server. - POP_ERROR_RESP response from POP server. - MOULE_ERROR_RESP I/O module returned and error response. - MOULE_TIMEOUT Timed out while waiting for an I/O module to respond. - ILLEGL OPERTION n operation was attempted that is illegal in the current mode or configuration. - EVIE_NOT_ONNETE n attempt was made to use a evice that is not connected. - INEXERROR rray index was out of bounds. - IVEEYZERO ivide by Zero. - OUTOFRNGE Parameter out of range. 0 - OVERFLOW Numeric value overflow. - WTHOGTIMEOUT Watchdog timeout. - STOPPE PL Stopped. - UFFEROVERFLOW Result of an attempted string operation was longer than the target string and was truncated. - INSTRUTION_TERMINTE --- Multi-scan device instruction was forcibly terminated before completion. - EIPMSG_RESP_TOO_LONG Received a response that exceeded the maximum length. 0 ell continued on next page RX User Manual, rd Edition, Rev. -

10 ppendix : odes and System s 0 Numeric s w/system-ssigned Nicknames (continued) Numeric Nickname Type escription ST $LastProto Status ell continued from previous page - EIPMSG_ERROR_RESPONSE ---- Received an error response from adapter. - MPP_ERROR_RESPONSE n error was returned to a peer to peer request in an RX or WX instruction. - FILESYS_ERROR File system returned an error. - FILESYS_NOMEI File operation failed because there is no media card installed or the media card didn t mount properly. 0 - FILESYS_NOIRSTRT The file system s.startfolderscan structure member must be set to start a scan with FILEQUERY instruction. - XIS_UNONFIGURE xis unconfigured. Must be configured with XONFIG prior to use. - XIS_INVLI_MOE Requested an unsupported xis mode. - XIS_UNKNOWN_ERROR xis controller received unknown command. - XIS_OMMN_PENING ttempted to send command to axis controller with a command pending. - XIS_INVLI_PRM xis command contained an invalid parameter. - XIS_ESTOP ttempted operation on an xis that is disabled through the.masterenable structure member. - XIS_ISLE xis instruction was terminated prior to normal completion. - XIS_SRIPT_USY ttempted new script operation while script is running. - XIS_LINROT_MISMTH Linear / Rotary mismatch between current xis configuration and request. 0 - XIS_FULT xis has faulted. - TLE_INVLI_PRM Invalid parameter in table driven output function. ontains the error response value from last protocol-based instruction (RX, WX, MRX, MWX, EIPMSG, LRX, LWX, etc.). ST $Inhibits onfiguration Specifies which errors should not result in fatal shutdown of the PU. ST0 $EthroppedPckts Status ST $EthStoppedIntr Status ST $EthSends Status ST $EthPktsReceived Status ST $EthPktsSent Status ontains the number of Ethernet packets that have been lost since the last powercycle. ontains the number of times the Ethernet interrupt was shut off due to excessive network traffic. ontains the number of Ethernet send errors that have occurred since the last power-cycle. ontains the total number of Ethernet packets that have been received since the last power-cycle ontains the total number of Ethernet packets that have been sent since the last power-cycle. ST $Tuneeadand onfiguration eadband value used the by the PI utotune process. ST $TuneSampleTime onfiguration Sample time value used the by the PI utotune process. ST $TuneMinPVhange onfiguration The Minimum PV hange value used the by the PI utotune process. ST $TuneOutputump onfiguration The Output bump value used the by the PI utotune process. ST $EthMissedFrames Status ST0 $Installed POM Status ontains the total number of packets since the last power-cycle that the Ethernet hardware did not process because the packets were incorrectly formed. - No POM installed 0 - Unknown POM installed - X-P-US (US POM with US- connector) - X-P-EOMLT (Ethernet POM with RJ- connector) - X-P-SER-TERM --- (Serial RS- with -pin header) - X-P-SER-TERM --- (Serial RS- with -pin header) - X-P-SER-RJ --- (Serial RS- with RJ- connector) -0 RX User Manual, rd Edition, Rev.

11 ppendix : odes and System s Numeric s w/system-ssigned Nicknames (continued) Numeric Nickname Type escription ST $FatalTermode Status ST $ctivesessions Status ST $PLSubType (for RX) Status When a fatal error occurs, the ERR LE will be on and this register will contain a value that explains what caused the fatal error. 0 : No Fatal ode : any of the following conditions: watchdog timeout, memory error, I/O - configuration or mapping - typically happens if the I/O layout changed, Ethernet I/O Master detected an error (usually a missing slave or the I/O layout in a slave has changed). : n I/O module in the local base is not responding to backplane requests : n Ethernet I/O Slave that is marked as required is not responding. : n instruction that was downloaded to the PL is not valid for the firmware version in the PU. This will typically only happen if the firmware is downgraded without clearing the Program section of the PL first. : Force Watchdog (WTHOG) instruction was executed. : n error occurred in the program, typically an issue in the MTH stack (overflow / underflow). : The limit on the number of local expansion modules that are allowed in the RX system has been exceeded. The number of active communications sessions using o-more! protocol - mesigner, HMI (if it s using M driver), RX/WX connections to other M PUs, or any rd party device that s using M protocol. This is for all ports, ethernet or serial or usb. Maximum of sessions For the RX Series PLs these are the valid Sub-types: : X-ME-M : X-ME-M- : X-M-0E- : X-M-0E- : X-M-0ER- : X-M-0R- : X-ME-0E- : X-ME-0E- 0: X-ME-0ER- : X-ME-0R- : X-M-E : X-M-E : X-M-ER : X-M-E- 0: X-M-E- : X-M-ER- : X-M-R : X-ME-E : X-ME-E 0: X-ME-ER : X-ME-E- : X-ME-E- : X-ME-ER- 0: X-ME-R : X-M-E : X-M-E 0: X-M-ER : X-M-E- : X-M-E- : X-M-ER- : X-M-R : X-ME-E : X-ME-E 0 ell continued on next page RX User Manual, rd Edition, Rev. -

12 ppendix : odes and System s 0 Numeric s w/system-ssigned Nicknames (continued) Numeric Nickname Type escription ST $POMIpSetupSrc onfiguration ell continued from previous page : X-ME-ER : X-ME-E- 0: X-ME-E- : X-ME-ER- : X-ME-R The X-P-EOMLT POM requires functional IP ddressing information to operate on an Ethernet network. ecause the EOMLT can be hot-swapped into an operating RX PU, you have the option of specifying where the IP ddressing for the EOMLT resides: Use the IP ddressing information that was statically assigned by NetEdit. In this mode the EOMLT operates like a traditional EOM. ny EOMLT that is installed will temporarily use the IP ddressing information that has been provided in the System onfiguration. If the EOMLT already has a statically assigned IP address that information will not be used. This will allow any external network connection - like o-more! esigner - to operate with any EOMLT that is installed in this RX PL, because the RX PU will assign the IP address. Overwrite the existing IP ddressing information in ROM of the EOMLT with the values from ST, ST, and ST, then use the newly written values. Specifies the source for the TP/IP configuration for the EOMLT POM (value in the least significant byte): 0: uses the IP ddress information in the X-P-EOMLT POM; also stores a copy of that information in the ST, ST, and ST. : ignore values from ST, ST, ST; do not write values from ST, ST, and ST to the EOMLT. : ignores any existing IP addressing information in the EOMLT and uses the values currently stored in ST, ST, and ST. : overwrite the IP ddressing information in ROM of the EOMLT with the values from ST, ST, and ST. ST will change to 0 after the ROM update is complete. The steps to manually change from the default mode of 0 in ST to using a given IP configuration are as follows: Write a value of to ST to get the EOMLT to ignore values from the EOMLT. fter delaying for a few milliseconds (in case the EOMLT was already is in the process of writing the values) write the new IP ddressing information to ST, ST, and ST. Then write a value of to ST to instruct the EOMLT to update it s ROM with the new values. ST will return to a value of 0 when the process is complete. - : Reserved. : EOMLT reporting an error in high Word of ST ST $POMIpddress onfiguration The IP ddress of the X-P-EOMLT POM that is installed. ST $POMIpNetmask onfiguration The Netmask of the X-P-EOMLT POM that is installed. ST $POMIpGateway onfiguration The Gateway ddress of the X-P-EOMLT POM that is installed. ST $Programhecksum -bit value that is the checksum of the current program data. ST $TimeZone (signed integer in minutes) ST $WatchdogReboots Status onfiguration ontains the number of minutes to apply to the UT value for the current location of the PL. The number of hardware and / or software watchdog reboots that have occurred since the last power-cycle. Each time the PU watchdog fires it will increment the value. When this value reaches 0 it will drop the PL into Program mode on the next restart. This is to prevent the PU from getting stuck in an unrecoverable crash loop. ST $FailedLoginnt Status The number of login attempts that have failed. - RX User Manual, rd Edition, Rev.

13 ppendix : odes and System s Numeric s w/system-ssigned Nicknames (continued) Numeric Nickname Type escription ST $ProductI onfiguration ST $ProductVersion onfiguration ST0 $ModehngFailed Status n -digit Hex value that is used by Generate MLoader Image and MLoader to validate the target PU before downloading the contents of the image file. n -digit Hex value (MMmm - where MM is the major version, mm is minor version and is the build number) that is used by Generate MLoader Image and MLoader to validate the target PU before downloading the contents of the image file. If an attempt to transition between PL modes is successful this register will contain 0. If an attempt to transition between PL modes fails, this location will contain one of the following failure codes: 00 - low level hardware initialization failed 0 - one or more modules failed to verify for longer than the verify filter time, and the system is in a permanent I/O shutdown. Power cycle or Re-Initialize I/O required to return to RUN mode 0 - there is an error in the manual I/O map 0 - there is an error in the manual I/O configuration 0 - the attempt to initialize the local I/O failed 0 - one or more Ethernet I/O Slaves is offline 0 - the Ethernet I/O Master failed to initialize 0 - an invalid instruction was downloaded to the PU 0 RX User Manual, rd Edition, Rev. -

14 ppendix : odes and System s 0 Notes: - RX User Manual, rd Edition, Rev.