Building Custom CRCs for Non-Standard Protocols

Posted by Kevin Rutherford on May 17, 2018 2:00:00 PM

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.

Read More

Topics: Wonderware, Device Integration, Protocols, OmniServer, drivers, connectivity, OPC, OPC DA, OPC UA, Protocol Design, Error Detection, CRC

Building Custom LRCs for Non-Standard Protocols

Posted by Kevin Rutherford on Apr 19, 2018 2:00:00 PM

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.

Read More

Topics: Wonderware, Device Integration, Protocols, OmniServer, drivers, connectivity, OPC, OPC DA, OPC UA, Protocol Design, Error Detection, LRC

Building Error Detection Codes for Custom Protocols

Posted by Kevin Rutherford on Mar 15, 2018 2:00:00 PM

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.

Read More

Topics: Wonderware, Device Integration, Protocols, OmniServer, drivers, connectivity, OPC, OPC DA, OPC UA, Protocol Design, Error Detection

How to Connect a Non-Standard Device with No Code

Posted by Kevin Rutherford on Jan 4, 2018 2:00:00 PM

l ask you to remember back to our blog post last month where took the information we pulled from a device’s protocol document (in the prior month's blog) 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.

Read More

Topics: Wonderware, Device Integration, Protocols, OmniServer, drivers, connectivity, OPC, OPC DA, OPC UA, Protocol Design

How to Implement a Custom Protocol for a Non-Standard Device with No Code

Posted by Kevin Rutherford on Dec 21, 2017 2:00:00 PM

So remember in our blog post last month 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 OmniServer.

This post, the second of three, goes beyond the protocol details we gathered from the document in our blog post last month 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.

Read More

Topics: Wonderware, Device Integration, Protocols, OmniServer, drivers, connectivity, OPC, OPC DA, OPC UA, Protocol Design

Your Protocol Document and Integrating a Non-Standard Device

Posted by Kevin Rutherford on Nov 9, 2017 2:00:00 PM

So you've been tasked with bringing data from a new device (maybe a weigh scale or barcode scanner or RFID system) into your HMI/SCADA system.  But you just have a protocol document from the manufacturer.  And for this new device, there is no existing, off-the-shelf connectivity driver or server available.

So what now? Do you contact a custom software development house?  That gets very expensive and time-consuming very quickly.

This post, the first of three, goes through what to look for in that protocol document from the manufacturer to know how to begin using OmniServer to integrate your device without requiring custom code in a fast, affordable manner that provides industry-standard client interfaces such as OPC DA and UA.

Read More

Topics: Wonderware, Device Integration, Protocols, OmniServer, drivers, connectivity, OPC, OPC DA, OPC UA, Protocol Design

Join Our Journey

Working in industrial automation since 1996, the Software Toolbox team has seen a lot. The level of automation system sophistication of our integrators and users has evolved, each driven by the demands of their market and clients.  Everyone's learning continues as technological change accelerates.

This blog is about sharing from these journeys.  From tips on implementing software, successes our clients have experienced, or new ideas and things to consider in your journey, we'll be sharing them here.

Subscribe to Our Blog

Recent Posts

Posts by Topic