Hello,

Is this working with the 82357, it would be a great starting point. Although I just don’t understand why interactive IO doesn’t work.?

Has anyone experienced differences between interactive IO and using the libraries - I guess interactive IO just is an interface to the libs?

My best bet right now is that REN should be controlled (pulled inactive) for reading data from the 436. I just don’t know how to test this with the 82357/VISA libraries.?

Regards,

?Staffan

On Monday, November 19, 2018, Daun Yeagley <daun@...> wrote:

Hi Staffan

The physical layer for IEE-488 itself is essentially unchanged from the original.? 488.2 deals more with the messaging protocol.
This is where all the "universal" commands originated (all the * commands like *IDN?, etc.).
If you saw my PM to you a bit ago, you saw an example of a "non-488.2" communication using the Agilent IO libraries.? In other words, those nifty commands are not available to the old "R2D2" command structure instruments.? I guess I'll include that listing here, for others to see as well.? This code sets up and gets readings from an HP3478A voltmeter, which is pre-488.2 (R2D2 "language")

Daun

Daun E. Yeagley II, N8ASB

On 11/19/2018 4:01 PM, Staffan wrote:

Hello,

Many thanks. Notice that I replied to your direct mail. I don't think the problem lies in the 436, but rather in how the USB dongle 82357 performs communication. Don't know if the GPIB standard was updated - 488.2 seems to be from 1992, whereas the instrument predates 1980. It would be great to have a configuration within VISA to support different standards for different instruments - or is this perhaps not needed? Sounds strange that there shouldn't be sufficient backwards compatibility for a data bus!

Regards,
? Staffan