23.03.2017 Views

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

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Ethernet POWERLINK 39-9<br />

typically in the order of some microseconds. The EPL protocol may also have a total hardware support,<br />

typically via FPGA technology. In this case, the EPL packet handler, the Ethernet controller, and the hub<br />

(if included) are completely embedded in hardware. The processing of incoming requests, in this case, is<br />

entirely carried out in hardware, and the interconnection between the Ethernet controller and the EPL<br />

packet handler can use dedicated buses, leading to extremely shorter response times, below 1.μs.<br />

Similarly to the jitter, the use of tree or linear topologies with several cascaded hubs also has a negative<br />

impact on the TAT since each hub situated between the MN and a CN adds its own delay. Moreover, it has<br />

to be noticed that the hub-induced delay affects both the MN requests and the CN replies, doubling in such<br />

a way its impact in each query of the CN.<br />

In general, the TAT in a transaction involving node i can be upper bounded as<br />

TAT i = DCN i + × Dhub × Nhub i + tprop + CReq + CRes<br />

2 (39.2)<br />

where<br />

D i CN is the nominal response time of the ith CN<br />

D hub is the nominal hub delay (homogeneous hubs assumed for simplification)<br />

N i hub is the number of hubs involved in a transaction between the MN and the ith CN<br />

t prop is the wire-propagation time<br />

C Req is the transmission time of the request message<br />

C Res is the transmission time of the corresponding response message<br />

As an example, a transaction in which the MN polls a CN having a short amount of data to transmit<br />

(up to 36 data bytes) may be considered. In this case, C Req = C Res = 6.72.μs. Assuming also a fast CN<br />

(i.e., with hardware support) yielding a 1.μs response time, a single hub with 400.ns delay, and that the<br />

segment (wire) length is of 100.m (leading to t prop = 500.ns), the TAT, given by Equation 39.2, is (in seconds):<br />

TAT = 1× 10 + 2 × ( 400 × 10 + 500 × 10 ) + 2 × 6. 72 × 10 = 16. 24 × 10<br />

−6 −9 −9 −6 −6<br />

If a two-hub topology is considered, the above computed value of TAT is increased by 800.ns, corresponding<br />

to a relative degradation of about 4.9% on the TAT. For a linear topology with 10 devices, the total increase<br />

would be around 22.2%. These performance figures show how the network topology design may have a<br />

substantial impact on the TAT.<br />

The use of switch devices may significantly worsen the performance. Indeed, cut-through switches<br />

induce a latency of at least 12.μs since message forwarding only starts after the reception of the destination<br />

address Ethernet field, thus multiplying the latency for a factor of at least 3. For store-and-forward<br />

switches, the latency time depends on the message size and can be very relevant (up to 120.μs per switch,<br />

if maximum size Ethernet messages are employed).<br />

39.7.3 Cycle Time<br />

The cycle time is a factor of paramount importance since EPL applications (for example, those concerned<br />

with motion control issues) may require very short cycle times (well below 1.ms, as discussed in [14]). The cycle<br />

time of EPL may be trivially calculated as the sum of the periods shown in Figure 39.2:<br />

TC = Tst + Tis + Tac + Tid<br />

(39.3)<br />

where the addends in Equation 39.3 represent the durations of the start, isochronous, asynchronous, and<br />

idle periods, respectively. However, the EPL cycle time is mostly determined by the duration of the isochronous<br />

period which, in its turn, is a direct function of the number of queries to the configured CNs.<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!