OmniServer - Universal OPC UA/DA Server Software
Driver for non-standard device protocols
Published by
Software Toolbox
OmniServer - Universal OPC UA/DA Server Software
Published by
Software Toolbox
Free Trial
Features
OPC standards support
OmniServer Supports the OPC UA Generic Data/Data Access profile as well as OPC Data Access 2.05a and has been interoperability and lab tested for OPC compliance. With commitment to standards, you are assured the widest range of software interoperability.
OPC UA Endpoint definition for easy integration with OPC UA Clients
![OPC standards support]()
Device/Interface types
OmniServer interfaces to a wide variety of devices. Because OmniServer was created to solve the problem of interfacing control and automation devices that do not use standard protocols like Modbus, the range of device types supported is infinite.
All devices have in common that they use one of these physical interface types:
- Ethernet via TCP/IP, UDP or Telnet
- USB (mapped as Com: port by low level drivers provided with the hardware)
- Serial / Com Port
- LPT port
Some examples of the types of devices that OmniServer interfaces to includes but is not limited to;
- Weigh Scales
- Barcode Readers
- RFID Readers
- Labelers
- Printers
- X-Ray/Meat Scanners
- Laser marking systems
- Mass Spectrometers
- Gas chromatographs
- Combustion analyzers
- Message Boards/Displays
- Security cameras
- Door control systems
![Device/Interface types]()
Codeless protocol implementation
OmniServer brings an end to custom code for device communications drivers. No more problems with supporting and maintaining custom solutions developed by an employee or contractor who is no longer available to help.
With the OmniServer protocol editor, you can start with one of our included samples or watch our training videos to learn how to visually take the information provided by your hardware vendor, and build up the communications steps.
![Codeless protocol implementation]()
Wizard driven configuration
Once your protocol is defined in the OmniServer protocol editor, you marry it up to your device settings to form a topic which defines how your HMI/SCADA/MES will see the device when browsing for tags in the OmniServer. Typically your system integrator or an automation engineer defines the protocol one time and saves it. The wizards help a novice user define basic communications settings for talking to the device, and pick the protocol used by the device.
Wizard configuration connects protocols with devices
![Wizard driven configuration]()
Free OPC Test Client included
Engineers configuring OmniServer to communicate with a device typically work independently from the HMI/SCADA/MES/Historian engineer. By including a free OPC Test Client in the product installation, the engineer configuring OmniServer can test their work independently. When the HMI, SCADA, MES, or Historian is connected, the engineer can be confident the right data appears to the client. If there is a problem, the test client application helps find where to look for the problem.
![Free OPC Test Client included]()
Extensive troubleshooting tools
Because OmniServer is part of a system involving a device, a communications network/path, and an HMI/SCADA/MES/Historian system, it's important to have tools to aid in finding what is wrong when unexpected results occur.
OmniServer provides a wide range of tools built into the product to help engineers and technicians isolation problems. See the Resources area for a copy of our Troubleshooting Tools Briefing document.
Item Values Window
-
This window shows values and status for all active items which have a client requesting data.
Logger Window
-
The logger window allows you to capture sends, receives, and errors in the raw protocol format which helps the engineer that configured the protocol find problems.
I/O Monitor
-
The I/O Monitor is a diagnostic and informational tool that displays both the data being transmitted to your devices and the data being received from your devices for the selected device or topic. If there is a problem in the protocol itself, the I/O Monitor allows us to see the actual data bytes being sent and received. This allows us to compare the actual data with the pattern in the protocol messages and determine what the problem is.
![Extensive troubleshooting tools]()
Datalogging & Email plug-ins
OmniServer offers optional plug-ins that allow you to do other things with the data while still sending it to an HMI/SCADA/MES system.
The email plug-in sends custom formatted messages based on condition.
The database plug-in logs data on condition/event to any ODBC compliant database.
The file plug-in logs data to CSV/text formatted files.
The OmniServer Pro Edition includes all of these plug-ins.
![Datalogging & Email plug-ins]()
OPC standards support
OmniServer Supports the OPC UA Generic Data/Data Access profile as well as OPC Data Access 2.05a and has been interoperability and lab tested for OPC compliance. With commitment to standards, you are assured the widest range of software interoperability.
OPC UA Endpoint definition for easy integration with OPC UA Clients
Device/Interface types
OmniServer interfaces to a wide variety of devices. Because OmniServer was created to solve the problem of interfacing control and automation devices that do not use standard protocols like Modbus, the range of device types supported is infinite.
All devices have in common that they use one of these physical interface types:
- Ethernet via TCP/IP, UDP or Telnet
- USB (mapped as Com: port by low level drivers provided with the hardware)
- Serial / Com Port
- LPT port
Some examples of the types of devices that OmniServer interfaces to includes but is not limited to;
- Weigh Scales
- Barcode Readers
- RFID Readers
- Labelers
- Printers
- X-Ray/Meat Scanners
- Laser marking systems
- Mass Spectrometers
- Gas chromatographs
- Combustion analyzers
- Message Boards/Displays
- Security cameras
- Door control systems
Codeless protocol implementation
OmniServer brings an end to custom code for device communications drivers. No more problems with supporting and maintaining custom solutions developed by an employee or contractor who is no longer available to help.
With the OmniServer protocol editor, you can start with one of our included samples or watch our training videos to learn how to visually take the information provided by your hardware vendor, and build up the communications steps.
Wizard driven configuration
Once your protocol is defined in the OmniServer protocol editor, you marry it up to your device settings to form a topic which defines how your HMI/SCADA/MES will see the device when browsing for tags in the OmniServer. Typically your system integrator or an automation engineer defines the protocol one time and saves it. The wizards help a novice user define basic communications settings for talking to the device, and pick the protocol used by the device.
Wizard configuration connects protocols with devices
Free OPC Test Client included
Engineers configuring OmniServer to communicate with a device typically work independently from the HMI/SCADA/MES/Historian engineer. By including a free OPC Test Client in the product installation, the engineer configuring OmniServer can test their work independently. When the HMI, SCADA, MES, or Historian is connected, the engineer can be confident the right data appears to the client. If there is a problem, the test client application helps find where to look for the problem.
Extensive troubleshooting tools
Because OmniServer is part of a system involving a device, a communications network/path, and an HMI/SCADA/MES/Historian system, it's important to have tools to aid in finding what is wrong when unexpected results occur.
OmniServer provides a wide range of tools built into the product to help engineers and technicians isolation problems. See the Resources area for a copy of our Troubleshooting Tools Briefing document.
Item Values Window
- This window shows values and status for all active items which have a client requesting data.
Logger Window
- The logger window allows you to capture sends, receives, and errors in the raw protocol format which helps the engineer that configured the protocol find problems.
I/O Monitor
- The I/O Monitor is a diagnostic and informational tool that displays both the data being transmitted to your devices and the data being received from your devices for the selected device or topic. If there is a problem in the protocol itself, the I/O Monitor allows us to see the actual data bytes being sent and received. This allows us to compare the actual data with the pattern in the protocol messages and determine what the problem is.
Datalogging & Email plug-ins
OmniServer offers optional plug-ins that allow you to do other things with the data while still sending it to an HMI/SCADA/MES system. The email plug-in sends custom formatted messages based on condition.
The database plug-in logs data on condition/event to any ODBC compliant database.
The file plug-in logs data to CSV/text formatted files.
The OmniServer Pro Edition includes all of these plug-ins.
Get Resources and Start FREE Trials
Easy Product Activation with Your Account
Products Saved to Personal Digital Library
Register Now
Already have an account?
Log In