Re: GPIB 'Multidevice' API timeout
- From: joseph2k <quiettechblue@xxxxxxxxx>
- Date: Mon, 05 Mar 2007 11:48:42 GMT
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
.
- Follow-Ups:
- Re: GPIB 'Multidevice' API timeout
- From: Peter Nyffeler
- Re: GPIB 'Multidevice' API timeout
- From: Nitro
- Re: GPIB 'Multidevice' API timeout
- Prev by Date: Re: Is a MOSFET really a good current source???
- Next by Date: Re: *Tricky* current measurement.
- Previous by thread: Why reset ,generally used is neg edge
- Next by thread: Re: GPIB 'Multidevice' API timeout
- Index(es):
Relevant Pages
|
