Error -1074135040 Revisited

[blockheadjr]

There are a couple threads in this forum that address this same error (albeit implementing different instruments), with a half dozen or so possible solutions - all of
which have failed to solve the problem for me.

Error -1074135040 occurred at cicld30 Initialize.vi
Possible reason(s):
Driver Status:  (Hex 0xBFFA0000)

(cicld30 refers to the California Instruments 3019LD 3kW AC Load, which is the source of the error in question)

Some background:

- I am using a new PC, and this is my first attempt at running a Labview VI on it.
- This same VI functioned without incident on my previous PC (which died).
- I'm using Labview 7.1.
- I'm using a GPIB inteface.

What I've tried so far to solve the problem (all of which have failed):
- Uninstalled and reinstalled Labview.
- Downloaded and installed NI-VISA 3.3.1 driver (latest version).
- Confirmed that MAX 'sees' all the correct instruments on the GPIB connection (Labview engages remote control of my instruments, and responds to *IDN?
queries, so I'm guessing that comm isn't an issue).
- Confirmed I have the latest IVI Compliance Package.
- Confirmed that the function name and parameters in the Library Call Node are correct (they worked before), and that the calling convention is correct.
- Built a new VI from scratch that just employs the Library Call Node (and required inputs and outputs).
- Alternately sweet talked/cursed at the monitor.

Here is an NISpy capture of the problem:

I noticed on previous threads about this error, there have been no single solution given for the problem, and each person who posed the problem solved it in 
different ways.  The feeling I get is that the root cause of this error is unknown, or that it is just a general purpose error that could mean just about anything 
(which isn't very helpful).  Besides posting other suggestions to solve my problem, would it be possible to have NI techs explore this issue further and 
perhaps add more robust error code schemes to better pinpoint error sources?



Thanks everyone for your help.

[Robert M]

What version of the compliance package do you have installed?  This error simply means that the IVI Engine is having problems loading.  If the engine cannot start, we have no way of knowing why.  It sounds like you are starting from a clean system, so I'm really not certain what might be going on.  Are there any other factors that might be involved here?  Do you meet the minimum specs for the compliance package? 

* Windows XP/2000/NT 4.0 or later
* Windows NT 4.0 users only: Windows Service Pack 6

* Internet Explorer 4.0.1
* PC using at least a 200 MHz Pentium class or higher microprocessor
* Minimum of 64 MB of RAM
* 150 MB of free hard disk space Have you tried running your application on a different computer?

Hope this helps,

[blockheadjr]

Thanks for your reply, Robert.  I'll try to give you as much info as I can here.

What version of the compliance package do you have installed?  IVI  Compliance Package 2.1.1.

Are there any other factors that might be involved here?  After loading Labview 7.1 onto the PC, my VIs had broken arrow errors - I was missing instrsup.dll and io.dll.  I loaded on instrsup.dll from a previous version of Labview (6.0), and io.dll from a different computer.

Do you meet the minimum specs for the compliance package? 

* Windows XP/2000/NT 4.0 or later  XP Professional
* Windows NT 4.0 users only: Windows Service Pack 6  n/a
* Internet Explorer 4.0.1  IE 6.0
* PC using at least a 200 MHz Pentium class or higher microprocessor  Pentium 4 1.8GHz
* Minimum of 64 MB of RAM  384 MB
* 150 MB of free hard disk space  I have plenty of hardspace

Have you tried running your application on a different computer?  The app I'm using has worked fine on a different computer.

There's nothing else I can think of to add at this time.  The configuration of our computers here at work are standardized - so the last computer that successfully ran this VI was identical to the one I'm using now.

[Robert M]

I'm curious as to why you were missing those dll's.  They should both have been installed with the compliance package, and missing them points to something not being installed correctly.  I'm wondering if other components are not installed on your system as well.  Also, using a possibly old version of the .dll may cause problems.  We'll want to make sure we are using the latest version of the .dll.  You may want to completely uninstall and reinstall the compliance package to make sure everything is installed correctly.

Regards,

[blockheadjr]

I realize that I gave incorrect info on the Labview Version - The package I have is Labview 7 Express, version 7.1.  Not sure if that makes a difference or not.

I did a search on all of the CDs that came with the Labview 7 Express package for both instrsup.dll and io.dll - to no avail.  Perhaps I'm missing a CD?  Here are the CD's I have:

LabVIEW 7 Express - Professional Development System - Wondows 2000/NT/XP - Version 7.1
LabVIEW - Companion Products for Windows - March 2004
Device Driver Reference CD - May 2004 (2 Disks - which include IVI Compliance Package 2.1.1)
NI-DAQ - for Windows 200/NT/XP/Me/98 - Version 7.1
NI-DAQ - Version 7.1 - Device Documentation
NI-488.2 for Windows - Version 2.1

I ran two searches: a *.dll search, and a *.dll.* search (since some dll's apparently have numerical suffixes).  Again, nothing even close to "io" or "instrsup". 

[Robert M]

The files aren't going to be in that format on the CDs.  They will be packed as part of a .cab file, rendering them unsearchable.  A reinstall of the Compliant Package should place them in the right folders in your system.

[blockheadjr]

So, I uninstalled Labview and then reinstalled.  After reinstallation, I did a search for instrsup.dll, to no avail.  I ran my VI, and the same error occured as before.  Either my CD is not installing the file, or the file isn't on the CD to begin with.

Perhaps there is an IVI compliance package update that definitely has the .dll files we've been talking about that I can download to my PC and try again?

[Robert M]

The IVI Compliance Package won't be installed or uninstalled with LabVIEW.  You can uninstall it from "Add/Remove Programs".  It is on the Driver CD that ships with LabVIEW.  You can also download the IVI Compliance Package 2.2 from our website.

[blockheadjr]

Yes, I meant that I had uninstalled and reinstalled Labview and all drivers. 

[Dennis_Knutson]

Did you actually select the IVI compliance drivers for installation? I don't think they are installed by default. When the driver installer finishes it's initialization, look for it under the Instrument Control features and see if it's checked. You should also be able to get the latest version from the download site mentioned