2.7 Controller Diagnostic Alarms
These diagnostic alarms are common among Mark Controls Platforms. However, some alarms are not applicable to all
controller platforms.
0
Description Diagnostic Alarm Reset
20
Description ToolboxST application detects unhealthy link or loss of communication between [ ] and controller.
Possible Cause
• I/O pack configuration files missing
• I/O pack restarted or did not complete startup
• I/O pack configured for dual networks, but only one network is connected
• Network issue preventing connection to ToolboxST application
• Power failure to the I/O pack
• Terminal board Bar Code entered incorrectly in ToolboxST configuration
• Wrong terminal board is configured in ToolboxST application
• I/O pack or module plugged into wrong jack on terminal board, or wrong jack number in ToolboxST configuration
• I/O pack configured in ToolboxST application, but configuration not downloaded to the controller
• I/O pack in program mode
Solution
• Verify that the Ethernet cables and network switch are operating correctly.
• Verify that the I/O pack configuration (such as Type, HW Form, Bar Code, position) matches the actual hardware.
• Manually restart the I/O pack or module.
• If ToolboxST communication is working correctly, any additional diagnostics should indicate the cause of the problem.
• Build and download parameters to the I/O pack or module.
• Download firmware and parameters to the I/O pack or module.
• Build and download the configuration to the controller, wait for I/O pack communication status to change, then scan and
download to the I/O pack.
Note This alarm is not reported to the WorkstationST Alarm Viewer. This alarm is generated by the ToolboxST application,
not by the firmware.
40 GEH-6855_Vol_II GEH-6855_Vol_II Mark VIeS Functional Safety Systems Volume II
Public Information
To Next Page
Loading...
