Barcode scanners and printers are devices that are very common in a variety of industries, whether it's for use in a manufacturing process or a multitude of other possible uses. But how do you go from scanning a barcode to printing that barcode?
In this video, we will cover how to connect to both a Datalogic barcode scanner and a Zebra barcode printer, as well as, transferring the scanned barcode data to the printer automatically.
If you know nothing else about OmniServer, you probably know it is commonly used for accessing information from devices that use ‘non-standard’ protocols including such devices as weight scales, barcode readers, and printers either over serial connections or Ethernet connections.
From its beginnings 25 years ago, OmniServer was designed to save time and effort when integrating your "other" devices, especially when compared to the time, effort and cost of alternatives such as custom code.
In this blog post, we will step through the 5 most time-saving features of OmniServer's Visual Protocol Editor, including short demo videos of each feature, highlighting how they can help you save up to 40% more of your time and effort when configuring an OmniServer protocol to communicate to your other devices.
OmniServer's connectivity and data parsing capabilities are its primary job; however, they are only the part of how OmniServer helps with integrating non-standard devices with Inductive Automation's Ignition HMI/SCADA. How does the device data actually make it into Ignition?
In this video blog, I'll show you how to make an OPC UA client connection from Ignition to OmniServer for integrating process data from all of your "other" devices that don't have a standard, off-the-shelf driver - and all without the expense and headaches of having to write custom code.
OmniServer's connectivity and data parsing capabilities are only part of how OmniServer helps with integrating non-standard devices with external software such as HMI, SCADA, MES, historians and other client application. How does the device data actually make it into the client?
In this video blog, I'll show you how to make a secure OPC UA connection from OPC UA clients supporting the Data Access profile to OmniServer for integrating 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.
It’s a new year and a new decade and, as everything moves faster, we all have to keep our knowledge and skills current.
In this blog post, we provide a quick reference to learning resources that users have told us were the most helpful to them over the course of the last year.
If you aren’t already subscribed to our blog, we encourage you to subscribe . We publish new content about once a week, sometimes more often, and you can control when you are notified of new content.
Those of you even somewhat familiar with OmniServer are likely aware that OmniServer is frequently used for accessing information from devices that use ‘non-standard’ protocols including such devices as weight scales, barcode readers, and printers either over serial connections or Ethernet connections.
Over the past several years, we've been working to evolve the OmniServer user experience with the goal of making it easier and more efficient to build a non-standard protocol/driver.
In this video blog post, we will step through the most powerful features of the new visual protocol editor for OmniServer, demonstrating the key enhancements to the user experience that will make integrating your non-standard devices easier and faster than ever.
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.
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.9 to help you with flexibility and testing while connecting to all of your non-standard devices.
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.
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.
