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-3<br />

TABLE 39.1<br />

EPL Parameters<br />

Parameter Description<br />

Value<br />

Transmission speed<br />

10–100.Mbps<br />

Maximum number of CNs 240<br />

Duration of the start period<br />

45.μs<br />

Quiet time of MN<br />

1.μs<br />

Elaboration time of each CN<br />

8.μs<br />

where MN and CNs exchange cyclic data. This is accomplished by means of two different frames,<br />

namely PReq (Poll Request) and PRes (Poll Response). PReq is issued by the MN toward a specific<br />

CN and carries the output data. The addressed CN, after an elaboration time, sends as a response<br />

the PRes frame containing the input data. Such a latter frame is not sent exclusively to the MN but,<br />

instead, it is broadcasted on the network so that all CNs receive it. After receiving the PRes frame,<br />

the MN waits for a quiet time, and then it moves on the next CN. It is worth observing that not all<br />

the CNs are necessarily polled at each EPL cycle. Indeed, the standard supports two <strong>communication</strong><br />

classes, referred respectively as continuous and multiplexed, which specify the way in which CNs are<br />

addressed. In the continuous class, a CN is polled at every cycle, whereas in the multiplexed class a<br />

CN is polled every n cycles (with n > 1). Both <strong>communication</strong> classes may be handled contemporaneously<br />

in an EPL cycle, so that it is possible to have a polling scheme in which some CNs that are<br />

queried continuously (i.e., every EPL cycle), whereas some others are polled with a period which is<br />

an integer multiple of the EPL cycle.<br />

At the end of the isochronous period, the MN broadcasts the SoA (start of acyclic) frame informing all<br />

CNs that the asynchronous period is started. In this period, only one asynchronous message may be sent<br />

either by the MN or by one of the CNs. In practice, during the isochronous period, the MN may collect<br />

requests for asynchronous transmissions (from itself and/or the CNs) and then, according to a priority<br />

scheme, it selects the node which is granted to transmit. The selected node, which is informed by the<br />

MN via the SoA frame, may transmit a frame belonging to one of two different categories, namely EPL<br />

AsyncSend frame and legacy Ethernet message. The AsyncSend frame type is defined by the EPL protocol;<br />

it can be used for acyclic process data (typically alarms) and it may be delivered either in unicast or in multicast<br />

mode. Concerning legacy Ethernet messages, they are used for general purpose <strong>communication</strong>, and<br />

they may be of whatever type although, to this regard, the EPL standard recommends the use of the UDP/<br />

IP protocol suite (rather than the most popular TCP/IP) since UDP introduces a lower overhead.<br />

Finally, the idle period is entered at the end of the asynchronous period. The purpose of this time<br />

interval is to guarantee that there are no message overruns, i.e., no messages cross the EPL cycle boundaries.<br />

Thus, in this period, there is no activity on the network since all stations simply wait for the beginning<br />

of a new cycle. Table 39.1 summarizes the most relevant parameters of the EPL protocol as derived<br />

from the standardization documents.<br />

The correct execution of the EPL cycle requires that all stations connected to the network are compliant<br />

with the EPL protocol. This mode of operation is referred in the standard document as “EPL mode.”<br />

Nevertheless, a specific mode of operation (namely “basic Ethernet mode”) allows for the coexistence<br />

on the same network of EPL stations as well as legacy Ethernet ones. For these configurations, however,<br />

as mentioned in the standard document, the strict determinism of the EPL cycle is no longer ensured.<br />

39.3 Frame Mapping<br />

The EPL frames are encapsulated in standard Ethernet protocol data units as shown in Figure 39.3.<br />

As can be seen, the Ethernet type field is set to the hexadecimal value 88ABh which uniquely identifies<br />

EPL. The first octet of the EPL frame (“message type,” i.e., the first octet in the Ethernet data field) specifies<br />

the type of frame. The codes used in order to specify the different frames are reported in Table 39.2.<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!