IVI Compliance Package 2.0

[Kimmo]

I had a problem when I installed the IVI Compliance Package 2.0 for my HP oscilloscope. Now none of my instruments communicate with labview. They do not find the old IVI library. I have labview 6.1. I think the older IVI driver engine 1.83 is overwritten while the IVI Compliance Package 2.0 is installed. An error comes while initialize is run. The IVI compliance 2.0 driver doesn't either work with my other instruments.

I am trying to communicate with a Tektronix tds 2012 oscilloscope and a Keithley 2700 data aquisation system which with have their own IVI libraries. With the old NI IVI engine 1.83 they worked perfectly. So what should I do. Do I have to somehow recover all I did or how can I make the IVI Compliance Package 2.0 and all
my old test programs work with instruments and labview.

[cymrieg]

Kimmo,

I am interested in how NI respond to your question. You will see a error BFFA6000 from our 2700 driver with the IVI engine 2.0. We have a modified driver going though our QA process now and should be available in a couple of weeks.

You could always un-install the 2.0 engine and go back to 1.83. Why did you upgrade? Going from 1.83 to 2.0 means all the instrument drivers and their installs need to change from using the ivi.ini to using the ConfigStore so it's going to take some time to catch up.

[Kimmo]

Thanks for your answer. I upgraded the engine in hope that it would be faster. The error with Keithley 2700 is:

KE2700 Initialize.viDriver Status: (Hex 0xBFFA1200) The specified configuration store file could not be deserialized.
Elaboration: IviConfigServer.IviConfigStore.1: Deserialize failed. Can not create XML DOMDocument. Please check your XML parser installation.

With tektronix the error is
tktds1k2k Initialize.viDriver Status: (Hex 0xBFFA1200) The specified configuration store file could not be deserialized.
Primary Error: (Hex 0xBFFA1190) The session handle is not valid.

Now I uninstalled all parts of the IVI 2.0 compliance package and reinstalled the 1.83 engine from the labview cd in modified mode. I can't still communica
te with the instruments and the errors are the same. Should I uninstall labview and then reinstall it?

[Kimmo]

Yes!! I solved the problem. Labview had to be uninstalled and then reinstalled. Then the 1.83 IVI engine works all right. Uninstalling 2.0 IVI package doesn't seem to help.

[gopinath]

Kimmo,

To completly uninstall the IVI compliance package 2.0 package, you also need to run the cleanup utility downloadable from the IVI Foundation website http://www.ivifoundation.org/ApprovedSpecs/Default.htm. This removes all the IVI shared components installed by the compliance package.

[gagi1]

Kimmo,

It seems that the problems you were seeing are caused by the incorrect installation of your XML parser. I would like to get more information about your system so we can try to reproduce the problem. I would appreciate if you could answer the following questions:

1. What is the OS version and Service Pack version?
2. What is the Internet Explorer version?
3. What other NI products you have installed on your system other than LabVIEW 6.1?

The answer you got from Keithley is not entirely correct. Going from 1.83 to 2.0 does NOT mean that all instrument drivers and their installers need to be updated to use the ConfigStore file. The matter of fact is that our own drivers are still not updated to use XML file but they do work with IVI C
ompliance Package (ICP) 2.0 just fine. The ICP installs the INI to XML Converter. The conversion happens automatically when you install the ICP 2.0. Also, if MAX detects any changes, it launches a conversion utility automatically before loading the configuration from the Master Configuration Store file. You can find more information on this in the ICP Release Notes.

Regards,

Vesna Jadric
Instrument Drivers/IVI
National Instruments

[somat_eng]

cymrieg,

By your answer, I'm guessing you are associated with Keithley instruments. I just posted a question about the error BFFA6000 which I'm getting from the 2700 IVI driver (I think). When will Keithley be releasing this updated driver? Is there a workaround for this problem? Any beta-testing opportunities?

- Thanks.

[cymrieg]

Yes, please send your email deatils to "jryland@keithley.com" and I will let you know where you can download the beta from.

Alternatively the only work-around is to un-install the IVI Compliance package 2.0 and re-install 1.83.

How did you end up with IVI Compliance package 2 on your system?

[gagi1]

The IVI Compliance Package 2.0 is a software package that contains IVI class drivers and the support libraries such as the IVI Engine and is based on and is compliant with the latest version of the instrument programming specifications defined by
the IVI Foundation.

It is available for download from ni.com and it also ships with LabVIEW 7.

National Instruments strongly recommends that customers do not revert back to previous IVI Software after installing the IVI Compliance Package.

Vesna Jadric
Instrument Drivers/IVI
National Instruments

[Kimmo]

Well I'm using Windows XP and the Internet Explorer version is 6.0. From the Microsoft webpage I downloaded the latest updates for Windows and Internet Explorer but it didn't help. I don't have any other Ni products installed on my computer except Labview 6.1 professional version. The situation of the task isn't anymore so critical because I succesfully reinstalled IVI engine 1.83 and everything works fine again.