Re: Fwd: Fwd: Agilent 82350b can't recover from read timeout?
Dirk Niggemann <[email protected]>
| Newsgroups | gmane.linux.hardware.gpib.general |
|---|---|
| Message-ID | <CAKrfojjBnUTw2_C-L28zY-GKG5N9vaahDvtD=H+gBuHLaRYJxw@mail.gmail.com> |
Hi Frank, Yes, disabling TCS works perfectly, as you suggested. Do you think that's the correct fix for this? Or should we aim for something like a read of DIR register just before every TCA? Regards, Dirk On Thu, Aug 1, 2019 at 3:41 AM Frank Mori Hess <[email protected]> wrote: > On Wed, Jul 31, 2019 at 8:08 PM Dirk Niggemann <[email protected]> > wrote: > > I thought the issue was directly related to the particular device > because i originally triggered the issue by sending an invalid command to > the board. > > You don't actually need to send anything- just reading from the device > without sending anything is sufficient, > > > > Yeah, attempting a read that fails will leave the board out of the > ANRS state, causing tcs to fail. Try modifying tms9914_aux.c by > changing tms9914_take_control so that it immediately returns > -ETIMEDOUT if "synchronous" is true. So basically, you want to make > sure it never writes AUX_TCS to the AUXCR register. > > > _______________________________________________ > 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