PROFIsafe_F_Global_Diagnostic

Type Function block

Description The function block is used to diagnose all downstream parameterized F-connections.
The FB can be used as an alternative to the corresponding F-diagnostic variables ACK_REQ_GLOBAL (acknowledgement required) and ACK_REI_GLOBAL (perform an acknowledgment). These variables summarize the F-connection-related individual diagnostic variables for all configured F-Devices.
The FB reads the output interface data of an F-Host instance and shows them as 16 bit value at its output formal parameter F_Diag_Status. This way, a required acknowledgement can be indicated. Via the input formal parameter F_Diag_Control, the 16 bit input interface data of the F-Host instance can be written and thus controlled. This way, acknowledging of diagnostic messages is possible.
The FB can only be used in the user program if no F-diagnostic variables are parameterized in the Safety PLC (observe the section "Notes" below).
The function block is activated by a rising edge Activate = FALSE > TRUE. If an error occurs during the execution of the function block, Error is set to TRUE. The DiagCode output indicates the current FB status.

Note
In addition, the PROFIsafe_F_Addr_Diagnostic FB is available which can be used to diagnose one particular F-downstream connection.

Block Icon

Notes

Important: The use of the FB described here and the corresponding system variables for F-diagnostics are mutually exclusive!
The function block can only be used in the safety-related application program if no F- diagnostic variables are parameterized in the Safety PLC. This applies regardless of the protocol used. As soon as one PROFIsafe F-diagnostic function block is activated, the use of the diagnostic system variables is blocked and they can no longer be used, even if the function block is deactivated again. In order to be able to use the diagnostic system variables again, the function blocks must be deactivated and the user program must be rewritten onto the controller. If at least one system variable has been parameterized for F-diagnostics and a function block is active at the same time, the function block goes into the error state. An error code is output at DiagCode and the function block remains in the error state until the user program is reloaded onto the controller.

Exactly one instance of this function block can be used in a project.

Function blocks of this type have to be instantiated. The instance name of the function block has to be declared in the 'Variables' table of the POU where the FB is going to be used. The instance name must be unique within the POU.

Parameters Input
Activate

Short description Value

Edge-controlled input for initializing and activating the function block.
Data type: BOOL
Initial value: FALSE

FALSE: Function block is inactive.

Edge FALSE > TRUE: Function block is activated. The input F_Diag_Control is then evaluated and the outputs are switching accordingly.

F_Diag_Control

Short description Value

Input bit field (16 bits) for controlling the interface data of an F-Host instance.
Data type: WORD
Initial value: 0x0000 The value TRUE at bit position x means that the corresponding diagnostic acknowledgement is triggered. The meaning of the bit positions are described in the table below.

Bit pos. x Corresponding system variable Meaning/name in the PROFIsafe profile

Bit 0 ACK_REI_GLOBAL OA_C, confirm a communication error for all local F-Hosts, if possible (edge-controlled).
Acknowlegding is only possible after a rising edge in ACK_REQ_GLOBAL (Bit 0 in F_Diag_Status).

Bit 1 reserved reserved

Bit 2 reserved reserved

Bit 3 CHF_ACK_REI_GLOBAL ChF_Ack_C, local F-Host confirms a channel fault, if possible.

Bits 4 to 15 reserved reserved

Outputs
Ready

Short description Value

Output for signaling "Function block activated/not activated".
Data type: BOOL

FALSE: Function block is not activated.

TRUE: Function block is activated.

F_Diag_Status

Short description Value

Mapped diagnostic information (bit field, length 16 bits) output by the F-host instance. This status word provides information about which detected errors can be acknowledged.
Data type: WORD
Initial value: 0x0000 The value TRUE at bit position x indicates the presence of a corresponding diagnostic message. The meaning of the bit positions are described in the table below.

Bit pos. x Corresponding system variable Meaning/name in the PROFIsafe profile

Bit 0 ACK_REQ_GLOBAL OA_Req_S, indication that at least one communication error can be acknowledged.

Bit 1 PASS_OUT_GLOBAL FV_activated_S, at least one remote F-Device delivers/writes fail-safe values.

Bit 2 reserviert reserviert

Bit 3 CHF_ACK_REQ_GLOBAL ChF_Ack_Req_S, at least one remote F-Device indicates that a channel error can be acknowledged.

Bit 4 DEVICE_FAULT_GLOBAL Device_Fault, at least one remote F-Device reports a device fault.

Bit 5 CE_CRC_GLOBAL CE_CRC, at least one remote F-Device reports a detected CRC error in the output telegram.

Bit 6 WD_TIMEOUT_GLOBA WD_timeout, at least one remote F-Device reports a watchdog timeout.

Bit 7 CE_CRC_H_GLOBAL CE_CRC, at least one local F-Host reports a detected CRC error in the input telegram.

Bit 8 WD_TIMEOUT_H_GLOBAL WD_timeout, at least one local F-Host reports a watchdog timeout.

Bit 9 LOOPBACK_GLOBAL Loop-back error, at least one local F-Host reports a routing error of an outgoing message.

Bits 10 to 15 reserved reserved

Error

Short description Value

Output for error message.
Data type: BOOL

FALSE: No error is present (that is to say, the FB is not in an error state) or the FB is not active.

TRUE: The function block has detected an error. The error state is shown at the DiagCode output.

DiagCode

Short description Value

Output for diagnostic message.
Data type: WORD Diagnostic message of the function block.
The possible values are listed and described in the following table row "Diagnostic codes".

Diagnostic codes The DiagCode output indicates the current FB status. While an error is indicated, this is the error code.
Table with diagnostic codes

Code (hex) Description Options for remedy

0000 State name: Idle
The function block is not activated. The Activate input is FALSE.
Output values:
» Ready = FALSE
» F_Diag_Status = 0x0000
» Error = FALSE
» DiagCode = 0x0000 Activate the function block by switching Activate to TRUE.

8001 State name: Init
The FB verifies the following:

No F-diagnostic variables are parameterized in the Safety PLC.

No other instance of the same FB has already been initialized in the project.

The FB can only be successfully initialized if both checks are successful.
Output values:
» Ready = TRUE
» F_Diag_Status = 0x0000
» Error = FALSE
» DiagCode = 0x8001 No measures required after successful initialization.
If the initialization fails:

Check the application program and the configuration of the Safety PLC.

Correct/modify accordingly.

Rebuild the project in PLCnext Engineer.

Write the modified project to the controller and perform a restart.

8000 State name: Success
The FB is active.
Output values:
» Ready = TRUE
» F_Diag_Status = interface data (OUT)
» Error = FALSE
» DiagCode = 0x8000 If this is an intended event, no measures are required.
If this is an unintentional event:

Check the application program and the configuration of the Safety PLC.

Correct/modify accordingly.

Rebuild the project in PLCnext Engineer.

Write the modified project to the controller and perform a restart.

C002 State name: Error double instance
Invalid FB configuration: An instance of the same FB has already been created or activated.
Output values:
» Ready = TRUE
» F_Diag_Status = 0x0000
» Error = TRUE
» DiagCode = 0xC002

Check the application program with regard to other FB instance.

Correct/modify accordingly.

Rebuild the project in PLCnext Engineer.

Write the modified project to the controller and perform a restart.

C003 State name: Error OA_C active
This error can have the following causes:

After the activation of the FB, a rising edge was detected at input F_Diag_Control in bit 0 (OA_C), although no acknowledgement was requested in output F_Diag_Status in bit 0 (OA_Req_S).

At input F_Diag_Control, bit 0 (OA_C) was not reset after acknowledgement, and a new acknowledgement was requested via output F_Diag_Status in bit 0 (OA_Req_S).

The same also applies to bit 3 (ChF_Ack_C) in input F_Diag_Control in conjunction with output F_Diag_Status bit 3 (ChF_Ack_Req_S).

Output values:
» Ready = TRUE
» F_Diag_Status = 0x0000
» Error = TRUE
» DiagCode = 0xC003

Check the application program.

Correct/modify accordingly.

Rebuild the project in PLCnext Engineer.

Write the modified project to the controller and perform a restart.

C005 State name: Error Diag variables active
F-diagnostic variables are parameterized in the Safety PLC.
Output values:
» Ready = TRUE
» F_Diag_Status = 0x0000
» Error = TRUE
» DiagCode = 0xC005

Check the application program.

Correct/modify accordingly.

Rebuild the project in PLCnext Engineer.

Write the modified project to the controller and perform a restart.

C006 State name: Error Write output
Internal firmware error. In this case, the firmware of the Safety PLC assumes the fail-safe state.
Output values:
» Ready = TRUE
» F_Diag_Status = 0x0000
» Error = TRUE
» DiagCode = 0xC006 Refer to the error reported in PLCnext Engineer. The error log of the Safety PLC can be read out and displayed in the Safety Cockpit.