Software Toolbox Technical Blog

Those of you who are aware of OmniServer will already know that it is primarily used to retrieve information from devices that use 'non-standard' protocols to communicate, such as weigh scales, barcode readers, and printers. An HMI, SCADA, MES, Historian, database, and more, could then read that data from OmniServer, making it a powerful, universal, data acquisition tool.

Some of these 'non-standard' device protocols require what we call "special handling". For most protocols, if you've used OmniServer, data that is sent or received is "what you see is what you get" type data. An ASCII "A" is transmitted or received and interpreted as an ASCII "A". But what if your device is expecting something else as part of its special handling in its communication protocol? Or what if you wanted to interpret the data differently from the device to meet new business standards or existing requirements?

OmniServer is capable of handling advanced protocols where the devices send special characters/bytes that need to be handled in a specific way. In this blog, we will explain how to use a feature called "translations" in OmniServer with certain protocols that require special handling.

Have you ever been confused on the difference between Modbus offsets and addresses? I’m sure you may have configured different Modbus devices from different manufacturers who follow different documentation standards, especially for memory mapping. As we all know, that can certainly increase implementation time. In this blog post, we are going to dive into how offsets and addresses compare and differ to hopefully provide a better understanding, cutting down that configuration time when using TOP Server. Before we start comparing offsets and addressing, let’s first get an understanding of what both are.

If you’re an existing user or you’ve been keeping up with our previously released Cogent DataHub blogs, you’re already aware that Cogent DataHub is renowned for its extensive connectivity options to industrial data systems, but most importantly its secure, high performance, scalable, firewall, DMZ, & proxy friendly data transfer within premises and to/from the cloud. However, it’s worth emphasizing that DataHub’s connectivity includes MQTT, IoT, OPC DA, OPC UA, OPC UA Alarms & Conditions, OPC Classic Alarms & Events, Modbus, Excel, ODBC & more. These methods of connectivity help users realize that with DataHub, data has the freedom to seamlessly and securely traverse across various platforms. We truly believe that "once the data is in DataHub, it can go anywhere, securely".

In this blog post, I'll provide insight into using DataHub’s Transform property to manipulate data that is being logged to a database table. To follow along with this blog, as a prerequisite, you will need to have an ODBC database configured and have DataHub set up to be writing to that database. For more information on connecting and writing to a database, please read our blog “DataHub – 5 Quick Steps to Writing to a Database Table”. Unlike loggers that only work with OPC data sources, DataHub’s capability to securely tunnel data and aggregate from diverse sources besides OPC empowers many different types of applications.

TOP Server is widely used in automation for data collection from your industrial control systems. One of the many benefits of using TOP Server is that it ensures data integrity – meaning that the accuracy, consistency, and completeness of the data is maintained from your data source all the way up to whatever is consuming that data from TOP Server, such as your HMI, SCADA, MES, or Historian. While its capability to collect unchanged raw data from field devices is invaluable, it may not always align with the desired format, and there could be elective data massaging or manipulation required to meet your business demands. TOP Server can convert data types and even scale to engineering units, but what if you need more advanced data such Cycle Time, Maximum Temperature, Downtime Reason, etc.?

The TOP Server Advanced Tags Plug-in enhances functionality by providing added features to any TOP Server driver, such as mathematical operations and data bridging across protocols, thereby streamlining analysis processes and enhancing decision-making capabilities within industrial control applications.

In this article, we'll briefly introduce a few key features of the TOP Server Advanced Tags Plug-in that could serve valuable to you in your data collection processes.

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.

OPC Router is a powerful tool that can be used to easily integrate large quantities of data from a variety of sources using its modular configuration, adding value to a variety of industrial, business (ERP/SAP), and IoT data systems. It's drag and drop visual workflows result in reduced engineering time and risk in Industry 4.0, IIoT, and Digital Transformation applications. When combined with Software Toolbox's OPC server offerings and other automation software, plus decades of expertise in automation, the results are rapid time-to-value solutions.

In the following video, we'll walk through a simple example to show you the fundamentals of developing a project in OPC Router. You'll learn how to comfortably navigate the interface and how to verify that your setup is functioning properly. This process will also give insight into the building blocks that make the product so malleable and adaptable to many different use cases.

When logging data to a database or text file, the way that data is presented is essential due to the implications it has for who, or what, is reading this data to make decisions. Without the correct configuration of the data’s timestamps, records can easily become misinterpreted or sorted in non-chronological order by further systems. It’s critical that your data logging solution provides flexibility to get your data when you want it, how you want it, and stored the way you want it. Providing full control of the timestamp format for many users is not just a feature of our OPC Data Logger, but a requirement based on other connected systems and standards. Customizable Time Formats is the focus of today’s blog, but it is just one of the OPC Data Logger’s many flexible features that have our fans raving over it.

Software Toolbox has been a fixture in the automation industry since 1996, offering software tools and components from project conception to completion. Our expert staff is committed to helping customers leverage current technologies while offering ways to enhance or expand systems and approaches to achieve even greater returns. When it comes to our OPC Data Client Development Toolkit, that promise remains the same, and we want to help you make the best decisions for your development workflow.

The OPC Data Client has offered the usage of NuGet packages since 2016 as an alternative to adding assembly references via the components when writing custom OPC client applications. As our users have moved towards the use of NuGet, we made this a requirement for .NET Framework beginning with our V2022.2 release. In this blog post and accompanying video, we will cover what NuGet is, when to use it, and how to use it if it makes sense for your requirements.