Re: GPIB 'Multidevice' API timeout



In article <usTGh.5157$M65.542@xxxxxxxxxxxxxxxxxxxxxxxxxx>, joseph2k <quiettechblue@xxxxxxxxx> 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?

Use the ibtmo command.
Note: Have a look at the lookup table in the manual to get the desired timeout
value.
.



Relevant Pages

  • Re: GPIB Multidevice API timeout
    ... the default command timeout is much too long to wait. ... this 'multidevice' API, that isn't an option. ... Does anybody know a GPIB command other than ibdev() that sets the bus ...
    (sci.electronics.design)
  • Re: Really need help on this one
    ... Is there a way to read the output of a particular command into ... Heres a better example using ssh. ... set timeout $timeout ... exec kill -9 $pid ...
    (comp.lang.tcl)
  • GPIB Multidevice API timeout
    ... the default command timeout is much too long to wait. ... the 'traditional' API, I would set the timeout using the ibdev ... command when I first initialize the GPIB device. ...
    (sci.electronics.design)
  • Re: GPIB Multidevice API timeout
    ... the default command timeout is much too long to wait. ... this 'multidevice' API, that isn't an option. ... Does anybody know a GPIB command other than ibdev() that sets the bus ...
    (sci.electronics.design)
  • Re: GPIB Multidevice API timeout
    ... the default command timeout is much too long to wait. ... this 'multidevice' API, that isn't an option. ... Does anybody know a GPIB command other than ibdev() that sets the bus ...
    (sci.electronics.design)