20
Description ToolboxST application detects unhealthy link or loss of communication between [ ] and controller
Possible Cause
• I/O pack or module did not complete start up
• I/O pack or module configuration files missing
• I/O pack or module restarted
• I/O pack or module configured for dual networks, but only one network is connected
• Network issue preventing ToolboxST application connection
• Power failure to the I/O pack or module
• Terminal board barcode typed incorrectly in the ToolboxST configuration
• Wrong terminal board is configured in the ToolboxST application
• I/O pack or moduleis plugged into wrong jack on terminal board, or wrong jack number is configured in the ToolboxST
application
• I/O pack or module configured in ToolboxST application, but configuration not downloaded to the controller
• I/O pack or module in program mode
Solution
• If the ToolboxST communication is working correctly, any additional diagnostics should indicate the cause of the
problem.
• Perform a build and download parameters to the I/O pack or module.
• Download firmware and parameters to the I/O pack or module.
• 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.
• Perform a 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 I/O pack or module.
446 GEH-6855_Vol_II GEH-6855_Vol_II Mark VIeS Functional Safety Systems Volume II
Public Information