Software Toolbox Technical Blog

---

With the recently released 2019.2 (5.56) version of the OPC Data Client Toolkit, developers of OPC UA custom client applications can now add the latest extension to the OPC UA specifications, PubSub, short for Publish-Subscribe, to their applications. This version also brings items of value for developers of any type of OPC client application, and also highlights some updates from a 2019.1 release we did last month to prepare for this big release.

In this blog post, we will cover the most significant updates to OPC Data Client and how they will benefit you and your custom OPC client projects.

---

At Software Toolbox, we commonly hear from users seeking a solution for connecting and gathering data from this or that type of hardware.  Beyond that, though, is what users do with the data once they have it.  A common need is reliably logging process to a database such as Microsoft SQL server.

In this blog post, we’ll discuss a specific use case of a German R&D firm needing to collect data from multiple OPC data sources and log that data to a SQL database for further analysis geared towards a pilot project developing a model for optimizing Combined Heat & Power Partnership (CHP) technology for transferability to many enterprises where heat and power generation are essential to the process.

---

If you're unfamiliar with state based control, it's a process automation design that essentially defines that all process facilities should operate in a recognized, definable state with previously defined normal and abnormal conditions with defined actions for each.  State based control is intended to allow company's in virtually any process industry to greatly reduce factors of human error and inconsistency, significantly increasing the efficiency of all processes.

In this blog post, we cover how a large chemicals manufacturer migrated to state based control using OPC UA and increased their efficiency, production levels and profitability as a result.

---

If you've heard of the Cogent DataHub, you may be aware that it supports email and/or SMS notifications of defined conditional events based on a variety of data from it's various supported interfaces (MQTT, OPC UA, OPC DA, DDE, ODBC and more).  Having the right people receive alerts (such as when a tank has reached a critical level or a critical piece of machinery is offline) in a timely fashion can be the difference between simple downtime and a major liability.

This blog post will discuss how to use variable distribution lists in conjunction with the Cogent DataHub's Email/SMS capabilities to ensure the right decision makers will always receive important notifications as quickly as possible.

---

For many industries, where having access to process data is critical, it's common to implement redundancy on many levels to ensure there is no disruption to data collection.  While there are different levels of redundancy, the one we see users most interested in is with OPC data source redundancy.

The following short video blog demonstrates step-by-step just how easy it is to configure the Cogent DataHub to handle redundant failover between OPC UA data sources, OPC DA data sources and more.

---

The New Year is a time of renewal, new projects, new challenges, and for some of you, new roles, or new people on your teams.

In this blog post, we provide a quick reference to resources from the past year that should be helpful to you and your colleagues.  If you aren't already subscribed to our blog, we encourage you to . We publish new content about once a week, sometimes more often, and you can control when you are notified about new content.

---

The 2018.3 release of the OPC Data Client toolkit continues to make OPC UA client development easier, more secure and interoperable, while continuing to support OPC DA, A&E, and XML-DA development.

In this blog post I have taken the release notes and boiled it down to the key benefits that might drive you to upgrade, get back on support, renew support, or, if you’re new to OPC client development, try our OPC Data Client toolkit.

---

Recently we worked with an aluminum smelter operation that has doubled in size since it first opened and has made a significant positive impact on the local economy by supplying aluminum to local industries which has fueled their growth.

Like any growing business, this user is always seeking ways to improve operations and reduce risk of downtime. In the end they need to deliver returns to their shareholders while continuing to support the local community, all of which requires consistent predictable operational results.  In this blog post, we'll cover how they used an off-the-shelf solution for integrating varied systems to reduce life cycle costs.

---

Earlier this year, we shared the story of how Namibia Breweries Ltd is using off-the-shelf open OPC software in their operations management system.  In that story, we shared how we had learned making beer in one of the world’s driest places takes some unique approaches to power sourcing, water management, and really all resources.

We visited with Namibia Brewing again recently when they attended the X-Change 2018 conference in the beautiful Central Drakensberg region of South Africa.   I had the chance to sit down with Annemarie Kruger, Renaldo Du Pisani, and Andre Engelbrecht and, in this blog post, you'll learn about how they have continued to evolve their system since I visited their site in 2017.

---

OmniServer's core connectivity and data parsing abilities are only part of the equation when integrating non-standard devices with Wonderware.  How does that device data then make it up into Wonderware?

In this video blog, part of a series on connecting Wonderware to OmniServer, I'll show you how to make a basic OPC DA connection from Wonderware System Platform to OmniServer for integrating process data from all of your "other" devices that don't have a standard, off-the-shelf driver - all without having to write custom code.

---

If you’ve been following our blog series on custom error detection, you’ll remember that OmniServer provides a large number of pre-defined Error Detection Codes (EDC) for use in different protocols for non-standard device communication.  And, again, it’s not uncommon to find an EDC from a vendor that is not pre-defined due to some specialized handling by the device manufacturer.

As we covered in our previous posts on creating a custom checksum and LRC, OmniServer gives you the ability to build custom EDCs in an OmniServer protocol to handle these situations.  This post, the final of three on custom Error Detection Codes, covers the basics steps to creating a custom CRC (Cyclic Redundancy Check) in an OmniServer protocol.

---

You may be aware that OmniServer provides a wide variety of pre-defined Error Detection Codes (EDC, also known as CRC, LRC and Checksums) for use in protocols for non-standard device communication.  However, it’s not uncommon to find an EDC that isn’t pre-defined due to some specialized handling by the device manufacturer.

To handle such situations, OmniServer provides the ability to build your own custom EDCs in an OmniServer protocol.  This post, the second of three on custom Error Detection Codes, will cover the basics of creating a custom LRC (Longitudinal Redundancy Check) in OmniServer.