Driver Examples and Source Code |
For the IVI-C driver:
Example programs (C++ and MATLAB) are associated with the IVI-C driver, and can be found in the folders:
<Program Files>\IVI Foundation\IVI\Drivers\KtMTrig
<Program Files (x86)>\IVI Foundation\IVI\Drivers\KtMTrig
Example programs for LabVIEW call into the IVI-C driver. If you have LabVIEW installed on the computer when the KtMTrig drivers are installed, the LabVIEW driver and its examples will be placed into all LabVIEW versions found on the destination computer. The LabVIEW driver and its help file are also placed into the folders:
<Program Files (x86)>\Keysight\MTrig\LabVIEW Driver
<Program Files (x86)>\Keysight\MTrig\LabVIEW Driver Help
The IVI-C driver source code, if optionally installed, can be found in the folders:
<Program Files>\IVI Foundation\IVI\Drivers\KtMTrig
<Program Files (x86)>\IVI Foundation\IVI\Drivers\KtMTrig
The source code is a Visual Studio 2013 C++ project and may be updated to newer versions of Visual Studio. To use the rebuilt driver, the driver dll in the build output directory must be registered using the regsvr32.exe utility or by setting the VS project C++ Linker settings to do so. This driver provides the lowest-level API that is a reliable API.
For the IVI.NET driver:
Example programs (C# and VB.NET) are associated with the IVI.NET driver, and can be found in the folders:
<Program Files>\IVI Foundation\IVI\Microsoft.NET\Framework64\v4.0.30319\Keysight.KtMTrig <version>
<Program Files (x86)>\IVI Foundation\IVI\Microsoft.NET\Framework32\v4.0.30319\Keysight.KtMTrig <version>
The IVI.NET driver source code, if optionally installed, can be found in the folder:
<Program Files>\IVI Foundation\IVI\Microsoft.NET\Framework32\v4.0.30319\Keysight.KtMTrig <version>\Source
The source code is a Visual Studio 2013 C# project and may be updated to newer versions of Visual Studio. This driver provides the lowest-level API that is a reliable API.
Connecting to the Chassis |
The driver help topic, “Driver Examples,” documents program examples for Visual Studio (C#, C++, VB), LabVIEW, and MATLAB. Each of these examples illustrates how to connect to an instrument in the respective development environment.
The IVI resources page (https://www.ivifoundation.org/getting-started/) has documents and videos that explain how to get started with an IVI-NET driver in different development environments:
Using IVI with Visual C++
Using IVI with Visual C# and Visual Basic .NET
Using IVI with LabVIEW
Using IVI with LabWindows/CVI
Using IVI with MATLAB
Configuring Instrument Settings |
|
For the IVI-C driver:
The KtMTrig IVI-C driver application programming interface (API) includes functions and attributes for setting instrument state variables, as well as functions for controlling the chassis and reading results from the chassis. These are documented in the help file: KtMTrig.chm, in the section: KtMTrig IVI-C Driver > IVI-C Reference.
There are two driver API hierarchies that client programs may use to control the instrument. The first is the instrument specific hierarchy. This hierarchy can be used to access all of the functionality of the instrument. This hierarchy is available to programs that use one of the driver constructors to instantiate the driver. For more information on initializing the driver, refer to the information in the KtMTrig IVI-C Driver > Initializing the IVI-C Driver help topic. For more information on using the instrument specific hierarchy, refer to the KtMTrig IVI-C Driver > IVI-C Reference > Hierarchy > Instrument Specific help topic.
The second hierarchy is the optional IVI Instrument Class compliant hierarchy which supports limited, basic instrument functionality common to most instruments of similar type. To see if this driver supports an IVI Instrument Class, refer to the IVI Compliance Information help topic. If supported, this hierarchy can be used to access the IVI class API for the <ClassName> class.
The help topics that are not under the Instrument Specific section describe the IVI compliant functions and attributes.
For the IVI.Net driver:
The KtMTrig IVI.NET driver application programming interface (API) includes methods and properties for setting instrument state variables, as well as methods for controlling the instrument and reading results from the instrument. These are documented in the help file: Keysight.KtMTrig.Fx40.chm, in the section: KtMTrig IVI-NET Driver > Reference.
There are two driver API hierarchies that client programs may use to control the chassis. The first is the instrument specific hierarchy. This hierarchy can be used to access all of the functionality of the chassis. This hierarchy is available to programs that use one of the driver constructors to instantiate the driver. For more information on using the driver constructors, refer to the information on The IVI.NET Driver Constructor in the KtMTrig IVI-NET Driver > Instantiating the KtMTrig IVI-NET Driver help topic. For more information on using the instrument specific hierarchy, refer to the KtMTrig IVI-NET Driver > Reference > Driver Hierarchy > IKtMTrig help topic.
The second hierarchy is the optional IVI Instrument Class compliant hierarchy which supports limited, basic instrument functionality common to most instruments of similar type. To see if this driver supports an IVI Instrument Class, refer to the IVI Compliance Information help topic. If supported, this hierarchy can be used to access the IVI class API for the <ClassName> class. For more information on using the class compliant hierarchy, refer to the KtMTrig IVI-NET Driver > Reference > Driver Hierarchy > IIviDriver help topic.
Configuring Driver Settings |
|
IVI instrument drivers implement inherent capabilities including properties/attributes that control driver behavior, utility methods/functions, and identifying information. For more information on using the inherent capabilities in the IVI.NET driver, refer to the KtMTrig IVI-NET Driver > Reference > Driver Hierarchy > IIviDriver help topic. For the equivalent information in the IVI-C driver, refer to the KtMTrig IVI-C Driver > IVI-C Reference > Hierarchy > Inherent IVI Attributes help topic and Utility help topic.
Properties/attributes that control driver behavior such as simulation, range checking, and instrument status checking can be enabled/disabled when initializing the driver or by using configuration information in the IVI Configuration Store. For more information, in the IVI.NET driver, refer to the KtMTrig IVI-NET Driver > Instantiating the IVI-NET Driver help topic. For the equivalent information in the IVI-C driver, refer to the KtMTrig IVI-C Driver > Initializing the IVI-C Driver help topic.
Obtaining the latest Introduction and KtMTrig driver |
|
Obtaining the latest revision of this Introduction: This document is re-released with a new revision letter whenever any information in this document changes. The revisions to the Introduction are listed in the table below, with the most recent revision listed first.
| Date (YYYY-MM-DD) |
Revision |
Description |
| 2016-12-16 |
(Revision letter is embedded in this document's file name.) |
First release of the Introduction for driver. |
To see if a later revision of the Introduction is available for this driver, perform the following steps:
- Go to www.keysight.com/find/M9019A.
- Click "Visit Technical Support".
- Select the "Drivers, Firmware & Software" tab.
- Click the "PXIe Chassis Family Drivers" link.
- Find your version of the driver.
- The link to the latest revision of the Introduction is provided under the "Supporting Documentation" label. It is recommended that you use the Introduction accessible from this link if it is a later revision than the Introduction you're reading now.
NOTE: In addition to checking for a later revision of this Introduction for your current driver version, you may also want to consider installing a later version of this driver, if available. See the next section to determine if a later driver version is available.
Obtaining the latest version of this driver: To see if a later version of this driver is available, perform the following steps.
- Go to www.keysight.com/find/M9019A.
- Click "Visit Technical Support".
- Select the "Drivers, Firmware & Software" tab.
- Click the "PXIe Chassis Family Drivers" link.
- Click the "Current Version" tab to view the latest version of this driver, and compare it to the driver version that you have.
- If the current version is later than your driver version, click the "Download" button and follow the instructions to download the current version and install it.
Hardware and Software supported with this driver |
|
Chassis supported with this driver: Keysight M9010A PXI Chassis, M9018A, M9018B, M9019A PXI Chassis
Hardware Revision Strings
Access the revision string for your chassis from the Soft Front Panel Help > About.
| Chassis |
Chassis
Manager
Firmware |
Monitor
Processor
Software |
Power
Supply
Hardware |
PCIe
Switch
Fabric |
Default Fabric |
| M9010A |
2.02 |
3.11 |
1 |
a1.2.a2.2 |
Only fabric: 2-Link Configuration: 1x8, 1x16 [Gen3 speed max] |
| M9018A |
1.07 |
0.59 |
5 |
1.1.257.1 |
2-Link Configuration: 2x8 [Rev. 2] |
| M9018B |
2.02 |
3.11 |
1 |
3.2.259.2 |
2-Link Configuration: 2x8 [Rev. 2] |
| M9019A |
2.02 |
3.11 |
1 |
a1.2.a2.2 |
Only fabric: 2-Link Configuration: 1x8, 1x16 [Gen3 speed max] |
Operating Systems Supported with this driver:
- Windows 7 (SP1)
- WES 7
- Windows 8.1 Update 1
- Windows 10
Keysight's IO Libraries Suite: The IO Libraries Suite (IOLS) must be installed prior to installing the PXIe Chassis Family driver. The following IO Libraries Suite releases are supported with this driver, with the most recent release listed first.
| Release Date |
Release |
Version |
Comments |
| 2016-10-26 |
17.3 |
17.3.21412.2 |
Use of the latest version is recommended. See www.keysight.com/find/iosuite for the latest version. |
| 2016-05-25 |
17.2 Update 2 |
17.2.20818.0 |
| 2016-08-21 |
17.2 Update 1 |
17.2.20605.2 |
|
| 2016-01-05 |
17.2 |
17.2.20407.1 |
Recommend upgrading to IOLS 17.2 (and above) to experience the improved device discovery algorithms performance and functionality.
Clients labels are shown in Keysight Connection Expert "Chassis Triggers" tab in IOLS 17.2 (and above).
User need to redo the reservations again as reservations with Keysight Connection Expert not persist after
upgrading to IOLS 17.2 (and above).
|
|
| 2015-11-21 |
17.1 Update 1 |
17.1.20011.4 |
No clients label is shown in Keysight Connection Expert "Chassis Triggers" tab in IOLS 17.1 update 1.
IOLS 17.1 update 1 software might takes longer time to perform its device discovery algorithms after the windows boot.
Note: Keysight Connection Expert will not display information or be usable until installation is complete.
|
|
