Table of Contents
Advertisement
335
Description Memory Verification Failed – Firmware Processes
Possible Cause A modification has occurred in the code segment for one of the processes. This indicates that a hardware
memory failure has occurred.
Solution Replace the controller.
336
Description Controller is Unlocked
Possible Cause
•
Leaving Data Init control state and not locked
•
The controller is unlocked through the ToolboxST application.
Solution From ToolboxST application, lock the controllers before running safety functions.
337
Description Output exchange disagreement detected
Possible Cause IONet malfunction or hardware problem. For at least one output, a difference was detected between the
controller outputs. This alarm remains active until the controllers agree on all outputs. A difference for non-Boolean data
generally indicates a deviation of more than 10% from the median value or no IONet EGD configuration is present. For
median values near zero, the variation exceeds integer 2 or real value 0.2.
Solution
•
For the Mark VIe runtime, use the ToolboxST disagreement display (View | Disagreements) to determine which variables
are in disagreement.
•
In the application, avoid use of global variable 'ControllerID' and avoid the use of sequencing block 'USB_HB'.
•
Check IONet (switches, cables); rebuild and download application to all processors. If the problem persists, replace the
processor module.
347
Description Running Application does not match the Branded Application
Possible Cause Application not branded or different from branded version.
Note The purpose of branding is to label a verified safety application, and to ensure that it is running.
Solution
•
Reload the branded application to the controller and I/O packs.
•
Use the ToolboxST application to brand the currently running application.
Controllers
Public Information
GEH-6855_Vol_II System Guide 53
- Quick Links:
- Ucsc Controllers
Hide quick links:
Advertisement
Table of Contents
