Why Upgrade to Version 2.6?
Upgrade for as little as $200 and get all upgrades for a year!
Features Added
- Maintenance Contract. Receive future upgrades for free and support for 1 year.
- Increased the object limit from 512 to 2048. You can now double or triple the number of devices or clients simultaneously connected to OmniServer over previous
versions.
- Added "Keep Alive" option for TCP devices. No longer guess if an unsolicited TCP connection has gone down. OmniServer will now set the reserved Status
item to False if TCP connection has failed when you select this option for your Winsock devices.
- New Email Wedge (Professional Version only). This powerful OmniServer Wedge will send email and SMS messages, formatted any way you choose, based upon a
condition of an item. Great for building alarming systems.
- Added ability to set up a "Message Count" item.
This invaluable feature can not only count the number of times a message completes, but can also be used to signal the receipt of an unsolicited message, even if the data in that message never changes. The Message Count item can be displayed and/or worked with in your HMI/SCADA system as needed.
|
Improved Compatibility
- Support for Vista and Windows 2008 Server. Now you can run OmniServer as a service or interactively in these newer operating systems.
- Added option for disabling the service's dependence on NetDDE service.
For the security-minded, setting this option tells OmniServer not to require the use of the operating system's NetDDE service, which for security reasons is disabled on operating systems Windows XP/SP2 and above.
|
Better Diagnostic & Protocol Design Capabilities
- Added box in the logger options for setting the size (in kB) of the logger text capacity.
For those devices with high message byte-counts, you can now capture upwards to 15 times more data in the Logger. Invaluable for diagnosing data interpretation problems.
- Added option to use fixed width font in the protocol editor window. (Default is now fixed width). The protocol editor now uses a Fixed Width font, which aids
in the readability of the protocol message. This will save time in hunting down errant characters in the data string, such as extra spaces.
- Set the default message length to 32768.
Increased from the old default of 250 characters, no longer will you get message rejection errors if your data stream just happens to go over 250 characters. Saves significant troubleshooting time.
- Added device and/or topic information to the end of IO event log entries. Another troubleshooting time saving, this aids in determining which data belongs to
which device or topic.
- Added header information of the object being monitored to the IO Monitor HTML snapshot file.
Invaluable for determining for which device or topic the snapshot was produced.
|
Bug Fixes
- Fixed bug where multiple UDP devices set up on the same port were ignoring data.
- Fixed some minor OPC issues: Now sends an "OnDataChange" for all items after a re-advise, after SetEnable(true), after
Group.SetState(Active == TRUE), and after a change data type during SetDataTypes.
|
|
