Yes, but not directly.

TestStand 2.0 gives direct access to COM objects with dual interfaces through the ActiveX Automation Adapter. This means that IVI-COM drivers, which have custom interfaces, cannot be accessed in this way. If you try to select an IVI-COM driver from the drop-down automation server list you will get a “This server exports no ActiveX Automation objects” error message.

NI has a longstanding tradition of supporting both IVI-C and IVI-COM with their measurement software so it’s quite likely that a future TestStand version will include support for IVI-COM drivers. This support would allow a TestStand step to directly execute a property or method in an IVI-COM driver.

To access IVI-COM drivers in TestStand 2.0, a wrapper must be created from the interfaces that TestStand can call directly to the IVI-COM driver. VIVID’s LabVIEW wrappers work, as do LabWindows/CVI wrappers (see application notes on these subjects). Another option is to create an ActiveX Server that TestStand can call using the ActiveX Automation Adapter. This Server would then call the methods and properties in the IVI-COM driver. This ActiveX Server could be created in Visual Basic or Visual C++.

The VXI PnP consortium is still active at this time, mostly they are working on the issue of IEEE-488.2 protocol for USB. The IVI Foundation has invited the VXI PnP consortium to merge with IVI and it appears quite likely that this will occur. At the last IVI board meeting a committee was formed to look into the mechanics of this merger.  8/10/2001