FSoE – Status and Diagnosis

States of the FSoE communication and problems which the safety controller has detected can be diagnosed at the output DiagCode of the driver function block (see below).

Diagnostic code

The diagnosis is divided into two categories:

16#8xxx for states of communication with transmission (see States of communication with transmission
16#Cxxx error states (see Error states)

States of communication with transmission

The diagnostic code can have the following values in the states of communication with transmission:

DiagCode = 16#80xx, contains the state of the FSoEMaster

State	Values for xx	Description
`Reset`	`16#64`	The connection is reset (outputs are in the safe state).
`Session`	`16#65`	The `Session ID` is transmitted (outputs are in the safe state)
`Connection`	`16#66`	The connection ID is transmitted (outputs are in the safe state)
`Parameters`	`16#67`	The parameters are transmitted (outputs are in the safe state)
`Data`	`16#68`	Process data or substitute values are transmitted. `S_ActivateOut` = `TRUE`: Transmit process data `S_ActivateOut` = `FALSE`: Transmit substitute values

Error states

If there are two errors in the FSoEMaster at the same time, then only the error with the highest priority is shown. The priorities of the errors are assigned according to the error category:

1st error category: DiagCode = 16#C0xx, initialization error
2nd error category: DiagCode = 16#C1xx, receiver error master
3rd error category: DiagCode = 16#C2xx, errors reported from the Safety Device

Initialization error

Diagcode = 16#C0xx, xx contains an additional error-specific error code

Values for xx	Description
`16#01-16#04, 16#06-16#0A`	Internal errors
`16#05`	Length of safe data is not supported (max. 32 byte data is supported)
`16#0B`	Invalid watchdog time; value 0 (parameter WatchdogTime) is not permitted
`16#0C`	Internal error, invalid logical module ID

Error detection of the FSoEMaster

Basis: [N3.5.4]

DiagCode = 16#C1xx, xx contains an additional error-specific error code

Values for xx	Description
`16#00`	Local reset or acknowledgement of a reset command
`16#01`	Unexpected command in the received telegram
`16#02`	Unknown command in the received telegram
`16#03`	Invalid `Connection ID` in the received telegram
`16#04`	CRC error for the received telegram
`16#05`	Watchdog error; no valid telegram received within the watchdog time
`16#07`	Invalid safety data in the received telegram
`16#FE`	Error reset signal
`16#FF`	Prompt for acknowledging the restart

Error – feedback signal from the Safety Device (Slave)

DiagCode = 16#C2xx, xx contains an additional error-specific error code

Values for xx	Description
`16#00`	Local reset or acknowledgement of a reset command
`16#01`	Unexpected command in the received telegram
`16#02`	Unknown command in the received telegram
`16#03`	Invalid `Connection ID` in the received telegram
`16#04`	CRC error for the received telegram
`16#05`	Watchdog error; no valid telegram received within the watchdog time
`16#06`	Invalid FSoE Safety Device Address
`16#07`	Invalid safety data in the received telegram
`16#08`	Invalid communication parameter length
`16#09`	Invalid communication parameter data
`16#0A`	Invalid application parameter length
`16#0B`	Invalid application parameter data
`16#80-16#FF`	Invalid device-specific safety-oriented parameters