Lenze ECSCSxxx - Manual (Page 446)

Appendix
Communication with MotionBus/system bus (CAN)
Communication phases of the CAN network (NMT)
13
l
446 EDBCSXS064 EN 4.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
Only contains command
2 bytes
Fig. 13−3 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!
Only a change to "Operational" status enables communication via the process
data!
Example:
If all nodes connected to the bus are to be switched from the
"Pre−Operational" communication status to the "Operational" communication
status via the CAN master, the identifier and the user data must have the
following values in the transmission telegram:
ƒ Identifier: 0x00 (broadcast telegram)
ƒ User data: 0x0100