
DNP3 will not be found in use on the factory floor. Rather, it is used in the field of SCADA where equipment spanning large geographical distances need to be monitored and controlled.
The typical SCADA system is described using an example in the Oil/Gas industry.
2 of the 4 key issues with the SCADA system example are explored.
The remaining 2 of the 4 key issues with the SCADA system example are explored.
The existing RTUs were replaced by DNP3 RTUs and a system of data acquisition was implemented that eliminated the issues.
The format used for storage of data as well as the format for communication of data is discussed.
DNP3 uses objects to represent and more importantly communicate data. Multiple types of objects can be linked to the same I/O points.
A look at why Event type objects need to be used in DNP3 for report by exception operations.
DNP3 has a list of object types as part of the specification. This is looked at here.
How default variations are configured and the scenarios under which they come into play.
DNP3 uses point indexes to individually reference I/O.
DNP3 data classes are linked to events and allow for even more efficient usage of bandwidth.
How Classes work with Polled and Unsolicited Report by Exception.
Two software applications will be downloaded and installed in order to simulate DNP3 communication.
Both applications are downloaded from the Github page. Web link resources attached to this lecture.
A high level look at the various parameters and groups of parameters that must be configured for FIU and RTU equipment.
A look at the settings for the client / master simulation software application.
A look at the settings for the outstation / server simulation software application.
The simulators are configured to perform polling only. No polled RBE or unsolicited RBE.
The simulators are configured to perform polling as well as polling with RBE.
Output control messages are delivered by two methods: Direct Operate and Select Before Operate.
Objects are used for manipulation of Discrete and Analog outputs, specifically through the use of parameters.
The simulation software is used to simulate output communication.
Sub-set levels within DNP3 give equipment vendors options for implementing various levels of the DNP3 protocol suitable to their devices.
The device profile document is a key tool of DNP3 in providing for interoperability between DNP3 devices and systems. It is a required document that must be provided by the manufacturer for any equipment conforming to the DNP3 standard.
For events to match up correctly across a system, it is essential that the clocks in all outstations are synchronized with the master station clock.
If you are involved or will be involved in data acquisition and control of equipment spread over large geographical areas, then you need to have a working knowledge of the DNP3 protocol.
If you work in the areas of Electrical Transmission and Distribution, Water and Waste Water Management, Oil/Gas or Security systems, then having a working knowledge of the DNP3 protocol is a significant asset.
This course has been designed with practicality in mind. At the end of this course, you will know how DNP3 devices represent data in memory and the types of messaging that they use to exchange data. You will also perform practical exercises using simulation software, allowing you to get first hand experience in configuring DNP3 devices for communications. Essentially, you will have a new practical skill in the field of SCADA Telemetry and Wide Area Communication.
Specifically, in this course, you will learn:
- The difference between SCADA and Factory Automation protocols.
- How DNP3 devices represent data in memory.
- DNP3 network messaging types..
- DNP3 terminology: RTU, FIU, Report By Exception, Polled and Unsolicited Communication.
- Configuration of settings in DNP3 devices.
- Configuration and simulation of DNP3 communication.
- Implementation levels and standards.
- DNP3 data frame formats.
and much more ...