Instrument Control (GPIB, Serial, VISA, IVI)

cancel
Showing results for 
Search instead for 
Did you mean: 

IVI virtual name definitions prevent IVI physical names from functioning

I am writing an application using CVI 7.0, which communicates with IVI devices using virtual names (in this instance a Pickering switch).
This works fine.
A colleague is developing several applications on the same equipment using TestStand 3.0 and is attempting to reference the switch device by its physical name.
We have found that once a virtual name has been defined in MAX, attempts to use the physical name fail.
If the virtual name is removed the physical name works again.
We need both applications to communicate with the devices through either virtual or physical names.
Note that only 1 application will run at a time - either TestStand or CVI.
See the attachment for the TestStan
d error response and MAX configuration.

Regards

Alan Knowler
0 Kudos
Message 1 of 2
(3,036 Views)
Alan,

The issue is most probably in the specific driver. The error that gets returned in TestStand is BFFA4005 which is a specific driver error (see NI IVI Driver Help). Since we do not have access to the source code of the Pickering driver, you should contact their support channels. Although you said that everything works fine in CVI 7.0 using virtual names, I think you could come across the same issue if you would just use a different order of calls such as Connect, followed by the GetPath, and then SetPath functions.

Best Regards,

Vesna Jadric
Instrument Drivers/IVI
National Instruments
Message 2 of 2
(3,036 Views)