![NANOTEC ELECTRONIC N5 Скачать руководство пользователя страница 112](http://html.mh-extra.com/html/nanotec-electronic/n5/n5_technical-manual_705153112.webp)
Technical Manual N5 (CANopen)
8 CANopen
CAN ID
Data
Byte 1
Byte 2
580+NodeID
<CMD>
Byte 3
Byte 4
Byte 5
Byte 6
Byte 7
Byte 0
<Data>
Segment SDO Upload confirm
Client
Server
Byte 0 with
<CMD>
is structured as follows:
0 0 0 t n n n c
7 6 5 4 3 2 1 0
Bit number
<CMD>
The bits have the following meaning here:
t
(toggle bit)
The bit alternates with each message sequence; it does not change within a sequence between
"request" and "response".
n
(number of bytes)
These three bits specify how many bytes contain no data. Example: If bits 2 and 1 are set to 0
and bit 3 is set to 1, then 011
b
= 03
d
bytes are not valid. This, in turn, means that byte 1 to byte
4 contain allowed values and byte 5 to byte 7 should be disregarded.
c
(more segments)
If no further SDO segments are sent and this is the last segment, the bit is set to 1.
Example: In this example, the "Manufacturer Hardware Version" object (1009
) is to be read. The
node-ID of the node in this example is 3.
The corresponding SDO message sequence is listed in the following table. The string that is to be read
out varies from controller to controller.
COB-ID
Data
Description
603
h
40 09 10 00 00 00 00 00
Init Upload; Index: 1009
h
; Subindex: 00
583
h
41 09 10 00 1E 00 00 00
Init Upload; Size: indicated; transfer type: normal; Num of
bytes: 30; Index: 1009
h
; Subindex: 00
603
h
60 09 10 00 00 00 00 00
Upload Segment Req.; Toggle bit: not set
583
h
00 4E 31 30 20 2D 20 57
Upload Segment Conf.; More segments: yes; num of bytes:
7; Toggle bit: not set
603
h
60 09 10 00 00 00 00 00
Upload Segment Req.; Toggle bit: set
583
h
00 54 31 32 30 39 2D 56
Upload Segment Conf.; More segments: yes; num of bytes:
7; Toggle bit: set
603
h
60 09 10 00 00 00 00 00
Upload Segment Req.; Toggle bit: not set
Version: 2.0.1 / FIR-v1650
112