Why doesn't ibfind() work (anymore)?

[dgholstein]

When using the latest NI488.2 drivers with an application compiled and linked to the 1.70 library, the ibfind() routine doesn't work. Is the ibfind() function working or do I need to re-compile/re-link whenever the drivers are updated?

...Dan

[LoganS]

Could you be more specific in how the ibfind is not working? Is there a particular error that is occuring when you try to use the ibfind function or is your system hanging or something else? I'm using the current version of the driver and ibfind appears to work just fine for me, so the more specific you are, the better able we'll be to troubleshoot any issues.

Logan S.

[dgholstein]

Thanks for the reponse.

It doesn't crash the computer, or application, it simply exits ibfind() without finding the device. I'm hesitant to re-compile/re-link against the latest library since it works well when run against the 1.70 package/DLL.

Do I have to re-compile/re-link everytime NI updates the driver?

...Dan

[NI-488.2 master]

You should not have to recompile and relink anything. We do a lot of testing to be sure that users don't need to recompile and relink their apps. What version of NI-488.2 are you using? What type of GPIB interface are you using? Does the NI-488.2 Troubleshooting Wizard pass for the installed board?

Craig A
National Instruments Engineer

[dgholstein]

It works with the NI 488.2 package 1.70, doesn't with any of the 2.x downloads.

I have this problem both with the PCI card and with the GPIB-USB, with Win XP and Win 2000.

All the diagnostics work fine, NI Communicator can be used to control any instrument attached to the GPIB bus. I've been able to pass the "*idn?" query and "IP" (Instrument Preset) to HP/Agilent instruments such as the 8510, 8720 and an HP oscilloscope through Communicator.

The only difference I encounter is that ibfind() works with 1.70 and not with 2.x. Note: I'm using ibfind(), not ibdev().

...Dan

[LoganS]

What version(s) of NI-488.2 do you currently have installed on your computer? How are you calling ibfind? Are you using LabVIEW or IBIC or some other means?

Logan S.

Message Edited by LoganS on 04-13-2005 07:46 AM

[dgholstein]

I am calling ibfind() from my MSVC-compiled DLL -- which, in turn, is being called from LabView. Why is it not clear the NI488.2 version I'm using is the only working version of 1.70, I'm I missing something here? 1.70 works, 2.1 and 2.2 don't.

[NI-488.2 master]

Can you post an NI-Spy capture of the ibfind that does not work? I think I could tell pretty quickly what the problem might be if you did so.

Craig A.
National Instruments Engineer

[b_s_]

Please help:
ibfind(dev0) doesn't work for us either,
we compiled our DAB logging SW using LabWindows CVI 8.0 (the application was written in LabWindows for DOS more than 10 years ago)
We have tried the current drivers available on ni.com (2.x) on Windows XP, Windows 2000 and Windows Me, on various PC's
(Pentium 4 (with and without hyperthreading enabled), PIII, PII, nothing helps.

Error message from the DAB logging software (Open Device not working):

Exit 02-06-2006 14:08:08 from module esvb
Instrument logical ID=0
Last command buffer:
esvb error 220
ibsta 0x8000
ERR GPIB error
iberr 0
EDVR DOS error
ibcnt -535560139


NI Spy captured this error message from our DAB logging SW (Instrument R&S ESVB)
> 1. ibfind(dev0)
> Process ID: 0x000002BC Thread ID: 0x000002D8
> Start Time: 12:43:08.709 Call Duration: 00:00:00.040
> ibsta: 0x8000 iberr: 0 ibcntl: -535560139(0xe0140035)

Is there any solution to this?
Is the only solution to use the driver version 1.7 (not available for download, but on request)
Regards Bjørn

[dgholstein]

I believe using 1.7 is the way to go.  It's a pain, but it's more difficult proving to NI that the driver is broken than to switch.  As well, NI has said we need to switch from ibfind() anyway, so I did.

   ...Dan