Lenze ECSCPxxx - Manual (Page 273)

Configuration
Configuring MotionBus/system bus (CAN)
Defining boot−up master in the drive system
8
l
273 EDBCSXP064 EN 8.0
8.1.3 Defining boot−up master in the drive system
If the bus initialisation and the related state change from "Pre−Operational" to
"Operational" is not carried out by a higher−level host system (PLC), another node can be
determined as boot−up master to carry out this task.
The master functionality only is required for the initialisation phase of the drive system. A
boot−up time for the master in the initialisation phase can be set via C0356/C2456
(
¶ 274).
By means of the NMT telegram start_remote_node (broadcast telegram) all nodes are
shifted to the NMT−state "Operational" by the master. A data exchange via the process
data objects can only be effected in this state.
Use C0352/C2452 for configuration.
Code Possible settings IMPORTANT
No. Designation Lenze/
{Appl.} Selection
C0352 CAN mst 0 Boot−up master/slave
configuration for CAN bus
interface X4
^ 273
0 Slave
1 Master boot−up Device is active as CAN boot−up
master.
2 Master node guarding
3 Slave heartbeat producer
4 Slave node guarding
C2452 CANa mst 0 Configuration of master/slave
for CAN bus interface X14
(CAN−AUX) ^ 273
0 Slave
1 Master
Save changes with C0003 = 1.
The settings are only accepted after carrying out one of the following actions:
ƒ Renewed switch−on of the 24 V low−voltage supply
ƒ Reset node via the bus system (by the network management (NMT))
ƒ Variable CAN_bResetNode_b or CANaux_bResetNode_b = TRUE
ƒ Reset node with C0358/2458 = 1
)
Note!
If reset node is executed via GDC, communication will be interrupted. You
therefore have to log in again manually or find the devices connected to the
bus once again (fieldbus scan).