Agilent VEE 9.3 Readme

Agilent IO Libraries Suite 16.1 supportability

Agilent VEE 9.3 supports Agilent IO Libraries Suite 16.1.

Microsoft Office Excel 2010 supportability

Agilent VEE 9.2 (and above) existing built-in Excel menu supports Microsoft Office Excel 2010. However, new features in Microsoft Office Excel 2010 are not supported.

Microsoft® Windows® 7 supportability

Agilent VEE 9.3 is a free upgrade of Agilent VEE 9.0. Agilent VEE 9.2 (and above) supports Windows 7 (Professional, Ultimate, and Enterprise with 32-bit and 64-bit supportability). Note that the 64-bit support has a 32-bit application running on WOW64 (Windows-on-Windows 64-bit) emulator.

When using Agilent VEE 9.2 (and above) in Windows 7 (both 32-bit and 64-bit), please be informed of the following limitation:

1. Configure IVI Driver Sessions

If you are using IVI-COM driver, the Configure IVI Driver Sessions feature which uses Agilent Instrument Explorer is currently unavailable.

2. Program Compatibility Assistant prompted after repair/modify Agilent VEE installation

After repair/modify Agilent VEE installation from Control Panel, Program Compatibility Assistant may be prompted. Click Cancel or select This program installed correctly to close the dialog.


When using Agilent VEE 9.2 (and above) in Windows 7 64-bit using WOW64 emulator, please be informed of the following limitations:

1. Error running Agilent VEE program or Agilent VEE runtime program containing MATLAB scripts

If you are running Agilent VEE program (.vee) or Agilent VEE runtime program (.vxe) containing MATLAB scripts for the first time, the error dialog "Matlab engine could not be started" may be prompted. Steps to fix this:

  1. Go to Start | Run and type 'secpol.msc'.
  2. In the prompted dialog, navigate to Local Policies | Security options.
  3. Set the value of User Account Control: Run all administrators in Admin Approval Mode to Disabled.
  4. Restart system and login with administrator privileges.
  5. Run the Agilent VEE program or Agilent VEE runtime program again and it should work fine.
  6. Repeat steps 1-4 with the value of User Account Control: Run all administrators in Admin Approval Mode set to Enabled.
  7. If step 6 is not performed, Standard User may not be able to launch Agilent VEE.

2. Use an Administrator role to enter product key

If you have not entered Agilent VEE product key during installation, please follow these steps to update the product key:

  1. Go to Start | All Programs and navigate to Agilent VEE 9.2 (or above).
  2. Right-click on VEE Pro 9.2 (or above).
  3. On the context menu, select Run as administrator (If not Run as administrator, the product key might not be visible to other users).
  4. If evaluation period has expired, proceed to step 5. After Agilent VEE is launched, go to Help | Product Key.
  5. Enter the product key at the prompted dialog box.

3. Declare global variable name

If an invalid name is used when declaring a global variable name, it will revert back to the old name without any error dialog.

4. Sequencer object Transaction

When adding Sequence Transaction, please use supported naming convention for Test/Exec name. If a Sequence Transaction cannot be edited due to invalid variable name, please delete that Sequence Transaction (select the incorrect transaction, right click and select Delete Trans) and replace with a new sequencer transaction.

5. MATLAB is not detected

Agilent VEE is unable to detect MATLAB installed on Windows 7 64-bit systems and will automatically use the built-in MATLAB Script Engine.

National Instruments (NI) interface is not officially supported

Agilent VEE 9.2 (and above) no longer provides official NI supportability. However, you are still able to use the existing NI interfaces.

For answers to installation related questions, review the file InstallReadme.htm in the Autorun directory of your Agilent VEE CD.

 

What's been fixed in 9.3

ID

Descriptions

Broken in

Resolution

SAD00408468

Agilent VEE may take some time to execute a program when most of the Agilent VEE object sequence pins are connected.

8.5

Agilent VEE will execute a program more efficiently now.

SAD00430425

Some Agilent VEE objects are not executed when If/Then/Else branches consist of connected Gate and Junction.

4.0

The Agilent VEE will execute successfully now.

SAD00432754

After a dynamic terminal changes, the Extensible VEE Object (EVO) error output pin disappears if it is not connected to any other VEE object.

9.21

The EVO error output pin is retained after a dynamic terminal changes.

SAD00439046

Database library FillDataSet User Function throw OutOfMemory exception if executed for a long time.

9.0

The Database library FillDataSet User Function will not throw OutOfMemory exception.

SAD00438905

Add vdcCreateWordScalar, vdcSetWordScalar, vdcGetWordScalarValue, and vdcGetWord1DArray APIs to libvapi.dll.

9.0

The APIs are added to the libvapi.dll.

What's been fixed in 9.22

ID

Descriptions

Broken in

Resolution

SAD00436003

Timer output value is without decimal fraction. For example, the output value is displayed as 1, instead of 1.105.

9.21

Timer output value is corrected with decimal fraction.

What's been fixed in 9.21

ID

Descriptions

Broken in

Resolution

SAD00415457

Registry information is not completely removed after patch uninstallation.

9.01

Registry information is fully removed after patch uninstallation.

SAD00416001

User config file folder name is non-numeric and causes Agilent VEE to shut down.

8.5

Agilent VEE will run with the non-numeric user config file folder name.

SAD00414315

IO Config icon is used in Windows 7 taskbar when running Agilent VEE runtime program or Runtime Default Preferences Configuration.

9.2

Correct Agilent VEE runtime icon is used.

SAD00414043

MATLAB plotedit function is not running.

8.5

MATLAB plotedit function has been removed from FOB.

SAD00422704

Timer output value is negative on some PC.

8.0

Timer output value is correct.

What's been fixed in 9.2

ID

Descriptions

Broken in

Resolution

SAD00403891

Agilent VEE sometimes communicates with the wrong instrument when using dynamic visa address.

9.01

Agilent VEE will communicate with the correct instrument now.

SAD00389124

Conflicts between UserFunction and built-in function when both functions have the same name.

9.0

Duplicated name is allowed. UserFunction will be called.

Microsoft and Windows are U.S. registered trademarks of Microsoft Corporation.

© Copyright 2011 Agilent Technologies, Inc.