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

Yes, that works too.

That leaves the question of why there is a byte to read when nothing was
sent?

Regards,

Dirk

On Tue, Jul 30, 2019 at 3:51 AM Frank Mori Hess <[email protected]> wrote:

> On Mon, Jul 29, 2019 at 3:08 PM Dirk Niggemann <[email protected]>
> wrote:
> > I'd traced it down to ibcac (in sys/ibcac.c) and
> tms9914_take_control()  in tms9914_aux.c myself- it skips the TCS because
> the board is not addressed to listen and goes straight to the TCA which
> fails with ATN unasserted.
> >
> > The weird thing is i managed to unwedge the TCA by sending  write_byte(
> priv, AUX_RHDF, AUXCR );  just before it- (in a misunderstanding of how
> holdoffs in read actually work, I think).
> >
>
> I wonder if it gets gummed up due to an unread byte in the data in
> register.  if you do a "read_byte( priv, DIR )" instead of the release
> data holdoff, does it also make the take control async work?
>
>
> _______________________________________________
> 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