New Hantek DSO2X1X models?

[xuraax]

@IMK.  thanks for the link. You need not worry unduly if this software has bugs. After all we all willingly opted to go for  a low cost DSO which we can afford and this inherently means we have to accept the scope as is.

From my point of view I would never be able to justify  the Tektronix equivalent especially due to the fact that for me it is just a hobby. Therefore having to live with a few bugs for me is better than no Scope at all.

Regards

[imk]

@IMK.  thanks for the link. You need not worry unduly if this software has bugs. After all we all willingly opted to go for  a low cost DSO which we can afford and this inherently means we have to accept the scope as is.

From my point of view I would never be able to justify  the Tektronix equivalent especially due to the fact that for me it is just a hobby. Therefore having to live with a few bugs for me is better than no Scope at all.

Regards

xuraax, for me electronic/software is just a hobby now so can't justify spending 20k on top of range scopes etc.
But this little Hantek is great, I take my hat off to them.
Been using it all day and haven't crashed it yet, so i think dso3kb_20210510 has really helped.
Do let me know how you get on please?

[DavidAlfa]

I've just bought mine! Catched a really a nice deal in aliexpress, with free 3-day delivery from Spain.

C210: 158€
D210: 171€
D215: 207€

For 36€ difference, I got the D210 (I'll unlock it later )
But the extra 13€ for the gen absolutely worths it.

Just in case anyone wants the link:
https://www.aliexpress.com/item/1005001632337246.html

It's simply perfect for hobbists and repairing consumer electronics, not measuring Hi-tech picosecond stuff at CERN, you know, just checking some signal like audio, digital protocols, pwm, voltage ripple...


Has anyone tested the real BW before/after the fw mod?

[Piton]

imk, uploaded your firmware to my hacked C10. Calibration does not work, writes error 511. The version has changed from B000 to B202. I had to solder the memory and reflash it to my native C10 with further hacking. I haven't mastered the platform-tools program yet, it's easier for me to solder it.

[Algoma]

They could have pulled that latest firmware off their website if there was a critical issue found within it.

[DavidAlfa]

We should make a folder somewhere (ex. Gdrive) with all fw revisions that appear, just in case! You guys getting betas directly from Hantek.
What's the sense on uploading to sites that only store the files for 2-3 days?

[imk]

imk, uploaded your firmware to my hacked C10. Calibration does not work, writes error 511. The version has changed from B000 to B202. I had to solder the memory and reflash it to my native C10 with further hacking. I haven't mastered the platform-tools program yet, it's easier for me to solder it.

Not MY firmware, it was firmware sent to me by Hantek to fix MY scope NOT your scope.
It has improved My scope but was maybe not ready for release to all versions of the scope.
Ask Hantek for firmware to fix YOUR scope and do be sure to remind them that you have HACKED YOUR scope.

I seem to remember reading on one thread that updating firmware on a HACKED scope was problematic.
I hope you don't dilute your beer too much with too many tears, but hackers beware.

[DavidAlfa]

No need to remind to always make a full backup, and all the hacking goes at your own risk
Specially having these (apparently) easy to use platform tools for making the backup...
Waiting for mine impatiently!

[xuraax]

imk, uploaded your firmware to my hacked C10. Calibration does not work, writes error 511. The version has changed from B000 to B202. I had to solder the memory and reflash it to my native C10 with further hacking. I haven't mastered the platform-tools program yet, it's easier for me to solder it.

I too got the 511 error on my hacked C10 when I tried to calibrate after this upgrade. The firmware version changed for me from 3000 to 3202.

may I ask why did you have to solder the memory and reflash it, and in any case can you explain how you did that just in case I may need to as well?

[Piton]

imk, it is clear that it is not yours, you do not take my words so literally, especially since this is a translation. I restored my device with the help of my own memory, which I dropped out before hacking, saved the firmware and programmed another memory, bought on Ali on the recommendation of Vitroks. Now I have soldered my native memory, because the purchased one for some reason did not want to reflash, the reason is unknown. The native must be kept for such cases. I will order another memory for hacking.
All firmware from the official website can be installed on the jailbroken device without any problems.

[DavidAlfa]

It's a shame that the qfn/dfn sockets are still pretty expensive:
https://www.aliexpress.com/item/1005002636631647.html
https://www.aliexpress.com/item/1005002036920820.html

[imk]

It's a shame that the qfn/dfn sockets are still pretty expensive:
https://www.aliexpress.com/item/1005002636631647.html
https://www.aliexpress.com/item/1005002036920820.html

I glue them upside down to 0.1 pitch per board and solder Kynar wire on them to 0.1 header pins, then the whole thing plugs in a breadboard
The trick is in the soldering as pad are soo close together it is easy to bridge them.
So i start on one side and solder the pad farthest away from me first.
Then i use a single sided razor blade perpendicular to the chip between the pad i just soldered and the one i am soldering next. (Heat shield)
The razor blade i temporarily fix with blue tack or masking tape, solder it and just keep moving the blade along the row of pads towards me.

Yes it's about as nuts as you can get but after bit of practice it gets easier and you end up with a little set chips 0.1 mounted.
Just stick bit of paper on top of the whole thing with chip type and pin number 1,8 - 9,16 etc.

Works for me 

[DavidAlfa]

That's not the problem.
I wanted to avoid soldering into the DSO board, specially if requiring hot air.
My idea was to replace the flash with the socket and forget about it.
But ughhh not nice having to unsolder everytime. Lifting pads nightmares...

[maskedviperus]

The firmware version denotes a fpga or board revision of some sort.

Im in the same boat. Cal error. Whoops

Can someone share platform tools please for 3000 so us fools have a way back til i get an email from them lol

[imk]

That's not the problem.
I wanted to avoid soldering into the DSO board, specially if requiring hot air.
My idea was to replace the flash with the socket and forget about it.
But ughhh not nice having to unsolder everytime. Lifting pads nightmares...

Hello David, now i understand you guys have opened up the scope and working on the flash chip to reprogram it.
You are way ahead of me i haven't even taken the back of the scope yet so no idea what it is like in there.
Ya unsoldering many times can be an issue and result in damage, do you have photo of what you are trying to re-program please?


So question; would it be easy to get at the LED's for the illuminated buttons as i find them a bit bright?

[DavidAlfa]

I didn't received mine yet!
The memory is a 8-pin spi flash, show in this post:
https://www.eevblog.com/forum/testgear/new-hantek-dso2x1x-models/msg3432650/#msg3432650

The leds, probably simple as replacing some resistors to lower the current.

[imk]

I didn't received mine yet!
The memory is a 8-pin spi flash, show in this post:
https://www.eevblog.com/forum/testgear/new-hantek-dso2x1x-models/msg3432650/#msg3432650

The leds, probably simple as replacing some resistors to lower the current.

Hello David,
Well when it arrives i hope you are as pleased with it as i am.
The firmware hantek sent to me has improved the lockup situation but not 100% fixed as i managed to crash it once yesterday.
That said for the monies you can't fault it really, i'll keep my fingers cross and hope hantek come up with complete fix.
Once you have the scope setup (triggered/decoded etc.)   it runs all day rock solid.
Problems seems to happen when you rotate the controls quickly, so take it easy on the knobs :-)

Now when it comes to setting up the serial protocol  trigger it took me ages to figure on how to change the Data Value  you want to trigger off.
What you have to look for in Menu Item Data is two little red dots, the are really tricky to see and almost inviable when you are editing the trigger value.
The way you use it is by turning the VO knobs and press the VO button.
In one state VO adjusts the value of High/Low Byte in the other state VO adjusts Which Byte you adjust... Watch the little Red Dot! Hope that helps

[DavidAlfa]

Thanks for the tips. Hopefully these issues will be fixed in the future.
For hobby use I think the price vs value is great, I can live with some ocassional lock ups while saving a big $$$ ammount

[xuraax]

I tried to load back the software dated 20210416 available on the official website. The firmware still indicated 3202 as against 3000 when I had first uploaded it. It still returned the error 511 during calibration. My unit is a hacked 2C10 same as IMK so I don't see what else could be different. Also why do we need to mess about with the memory chip? I am assuming when we upload a software it goes into this same memory chip.

[imk]

I tried to load back the software dated 20210416 available on the official website. The firmware still indicated 3202 as against 3000 when I had first uploaded it. It still returned the error 511 during calibration. My unit is a hacked 2C10 same as IMK so I don't see what else could be different. Also why do we need to mess about with the memory chip? I am assuming when we upload a software it goes into this same memory chip.

After update my scope shows Firmware 3202, software 20210416.00
However i have not tried the recalibrate it (maybe I should) does your scope work ok apart calibration issues?

[xuraax]

After update my scope shows Firmware 3202, software 20210416.00
However i have not tried the recalibrate it (maybe I should) does your scope work ok apart calibration issues?

My scope displays the same info as yours. I have not tried it exhaustively but it seems to work ok and has not hung up yet.

Maybe you should try to recalibrate.

Also note that when I had installed the official version I had not bothered to recalibrate so it may be the problem was already there back then.

The only thing I note is that, when I hook up ch1 to the 1kHz source, there is a small but visible offset between the Zero position and the square wave low when the Zero position is set to mid screen. However when the Zero level is set lower this offset quickly disappears.

Maybe people who have hacked their scope and updated ONLY with the official version can shed some light on this if they can run calibration.

[QuitButton]

Looking at the disassembly of a 5102P, the LEDS look to be surface mount underneath the buttons.

Probably easiest to stick a layer or two of Kapton tape over them.

[imk]

QuitButton

Thanks for the teardown video, seems easy job to get at the LED's.
However, I have tried to pull the knobs off couple of the rotaries and they just won't budge I guess I'll have to try harder.
BTW where did you get the replacement front panel from and about how much was it please?

Many thanks imk

[maskedviperus]

Ive been giving it a go with the 5/10 build on my formerly firmware 3000 scope and i cant seem to find anything wrong aside calibrate being broken.

I was able to save to usb as csv....something that was a guaranteed freeze at 80% complete before....  im super on the fence whether to send this thing back and increase my budget 200 more....the part that i do not like is that when i emailed them and asked them what the difference is between firmware 3000 and 3200, they informed me its a fpga/hw change....i dont know what that means lol

[imk]

Ive been giving it a go with the 5/10 build on my formerly firmware 3000 scope and i cant seem to find anything wrong aside calibrate being broken.

I was able to save to usb as csv....something that was a guaranteed freeze at 80% complete before....  im super on the fence whether to send this thing back and increase my budget 200 more....the part that i do not like is that when i emailed them and asked them what the difference is between firmware 3000 and 3200, they informed me its a fpga/hw change....i dont know what that means lol

I guess the "Field-programmable gate array" is a newer/different chip and maybe PCB changed to accommodate it.
As for sending it back i am to a little on the fence, but had a bad experience once sending stuff back to China as it just never arrived.
My feeling is that China is pretty much a one way shopping experience, worth a look at thread below
https://www.eevblog.com/forum/testgear/my-experience-review-hantek-dso2d10/new/?topicseen#new

I looked long and hard for an alternative  Rigol & Siglent make nice scopes at good prices but to match function spec was three times the folding holding.
The other option is DreamSourceLabs USB scope, I bought their logic analyzer and am very happy with it.
The big problem with PC  scopes is for is you need PC to make it work and i wanted something small and portable.
Good luck which ever way you go.