Objects 0X1C32 And 0X1C33; Figure 41: Overrun Counter In Subindex 11 - WAGO I/O-SYSTEM 750 Manual

102 Function Description
7.4.3

Objects 0x1C32 and 0x1C33

Objects 0x1C32 and 0x1C33, shown in the following table, control which
synchronization process is used by the slave to read its inputs and outputs and to
exchange data with the EtherCAT
The EtherCAT
access on Sync Manager 2 so that a local bus cycle is initiated by the arrival of
new output data.
If the EtherCAT
discarded and input data transmitted multiple times unchanged. This is called a
cycle time overrun or a local bus overrun.
Additional information about cycle time overruns
You can read about cycle time overruns in more detail in "Function
Description" > "Data Exchange" > "Control of the Process Images" >
"Behavior of the Fieldbus Controller in Cycle Time Overruns".
The minimum EtherCAT
causing an appreciable number of local bus overruns (Assuming no CoE access
and no I/O module diagnostics) is specified in each case in subindex 5 of both
objects.
If new output data are written while a local bus cycle is running, then the counter
in SI11 is increased. Any further writings of output data during this local bus cycle
do not lead to increases in the counter. The counter is increased again only by a
new overrun in the next local bus cycle.
The following figure shows this by means of an example in which the local bus
cycle time is two and a half times that of the EtherCAT

Figure 41: Overrun Counter in Subindex 11

Manual
Version 1.2.1
750-354/000-001 EtherCAT® Fieldbus Coupler, ID Switch

fieldbus.

fieldbus coupler synchronizes the local bus cycles to the write
®
cycle is faster than the local bus cycle, the output data is

cycle time that supports the fieldbus coupler, without
WAGO-I/O-SYSTEM 750

cycle time.