Agilent 82350b can't recover from read timeout?

Hi,

I have a strange difference in behaviour between the Agilent 82357a and the
Agilent 82350b cards in linux-gpib-4.2.0 running on ubuntu 16.04 on a
32-bit kernel  4.4.0-157-generic.

Sending an invalid command ('ID' instead of '*IDN?') to a specific device
(HP7673 on ID 8) results in a bus lockup. On the 82357a this can be cleared
using ibclr() but on the 82350b the lockup can only be cleared by
reinitialising the board with gpib_config.

Any other command aborts immediately with iberr set to 14  EBUS until the
board is reinitialised.

The EBUS error is directly translated ETIMEDOUT error from the ibcmd ioctl,

This error occurs immediately, even if the timeout is set to 10s, so it's
almost like the timer can't  successfully restart after a timeout.

I can't figure why nothing clears this error on the 82350b.

The weird thing is that the same board works OK in win7 using the Keysight
VISA drivers, so it's not an inherent problem with the 82350 board.

The problem is definitely timer related because any read timeout triggers
the same behaviour. You don't actually need to write invalid data, just
triggering any read timeout causes the problem.

Regards,

Dirk

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