Re: Agilent 82357B repeatable hard failure

Hi Dave, Everyone,

The loop reading the status and checking for ATN in 
agilent_82357a_take_control
was helpful in finding the problems with the ADSR but maybe it isn't 
needed anymore.
I did a couple tests.  I tried setting timeout to 1 to check that ATN is 
there on the first read.
Then I took out the loop and the timeout check.  I ran the 
hp3478_read_calibration script
in a loop for a few minutes.  It works.

I checked the times for a hp3478_read_calibration run and removing the check
for the ATN reduced the time from 7.6 seconds to 7.3 seconds.

JIm

On 9/30/23 04:03, dave penkler wrote:
>
> Hi Jim,
>
> On Fri, 29 Sept 2023 at 14:46, Jim Houston <[email protected]> wrote:
>
>     Hi Dave,
>
>     Thanks again for all of your efforts in debugging this problem.  I
>     have
>     enjoyed working with you.
>
>
> I enjoyed working with you on this. Your logic analyser trace at the 
> interface level  of the 9914 IC was a huge help.
>
>     I like setting ATN from the end of the read function.  I think this
>     works well for
>     the normal case where we send a query and get a reply.
>     I would avoid duplicating code and call the
>     agilent_82357_take_control
>     function.
>
>
> OK,  I had done an in-line write to the auxiliary command register to 
> avoid the reading of the status byte in the timeout loop. But it can't 
> hurt so I'll go with your suggestion.
>
>     I see a balance between  the chance that setting ATN might break
>     something against
>     knowing that having a  correct ibsta() value will fix something.
>
> Agreed.
>
>     Jim Houston
>
> -Dave

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