Beckhoff EL6751 Documentation page 159

LWR telegram and the EtherCAT input data just before the start of the next task cycle with a LRD telegram.
A second alternative would be to allow the task (and hence the EtherCAT master) to run with half the cycle
time of the CAN interface cycle.
5.5.2.3 Object description – CAN interface
If the EL6751 is used as a CAN Layer-2 interface, the following objects are available:
Index (hex)
1000 [} 131]
1008 [} 131]
1009 [} 131]
100A [} 131]
1011 [} 132]
1018 [} 132]
10F0 [} 132]
10F2 [} 133]
1600 [} 160]
1685 [} 134]
1A00 [} 160]
1A85 [} 138]
1C00 [} 138]
1C12 [} 139]
1C13 [} 139]
1C32 [} 140]
1C33 [} 141]
6000 [} 161]
6001 [} 161]
7000 [} 161]
7001 [} 161]
8000 [} 162]
8001 [} 162]
F000 [} 149]
F108 [} 131]
F200 [} 153]
F800 [} 154]
5.5.2.3.1 Standard objects (0x1000-0x1FFF)
Here, only those objects that have a different meaning than in the CANopen master [} 131] are described.
EL6751
Parameterization and commissioning
Name
Device type
Device name
Hardware version
Software version
Restore default parameters
Identity
Backup parameter handling
Backup parameter storage
RxPDO-Map CAN Interface
RxPDO-Map CAN Control
TxPDO-Map CAN Interface
TxPDO-Map CAN Status
Sync manager type
RxPDO assign
TxPDO assign
Sm output parameter
SM input parameter
CAN Interface input (11-bit identifier)
CAN Interface input (29-bit identifier)
CAN Interface output (11-bit identifier)
CAN Interface output (29-bit identifier)
CAN interface configuration
CAN filter table
Modular device profile
CAN Status
CAN Control
CAN bus parameter
Version: 3.5 159