HIMA HIQuad X - Behavior in the Event of Faults; Table 19: Operating System States, User Interventions

Product Description System
Page 56 of 110 HI 803 211 E Rev. 1.01.00
Table 19 specifies how the user may intervene during the corresponding states.
State
Possible user interventions
LOCKED
 Changing the factory settings.
 Using a PADT command to stop (STOP state).
 Using a PADT command to start (RUN state).
STOP/VALID
CONFIGURATION
 Loading the user program.
 Starting the user program.
 Loading the operating system.
 Taking preliminary actions for forcing variables.
STOP/INVALID
CONFIGURATION
 Loading the user program.
 Loading the operating system.
STOP/LOADING OS
None. Once the loading process is completed, the processor module
stops (STOP state).
RUN
 Stopping the user program.
 Forcing variables.
 Performing the test.
RUN/UP STOP
 Using a PADT command to stop (STOP state).
Table 19: Operating System States, User Interventions
i
The cycle time increases by the number of modules used in the system. This applies
irrespective of whether or not the modules are included in the configuration.
 Connecting additional extension racks with several modules during operation can
cause the watchdog time to be exceeded!
4.8.2 Behavior in the Event of Faults
If faults occur, the processor module enters the error stop state and tries to restart. It performs a
complete self-test which can also cause another error stop.
If a fault is still present, the module restarts with reduced functionality to prevent a reboot loop.
Once the processor module has properly run for one minute, the next error stop to occur is
considered the first error stop attempting a restart.
i
Use the PADT for troubleshooting and removing the cause of the fault, e.g., by loading a new
application.