Safety Manager Safety Manual - Tuv-fs.com

SafeNet communication
System response towards a safety related reset
The response to a safety related reset action depends on the QPP state of the
Control Processor. The following QPP states make the Control Processor respond
to a reset:
1. Running
The Control Processor is running without faults.
Initiating a reset will have no effect on the SM Controller state.
2. Running with Flt
The Control Processor is running with faults.
Initiating a reset will move the faults logged in the actual fault database to the
historical fault database (clearing the actual faults database) and log the reset.
3. CPReady (after startup or after recovering from a fault)
(Both Control Processors contain the same application.)
Initiating a reset, with a QPP in CPReady and identical applications residing
in CP1 and CP2, will start the application in the ready QPP.
4. CPReady (during an OLM procedure)
(Both Control Processors contain different applications.)
Initiating a reset with a QPP in CPReady and different applications in the
Control Processors (OLM) will cause an application switch-over from the
running Control Processor to the ready (idle) Control Processor.
5. Halt with Flt (during an OLM procedure)
(Both Control Processors contain different applications.)
The Control Processor was halted due to a fault detected during the OLM
compatibility check procedure. Initiating a reset will clear the fault database,
run a new diagnostic cycle and log the result in the fault database.
a. The QPP remains in the Halt with Flt state if faults are detected
during the diagnostic cycle;
b. The QPP goes to the CPReady (during OLM) state if no faults are
detected.
Safety Manager Safety Manual 45