Software Toolbox Technical Blog

As you may already be aware, the Cogent DataHub has a wide range of flexible connectivity options between different data sources such as MQTT, OPC UA, OPC DA, ODBC, DDE and so much more.  MQTT client and broker functionality in particular allow DataHub to integrate MQTT data sources with HMI, SCADA, MES, historian and other systems that don't natively support MQTT.

In this next installment of our Cogent DataHub Virtual Training series, we will cover step-by-step how to easily connect 3rd party MQTT clients to the DataHub MQTT broker and convert their data for access by your own systems with OPC UA or OPC DA client capabilities.

Access to various industrial data via RESTful web services is increasingly becoming necessary in this era of inter-connectivity and big data. From sources such as devices with self-hosted web services to relevant market data such as weather information and pricing for commodities and energy, there is a host of relevant data to be integrated from such RESTful web services.

In this video training blog post, we will cover step-by-step how to easily connect to and consume data from RESTful web services and then push that data to OPC and SQL systems with the OPC Router.

Many of the great questions in life begin with the word ‘where’. Where do we come from? Where are we going? Where should I install my LGH File Inspector?

While I cannot provide a whole lot of input on the first two questions, I do have some suggestions on where to install your LGH File Inspector.

In this Tech Support Corner blog post, we will explore some common factors that we have seen impact, or drive, the ideal placement of an LGH File Inspector installation – a question that we get quite commonly from users like you.

Cogent DataHub is always expanding its wide range of flexible connectivity options between different data sources such as MQTT, OPC UA, OPC DA, ODBC, DDE and so much more.  With the advent of IIoT and its increasing adoption across industries, connectivity to various traditionally non-IIOT data sources via MQTT is key.

If you're not familiar with the concept of a virtual or digital twin, it's the idea of virtual modeling a physical asset or system.  Ultimately, the key motivators for creating digital twins is having the ability to accurately model and predict what will happen with the real-world physical equivalent of that digital twin.  Digital twins are extremely beneficial towards predictive analytics used for pro-active maintenance and process optimization across industries.

In this next installment of our Cogent DataHub Virtual Training series, we will cover step-by-step how to easily connect and push data from OPC data sources to digital twins in the Azure IoT Hub including how to optionally do so through a network DMZ (DeMilitarized Zone) using an additional DataHub as a proxy server for even greater security.

While TOP Server for AVEVA™, formerly Wonderware provides connectivity to hundreds of device types and protocols, that is only part of how TOP Server helps with integrating industrial process data with external software such as AVEVA™ System Platform, formerly Wonderware and other client applications.

You're likely aware that TOP Server is an OPC UA server.  But TOP Server can also act as an OPC UA client for integrating with other OPC UA servers, as well.  For situations where you have a UA server to integrate but you're not quite ready to move to OPC UA for all of your client applications, this provides the flexibility you need.

In this video blog, I'll show you how to make a secure OPC UA connection from TOP Server to other OPC UA servers supporting the Data Access profile.  We cover the basics of configuring the OPC UA Client driver in TOP Server and making an OPC UA connection to another OPC UA server.

Cogent DataHub enables a wide range of flexible connectivity options between interfaces for different data sources such as OPC UA, MQTT, OPC DA, ODBC, DDE and so much more.  This is why we commonly refer to DataHub as a "gateway", as it is frequently utilized for data integration by external software such as HMI, SCADA, MES, historians and other client applications, including for IIoT integration.

In Part 1 of our Cogent DataHub Virtual Training series, we will cover step-by-step how to easily connect OPC UA (Data Access Profile) client applications to your OPC DA Classic server data sources.

As we discussed in the first post of this series, the term "OPC client" often refers to off-the-shelf HMI or SCADA applications.  OPC clients can also be other custom developed software applications in your enterprise that could benefit from access to OPC process data.  Or there might be a new custom application you need to develop that requires access to OPC process data.  In those situations, you need a reliable, straightforward method to enable those applications as OPC clients.

In Part 2 of our series on How to Develop Custom OPC Clients, we will cover step-by-step how to use low-code techniques to read, write and subscribe to OPC process data through building a basic OPC client application in Visual Studio.NET.

Software-based licensing is a commonality among software solutions across all industries, not just industrial process control.  It's flexible, doesn't require physical shipping and is very reliable. But some system architectures can ultimately benefit from another licensing option - hardware keys.

Hardware key licensing is invaluable for high-availability systems for a number of reasons.  We've recently expanded licensing support in OmniServer, the proven OPC solution for integrating non-standard devices that don't have an off-the-shelf driver, to include optional hardware key support.

In this blog post, we'll cover the key reasons that hardware key licensing is beneficial for many OmniServer users.