Skip to content
Ask A Question
  • There are no suggestions because the search field is empty.

Same protocol on two identical devices: Works on one, not on another.

I have developed a protocol to talk to my device. It works great. However, when I use the same protocol on an identical, second device, it doesn't poll the device or read the data correctly. What is happening?

This means that the second identical device is not as identical as thought. Something on that device has been configured differently from the first, working, device.

Here's how to find out what to check for on the device. In these steps, "Device #1" is the device on which the OmniServer protocol works, and "Device #2" is the one on which the protocol doesn't work:

  1. Compare the data coming from the Device #1 and Device #2. This can be done either by looking at the OmniServer I/O Monitor outputs for each device or the output of the OmniServer Logger for each device.
  2. If the data for Device #2 is vastly different from Device #1 (for example, Device #1 says "Software Toolbox" and Device #2 says "sfIU7326543&;;0"), then suspect a COM port setting or garbage on the line. If you can eliminate these, then suspect a configuration problem on Device #2.
  3. If the data for Device #2 looks the same as Device #1, look again. Somewhere, something is definitely different. Normally, this will take the form of a missing EDC (error detection code) or a missing delimiter, such as a Carriage Return or EOT. This will be a configuration problem on the part of the device.