Keysight's new 34465A (6.5 digit) and 34470A (7.5 digit) bench multimeters

[plesa]

I have LabView program for 50k/s digitizing with 34411A, so let me know if it can help.

[Sparky]

I have LabView program for 50k/s digitizing with 34411A, so let me know if it can help.

@plesa: It would be great to try it with 34465A/34470A, and see if allows 50kHz digitizing also.  That way we would have a better idea of possible limitations in BenchVue and not with the instrument. 

Does your test program require full LabView installation, or can it run "stand alone" as an application?  I'm happy to test it

Sparky

[plesa]

I build exe, so it is standalone app.
It creates live view, log data to HDD and create live histogram.
For fast readout do not forget uncheck autozero.
http://www.filedropper.com/agilentdmmloggingutility

[Sparky]

I build exe, so it is standalone app.
It creates live view, log data to HDD and create live histogram.
For fast readout do not forget uncheck autozero.

@plesa: I tried your program but I get the error shown in attachment when I run it.  Do you know what it is?  Anything I can provide to help identify the problem?

(There was a second error about the directory C:\temp but that was easily resolved by creating the required directory).

[plesa]

I build exe, so it is standalone app.
It creates live view, log data to HDD and create live histogram.
For fast readout do not forget uncheck autozero.

@plesa: I tried your program but I get the error shown in attachment when I run it.  Do you know what it is?  Anything I can provide to help identify the problem?

(There was a second error about the directory C:\temp but that was easily resolved by creating the required directory).

Error should be fixed.
Try
http://www.filedropper.com/loggerwithhistogram

[ansgar96]

Hey,

I get this problem when my 34465A is connected to my home-network via LAN. Does anyone else have also problems like this or does someone know whats the problem? LAN settings are the default settings.

[HighVoltage]

There used to be a problem with agilentlxiwebservice.exe in an older FW
You can find it in a release notes:

#4650  When mDNS is disabled with no LAN connection, AgilentLxiWebService.exe dies.

But I never had this problem.

[ansgar96]

Hey,

Forgot to mention, I have the new 2.11 Firmware installed :/

Best regards

[Sparky]

Error should be fixed.
Try <snip>

I cannot download from the new link.  Apparently the download does work after getting through the capcha...  I didn't get a chance to re-test as moving my lab equipment...

[bson]

Is this a know bug?

Minimum is 10.00000 yet the "Autoscale Once" function places the entire trend graph below 10...
The statistical average positively doesn't match the plot.

Plot is set to show all points.

34465A, firmware is 02.08 and I'm wondering if updating is known to fix this...

[LA7SJA]

I can't replicate this on my 34461A running 2.11 but here is the changelog for 2.11 (#2 could be of interest)


34460A/34461A/34465A/34470A Revision 2.11 Enhancements and Fixes
1. Resolved an issue which caused capacitance measurements to intermittently fail with high offset voltages present.
2. Removed/resolved a 3 ppm reading shift that occurred in DCV measurements on the 100V and 1000V ranges when Input Z (impedance) is switched between 10M and Auto.
3. Resolved a Windows Application Error that occurred when LAN service VXI-11 was disabled and power is cycled.
4. Resolved a lock-up condition that occurred during frequency measurements using trigger settings TRIGger:DELay MIN and *TRG.

Firmware, release notes and tools:
http://www.keysight.com/main/software.jspx?ckey=2367633&lc=eng&cc=TH&nid=-536902435.1058513&id=2367633

Johan-Fredrik

[Dr. Frank]

This bug should have been fixed with 2.08 already:

34460A/34461A Revision 2.08 Enhancements and Fixes
..
4. Resolved a trend chart scaling defect in which readings would incorrectly appear outside of the vertical scale limits.

The 2.11 fix #2 is not related to the trend chart display, and only shows up in the 100V and 1kV DC ranges.
It's a real measurement fault, which can be displayed in the trend chart as a 3ppm step up/down, each time one toggles the Impedance switch.

Therefore I recommend to upgrade to 2.11, also to make sure, that any known scaling errors are removed.

Frank

PS: Another ~ 10ppm error in the 100V and 1kV DCV range has been found, due to erratic setting of the divider heater.
This has been confirmed by Keysight and is currently under investigation for FW correction.

I hope, that this is also the root cause for the ~ +10ppm ACAL error in these ranges.
 

[HighVoltage]

34465A, firmware is 02.08 and I'm wondering if updating is known to fix this...

I can also confirm, that this is not a problem anymore in the latest firmware.
This was really troubling me in my first 34461A and I am glad it was solved.
 
Edit:
Added picture of a trendchart from a 10V reference

[bson]

02.11 looks much better!  But maybe still not quite perfect...



The average is 10.000022 but assuming the Y axis labels are 10.00000, 10.00010, 10.00019 then the graph is too high.  It shows points at 10.000040 and higher, which is above the max value recorded.  This is the case even if the bottom tick is actually at 9.99999 - but then we have TWO errors instead of one...

[Dr. Frank]

02.11 looks much better!  But maybe still not quite perfect...



The average is 10.000022 but assuming the Y axis labels are 10.00000, 10.00010, 10.00019 then the graph is too high.  It shows points at 10.000040 and higher, which is above the max value recorded.  This is the case even if the bottom tick is actually at 9.99999 - but then we have TWO errors instead of one...

Well, the problem is, that the graphs scale has 5 digits of resolution only.

So your assumption is very probably wrong. The scaling is 10.00000, 10.00005, 10.00010.
10.00019 as an upper limit would have been rounded to 10.0002, instead.

I recommend to manually scale the y-axis, so you will have better control of the limits.

Frank

Btw.: Received FW 2.12 today. Problem fixed, but not yet the ACAL issue.

[Dr. Frank]

If you open the Vertical Scale menu, then Low = 10.000 0 V, High = 10.000 1 V, that's a 100µV span only. See first two screenshots.
It's not possible to manually choose a higher resolution, because number entry is also limited to 6 digits, for 10V, that's 5 decimal places only.

So there's no error with your instrument, obviously.

At 9.999 98 V input voltage, you will get higher resolution, and might specify Center = 9.999 98V, Span = 10.0000µV

PS: Or even more resolution, i.e. 1 tick = 250nV (Center = 9.999 99V), recorded at NPLC 100.
You can even distinguish the A/D's resolution of 100nV (1E-8).
It's also a '465A.

Frank

[TheSteve]

Btw.: Received FW 2.12 today. Problem fixed, but not yet the ACAL issue.

It's nice to see they can be very reactive to the bugs that you find. Please do the 34461A owners a favor and ask them to fix the continuity bug.

[bson]

The scaling is 10.00000, 10.00005, 10.00010.

Ah, yes, 10.00005 could have been rounded to 10.0001 and this in fact very likely the case.

It would be nice if they'd add another digit, which should fit easily.

[sotos]

Btw.: Received FW 2.12 today. Problem fixed, but not yet the ACAL issue.

It's nice to see they can be very reactive to the bugs that you find. Please do the 34461A owners a favor and ask them to fix the continuity bug.

 

[rosbuitre]

Btw.: Received FW 2.12 today. Problem fixed, but not yet the ACAL issue.

It's nice to see they can be very reactive to the bugs that you find. Please do the 34461A owners a favor and ask them to fix the continuity bug.

 

We do not appear in the web   

[sotos]

Btw.: Received FW 2.12 today. Problem fixed, but not yet the ACAL issue.

It's nice to see they can be very reactive to the bugs that you find. Please do the 34461A owners a favor and ask them to fix the continuity bug.

We do not appear in the web   

Here we are.

http://www.keysight.com/owc_discussions/thread.jspa?threadID=40301&tstart=0

And here

https://www.eevblog.com/forum/testgear/34461a-problem-after-updating-to-firmware-a_02_09-behavior-in-continuity-test/

[rosbuitre]

Btw.: Received FW 2.12 today. Problem fixed, but not yet the ACAL issue.

It's nice to see they can be very reactive to the bugs that you find. Please do the 34461A owners a favor and ask them to fix the continuity bug.

We do not appear in the web   

Here we are.

http://www.keysight.com/owc_discussions/thread.jspa?threadID=40301&tstart=0

And here

https://www.eevblog.com/forum/testgear/34461a-problem-after-updating-to-firmware-a_02_09-behavior-in-continuity-test/

I did not say well  , does not appear to download in Keysight web the new version of firmware (2.12)

Regards

[Dr. Frank]

It's nice to see they can be very reactive to the bugs that you find. Please do the 34461A owners a favor and ask them to fix the continuity bug.

Well, your wish is my command..

Jim Durr just confirmed, that they've already solved this known problem, and it will be on the next FW release.
Watch for the Keysight Technology Support site, he promised to post that information there, too.

Frank

[TheSteve]

It's nice to see they can be very reactive to the bugs that you find. Please do the 34461A owners a favor and ask them to fix the continuity bug.

Well, your wish is my command..

Jim Durr just confirmed, that they've already solved this known problem, and it will be on the next FW release.
Watch for the Keysight Technology Support site, he promised to post that information there, too.

Frank

Dr Frank to the rescue, thank you sir.

[Dr. Frank]

Dr Frank to the rescue, thank you sir.

Please, that's not my merit at all.. I just asked Jim Durr about this issue, and he told me that they already had solved it..

Anyhow, it will take some time for the official release, due to their strict Q.A. system, and PV process, i think