![NANOTEC ELECTRONIC N5 Technical Manual Download Page 104](http://html.mh-extra.com/html/nanotec-electronic/n5/n5_technical-manual_705153104.webp)
Technical Manual N5 (CANopen)
8 CANopen
Default CAN-ID
Service
Description in
300
h
+Node-ID
RX Process Data Objects (PDO)
380
h
+Node-ID
TX Process Data Objects (PDO)
400
h
+Node-ID
RX Process Data Objects (PDO)
480
h
+Node-ID
TX Process Data Objects (PDO)
500
h
+Node-ID
RX Process Data Objects (PDO)
580
h
+Node-ID
TX Service Data Objects (SDO)
600
h
+Node-ID
RX Service Data Objects (SDO)
Section Service Data Object (SDO)
700
h
+Node-ID
BOOT-UP Protocol
Section Boot-Up Protocol
700
h
+Node-ID
Nodeguarding and Heartbeat
Section Heartbeat and nodeguarding
8.2.1 Network Management (NMT)
Network Management is oriented towards CANopen devices and follows a master-slave structure.
NMT requires a CANopen device in the network that performs the role of the CANopen master. All
other devices have the role of the NMT slave. Each NMT slave can be addressed via its individual
node-ID in the range from [1–127]. NMT services can be used to initiate, start, monitor, reset or stop
CANopen devices.
In doing so, the controller follows the state diagram shown in the following figure. The "Initialization"
state is only reached after switching on or by sending a "Reset Communication" or "Reset Node" NMT
command. The "Pre-Operational" state is automatically activated after initialization.
Shown in the following table is an overview of the activity of the services in the respective states. Note
that the Stopped state stops communication completely and only permits controller of the NMT state
machine.
Service
Initializing
Pre-Operational
Operational
Stopped
PDO
Active
SDO
Active
Active
SYNC
Active
Active
EMCY
Active
Active
BOOT-UP
Active
NMT
Active
Active
Active
Version: 2.0.1 / FIR-v1650
104