Haha, looks like they screwed something and had to remove it.
Every update partially fixes something, but breaks other 3, probably their testing team is a single guy in a dark room
Can you answer me if DK124 (from power supply on Hantek DSO2X1X) can be replaced with VIPER22ADIP-E?
Now I have noise problem. What does a 100mV / 100kHz signal look like to you on 10x probe?
What is the source of the noise?
Mine looks similar when using the probe on CH1 and the alligator clips for the generator.
I was able to improve this by using the 20MHz bandwith limiter.
Same signal with 1x probe, with and without BM limit
Also good results when using a BNC to BNC coax cable.
So the noise is not from the scope, it is coming from the probing setup.
ST - FERD technology outperforms Schottky diodes
Hi, In which way does this tech outperform a schottky, when the voltage drop is higher?
The current depends on the device, can't do much about that, so power dissipation is lower when using schottkies.
The zoom bug persists, it still won't past the X position where the trigger is set.
I tracked this issue back to older versions, at least up to 2021.04.16, but works in the oldest 2020.11.18 (Attached picture).
As we know, most freezing issues where caused by the Fw version, not the software itself.
So I'm going to use latest FW with 2020.11.18 software and see how it performs.
Perhabs you could try too, as I barely use it lately.
Edit: Latest SW with working zoom is 2021.01.05
Wasn't the zooming what we were talking about? Not the cursors.
There's no "Track" or "Manu" modes in zoom mode.
I found some workarounds for the trigger sync bugs.
Basically, setting the trigger slightly higher than Vmax eventually finds a good spot where it barely moves.
This leads me to think that the trigger is done by the fpga, before any filtering.
Check how a 20mV signal looks without HR mode! lot's of noise, spikes, ugly as hell!
Probably the fpga is seeing even worse data than what you actually see on the screen, that would explain why the trigger is almost unusable in low V/div modes.
So basically you're searching to sync these spikes, if you set it in the middle you get a lot of random noise making the trigger crazy.
Nobody knows what the actual f*** s*** they've done
So I'm researching sw versions for my 2c10 (before converting to 2d15) and mine shipped with latest fw 3202 but sw 20210726.00 with fully populated board marked 2D15 (bought mine via Hantek @ Amazon a few weeks ago) which I thought was way behind sw wise but after reading some of the last comments I'm taking it as some are having problems with sw versions even older then mine and having better stability\accuracy with even older then that sw versions, latest is not always the great it seems with this unit's sw. Think I'm going to learn my scope and how it should work with additional reading before messing with it anymore
side note\question from newb scope user: any problems with sw 20210726 that would prevent correct learning of scopes? last few posts seems to indicate that 20201118 may be the most stable\accurate, but faq says 20210416 which I'm inclined to trust more, any advice or insight greatly appreciated as I don't even know what I'm doing past very basics lol
I'm off to read\research!
None have any extreme bug preventing typical use of the scope.
Most issues are related with cursors, zooming...
Except, at least, 2020.11.18. Has a trigger bug, where it triggers much sooner than the adjusted threshold, making handling almost impossible.
2021.04.16 works pretty well, but it already has the zooming bug.
Can't tell much more, it seems I'm the only one testing older versions, instead blindly updating to the latest.
Well the industry norm (at least since the 90s) is normally that later versions of software that's in the maintenance phase gets more stable so it's understandable that people try the latest versions available. But you're right that it's obvious that the latest version apparently isn't necessarily the best or the most stable when it comes to this unit and everyone need to keep in mind that these are not feature updates (although one could wish for some feature enhancements in some areas).
Do you fellas notice huge discrepancies between DVM readings and the Measurements you can set to bottom of screen? Mine rarely match up, to the point I'm using my DMM, which I've noticed is a full 4 degrees off from each other, I just picked up a 2nd quality DMM to confirm voltage readings to see which is the one thats off, also going to take notes between software versions to see which is the most accurate and has the same readings within all measurements displayed. Ill try to list what I find coherently, still learning how to use a scope so ... lol
Thanks. Added to the collection. Also made a specifix FW changer package for it.
However I smell more Hantek "engeneereng"...
Looks like Hantek's testing department is non-existent, but they seem to respond reasonably well at bug reports.
So, what about making a single post and keep it with all bugs being found, ex. like this example?
I'd have no problem keeping it updated.
» Current software version «
» 2022.02.10
» Vertical view «
» Horizontal view «
» Serious artifacts caused by undersampling, ex. a 10MHz signal shows garbage below 20us/div, you might not notice there's a signal there.
» Confirmed in FWs: 3102
» Zoom window can't be moved to the left past the trigger position, didn't happen before 2021.02.23
» Confirmed in FWs: 3102
» Math «
» Trigger «
» Wave generator «
» Amplitude can be set too high and cause distortion if offset was modified first. Backwards, it works correctly.
» Confirmed in FWs: 3102
» Duty moves in 1% steps, but after rotating fast and reaching 99%, it'll stick to 10% steps until manually reaching 0%.
» Confirmed in FWs: 3102
» Decoding «
» Impossible to decode SPI no matter the trigger options? Displays a "0" or "?" on each clock cycle instead every 8/16/32.
» Confirmed in FWs: 3102
» Display «
» Measure «
» Statistics don't reset after disabling/enabling, you need to go into Type and deselect/select all.
» Confirmed in FWs: 3102
» Poor accuracy in voltage measurements
» Confirmed in FWs: 3102
» Cursor «
» Acquire «
» Other issues «
I like the idea, however people should also submit for each bug the SW and FW version it was found in.
It'll be a "Current existing bugs". You're supposed to be using the latest version.
How in earth are you reporting a bug from an old version? It might have been fixed by now.
Yeah, it's a good idea to note down the Fpga version to better track the bug source and compare between us.
I'm expecting some cooperation from you guys, let's do this
Time to start pushing and making them work hard to fix something they've been selling 2 years already.
Some bugs at release? Sure.
Same bugs after 2 years? No excuses here, can be only called by its name: Laziness.
Brilliant David
I'll get the latest loaded up when I get back into the office on Wednesday and I'll report anything I find.
73s Ted
2E0THH
I was able to attach an external battery
Very nice! But you did not show how you wired it inside the scope!?!
What is the power supply output(s) in the scope?
I was able to attach an external battery
I like your mod.
It is practical for mobility and also protects the scope when you want to poke around freely in ground-referenced circuits.
Have you noticed any change in the noise floor and/or sensitivity?
How much impact does the additional SMPS have on them?
Has anyone tried the FPGA - FW update that Hantek sent to MAXIE?
I updated mine this weekend and did a quick test, it looked OK.
I wasn't able to do an in-depth test yet, I'll come back when I have some results.
I was able to attach an external battery
I like your mod.
It is practical for mobility and also protects the scope when you want to poke around freely in ground-referenced circuits.
Have you noticed any change in the noise floor and/or sensitivity?
How much impact does the additional SMPS have on them?
Without measuring probes, the noise level is the same, with probes 10x noise level is higher, because I think the grounding is missing. I use 200Mhz probes, because have lower attenuation over 100Mhz.