nx interface
vacon • 19
24-hour s358 (0)40 837 1150 • Email: [email protected]
7
7.
CANOPEN-VACON NX INTERFACE
CanOpen communication objects transmitted via the CAN network are described by services and
protocols. They are classified as follows:
-
The real-time data transfer is performed by the Process Data Objects (PDOs) protocol
REAL-TIME CONTROL OF THE DRIVE
-
Service Data Objects (SDO) protocols provide the read and write access to entries of a device
object dictionary
CONFIGURATION OF THE DRIVE, READ/WRITE DRIVE PARAMETERS
-
The Network Management (NMT) protocols provide services for network initialization, error
control and device status control
START/STOP CANOPEN COMMUNICATION
7.1
CanOpen message frame
SOF
COB-ID
RTR
CTRL
Data Segment
CRC
ACK
EOF
1bit
11bit
1bit
5bit
0-8bytes
16bits
2bits
7bits
SOF Start of Frame
CRC Cyclic Redundancy Check
RTR Remote Transmission Request
ACK Acknowledge
CTRL Control Field (i.e. Data Length)
EOF End of Frame
COB-ID
The identification field of the CANopen-message is 11 bits.
ID-Bit
10
9
8
7
6
5
4
3
2
1
0
COB-ID
Function Code
Module-ID
The default identification field consists of a functional part and a module-ID part. The functional part
determines the object priority. This kind of identification field allows communication between a
master and 127 slaves. Broadcasting is indicated by a module-id of zero. Function codes are
determined with object dictionaries in device profiles.