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.
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.
A Topic Variable is a flexible special OmniServer element that gives you the ability to define a device specific variable such as a Device ID at the OmniServer topic level. This effectively makes your OmniServer protocol reusable for those devices using the same protocol, since you can now specify the value of the variable when creating the OmniServer topic instead of creating a protocol for each device with the value hard coded.
In this video blog, I show you how to get the most from your OmniServer by using topic variables with your protocol to reduce your engineering time and effort to create an OmniServer protocol.
You've probably either received one of my emails or possibly heard from a colleague about our latest TOP Server release – so you may have a general idea of the key new features in the TOP Server V6.3 release.
In this blog, I'll go through the top 3 key features released in V6.3 in more detail and how they benefit you as a TOP Server user.
There are some nice, time-saving updates available in TOP Server V6.2. In case you happened to miss it, I did a high-level post shortly after the release giving you an overview of the four biggest features from V6.2 - click here to see that post.
A Register Number is a time-saving special OmniServer element that allows you to configure one item that is requesting the same type of memory or offset in a device instead of one item for each memory or offset location.
In this video blog, I show you how to get started using registers to more efficiently build an OmniServer protocol without having to manually create an item for every piece of data whenever possible.
