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.

40-10 Industrial Communication Systems<br />

which <strong>communication</strong> can be implemented flexibly. It only has to be ensured that all IRT frames can be sent<br />

within the “orange interval.” The synchronized “send cycle” causes all nodes participating in IRT <strong>communication</strong><br />

to start transmitting I/O data at the start of the “orange interval.” As a result, all possible wait times<br />

are reduced to a minimum (same as in unsynchronized <strong>communication</strong>), whereas the I/O traffic is secured<br />

against other data traffic. The data frames are transmitted to the end node via the respective destination port<br />

solely on the basis of their MAC address (and corresponding Frame_ID). This enables a very flexible method<br />

of <strong>communication</strong> that is not subject to any special rules. Changes in the plant topology have no effect here.<br />

However, based on the concept, the enhanced flexibility and resulting ease of adaptability of a system is made<br />

possible at the expense of incomplete optimization of the bandwidth utilization because a small reserve is<br />

provided for in the “orange interval.” This ensures that all frames have been sent. Frames within the “orange<br />

interval” can be transmitted with or without VLAN tag.<br />

40.3.2 Communication Based on RT_CLASS_3 (Red Interval)<br />

In this case, the <strong>communication</strong> in the “red interval” is based on a schedule configured in advance (during<br />

engineering phase), i.e., in addition to the information for the end nodes, the network components<br />

located in between require information defining the forwarding of frames. Frames are forwarded based<br />

exclusively on the planning algorithm defined in IEC 61158. As a result of planning, an Ethernet controller<br />

(or more precisely, the integrated switch in an Ethernet controller) knows exactly which frame<br />

arrives at which port and when it must be forwarded to where. This enables a very high utilization<br />

of the bandwidth available. If a system requires RT_CLASS_3 <strong>communication</strong>, the bus cycle must be<br />

divided into a “red interval” and a UDP/IP part (green interval) during engineering. Here, the timing<br />

and length of each frame to be sent is specified on a port-by-port basis. The plant topology, the respective<br />

frame length, and the cable lengths between the individual nodes are critical factors in the timing for<br />

the purpose of its optimal utilization. If the system is changed, the planning algorithm must therefore<br />

be repeated. Data transmission in the IRT portion is always scheduled. The “schedule” is geared only<br />

to the sequence of arriving frames, which is determined by their Frame_ID and the frame length. The<br />

time-controlled processing of jobs within the “red interval” aids in eliminating the final sources of inaccuracies.<br />

Since RT_CLASS_3 <strong>communication</strong> is oriented only on the basis of timing, the throughput<br />

times of data frames through a switch are significantly shorter. Likewise, the performance in branched<br />

networks can be increased by optimized use planning of the same <strong>communication</strong> path. The topology<br />

information is sent to the respective IO controller during system power-up. RT_CLASS_3 frames are<br />

always sent without VLAN tag since the chronological position is always known.<br />

40.3.3 Cycle Duration and Constrains<br />

The maximum frame length in Ethernet/PROFINET yields a minimum duration of the “green interval” of<br />

125.μs (4 × 31.25.μs). However, certain rules must be defined in order to carry out efficient data <strong>communication</strong><br />

involving different RT classes, ensuring that the timing and the isochronous operation are adhered to in<br />

every configuration. The general rule is that at least two TCP/IP frames with maximum length can be sent<br />

per millisecond. This corresponds to a transmission time of approximately 250.μs. For bus cycles

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

Saved successfully!

Ooh no, something went wrong!