Lenze 8400 BaseLine C - Manual (Page 182)

9 System bus "CAN on board"
9.5 Communication phases/network management
182
Lenze · 8400 BaseLine C · Reference manual · DMS 1.6 EN · 01/2014 · TD05
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
9.5.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
C352 .
• 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 C356/1 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
C352 CAN slave/master Slave
C356/1 CAN delay boot-up - Operational 3000 ms

Note!
A change in master/slave operation in C352 will only become effective by
• renewed 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 ( C002/26 ) is provided as an alternative to the
"Reset node" NMT telegram for the reinitialisation of the CAN-specific device parame-
ters.