Software Toolbox Technical Blog

Welcome to the kickoff post of our Data Storage Deep Dive blog series! In this series, we will explore the crucial role of data storage solutions and Historians in industrial automation. Over the coming weeks, we’ll be looking into how solutions delivered by Software Toolbox can be utilized with Historians, helping you make the most of your industrial data.

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.

Applications tend to have a lot of moving parts. Here at Software Toolbox, we know that understanding these parts is important whether you are new to an application or a seasoned veteran who wants a more robust understanding for the sake of troubleshooting and optimization. Because of this, part of our job is to help you recognize and understand the components of our products to maximize your ROI when using our solutions.

In this blog post, we'll provide an overview of the different components of OPC Data Logger, an effective solution for reliable, event-driven logging of data from OPC server data sources (both OPC UA and OPC DA) to SQL and ODBC databases (including Microsoft Azure SQL) or text and CSV files. We'll cover the wizard-based interface used for Configuration, the difference between the Service and Runtime, and the Notification functionality so you can understand the purpose of each component and how to configure them to meet your logging needs.

Storing process data almost always comes with varying project requirements, making it difficult for users to find solutions that cater to specific configuration needs. Luckily, the wide variety of configurable functionality in OPC Data Logger allows for creating unique projects to fit your needs.

If you’re an existing user of OPC Data Logger or in the market for an OPC logging solution, you likely agree that having a reliable and accurate record of your data is a top priority. One of the most valuable parts of investing in a data logging solution is being able to trust that all the data from your sources is captured. But what happens if you lose the connection to your database? What happens to the incoming data during that downtime? Software Toolbox offers several solutions for logging data and today we will focus on OPC Data Logger and its database logging capabilities. 

If you've been following our ongoing Exploring OPC UA blog series, we've been covering key Software Toolbox solutions and the specifics of configuring OPC UA security and connectivity.

In this seventh post of the series, we will focus on OPC Data Logger, specifically stepping through settings related to security, endpoints and certificate management and connecting OPC Data Logger to OPC UA servers for logging data.

An often important task when logging important process data to a database or even to the cloud is verification that the data has been logged. This ensures that data has been successfully logged and will not be lost when overwritten in the downstream process.

In this video blog, we'll step through the configuration required in the OPC Data Logger for logging important process data to a database on condition related to a monitored item and how to perform a writeback to the OPC data source confirming the data has been successfully logged.

With the advent of cloud-based solutions in every industry, it's only natural that you might need to migrate from a traditional locally-hosted SQL database for logging your process data to Azure. Fortunately, logging both to traditional SQL and Azure SQL are similar in many ways and OPC Data Logger makes it possible to log to both for OPC UA and DA data sources.

In this video blog, we'll review the basic setup and architecture for OPC Data Logger and then step through the configuration required for logging to SQL and Azure SQL from an OPC server.