> ------ Original Message ------
> From: scott@...
> To: [email protected]
> Sent: Tuesday, September 17th 2024, 01:26 PM
> Subject: Re: [HP-Agilent-Keysight-equipment] HP 5245L: unknown chassis capacitor
?

Thanks to all for the input.

Sure enough, my 5245L has "H96" on the back, and there is a little sticker above the AC input that says "50-400 Hz", covering up the chassis stenciling which surely said "50-60 Hz".

There are two solid red wires from one capacitor terminal; one goes to S4 on the back panel (120/240 VAC selector switch) and the other goes to the fan.

Sounds to me like if I don't intend on using this in an airplane, I can eliminate the capacitor and run a single red wire from the fan to S4...agree?

?

It *should* compile on Debian using autotools. ...see the github page on
the commands to do this.

|$ ./autogen.sh $ cd build/ $ ../configure $ make all $ sudo make install|

I'll check the build later on a RPi (Debian..ish). I have had issues
with other software I've written where the GTK library versions on
Debian are a year or more behind Fedora.
I'll probably try and do a flatpak (which will run on any distro) but
I'm not sure I can do this given it links to the GPIB driver that is a
kernel module (and probably cannot be a flatpak).
Michael

?

Do you have a simple example at hand? I used the Prologix adapter in the past with KE5FX toolbox but never with pyvisa. I prefer to use Python as I want more data processing options than available with the kit.

Hi again.

The BIG advantage of a Prologix adapter (or clone) is that for simple tasks, it will work with anything that recognises it as a "Serial Device", and dumb terminal program.

One with programmable macro's is most useful though, it's amazing what you can do with that sort of program!
Such as? for Windows, or...
CuteCom for Linux.

It is OS agnostic (no custom drivers needed) and can work as a device, as well as a controller.

So you could configure it as a "listen only" device, then you have a crude bus monitor tool, for when you have something weird going on between some other software and instrument.? It won't show you the handshake sequence, but will present you with all the data bytes flying up/down the bus.

Hint, the later devices have some EAROM built in, so you can save it's configuration.? That almost gives you a Plug-n-Play bus monitor if you need, just fire up a simple ASCII terminal emulator, that can show valid representations of the usual ASCII control characters.)

OK, it takes a bit of effort to decipher it, but it's better than nothing, if you've not got a built in diagnostic/analyser tool for your main GPIB interface, such as the National Instrument supplied tools, "Ni IO Trace" etc (used to be called Ni-Spy) that come with their interface software.? I do not know what HPAK supply that is equivalent.

If I were you, I'd hang onto it, as it is still a useful tool in its own right, even if? you usually use one of the big name devices for the main tasks..?? Add a small single board computer (Raspberry Pi, or others) and configure it as a "Device", and you have the beginnings of a custom GPIB device, for "Whatever" needs.

All the best.

Dave KBV.

PS:??? There was a "lot of noise" a while back, about weather or not to add the ability to use Prologix adapters to PyVisa.? I have no idea if that ever happened, but I do remember a lot of people not liking that idea for some reason.

?

Hi all,

Thanks to Milan's pointer I de-soldered the two electrolytic capacitors on the little PSU daughter board and they were faulty.

The 47uF@C5 was only 22uF and the 33uF@C6 thinks its a 100ohm resistor!?

Pic of board below before I de-soldered C6.

thanks to all for suggestions.

regards

Tim