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.

40-4 Industrial Communication Systems<br />

has been designed for performance, brings with it specific hardware requirements (Ethernet controller/<br />

switch with support of isochronous operation).<br />

RT_CLASS_3: Synchronized <strong>communication</strong> within a subnet. During synchronized RT_CLASS_3<br />

<strong>communication</strong>, process data are transmitted with maximum precision in an exact order specified during<br />

system engineering (maximum allowable deviation from start of bus cycle of 1.μs). With the aid of<br />

topology-optimized data transmission, this is also referred to as IRT functionality. In RT_CLASS_3<br />

<strong>communication</strong>, there are no wait times. In order to take advantage of the data transmission designed<br />

for maximum performance, special hardware requirements apply (Ethernet controller with support of<br />

isochronous operation).<br />

RT_CLASS_UDP: The unsynchronized cross-subnet <strong>communication</strong> between different subnets requires<br />

addressing information via the destination network (IP address). This variant is also referred to as RT_<br />

CLASS_UDP. Standard switches can be used in this RT class.<br />

For RT frames, data cycles of 5.ms at 100.Mbps in full-duplex mode with VLAN tag are sufficient. This<br />

RT <strong>communication</strong> can be realized with all available standard network components.<br />

40.1.3 Conformance Classes<br />

Since the complete scope of functions implemented in PROFINET IO is not required in every automation<br />

system, the conformance classes/application classes are introduced. The objective is to simplify the<br />

application areas of PROFINET IO. The resulting application classes enable plant operators to easily<br />

select field devices and bus components with explicitly defined minimum properties. The minimum<br />

requirements for three conformance classes (CC-A, CC-B, CC-C) have been defined from the perspective<br />

of the plant operator. In addition to the three application classes, additional specifications have been<br />

made for device types, type of <strong>communication</strong>, transmission medium used, and redundancy behavior.<br />

This specification ensures the interoperability in an automation system with regard to the scope of functions<br />

and performance parameters. It is assured that all field devices within the selected CC meet the<br />

same minimum requirements. The application areas currently are<br />

CC-A: Use of the infrastructure of an existing Ethernet network including integration of basic<br />

PROFINET functionality. All IT services can be used without restrictions. Examples of typical<br />

applications are in building automation and process automation. Wireless <strong>communication</strong> is<br />

only possible in this class.<br />

CC-B: In addition to the functions of CC-A, the scope of functions of CC-B supports easy and<br />

user-friendly device replacement without the need for an engineering tool. To increase the data<br />

security, a media redundancy protocol for TCP (UDP)/IP data is integrated. Examples of typical<br />

applications are in automation <strong>systems</strong> with a higher-level machine controller that place<br />

relatively low demands for a deterministic data cycle.<br />

CC-C: In addition to the functions of CC-B, the scope of functions of CC-C supports highprecision<br />

and deterministic data transmission, including for isochronous applications. The<br />

integrated media redundancy enables smooth switchover of the I/O data traffic if a fault<br />

occurs. An example of a typical application is the field of motion control.<br />

40.1.4 Prerequisites<br />

PROFINET IO field devices are addressed using MAC addresses and IP addresses. Each subnet is represented<br />

by a different network_ID (subnet mask). PROFINET IO field devices are always connected<br />

as network components via switches. This takes the form of a star topology with separate multiport<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!