Fragmentation

During normal operation, messages do not need to be fragmented!

If messages need to be fragmented, proceed as follows:

At the start of each message, the length of the subsequent useful data is transmitted. Subsequently, a fragmentation code is sent. This fragmentation code is not included in the length byte (D-Len).

• FragStart -> first fragment.
• FragMiddle -> middle fragment.
• FragEnd -> last fragment.

Special requirements for Profibus

With Profibus, a "token" is constantly transmitted through the system, from which the respective subscribers take the data applicable to them and to which the subscribers write the data for the master, each received fragment must be acknowledged with ,,FRAG ACK'' and the D-Len byte of the received fragment. When a fragmented message is sent to the master, each fragment must be acknowledged by the master with "FRAG ACK" and the D-Len byte of the received fragment, so that the module can dispatch the next module. If a fragmented message is sent by the master to the module, the next fragment can only be dispatched when the module has acknowledged the receipt of the previous one (with "FRAG ACK" and the D-Len byte of the received fragment). The last fragment must not be acknowledged.