Re: GPIB 'Multidevice' API timeout
- From: "Nitro" <nitro-57@xxxxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 06 Mar 2007 00:30:47 -0500 (EST)
On Mon, 05 Mar 2007 11:48:42 GMT, joseph2k wrote:
PaulH wrote:
I'm using the GPIB 'multidevice' API for a project, but I find that
the default command timeout is much too long to wait. Typically, using
the 'traditional' API, I would set the timeout using the ibdev()
command when I first initialize the GPIB device. But, since I'm using
this 'multidevice' API, that isn't an option.
Does anybody know a GPIB command other than ibdev() that sets the bus
timeout?
Thanks,
PaulH
Unless i mistaken that is a driver function, not a proper bus property. But
it has been 20 years, do you have a current ieee-488 spec you can lend me?
--
JosephKK
Gegen dummheit kampfen die Gotter Selbst, vergebens. Â
--Schiller
Hi, Just adding my concurrance. ibtimo() and ibdev() are typically National
Instruments driver API calls. ibtimo() is used for an open device using an
existing device handle. ( ibdev() is to open a device and you can set the
initial values.)
Remember the timeout value is an index not the acutal timeout. They have
defines for the times (T10, T30 etc).
What is the underlying driver that the 'multidevice API' is using?
Bart
.
- Follow-Ups:
- Re: GPIB 'Multidevice' API timeout
- From: joseph2k
- Re: GPIB 'Multidevice' API timeout
- References:
- Re: GPIB 'Multidevice' API timeout
- From: joseph2k
- Re: GPIB 'Multidevice' API timeout
- Prev by Date: Re: LISN
- Next by Date: Which adder to choose?
- Previous by thread: Re: GPIB 'Multidevice' API timeout
- Next by thread: Re: GPIB 'Multidevice' API timeout
- Index(es):
Relevant Pages
|
