14.2.22.3 Cause of controller failure
On a controller failure the alarm specifier provides information about the cause of the
failure
Name Code Description
REASON_UNKNOWN 0 The reason is unknown
ALARM_OVERFLOW 1 Overflow of interrupts
MESSAGE_QUEUE_OVERFLOW 2 Overflow of EtherCAT events
CYCLIC_FRAMES_NOT_IN_BUSCYCLE 3 EtherCAT receive telegram was not received within
the bus cycle time
APPL_BUSCYCLE_ERROR 4 Bus cycle time could not be fetched e.g. due to a
high system load
14.2.22.4 CoE emergency
A CoE emergency is a special type of mailbox communication in the EtherCAT slave.
Here the EtherCAT slave can signalise the EtherCAT master that an error has occurred. It
has the following structure:
Name Data type Description
Error Code WORD Error Code
Error Register BYTE EtherCAT state on the error of the salve
Data BYTE[5] Manufacturer Specific Error Field (MEF), contains
additional diagnostics data
14.2.22.5 AL Status Code
AL is the abbreviation for Application Layer. The AL status code is an error code of the
slave application.
14.2.22.6 Data structure BUS_STATE_CHANGED
Header
NrOfSlavesTotal - Number of slaves, which are not in master state
NrOfSlavesUndefined - Number of slaves in state undefined
NrOfSlavesInit - Number of slaves in state Init
NrOfSlavesPreop - Number of slaves in state PreOp
NrOfSlavesBoostrap - Number of slaves in state Bootstrap
NrOfSlavesSafeop - Number of slaves in state SafeOp
NrOfSlavesOp - Number of slaves in state Op
VIPA SPEED7
Integrated Standard
System Function Blocks > SFB 54 - RALRM - Receiving an interrupt from a periphery module
HB00 | OPL_SP7 | Operation list | en | 18-30 789
To Next Page
Loading...
