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.

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

6.4.4 Certification authorities<br />

The DNP3 Users Group has authorized three test houses to carry out conformance testing<br />

<strong>and</strong> issue conformance certificates for DNP3. Third party conformance testing is not a<br />

requirement to use DNP3, but if certification is required by an end user, this can only be<br />

obtained from one of these authorities.<br />

Authorized Testing Authorities:<br />

• Advanced Control <strong>Systems</strong> (Georgia, USA)<br />

• Reltronics (Canada)<br />

• Subnet Solutions (Calgary, Canada)<br />

6.5 DNP3 polling <strong>and</strong> communications options<br />

The designer of a <strong>SCADA</strong> system utilizing DNP3 needs to select an operational mode for<br />

the acquisition of data from the system. Whereas many older <strong>SCADA</strong> systems are based<br />

on purely polled data acquisition, DNP3 offers the choice of report-by-exception<br />

operation. The advantage that this operational mode gives is a substantial saving in b<strong>and</strong>width<br />

usage.<br />

Instead of slave devices reporting the status of all of their points in response to master<br />

station polls, they report changes only. This method assumes, <strong>and</strong> requires, that the<br />

<strong>SCADA</strong> master can reliably retain its record of the present status of the slave <strong>and</strong> that any<br />

changes to that status will be reliably reported to the master. When the typical operation of<br />

<strong>SCADA</strong> systems is considered it is apparent that such a system can make considerable<br />

savings in the amount of data that is communicated. This reduction in communication<br />

requirements can translate to allowing a much larger number of slaves to be connected to<br />

a given communication path than might otherwise be the case.<br />

In fact, the combination of polled versus non-polled operation, <strong>and</strong> report-by-exception<br />

combine to make four variations. The DNP3 documentation identifies the following four<br />

operating modes <strong>and</strong> identifies them in order of decreasing efficiency in use of communications<br />

b<strong>and</strong>width.<br />

A mode commonly used is unsolicited report-by-exception. This mode gives security<br />

against failure of communications systems, while still retaining the benefit of limited<br />

b<strong>and</strong>width usage. This addresses a problem that can occur with quiescent operation, which<br />

is undetected communication failures. In a fully quiescent system, if a link should fail<br />

there is no way to detect the failure because the master may not be attempting to initiate<br />

any communications over that link. In this case the failure would only be apparent if<br />

the master attempted to carry out a control action.<br />

When implementing an unsolicited report-by-exception operating mode, the frequency<br />

of background polling <strong>and</strong> the amount of information sought by this can be adjusted to<br />

provide optimal system performance. For example, a periodic background poll might be

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

Saved successfully!

Ooh no, something went wrong!