• Home
• Function/Function Block Reference
• Diagnostic FBs for safety-related Up-/Downstream Communication
• FSoE_F_Addr_Diagnostic

FSoE_F_Addr_Diagnostic

Type	Function block
Description	The function block is used to diagnose downstream FSoE F-connections. The FB can be used as an alternative to the corresponding F-diagnostic variables FSOE_MSTR_ADDR_[nnnnn]_ACK_REQ (acknowledgement required) or FSOE_MSTR_ADDR_[nnnnn]_ACK_REI (perform an acknowledgment). (For the variables, nnnnn corresponds to the FSoE F-address.) The FB reads the output interface data of an FSoE-Master instance and shows them as 16 bit value at its output formal parameter FSoE_Diag_Status. This way, a required acknowledgement can be indicated. Via the input formal parameter FSoE_Diag_Control, the 16 bit input interface data of the FSoE-Master 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). One instance of this function block can only ever be used for one point-to-point downstream F-connection. 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 FSoE_F_Global_Diagnostic FB is available which can be used to diagnose all parameterized F-downstream connections.
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 FSoE 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. Reparameterization at runtime is not permitted and is not accepted by the FB. 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 and the FSoE F-address is read from input F_Address_In and permanently stored in the FB. The other inputs are then evaluated and the outputs are switching accordingly. F_Address_In Short description Value Input for specifying the FSoE F-address. Data type: WORD Initial value: 0x0000 F-address of the downstream FSoE F-connection to be diagnosed. Value range: 0x0001 to 0xFFFE FSoE_Diag_Control Short description Value Input bit field (16 bits) for controlling the interface data of an FSoE-Master 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. In the following table, the value nnnnn represents the value in F_Address_Out. Bit pos. x Corresponding system variable Meaning/name in the FSoE profile Bit 0 FSOE_MSTR_ADDR_[nnnnn]_ACK_REI Confirm a communication error. Bit 1 FSOE_MSTR_ADDR_[nnnnn]_PASS_ON The corresponding FSoE instance sends fail-safe values. Bits 3 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. If the FB initialization was successful, the value applying at F_Address_In is now mirrored at F_Address_Out. F_Address_Out Short description Value Output for displaying the mirrored FSoE F-address of the downstream FSoE F-connection. Data type: WORD After successful initialization (by a rising edge FALSE > TRUE at Activate), the address of the F-downstream connection present at input F_Address_In is mirrored here (value range 0x0001 to 0xFFFE). Otherwise the value 0x0000 is output. FSoE_Diag_Status Short description Value Mapped diagnostic information (bit field, length 16 bits) output by an FSoE 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. In the following table, the value nnnnn represents the value in F_Address_Out. Bit pos. x Corresponding system variable Meaning/name in the FSoE profile Bit 0 FSOE_MSTR_ADDR_[nnnnn]_ACK_REQ The value TRUE indicates that a previously occurring FSoE communication error has been rectified and can be acknowledged by the user. Bit 1 FSOE_MSTR_ADDR_[nnnnn]_PASS_OUT If TRUE, the FSoE-instance delivers fail-safe values instead of valid process data. Bit 2 reserved reserved Bit 3 reserved reserved Bit 4 reserved reserved Bit 5 FSOE_MSTR_ADDR_[nnnnn]_CE_CRC If TRUE, the FSoE instance has detected and reported a CRC error. Bit 6 FSOE_MSTR_ADDR_[nnnnn]_WD_TIMEOUT If TRUE, the FSoE instance has detected and reported a watchdog timeout. Bit 7 reserved reserved Bit 8 reserved reserved Bit 9 reserved reserved Bit 10 FSOE_MSTR_ADDR_[nnnnn]_COMM If TRUE, the FSoE instance has detected and reported a communication error. Bits 11 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_Address_Out = 0x0000 » FSoE_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. A valid F-address is present at the F_Address_In input. No other FB instance has already been initialized with this F-address. The FB can only be successfully initialized if all three checks are successful. Output values: » Ready = TRUE » F_Address_Out = F_Address_In if initialized. Otherwise 0x0000. » FSoE_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. The address at input F_Address_In has been accepted and this address value is now also present at output F_Address_Out. Output values: » Ready = TRUE » F_Address_Out = F_Address_In » FSoE_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. C000 State name: Error invalid F-Address Invalid FB configuration: The FB has detected an invalid value at input F_Address_In (0x0000 or 0xFFFF). Output values: » Ready = TRUE » F_Address_Out = F_Address_In if initialized. Otherwise 0x0000. » FSoE_Diag_Status = 0x0000 » Error = TRUE » DiagCode = 0xC000 Check the application program with regard to the invalid value at the FB input. Correct/modify accordingly. Rebuild the project in PLCnext Engineer. Write the modified project to the controller and perform a restart. C001 State name: Error F-Address not found Invalid FB configuration: The address value at input F_Address_In could not be found in the configuration of the Safety PLC. Output values: » Ready = TRUE » F_Address_Out = F_Address_In if initialized. Otherwise 0x0000. » FSoE_Diag_Status = 0x0000 » Error = TRUE » DiagCode = 0xC001 Check the application program with regard to the wrong value at the FB input. 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: The address value at input F_Address_In is already used with another instance of the FB. Output values: » Ready = TRUE » F_Address_Out = F_Address_In if initialized. Otherwise 0x0000. » FSoE_Diag_Status = 0x0000 » Error = TRUE » DiagCode = 0xC002 Check the application program with regard to the address value at the FB input used twice. 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 FSoE_Diag_Control in bit 0 (OA_C), although no acknowledgement was requested in output FSoE_Diag_Status in bit 0 (OA_Req_S). At input FSoE_Diag_Control, bit 0 (OA_C) was not reset after acknowledgement, and a new acknowledgement was requested via output FSoE_Diag_Status in bit 0 (OA_Req_S). Output values: » Ready = TRUE » F_Address_Out = F_Address_In if initialized. Otherwise 0x0000. » FSoE_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. C004 State name: Error F-Address changed The address value in F_Address_In has changed after the activation of the FB. Output values: » Ready = TRUE » F_Address_Out = F_Address_In if initialized. Otherwise 0x0000. » FSoE_Diag_Status = 0x0000 » Error = TRUE » DiagCode = 0xC004 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_Address_Out = F_Address_In if initialized. Otherwise 0x0000. » FSoE_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_Address_Out = F_Address_In if initialized. Otherwise 0x0000. » FSoE_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.