3 parameterising the controller as can master, Parameterising the controller as can master, 10 "can on board" system bus – Lenze E94AxPExxxx User Manual
Page 345
Lenze · 9400 Servo PLC· Reference manual · DMS 4.0 EN · 11/2013 · TD05/06
345
10
"CAN on board" system bus
10.5
Communication phases/network management
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
10.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
• 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.
• In
, you can set a delay time which must elapse after power-up before the controller
applies the "Start Remote Node" NMT telegram to the bus.
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.
As an alternative to the "Reset Node" NMT telegram, the device command
= "91:
CAN on board: Reset Node" can be used to reinitialise the CAN-specific device
parameters.