PROFIsafe Status and Diagnosis
Problems that the safety controller has detected can be diagnosed in three places:
Problems are reported to the PROFINET Host (master controller) by means of the usual PROFINET diagnostic mechanism with a diagnostic code.
In CODESYS, the diagnostic information is displayed as status messages on the Status tab of each F-Module. See Object: 'F-Device Module' (below the standard controller)
In the standard application, the diagnostic codes are available by means of the instance of the
ProfinetFDevice
function block. Every F-Module that is displayed in the device tree has a driver instance from the function blockProfinetFDevice
. For more information: see ProfinetFDevice (FB)
DiagCode | Description |
---|---|
Errors in the received F-Parameters I (standardized error codes): | |
| Discrepancy of the destination address |
| Invalid destination address |
| Invalid or non-matching source address |
| The watchdog time is 0 ms ( |
| The parameter |
| The parameter |
| The version of the F-Parameter is incorrect. |
| The data of the received F-Parameter blocks are inconsistent (CRC1 error). |
|
|
Errors in cyclic communication (standardized error codes): | |
| Transmission error: Data is inconsistent (CRC2 error) |
| Transmission error: Timeout ( |
Internal errors in the interface from safety controller to standard controller: | |
| The request for an IO Service could not be sent within the watchdog time. |
| The expected response for an IO Service was not received within the watchdog time. |
| The response for an IO Service has an invalid format or contains invalid data. |
Errors in the received F-Parameters II (CODESYS-specific error codes): | |
| The number of received F-Parameter bytes is invalid ( |
| Setting the F-Parameter is not supported by the module. |
For more information, see: ProfinetFDevice (FB)