Reason for 4/12/00 release:
* New release.

Reason for 6/16/00 release:
* Corrected a problem with writing digitals to 4xxxx/bit outputs (analog datablocks). If the driver wrote values to any word other than the first one, other digitals in the word were also changed.

Reason for 7/5/00 release:
* Corrected a problem with registering the MB1 Server on a non-English NT system.

Reason for 7.13 release on 7/20/00:
* Added Force Group Writes as an option to the Output Mode field. Force Group Writes instructs the driver to use only the multiple register function codes, even if writing a single value.

Reason for 7.13a release on 11/10/00:
* Corrected a problem with digital data (ox Coil Status and 1x Input Status). The data was not being sent to the Master correctly, when the server was configured for Slave mode.

Reason for 7.13b release on 12/18/00:
* Corrected a problem with returning Float data correctly from the MB1 driver when it is running in Slave mode.

Reason for 7.13c release on 2/21/01:
* Corrected a problem with not receiving all channel, device, and datablock error codes.

Reason for 7.13d release on 3/8/01:
* Corrected a problem with responding to a Slave request from a Coil or an Input Status. The driver was adding an extra byte to the response when the message was an odd number of bytes.

Reason for 7.13e release on 3/21/01:
* Corrected a problem writing to control address such as !MODE, !SEND, and !POLL from a picture.

Reason for 7.13f release on 04/04/01:
* Corrected a problem with selecting the ModiconLong hardware option in Database Manager.

Reason for 7.13g release on 6/7/01:
* Corrected a problem with writing text to process database while in Slave mode.

Reason for 7.13h release on 7/12/01:
* Added support for Rainbow SuperPro hardware keys to the driver.

Reason for 7.13i release on 7/12/01:
* The previous version contained old release notes. This version corrects the problem.

Reason for 7.13j release on 7/31/01:
* Writes to extended memory are now based on the number of registers used.
* Digital writes are now multiplied by 2 when in slave mode.

Reason for 7.13k release on 8/1/01:
* The icon for the release notes was not appearing in the FIX or iFIX program group. The driver's installation program was changed so that the release notes icon appears.

Reason for 7.13l release on 9/6/01:
* Changed Memory.DLL to correct general cleanup issues in the driver.
* Changed Serial.DLL to address high CPU usage.
* Disabled the duplicate name check when loading a driver configuration. In a large configuration, this check delayed the loading of the file. This check is still made when importing a CSV file.

Reason for 7.13m release on 9/17/01:
* Selecting the TrueFloat data type was increasing the length of the datablock incorrectly. Changed the driver so that the length of the datablock is correct when the TrueFloat data type is used.

Reason for 7.13n release on 4/23/02:
* Corrected a problem with the TrueFloat data type when the Server is configured for ASCII and Single Write mode. Apparently, the Server was sending only two bytes of data instead of four bytes.

Reason for 7.14 release on 5/3/02:
* Added support for Windows XP.

Reason for 7.14a release on 5/8/02:
* Revised documentation to reflect Windows XP-specific configurations.

Reason for 7.14b release on 6/7/02:
* Corrected a problem with communication failures and Server Busy errors when a modem disconnects or you disable a channel.

Reason for 7.14c release on 7/23/02:
* Corrected a problem with memory leaks during asynchronous OPC communication.
* Corrected a problem with resetting the parity and stop bit settings when importing a CSV file.

Reason for 7.15 release on 10/17/02:
* Added support for new Aladdin hardware key.* Implemented new security feature that allows users to configure the logon account for the driver when running as a service.

Reason for 7.15a release on 11/22/02:
* Corrected problem where server failed to receive messages containing characters after the carriage return/line feed (CR/LF) when using the ASCII protocol.

Reason for 7.16 release on 1/13/03:
* Added support for broadcast messages.
* Added support for subsecond processing for both primary and secondary poll times.

Reason for 7.16a release on 1/23/03:
* Corrected problem where Datascope would display the received message twice, sometimes overlapping the messages in the display.

Reason for 7.16b release on 02/11/2003:
* Modified documentation to comply with GE standards.

Reason for 7.16c release on 07/21/2003:
* Added functionality to allow configuration of a delay between multiple Broadcast write messages. A delay in milliseconds can now be configured through the RTS Turnaround field on the Radio/Telephone dialog.

Reason for 7.16e (includes 7.16d modifications) release on 12/12/2003:
* Validated Server running under Windows Server 2003.
* Validated Server running with Cimplicity PE v6.1.

Reason for 7.16f release on 10/15/2004:
* Corrected issue where the driver would stop polling after 49 days.
* Corrected issue where the Power Tool was unable to find the help file if installed to a directory other than dynamics.
* Updated documentation for specific handling of start and end addresses concerning unsolicited messaging on a slave channel. Please note that the these datablock addresses must match the master datablock addresses.

Reason for 7.16g release on 5/23/2005:
* Polling of one or more datablocks results in quick timeouts after a period of about 49.7 days.

Reason for 7.16h release on 11/17/2005:
* PowerTool allows entry of non-6x Analog DataBlock lengths greater than 125.
* PowerTool allows entry of 6x Analog DataBlock lengths greater than 124.
* Autocreate creates 6x Analog Datablocks with lengths greater than 124.
* The Server was not considering the file number when validating 6x addresses.
* Autocreate not working for digital addresses.

Reason for 7.16i release on 12/30/2005:
* Updated code to address potential corrupt timestamp while using driver in simulation mode.
* Updated code to address potential crash upon exit, or by creating a new configuration.
* Updated remote server connection to display a large network in it's entirety.
* Updated remote server connection so that the user must enter data for the remote machine name..

Reason for 7.16j release on 11/06/2006:
* Corrected issues when using Hardware Option types Long64 and Float64.

Reason for 7.16k release on 07/11/2008:
* Corrected issues that caused retries to occur after writing to a TrueFloat item.

Reason for 7.16m Service Pack release on 08/21/2009:  [note: this Service Pack contains SIMs 7.16L and 7.16m combined with all previous SIMs]
* Corrected issue reading/writing COIL (0x) addresses from iFIX Workspace.  Server was rejecting OPC address to 0x memory when entered in DataLink in Workspace ... error : Invalid Item ID.
* Proactively reviewed code to identify and correct any areas of concern that might have the potential to cause issues in the field as a result of the driver and database getting "out-of-sync".

Reason for 7.16o Service Pack release on 11/09/2009: 
* Corrected issue reading A_IOAD field through EDA. ex: Alarm OCX in Workspace sometimes showed incorrect I/O address.