OK, understood. So it seems that the next step is to try to connect with those reported devices and see if an error is returned, identifying the really connected ones from the placeholders...
On Thu, Jan 23, 2014 at 5:00 PM, Ulrich Bangert <df...@ulrich-bangert.de> wrote: > Azelio, > >> Try to stop the HPIB driver... > > I do not have any HPIB (=HP specific) driver in my system. Instead I use the > GPIB32.DLL that comes together with every National Instruments GPIB > interface adapter. The DLL is basically thought as the National Instruments > support for C-Programmers but I wrote a wrapper unit to be able to use the > DLL from my Delphi programming environment. > > The DLL is the BASIC translation between software and hardware and can > hardly been left away. It is responsible for the fact that you can use the > same DLL function calls regardless of what physical interface is used, i.e. > it works with a PCI plugin card as well as with USB to GPIB adapters as well > as with network based GPIB adapters (as long as the all come from NI). That > is one of the really NEAT things with NI stuff. > > Best regards > Ulrich > > > >> -----Ursprungliche Nachricht----- >> Von: time-nuts-boun...@febo.com >> [mailto:time-nuts-boun...@febo.com] Im Auftrag von Azelio Boriani >> Gesendet: Donnerstag, 23. Januar 2014 14:27 >> An: Discussion of precise time and frequency measurement >> Betreff: Re: [time-nuts] Help for general GPIB problem >> >> >> Try to stop the HPIB driver... maybe the driver is reporting >> as available even if no hardware is actually connected. >> >> On Thu, Jan 23, 2014 at 12:22 PM, Ulrich Bangert >> <df...@ulrich-bangert.de> wrote: >> > 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 -- time-nuts@febo.com >> > To unsubscribe, go to >> > https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts >> > and follow the instructions there. >> _______________________________________________ >> time-nuts mailing list -- time-nuts@febo.com >> To unsubscribe, go to >> https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts >> and follow the instructions there. > > _______________________________________________ > time-nuts mailing list -- time-nuts@febo.com > To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts > and follow the instructions there. _______________________________________________ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there.