HP / Agilent 34401A hidden menu

[iMo]

I looked up thermistor data for 2.2k, 5k, and 10k type B thermistors (which is what I think HP supported). They all have the same beta value. HP got a little lazy with the 7-5-2 firmware as all they would have had to do is scale the ohm readings for the 5k thermistor temperature table to support 2.2k and 10k thermistors.

I know this is some heavy math , but here goes:

Table lookup OHMS = measured OHMS * 5 / thermistor TYPE KOHMS - a whopping one line of code!

in fact, source code wouldn't even have to add one line of code.  Instead of table_lookup=measured_ohms, they could have changed it to table_lookup=measured_ohms*5/thermistor_type_kohms.

IMHO they do consider the "beta" of the thermistors as well.
https://www.eevblog.com/forum/testgear/hp-agilent-34401a-hidden-menu/msg4659010/#msg4659010

[RolandK]

I just work at some 34401a. I can confirm that the commands
DIAG:POKE 28,0,1191 math menu -> min-max: enable sdev, pp
DIAG:POKE 30,0,1191 temp menu, scpi commands
DIAG:POKE 31,0,1191 menu -> scale, calc:scale
DIAG:POKE 32,0,1191 resolution menu -> custom aperture
DIAG:POKE 33,0,1191 system menu -> store state, recall state
DIAG:POKE 25,0,1      10mA AC range
work with revision 07-XX-XX to 11-XX-XX and are permanent (just use without the comments)

with revision 03-XX-XX to 06-XX-XX the 10mA AC range is permanent possible, too:
DIAG:POKE 25,0,1      10mA AC range

with revision 02-XX-XX the 10mA AC range is possible, but not permanent:
DIAG:POKE 25,0,1      10mA AC range

[Ocela]

 

[felixd]

Works a treat

I just work at some 34401a. I can confirm that the commands
DIAG:POKE 28,0,1191 math menu -> min-max: enable sdev, pp
DIAG:POKE 30,0,1191 temp menu, scpi commands
DIAG:POKE 31,0,1191 menu -> scale, calc:scale
DIAG:POKE 32,0,1191 resolution menu -> custom aperture
DIAG:POKE 33,0,1191 system menu -> store state, recall state
DIAG:POKE 25,0,1      10mA AC range
work with revision 07-XX-XX to 11-XX-XX and are permanent (just use without the comments)

with revision 03-XX-XX to 06-XX-XX the 10mA AC range is permanent possible, too:
DIAG:POKE 25,0,1      10mA AC range

with revision 02-XX-XX the 10mA AC range is possible, but not permanent:
DIAG:POKE 25,0,1      10mA AC range

[RolandK]

There must be something wrong with this 34401a:  - i do not mean the missing knobs for I/O and front/rear


I just connected a Rev1 display to an Agilent branded 34401a with firmware 11-05-02.
It behaved as expected - they didn't remove the firmware part for the elder Rev1 display

[wkb]

Probably the easiest solution. Also for repair / spare parts logistics.

[RolandK]

Next i will try to update the 34401a with Revision 02-01-01 to Revision 11-05-01.

I only fear, that i have to repeat the calibration.
First lets have a look how the calibration data looks on which revision and try to read them out or to read the eeprom.

[willinsau]

Would anyone be able to share the V11 firmware? It looks like the previous download link is no longer working.

The 07-05-02, 10-05-02, and 11-05-02 firmware binaries here contain the 9 STORE STATE, 10 RCL STATE, and 11 POWER ON menu strings. The 05-01-01 firmware binary does not.

https://xdevs.com/doc/HP_Agilent_Keysight/34401A/fw/
34401a_05-01-01-mcu_program.bin
34401a_07-05-02-mcu_program.bin
34401a_10-05-02-mcu_program.bin
34401a_11-05-02-mcu_program.bin

[squadchannel]

attached.
downloaded from xdevs 

[dimmog]

Would anyone be able to share the V11 firmware? It looks like the previous download link is no longer working.

The 07-05-02, 10-05-02, and 11-05-02 firmware binaries here contain the 9 STORE STATE, 10 RCL STATE, and 11 POWER ON menu strings. The 05-01-01 firmware binary does not.

https://xdevs.com/doc/HP_Agilent_Keysight/34401A/fw/
34401a_05-01-01-mcu_program.bin
34401a_07-05-02-mcu_program.bin
34401a_10-05-02-mcu_program.bin
34401a_11-05-02-mcu_program.bin

If you use Facebook https://www.facebook.com/groups/34401A/files/files

[willinsau]

Next i will try to update the 34401a with Revision 02-01-01 to Revision 11-05-01.

I only fear, that i have to repeat the calibration.
First lets have a look how the calibration data looks on which revision and try to read them out or to read the eeprom.

have you succeed? what's happing? need calibration?

[willinsau]

Thanks so much.
Succeed!

If you use Facebook https://www.facebook.com/groups/34401A/files/files
[/quote]

[willinsau]

attached.
downloaded from xdevs 

Thanks, 

[dimmog]

Thanks so much.
Succeed!

If you use Facebook https://www.facebook.com/groups/34401A/files/files

[/quote]

Please note that upgrading the firmware from any version below 07.05.02 to 11.05.02 will require a complete recalibration of the instrument.

[squadchannel]

Upgrading to 11-xx-xx requires some additional steps.

1) 06-xx-xx, the front panel VFD display controller has been changed.
Therefore, to upgrade from firmware versions prior to 06-xx-xx, you must replace the front panel board.
To verify that the board has been upgraded, the second two-digit section of the revision number must be 02 or higher. xx-02-xx or xx-03-xx. "01" indicates the early board.
06-xx-xx is the only revision that is compatible with both the early and late front panels.
that's not the case....

2) Upgrading to 11-xx-xx requires recalibration or modification of the calibration data.

Please note that upgrading the firmware from any version below 07.05.02 to 11.05.02 will require a complete recalibration of the instrument.

It was somewhere, but I can't find it.

[willinsau]

some confused. I'am now 07-05-02, update need recalibration?

[Hydron]

I don't believe so, but I'm not an expert. Not sure what the advantage of the upgrade would be though, v7 already has the hidden features if you want to activate them (first version with them). Is there a change log available?

[dimmog]

some confused. I'am now 07-05-02, update need recalibration?

If your unit is running firmware 07-05-02, upgrading to 11-05-02 does not require recalibration, as both versions use the same EEPROM calibration data structure.

[willinsau]

Thanks for your verificate.
The way are ALL WORKS

I just work at some 34401a. I can confirm that the commands
DIAG:POKE 28,0,1191 math menu -> min-max: enable sdev, pp
DIAG:POKE 30,0,1191 temp menu, scpi commands
DIAG:POKE 31,0,1191 menu -> scale, calc:scale
DIAG:POKE 32,0,1191 resolution menu -> custom aperture
DIAG:POKE 33,0,1191 system menu -> store state, recall state
DIAG:POKE 25,0,1      10mA AC range
work with revision 07-XX-XX to 11-XX-XX and are permanent (just use without the comments)

with revision 03-XX-XX to 06-XX-XX the 10mA AC range is permanent possible, too:
DIAG:POKE 25,0,1      10mA AC range

with revision 02-XX-XX the 10mA AC range is possible, but not permanent:
DIAG:POKE 25,0,1      10mA AC range

[jundar]

Just curious, for clarification purposes.
What FW version does your unit have?

Thanks for your verificate.
The way are ALL WORKS

I just work at some 34401a. I can confirm that the commands
DIAG:POKE 28,0,1191 math menu -> min-max: enable sdev, pp
DIAG:POKE 30,0,1191 temp menu, scpi commands
DIAG:POKE 31,0,1191 menu -> scale, calc:scale
DIAG:POKE 32,0,1191 resolution menu -> custom aperture
DIAG:POKE 33,0,1191 system menu -> store state, recall state
DIAG:POKE 25,0,1      10mA AC range
work with revision 07-XX-XX to 11-XX-XX and are permanent (just use without the comments)

with revision 03-XX-XX to 06-XX-XX the 10mA AC range is permanent possible, too:
DIAG:POKE 25,0,1      10mA AC range

with revision 02-XX-XX the 10mA AC range is possible, but not permanent:
DIAG:POKE 25,0,1      10mA AC range

[willinsau]

11-05-02 and 08-05-02