Re: Agilent 82357B repeatable hard failure

Hi Dave,Everyone

I ran the onebyte2 test against both the SVN kernel and the patched kernel
the output follows.  I'm getting failures on IBEOS ioctl.  I'm still 
looking at
this and I may send another email if I figure it out.  I did a fresh 
install and
I may have broken something in the process.

JIm Houston

Test with current SVN kernel:

jhouston@gpib-test2:~/onebyte$ ./onebyte2 -d 22 s
   0x0168 ibwrt
+ 0x0138 ibrd dev
libgpib: IBEOS ioctl failed
0 0x0130 ibrd board
libgpib: IBEOS ioctl failed
0 0x0130 ibrd board
libgpib: IBEOS ioctl failed
. 0x013c ibrd board
libgpib: IBEOS ioctl failed
0 0x0130 ibrd board
libgpib: IBEOS ioctl failed
0 0x0130 ibrd board
libgpib: IBEOS ioctl failed
0 0x0130 ibrd board
libgpib: IBEOS ioctl failed
9 0x0130 ibrd board
libgpib: IBEOS ioctl failed
E 0x01a4 ibrd board
libgpib: IBEOS ioctl failed
- 0x0134 ibrd board
libgpib: IBEOS ioctl failed
3 0x0138 ibrd board
libgpib: IBEOS ioctl failed
  0x0124 ibrd board
libgpib: IBEOS ioctl failed

  0x2128 ibrd board
jhouston@gpib-test2:~/onebyte$

With patched kernel:

jhouston@gpib-test2:~/onebyte$ ./onebyte2 -d 22 s
   0x0128 ibwrt
0 0x0174 ibrd dev
libgpib: IBEOS ioctl failed
. 0x0174 ibrd board
libgpib: IBEOS ioctl failed
0 0x0174 ibrd board
libgpib: IBEOS ioctl failed
0 0x0174 ibrd board
libgpib: IBEOS ioctl failed
0 0x0174 ibrd board
libgpib: IBEOS ioctl failed
7 0x0174 ibrd board
libgpib: IBEOS ioctl failed
E 0x0174 ibrd board
libgpib: IBEOS ioctl failed
- 0x0174 ibrd board
libgpib: IBEOS ioctl failed
3 0x0174 ibrd board
libgpib: IBEOS ioctl failed
  0x0174 ibrd board
libgpib: IBEOS ioctl failed

  0x2174 ibrd board
jhouston@gpib-test2:~/onebyte$


On 9/28/23 13:13, dave penkler wrote:
> Hi Jim,
> Please find attached a new version of onebyte to check that board 
> level reads work after setting ATN at the end of the read.
> The attached patch for the driver is against the current SVN and sets 
> ATN at the end of the read as you proposed.
> @MichaelK you might try this one on the R&S power meter.
> It worked on my Beiming clone:
> In the ibsta 0x174 = CMPL | REM | CIC | ATN | LACS  we see the ATN bit 
> set.
> $ onebyte2 -d8
>   0x0168 ibwrt
> H 0x0174 ibrd dev
> E 0x0174 ibrd board
> W 0x0174 ibrd board
> L 0x0174 ibrd board
> E 0x0174 ibrd board
> T 0x0174 ibrd board
> T 0x0174 ibrd board
> - 0x0174 ibrd board
> P 0x0174 ibrd board
> A 0x0174 ibrd board
> C 0x0174 ibrd board
> K 0x0174 ibrd board
> A 0x0174 ibrd board
> R 0x0174 ibrd board
> D 0x0174 ibrd board
> , 0x0174 ibrd board
> E 0x0174 ibrd board
> 3 0x0174 ibrd board
> 6 0x0174 ibrd board
> 3 0x0174 ibrd board
> 1 0x0174 ibrd board
> A 0x0174 ibrd board
> , 0x0174 ibrd board
> 0 0x0174 ibrd board
> , 0x0174 ibrd board
> 2 0x0174 ibrd board
> . 0x0174 ibrd board
> 1 0x0174 ibrd board
> - 0x0174 ibrd board
> 5 0x0174 ibrd board
> . 0x0174 ibrd board
> 0 0x0174 ibrd board
> - 0x0174 ibrd board
> 1 0x0174 ibrd board
> . 0x0174 ibrd board
> 0 0x0174 ibrd board
>
>  0x2174 ibrd board
> Cheers,
> -Dave
>
>
> On Thu, 28 Sept 2023 at 17:59, dave penkler <[email protected]> wrote:
>
>     Hi Jim,
>     Can you please let us know if the removal of TCS in the SVN works
>     for your reading of the calibration data.
>     I have thought some more about your proposal to set ATN at the end
>     of the read. We just need to verify that board level reads after
>     the first device level read still work with the ATN workaround.
>     If it does that would give us a reliable board level ibsta, From
>     the logic analyser traces it looks like the board gives valid ADSR
>     responses when it is in the Talker Active state i.e. after ibwrt.
>     -Dave
>

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