Hmm, yes, it's tough to say what might have motivated that recommendation. I have no idea what a "device template" is, or what it might mean for ibfind() to be "difficult to port." It's worked for many years here, with both genuine and emulated (HP 82350-series) adapters.
The one issue I've experienced is the inability of 64-bit Windows apps to detect the emulated NI488.2 devices provided by Agilent I/O Libraries for the 82357 adapters. This is why the 32-bit drivers are still linked with gpib-32.obj rather than the newer ni4882.obj API module. -- john, KE5FX Miles Design LLC > -----Original Message----- > From: [email protected] [mailto:time-nuts- > [email protected]] On Behalf Of Ulrich Bangert > Sent: Friday, January 24, 2014 1:29 AM > To: 'Discussion of precise time and frequency measurement' > Subject: Re: [time-nuts] Help for general GPIB problem > > John, > > thank you for your help. The idea to use IBDEV resulted from the following > official NI statement: > > Snip---------------------------------------------------------------- > > For current and new GPIB applications, IBDEV should be used. IBFIND will > return a board or device descriptor based off the device templates in the > GPIB.ini file. Since IBFIND relies on GPIB.ini to return the board or device > descriptor, it is difficult to port. For example, with the device templates, > the device name can be changed to a custom name. Unless the device > templates > are ported to the target machine, the call will fail. IBFIND is found in > older applications and can be easily updated to using IBDEV instead. > > IBDEV is far more portable in that it frees the application from the need to > rely on specific device names. IBDEV also returns a board or device > descriptor but allows you to programmatically specify all the required input > parameters in the parameter list of IBDEV (thus avoiding the need to refer > to device templates). IBDEV should be used when creating a new GPIB > device > application. > > IBFIND should still be used to open a GPIB board communication session, > not > for communication with instruments. > > Snip--------------------------------------------------------------- > > But i will of course follow your suggestion to look up Timelab's enumeration > function. > > 73's de Ulrich, DF6JB > > > -----Ursprungliche Nachricht----- > > Von: [email protected] > > [mailto:[email protected]] Im Auftrag von John Miles > > Gesendet: Freitag, 24. Januar 2014 08:58 > > An: 'Discussion of precise time and frequency measurement' > > Betreff: Re: [time-nuts] Help for general GPIB problem > > > > > > You probably want ibfind() rather than ibdev(). Take a look > > at gpibport.cpp in the TimeLab source > > (drivers/shared/gpibport.cpp under the installation folder), > > in the enumerate_ports() function. > > > > -- john, KE5FX > > Miles Design LLC > > > > > -----Original Message----- > > > From: [email protected] [mailto:time-nuts- > > [email protected]] > > > On Behalf Of Ulrich Bangert > > > Sent: Thursday, January 23, 2014 3:23 AM > > > To: Time nuts > > > Subject: [time-nuts] Help for general GPIB problem > > > > > > Gentlemen, > > > > > > I am just going to improve my EZGPIB utility so that it can > > make use > > > of > > more > > > than one GPIB-interface (supported by GPIB32.Dll, not Prologix). I > > > have been trying to enumerate all detected interfaces by using > > > > > > ibdev(bi,0,0,T300ms,0,1) > > > > > > in a loop where bi starts with "0" and is incremented by > > "1" until the > > > result of the call gets negative. Much to my surprise this loop > > > detects 4 > > > (!) interfaces GPIB0 to GPIB3 even if absolutely NO > > interface is connected > > > to the pc. > > > > > > What am I doing wrong. Is "4" the maximum number of interfaces that > > > may be handled by GPIB32.Dll ???? > > > > > > What do I need to do to find the real number of detected interfaces > > > ????? > > > > > > Best regards and TIA for your answers > > > > > > Ulrich Bangert > > > www.ulrich-bangert.de > > > Ortholzer Weg 1 > > > 27243 Gross Ippener > > > > > > _______________________________________________ > > > time-nuts mailing list -- [email protected] > > > To unsubscribe, go to https://www.febo.com/cgi- > > > bin/mailman/listinfo/time-nuts and follow the instructions there. > > > > _______________________________________________ > > time-nuts mailing list -- [email protected] > > To unsubscribe, go to > > https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts > > and follow the instructions there. > > _______________________________________________ > time-nuts mailing list -- [email protected] > To unsubscribe, go to https://www.febo.com/cgi- > bin/mailman/listinfo/time-nuts > and follow the instructions there. _______________________________________________ time-nuts mailing list -- [email protected] To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there.
