OmniServer
Documentation
- OmniServer I/O Server End User License Agreement
- OmniServer End User License Agreement (EULA)
- Is there a document that explains what the system tags in OmniServer are?
- OmniServer System Requirements
- What do the colors in the I/O Monitor Window of OmniServer mean?
- OmniServer Release Notes
- OmniServer Installer File Hashes
Installation/Upgrade
- [PDF] Silent Install for OmniServer
- When upgrading from V2.0 to V2.5, must I change my client program?
- Known Issue - OmniServer Version 2.10.0.3 Application Error
- Running OmniServer Keyboard Wedges on Windows Vista/Windows 7/Server 2008 operating systems
- When upgrading from V1.x to V2.x or 3.x, does anything need to be changed in the client program?
Licensing
- How to Register/Unlock an OmniServer License
- What Can Cause a Broken OmniServer License?
- [PDF] Guide - Converting OmniServer Software Licenses to Hardware Key Dongle
- OmniServer V2.8 - Upgrading V2.7 - Licensing Issue
- OmniServer Hardware Key Driver not Installing Automatically
- OmniServer License Transfer
Project Configuration/Management
- Using persisted logging in OmniServer
- Running OmniServer as Service (Server 2008/2008 R2/2012/Windows 8/Windows 7/Vista/Windows 10)
- OmniServer Upgrade Procedure - V1.x
- OmniServer Upgrade Procedure - V2.5
- OmniServer Upgrade Procedure - V2.0
- OmniServer Upgrade Procedure - Versions 2.6 or Higher to Current Version
- Setting the Update Rate for an individual Item
- OmniServer - Configuring multiple connections to the same device
- Location of Protocols and Configuration in OmniServer
- Connecting OmniServer to a Mettler Toledo IND780
- OmniServer Configuration not saving when I close the application
- OmniServer Topic "Write Delay" and "Update Interval"
- Updating the client if the same value is read.
- Can I assign multiple devices to one topic?
- Triggering messages based upon the value of an item
- Can I develop with a Demo and use the DPD file in Production?
- Same protocol on two identical devices: Works on one, not on another.
Tutorials
Protocol Configuration
- OmniServer Starter Protocol for Brooks (Fisher Rosemount) PetroCount Inventory Management System (IMS)
- OmniServer Starter Protocol for Weather Data
- Ignoring Bits within a sequence
- Sending out a sequence of commands
- Simulating a TCP Keep-Alive Message in OmniServer
- OmniServer Sample for Mettler Toledo Scales using the SICS Protocol
- OmniServer Starter Protocol for OPEN WEB NET Protocol
- Using {0xFF} as a delimiter generates an error
- Using OmniServer, How do I read a string of numbers separated by commas?
- How to determine or control what part of the message is used in the CRC calculations?
- Maximum String Length in OmniServer
- How can OmniServer recognize square brackets in my data?
- Mixing Item Translations
- Do I always have to format my data?
- How do I strip leading spaces from a number?
FAQs
- Can I connect to a TCP server application located on the same PC as OmniServer?
- How to Auto-Restart the OmniServer service
- Knowing when a device timeout occurs
- Behavior when messages are chained in OmniServer upon timeout
- OmniServer connectivity with virtual COM ports
- Backing Up / Moving OmniServer Configurations from one machine to another
- OmniServer Maximum UA Session Count
- Using Backslashes in OmniServer Protocols
- Recommendations when using a public mail server with OmniServer Email Plug-in/Wedge
- Does OmniServer Support IP Multi-Cast?
- Scaling data in OmniServer
- What does the item "Status" mean in the Item Values window?
- How do I verify the OmniServer is connected using unsolicited messages?
- OmniServer 3.0 Duplicate Topics
- DDE Connections on Newer Operating Systems (Win 7 / Server 2008 / etc.)
- Unable to Access Topic Items with Password Protected Protocol
- Disconnect/Reconnect InTouch to OmniServer during Runtime
- "Status" never goes to True (1) after device reconnects
- Do you have a driver that supports IEEE 488 GPIB?
Error Codes/Messages
- Getting Error: Unable to Connect to Runtime Program
- Error 4226 in Windows Event Log on XP SP2 Computer
- OmniServer Socket Error 10035
- OmniServer is "Unable to connect to runtime program" after installing Windows XP Service Pack 3
- OmniServer - Windows Event 33 Error Message for osrvstrt.exe process
- Received Error 1035 when starting a service
- Error Installing OmniServer V2.7 or newer on Windows 2000
- Not able to save OmniServer Protocol
- Receiving Error "You don't have the privilege to access this option" on Windows 8 or Server 2012
- Getting "Received Break" errors in OmniServer Logger.
- OmniServer File Wedge access to files on a network share
- Error 10013 (Winsock v2.0 unavailable)
- Reading both Strings and Reals in one Data Type