Software Toolbox Technical Blog

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.

When you live in a remote region that is one of the most arid places on earth, you import your raw materials, and you’re making millions of hectoliters of beer a year, you have to make the most of all the resources you have and leverage what is in abundance in your location.  Namibia Breweries Ltd. (NBL) has a long history of success in a tough environment at their Windhoek site. They have received numerous awards for their innovative approaches to meeting their information system needs.

In this blog post, we’ll share their look into how they use off-the-shelf software and their teams' intellectual know-how and creativity to empower their manufacturing success.  If you read the stories in Automation World or Pro Food World you learned about how Andre Engelbrecht, manager of industrial control systems at NBL, and his teammates Annemarie Kruger, Rolando du Pisani and others unlocked data sources and built a digital smart manufacturing platform across the entire facility.  In this article, we’re going to share the rest of the story of NBL’s integration points, problems solved, and how they leveraged Software Toolbox’s full value proposition as part of their team effort.

Software Toolbox has worked with integrators, users, OEMS and distributors of Wonderware Software products since 1997.  At a Schneider Electric Software conference in 2017, they met a hardware supplier new to the Wonderware user community, , also known as TPI.  It turns out TPI is not new to the vibration monitoring space, though, and has a long history of providing handheld test and measurement equipment. In this video blog...

As someone who has worked with non-standard device connectivity using OmniServer for over 10 years, I sometimes take for granted the knowledge that I have gained over that time.  If you're anything like me, once you figure out the data you need from your device's protocol document, you just want to get your protocol knocked out as quickly as possible so you can start communicating.

In this post, I'm going to cover 4 key tips that I've learned over the years when working in OmniServer to build a protocol that you may not have realized and that could add convenience and save you a lot of time, which is time you can be spending on other important tasks.

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.  The last year has been one where our team has grown and worked to deliver the relevant content you need to learn more about software for automation & control, how to use our products, and the type of problems we solve.

In this blog post, we’ll provide a quick review of some key items from the last year that can help you or your colleagues in the coming year.  If you aren’t already subscribed to our blog, we encourage you to . We publish new content at least once a week, sometimes more often, and you can control the frequency of when you are notified of new content.

l ask you to remember back to  where took the information we pulled from a device’s protocol document () and created a custom protocol in OmniServer.  As you’ll recall, our protocol has now been designed.

But how do you go about testing the protocol and proving that it works? This final post in the series takes you through the steps of getting connected and actually troubleshooting your OmniServer protocol.

So remember in  where you just have a protocol document from the manufacturer for a device you need to integrate with your control system?  And for this new device, there is no existing, off-the-shelf connectivity driver or server available.

And remember asking yourself, “How do I connect to this non-standard device?”  With custom software development being very expensive and time-consuming, we discussed a better way using .

This post, the second of three, goes beyond the protocol details we gathered from the document in  to provide the basics on how to actually use those details to build a working protocol in OmniServer without custom code for a fast, affordable solution with industry-standard client interfaces including as OPC DA and UA.

If you haven't received one of my emails or heard from a colleague about our latest TOP Server release, you may not have heard about the key new features in the TOP Server V6.4 release.

In this post, I'm going to go through the top 3 key features released in V6.4 in more detail and how they benefit you as a TOP Server user.