EBus Error Behaviour
This parameter is used to set the reaction to an EtherCAT error. The following options are available:
Legacy | Output data is still written, input data is frozen and therefore no longer current. |
Set IOs to 0 | Output data is written to zero; input data is written to zero; when the E-bus is error-free, it automatically starts the data exchange. |
Set IOs to 0 without EBus restart | Output data is written to zero; input data is written to zero; when the E-bus is error-free, it can be activated again via the record data (see below). |
Activation of EtherCAT following an EtherCAT error
Information about the EtherCAT state can be obtained in the DAP via the DWord "Status". As soon as an error is detected in the EtherCAT network, the bit EcFrameError is set (in the High Word Bitoffset x.2). If the error has been rectified and the EP9300-0022 is ready once again to start the EtherCAT communication, the bit EcFrameError is reset and the flag NeedEBusReset is set in the High Word Bitoffset x.4.
The reset is issued via Record Data Write and is structured as follows.
Profinet Record Data (Write Request) | Value | Meaning |
---|---|---|
Slot | 0 | Slot number |
SubSlot | 1 | Sub slot number |
Index | 0x2013 | Index Reset |
Length | 2 | Data length |
Data | 0x1234 | Value |
Once the reset has been issued, the bit NeedEBusReset is reset.