Importing LV driver into instr.lib folder

[KF]

I have a problem importing LabVIEW driver into instr.lib directory so that I could access these LabVIEW functions via function palette. I understand that I only need copy all the driver files (i.e. *.llb file and all *.mnu files) into a designated folder within instr.lib directory. However, even though I have restart my LabVIEW application, I still could not access the driver functions from the function palette and I could only see question mark (?) on these functions (see screenshot below).

KF

[Darren]

Make sure the folder you dropped the .mnu and .llb files into doesn't have an underscore next to the name.  Also, you didn't modify the name of the .llb or any of the VIs in it, did you?  If you did, the .mnu won't be able to link to the VIs.  Finally, make sure you're looking in the right place in the palettes...you should be looking under the Instrument I/O > Instrument Drivers subpalette (in LabVIEW 8.0).  If you're still having problems, perhaps you should respond with more details about the issue you're having (and a screenshot that isn't a broken link), like the actual directory structure on your disk where you dropped the .llb and .mnu files.

Good luck,

-D

[KF]

I created a folder with the name of AgXXXXX inside directory C:\Program Files\National Instruments\LabVIEW 7.1\instr.lib

This means all my *.llb file and *.mnu files are located within the following directory C:\Program Files\National Instruments\LabVIEW 7.1\instr.lib\AgXXXXX

I didn't rename any files that I have extracted. Could it be something wrong with *.mnu files?

***

KF

***

[Darren]

I guess something is screwy with the .mnu files.  Have you tried opening the VIs directly (by using File > Open or the "Select a VI" option on the Functions palette)?  If so, did the VIs open ok?  If the VIs are fine, and you have them in a folder in instr.lib like you describe, then faulty .mnu files is about the only other explanation I can think of.

Good luck,

-D

[thehobbs]

Are you using an instrument driver from the Instrument Driver Network?  If so, which one?

The driver's folder name in instr.lib is very important and must match what the .mnu files expect it to be.

You also mentioned 'importing' the driver.  Did you use the Import CVI Driver functionality in LabVIEW?

[Dennis_Knutson]

Jason is right about the name of the folder has to match the name of the driver. There is no such driver as AGxxxxx.

[KF]

Actually I am checking if the driver for a-yet-to-be-released test instrument is working fine with LabVIEW; now I know what went wrong.

The folder (where the driver sits in) name must be the same as the library file, otherwise it won't work (i.e. folder must be created as hp34401a if the library file name is hp34401a.llb).

In normal case, end users will not have to create a folder themself, since standard LabVIEW driver package comes in a self-extract exe format.

Thanks for the pointer, guys.

***

KF

***