Today my Keysight 34470A arrived...
Same "axis numbering" problem on my brandnew 34465A:
2.5 , 2.5000 , 2.5001 - WTF?
Isn't there enough place for:
2.49995 , 2.50000 , 2.50005
Today my Keysight 34470A arrived...
Same "axis numbering" problem on my brandnew 34465A:
2.5 , 2.5000 , 2.5001 - WTF?
Isn't there enough place for:
2.49995 , 2.50000 , 2.50005
It's actually...
2.500 10
2.500 05
2.500 00
But, yeah. Agreed on the for rounding and truncating axis labels in the first place. You're not the first to trip over this!
Yes, you're right. And it shows, keysight cannot even round correctly, they just truncated the values...
Is anybody here, who has a good contact to Keysight/Agilent/HP, who could ask for solving this bug?
BTW: How can I store a screenshot of the instrument's display?
Yes, you're right. And it shows, keysight cannot even round correctly, they just truncated the values...
Shure?
Most probably their math package uses "round to nearest even" to avoid propagation of rounding errors e.g. in statistics mode.
...I would wanted to have the StdDv shown in engineering notation or proper units and not so many zeros.
Like the 34410A / 34411A has it shown.
5.67 uV on the 43410A instead of 0.000,005 V
Hopefully we will see this in a future update as well.
QuoteBTW: How can I store a screenshot of the instrument's display?You can save it to a screenshot or use Benchvue or over the LXI web interface.
It is pretty easy and works well.
Same "axis numbering" problem on my brandnew 34465A:
2.5 , 2.5000 , 2.5001 - WTF?
Isn't there enough place for:
2.49995 , 2.50000 , 2.50005
It's actually...
2.500 10
2.500 05
2.500 00
But, yeah. Agreed on the for rounding and truncating axis labels in the first place. You're not the first to trip over this!
I've seen a better solution for that space vs. resolution problem, I think, it was on the KEI 7510, i.e. the 'base value' is displayed to one or two decimal places somewhere on a major tick, and the major ticks divisor is displayed separately at the top.
BTW: How can I store a screenshot of the instrument's display?
BTW: How can I store a screenshot of the instrument's display?Press <Shift> DISPLAY, and then there should be an item inside the file management items, labelled as screen shot.
At first, yes, there is not enough space to display all these digits.
2.499 95 / 2.500 00 / 2.500 05
OK...?
I had no problem to find space for the additional (one) digit, see attachment.
(The red marked distance is unchanged, but could be reduced, too.)
I dunno. That looks like ass, IMHO. With a wide-aspect display like this, it certainly wouldn't have done any harm to spend a few horizontal pixels replicating the +5.04 at every graticule line.
Graph rendering isn't a ripe subject for "innovation" unless you're absolutely certain you're improving things. If this labeling method didn't catch on in the 400 years since Descartes, what are the odds that it's the right thing to do now?
Also, what's going on in the last few lines, where the scale goes from .184 ... .096 ... .008 ... .920? Am I supposed to mentally apply the "+5.04" prefix to all of these? That's a worse bug than anything in the Keysight screenshots.
I realize this isn't a Keithley thread, but if anyone would like to see similar screenshots from the k7510 for comparison I'd be happy to post them.
For such small differences, I found a better approach. By using the Math Scale function, you might either substract the average value (B = 2.500 000V), with a resolution of 1µV, and the window is now controllable in Center and Span to fractions of µV. Note also, that the instrument displays down to the resolution of the A/D, about 8 digits, or 100nV.
For sure, it can do something like this, expressing the whole statistics in ppm.. gives much bigger resolution for the StD value..
Is anybody here, who has a good contact to Keysight/Agilent/HP, who could ask for solving this bug?
Congratulations on your 34465A and nice comparison to the 3458A.
What 10 k Resistor did you base this on, to be so perfect on the mark?