![background image](http://html1.mh-extra.com/html/icp-das-usa/can-8124/can-8124_user-manual_3568919130.webp)
CAN-8124/CAN-8224/CAN-8424 User Manual
CAN-8124/ CAN-8224/ CAN-8424 User Manual (Version 2.0, Aug/2007)
130/153
z
Acknowledge Fragmentation
This example relates to when fragmentation of an Explicit Message is
performed in an Acknowledged fashion. Acknowledged fragmentation consists
of the transmission of a fragment from the transmitting module followed by the
transmission of an acknowledgment by the receiving module. The receiving
module acknowledges the reception of each fragment. This provides a degree
of flow control. The assumption is that larger bodies of information may be
moved across Explicit Messaging Connections (e.g. Upload/Download
functions) and, as such, a degree of flow control is necessary.
In this demo, assume that attribute data=0102030405060708090A. The
assembly instance ID=4, attribute=3.
Note: The slave device node is 0x09, and the master node ID is 0x0A
1. Requests the use of the Predefined Master/Slave Connection set
Master
(MAC
ID
=0x0A)
Slave
(MAC
ID
=0x09)
_ Group 2 Message
| _ Destination MAC ID=0x09
| | _ Message ID =6
| | | _ Frag=0. Transaction ID=0. Souce MAC ID= 0x0A
| | | | _ Service=Allocate_Master/Slave_Connection_Set Request
| | | | | _ Class ID=3
| | | | | | _ Instance ID=1
| | | | | | | _ Allocation Choice= Explicit
| | | | | | | | _ Allocator’s MAC ID=0x0A
ID=10 001001 110. Data= 0A 4B 03 01 01 0A
_ Group 2 Message
| _ Source MAC ID=0x09
| | _ Message ID =3
| | | _ Frag=0. Transaction ID=0. Destination MAC ID= 0x0A
| | | | _ Service=Allocate_Master/Slave_Connection_Set Response
| | | | | _Connection Message Body Format = DeviceNet (8/8)
| | | | | |
| | | | | |
| | | | | |
ID=10 001001 011. Data= 0A CB 00