Products > Test Equipment
Keysight's new 34465A (6.5 digit) and 34470A (7.5 digit) bench multimeters
bson:
--- Quote from: carl_lab on August 17, 2016, 08:36:21 pm ---
--- Quote from: HighVoltage on March 16, 2015, 08:28:59 pm ---Today my Keysight 34470A arrived...
--- End quote ---
Same "axis numbering" problem on my brandnew 34465A:
2.5 , 2.5000 , 2.5001 - WTF? :palm:
Isn't there enough place for:
2.49995 , 2.50000 , 2.50005
--- End quote ---
It's actually...
2.500 10
2.500 05
2.500 00
But, yeah. Agreed on the :palm: for rounding and truncating axis labels in the first place. You're not the first to trip over this!
carl_lab:
--- Quote from: bson on August 18, 2016, 02:53:37 am ---
--- Quote from: carl_lab on August 17, 2016, 08:36:21 pm ---
--- Quote from: HighVoltage on March 16, 2015, 08:28:59 pm ---Today my Keysight 34470A arrived...
--- End quote ---
Same "axis numbering" problem on my brandnew 34465A:
2.5 , 2.5000 , 2.5001 - WTF? :palm:
Isn't there enough place for:
2.49995 , 2.50000 , 2.50005
--- End quote ---
It's actually...
2.500 10
2.500 05
2.500 00
But, yeah. Agreed on the :palm: for rounding and truncating axis labels in the first place. You're not the first to trip over this!
--- End quote ---
Yes, you're right. And it shows, keysight cannot even round correctly, they just truncated the values... |O
That's not what I expect, when I spend $1500 or more...
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?
Andreas:
--- Quote from: carl_lab on August 19, 2016, 06:56:06 am ---
Yes, you're right. And it shows, keysight cannot even round correctly, they just truncated the values... |O
--- End quote ---
Shure?
Most probably their math package uses "round to nearest even" to avoid propagation of rounding errors e.g. in statistics mode.
With best regards
Andreas
HighVoltage:
--- Quote from: carl_lab on August 19, 2016, 06:56:06 am ---Is anybody here, who has a good contact to Keysight/Agilent/HP, who could ask for solving this bug?
--- End quote ---
I think this one has made it in to the requested changes for future FW updates.
Also, 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.
[/quote]
--- Quote ---BTW: How can I store a screenshot of the instrument's display?
--- End quote ---
You can save it to a screenshot or use Benchvue or over the LXI web interface.
It is pretty easy and works well.
carl_lab:
--- Quote from: Andreas on August 19, 2016, 07:06:35 am ---
--- Quote from: carl_lab on August 19, 2016, 06:56:06 am ---
Yes, you're right. And it shows, keysight cannot even round correctly, they just truncated the values... |O
--- End quote ---
Shure?
--- End quote ---
No, maybe "round to nearest even" is used, you are right, but...
--- Quote from: Andreas on August 19, 2016, 07:06:35 am ---Most probably their math package uses "round to nearest even" to avoid propagation of rounding errors e.g. in statistics mode.
--- End quote ---
...on axis numbering, same result as shown in screenshot (2.5 , 2.5000 , 2.5001 is nonsense).
--- Quote from: HighVoltage on August 19, 2016, 08:19:11 am ---...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.
--- End quote ---
+1
--- Quote from: Andreas on August 19, 2016, 07:06:35 am ---
--- Quote ---BTW: How can I store a screenshot of the instrument's display?
--- End quote ---
You can save it to a screenshot or use Benchvue or over the LXI web interface.
It is pretty easy and works well.
--- End quote ---
OK. I tried to save to USB and got only raw data...
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version