Lenze ECSEE012 - Page 81

Configuration
General information about the system bus (CAN)
Communication phases of the CAN network (NMT)
8

81
EDBCSXE040 EN 6.0
Network management (NMT)
The telegram structure used for the network management contains the identifier and the
command included in the user data which consists of the command byte and the node
address.
Identifier User data
Value = 0
11 bits
Contains commands only
2bytes
Fig. 8−4 Telegram for switching over the communication phases
The communication phases are changed over by a node, the network master, for the entire
network. The change−over can also be done by a controller.
With a certain delay after mains connection, a telegram is sent once which changes the
status of the entire drive system to "Operational". The delay time can be set via the
following codes:
Interface Code
X1 Automation interface (AIF) C2356/4
X4 ECSxS/P/M: MotionBus (CAN)
ECSxA/E: System bus (CAN)
C0356/4
X14 System bus (CAN)
l Interface is not available for ECSxE.
C2456/4
 Note!
Communication via process data only is possible with a state change to
operational"!
Example:
For changing the state of all nodes on the bus from "pre−operational" to
operational" via the CAN master, the following identifier and user data must
be set in the telegram:
ƒ Identifier: 00 (broadcast telegram)
ƒ User data: 0100 (hex)