EBus Error Behaviour
The parameter EBus error behavior is new in firmware version 8.
![EBus Error Behaviour 1:](Images/png/3743493387__Web.png)
This parameter is used to set the response to an E-bus 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). |
Activating the E-bus after an E-bus error
In the DAP, information about the E-bus is provided via the status DWord. When an error occurs in the E-bus, the bit EcFrameError is set (in the high word bit offset x.2). Once the error has been rectified and the coupler is ready to restart the E-bus, the bit EcFrameError is reset and the flag NeedEBusRese is set in the high word bit offset x.4.
![EBus Error Behaviour 2:](Images/png/3743496203__Web.png)
The reset is issued via record data 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 |
Lenght | 2 | Data length |
Data | 0x1234 | Value |
Once the reset has been issued, the bit NeedEBusReset is reset.