Keysight VEE 9.33 Readme
Microsoft Windows® 11 supportability
Keysight VEE 9.33 is a free upgrade of Keysight VEE
9.0/9.2/9.3/9.32. Note that the 64-bit support has a 32-bit application running
on WOW64 (Windows-on-Windows 64-bit) emulator.
To avoid confusion, deprecated Active X controls in Windows 11 and
its relevant example files in Examples\ActiveX folder had been removed. VEE
programs utilizing those controls may still be used. However, users are
required to copy the relevant ActiveX controls from earlier Windows OS to their
respective folders in the new Windows environment manually.
When using Keysight VEE in Windows 11 (64-bit), take note of the
following limitations:
Any
attempt to import or call with VEE Pro 9.33 on the followings are not
supported:
- 64-bit drivers,
libraries (DLL) and components such as IVI-COM 64-bit or VISA-COM 64-bit.
- Interfaces or calls to
64-bit software such as MATLAB 2016a.
- Assemblies compiled with
Microsoft .NET Framework 4.0 and above.
WhichOS is
capped at Windows 8
VEE's WhichOS function will return
"Windows_8_8.1_10".
National Instruments (NI) interface is not officially supported
Keysight VEE 9.2 (and above) no longer provides official NI
supportability. However, you are still able to use the existing NI interfaces.
Keysight IO Libraries Suite 2023 Update 1 supportability
Keysight VEE 9.33 has the ‘missing visa32.dll’ error when used
with Keysight IO Libraries Suite 2023. This issue is resolved when used with
Keysight IO Libraries Suite 2023 Update 1.
Microsoft® Office 365 supportability
Keysight VEE 9.33 (and above) existing built-in Excel menu
supports Microsoft Office Excel 365. Certain calls might result in a dialog
displayed which requires user's interaction. However, not all new features in
Microsoft Office Excel are supported.
When using Microsoft Office Access 2013, if you receive the "Microsoft.ACE.OLEDB 12.0 provider is not registered on the
local machine" error message, install Microsoft Access Database Engine
2007 Redistributable or Microsoft Access Database Engine 2010 Redistributable.
Other Limitations
When using Keysight VEE in Windows 11 with WOW64 emulator, please
be informed of the following limitations:
1. Error running Keysight VEE program or Keysight VEE runtime
program containing MATLAB scripts
If you are running Keysight VEE program (.vee) or Keysight VEE
runtime program (.vxe) containing MATLAB scripts for
the first time, the error dialog "Matlab engine
could not be started" or "VEE can't find a MATLAB Engine to run
MATLAB script ..." may be prompted.
2. Error System.UnauthorizedAccessException
when launch Keysight VEE
Sometimes Keysight VEE may display the "System.UnauthorizedAccessException:
Access to the path {Keysight VEE Installed Directory}\PipelineSegments.store
is denied." error message.
For
limitations 1 and 2, perform any of the methods below once.
(a) Modify Windows User Account Control settings
- For Windows 7, go to Start
| Run. For Windows 8,
Windows 10 and Windows 11, go to Start, right click on it and
select Run.
- Type "secpol.msc" and press Enter or OK.
- In the Local Security
Policy window, navigate to Local Policies | Security
options.
- Set the value of User
Account Control: Run all administrators in Admin Approval Mode to Disabled.
- Restart the machine and
log in with administrator privileges.
- Run the Keysight VEE
program or Keysight VEE runtime program again and it will run
successfully.
- Repeat steps 1-4 with
the value of User Account Control: Run all
administrators in Admin Approval Mode set to Enabled.
- If step 7 is not
performed, Standard User may not be able to launch Keysight VEE.
(b) Modify executable Privilege Level
- For Keysight VEE
program, go to {Keysight VEE Installed Directory}\vee.exe. For Keysight VEE runtime program, go to {Keysight
VEE Runtime Installed Directory}\veerun.exe.
- Right click on the
executable file (for example, vee.exe or veerun.exe).
- On the context menu, go
to Properties | Compatibility | Privilege
Level.
Check Run this program as an administrator.
- Run the Keysight VEE
program or Keysight VEE runtime program again.
- 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.
- Repeat steps 1-3 to
uncheck Run this program as an administrator.
(c) Using an elevated command prompt
Steps below are illustrated using Keysight VEE 9.3, use
appropriate value for Keysight VEE 9.2.
- For Windows 7, go to Start
| Run,
type "cmd". Look for cmd.exe in the
results, right click on it and select Run as
administrator.
For Windows 8, go to Start, right click on it
and select Command Prompt (Admin). For Windows 10 and 11, go to Start,
right click on it and select Terminal (Admin).
- 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.
- At the command prompt,
enter the following command and press Enter.
For Keysight VEE program,
{Keysight VEE Installed Directory}\vee.exe (for
example, "C:\Program Files (x86)\Keysight\VEE Pro 9.3\vee.exe").
For Keysight VEE runtime program,
{Keysight VEE Runtime Installed Directory}\veerun.exe
{Keysight VEE runtime program full path} (for example "C:\Program
Files (x86)\Keysight\VEE Pro RunTime 9.3\veerun.exe"
"C:\Users\User1\Documents\MyProgram.vxe").
- The Keysight VEE program
or Keysight VEE runtime program will run successfully.
(d) Run the program as an administrator (Only applicable for
Keysight VEE Pro)
Steps below are illustrated using Keysight VEE Pro 9.3, use
appropriate value for Keysight VEE Pro 9.2.
- For Windows 7, go to Start
| All Programs | Keysight VEE Pro 9.3. For Windows 8, go to Start screen, look for VEE
Pro 9.3.
For Windows 10, go to Start, look for Keysight
VEE Pro 9.3
in program list. For Windows 11, go to Start, type in ‘VEE Pro 9.3’ in the search
bar to locate the file.
- For Windows 7 and
Windows 8, right-click on VEE Pro 9.3 and select Run
as administrator.
For Windows 10 and Windows 11, right-click on VEE Pro 9.3, go to More and select Run as administrator. - 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.
- Run the Keysight VEE
program again and it will run successfully.
3. Use an Administrator role to enter product key
If you have not entered Keysight VEE product key during
installation, please follow these steps to update the product key:
Steps below are illustrated using Keysight VEE Pro 9.3, use
appropriate value for Keysight VEE Pro 9.2.
- For Windows 7, go to Start
| All Programs | Keysight VEE Pro 9.3. For Windows 8, go to Start screen, look for VEE
Pro 9.3.
For Windows 10, go to Start, look for Keysight
VEE Pro 9.3
in program list. For Windows 11, go to Start, type in ‘VEE Pro 9.3’ in the
search bar to locate the file.
- For Windows 7 and
Windows 8, right-click on VEE Pro 9.3 and select Run
as administrator.
For Windows 10 and Windows 11, right-click on VEE Pro 9.3, go to More and select Run as administrator. If not Run as administrator, the product key might not be visible to other users. - 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.
- If evaluation period has
expired, proceed to step 5. After Keysight VEE is launched, go to Help | Product
Key.
- Enter the product key at
the prompted dialog box.
When using Keysight VEE in Windows 11, take note of the
following limitations:
1. Configure IVI Driver Sessions
If you are using IVI-COM driver, the Configure IVI Driver Sessions
feature which uses Keysight Instrument Explorer is currently unavailable.
2. Program Compatibility Assistant prompted after
repairing/modifying Keysight VEE installation
After repairing/modifying Keysight VEE installation from Control
Panel, Program Compatibility Assistant may be prompted. Click Cancel or select This
program installed correctly to close the dialog.
For
additional FAQs, please visit Keysight VEE technical support Web page (http://www.keysight.com/find/vee_faq)
and browse to FAQs section.
What's been fixed in 9.33
|
ID |
Descriptions |
Broken in |
Resolution |
|
526020 |
Importing a VEE library
changes the “internal” scope of a private function within the “imported”
library. |
9.0 |
The scope is correct
now. |
|
526025 |
VEE program causes
multiple library entries to appear within the “Program Explorer” panel. |
9.0 |
The entries are
corrected. |
|
- |
Updated Keysight
Software End-User License Agreements. |
- |
- |
What's been fixed in 9.32
|
ID |
Descriptions |
Broken in |
Resolution |
|
SAD00450486 |
Concatenator and
collector produced incorrect mapping value sometimes. |
8.0 |
The mapping values are
correct now. |
|
SAD00454118 |
There is memory leak
when using built-in-function asInt32, asReal32, asReal64, asUInt8, asUInt16
with input parameter data type is text. |
9.0 |
There will be no memory
leak for the scenarios mentioned. |
|
SAD00454192 |
There is memory leak
when an object's Error output pin is added, and Output Terminal value is
un-assigned or there is invalid variable name. |
8.0 |
There is no memory leak
for the scenarios mentioned. |
|
SAD00453925 |
Keysight VEE 9.31 Readme
file resolution text for SAD00419467 mentioned unsupported MATLAB version. |
9.0 |
The resolution text is
updated with supported MATLAB versions. |
|
SAD00410706 |
Instrument Manager is
unable to find connected instruments when NI-VISA is installed as primary
VISA. |
9.0 |
There is no code change.
Instrument Manager is able to find connected
instruments using NI-VISA 5.1.2. |
|
SAD00451070 |
Direct I/O gives error
for EXECUTE commands when NI-VISA is installed as primary VISA and NI
GPIB-USB-HS is used. |
7.0 |
The commands execute
successfully now. |
|
SAD00453794 |
The checking on the
accepted maximum value of fractional digit of Real's Fixed number format is
not consistent at Default Preferences and Number Format dialog. |
9.0 |
The checking is
consistent now. |
|
SAD00454299 |
Extensible VEE Objects
in imported User Functions are editable. |
9.3 |
Extensible VEE Objects
in imported User Functions are view only. |
|
SAD00454584 |
Default Preferences >
Environment > Number > Trig Mode value has no effect on some Trig
built-in functions (i.e. tan/cos/sin/cot). The
functions always use Radians mode for calculation. |
8.0 |
The Trig Mode will be
used in the Trig built-in functions calculations. |
|
SAD00449931 |
MATLAB noanimate parameter name does not match with the input
terminal name. |
9.31 |
The parameter name
matches input terminal name now. |
|
SAD00454293 |
Send error report dialog
instructions are outdated. |
9.2 |
The send error report
dialog is updated with the latest instructions. |
|
SAD00407513 |
On Windows 7, no error
dialog is prompted when the value for Declare Variable's Name field is
invalid. |
9.2 |
On Windows 7, error
dialog will be prompted when the value is invalid. |
|
SAD00408721 |
On Windows 7, no error
dialog is prompted when the value for Sequencer's Test field is invalid. |
9.2 |
On Windows 7, error
dialog will be prompted when the value is invalid. |
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 |
Keysight VEE is unable
to detect MATLAB 2010b. |
8.5 |
Keysight VEE detects
MATLAB 2010b and MATLAB 2011a. Keysight Help file is updated with details. |
|
SAD00438251 |
Keysight VEE doesn't
support some MATLAB data type i.e. logical. Keysight
VEE will prompt runtime error when terminals value is of such data type. |
8.5 |
Keysight VEE supports
more MATLAB data types. Keysight 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 Keysight 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 |
Keysight VEE may take
some time to execute a program when most of the Keysight VEE object sequence
pins are connected. |
8.5 |
Keysight VEE will
execute a program more efficiently now. |
|
SAD00430425 |
Some Keysight VEE
objects are not executed when If/Then/Else branches consist of connected Gate
and Junction. |
4.0 |
The Keysight 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 Keysight VEE to shut down. |
8.5 |
Keysight VEE will run
with the non-numeric user config file folder name. |
|
SAD00414315 |
IO Config icon is used
in Windows 7 taskbar when running Keysight VEE runtime program or Runtime
Default Preferences Configuration. |
9.2 |
Correct Keysight 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 |
Keysight VEE sometimes
communicates with the wrong instrument when using dynamic visa address. |
9.01 |
Keysight 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.
Descriptions
in this document are subject to change without notice. Always refer to Keysight
web site for latest revision.
Last
updated: October 2023.
© Copyright 2018-2023
Keysight Technologies, Inc.