Reason for 7.16 Release on 3/14/2002:
* New driver.

Reason for 7.16a Release on 3/29/2002:
* LVZ, LZ12, LZ15, SQR, SQ12, SQ15, REG, 15RN, and 12CL signal conditioning were not accepted by Database Manager.

Reason for 7.16b Release on 4/9/2002:
* Corrected a problem with IP address persistance. The address being entered was changing to a random address on non-English versions of Windows when the thousands separator was defined as "." (dot).

Reason for 7.16c Release on 4/30/2002:
* Corrected a problem with exception-based processing. Digital tags were not working when they were configured as exception-based.

Reason for 7.16d Release on 9/10/2002:
* Addressed issue where bit base index for pull-down entries for 1-16 and 15-0 were reversed. Originally, if you selected bit base 1-16 in the Power Tool, address 40001:16 was rejected in the database, but address 40001:0 was accepted. Conversely, if you selected bit base 15-0, address 40001:0 was rejected in the database, but address 40001:16 was accepted.
* Also addressed issue where unsolicited messages were sometimes delivered to not only the devices and datablocks configured for unsolicited messages, but also delivered to devices and datablocks not configured for unsolicited messages.

Reason for 7.17 Release on 10/15/2002:
* 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.
* Corrected problem writing to 6x extended registers.

Reason for 7.17a Release on 1/6/2003:
* Corrected problem accessing discrete registers and individual bits in 3x and 4x registers using OPC datalinks from within the WorkSpace..

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

Reason for 7.17c Release on 04/22/2003:
* Corrected issues with remote database access. I/O addresses disappearing when adding or duplicating blocks. Data sometimes displayed ??'s

Reason for 7.17d Release on 07/16/2003:
* In some cases, server was unable to connect to devices on different subnets.
* Overruns occurring after performing writes (more prevalant when polling at high rate).
* Various documentation changes.

Reason for 7.17e Release on 10/06/2003:
* Correct issues entering decimal polling times on non-English systems ... decimal portion was disappearing.

Reason for 7.17g (includes 7.17f modifications) release on 12/05/2003:
* Validated Server running under Windows Server 2003.
* Validated Server running with Cimplicity PE v6.1

Reason for 7.17h release on 04/20/2004:
* Corrected issue with 0x digital writes in simulation mode.

Reason for 7.17i release on 02/03/2005:
* MBEdrv.exe sometimes stayed in memory after shutdown.
* The first execution of a special command (e.g. !Send) sometimes failed with an "I/O General Failure" error message. After the first execution, it worked as expected.

Reason for 7.17j release on 4/8/2005:
* Corrected issue where MBEDrv.exe would not properly exit from memory on hyper-threaded, or dual processor systems.

Reason for 7.17k release on 12/29/2005:
* Corrected issue for potential crashes upon exiting the driver.
* Modified the remote serve connection so that it will not accept a blank input.
* Corrected issue where the entirety of a very large network will be listed when trying to connect to a remote server.

Reason for 7.17L release on 10/24/2006:
* Corrected issues with signed integer values when reading and writing this driver through an OPC client. Negative values were not being handled correctly.

Reason for 7.40 Service Pack release on 10/01/2007:
* MBE now validated for use with Microsoft Vista OS.
 

Reason for 7.41 release on 08/13/2008:
* The MBE server now supports 15 digits of precision with analog data.

If you are using this MBE server in iFIX 4.5, 15-digit precision is supported for data values only, and not for signal conditioning. Therefore, in iFIX 4.5, signal conditioning calculations are limited to 7 digits of precision. In other words, if the range of your EGU limits exceeds 7 digits, a small amount of imprecision will be introduced into the calculated result for signal conditioning.

If you are using iFIX 5.0 with this MBE server(v7.41), 15-digit precision is supported for both data values and signaling conditioning. Please note: at the time of this Service Release, iFIX 5.0 has not yet been released.

Prior to iFIX 4.5, 15-digit precision was not supported. Instead, you are limited to the 7 digit limits imposed by the use of single precision values.

Reason for 7.42 Service Pack release on 11/24/2008:
* Two new driver data types have been added to the Server. "Signed Long64" - 64-bit signed long integer value. "Float64" - 64-bit IEEE floating point value. These new data types can be selected for use by entering them in the "Data Type" field of the Data Block configuration in the Power Tool.

Reason for 7.42a Service Pack release on 05/21/2009:
* Corrected issue where; if the driver and database configurations got out of sync, it could sometimes result in the database showing ?????'s after a restart or reload.  This issue occured most frequently when using iFIX's Enhanced Failover feature.

Reason for 7.42b Service Pack release on 03/12/2010:
* Re-branded with new company name GE Intelligent Platforms, Inc.  Also validated running under Windows Server 2008.