11.3.4 Segmented Transfer
For data lengths > 4 Bytes the so called Segmented Transfer is used – the expedited
Transfer only supports lengths up to 4 Bytes.
In the first “Initiate” Telegram the overall amount of used data of the following s
quence telegrams is defined.
In the following telegrams 7 data byes per telegram
are send until the amount of data
bytes to be transmitted was reached
. The sequences of the Segmented Transfer are
separated by a toggle bit in the command specifier for the request and the reply tel
e-
gram. A “Continue” Bit marks the last telegram.
11.3.4.1 Reading „Segmented Transfer“
When Reading a regular Read access via command specifier 0x40 is executed. The
response contains the command specifier 0x41 that marks the requirement of Se
mented Transfer for this object. The following requests alternate with command spe
ifiers 0x60 and
0x70 until all data bytes were transmitted. In the last segment the
command specifier (bits 1…3) contains the amount of not used data bytes in that last
segment.
The resulting request and response telegrams are shown in the following sequence.
The Command Specifier have the following setup:
Initiate Upload Command Specifier:
Segment Upload Command Specifier:
2 = Initiate upload request
3 = Upload segment request
2 = Initiate upload response
0 = Upload segment response
Only valid if e =1 AND s = 1,
in all other cases n = 0.
If valid: Amount of data bytes, that con-
tain no useful data
0 = Normal (Segmented) Transfer
1 = Expedited Transfer (see chapter
0 = Data frame size is displayed
1 = Data frame size is not displayed
Toggle bit, toggled with each
Segment change
0 = First and odd segments
1 = Second and even segments
Continue bit, marks following
segments
0 = Further segments follow.
1 = This was the last segment.
34 CM-CAN ACU 04/13