BONFIGLIOLI Vectron Active Cube, User Manual

Page: 35 / 240

The following sequence of telegrams results:
Initiate SDO Upload
COB-ID 0 1 2 3 4 5 6 7
Request Client

Server
0x600 +
Node-ID
cs Index Subidx Daten
0x40 LSB
MSB 00 00 00 00
Response Server

Client
0x580 +
Node-ID
cs Index Subidx Daten
0x41 LSB MSB LSB … … MSB
Segment Upload, first and odd segments
COB-ID 0 1 2 3 4 5 6 7
Request Client

Server
0x600 +
Node-ID
cs Daten
0x60 00 00 00 00 00 00 00
Response Server

Client
0x580 +
Node-ID
cs Daten
0x00 LSB
… … … … … MSB
Segment Upload, second and even segments
COB-ID 0 1 2 3 4 5 6 7
Request Client

Server
0x600 +
Node-ID
cs Daten
0x70
00 00 00 00 00 00 00
Response Server

Client
0x580 +
Node-ID
cs Daten
0x10 LSB … … … … … MSB
Segment Upload, last segment
COB-ID 0 1 2 3 4 5 6 7
Request Client

Server
0x600 +
Node-ID
cs Daten
0x60
oder
0x70
00 00 00 00 00 00 00
Response Server

Client
0x580 +
Node-ID
cs Daten
0xnn LSB … … … … … MSB
11.3.4.2 Writing Segmented Transfer
The first telegram to write is executed via Command Specifier 0x21. The amount of
entered data bytes in the data area defines the amount of data bytes to be transmit-
ted in the following segment transfers. The following segments are controlled via
Command Specifier 0x00 and 0x10 in toggling order until all data were transmitted.
The last segment contains in the Command specifier (Bit 1…3) the amount of not
used data bytes in the last telegram.
The resulting request and response telegrams are shown in the following sequence.
An example is described in chapter 12.3.1.4.
04/13
CM-CAN ACU
35