Software Toolbox Technical Blog

DNP3 (Distributed Network Protocol) is a communications protocol primarily used for communications between a client application such as HMI, SCADA, or Historian and Remote Terminal Units (RTUs) or Intelligent Electrical Devices (IEDs). Originally designed for power distribution and transmission, the DNP3 protocol has also found a home in water/wastewater, oil & gas, and transportation thanks to its robust error checking and if applied properly, efficient bandwidth usage.

If you're reading this, you may be a part of one of these industries and might have a DNP3 RTU being used and need to integrate data from that process. If so, we can certainly help with that. A newer application of DNP3 is in the Emerson FB-3000 RTU's used in oil & gas. Our FB-3000 EFM Exporter leverages the TOP Server DNP3 driver to generate FlowCal CFX export files.

The TOP Server DNP3 Client Suite supports data access from any device supporting the DNP3 protocol that acts as a server, over serial or Ethernet connections, wired or wireless/radio.

Our DNP3 drivers also boast deep functionality advantages including things like:

• Automatic Tag Generation support for Channel and Device Configuration, Authentication Statistics, Data Set, Device Attribute, and File Control
• Support for Integrity & Event polls across multiple classes that users define in the RTU to provide different frequency of retrieval for different points
• Unsolicited messaging from the devices on conditions defined in the RTU
• Analog deadband configuration
• Secure DNP3 Support (Configurable User Authentication, Aggressive Mode support, User Key Management, Auto-generated internal Authentication Statistics tags)
• Preservation of timestamps set in the device
• WITS Phase 1, 2, and 3 support for the water industry
• File transfer support (critical for Emerson FB-3000 devices, and used by some devices for remote configuration file upload and activation)

In this video blog, we'll show you how to get started using our TOP Server DNP3 Client Ethernet driver to connect and gather process data from a DNP3 device for HMI, SCADA, Historian, MES, and other client applications. For a deep dive into how DNP3 polling works and is different, for good reasons, than many protocols, read our DNP3 Polling Behavior technical blog.

In the world of industrial automation and control systems, communication protocols play a crucial role in ensuring seamless data exchange between devices. Modbus started as a protocol used in Modicon, now Schneider Electric, PLCs in the 1970’s. It was adopted across the industry for its clarity and simplicity. With any protocol, including and especially with Modbus, there are areas where the parties to the communication, the client and server, can interpret the bit stream of data differently once exchanged because the Modbus protocol specification does not speak to those interpretations.

Whether you're running a production system in manufacturing, oil and gas, building automation, or energy, safety and uptime are of the utmost importance, especially with cybersecurity attacks increasing in frequency and complexity.

That’s why when running an application with widespread user access, managing user permissions and configurations is so important, and you need a solution that is as security centric as you are. In this blog post, we delve into how to manage user groups and permissions inside the TOP Server’s User Manager and Security Policies Plug-In to ensure a robust and secure gateway to your TOP Server Configuration.

Your operations visibility relies on real-time data from machinery, systems, and field devices. When there are communications issues resulting in loss of or inaccurate data, addressing issues promptly is critical. Whether it's stale, poor quality, or missing data in your SCADA or HMI application, a well-defined troubleshooting procedure is a must. Like all our products, the TOP Server OPC Server offers an arsenal of tools to inform you about what is happening and streamline your troubleshooting process, summarized in our previous blog post, Minimize Downtime with TOP Server Troubleshooting Tools.

In this post, we'll take a deep dive into some of those tools, with an emphasis on the device connection side of TOP Server, teaching you a step-by-step process to pinpoint communication issues at their source. While this specific example uses the Modbus Ethernet Driver and an OPC DA Client connection, the same principles can be applied when troubleshooting various other scenarios.

The GE Ethernet family of PLCs and PACs is one of the most popular controllers across many automated industries. If you're reading this, you likely have at least one GE Ethernet controller being used in your industrial process and need to integrate data from that process.

The TOP Server GE Ethernet driver supports data access from devices using the GE SRTP Ethernet Protocol, including Series 90-30, Series 90-70, Horner OCS (Horner's Operator Control Stations), PACSystems RX3i and RX7i, and the VersaMax Family, as well as an expanded range of GE PLCs through the open device model selection within the driver.

In this video blog, I'll show you how to get started using our GE Ethernet driver to connect and gather real-time process data from GE controllers for HMI, SCADA, MES and other client applications.

In a prior blog post regarding redundancy, we learned how critical it is to plan for redundancy in the Industrial Automation space. We covered how the TOP Server Media-Level Redundancy Plug-In  facilitates duplicate or backup systems used to maintain reliable communications with the critical components in your environment which in turn minimizes data loss and increases the availability of your critical industrial data.

Tags, nodes, points, items, symbols – in our industry, we often see these terms thrown around, but in most instances, we’re all talking about the same thing. From the TOP Server OPC Server's perspective, we refer to them as tags. A tag is an OPC Server software application’s representation of a device address to use for communication. This is how your HMI, SCADA, MES, historian, or other client application is able to consume data. If you’re a TOP Server user, you know that you are required to configure tags to get data from your device, but did you know there are multiple options of how to accomplish this?

Have you ever wondered why certain features in TOP Server work the way you experience them, or how something might work in certain scenarios?  Well this blog post tries to answer a few of those type of questions!

Anyone that has used TOP Server before has had to make edits to the configuration. While TOP Server allows changes to many settings while actively collecting and serving data, and makes it simple, there are things to consider to avoid disrupting operations. TOP Server has certain restrictions in place when making configuration changes, and while potentially frustrating, these are for your benefit and security. For example, perhaps you have tried to make a certain change, but observed that the setting immediately changes back and “doesn’t stick”. Or maybe you’ve logged onto your machine and were unable to make any configuration changes at all. Why is that?