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 controller is put into the FAILURE control state.
Solution Replace the controller.
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, controller put in FAILURE
control state.
Solution
• Ignore this alarm if it occurs during a restart of the controller.
• If the alarm occurs during normal operation, then replace the controller.
359
Description Internal Runtime error - Sequencer client execution overrun
Possible Cause Possible hardware malfunction. Sequencer critical client overrun detected. Alarm occurs after a
sequencer critical client has been run faster than its nominal rate three times in a row; after five, controller put in FAILURE
control state.
Solution
• Ignore alarm if it occurs during a restart of the controller.
• Replace the controller, if the alarm occurs during normal operation.
360
Description Internal Runtime error - Sequencer frame period out-of-bounds (±15%)
Possible Cause Possible hardware malfunction. Frame period greater than ±15% of nominal. Alarm occurs following
frame period out-of-bounds condition occurring three frames in a row; after five, controller put in FAILURE control state.
Solution
• Ignore alarm if it occurs during a restart of the controller.
• Replace the controller, if the alarm occurs during normal operation.
56 GEH-6855_Vol_II GEH-6855_Vol_II Mark VIeS Functional Safety Systems Volume II
Public Information
To Next Page
Loading...
