17.03.2014 Views

DVP-ES2-EX2-SS2-SA2-SX2-Operation Manual

DVP-ES2-EX2-SS2-SA2-SX2-Operation Manual

DVP-ES2-EX2-SS2-SA2-SX2-Operation Manual

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

7 CANopen Function and <strong>Operation</strong><br />

The data format for RxPDO and TxPDO is as follows.<br />

COB-ID Byte 0 Byte 1 Byte 2 Byte 3 Byte 4 Byte 5 Byte 6 Byte 7<br />

Object<br />

identifier<br />

‣ SDO (service data object)<br />

The SDO is used to build the client/server relation between two CANopen devices. The<br />

client device can read the data from the object dictionary of the server device, and write the<br />

data into the object dictionary of the server device. The visit mode of the SDO is<br />

“client/server” mode. The mode which is visited is the SDO server. Every CANopen device<br />

has at least one service data object which provides the visit channel for the object<br />

dictionary of the device. SDO can read all objects in the object dictionary, and write all<br />

objects into the object dictionary.<br />

The SDO message contains the index information and the subindex information which can<br />

be used to position the objects in the object dictionary, and the composite data structure<br />

can easily pass the SDO visit. After the SDO client sends the reading/writing request, the<br />

SDO server replies. The client and the server can stop the transmission of the SDO .The<br />

requested message and the reply message are divided by different COB-IDs.<br />

The SDO can transmit the data in any length. If the data length is more than 4 bytes, the<br />

data has to be transmitted by segment. The last segment of the data contains an end flag.<br />

The structures of the SDO requested message and reply message are as follows.<br />

The format of the requested message:<br />

Data<br />

COB-ID Byte 0 Byte 1 Byte 2 Byte 3 Byte 4 Byte 5 Byte 6 Byte 7<br />

600(hex) Requested Object index<br />

+Node-ID code LSB MSB<br />

Object<br />

Requested data<br />

subindex bit7-0 bit15-8 bit23-16 bit31-24<br />

The definition of the requested code in the requested message:<br />

Request code<br />

(hex)<br />

Description<br />

23 Writing the 4-byte data<br />

2B<br />

2F<br />

Writing the 2-byte data<br />

Writing the 1-byte data<br />

40 Reading the data<br />

80 Stopping the current SDO function<br />

The format of the reply message:<br />

COB-ID Byte 0 Byte 1 Byte 2 Byte 3 Byte 4 Byte 5 Byte 6 Byte 7<br />

580(hex)<br />

+Node-ID<br />

Reply Object index<br />

code LSB MSB<br />

Object<br />

Reply data<br />

subindex bit7-0 bit15-8 bit23-16 bit31-24<br />

The definition of the reply code in the reply message:<br />

Reply code (hex)<br />

Description<br />

43 Reading the 4-byte data<br />

4B<br />

Reading the 2-byte data<br />

4F<br />

Reading the 1-byte data<br />

60 Writing the 1/2/4-byte data<br />

7-11

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!