Configuration
Configuring MotionBus/system bus (CAN)
Defining boot−up master in the drive system
175
EDBCSXS064 EN 4.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 is only required for the initialisation phase of the drive system.
C0356 serves to set a boot up time for the master for the initialisation phase (
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.
The configuration is carried out via C0352.
Code
Possible settings
IMPORTANT
No.
Designation
Lenze/
{Appl.}
Selection
C0352 CAN mst
0
Boot−up master/slave
configuration for CAN bus
interface X4
175
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
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))
ƒ
Reset node with C0358 = 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).