23.03.2017 Views

wilamowski-b-m-irwin-j-d-industrial-communication-systems-2011

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

34-8 Industrial Communication Systems<br />

34.5.2 Buffer Transfer Timings<br />

A buffer transfer implies the transmission of a pair of frames: ID_DAT, followed by a RP_DAT. We denote<br />

this sequence as an elementary transaction. The duration of this transaction equals the time needed to<br />

transmit the ID_DAT frame, plus the time needed to transmit the RP_DAT frame, plus twice the turnaround<br />

time (t r ). The turnaround time is the time elapsed between any two consecutive frames.<br />

Every transmitted frame is encapsulated with control information from the PHL. Specifically, an<br />

ID _DAT frame has always 8 bytes (corresponding to a 2 bytes identifier plus 6 bytes of control information),<br />

whereas a RP _DAT frame has also 6 bytes of control information plus up to 128 bytes of useful<br />

data. The duration of a message transaction is<br />

( ) + ( ) + ×<br />

len id_dat len rp_dat<br />

C =<br />

bps<br />

where<br />

bps stands for the network data rate<br />

len() is the length, in bits, of frame <br />

t r<br />

2 (34.1)<br />

For instance, assume that all variables have a data field with 4 bytes (resulting in ID _DAT: 8 bytes and<br />

RP _DAT: 10 bytes). If t r = 20.μs and the network data rate is 2.5.Mbps then, the duration of an elementary<br />

transaction is (64 + 80)/2.5 + 2 × 20 = 97.6.μs (Equation 34.1).<br />

34.5.3 Bus Arbitrator Table<br />

In WorldFIP networks, the bus arbitrator table regulates the scheduling of all buffer transfers. The BAT<br />

imposes the timings of the periodic buffer transfers and also regulates the aperiodic buffer transfers. In<br />

Section 34.3.2, we have discussed the importance of the BAT as an indispensable tool for the scheduling of<br />

periodic transmissions. In this section, we will deal with this in depth and will discuss the problem of how<br />

to dynamically organize the BAT when new requests for asynchronous transmission are received by the BA.<br />

Assume here a WorldFIP system where six variables are to be periodically scanned, with scan rates as shown<br />

in Table 34.2. The WorldFIP BAT must be set in order to cope with these timing requirements. Two important<br />

parameters are associated with a WorldFIP BAT: the microcycle (elementary cycle) and the macrocycle.<br />

The microcycle imposes the maximum rate at which the BA performs a set of scans. Usually, the microcycle<br />

is set equal to highest common factor (HCF) of the required scan periodicities. Using this rule, and for the<br />

example shown in Table 34.2, the value for the microcycle is set to 1.ms. A possible schedule for all the periodic<br />

scans can be as illustrated in Figure 34.7, where we consider C = 97.6.μs for each elementary transaction.<br />

It is easy to depict that, for example, the sequence of microcycles repeats each 12 microcycles. This<br />

sequence of microcycles is said to be a macrocycle and its length is given by the lowest common multiple<br />

(LCM) of the scan periodicities.<br />

The HCF/LCM approach for building a WorldFIP BAT has the following properties:<br />

1. The scanning periods of the variables are multiples of the microcycle.<br />

2. The variables are not scanned at exactly regular intervals. For the given example, only variables A<br />

and B are scanned exactly in the same “slot” within the microcycle. All other variables suffer from<br />

a slight <strong>communication</strong> jitter. For instance, concerning variable F, the interval between microcycles<br />

1 and 7 is 5.80.ms, whereas between microcycles 7 and 13 it is 6.19.ms.<br />

TABLE 34.2 Example Set of Periodic<br />

Buffer Transfers<br />

Identifier A B C D E F<br />

Periodicity (ms) 1 2 3 4 4 6<br />

© <strong>2011</strong> by Taylor and Francis Group, LLC

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!