ibfind wont recognize device name from template

[bk1]

I have installed a PCI-GPIB card and downloaded latest
driver software (ni488222.exe) on to a Windows 2000
system. I changed device names in template (using
Gpibconf.exe) to accomodate existing application.
Here is the problem:
ibfind(device) does not work in the application OR in
the interactive NI tool. However, MAX can see the
devices and I can query them as well.
The GPIB controller and devices (dmm, power supplies
etc.)all check out ok. The ibfind call does not seem
to utilize the GPIB.INI file.

example: in the interactive tool I enter ibfind DMM,
the result is [8000] (err) error: EDVR (0xe0140035).
This appears to suggest that the device name "DMM" is
not in the device template. I have verified t
hat it
exists in the GPIB.INI file. What have I missed?

Thanks in advance...

Bill

[JoshuaP]

Hey Bill,

The first thing you need to do is open up the GPIB.INI file and change it back to its defaults.

Then, run GpibConf.exe located at C:\Program Files\National Instruments\NI-488.2\Bin. Change the Device Name to your desired DEVx and double click on DEVx and change the name to DMM. Click OK twice and now try running ibfind.

If you still get the error, then open up the GPIB.ini file and remove the quotes (" ") around the attributes. Specifically, make sure you remove the quotes around "DMM".

I hope this helps out.

JoshuaP
National Instruments

[bk1]

Thanks Joshua. I removed the quotes inside the GPIB.INI
file and things seem to be working now.

Regards,
Bill

[pDub]

I have found the same problem with my version NI-488.2 ver 2.2. I also am running on Windows 2000. I have also found that if I run the GPIBCONF program and just open the window to edit the name, it gets screwed up even if I click "cancel" instead of "OK". My application software looks for a specific device name to know if the device is supposed to be used for a particular system, so changing the device name is a requirement.

I had originally tested our software on a previous version of NI-488.2 (2.1, I think), and I don't remember this being a problem. Is this a problem with 2.2? This is obviously a bug and should be fixed. Modifying the GPIB.INI file as part of our standard system setup procedure will not fly...

Thanks,
pDub

[NI-488.2 master]

This problem is fixed in version 2.3 of the driver, which is available on the ni website.

Let us know if you still experience a problem with it.

Craig A.
National Instruments Engineer