Did You Know? How to Integrate Virtual COM Devices with OmniServer

Posted by Kevin Rutherford on Feb 14, 2019 2:00:00 PM

If you're familiar with OmniServer, you likely already know how OmniServer is commonly used to retrieve information from devices that use ‘non-standard’ protocols to communicate such as weight scales, barcode readers, and printers either over serial connections or Ethernet connections.

However, with the advent of USB connectivity, many such devices that would have traditionally been a serial/COM device now physically connect to a machine via USB, instead.

Continuing our "OmniServer Did You Know?" blog series, we will cover how OmniServer can easily connect to USB or serial-to-Ethernet devices that are mapped virtually as Serial/COM devices.

Read More

Topics: Wonderware, Device Integration, Protocols, OmniServer, OmniServer Did You Know

Did You Know? How to Test OmniServer Protocols Prior to Building Your Client Application

Posted by Kevin Rutherford on Jan 3, 2019 2:00:00 PM

When working with non-standard protocols based on protocol documentation from a device vendor, there will always be some expected amount of testing, trial-and-error and troubleshooting in order to fine tune communications with a device.

Continuing our "OmniServer Did You Know?" blog series, this blog post focuses on how to use the built-in Item Values window in the OmniServer diagnostic tools and the included OPC Test Client to test communications using OmniServer.

Read More

Topics: Wonderware, Device Integration, Protocols, OmniServer, OmniServer Did You Know

Demystifying Modbus Function Codes

Posted by Kevin Rutherford on Dec 13, 2018 2:00:00 PM

With the wide range of devices that use Modbus for their communication protocol, you'll find many different interpretations, terminology and labels with respect to how to access different types of data in those devices.  Sometimes a device manual might only refer to the supported Modbus function codes and the range of offsets available for those function codes.

In this blog post, I will step through the specifics of Modbus function codes and how they pertain to addressing, and how they affect what addresses to use in TOP Server for Wonderware applications.

Read More

Topics: Wonderware, TOP Server, Modbus, Automation 101, Protocols

Did You Know? How to Recover from Device Errors with OmniServer Error Messages

Posted by Kevin Rutherford on Nov 7, 2018 2:00:00 PM

With any communication server for collecting process data, there has to be a reliable mechanism built-in for dealing with error responses from the underlying devices.  This is true even for OmniServer as a user-configurable communication server.

Continuing our "OmniServer Did You Know?" blog series, this blog post focuses on how to use error messages and notification items in an OmniServer protocol to properly handle error responses or conditions received from your non-standard process devices.

Read More

Topics: Wonderware, Device Integration, Protocols, OmniServer, OmniServer Did You Know, error handling

Demystifying Modbus Register Addressing with TOP Server for Wonderware

Posted by Kevin Rutherford on Oct 11, 2018 2:00:00 PM

I'm sure you've all at least had some interaction with Modbus, working in the automation industry.  It's one of the most widely used protocols (if not the most widely used) in the world.  Which is both its blessing and its curse, to some extent.

Given how long Modbus has been around and in use as an "open" protocol (starting in 1979), there have been many different interpretations of Modbus throughout the years.  And with those different Modbus interpretations, much confusion about the different terminology for accessing data.

In this blog post, I will step through the basics of Modbus addressing including how offsets come into play, and how they affect what addresses to use in TOP Server for Wonderware applications.

Read More

Topics: Wonderware, TOP Server, Modbus, Automation 101, Protocols

Did You Know? How to Setup Chained Messages in OmniServer

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

In a nutshell, OmniServer's purpose is to retrieve information from devices that use ‘non-standard’ protocols to communicate such as weight scales, barcode readers, and printers.

Sometimes with some protocols, simply sending one message to a device, or doing nothing but simply transferring data to a client isn't enough. There are some more complex protocols where you will need to send a series of messages to the instrument, or respond to an event coming in from the device or to handle a sequence of handshaking messages. This is where "chained messages" come into play in an OmniServer protocol.

In this second post of a follow-up to our "OmniServer Did You Know?" blog series, we will cover how to chain multiple OmniServer command/request messages together in a protocol to flexibly handle such complex protocols.

Read More

Topics: Wonderware, Device Integration, Protocols, OmniServer, OmniServer Did You Know

Did You Know? How to Setup a Heartbeat Message in OmniServer

Posted by Kevin Rutherford on Sep 20, 2018 2:00:00 PM

As you probably know, OmniServer is used to retrieve information from devices that use ‘non-standard’ protocols to communicate such as weight scales, barcode readers, and printers.

In some situations, device protocols need to be designed to where the client application (HMI, SCADA or other), and not OmniServer, is in complete control of the polling. But before you send out the next message, how do you know if the device is still connected?

In this first post of a follow-up to our "OmniServer Did You Know?" blog series, we will cover how to create what is known as a heartbeat message to confirm your device is "listening" before sending the next message.

Read More

Topics: Wonderware, Device Integration, Protocols, OmniServer, OmniServer Did You Know

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, ProtocolDesign, 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, ProtocolDesign, 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, ProtocolDesign, Error Detection

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

see all