12-09-2005 01:53 PM
12-12-2005 01:14 AM
I tried the NI class driver for IviDCPwr with a logical name, which configuration is mapped to an IVI-COM IviDCPwr driver as the Software Module. As I see it, the NI class driver does not operate with IVI-COM driver.
The error was:
Error -1074134949 occurred at IviDCPwr Initialize With Options.vi
Possible reason(s):
Driver Status: (Hex 0xBFFA005B) Primary Error: (Hex 0xBFFA005B) File not found.
After changing the IVI configurtaion for the logical name to map to an IVI-C driver as the Software Module, everything went fine. My environment is LabVIEW 7.1 + NI IVI Compliance Package 2.2, with driving Kikusui PAT series DC supply prototype IVI-COM driver. I believe it is also true when using Agilent, as the IVI-COM driver architecture is the same. I have not tested with the latest compliance package yet though. I think that NI class drivers are just incompatible with IVI-COM.
12-12-2005 02:55 PM
10-26-2006 07:24 PM
10-27-2006 10:50 AM
11-23-2009 01:26 PM
Hello,
My local Field Engineer, Travis Marsh, suggested that I try and ping this thread again and see if there was any change to NI's support policy for IVI-COM adapaters for RFSA and RFSG. He said if there were more specific questions you might give him a call directly.
Also, so if I understand this all correctly I can use IVI Class functions for any for the 5 basic classes (Power supplies, FGEN, SCOPE, DMM, Power Meter) if I have an IVI-C or IVI-COM driver but I can only use IVI-C drivers if I want to use the class functions for RFSA and RFSG.
Thanks,
11-24-2009
09:22 AM
- last edited on
06-13-2024
03:39 PM
by
Content Cleaner
Hello Joe,
The IVI-COM adapters make it possible to use the IVI-C Class drivers with IVI-COM drivers. With the recent release of IVI Compliance Package 4.1 (ICP), we now have IVI-COM adapters for all 12 of the IVI classes. You will need to make sure and enable the IVI-COM adapter feature in the ICP installer's feature tree. TestStand uses the IVI-C Class drivers, so you will need the IVI-COM adapters if you plan on using any IVI-COM drivers that do not have IVI-C wrappers. If an IVI-COM driver has an IVI-C wrapper, the wrapper will be used instead of the IVI-COM adapter.
Please take note that the IVI-COM adapters merely translate the IVI-C Class driver calls to the IVI-COM driver's class interface. If you see problems when using the IVI-COM driver, please try communicating with it directly through the ActiveX interface because the problem is most likely in the actual driver, not the IVI-C class driver or COM adapter.
Cheers,
NathanT