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.
If you’ve worked with OmniServer to connect your non-standard devices in the past, you may be aware of the large number of pre-defined Error Detection Codes (EDC, also known as CRC, LRC and Checksums) available. However, as is the nature of custom protocols out there, it’s not uncommon to find an EDC that isn’t pre-defined due to some specialized handling by the device manufacturer.
To that end, OmniServer provides the flexibility to define your own custom EDCs in an OmniServer protocol. This post, the first of three on custom Error Detection Codes, will cover the basics of creating a simple custom checksum in OmniServer.
