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.

5-2 Industrial Communication Systems<br />

Engineering<br />

tool A<br />

Portability<br />

Configurability<br />

Engineering<br />

tool B<br />

Industrial<br />

<strong>communication</strong> system<br />

Interoperability<br />

FB<br />

(function i)<br />

Functionblock<br />

(FB)<br />

Functionblock<br />

(FB)<br />

FB<br />

(function i)<br />

Automation device x<br />

Automation device y<br />

FIGURE 5.1<br />

Distributed automation system.<br />

to consider not only the physical connection but also different other levels. This ability to cooperate can<br />

be described by different terms.<br />

Two components need to have identical properties to reach a certain level of cooperation. These five<br />

properties are<br />

1. Identical <strong>communication</strong> protocol on layer 1–7<br />

2. Usage of services by the application<br />

3. Definition of the interface variables regarding, for example, data type, resolution, or measuring unit<br />

4. Semantics of the application (algorithms, amount, and meaning of interface variables)<br />

5. Dynamic behavior regarding, for example, control parameters or filter constants<br />

Depending on the number of properties that a system fulfills, we can assign the following terms (Table 5.1):<br />

Compatible and interconnectable require loosely defined <strong>communication</strong> agreements; the components<br />

must not interfere with each other, which translate to requirements on the physical channel, for<br />

example, voltage level or bitrates. Interworkable <strong>systems</strong> need to have an agreement on the meaning of<br />

transmitted information in terms of data types (e.g., how many bytes make up a number?, is it an integer<br />

or a floating point?) and also have to define error values in case a value cannot be transmitted (e.g.,<br />

too big or sensor is broken). An example for this level of cooperation can be found in local operating<br />

network (LON) [1], where standard network variable types (SNVTs) have been defined. For example, the<br />

type snvt_temp defines temperature, which can be used for transmitting common temperatures with<br />

the following properties:<br />

• Data type: unsigned long integer<br />

• Total length: two bytes<br />

• Measuring unit and range: degree Celsius ranging from −274°C to +6279.5°C<br />

• Resolution: 0.1°C<br />

On this level, the user of the system can be sure that the components do not interfere with each<br />

other, that they can exchange data, and also have the same understanding of the interpretation of<br />

TABLE 5.1 Term Definitions by Properties<br />

1–5 Given above<br />

Incompatible None<br />

Compatible 1<br />

Interconnectable 1 2<br />

Interworkable 1 2 3<br />

Interoperable 1 2 3 4<br />

Interchangeable 1 2 3 4 5<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!