Software Toolbox Technical Blog

Another common non-standard device integration scenario that we encounter is integration of phone and intercom systems with the control system.  There is normally a control application provided by the system manufacturer but that adds another system that the user has to know, use and maintain.

In the next blog post of a series on OmniServer user stories, we’ll discuss a specific use case of a system integrator working with a correctional facility needing direct integration of their Telecor phone and intercom system with Wonderware.  And we'll discuss how OmniServer provided a driver to the Telecor system without the need for custom code, eliminating the need for an additional control application.

A common non-standard device integration scenario that we encounter is needing to integrate devices that are not currently automated in any way.  There is some manual process to send data to or retrieve data from these devices which, as always, introduces greater risk of error due to human factors.

In the next blog post of a series on OmniServer user stories, we’ll discuss a specific use case of a user in consumer packaged goods needing to automate printing directly from Wonderware using data from their MES system.  And we'll discuss how OmniServer provided a driver without the need for custom code, eliminating their inefficient manual printing process.

Another common device integration scenario that we frequently encounter at Software Toolbox is needing to make weight data from a scale, weigh bridge or other weighing equipment available in an HMI or SCADA such as Wonderware.  Whether it's manufacturing, food and beverage or other industries, weight data is, for all intents and purposes, very similar regardless of what is being weighed.

In this second blog post of a series on OmniServer user stories, we’ll discuss a specific use case of a food and beverage producer needing to integrate their GSE scale data with Wonderware and SQL and how OmniServer provided a driver without the need for custom code.

One of the most common device integration scenarios that we encounter is needing to control a printer and/or label applicator directly from an HMI or SCADA such as Wonderware.  And printers can be tricky, with most having similar but still different communication protocols - so how does one account for that kind of variability?

In this first blog post of a series on OmniServer user stories, we’ll discuss a specific use case of a paper products manufacturer needing direct control of their printing and labeling process directly from Wonderware and how OmniServer provided a driver without the need for custom code.

With the relatively recent availability of OPC UA server capabilities in Siemens S7-1500 PLCs, access to live production data is now open to third-party applications. As a result, those applications can now communicate with hardware that was formerly locked behind proprietary communication drivers.

The OPC Data Logger's OPC UA client interface allows users to quickly and easily connect to S7-1500 PLC’s and log data to their preferred data storage option without the need for intermediate applications. This blog post covers the high-level steps involved with logging data from an S7-1500 controller and you can then download the free hands-on guide with detailed steps.

Whether your role is IT or OT, there tends to be an almost universal dislike of having to work with printers. It is likely, for this exact reason, that when tasked with integrating a printer (be it a laser jet printer for labelling packaging, or a label printer to track your products) many users are simply forgoing the integration completely.  That might mean opting for limited integration with a PLC on the line or simply choosing to not integrate at all while continuing to make any configuration changes manually.

In this blog post, continuing our OmniServer Did You Know series, we’ll discuss several methods that users have implemented over the years when needing to use printers in a process and how OmniServer provides an off-the-shelf, easy-to-use alternative for direct integration of most printers with your process control systems.

OmniServer's main purpose is enabling connectivity without custom code for devices that use ‘non-standard’ protocols to communicate such as weight scales, barcode readers, and printers.  And OmniServer does that in a more efficient and cost-effective manner than writing custom code.

Furthering the goal of efficiency and cost-effectiveness, you may or may not be aware that OmniServer supports CSV import and export for speedy configuration of many things including topics, devices and, in the actual protocol itself, items, registers, topic variables and even messages.  On larger projects, this provides a substantial time savings.

In this post continuing our "OmniServer Did You Know?" blog series, we will cover how to use CSV import and export in OmniServer to facilitate faster configuration on larger protocol implementations.

If you're familiar with OmniServer, you know that OmniServer is frequently used for accessing 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.

With the advent of touchscreen technology and the increasing availability and familiarity with drag-and-drop functionality across computer systems and applications, we feel it is important to evolve the OmniServer user experience to be more inline with current technologies and user expectations regarding ease-of-use.

In this blog post, we will cover a visual protocol editor we've been working on for OmniServer, showing you the key enhancements to the user experience that will make integrating your non-standard devices easier than ever.  And you'll be given the chance to download the free trial.