OT: Test for NI IEEE-488 interface
Gentlemen,
I know this is a bit OT but otherwise I also know that some of you are
well acquainted to IEEE-488 data acqusition:
Suppose I can test whether the National Instruments DLL for their range
of IEEE-488 interfaces is available on a Windows based system. Suppose
also that I can load the DLL dynamically and find out whether all the
expected function names are really exported by the DLL, i.e. if an
IEEE-488 interface WERE really connected to the pc I would be in full
control of it.
What actions (DLL-calls) would you suggest for a good test of the
presence of an IEEE-488 interface and it's basic functionality? The test
should NOT involve any communication to instruments on the bus. Its just
to find out whether an interface is available and if it can be expected
to be in working condition.
Best regards and TIA
Ulrich Bangert
www.ulrich-bangert.de
Ortholzer Weg 1
27243 Gross Ippener
Germany
Ulrich,
I do not have a plug-in NI card (I do have a USB type controller from NI
though) so I am not sure what I am going to say will work, but it's worth a
try.
I believe the IEEE-488 controller has its own address (that is not often
used, but the IEEE-488 spec requires that), so you should be able to address
it and get its name. You should also be able to set its time-out and ask it
to query a non-existant instrument and get the time out error from the
controller card, which I believe is different from the time-out from the DLL
(which you would obtain if there were no controller card).
Didier KO4BB
-----Original Message-----
From: time-nuts-bounces@febo.com
[mailto:time-nuts-bounces@febo.com] On Behalf Of Ulrich Bangert
Sent: Saturday, October 06, 2007 7:23 AM
To: Time nuts
Subject: [time-nuts] OT: Test for NI IEEE-488 interface
Gentlemen,
I know this is a bit OT but otherwise I also know that some
of you are well acquainted to IEEE-488 data acqusition:
Suppose I can test whether the National Instruments DLL for
their range of IEEE-488 interfaces is available on a Windows
based system. Suppose also that I can load the DLL
dynamically and find out whether all the expected function
names are really exported by the DLL, i.e. if an
IEEE-488 interface WERE really connected to the pc I would be
in full control of it.
What actions (DLL-calls) would you suggest for a good test of
the presence of an IEEE-488 interface and it's basic
functionality? The test should NOT involve any communication
to instruments on the bus. Its just to find out whether an
interface is available and if it can be expected to be in
working condition.
Best regards and TIA
Ulrich Bangert
www.ulrich-bangert.de
Ortholzer Weg 1
27243 Gross Ippener
Germany
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.
Didier,
I do not have a plug-in NI card (I do have a USB type
controller from NI
though) so I am not sure what I am going to say will work,
but it's worth a try.
I am not sure by 100%, just say 99 % but I believe that the DLL
installed with ALL NI IEEE-488 interfaces is pretty much the same
regardless of the type of interface and that the handling of different
interfaces is managed completely INSIDE the DLL itself. That is why I am
hoping to find a suitable test for ALL NI interfaces and your
suggestions are well worth trying. I have currently a PCI-interface
available to make some experiments with and would like to send you some
tests for your USB based interface ASAP in case you are willing to help
me with that.
73 and my best regards
Ulrich
-----Ursprungliche Nachricht-----
Von: time-nuts-bounces@febo.com
[mailto:time-nuts-bounces@febo.com] Im Auftrag von Didier Juges
Gesendet: Samstag, 6. Oktober 2007 16:14
An: 'Discussion of precise time and frequency measurement'
Betreff: Re: [time-nuts] OT: Test for NI IEEE-488 interface
); SAEximRunCond expanded to false
Errors-To: time-nuts-bounces+df6jb=ulrich-bangert.de@febo.com RETRY
Ulrich,
I do not have a plug-in NI card (I do have a USB type
controller from NI
though) so I am not sure what I am going to say will work,
but it's worth a try.
I believe the IEEE-488 controller has its own address (that
is not often used, but the IEEE-488 spec requires that), so
you should be able to address it and get its name. You should
also be able to set its time-out and ask it to query a
non-existant instrument and get the time out error from the
controller card, which I believe is different from the
time-out from the DLL (which you would obtain if there were
no controller card).
Didier KO4BB
-----Original Message-----
From: time-nuts-bounces@febo.com
[mailto:time-nuts-bounces@febo.com] On Behalf Of Ulrich Bangert
Sent: Saturday, October 06, 2007 7:23 AM
To: Time nuts
Subject: [time-nuts] OT: Test for NI IEEE-488 interface
Gentlemen,
I know this is a bit OT but otherwise I also know that some
of you are well acquainted to IEEE-488 data acqusition:
Suppose I can test whether the National Instruments DLL for
their range of IEEE-488 interfaces is available on a Windows
based system. Suppose also that I can load the DLL
dynamically and find out whether all the expected function
names are really exported by the DLL, i.e. if an
IEEE-488 interface WERE really connected to the pc I would be
in full control of it.
What actions (DLL-calls) would you suggest for a good test of
the presence of an IEEE-488 interface and it's basic
functionality? The test should NOT involve any communication
to instruments on the bus. Its just to find out whether an
interface is available and if it can be expected to be in
working condition.
Best regards and TIA
Ulrich Bangert
www.ulrich-bangert.de
Ortholzer Weg 1
27243 Gross Ippener
Germany
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.
Hi, Ulrich --
I only support the GPIB0 device name in my package, so it's easy enough in
my case to do an ibfind("GPIB0"). If that returns >= 0 (and the ERR flag is
not set in the returned value), then I do an ibonl(GPIB0,0) to close the
handle, and assume that a valid National Instruments interface is present.
If you wanted to support other device names, you'd need to repeat that
procedure for all of them, I imagine.
-- john, KE5FX
-----Original Message-----
From: time-nuts-bounces@febo.com [mailto:time-nuts-bounces@febo.com]On
Behalf Of Ulrich Bangert
Sent: Saturday, October 06, 2007 5:23 AM
To: Time nuts
Subject: [time-nuts] OT: Test for NI IEEE-488 interface
); SAEximRunCond expanded to false
Errors-To: time-nuts-bounces+jmiles=pop.net@febo.com RETRY
Gentlemen,
I know this is a bit OT but otherwise I also know that some of you are
well acquainted to IEEE-488 data acqusition:
Ulrich,
Any possibility to get an English version of your "Über die Stabilität von Oszillatoren und Frequenznormalen" article?
Regards, José, EA1PX
----- Original Message -----
From: "Ulrich Bangert" df6jb@ulrich-bangert.de
To: "Time nuts" time-nuts@febo.com
Sent: Saturday, October 06, 2007 2:22 PM
Subject: [time-nuts] OT: Test for NI IEEE-488 interface
Gentlemen,
I know this is a bit OT but otherwise I also know that some of you are
well acquainted to IEEE-488 data acqusition:
Suppose I can test whether the National Instruments DLL for their range
of IEEE-488 interfaces is available on a Windows based system. Suppose
also that I can load the DLL dynamically and find out whether all the
expected function names are really exported by the DLL, i.e. if an
IEEE-488 interface WERE really connected to the pc I would be in full
control of it.
What actions (DLL-calls) would you suggest for a good test of the
presence of an IEEE-488 interface and it's basic functionality? The test
should NOT involve any communication to instruments on the bus. Its just
to find out whether an interface is available and if it can be expected
to be in working condition.
Best regards and TIA
Ulrich Bangert
www.ulrich-bangert.de
Ortholzer Weg 1
27243 Gross Ippener
Germany
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.
__________ Información de NOD32, revisión 2575 (20071006) __________
Este mensaje ha sido analizado con NOD32 antivirus system
http://www.nod32.com
Hi Ulrich,
I'll be glad to. It's here, somewhere :-)
Didier
-----Original Message-----
From: time-nuts-bounces@febo.com
[mailto:time-nuts-bounces@febo.com] On Behalf Of Ulrich Bangert
Sent: Saturday, October 06, 2007 11:18 AM
To: 'Discussion of precise time and frequency measurement'
Subject: Re: [time-nuts] OT: Test for NI IEEE-488 interface
Didier,
I do not have a plug-in NI card (I do have a USB type
controller from
NI
though) so I am not sure what I am going to say will work, but it's
worth a try.
I am not sure by 100%, just say 99 % but I believe that the
DLL installed with ALL NI IEEE-488 interfaces is pretty much
the same regardless of the type of interface and that the
handling of different interfaces is managed completely INSIDE
the DLL itself. That is why I am hoping to find a suitable
test for ALL NI interfaces and your suggestions are well
worth trying. I have currently a PCI-interface available to
make some experiments with and would like to send you some
tests for your USB based interface ASAP in case you are
willing to help me with that.
73 and my best regards
Ulrich
Jose,
I am sorry to say that I do not have the time to translate it myself.
Perhaaps later but I am currently very busy with a lot of other things.
73 and my best regards
Ulrich, DF6JB
-----Ursprüngliche Nachricht-----
Von: time-nuts-bounces@febo.com
[mailto:time-nuts-bounces@febo.com] Im Auftrag von Jose Manuel
Gesendet: Sonntag, 7. Oktober 2007 02:46
An: Discussion of precise time and frequency measurement
Betreff: Re: [time-nuts] OT: Test for NI IEEE-488 interface
); SAEximRunCond expanded to false
Errors-To: time-nuts-bounces+df6jb=rich-bangert.de@febo.com RETRY
Ulrich,
Any possibility to get an English version of your "Über die
Stabilität von Oszillatoren und Frequenznormalen" article?
Regards, José, EA1PX
----- Original Message -----
From: "Ulrich Bangert" df6jb@ulrich-bangert.de
To: "Time nuts" time-nuts@febo.com
Sent: Saturday, October 06, 2007 2:22 PM
Subject: [time-nuts] OT: Test for NI IEEE-488 interface
Gentlemen,
I know this is a bit OT but otherwise I also know that some
of you are
well acquainted to IEEE-488 data acqusition:
Suppose I can test whether the National Instruments DLL for their
range of IEEE-488 interfaces is available on a Windows
based system.
Suppose also that I can load the DLL dynamically and find
out whether
all the expected function names are really exported by the
DLL, i.e.
if an IEEE-488 interface WERE really connected to the pc I
would be in
full control of it.
What actions (DLL-calls) would you suggest for a good test of the
presence of an IEEE-488 interface and it's basic functionality? The
test should NOT involve any communication to instruments on
the bus.
Its just to find out whether an interface is available and
if it can
be expected to be in working condition.
Best regards and TIA
Ulrich Bangert
www.ulrich-bangert.de
Ortholzer Weg 1
27243 Gross Ippener
Germany
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.
__________ Información de NOD32, revisión 2575 (20071006) __________
Este mensaje ha sido analizado con NOD32 antivirus system
http://www.nod32.com
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.
John,
you are saying that the first device detected by the dll is always named
"GPIB0"? That would make life easy.
73s and my best regards
Ulrich
-----Ursprungliche Nachricht-----
Von: time-nuts-bounces@febo.com
[mailto:time-nuts-bounces@febo.com] Im Auftrag von John Miles
Gesendet: Samstag, 6. Oktober 2007 20:27
An: Discussion of precise time and frequency measurement
Betreff: Re: [time-nuts] OT: Test for NI IEEE-488 interface
); SAEximRunCond expanded to false
Errors-To: time-nuts-bounces+df6jb=ulrich-bangert.de@febo.com RETRY
Hi, Ulrich --
I only support the GPIB0 device name in my package, so it's
easy enough in my case to do an ibfind("GPIB0"). If that
returns >= 0 (and the ERR flag is not set in the returned
value), then I do an ibonl(GPIB0,0) to close the handle, and
assume that a valid National Instruments interface is present.
If you wanted to support other device names, you'd need to
repeat that procedure for all of them, I imagine.
-- john, KE5FX
-----Original Message-----
From: time-nuts-bounces@febo.com
[mailto:time-nuts-bounces@febo.com]On
Behalf Of Ulrich
Bangert
Sent: Saturday, October 06, 2007 5:23 AM
To: Time nuts
Subject: [time-nuts] OT: Test for NI IEEE-488 interface
); SAEximRunCond expanded to false
Errors-To: time-nuts-bounces+jmiles=pop.net@febo.com RETRY
Gentlemen,
I know this is a bit OT but otherwise I also know that some
of you are
well acquainted to IEEE-488 data acqusition:
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.
It's up to the user, via the NI 488.2 configuration utility. They can set
the board to be GPIB1 or (presumably) many other values. My software only
talks to GPIB0, and the only time this has been a problem is with some
GPIB-ENET installations, where the interface has defaulted to GPIB1 for some
reason.
A better technique would be to call ibfind() for all possible GPIBxx
devices, keeping track of which one(s) are valid. Offhand I don't know if
there's an enumeration function for device identifiers.
-- john, KE5FX
-----Original Message-----
From: time-nuts-bounces@febo.com [mailto:time-nuts-bounces@febo.com]On
Behalf Of Ulrich Bangert
Sent: Sunday, October 07, 2007 2:05 AM
To: 'Discussion of precise time and frequency measurement'
Subject: Re: [time-nuts] OT: Test for NI IEEE-488 interface
); SAEximRunCond expanded to false
Errors-To: time-nuts-bounces+jmiles=pop.net@febo.com RETRY
John,
you are saying that the first device detected by the dll is always named
"GPIB0"? That would make life easy.
73s and my best regards
Ulrich
-----Ursprungliche Nachricht-----
Von: time-nuts-bounces@febo.com
[mailto:time-nuts-bounces@febo.com] Im Auftrag von John Miles
Gesendet: Samstag, 6. Oktober 2007 20:27
An: Discussion of precise time and frequency measurement
Betreff: Re: [time-nuts] OT: Test for NI IEEE-488 interface
); SAEximRunCond expanded to false
Errors-To: time-nuts-bounces+df6jb=ulrich-bangert.de@febo.com RETRY
Hi, Ulrich --
I only support the GPIB0 device name in my package, so it's
easy enough in my case to do an ibfind("GPIB0"). If that
returns >= 0 (and the ERR flag is not set in the returned
value), then I do an ibonl(GPIB0,0) to close the handle, and
assume that a valid National Instruments interface is present.
If you wanted to support other device names, you'd need to
repeat that procedure for all of them, I imagine.
-- john, KE5FX
-----Original Message-----
From: time-nuts-bounces@febo.com
[mailto:time-nuts-bounces@febo.com]On
Behalf Of Ulrich
Bangert
Sent: Saturday, October 06, 2007 5:23 AM
To: Time nuts
Subject: [time-nuts] OT: Test for NI IEEE-488 interface
); SAEximRunCond expanded to false
Errors-To: time-nuts-bounces+jmiles=pop.net@febo.com RETRY
Gentlemen,
I know this is a bit OT but otherwise I also know that some
of you are
well acquainted to IEEE-488 data acqusition:
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.