VISA error

[Oliver Friedrich]

Hallo NG,

I've programmed a VI that communicates via GPIB with an instrument. Works
fine on the Computer (NT 4.0 with LV 5.1.1 Full Development), where I
developed the VI.

I built an application of this VI. Works fine on the Computer, where I
developed.

When I try to portate it on another Computer (NT 4.0 with Runtime Engine LV
5.1.1) I have the following error

Error -1073807202 occurred at an unidentified location.

Possible reasons:

VISA: (Hex 0xBFFF009E) A code library required by VISA could not be located
or loaded.

Which library is missing ?

Thanks a lot

[Johannes Niess]

"Oliver Friedrich" writes:


[...]

>
> When I try to portate it on another Computer (NT 4.0 with Runtime Engine LV
> 5.1.1) I have the following error
>
> Error -1073807202 occurred at an unidentified location.
>
> Possible reasons:
>
> VISA: (Hex 0xBFFF009E) A code library required by VISA could not be located
> or loaded.
>
> Which library is missing ?

The VISA runtime engine? AFAIK it is an extra installation package.

[Brian_Vibert]

VISA needs to be installed on the target machine. If you installed a NI GPIB card then VISA should have been installed.

Make sure you have VISA installed, if it is and still doesn't work then maybe try to re-install it.

Hope this helps!

Brian

[Rob Cole]

This is a problem of something missing in VISA. Either the VISA driver needs to be loaded for the GPIB card, or, if it's not an NI GPIB card, then using a VISA name supplied by Max.

If you are using an non-NI GPIB card (we use HP cards) then you need to use the "standard" VISA name format. The format is:
GPIB0::12::INSTR
The GPIB0 is for the first GPIB card in the system (you can also use GPIB1 for the second card, etc.). The 12 would be the GPIB address number of the instrument and, of course, the INSTR is for an instrument and in most cases you can leave the INSTR off.

Hope that this helps solve your problem.

Rob

[rookie]

Thank you that worked for me. I had the same issue flare up just this morning. I can not believe someone else had the same issue at the same time. This was a great resource. Thanks

[RLL]

re: VISA errors.

I'm new to all of this.  I needed to replicate an ATE system that was put together for us by a large US consulting company several years ago (before my time).  They were pretty good with their documentation, but they neglected to mention that a VISA run time is needed to be installed before their application would work.  Probably because they developed the software on the existing systems and the Labview/CVI development system automatically installed VISA.  The system uses instruments from Agilent and Tek, and a Keithley KPCI-488 card as the controller.  I installed everything as they described and when I ran the application (that had been developed with CVI), got the now classic error bfff009e, "A code library required by VISA could not be located or loaded".

This has got to be one of the dumbest, least clear error messages I've seen in a long time.  Not knowing anything else, an educated guess would indicate that it is VISA itself that is generating this error message.  It doesn't tell you what specifically is missing so it is almost usless.  However, a search of the NI message boards here indicates that it is actually a total lack of VISA at all that causes this error message.  Using the search string "a code library" results in 60 hits, most all for the same issue in one way or another.  It would seem to me that an error message that simply states instead "VISA is not installed" or some such thing would have saved hundreds of developers countless debugging hours.

I know this is not NI's fault, I have seen the same error message within an XML file of error messages on Agilent's software as well so it must be a "standard" message.

My 2 cents...

Oh and another thing, the CEC488 driver software that comes with the Keithley KPCI-488 card seems to expect the VISA run time to be in the C:\VXIPNP directory and not the C:\Program Files\IVI Foundation\VISA directory.  This means that you MUST use Version 4.1 or earlier.  (Or maybe install one of these earlier ones then install the latest.)  I couldn't get an install of 4.2 to work, but 4.1 does.  Maybe if I now install 4.2 it will work because it defaults back to the old installation directory.  See the readme for version 4.2.

-RLL