351
Description Internal Firmware error - Thread [ ] timing overrun
Possible Cause An application task scheduled with a scan rate either occurred twice as fast or twice as slow as the
expected rate.
Solution
• Check the idle time on the I/O pack or module, and verify that the frame rate is correct.
• Reload the firmware and application code.
• If the problem persists, replace the I/O pack or module.
357
Description Internal Runtime error - Sequencer out-of-order or overrun detected
Possible Cause There is a possible hardware malfunction. Sequencer critical clients were scheduled out of order or were
overrun. This alarm occurs following three successive frames of sequencer critical client out-of-order detections. After five,
the I/O module is put into the FAILURE control state.
Solution Replace the I/O module.
358
Description Internal Runtime error - Sequencer client execution underrun
Possible Cause Possible hardware malfunction. Sequencer critical client underrun detected. Alarm occurs after a
sequencer critical client has been run slower than its nominal rate three times in a row. After five in a row, the I/O module is
put into FAILURE control state.
Solution
• Ignore alarm if it occurs during a restart of the I/O module.
• Replace the I/O module, if the alarm occurs during normal operation.
359
Description Internal Runtime error - Sequencer client execution overrun
Possible Cause Possible hardware malfunction. Sequencer critical client overrun detected. This alarm occurs after a
sequencer critical client has been run faster than its nominal, rate three times in a row. After five times in a row, the I/O
module is put into FAILURE control state.
Solution
• Ignore this alarm if it occurs during a restart of the I/O module.
• Replace the I/O module, if the alarm occurs during normal operation.
466 GEH-6855_Vol_II GEH-6855_Vol_II Mark VIeS Functional Safety Systems Volume II
Public Information
To Next Page
Loading...
