Eaton XC-CPU101 Series, Instruction Leaflet

Page: 74 / 96

Programming via CANopen
network (Routing)
12/14 MN05003004Z-EN
56
Alternatively, you can use the BlockSizeEditor application to
change the block size.
The download block size is defined in the following registry key:
[HKEY_LOCAL_MACHINE\SOFTWARE\3S-Smart Software Solutions
GmbH\Gateway Server\Drivers\Standard\Settings\Tcp/Ip (Level 2
Route)]
“Blocksize“=dword:00020000
The default block size is 20000
hex
(=128 Kbyte), the block size for
routing is 1000
hex
(= 4 Kbyte).
Notes
• If large files are written to the target PLC or read from the PLC,
it is possible that the online connection will be interrupted after
the transfer process has been completed. Renewed connection
is possible.
• If a program with a modified routing node ID is loaded into the
target PLC, the target PLC accepts the modified routing node ID;
however, the communication connection will be interrupted.
Reconnection with a corrected routing Node ID is possible.
• If a PLC receives a program without valid routing parameters
(Baud rate / Node ID), this PLC cannot be connected via a
routing connection.
• The routing is independent of the configuration (master/slave):
a target PLC that has not been configured as a master or as a
slave can be accessed. It must only receive the basic parameters
such as Node ID and baud rate, as well as a simple program.
Addressing
PLCs on the CAN-Bus can be configured as a master or as a slave.
The PLCs are assigned with a Node ID/node number (address) in
order to uniquely identify them (with the basis communication).
To use the routing function to access a target PLC, you must assign
a further routing ID to the routing and target PLC. An RS200 or
Ethernet interface can be used as a connection between the PC
and XC232 .
Table 12: Example for setting the Node Id, Baud rate
The Routing-ID of the master (XC100, XC200) can be set in the
PLC configurator under the “Other parameters” tab:
The ID for basis communication is defined in the “CanMaster”
folder in the “CAN parameters” tab (Figure 79).
Figure 77: Routing via XC…, EC4-200
a Ethernet connection only possible with XC200
PC
Routing control
(Master) Target controller
(Device)
Node-ID: 1
Routing ID: k Routing-ID n
Node-ID m
k, n, m = 2…127
RS232 Ethernet a CANopen
PLC Functio
n Node
ID Routing
ID Baud
rates
Se
e
?
i?
.
Routing
controller Master 1 127 125 KB 79
Target
controller Device 3 54 125 KB 80
h The following applies for device PLCs: The Routing-ID
must
not be equal to the Node-ID (Basis
communication)!
The exception is the XC100 with operating system f
V2.0: the Routing-ID must be equal to the Node-ID!
Figure 78: CAN Master routing settings (XC200)
Figure 79: CAN Master: Node ID for basis communication