Fwd: Fwd: Agilent 82350b can't recover from read timeout?

H Frank,

I checked the value returned from the DIR register and it's almost always
0xa so the last byte sent on the previously successful read. Or 0 if we
never read anything.

I am already testing with the _unaccel driver because i wanted to make sure
this wasn't a side effect of using the FIFOs- sorry, I should have
mentioned that.

Regards,

Dirk

On Wed, Jul 31, 2019 at 5:41 PM Frank Mori Hess <[email protected]> wrote:

> On Tue, Jul 30, 2019 at 4:14 AM Dirk Niggemann <[email protected]>
> wrote:
> >
> > Yes, that works too.
> >
> > That leaves the question of why there is a byte to read when nothing was
> sent?
> >
>
> Oh, maybe there isn't a byte.  Reading the DIR register tickles the
> data holdoff logic, so maybe that could cause it.  Another thing you
> could try is using "agilent_82350b_unaccel" as the board type, to take
> the fifos out of the picture.  Then the driver will only use the
> tms9914 directly.
>
>
> _______________________________________________
> Linux-gpib-general mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/linux-gpib-general
>

_______________________________________________
Linux-gpib-general mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/linux-gpib-general