Agilent VEE 9.31 Readme

Installing Agilent VEE 9.31 on machines with Agilent VEE 9.3

If you already have Agilent VEE 9.3 installed, cancelling the installation of Agilent VEE 9.31 halfway through will delete the previously installed Agilent VEE 9.3. This is because Agilent VEE 9.31 is a full installation package. It can be installed with or without Agilent VEE 9.3 pre-installed on the machines. If Agilent VEE has been removed, re-install the Agilent VEE 9.3 or Agilent VEE 9.31.

Agilent IO Libraries Suite 16.2 supportability

Agilent VEE 9.31 supports Agilent IO Libraries Suite 16.2.

Microsoft Office Excel 2010 supportability

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

Microsoft® Windows® 7 supportability

Agilent VEE 9.31 is a free upgrade of Agilent VEE 9.0/9.2/9.3. 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 repairing/modifying Agilent VEE installation

After repairing/modifying 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.
Perform any of the methods below once.

(a) Modify Windows 7 User Account Control settings

  1. Go to Start | Run, type "secpol.msc" and press Enter.
  2. In the Local Security Policy window, 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 the machine and log in with administrator privileges.
  5. Run the Agilent VEE program or Agilent VEE runtime program again and it will run successfully.
  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.

(b) Modify executable Privilege Level

  1. For Agilent VEE program, go to {Agilent VEE Installed Directory}\vee.exe. For Agilent VEE runtime program, go to {Agilent VEE Runtime Installed Directory}\veerun.exe.
  2. Right click on the executable file (for example, vee.exe or veerun.exe).
  3. On the context menu, go to Properties | Compatibility | Privilege Level. Check Run this program as an administrator.
  4. Run the Agilent VEE program or Agilent VEE runtime program again.
  5. If the User Control Account dialog box appears asking for permission to allow the program to make changes to the machine, click Yes and the program will run successfully.
  6. Repeat steps 1-3 to uncheck Run this program as an administrator.

(c) Using an elevated command prompt

Steps below are illustrated using Agilent VEE 9.2, use appropriate value for Agilent VEE 9.3.

  1. Go to Start | Run, type "cmd".
  2. Look for cmd.exe in the results, right click on it and select Run as administrator.
  3. If the User Control Account dialog box appears asking for permission to allow the program to make changes to the machine, click Yes to continue.
  4. At the command prompt, enter the following command and press Enter.

    For Agilent VEE program,
    {Agilent VEE Installed Directory}\vee.exe (for example, "C:\Program Files (x86)\Agilent\VEE Pro 9.2\vee.exe").

    For Agilent VEE runtime program,
    {Agilent VEE Runtime Installed Directory}\veerun.exe {Agilent VEE runtime program full path} (for example "C:\Program Files (x86)\Agilent\VEE Pro RunTime 9.2\veerun.exe" "C:\Users\User1\Documents\MyProgram.vxe").

  5. The Agilent VEE program or Agilent VEE runtime program will run successfully.

(d) Run the program as an administrator (Only applicable for Agilent VEE Pro)

Steps below are illustrated using Agilent VEE Pro 9.2, use appropriate value for Agilent VEE Pro 9.3.

  1. Go to Start | All Programs | Agilent VEE Pro 9.2.
  2. Right click on VEE Pro 9.2, and select Run as administrator.
  3. If the User Control Account dialog box appears asking for permission to allow the program to make changes to the machine, click Yes to continue.
  4. Run the Agilent VEE program again and it will run successfully.


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.

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.

For additional FAQs, please visit Agilent VEE technical support Web page (http://www.agilent.com/find/vee_faq) and browse to FAQs section.

 

What's been fixed in 9.31

ID

Descriptions

Broken in

Resolution

SAD00436238

Excel library does not allow writing more than 65536 rows with Microsoft Excel 2007 and later.

9.2

Excel library allows writing more than 65536 rows with Microsoft Excel 2007 and later.

SAD00444163

Excel library does not allow writing more than 256 columns with Microsoft Excel 2007 and later.

9.2

Excel library allows writing more than 256 columns with Microsoft Excel 2007 and later.

SAD00423444

Excel SaveAs library object does not allow the use of enumerated value.

9.2

Added Excel Save Workbook (Format No.) library object which supports enumerated value.

SAD00443877

Excel Create Chart library object does not allow specifying second Y axis.

9.0

Added a few Excel Create Chart library objects which specifies secondary Y axis for line chart, XY chart and bar chart respectively.

SAD00409103

Excel SaveAs library object does not allow .xlsx file type.

9.2

Excel SaveAs library object allows .xlsx file type.

SAD00443880

When SendDataSetting's Orientation is set to Horizontal, the object does not support UInt8 and Int32 one dimensional array.

9.2

When SendDataSetting's Orientation is set to Horizontal, the object now supports UInt8 and Int32 one dimensional array.

SAD00443872

Excel SendDataSettings library object generates a few compiler warnings during run.

9.3

Excel SendDataSettings library object does not generate compiler warning during run.

SAD00446908

Device with two Junctions connected to its input pin produces invalid compiler warning if its sequence output pin is connected back to the input pin.

9.3

Such connection will not produce compiler warning now.

SAD00441276

When using Flow > Start button to run program, compiler warnings are accumulated in Output Window.

9.3

When using Flow > Start button to run program, the previous compiler warnings in Output Window will be cleared.

SAD00446251

Output Window will be automatically prompted when there is a new output message. This is annoying.

9.3

Output Window will be automatically prompted only if the message is a compiler warning and Enable Compiler Warning is checked.

SAD00446865

Some programs (for example, mfgtest.vee) in examples folder produce VEE Serious Error dialog during run.

9.3

The program will run successfully.

SAD00447039

Examples manual40.vee and manual41.vee produce invalid error during run. It is caused by control input pin connection.

9.3

The example programs are updated to run without error.

SAD00445781

Some links in MATLAB Help desk help file are broken.

8.5

The broken links in the help file are now fixed.

SAD00442536

MATLAB global variables are not recognized in different MATLAB script objects.

8.5

MATLAB global variables are recognized in different MATLAB script objects.

SAD00419467

Agilent VEE is unable to detect MATLAB 2010b.

8.5

Agilent VEE detects MATLAB 2010b and later. Agilent Help file is updated with details.

SAD00438251

Agilent VEE doesn't support some MATLAB data type i.e. logical. Agilent VEE will prompt runtime error when terminals value is of such data type.

8.5

Agilent VEE supports more MATLAB data types. Agilent VEE Help file is updated with supported MATLAB data types.

SAD00446702

A lot of MATLAB functions’ default terminal names are invalid (for example, with single quote).

8.5

MATLAB functions' default terminal names in Function & Object Browser are updated.

SAD00449447

Active X Control Help content for Microsoft Office application is out of date.

9.2

The content is updated.

SAD00449552

Example program user32.vee is unable to run in Agilent VEE 8.5 and above.

8.5

The example file is updated.

SAD00449777

A few example programs in examples\contrib\win32API cannot run in Windows 7.

9.2

The example programs (for example, kernel32.vee) are updated.

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 2012 Agilent Technologies, Inc.