Skip to content
Ask A Question
  • There are no suggestions because the search field is empty.

OmniServer Release Notes

The latest version of OmniServer can be downloaded here.  If you need an older version, please open a support ticket and let us know what version you need, and your serial number.

V3.5 Build 002 -  May 2025

  • Active Client Count now visible in UI for:
    • OPC DA Clients
    • OPC UA Clients
    • SuiteLink Clients
  • Configurable Max UA Sessions property now available for each individual OPC UA Endpoint
  • Resolved issue related to converting software licenses to hardware keys

V3.5 Build 001 -  March 2025

  • Enable/Disable OPC UA Endpoints
  • Copy OPC UA Endpoints to Clipboard
  • Resolved issue related to how OPC UA Configuration changes are applied
  • MQTT Client - removed case-sensitive requirement
  • Updated Dotfuscataor V7.1.0 for Visual Protocol Editor (VPE).

V3.5 Build 000 -  October 2024

  • Updated Installer to InstallShield 2023.
  • Removed ability to delete Default End Point in UA Configuration Menu.
  • Internal OPC UA enhancements.

V3.4 Build 002 -  August 2024

  • Improved performance and reliability of Device_Issue system tag
  • Unnecessary restart of UA stack eliminated when UA Configuration window is opened.
  • Implemented error state in logger to detect COM port error reporting from operating system.
  • Improvements made to Visual Protocol Editor Find and Replace feature. 

V3.4 Build 001 -  July 2024

  • New MQTT (Message Queuing Telemetry Transport) Client Plug-In add to Professional Edition allowing integration of non-standard hardware with MQTT Brokers (i.e. HiveMQ, Mosquitto, and others)
    • Quality of Service (QoS) mechanisms incorporated 
    • Username/Password authentication support
    • User-configurable Client IDs for scalability
    • Various Payload format types supported
      • JSON (JavaScript Object Notation)
      • Key Value
      • Custom

V3.3 Build 006 - February 2024

  • Find and Replace feature implemented in Visual Protocol Editor, allowing users to find and replace specific syntax from all Protocol Data and Messages tabs. 

V3.3 Build 005 - January 2024

  • Resolved issue in Visual Protocol Editor where Error Detection Code Polynomial values were not maintained when switching between Legacy Editor. 
  • Enhancement of Translations in both Visual Protocol Editor and Legacy Editor, allowing multiple received values to be translated to the same output value. 
  • Improved Visual Protocol Editor usability by implementing optional global and protocol editor-level setting that replaces all ASCII spaces in all messages with OmniServer {$SP} representation of a space. 

V3.3 Build 004 - December 2023

  • Implemented 10-day Emergency License Feature. OmniServer switches to Emergency Mode in the event of a license break.
  • Increased max number of OPC UA sessions to 300 through the use of multiple endpoints.
  • Improved protocol editor usability by adding required prefix notifier.  

V3.3 Build 003 - September 2023

  • Updated relevant components to OpenSSL version 3.0 for improved security. 
  • Updated OPC UA Server interface to accommodate OpenSSL requirements. 
  • Added configurable Max OPC UA Session Count within OPC UA Configuration UI with a valid range of 1 - 100 sessions. 
  • Various enhancements to Visual Protocol Editor (VPE).

V3.2 Build 015 - July 2022

  • Added CSV import/export support for Response Only (Unsolicited) protocol messages for the Visual Protocol Editor (VPE).
  • Resolved an issue in the Visual Protocol Editor that resulted in extra invalid characters at the end of protocol messages that resulted in a non-functional protocol.

V3.2 Build 014 - May 2022

  • Updated the OPC UA server interface to address a security vulnerability resolved by the latest third-party OPC UA components.

V3.2 Build 013 - May 2022

  • Resolves a known issue with protocol Error Messages not being properly processed when set to an Action Type of "Accept".
  • Resolves a known issue with the Visual Protocol Editor where the :Q sequence format (Ignore leading spaces on numerics) was being treated as invalid - this format is now accepted in the VPE.
  • Added support for special decimal, octal and hexadecimal number formatting to the Visual Protocol Editor (for example, {123} for decimal, {0o123} for octal, {0x123} for hexadecimal).
  • Updated the OPC UA server interface to address a security vulnerability (click for full details on potential impacts, next steps and updated version download).
  • Resolves high CPU experienced with some response only protocols on some machines.

V3.2 Build 012 - January 2022

  • Windows Server 2022 is now officially supported.
  • Windows 11 is now officially supported.
  • Added the ability to export and import the entire OmniServer configuration including devices, topics and the protocols assigned to configured topics. Exports are zip files containing .csv exports for devices and topics and .DPD protocol files.
  • Enhanced device export and import allowing all devices regardless of type (Ethernet, Serial and/or LPT) to be exported/imported in the same file.
  • Added the ability to reset topic and device poll statistics in the OmniServer Configuration (under Diagnostics > Poll Statistics, right-click on the associated "reset_device" or "reset_topic" and select "Reset Device Statistics" or "Reset Topic Statistics" respectively. All server statistics may also be reset by right-clicking on "reset_all_topics_devices" under the $system.overallstatus group and selecting "Reset All Topic/Device Statistics".

V3.2 Build 011 - October 2021

  • Enhanced support/maintenance period support in OmniServer licensing to better handle upgrades to new versions with both hardware and software licenses. Upgrades should now work seamlessly when the support/maintenance date on the machine is current and eligible for the version being installed.
  • Updated the Email Plug-in / Wedge to support configurable SSL/TLS encryption with a configurable port that auto-defaults to the most common port for the selected encryption type, as well as, a new test function that allows you to easily confirm your email settings are correct.
  • Removed the default NetDDE dependency to better support users on newer operating systems where NetDDE is no longer included. This makes it easier and more user-friendly to enable OmniServer to run as a Windows service.
  • Resolved an issue when cancelling the installation of an upgrade could cause the user not to be able to access the previously installed version.

V3.2 Build 010 - August 2021

  • Resolves a known issue introduced in V3.2.0.9 that incorrectly initializes all item values to "1" until an update is received from the device and trigger items would incorrectly initialize to bad quality, preventing writes from OPC UA clients.
  • Resolves a known issue introduced in V3.2.0.8 affecting the OmniServer runtime when running as a Windows service - previously, after opening then closing the OmniServer Configuration interface, the runtime would stop communicating with device until it was restarted.
  • New toolbar and File menu options for import and export of the entire OmniServer topic, device and protocol configuration - topics and the devices and protocols they are using will be exported as one zip file which can then be imported as a whole in another OmniServer - useful for backing up or transferring existing configurations.
  • New File menu option for saving/exporting the OmniServer configuration (omnisrv.cfg) file - useful for backing up or moving your topic, device and plug-in configurations to another machine.
  • New toolbar and File menu options for saving/exporting one or more OmniServer protocols - useful for backing up or moving protocols (supports multi-select and has an "All" option to easily save/export all of your existing OmniServer protocols.

V3.2 Build 009 - July 2021

  • Updates to the Visual Protocol Editor for increased usability including message fields being already expanded and more intuitive right-click options for adding new elements such as items and topic variables.
  • Improves user experience when defining topics and devices by preventing settings and buttons from being cut off when the user interface was resized too small.
  • Resolves an issue where OPC UA clients writes to trigger items required an initial value (NOTE: for items that are NOT triggers, if OPC UA writes are required and the item hasn't received an initial update from a device, an Initial Value must be specified for the item in the OmniServer protocol).
  • Resolves issue with new protocols not appearing until a restart of the runtime.
  • Resolves issue that required the toolbar button for the Software Toolbox OPC Test Client to be clicked twice to launch for subsequent launches.

V3.2 Build 008 - May 2021

  • Updated OPC UA common name visible to OPC UA clients to "UaOmniserver@[MachineName]". (NOTE: Requires that OPC UA security certificate be re-issued to take effect.).
  • Updated some labeling in the Visual Protocol Editor (VPE) to be more descriptive.
  • Updates to the installer to improve handling of installation for some prerequisites.
  • Resolved an issue where protocol changes on copied protocols weren't being saved until the runtime was restarted.
  • Resolved issue with opening password-protected protocols using the Visual Protocol Editor (VPE).
  • Resolved an issue on some systems with items not updating unless a second client application is connected.

V3.2 Build 007 - February 2021

  • Resolves known issue introduced in OmniServer V3.0.113 where it was not possible to specify both a Port and Listen Port for Ethernet configurations of type UDP. This issue affected versions 3.0.113 through 3.2.0.6 - users requiring this functionality with UDP devices should upgrade to V3.2.0.7 or newer.

V3.2 Build 006 - January 2021

  • Resolves issue with delayed Windows recognition of hardware key licenses, resulting in reversion to demo status
  • Resolves issue with hardware key licenses not being recognized on fresh V3.2.0.5 and the initial release of V3.2.0.6 installations
  • Resolves issue with OmniServer correctly processing Support/Maintenance update codes for hardware key licenses when renewing OmniServer Support/Maintenance.

V3.2 Build 005 - October 2020

  • New "Use Strict Message Parsing" setting added for better compatibility with certain protocols without a fixed leading character.
    • Setting is disabled by default for compatibility with most protocols.
    • Setting is accessible via the OmniServer Configuration under
      View -> Runtime Options -> System Settings.
  • Updated OPC UA server interface for increased reliability and performance.
  • Resolves known memory leak and hanging behaviors affecting some users.
  • Resolves known issue affecting registered transactions when using OPC UA.
  • Compatible with the latest Windows 10 Update (Version 2004).

V3.2 Build 003 - July 2020

  • Added hardware key licensing support - this is available for purchase as an option with any new license and for existing software licenses.
  • Fixed issue with Topic Variable display labels during Topic Configuration - Topic Variable name is now displayed instead of Descriptions.
  • Added support for legacy number encoding in use by certain protocols created with older versions of OmniServer - those protocols are now fully compatible with the current version.
  • Fixed issue related to SuiteLink client connection issues that could cause a crash under certain circumstances.

V3.2 Build 002 - March 2020

  • Fixed issue requiring protocol editor to be closed for changes to be applied to the runtime.
  • Fixed issue with duplicate protocol creation when switching between the Visual Protocol Editor and the Legacy Protocol Editor.

V3.2 Build 001 - January 2020

  • Now installs with a new Visual Protocol Editor which adds a host of ease-of-use features for building and editing protocols, including:
    • Drag-and-drop support
    • Table-based configuration of items, topic variables, etc.
    • User-configurable “Favorites” – build your own frequently used sequences for drag-and-drop into your protocol messages
    • Configurable layout for building protocol messages – show/hide items, topic variables, special characters and more based on what you need.
  • The Visual Protocol Editor is now the default editor – try it with your protocols and see how easy it is.
    • NOTE:  The Legacy editor is still included and it’s easy to switch as needed.
  • Windows Server 2019 is now officially supported.

V3.1 Build 009 - October 2019

  • Now installs with an upgraded Software Toolbox OPC Test Client for testing protocols and OPC DA connections to OmniServer.
    • New toolbar button in the OmniServer configuration for launching the Software Toolbox Test Client – by default, the client will automatically subscribe to all protocol items for any topics configured in OmniServer.
    • Auto-subscribe feature can be turned off under View -> General Options by disabling the setting “Automatically add all topic tags when launching Test Client”.
  • Option is now provided during installation to specify a different directory for OmniServer’s ProgramData folder which is where protocol and configuration files are located.

V3.1 Build 008 - August 2019

  • Resolves a known issue with update and modify installations in the previously released V3.1.0.8 installer on 30 July 2019.  Certain required Windows runtime components were not being installed as needed when upgrading or modifying an existing OmniServer installation.
  • Resolves known issue with initial value updates to OPC clients provided incorrectly as a Boolean data type.
  • Resolves known issue with the port displayed for an Ethernet device in its properties description – only the outbound TCP port was ever displayed even if the device was defined as Inbound.  Now the correct port is displayed corresponding to the device configuration for “Inbound Connection” being enabled or disabled.
  • Resolves known issue with OPC browsing ordered of items being out of order.  The order of items is now correctly returned in alphabetical order for ease of browsing.
  • Enhanced system logging to assist in better troubleshooting during unexpected system crashes.
  • Resolves issue with protocol Error Messages.
  • Resolves issues with the protocol UI through inclusion of certain Windows runtime components normally installed by Windows on most systems.
  • Resolves an issue introduced in a previous version that caused some unsolicited messages to not be recognized.
  • Installer now checks for Admin privileges.

V3.1 Build 007 - April 2019

  • Updated OPC UA server interface supports latest secure encryption algorithms and certificate store:
    • Supported security policies (encryption algorithms) now include:
      • Basic256 SHA256
      • AES128 SHA256 RSA-OAEP
      • AES256 SHA256 RSA-PSS
    • OpenSSL Certificate Store
    • NOTE: Users making OPC UA connections to OmniServer should confirm that your OPC UA Client application supports one of the above security policies prior to upgrading to OmniServer V3.1.0.7 - it will be necessary to change your OPC UA connection settings both in your OPC UA Client and your OmniServer OPC UA endpoint to match using one of the new security policies.
  • Updated Visual Studio runtime to VS2015 for OPC UA updates - as a result, support for Windows XP and Server 2003 operating systems has been discontinued.
  • Resolved known issue using Ping utility in OmniServer device configuration without Admin privileges.
  • Resolved issue with inbound UDP Ethernet connections introduced with V3.1.0.6.
  • Resolved issue with importing configuration files introduced with V3.1.0.6 that caused the runtime to crash.

V3.1 Build 006 - January 2019

  • Resolved performance issues related to frequent client write behavior.

V3.1 Build 005 - October 2018

  • Updated topic import features for increased performance resulting in faster imports of larger topic counts.
  • The user interface has been updated for the Device State Coloring feature - this feature is now enabled/disabled under the Diagnostics main menu (previously, this feature was enabled under View -> Runtime Options -> System Settings.
    • This update provides improved stability and performance for this feature.

V3.1 Build 004 - August 2018

  • Added a new server-level Status item feature - server-level Overall_Status is a composite item of all individual topic-level Status items that will show a state of "True" when any topic status is "False" meaning the topic is having communication issues.
    • This item can be monitored from client applications as an overall server level indicator that there may be an underlying communications issue to diagnose.
  • Added device status color coding to the OmniServer user interface which works in conjunction with an individual topic's status, enhancing visual troubleshooting.
    • When the topic's Status is "True" communications are normal and the associated device will be green in the Devices view in OmniServer.
    • When the topic's Status is "False" there is a communications fault and the associated device will be red in the Devices view in OmniServer.
    • NOTE: Users wishing to take advantage of this functionality must be enable the setting "Activate the Device Runtime Behavior" available in the View menu under Runtime Options -> System Settings.  (Starting with V3.1 Build 005, this feature is now enabled/disabled under the Diagnostics main menu)
  • Added a new Diagnostics view - Offline Devices - which will display any devices having communications issues (i.e. devices in red, per the new color coding) along with the error causing the communication issue.
  • Resolved a known issue with topic import/export functionality that could cause the OmniServer configuration to crash unexpectedly.

V3.1 Build 003 - April 2018

  • Added button to Device properties window for creating a new Topic - Topic is created using the specific device where the button was pressed.
  • Updated all configuration windows to support using the Tab key to move from one field to the next.
  • Increased the length of the drop-down list for available Protocols when configuring a Topic.
  • Improved the warning message displayed when attempting to launch the OmniServer Poller when it is already running as a Windows service.
  • Resolved an issue with initial values not being respected for string items when a command/response message was being automatically activated.
  • Resolved an issue with importing password-protected protocols.

V3.1 Build 001 - March 2018

  • Resolved an issue with inbound TCP socket handling introduced with V3.1.0.0.

V3.1 Build 000 February 2018

  • Added new system items for resetting Poll Statistics at the topic and device level, as well as resetting all Poll Statistics for the entire server.
    • Items “reset_device”, “reset_topic” and “reset_all_topics_devices” are now available in the Poll Statistics groups for each respective device and topic.
    • Refer to help file section Server Details > Diagnostic Windows > The Poll Statistics Window for full details.
  • Added new device-level system items for monitoring and controlling OmniServer connections to a device from a client application.
    • Items “device_status” and “toggle_connection” are now available in the Poll Statistics groups for each respective device.
    • Refer to help file section Server Details > Diagnostic Windows > The Poll Statistics Window for full details.
  • Added new device-level system item for monitoring when there are errors occurring for a specific device.
    • Item “device_issue” is now available in the Poll Statistics groups for each respective device.
    • Refer to help file section Server Details > Diagnostic Windows > The Poll Statistics Window for full details.
  • Improved validation on entry of invalid Unlock Codes during OmniServer licensing.
  • Resolved known issue with self-registration during OmniServer uninstall.
  • Resolved known issue with re-import on topic export lists edited in Microsoft Excel.
  • Resolved known issue saving changes during TCP Device edits.

V3.0 Build 116 - June 2017

  • Added protocol formatting support for ignoring leading zeroes for floating point data types (setting “Ignore leading Zero for Real Numbers” now available under the “Advanced Formatting” tab in the protocol Sequence Builder.
  • Resolved known Wonderware SuiteLink interface connectivity issue present in certain situations where the SuiteLink client connection is reinitialized.

V3.0 Build 115 - March 2017

  • Resolved known issues with Topic creation introduced with V3.0 initial release.
  • Support added for Host Message import/export via CSV.

V3.0 Build 112 - October 2016

  • NEW Support/Maintenance Period Intelligence - OmniServer V3.0 now detects support/maintenance coverage - future upgrades will no longer require re-registrations for users covered by active maintenance/support agreements.
  • NEW Configuration Wizard - OmniServer adds a user-friendly configuration wizard that walks you through the process of configuring a topic and associating new/existing protocols and devices to get started communicating more efficiently.
  • Updated Configuration Interface with Tree View - The main configuration side bar has been updated to display an integrated tree view of all configuration views including Topics, Devices, Protocols, Clients and Diagnostic Tools.
  • Updated Topic and Device Configuration experience - From the new expanded tree view, select your topic or device and edit the properties directly in the main panel.
  • New Client Count Poll Statistics item - new topic-level poll statistics item provides a count of how many clients are actively connected to each topic in OmniServer.  Count is also visible in the Poll Statistics diagnostics view in OmniServer.
  • Updates to Computer ID Generation - Computer ID mechanism for licensing OmniServer has been enhanced to prevent unexpected license invalidation.
  • Resolved issues with I/O monitor capture and display inconsistencies.
  • Stop Poller and Start Poller menu sub-options from File menu have been returned - previously these settings were removed in V2.10 Build 1 for OPC UA certification testing.

V2.10 Build 7 - August 2016

  • Resolved issue with inbound/unsolicited TCP socket behavior - received data was not being successfully processed if the device closed the connection immediately after sending the data.

V2.10 Build 6 - March 2016

  • Support for Windows 10 and Server 2012 R2 operating systems.
  • New DATALOGIC Sample Protocol! - Provides default unsolicited communications with Datalogic barcode scanner configured for barcode followed by carriage return.
  • Updated default configuration views for enhanced usability - The default view for each configuration window is now “Details” view, which provides better readability of device, topic and protocol naming, as well as, visibility into certain setting information without having to open the component (such as communications parameters).
    • NOTE: To change the View to another option, these are still fully configurable via the View menu in the OmniServer configuration.

V2.10 Build 5 - January 2016

  • Updated to the latest OpenSSL libraries for use with OPC UA Server interface, which pro-actively addresses vulnerabilities published by the OpenSSL team on December 3, 2015.

V2.10 Build 4 - November 2015

  • Addresses VC2010 dependency installation issue introduced in 2.10.0.3.

V2.10 Build 3 - October 2015

  • Security update for OpenSSL library V1.0.1p (used by the OmniServer OPC UA Server interface) - only applicable when using the OmniServer OPC UA Server interface for OPC UA client applications.
  • Updated Topics List import/export via CSV - Topic Variable values associated with a topic are now detected and retained in the CSV file.
    • Important - Only the actual values for Topic Variables defined in the Topic can be edited via CSV import/export of the Topics list.
    • The actual Topic Variables (including the name and description) are defined in the OmniServer protocol that is associated with a Topic.  As such, it is not possible to add/remove Topic Variables using the import/export for the Topics list.
    • Import/export of actual Topic Variables is possible within the specific protocol itself.

V2.10 Build 1 - July 2015

This revision addresses the following discovered non-breaking issues required for OPC UA certification testing:

  • Stop Poller and Start Poller menu sub-options from File menu have been temporarily removed until a subsequent minor release.
  • Behavior has been updated to correctly issue an error message to an OPC UA client application when a write operation has been performed for a device that is currently disconnected.
  • Support added for reading up to 65,535 tags in a single OPC UA read.

V2.10 Build 000 - June 2015

  • OmniServer Logger is now configurable for logging event data to static log file, including support for spanning to new log files based on number of events or duration.  Also supports easily deleting old log files based on a specified date range. (Click for Configuration Instructions) 
  • I/O Monitor enhanced to keep sent and received packets displayed on their own separate lines for ease of viewing.
  • I/O Monitor snapshot menu option enhanced to allow specifying a Save As location and file name for the .html output file from the I/O Monitor.
  • Various updates to OPC UA server interface for OPC Foundation lab certification testing.
  • Resolved known issue preventing OmniServer Version 1.x protocol files from importing - Version 1.x legacy protocol files now imported with no issues.

V2.9 Build 017 - April 2015

  • Updated with the latest release of OpenSSL library for security update.

V2.9 Build 016 - March 2015

  • Updated help file with better context sensitivity and ease-of-use.
  • Help file from the Build sequencer dialog box always points to main help page of  build sequencer irrespective of any tab selected.  This has been fixed to point to the corresponding help pages.

V2.9 Build 014 - September 2014

  • Update to the OPC DA server interface resolving incorrect quality behavior for tag writes when the device is unavailable.  OPC DA quality is now adjusted appropriately when a write operation is attempted and the target device is unavailable.

V2.9 Build 013 - September 2014

  • Resolves an issue with Windows Sockets (Winsock) handling for OmniServer Winsock communications - existing socket connection was incorrectly being closed upon a device not responding within the defined Response Timeout period.

V2.9 Build 011 - May 2014

  • New sample protocol for Mettler Toledo scales supporting communications (serial or Ethernet) with the Mettler Toledo SICS protocol
  • Enhancements to OPC UA server interface:
    • Implemented latest version of third-party OPC UA server toolkit.
    • Support for sampling/polling model for updates to an OPC UA Client (previously, only exception-based subscription model was supported)

V2.8 Build 010 - January 2014

  • Support for CSV Import/Export of the following:
    • Topics
    • Devices
    • Protocol - Items List
    • Protocol - Register Number List
    • Protocol - Topic Variables List
  • Support for Importing .DPD Protocol files from the OmniServer Configuration Window.
  • Support for Importing Existing .CFG Configuration Files from the OmniServer Configuration Window.
  • Support for stopping/starting OmniServer Poller from the OmniServer Configuration Window.
  • New Diagnostics Menu - Makes it easier to find the menu options for OmniServer Diagnostic functions.
  • Usability Changes:
    • Renamed “Host Messages List” to “Command/Request Message List” (More accurately explains what the list contains)
    • Added descriptive text under the following Protocol dialog sections:
      • Command/Request (Host) Message - Request section
      • Command/Request (Host) Message - Response section
      • Unsolicited Message - Received section
      • Unsolicited Message - Response section

V2.7 Build 022 - December 2011

  • Corrected a rare licensing glitch that prevented OmniServer from being licensed

V2.7 Build 020 - November 2010

  • Corrected an issue with password protected protocols being used by multiple topics.  Issue prevented protocol access by additional topics using the same password protected protocol.

V2.7 Build 019 - September 2010

  • Added OPC UA Server support.
  • Added ability to collapse topics in the Item Values window view.
  • Corrected bug with Event Logger not displaying TCP Winsock errors properly.
  • Known Issue - Test Device "RANDOM" can currently only be used by a single topic.

V2.6 Build 008 - September 2008

  • Corrected printing bug in Logger and Snapshot file.

V2.6 Build 007 - July 2008

  • Added option for disabling the service's dependence on NetDDE service.
  • Fixed bug where multiple UDP devices set up on the same port were ignoring data.
  • Added box in the logger options for setting the size (in kB) of the logger text capacity.
    The new limit is from 64kb to 999kb (default 64kb).
  • Added option to use fixed width font in the protocol editor window. (Default is now
    fixed width)
  • Increased the object limit from 512 to 2048.
  • Added "Keep Alive" option for TCP devices.
  • Added option to change the background color behind the address column in the IO Monitor
    window. (Default is gray)
  • Updated splash and about box to latest SWTB logo.
  • Set the default message length to 32768.
  • Enabled the email client wedge module.
  • Added device and/or topic information to the end of IO event log entries.
  • Added header information of the object being monitored to the html snapshot file.
  • Implemented improved licensing scheme.
  • Changes to improve OPC compliance: Now sends an OnDataChange for all items after
    a re-advise, after SetEnable(true), after Group.SetState(Active == TRUE), and after
    an item changes it's data type during SetDataTypes.
  • Added ability to set up a "Message Count" item. This works just like a Notification
    Item but instead of setting a flag when the message occurs, the value will increment.
  • New OPC Client testing program - OmniServer Test Client. Replaces the OPC Test Client
    found in Version 2.5. If you are upgrading from Version 2.5, this will be added to
    your server's installation in addition to the older test client.

V2.5 Build 003 - December 2005

  • (All Editions) Fixed memory leak when using protocols with unsolicited messages.
  • (Professional) Added Database Wedge support for MySQL database server. The Wedge
    should now work with most any ODBC SQL database server.

V2.5 Build 001 - July 2005

  • Cleared OPCDA 2.x Interoperability Testing.
  • Passed OPCDA 2.05 Compliance Test.
  • GPIB support removed.
  • OPC ProgID changed to  . Please note: If you install this program on a computer that had OmniServer V2 installed, the older ProgID, DSSI.OmniServer.2, will still work with your client. If OmniServer V2 was not installed, then DSSI.OmniServer.2 will not work, and you will need to change your client application to reflect the new ProgID.
  • Dropped support for Windows 95 & 98.
  • Added support for Windows 2003 Server and XP SP2.
  • Rebranded the server.
  • Memory leak when using Unsolicited Messages fixed.
  • New Product Structure. The older product is now split into three Editions:
    • OmniWedge - Uses the Keyboard wedge to communicate to Windows programs via keystrokes.
    • OmniServer Server Edition - Traditional OPC/DDE/Suitelink communication.
    • OmniServer Professional Edition - The Server Edition plus the WedgeSuite. The suite
      currently contains a Database, Keyboard, and File wedge.
  • New OPC Client testing program - the Browse Demo.
  • New unlock/registration code required for upgrades from 1.x and 2.0 to 2.5.