The following short video blog demonstrates step-by-step just how easy it is to configure the Cogent DataHub to handle redundant failover between OPC UA data sources, OPC DA data sources and more.
Recently we worked with an aluminum smelter operation that has doubled in size since it first opened and has made a significant positive impact on the local economy by supplying aluminum to local industries which has fueled their growth.
Like any growing business, this user is always seeking ways to improve operations and reduce risk of downtime. In the end they need to deliver returns to their shareholders while continuing to support the local community, all of which requires consistent predictable operational results. In this blog post, we'll cover how they used an off-the-shelf solution for integrating varied systems to reduce life cycle costs.
OmniServer's core connectivity and data parsing abilities are only part of the equation when integrating non-standard devices with Wonderware. How does that device data then make it up into Wonderware?
In this video blog, part of a series on connecting Wonderware to OmniServer, I'll show you how to make a basic OPC DA connection from Wonderware System Platform to OmniServer for integrating process data from all of your "other" devices that don't have a standard, off-the-shelf driver - all without having to write custom code.
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.
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.
With DDE (Dynamic Data Exchange) fast becoming obsolete technology (Microsoft superseded DDE with OLE years ago), OPC DA and, more recently, OPC UA data sources have become the primary go-to for process data integration. Recently, Microsoft even disabled certain DDE functionality in MS Office applications due to security concerns and malware exploitation targeting the DDE interface.
But the usefulness of MS Excel for data analysis across many industries even today is still undeniable and the primary mechanism for MS Excel to connect to a data source is via DDE. So what do you do if you're still using MS Excel for process data analysis and reporting via DDE? What's the alternative?
The following short video blog demonstrates step-by-step how to easily read/write data from process data sources (OPC DA and OPC UA Servers) using MS Excel (without DDE) with the Cogent DataHub.
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.
Knowledge is power and knowing the current state of your underlying server hardware for your process can be very powerful indeed. Keeping a pulse on information like CPU usage, available memory, memory consumption by a process and whether or not critical process are still running can be the difference between hours of downtime with thousands of dollars in lost production and being able to proactively avoid any downtime.
The following short video blog demonstrates step-by-step how easy it is to use the Cogent DataHub to monitor vital system statistics on your servers that can be shared in real-time via supported client interfaces such as OPC DA and OPC UA or even send email/SMS notifications.
