New Hantek DSO2X1X models?

[aleph0]

OK!
Any chance the platform_tools zip file is corrupted?
I downloaded it both in windows and in Linux and cannot extract the restore.bat file (or the Readme_English.pdf file for that matter) from it, but many other files such as Readme_English.doc extract just fine.
I see platform_tools.zip with the following md5:

Code: [Select]

$ md5sum platform-tools.zip
70280b90e88a60ff001bd984a0b3a0ae  platform-tools.zip

[DavidAlfa]

Indeed, it was corrupted! Something went wrong when I updated it 2 weeks ago.
Should be working now.

Code: [Select]

md5  8086da8f46f5d6ae4dd18a254f4c0757


[aleph0]

I finally got time to flash it. Went into FEL mode, ran restore.bat, screen showed the funny colored stripes, flash finished without issues, scope rebooted and... still the same behavior. no buttons work, no signal being displayed for either of the channels, all buttons have their lights on..
this sucks big time. I guess at this point I should ask for a refund as the scope is completely useless.

Thank you very much DavidAlfa for all your help.

[DavidAlfa]

Yeah, this is a real problem then!
You could try to disassemble it and reseat the ribbon cable connecting the mainboard and the front panel.
There's no warranty stickers anywhere, and it's pretty simple.

[laserdyne.rd]

TRIGGER PROBLEM. (DSO2D15)
Pretty sure this is a bug.
In 'Normal' trigger mode, I hit 'Run/Stop' to STOP, but it still triggers once AFTER Run/Stop is red. It behaves almost identically to the Single Seq button.
It's pretty bad; sometimes it's hard to get that one magic capture, only to have it disappear when you disconnect the probe.
Can anyone confirm this? My setup uses x10 probe and Ch1. Not sure if it applies elsewhere.
SW 1.0.3.0.0
FW 3205

[DavidAlfa]

Yes, it's damn annoying!

[Cántabro]

Hello, greetings, I am using the translator.
I wanted to comment that in Amazon Spain, you have the offer of the screenshot.
It looks like a hantek, with another mark. is it fake? it's a mistake?

[Cántabro]

I don't see how to add photo
I'll give you the link, look especially at the price of dso2d15

https://www.amazon.es/Osciloscopio-generaci%C3%B3n-Almacenamiento-Digital-fidelidad/dp/B0CFVTWPTB/ref=mp_s_a_1_31?crid=1GWS48T4HJIXT&keywords=osciloscopio&qid=1692477710&sprefix=osci%2Caps%2C268&sr=8-31

What is your opinion?

[Aldo22]

These prices do not make sense in my opinion.
The one with the best features is the cheapest?
I would be careful.

[Cántabro]

These prices do not make sense in my opinion.
The one with the best features is the cheapest?
I would be careful.

as it is Amazon, there is not much problem, it is returned and ready, there is a 30-day trial

[DavidAlfa]

I don't see how to add photo
I'll give you the link, look especially at the price of dso2d15
...
What is your opinion?

Link not working. But more than $200 for it = NOPE. Save for the SDS1104X-E instead.
I got mine durign the pandemic for 170eur including shipping.

[Aldo22]

Link not working. But more than $200 for it = NOPE. Save for the SDS1104X-E instead.

The link worked before.
Apparently they noticed that something was wrong and removed the offer.
DSO2D15 (150MHz + SG) was 105 euros or so.

[DavidAlfa]

Haha next time just buy it, return later if not happy, it's amazon!

[Cántabro]

Link not working. But more than $200 for it = NOPE. Save for the SDS1104X-E instead.

The link worked before.
Apparently they noticed that something was wrong and removed the offer.
DSO2D15 (150MHz + SG) was 105 euros or so.

I bought it, and they just canceled it, they refund my money. I think it is not correct according to the law, shopping online

[Veteran68]

Laws vary from place to place, but honest pricing mistakes are typically not required to be honored. For some reason, some people believe that once a price is stated, they are legally obligated to sell at that price, no matter what. Some sellers will honor the price out of customer good will but aren't required to. Only if pricing games are played to lure in customers to buy something else (bait and switch) or some other manipulation is it illegal. But if they discover a genuine pricing error, cancel and refund, then pull the listing and fix the price, that should be within the law in most places I'd wager.

[Cántabro]

I'll leave it as a midsummer night's dream. They have also deleted it from my orders, and the money is in my account. there is no trace on my orders, and they have deleted the ad. Although I have screenshots hahahaha Well I leave the subject, it was a good offer.

[laserdyne.rd]

Yes, it's damn annoying!

Is there a pathway to report this and get it fixed? It is literally a blocker for us using this scope. It's great otherwise.

[Z_E_V_S]

TRIGGER PROBLEM. (DSO2D15)
Pretty sure this is a bug.
In 'Normal' trigger mode, I hit 'Run/Stop' to STOP, but it still triggers once AFTER Run/Stop is red. It behaves almost identically to the Single Seq button.
It's pretty bad; sometimes it's hard to get that one magic capture, only to have it disappear when you disconnect the probe.

Yes, this is a trigger error.
And in the "normal" trigger mode, the memory depth is only 4k, even if you set a higher value.
Therefore, for rare events, I recommend using a single trigger start.

[aleph0]

Yeah, this is a real problem then!
You could try to disassemble it and reseat the ribbon cable connecting the mainboard and the front panel.
There's no warranty stickers anywhere, and it's pretty simple.

Removed the ribbon cable and reinserted it on both ends (main board and front board), but no luck. I'm now in conversations with the seller about a refund.

Having said that, would you recommend a siglent sds1104-e or a rigol for a beginner? I'll be doing basic homebrew computer stuff, Ben Eater style, so 100MHz is more than enough for me.

[Veteran68]

I personally would take the Siglent SDS1104X-E over the comparable in price Rigol DS1104Z. Hard to beat it's overall value in its price category. The new Rigol 800/900 series scopes *might* displace it as king of its hill, but they're not yet generally available and so not many public reviews on it.

[dirtmover]

Yes, it's damn annoying!

Is there a pathway to report this and get it fixed? It is literally a blocker for us using this scope. It's great otherwise.

You can try reporting at https://www.eediscuss.com but don't expect action any time soon, if at all!

[aleph0]

ty dirtmover. I notified them here https://www.eediscuss.com/forum.php?mod=viewthread&tid=17977 but nothing yet. Not holding my breath...

[morgan_flint]

Hi DavidAlfa and all,

Today I connected the scope after a long time without using it. To my surprise, I found none of the rotary encoders give any response!

Entered in UTILITY/FrontPanelSelfTest and checked that all the buttons work OK, but none of the rotary encoders.

I tried a factory reset (both Keysight application and serial console), but still the same.

Looking at the schematics, I see the signals for the buttons and encoders share the same path in the ribbon cable, so I don't think the problem is there. I suspect then it could be SW or FW corruption. Probably, FPGA's FW, as the FPGA is controlling the user interface, if I remember well.

I have backups done with David's Backup Builder. Do you think restoring with dso3kb_CN2149029XXXXX_FPGA.upk could be the solution? Or is better to take the opportunity to update everything to the lastest versions? (I never updated SW or FW)

PD: I tried to restore with dso3kb_CN2149029XXXXX_FPGA.upk but can't do it as without the rotary encoder it's not possible to select the update from the directory... I'm afraid I'll have to restore in FEL mode

[DavidAlfa]

Having a backup, try platform-tools.
Or reseating the ribbon cable just in case, doesn't take much work.

[morgan_flint]

Ok, thanks.

Now I'm waiting for another backup with DSOFlash to end, just to be sure before starting anything.

I'll take a new look at the ribbon cable, but I don't think that is the case, as the pushbutton signals travel through the same path as those of the encoders (see attachments).

The yellow signals go to the ribbon cable, the green ones correspond to pushbuttons (including those in the encoders, at Scan_Data_5), and the red ones to the rotary part of the encoders. If there's a bad connection, it should be between the encoders' diodes and U2, and to see that I have to take apart the display, a bit more complicated than accessing the main board, but I'll do it when the backup ends.

BTW, I've had problems with the FEL driver in this PC, followed all the instructions but DSOFlash gave an error. I've done the same on another PC and it's going OK.

EDIT: Backup finisher, took apart the display and reseated the ribbon cable. Also, checked with the multimeter continuity from all the diodes' anodes to pins 1 and 2 of U2. All correct. I also took the opportunity to clean the board, which had a lot of flux residues (I thought it could have been the culprit, if these residues had become conductive with humidity, for example). But no luck. I'll try platform tools