Software Toolbox Technical Blog

Continuing our Summer of IoT blog series, we'll delve into the exciting new release of Cogent DataHub V11. For those that may have missed our previous post on Cogent DataHub V11 Features to Be Excited About, the entirely revamped security profile provides a Secure out-of-the-box experience for V11 users that opens a variety of customized options. Today we take a deep dive into a part of the security improvements, and next month we’ll take a second deep dive into security.

Welcome back to our Summer of IoT blog series! This week, we are excited to announce the release of OmniServer Version 3.4.0.1 which in the professional edition, now includes MQTT client capability, which enables publishing data to MQTT Brokers such as the Cogent DataHub Smart Broker, HiveMQ, Mosquitto, and others.

Welcome back to our Summer of IoT blog series! In this third installment, we continue our journey through the fascinating world of IoT, delving deeper into the transformative technologies Software Toolbox has to offer for shaping our connected future. Today, we will be highlighting the TOP Server MQTT Client driver and demonstrating how it can effortlessly integrate real-time data from MQTT brokers into your existing industrial automation systems, such as your HMI, SCADA, MES, or Historian.

Welcome back to our Summer of IoT blog series! We hope that last week’s introduction to the series created excitement as we continue to explore how our IoT solutions can help you achieve even greater success with your Industry 4.0 and Digital Transformation initiatives.

In today's video blog, we will be integrating REST with MQTT by using OPC Router to connect to a RESTful API service and publish data to HiveMQ's MQTT Broker.

MQTT continues to grow in popularity and implementation within the industrial automation community. For those who are still new and learning about this protocol, MQTT is a light-weight transfer protocol built around a publish/subscribe architecture. In simple terms, MQTT can be compared to a mail envelope, providing structure and a common appearance with a supported delivery system, while the actual content of that envelope can vary widely.

Because of the ambiguity of message content, implementations of MQTT can be utilized for various needs across segments in our industry, though the varying message content presents its own issues that are outside the scope of this article. There are multiple solutions for providing structure and standards around the message content that we will discuss in future posts.

This blog will primarily focus on the reliability of message delivery based on the concept of Quality of Service (QoS). We will be utilizing the Cogent DataHub to showcase these options, as it can act as both the MQTT Broker & Client. It is important to note that this information can be applied to various MQTT implementations, including other Software Toolbox product offerings with MQTT, such as OPC Router or the TOP Server MQTT client driver.

If you have been following our blog for a while or have been exploring IoT platforms available in the market, you may know that the Google Cloud Platform combined with the Google IoT Core is a frequently used combination in the industry. Google has recently announced that it will be shutting down the Google IoT Core. In doing so, Google is forcing many of its Cloud Platform users to switch platforms.

In this blog post, we will review detailed information about the alternatives to the Google Cloud Platform that are available for use with all of the IoT capable products we provide, and how the change works.

Cogent DataHub® is a gateway that enables a wide range of connectivity interfaces for different data sources such as OPC UA, OPC DA, ODBC, DDE and so much more.  Included in those available interfaces is the ability to act as both an MQTT client and broker even including Sparkplug B support for enabling MQTT integration with many other types of systems that don't natively support MQTT.

A key facet of the MQTT specification that can sometimes be complex for our users and cause issues with compatibility between DataHub and other MQTT clients and brokers is how to handle the formatting of MQTT messages. As you may or may not know, while MQTT does specify how to construct a message header for routing by an MQTT broker, it does NOT specify the actual message content. This tends to be a challenge when MQTT clients from different developers need to work together, since they need to be using the same format for the message content.

In this video blog, I'll show you how to use DataHub V10's Advanced MQTT Parser capability to specify flexible formats that will work with virtually any other vendor's MQTT clients and brokers.

Ongoing digital transformation and operational visibility initiatives continue to demand the integration of different systems using different technologies. With increased adoption of secure OPC UA and MQTT Sparkplug B, it’s only to be expected that users will have systems that support one or the other technology but need to communicate with each other.

Although OPC UA supports a publish-subscribe mechanism with OPC UA PubSub, and adoption of OPC UA is strong and growing, the reality is there will be situations where the user is already using MQTT Sparkplug B and needs to integrate it with OPC UA or vice-versa, without writing custom code or going through complex configuration.

Software Toolbox was founded in 1996 on the principal of making data and device integration easy by using configurable off-the-shelf software to avoiding writing custom solutions and knowing the pros and cons of and ins and outs of many technologies. That mission remains strong, as you’ll see, as we discuss interoperating between OPC UA and MQTT in this blog post.