Get ctrlX SAFETY FSoE Diagnosis on ctrlX CORE

This function block can be used to perform an error analysis of FSoE communication between an FSoE master and an FSoE slave in the PLC. The function block also monitors the command of an FSoE connection. If the command has the value 54, the following data is correct.

If the command has the value 42, the following data contains an error code instead the datas:

0: strError:= 'Local reset or acknowledgement of a RESET command'
1: strError:= 'Unexpected command (INVALID_CMD)'
2: strError:= 'Unknown command (UNKNOWN_CMD)'
3: strError:= 'Invalid connection ID (INVALID_CONNID)'
4: strError:= 'CRC error (INVALID_CRC)'
5: strError:= 'Watchdog has expired (WD_EXPIRED)'
6: strError:= 'Invalid FSoE Slave Address (INVALID_ADDRESS)'
7: strError:= 'Invalid safety data (INVALID_DATA)'
8: strError:= 'Invalid communication parameter length (INVALID_COMMPARALEN)'
9: strError:= 'Invalid communication parameter data (INVALID_COMPARA)'
10: strError:= 'Invalid application parameter length (INVALID_USERPARALEN)'
11: strError:= 'Invalid application parameter data (INVALID_USERPARA)'

If an error occurs, it is entered in a logbook with a time stamp.  The Loogbook can be analysed as internal instance Array arErrorLog, the TimeStamps are a different Array arErrorLogDateTime with the same Index.

This Functionblock can also be used to analyse the actual FSoE Cycletime between FSoE Master and FSoE Slave. This can be helpfull for configure the FSoE-Devices with the right FSoE Watchdog value. But the configured value should be higher as the monitored value of this Functionblock.
To determine the most accurate FSoE cycle time, the function block should be called up in the fastest possible task.
If it is only to record and save error entries, the task in which the function block is called can run significantly slower

In this example, there is an FSoE connection between 2 ctrlX SAFETY control units. One SAFEX is the FSoE master and one is the FSoE slave.

The FSoE command, the address %IB0, is monitored on the FSoE Master connection1. (direction FSoE master to FSoE slave).
The FSoE data , the address %IB1, is monitored on the FSoE Master Connection1.
The FSoE CRC (checksum), the address %IW4, is monitored on the FSoE Master Connection1.