Cogent DataHub is known for its extensive connectivity to OPC DA, OPC UA, OPC A&E, Databases, Excel, ODBC, DDE, Linux, Modbus. The new V9 takes our saying that "once the data is in DataHub, it can go anywhere" to a new level with IoT connectors and more as listed below.
In this blog post, I'll provide insight into these new features and show you how Cogent DataHub delivers secure, scalable, integrated connections within and between your plants, to the cloud and beyond.
As part of our continuous improvement process at Software Toolbox, OmniServer is updated several times a year to add additional useful features and tools, and to resolve any known issues.
In this video blog, I will cover updates and enhancements available in OmniServer V3.1.0.5 to help you with usability, performance and troubleshooting while connecting to all of your non-standard devices.
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 AVEVA applications.
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.
If you're reading this post, you're more than likely working in the oil and gas industry, and you probably have flow computers and devices from different vendors storing historical EFM (Electronic Flow Measurement) data. And, if your company is anything like the other companies in that industry, you use that EFM data for analysis, custody transfer and production optimization using one of the common EFM flow measurement analysis packages such as Flow-Cal, Quorum PGAS or even CSV or SQL.
In this blog post, I'll cover the video how-to resources available to help you get started using our EFM Suite for TOP Server to poll and export collected EFM data from various flow computers for Wonderware applications.
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.
If you're in the oil and gas industry, you're aware that, flow computers and devices from different vendors store historical EFM (Electronic Flow Measurement) data that is used for analysis, custody transfer and production optimization. To that end, oil and gas companies use several EFM flow measurement analysis packages such as Flow-Cal, Quorum PGAS or even CSV or SQL to store and analyze that collected EFM data.
In this video blog, I'll show you how to get started using our EFM Exporter plug-in for TOP Server to poll and export collected EFM data from various flow computers for Wonderware applications.
OmniServer's connectivity and data parsing capabilities are only part of how OmniServer helps with integrating non-standard devices with Wonderware. How does the device data actually make it into Wonderware?
In this video blog, part of a series on connecting Wonderware to OmniServer, I'll show you how to make a basic SuiteLink connection from Wonderware Historian to OmniServer for historizing process data from all of your "other" devices where there isn't a standard, off-the-shelf driver - all without the cost and effort of having to write a custom driver.
