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.

39-8 Industrial Communication Systems<br />

transmitted within two subframes. The CRC type used (either CRC8 or CRC16) depends on the size of<br />

the user data. All systematic failures will be recognized by the POWERLINK safety protocol including<br />

delay, repetition, wrong sequence, insertion, loss, and masquerade [11].<br />

39.7 Performance Analysis<br />

While the performance of real-time networks can be assessed according to a multitude of performance<br />

criteria, in the context of EPL the most common metrics are jitter, turn-around time (TAT), and cycle<br />

time. Other parameters, such as the latency of the asynchronous messages, are also commonly used to<br />

assess the protocol performance. This section addresses the performance analysis of the EPL protocol,<br />

illustrating how these parameters can be estimated and how key network design options affect them.<br />

39.7.1 Jitter<br />

Jitter, defined as the maximum time deviation that may occur on cyclic events, is defined in the EPL<br />

standard as being in the submicrosecond range. The jitter in EPL networks is determined by the MN,<br />

which is responsible for correct sending of the SoC message, as well as by the network components.<br />

While the MN jitter is intrinsic to the hardware/software implementation characteristics, the jitter due<br />

to the network components depends on the nature of the components themselves and of the network<br />

topology. Although the jitter induced by a single hub (or by a limited number of such devices) may seem<br />

negligible, as stated above EPL permits the violation of the IEEE 802.3 topology guidelines, opening the<br />

way for the use of tree or linear topologies with several cascaded hubs. Despite their convenience, such<br />

topologies have a negative impact on the global network jitter, which depends on the highest number of<br />

hubs that exist between the MN and any CN. The jitter upper bound can be computed as<br />

where<br />

J mn is the MN jitter<br />

J hub is the hub-induced jitter (homogeneous hubs assumed)<br />

N hub is the number of hubs between the MN and any CN<br />

J NET = Jmn + Nhub × Jhub<br />

(39.1)<br />

For illustrative purposes, consider a MN and a CN interconnected by a single hub. In this configuration,<br />

considering, for example, the POWERLINK interface described in [3], J mn = 50.ns, whereas a<br />

typical value for the hub-induced jitter is J hub = 70.ns. Thus, the jitter upper bound becomes, trivially,<br />

J mn = 120.ns. For a two-level tree topology, the jitter upper bound becomes J mn = 190.ns, with an<br />

increase of 58.3%. In these conditions, a linear topology has to be limited to 13 devices in order to<br />

guarantee a jitter value below 1.μs.<br />

39.7.2 turn-Around Time<br />

Another important performance criterion is the TAT, defined as the time elapsed between the transmission<br />

of a request and the reception of the corresponding response. The TAT has a noticeable impact on the<br />

bandwidth utilization efficiency since this corresponds to network idle time.<br />

As for jitter, the TAT depends on constructive aspects of the network components and devices as well<br />

as on the network topology. In software-based implementations, the EPL stack is entirely executed in a<br />

microprocessor, requiring several processing steps to decode the requests and issue the corresponding<br />

replies. The associated latency depends on the delays introduced by several factors such as code execution<br />

times, DMA techniques, interrupt handling procedures and bus protocols that may lead to response times<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!