4. Why Introduce IVI in TestExec SL?
Venturi 2 Venturi S3
GPIB instruments / VXI cards LXI instruments / PXI cards
SCPI commands SCPI commands / IVI drivers
Supported by action “msginstXXX” No SCPI commands for PXI cards
TestExec SL Training
Sequences, Multithreading & IVI-COM
4
5. Setting the System.ust File
Launch TestExec SL 7.1.2
system.ust
hwhIVI.dll
Path: C:Program Files (x86)AgilentTestExec SL 7.1Bin
Auto generated and will be saved
to IviConfigurationStore.xml
Software Modules are read from
IviConfigurationStore.xml
1
2
3
4
5
6
7
TestExec SL Training
Sequences, Multithreading & IVI-COM
5
6. Creating IVI-COM Action
1
2
3
4
5
6
hwhIVI.dll
7
8
TestExec SL Training
Sequences, Multithreading & IVI-COM
6
Notice that there is no parameter for
instrument. The instrument parameter is
located at lifetime tab with parameter
name “Instance Reference”.
7. IVI Class Driver vs IVI Specific Driver
IVI
Class
Driver
IVI
Specific
Driver
TestExec SL Training
Sequences, Multithreading & IVI-COM
7
MyDMMVoltMeasMyDMMVoltMeas
M918x Child Assembly
specific to PXI DMM
DMM Child Assembly
generic to all DMM
DMM Class name
generic to all DMM
M918x Class Name
specific to PXI DMM
and only for DC Voltage
measurement
11. IVI Migration Editor
Migrates logical names, driver sessions and hardware assets
Only migrates IVI Data which uses IVI-COM driver and that driver must exists in
the destination file
Located in C:Program Files (x86)AgilentTestExec SL 7.1Bintxslivimigrated.exe
TestExec SL Training
Sequences, Multithreading & IVI-COM
11
13. Limitation
Switching modules with IVI-COM
is not fully integrated
Cannot be used with IVI-COM
with more than 2 classes (eg
Agilent E3631A power supply)
TestExec SL Training
Sequences, Multithreading & IVI-COM
13