-

Diagnostic codes

The hexadecimal diagnostic codes listed here are output as WORD data type at the DiagCode output of the function block.

Code (hex)DescriptionOptions for remedy
0000The function block is not activated.Activate the function block by switching Activate to TRUE.
8000The function block has neither detected a status event nor an error in order to switch S_SafetyActive to SAFEFALSE.

Execution of the safety-related function in the connected periphery was requested (S_OpMode = SAFEFALSE).

The feedback signal connected to the S_Acknowledge input of the connected periphery was switched to SAFETRUE by the periphery.
If this is an intended event: No measure required.

If this is an unintended event:

  • Verify the safety-related functions.
  • Verify the safety-related code.
  • Verify the connected safety-related periphery.
8001The function block is activated. The mandatory start-up inhibit of the function block is active.Perform a reset on the function block to exit the active start-up/restart inhibit of the function block.
8002Execution of the safety-related function in the connected periphery is not requested at the S_OpMode input. The feedback signal of the periphery connected to the S_Acknowledge input does not confirm the defined safe state.If this is an intended event: No measure required.

If this is an unintended event: Switch the S_OpMode input to SAFEFALSE to control the safe mode of the periphery.
8003The defined safe state is requested at the S_OpMode input with a SAFEFALSE signal. This request is output at S_SafetyRequest. In order to forward the request of the defined safe state to the periphery, the S_SafetyRequest output must be connected to the periphery.

The feedback signal connected to the S_Acknowledge input in the connected periphery was not yet switched to SAFETRUE by the periphery.

By monitoring the time interval (value at MonitoringTime) between the request of the defined safe state and the acknowledged confirmation of the defined safe state, the function block detects the specified time being exceeded as an error.
If this is an intended event: No measure required.

If this is an unintended event:

  • Verify the safety-related functions.
  • Verify the safety-related program.
  • Verify the connected safety-related periphery.
8005Following a reset of the function block as a consequence of the function block error, the value SAFEFALSE is detected at the S_OpMode input. However, following an error message of the function block, the S_OpMode input must show the SAFETRUE state.Switch the S_OpMode input to SAFETRUE.
8012The defined safe state of the connected periphery is not requested. However, the feedback signal of the periphery connected to the S_Acknowledge input does confirm the defined safe state.
  • Verify the safety-related functions.
  • Verify the safety-related program.
  • Verify the connected safety-related periphery.
C002Once the defined safe state was confirmed by the connected periphery at the S_Acknowledge input, the value at S_Acknowledge changed.
  • Verify the safety-related functions.
  • Verify the safety-related program.
  • Verify the connected safety-related periphery.
C003The defined safe state of the connected periphery was requested at the S_OpMode input. The feedback signal of the periphery connected to the S_Acknowledge input did not respond within the time specified at MonitoringTime.
  • Verify the safety-related functions.
  • Verify the safety-related program.
  • Verify the connected safety-related periphery.
C004A permanent TRUE was detected at Reset.
  • Switch Reset = FALSE.
  • Verify the reset control device and its wiring.
C005A permanent TRUE was detected at Reset.
  • Switch Reset = FALSE.
  • Verify the reset control device and its wiring.
C006A permanent TRUE was detected at Reset.
  • Switch Reset = FALSE.
  • Verify the reset control device and its wiring.