3 parameterising the controller as can master, Parameterising the controller as can master, 12 system bus "can on board – Lenze 8400 TopLine User Manual
Page 763
![background image](/manuals/566308/763/background.png)
Lenze · 8400 TopLine · Reference manual · DMS 6.0 EN · 06/2014 · TD05/TD14
763
12
System bus "CAN on board"
12.7
Communication phases/network management
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
12.7.3
Parameterising the controller as CAN master
If the initialisation of the system bus and the associated status change from "Pre-Operational" to
"Operational" is not effected by a superimposed host system, the controller can instead be defined
to be a "quasi" master to execute this task.
The controller is configured as CAN master in
• Being the CAN master, the controller sets all nodes connected to the bus (broadcast telegram)
to the "Operational" communication status with the "Start remote node" NMT telegram. Only
in this communication status, data can be exchanged via process data objects.
• A delay time can be set in
which must expire after mains switching before the
controller transmits the "Start remote node" NMT telegram.
Tip!
Master functionality is only required during the initialisation phase of the drive system.
Parameter
Info
Lenze setting
Value Unit
CAN slave/master
Slave
CAN delay boot-up - Operational
3000 ms
Note!
The changes of the master/slave operation in
will not be activated until
• another mains switching of the controller
or
• the "Reset node" or "Reset communication" NMT telegram has been transmitted to
the controller.
The "CAN reset node" device command (
) is provided as an alternative to the
"Reset node" NMT telegram for the reinitialisation of the CAN-specific device
parameters.