Eaton XN-312-GW-CAN, Manual

Page: 23 / 388

1 XN-312-GW-CAN gateway
1.5 Important data for engineering
Gateway XN-312-GW-CAN 06/16 MN050003-EN www.eaton.eu
19
1.5 Important data for engineering
In connection with the I/O slice modules, the CAN gateway will appear as a
modular module on the field bus. This manual focuses on the CAN gateway
exclusively.
Each XN300 module is presented as a separate module, with its data, to the
field bus master.
The following is the maximum number of I/O slice modules that can be run
with the gateway:
Make sure to take the maximum volume of data that can be transmitted on
the field bus into account. The corresponding limit will be defined by the field
bus.
The following applies to CANopen: 4 TPDOs and 4 RPDOs with 8 bytes of
data each will be provided to each field bus module, i.e., a total of 32 bytes in
each direction. Additional COB-IDs can be used with an offset of 32, 64, and
96 bytes, meaning that a total of 4 * 32 = 128 bytes of payload data are avail-
able in each direction. This means that there are a max. of 16 TPDOs and
16 RPDOs available.
Another 8 TPDOs and 8 RPDOs, with 8 bytes of data each, are available per
direction. However, these objects will not be mapped automatically, and
need to be mapped manually instead. Accordingly, for each of the PDOs
from 17 through 24 that are in use, the user needs to enter a COB-ID that is
not yet being used in the system.
This means that the total number of TPDOs and RPDOs available is max.
24 TPDOs and 24 RPDOs.
Accordingly, 128 bytes + 64 bytes = 192 bytes of payload data are available
for each direction.
Gateway field bus
XN-312-GW-CAN CANopen, according to DS301.4 profile
Gateway Maximum number of I/O slice modules on the system bus
XN-312-GW-CAN 32
NOTICE
When using these COB-IDs, none of the modules used on the
same CAN network should have
Node ID of XN-312 g offset (32/64/96)
as this will result in frame collisions on the bus.
Field bus-slave Max. input data [Byte] Max. output data [Byte]
CANopen 128 128