OmniServer gives you the ability to access data from non-standard devices that would likely otherwise be unavailable to your process and business systems. OmniServer does this by taking care of all the polling and data parsing from those devices for you without the use of a programming language.
You need OmniServer because it gives you access to more of your process data, helping you make better and more informed decisions with the potential to lower costs and downtime while increasing efficiency and profitability.
For connecting client applications such as HMI, SCADA, MES or historians, the following standard interfaces are supported:
Connect any or all of your client applications to OmniServer using any combination of the above client interfaces at the same time.
For connecting devices, serial port, Ethernet, LPT printer port and USB (via virtual COM port, where available) are supported for connecting to:
Unlike most OPC servers that can communicate with specific devices and no others, OmniServer can be configured to communicate with virtually any one device or multiple devices.
OmniServer's easy-to-use visual protocol editor lets you build a description of the data stream used to communicate with the device (referred to as a "Protocol") using documentation from your device manufacturer for the details of the communication protocol.
Once the protocol is configured, OmniServer takes care of the communications with the device and the delivery of the data to your client application.
OmniServer's Visual Protocol Editor is so much easier than learning how to write custom code - With drag-and-drop support for building protocol messages, table-based configuration for items and other protocol components, configurable "favorite" protocol message sequences and more.
Through our continuous improvements process, OmniServer gets better and easier to use each year. Ease-of-use features to enabling you to configure OmniServer as efficiently as possible include:
These features make configuration easier so you can focus on the other items on your to-do list:
Error Detection Codes (EDC) are sequences sometimes included in a message that perform some calculation on the bytes of the message to ensure that it has arrived complete, correct and hasn't been altered or tampered with in any way.
An EDC can include Checksums, CRCs and LRCs. OmniServer includes a large selection of the most common EDCs. And there is a custom EDC builder for EDCs that aren't covered by those common ones.
Optional hardware key dongle support is also available for all editions (for new and existing licenses).Already Know What Edition You Need or Need a Hardware Key? Order Here!
32-Bit (x86) Operating Systems (including Service Packs)
64-Bit (x64) Operating Systems (including Service Packs)
***Windows XP and Server 2003 are no longer supported as of V18.104.22.168***
Contact us if you require support for Windows XP, Vista, or Server 2003.
OmniServer guidelines are that hardware should meet the recommended requirements for the Operating System to be used.
In general, the machine should have the following at a minimum:
OmniServer online documentation covers release history, how to get started, details on menus and settings, best practices, troubleshooting tools, and more.
We know that sometimes it helps to see someone showing you how to do things. We have a wide range of videos available for OmniServer from short how-to videos to detailed on-demand webinars. Click to view the videos list
OmniServer includes several built-in tools for debugging protocol messages and troubleshooting issues.
The OmniServer Troubleshooting Brief covers the basics of those troubleshooting tools and how to use them.
Additionally, our online troubleshooting flowchart is a good way to step through what might be causing an issue.
OmniServer is a true server application - a client connection requesting at least one piece of data from at least one device is required. To that end, a flexible and powerful OPC Test Client installs with OmniServer for getting up and running with your non-standard devices. This is especially useful if your final client application is not yet available.
OmniServer installs with a selection of sample protocols ranging from barcode scanners to weigh scales. These free samples are a good examples if you're connecting to a similar device type.
Also, we have accumulated a number of other samples for protocols created for various devices in OmniServer.
Don't see your protocol/device listed? Contact our technical support team with the make/model of your device and any protocol information you may have and we can assist you.
One of the trickiest questions to answer when a user asks it is "What specific devices does OmniServer connect to?". It's tricky because OmniServer is so versatile that it connects to hundreds of device types - barcode scanners, weigh scales and bridges, RFID systems, intercom system and so many more.
So one of the best ways to explain what OmniServer connects to is with some real-world examples.
The demo is the full product once licensed. Once a client application connects to the OmniServer, the OmniServer runtime will operate for 2 hours at a time. At the end of the 2 hour demo period, the demo timer must be reset by restarting the OmniServer runtime.