keithley 2302 ivi driver spits error -1074135040

[richjoh]

I have the latest and greatest IVI driver (2302 IVI driver) for the Keithley 2302 Battery simulator but when the driver calls Ivi.dll, it spits out error -1074135040. The dll is located in c:\Windows\system32.

I'm running windows XP. I had an older IVI installed that did the same thing. These are National Instruments "Certified" drivers...

[AnalogKid2DigitalMan]

Have you installed the IVI Compliance Package?

-AK2DM

[richjoh]

Just installed the latest Ivi package you mentioned. I still get this error. Are there any settings I need to perform in MAX to resolve this issue. Btw, I kept the old IVI package and installed, on top it, the new IVI (LV ver 7 is not listed in the new installer). I'm using LV7.

[Albert.Geven]

The biggest problem with IVI is the bad debugability and installation.

I asked Keithley to get rid of all these problems and deliver LabVIEW based ("G") drivers.

[cymrieg]

Albert,

I agree for LabVIEW users then a Native LabVIEW driver is best. I would like to exchange a few emails with you (pick your brains so to speak) about Native LabVIEW drivers. Can you send an email to instrumentdrivers@keithley.com and I will repond with my questions?

[NathanT]

Hello Rich,

        I just did a simple test in LabVIEW 8.2.1 with the specific driver wrapper:

and did not receive any errors.  If you are calling the specific driver directly, then there are no IVI settings that you need to configure in MAX.  If you would like to use the IVI Class Drivers, then you will need to configure IVI settings in MAX.  What old IVI package are you referring to?  If you have access to a clean machine or one that is easily re-imaged, another option is to see if the error is reproduced with a clean install of a supported version of LabVIEW and the current versions of NI-VISA and ICP.

Cheers,

NathanT

[richjoh]

---

NathanT wrote:

Hello Rich,

        I just did a simple test in LabVIEW 8.2.1 with the specific driver wrapper:

and did not receive any errors.  If you are calling the specific driver directly, then there are no IVI settings that you need to configure in MAX.  If you would like to use the IVI Class Drivers, then you will need to configure IVI settings in MAX.  What old IVI package are you referring to?  If you have access to a clean machine or one that is easily re-imaged, another option is to see if the error is reproduced with a clean install of a supported version of LabVIEW and the current versions of NI-VISA and ICP.

Cheers,

NathanT

---

Hi NathanT,

I not able to match your test environment. I'm using LV7 (and not allowed to update). The "Int with Options.vi" BD shows that "ivi.dll" is called and results in the error mentioned. Weirdly, I have other machines at my facility running without flaw with IVI compliance package 3.2 with toolset 2.1.4. But, my issue persist on my present working PC using same package and toolset.

Message Edited by richjoh on 11-02-2009 04:22 PM

Message Edited by richjoh on 11-02-2009 04:24 PM

[NathanT]

Hello Rich,

       I don't see a 2.1.4 version of the IVI Driver Toolset (just a 2.0 version).  Could you please consult Add/Remove Programs to confirm the version?

Another thing to try is using the IVI Class driver and see if the error continues.  After you do that, I will see about setting up a test system with the SW that you have and seeing if the problem reproduces in simulation mode.

Thanks,

NathanT

[NathanT]

Hello Rich,

        When I started with a clean image of WinXP and installed LV 7.0 PDS, and IDT 2.0, the ke230x Getting Started VI worked fine in simulation mode.  I then installed ICP 3.2 and ran the VI again without any errors.  There is a good chance that your machine is somehow in a bad state.  I recommend uninstalling all of the IVI software and trying only reinstalling ICP 3.2.  If that does not help, you should probably call in to NI Support and speak with an Applications Engineer (ni.com/support).  I have attached the old and unsupported version of the ke230x LV70 installer for you.

Thanks,

NathanT