02.02.2018 Views

Practical_modern_SCADA_protocols_-_dnp3,_60870-5_and_Related_Systems

Create successful ePaper yourself

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

214 <strong>Practical</strong> Modern <strong>SCADA</strong> Protocols: DNP3, <strong>60870</strong>.5 <strong>and</strong> <strong>Related</strong> <strong>Systems</strong><br />

object addresses, as for two-octet addressing. The information object address of zero is<br />

reserved for the case when the address is not relevant. The information object address is<br />

shown in Figure 8.20.<br />

Data Unit<br />

Identifier<br />

Type ID<br />

Variable Structure Qualifier<br />

Cause of Transmission<br />

Common Address of ASDU<br />

Information Object Address<br />

Information Information Elements<br />

Object 1<br />

Time Tag<br />

Bit 7 6 5 0<br />

Octet 1<br />

Octet 2<br />

Octet 3<br />

Figure 8.20<br />

Information object address<br />

On a system basis, specific data is uniquely identified by the combination of the<br />

common address <strong>and</strong> the information object address.<br />

An example of how this might work in practice is where there are a number of identical<br />

intelligent electronic devices IEDs connected to a sub-master RTU, which is in turn<br />

connected to a master station. These could be re-closers on a distribution system. Each<br />

IED will have an identical data structure internally, as determined by the device manufacturer.<br />

Most likely this will be some tens of information elements or data points, which<br />

could be addressed by a one-octet information object address. However, as the system<br />

includes RTUs that have many more data points, two-octet addressing is used across the<br />

system. At a system configuration level, there will be a single model for that type of<br />

re-closer, <strong>and</strong> configuration of each device into the system database will be a matter of<br />

using the st<strong>and</strong>ard point-mapping for that device type <strong>and</strong> adding the station number to<br />

form unique point references.<br />

8.5.4 Message addressing <strong>and</strong> routing<br />

Control <strong>and</strong> monitor directions<br />

An important concept in underst<strong>and</strong>ing addressing under IEC <strong>60870</strong>-5 is the difference<br />

between control <strong>and</strong> monitor directions. It is an assumption that the overall system has a<br />

hierarchical structure involving centralized control. Under the protocol, every station is<br />

either a controlling station or a controlled station. The communications network structure<br />

will normally be aligned with this, <strong>and</strong> for unbalanced communications links the controlling<br />

stations will be primaries, <strong>and</strong> the controlled stations will be secondaries at the link<br />

level. This follows naturally from the fact that a hierarchical structure involves multiple<br />

controlled stations, controlled by one or at least few controlling stations.<br />

In such a system, control messages such as comm<strong>and</strong>s or interrogations are transmitted<br />

by the controlling station, <strong>and</strong> these result in actions <strong>and</strong> return information transmitted<br />

by the controlled station.<br />

Addressing of ASDUs<br />

Messages are addressed in the control direction by the common address field of the<br />

ASDU. This address field is one or two octets, <strong>and</strong> defines the station (or logical station)

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

Saved successfully!

Ooh no, something went wrong!