I don’t understand why you would think leaving YouTube comments would end up being more helpful than contacting Keysight directly.Agreed. You might even get a pre-release firmware version that addresses the issues (some or all). Not contacting support about the problem you have leaves the manufacturer in the dark and your issues won't be fixed for sure.
I agree, it should not happen and is annoying as hell. Unfortunatly we can see this kind of stuff happening with basicially all big players when it comes to the modern, digital driven testgear. Tens of thousends of dollars for an MSO Series 4, RTM3004 or whatever - the first firmware releases were spicked with bugs. Pressure to release new products seems to be to bug to hold back until this kind of stuff is fixed... ;/But in the end rushing out new equipment is doing nobody any good because people will be wary of new equipment and postpone purchases.
I agree, it should not happen and is annoying as hell. Unfortunatly we can see this kind of stuff happening with basicially all big players when it comes to the modern, digital driven testgear. Tens of thousends of dollars for an MSO Series 4, RTM3004 or whatever - the first firmware releases were spicked with bugs. Pressure to release new products seems to be to bug to hold back until this kind of stuff is fixed... ;/But in the end rushing out new equipment is doing nobody any good because people will be wary of new equipment and postpone purchases.
I agree, it should not happen and is annoying as hell. Unfortunatly we can see this kind of stuff happening with basicially all big players when it comes to the modern, digital driven testgear. Tens of thousends of dollars for an MSO Series 4, RTM3004 or whatever - the first firmware releases were spicked with bugs. Pressure to release new products seems to be to bug to hold back until this kind of stuff is fixed... ;/But in the end rushing out new equipment is doing nobody any good because people will be wary of new equipment and postpone purchases.
New anything is getting scary. It is interesting how many bugs are found so quickly by folks outside the company. External testing could alleviate a good portion of buggy new stuff. Give Dave Jones one and he will find a lot of the bugs :-DD
I agree, it should not happen and is annoying as hell. Unfortunatly we can see this kind of stuff happening with basicially all big players when it comes to the modern, digital driven testgear. Tens of thousends of dollars for an MSO Series 4, RTM3004 or whatever - the first firmware releases were spicked with bugs. Pressure to release new products seems to be to bug to hold back until this kind of stuff is fixed... ;/But in the end rushing out new equipment is doing nobody any good because people will be wary of new equipment and postpone purchases.
Well, one of the lines I wanted to add to my previous posting is 'If A-brands are going to be consistent in this behaviour then people might as well buy gear from Rigol or Siglent'. It is already a fact that A-brands push out equipment ahead of schedule and need about a year to fix firmware bugs. IMHO it is still worth buying an A-brand due to pedigree; the core of the instrument usually is based on old & well proven designs / methods so it will also work in the corner cases where gear from Rigol & Siglent typically fails. Due to the latter I decided to leave the line out.I agree, it should not happen and is annoying as hell. Unfortunatly we can see this kind of stuff happening with basicially all big players when it comes to the modern, digital driven testgear. Tens of thousends of dollars for an MSO Series 4, RTM3004 or whatever - the first firmware releases were spicked with bugs. Pressure to release new products seems to be to bug to hold back until this kind of stuff is fixed... ;/But in the end rushing out new equipment is doing nobody any good because people will be wary of new equipment and postpone purchases.
You previously claimed that you get something that Just Works and meets specs when you buy A brands. That they do proper QA and fundamental functional problems thus get caught before release, and that this justified their higher price. Do you still stand by that? Because it looks to me like that's becoming less true as time goes on, if this thread is anything to go by.
The Danny Bogdanoff show is pretty active on this forum, as the brand ambassador for Keysight I am sure he could set the wheels in motion as to an investigation of your reported issue.
Well, one of the lines I wanted to add to my previous posting is 'If A-brands are going to be consistent in this behaviour then people might as well buy gear from Rigol or Siglent'. It is already a fact that A-brands push out equipment ahead of schedule and need about a year to fix firmware bugs. IMHO it is still worth buying an A-brand due to pedigree; the core of the instrument usually is based on old & well proven designs / methods so it will also work in the corner cases where gear from Rigol & Siglent typically fails. Due to the latter I decided to leave the line out.
Siglent SDG2000xyz function generator versus Tektronix AFG31000 for example. The latter stays in phase with an external reference when doing modulation. Also the Tektronix AFG31000 is a true stand-alone unit. You don't need any PC software to edit / import arbitrary waveforms.Well, one of the lines I wanted to add to my previous posting is 'If A-brands are going to be consistent in this behaviour then people might as well buy gear from Rigol or Siglent'. It is already a fact that A-brands push out equipment ahead of schedule and need about a year to fix firmware bugs. IMHO it is still worth buying an A-brand due to pedigree; the core of the instrument usually is based on old & well proven designs / methods so it will also work in the corner cases where gear from Rigol & Siglent typically fails. Due to the latter I decided to leave the line out.
Makes sense. Do you have some examples of where an A brand handled a corner case where the B brands failed?
When these are addressed, I'm willing to give EL30000 series a serious consideration.The Danny Bogdanoff show is pretty active on this forum, as the brand ambassador for Keysight I am sure he could set the wheels in motion as to an investigation of your reported issue.
Haha ;D
I'm passing this along to the team for feedback!
Sorry for the delay, took a few days off and am catching up!Feel free to PM. I returned the unit I purchased for a refund, I don’t have access to one. If you provide a demo unit, I’d be happy to retest and report the findings here, in case it was only my unit, there might be weird interaction with network equipment, I don’t know.
@niner_007 the R&D team would love to chat if you're willing, I'll send you a PM.
The SCPI lockup issue is something we haven't seen before, we've been doing nonstop / no delay commands without issues, so the team would like to take a look / chat and see if there's a bug, but we suspect it's just your load and we want to get it replaced.
Regarding battery testing, from R&D:
"
The EL30000 Series does not currently have a dedicated battery test feature, but we are considering adding it through a future firmware release. Meanwhile, you will need to use a PC to control the load and stop the discharge before the battery reaches its cutoff voltage.
"
Obviously we'll need to get the comms issue worked out for your unit.
From Bill Griffith, one of our power folks:
"- The current definition for undervoltage better is for testing power supplies. The latch mode assumes the input voltage starts low, and rises toward the undervoltage limit at which point the load turns on and stays on regardless of voltage. E.g. once live stay alive.
- I wrote a simple program to test batteries with an undervoltage cutoff: https://blogs.keysight.com/blogs/tech/bench.entry.html/2021/05/03/battery_and_celltes-HXQ1.html
- Loads potentially have two sets of ranges, one for the load and one for the measurement system. You do not want to auto-range the load as it would affect the source. It might be beneficial in some cases to auto-range the measurement system. However, it is much simpler just to tie the load and measurement system together. I personally, prefer the ease-of-use of a single setting for high, medium, and low range.
- For lower power BNC connections – I cut off a dual banana plug. You used two of them in this video: https://youtu.be/FM7dWAC6wok?t=22 I personally like the front connectors – we used them to test the 20 A output of the power supply
(Attachment Link)
"
Recent Keysight hardware is just not as great as in the old days. There are plenty of other examples discussed here:Bug in 53230 counter implementation (https://www.eevblog.com/forum/testgear/keysight-53230-frequency-counter-review-and-bug-identification/)
Disappointing performance of B2962 power source (https://www.eevblog.com/forum/metrology/detailed-review-of-keysight-smupower-source-b2962a/)
Drift of 34470 DMM due to ACAL (https://www.eevblog.com/forum/metrology/keysight-34470a-calibration-and-acal-problems/)
Bugs with bursts in 33522 function generator (https://www.eevblog.com/forum/testgear/agilentkeysight-awg-fw-errors/)
I bought E36232 and EL34143 at the same time, the experience is very bad! They both have serious anti-human logic in their basic operations. The device has knobs but noway to adjust voltage or current by bit. Only 0.001V per turn of the knob, which makes the knob useless! And even when benchvue is used, EL36232 is often disconnected, and USB has to be replugged to reconnect the instrument. Very, very bad experience. :( :( :( :( :( :(
[11:36] M1MaxMacBookPro.local:keysight_EL3000_beta_khew_13MAY2022 | md5 Jati750B_9.2.7_1.0.6_17_114_dfd9d5d1396b24671c2adaa64d85875e.dfu
MD5 (Jati750B_9.2.7_1.0.6_17_114_dfd9d5d1396b24671c2adaa64d85875e.dfu) = dfd9d5d1396b24671c2adaa64d85875e
Release notes say: "Added new battery test features."
Release notes say: "Added new battery test features."
I just went ahead and installed the firmware update on my EL34143A. The "Mode" menu now has a new option called "Battery Test." I've attached a screenshot of what's displayed when you select it.
any ideas how that works with models that have 2 inputs? can it work in parallel mode?