EEVblog Electronics Community Forum
Products => Test Equipment => Topic started by: Perepandel on October 22, 2020, 10:14:55 am
-
Hi,
I've posted some about this also in the https://www.eevblog.com/forum/testgear/hantek-tekway-dso-hack-get-200mhz-bw-for-free/ (https://www.eevblog.com/forum/testgear/hantek-tekway-dso-hack-get-200mhz-bw-for-free/) thread, as it would be nice to know if these models are bandwith hackable, also.
But in this thread my aim is to discuss any available info on these supposed new models, as nothing can be found on Hantek's site. Could it be that they are fake?? They seem like an upgraded version of DSO5xx2 with much more memory (8M), an in-built function generator, serial decoding, 12bit precision and from 100 to 150 MHz, and cheaper than the DSO5xx2 models. No info on Google or whatsoever, either.
-
It's still an 8 bit scope. the AWG is 12 bit.
-
Hi Sithrebel,
I'm also curious having ordered one from Aliexpress (DSO2C10), do you have actual information on these scopes? could they actually be FAKES? I'm NEW to this...
regards
Luigi
-
There's a thread about the DSO2D10:
https://www.eevblog.com/forum/testgear/what-is-a-hantek-dso2d10/ (https://www.eevblog.com/forum/testgear/what-is-a-hantek-dso2d10/)
-
Thanx Tunk!
-
Hi All,
got a reply from zhangqiang@hantek.com saying "this is our new product, it is not a fake" Great, hope it comes soon..
lm
-
Hi! Thanks for the info; I just got to know about that thread some minutes ago. Actually this one is older, so they should be referret to here ::)
Anyway... I just got mine about two weeks ago but it's still inside its box for two reasones: first of all, I don't have the time to play with it due to work & studies constraints, and second, I ordered the 100 Mhz one because it was the only one available at the moment but later I found the 150 one in stock, so I ended ordering it too, hoping I'll be able to sell the other one. It's still in transit.
I hope we've made a good purchase. Some months ago I was about to buy a DSO5102P but got informed about its short memory length. Then I was in search of a Siglent SDS1202x-e but it's at about twice is "old" price and I got tired of waiting for months to get a deal, which has not come, even after some failed attempts (fake Amazon ads and so on). Then one day this model appeared suddenly on AliExpress.
What's not clear to me is what the 12-bit resolution refers to. Some say it's for the function generator only. Some specs say the oscillo itself has a 12-bit vertical res; others say it's a 8-bit oscillo. No definite answer.
What I like also is that it comes with serial decoding.
I have very little experience with oscillos. I'll give more info when I have the chance to play with it.
-
Anyway... I just got mine about two weeks ago but it's still inside its box for two reasones:
If it was me, I would open it and check if it works. And if it doesn't, contact the seller.
-
Anyway... I just got mine about two weeks ago but it's still inside its box for two reasones:
If it was me, I would open it and check if it works. And if it doesn't, contact the seller.
Haven't opened it yet as I've already got the 150 Mhz already, but haven't had the time to play with it; just to test that it work and looks good. Maybe this weekend.
I've algo got the manual in PDF from Hantek as it was missing on the driver CD :palm:, so I asked them via email and at least I have to aknowledge that they were very quick replying. As an unexpected gift, I got a firmware update. Which opens up the question of how feasible would be to flash an inferior device (the 100 Mhz version and even the ones without signal generator) and see what happens... Any volunteers? Remember I have an spare, new unit for sell ;D
-
I have an DSO2D10 on order from Banggood and they are already 3 week late to ship it, their excuse is "excessive demand".
@Perepandel, do you think I can flash my DSO2D10 (when I get it) with your 150MHz firmware version, is it for the DSO2D15 (Signal Generator version)???
-
I have an DSO2D10 on order from Banggood and they are already 3 week late to ship it, their excuse is "excessive demand".
@Perepandel, do you think I can flash my DSO2D10 (when I get it) with your 150MHz firmware version, is it for the DSO2D15 (Signal Generator version)???
Hi upsss! Have you already got your machine? I have no idea what would happen in case you flashed it with the firmware I got. My bet is nothing will break, not to the point that it would get bricked, at least. The hardware can't be that different, in case it is :-//. I think the worst that could hapen may be that the new features don't work. Or maybe it even refuses to flash prior to that. And, finally, you should keep a copy of the original firmware in case everything goes wrong. I don't know if the upgrader offers that possibility (to save it prior to flashing).
I can send you the file in case you want to try, but of course I don't offer any warranty in case it doesn't work and your oscilloscope becomes dead. I think you should ask the more experienced people in this forum regarding what to do.
-
Hi Perenpendal,
I have a DSO2D10 and am curious to see what will happen when I update it with the DSO2D15 firmware.
The hardware is exactly the same, the PCB is marked 2D15.
So if you can email the firmware to me, please do.
Mine already had a fault where it freezed on 80% Hardware Initialization, so Hantek support has sent me the necessary platform tools to get the low level hardware back to work again.
According to them these models are actually unbrickable since they use the Allwinner Controllers. that is also used in Raspberry Pi, Orange Pi, and some Android Phones. etc. Its basically an Android Platform.
They use Phoenixsuite_CN to load the Boot Files, etc.
It uses the Allwinner F1C200s controller which is a fantastic controller to work with.
Download the datasheet and user manuals Pdf files from the internet and check it out.
Its a Linux system off-course. I wish I could get hold of the source files for the firmware so that one can do your own mods on bugs.
zadig-2.5 are used to load the WinUSB driver to make it work as a programmable WinUSB slave.
Then they use Sunxi-fel to convert it to Android. After that Phoenixsuite_CN is used to load the bootfiles, etc.
To convert the processor to a USB slave there is a small button underneath that must be depressed when you switch it on. One of the small ventilation holes just at the right spot. It can then be plugged into your PC and will register as a WinUSB device under Device Manager instead of a measuring Instrument instead.
Off-course the back USB connector is used for this purpose.
-
Hi Perepandel, I have NOT received my DSO2D10 yet, it is supposed to be shipped on December 28, which is 3 weeks past their (Banggood) original shipping date.
Maybe Hantek is fixing some bugs and that is why they are delaying shipments. I rather wait a few more weeks and not have to deal with any obvious bugs.
In another thread you mentioned that you already have 2 of these new scopes, which versions did you get. How do you like them, any problems?
I looks like CMAASS has already also the DSO2D10 and he sounds like he knows what he is talking about. Maybe he will the first guy to try your DSO2D15 firmware and hopefully we all will follow him.
-
Is it full firmware file or just update file? If it's just update file it's no use , because the update file for the DSO2D10 and DSO2D15 is the same.
-
Can you please share the files and method.
-
Hi jobitjoseph1,
are you referring to the platformtools and Phoenixsuite_CN tools or to the Firmware?
-
Hi cmaass,
Both platform tools and the firmware.
-
I will see what I can do, those are very large files.
I will post the firmware so long, it is a small file for the DSO2D10
I just want to add, after I used the platform tools whenever I press the System Info function key in the Utility Menu it no longer shows the Model number, Serial number and Hardware info, those are undefined.
It only shows the Software and Firmware numbers.
So I don't even know what model Number it is now, only that it is a type D.
When I received the scope from Aliexpress the Waveform Generator did not exist on it. I then wrote to Hantek and they have send me a firmware update within 2 days.
The same when it freezed on 80% Hardware Init. It also took only 2 days before I received the platform tools. All these were from a guy named wangshuang, he was very helpfull.
There aftersales service is very good.
There are still a lot of bugs that has to be sorted out. I wrote to Hantek about them, hope they can fix it.
-
hi Perepandel,
does the firmware file for the 2D15 has the same name and date or does it differ?
-
There are still a lot of bugs that has to be sorted out. I wrote to Hantek about them, hope they can fix it.
Maybe that is the reason they stooped/delaying new shipments.
-
hi Perepandel,
does the firmware file for the 2D15 has the same name and date or does it differ?
As per hantek it's the same
-
Bug spotted
Frequency measurement on 4k,40k and 400Kpt is wrong.for 1Khz signal measurement shows 498Hz, measurement works fine with 4M & 8Mpt memory depth are fine.
(https://i.imgur.com/vhMXW2M.jpg)
(https://i.imgur.com/DgEv9z0.jpg)
(https://i.imgur.com/CfHsKMw.jpg)
-
Hi, I had the same problem.
It was fixed after reloading the boot files, etc with the platform tools.
However like I said after using the platform tools my system info disappeared.
See my former post.
Below is the link to download the platform tools.
Just follow the instructions in the readme_English.docx file in the platform tools folder.
What I found is, after I loaded the Android driver with sunxi-fel uboot images/uboot_fastboot.bin , when I ran the cmds.bat file , when the scope rebooted it freezed,
I then switched the scope off and on again by pressing the button underneath while switching it on. (I used a matchstick to press the button, that way you cannot short out anything.)
After that I ran the cmds.bat file straight away whithout using sunxi-fel, since the Android file is now already present. It then booted without any problems.
If it shows as a Winusb device under Device Manager with the driver info as you saw in the Zadig-2.5 utility, you can just use the cmds.bat file whenever the scope freezes during rebooting and if you are unable to reload the update file. Although it only happened to me that one time.
However there are a lot of other bugs present as you will eventually discover.
The Phoenixsuite_CN.msi is in Chinese, so if it does not install just try again by pressing other buttons ;D. The first time that I used the zadig_2,5 utility the scope came up as an unknown device and I had to re-install Phoenixsuite again and reloaded the win driver with zadig before it showed up correctly.
Here is the link to download the platform tools.: https://fil.email/7UJkVuFZ
Best of luck!
Disclaimer: You use these at your own risk if it does nor work, although according to them the Allwinner Controller is unbrickable.
If anyone can figure out how to get the system info back again please let us know.
-
In my scope the software version is shown as 20201127.01
When I contacted hantek and my dealer they send dso3kb_20201026 saying it's the latest update. Which one is actually the latest version.
-
It seems they will have plenty of HW revisions!!! :scared:
(https://i.imgur.com/CfHsKMw.jpg)
-
Hi jobitjoseph1
So it seems yours is later than mine.
Could you please upload it here so that I also can have the latest version.
When I do the platform tools low level it also shows on mine as 20201127.01 and mine is 20201118.01, so it must be integrated into the platform tools.
I just want to make sure I have the latest update on a stick.
Thanks.
-
Just make sure to pack it to a .zip or .rar.
They do not aloud .upk for uploading.
-
Hi jobitjoseph1
So it seems yours is later than mine.
Could you please upload it here so that I also can have the latest version.
When I do the platform tools low level it also shows on mine as 20201127.01 and mine is 20201118.01, so it must be integrated into the platform tools.
I just want to make sure I have the latest update on a stick.
Thanks.
Hi, frequency and time period measurement fixed with new firmware . Please find it in the attachment.
-
I found a bug on this update 20201207.01 after installing it.
While measuring a signal from the AWG. if I switch the scope to autorange, when I increase the frequency from the Gen, the scope freeze.
I then rebooted and after this the Auto Set did not work anymore.
I then went back to autorange, pressed auto set again and this time it worked.
Another thing that bothers me, if there is an AC signal present on a DC level and I want to measure just the AC signal, when I switch the input coupling to AC, as soon as I press Auto Set, it jumps back to DC and measure the DC value.
Its impossible to measure a small AC waveform, such as an audio signal, which rides on DC level by using Auto Set.
Auto Set should not switch the Input Coupling. That is why I tried autorange to see if I could do it with that.
-
In a way I am glad that they delayed shipping my scope, the latest shipping date is now December 28. Hopefully by then they will fix all these stupid bugs, although I am not holding my breath.
-
You should write them informing of this, @cmaass
-
Banggood shipment of the DSO2D10 was postponed again, now to January 4.
-
I did inform Hantek Support of the Bug.
-
After reporting the Bug to Hantek they've sent me the latest update. Download beneath.
I will try to upload the platform tools to filemail again.
It is a very large file that is why it cannot be posted on this forum.
Will post the link later on.
-
After reporting the Bug to Hantek they've sent me the latest update. Download beneath.
I will try to upload the platform tools to filemail again.
It is a very large file that is why it cannot be posted on this forum.
Will post the link later on.
the bug fixed with this update?
-
They said so yes, but I still have to check if it is fixed.
Did not load the update yet.
-
OK, I uploaded the new firmware. Firmware is now b000.
I now even found more bugs on the Autorange.
The Scope freeze under various circumstances which is not consistent, it changes.
Sometimes it freeze when I switch on the AWG, sometimes when I change the AWG frequency, etc. etc.
Also the number of cycles that it displays is sometime up to ten, sometimes only five and so on.
As soon as I want too use Autorange on single period it sometimes freeze.
The input still switches to DC when pressing Auto Set.
They told me it is supposed to do that, which I cannot believe.
It is stupid,it should not.
Below is a new link to download the platform tools.
It is only available for 7 days.
Just follow the instructions in the readme_English.docx file in the platform tools folder.
I just want to add, after I used the platform tools whenever I press the System Info function key in the Utility Menu it no longer shows the Model number, Serial number and Hardware info, those are undefined.
It only shows the Software and Firmware numbers.
What I found found was that after I loaded the Android driver with sunxi-fel uboot images/uboot_fastboot.bin , when I ran the cmds.bat file , when the scope rebooted it freezed,
I then switched the scope off and on again by pressing the button underneath while switching it on. (I used a matchstick to press the button, that way you cannot short out anything.)
After that I ran the cmds.bat file straight away whithout using sunxi-fel, since the Android file is now already present. It then booted without any problems.
If it shows as a Winusb device under Device Manager with the driver info as you saw in the Zadig-2.5 utility, you can just use the cmds.bat file whenever the scope freezes during rebooting and if you are unable to reload the update file. Although it only happened to me that one time.
The Phoenixsuite_CN.msi is in Chinese, so if it does not install just try again by pressing other buttons ;D. The first time that I used the zadig_2,5 utility the scope came up as an unknown device and I had to re-install Phoenixsuite again and reloaded the win driver with zadig before it showed up correctly.
Here is the link to download the platform tools.: https://fil.email/OQeqFVAX
Best of luck!
Disclaimer: You use these at your own risk, if it does nor work, don't blame me, although according to them one cannot brick the Allwinner Controller. I don't know.
If anyone can figure out how to get the system info back again please let us know.
-
OK, I uploaded the new firmware. Firmware is now b000.
I now even found more bugs on the Autorange.
The Scope freeze under various circumstances which is not consistent, it changes.
Sometimes it freeze when I switch on the AWG, sometimes when I change the AWG frequency, etc. etc.
Also the number of cycles that it displays is sometime up to ten, sometimes only five and so on.
As soon as I want too use Autorange on single period it sometimes freeze.
The input still switches to DC when pressing Auto Set.
They told me it is supposed to do that, which I cannot believe.
It is stupid,it should not.
Below is a new link to download the platform tools.
It is only available for 7 days.
Just follow the instructions in the readme_English.docx file in the platform tools folder.
I just want to add, after I used the platform tools whenever I press the System Info function key in the Utility Menu it no longer shows the Model number, Serial number and Hardware info, those are undefined.
It only shows the Software and Firmware numbers.
What I found found was that after I loaded the Android driver with sunxi-fel uboot images/uboot_fastboot.bin , when I ran the cmds.bat file , when the scope rebooted it freezed,
I then switched the scope off and on again by pressing the button underneath while switching it on. (I used a matchstick to press the button, that way you cannot short out anything.)
After that I ran the cmds.bat file straight away whithout using sunxi-fel, since the Android file is now already present. It then booted without any problems.
If it shows as a Winusb device under Device Manager with the driver info as you saw in the Zadig-2.5 utility, you can just use the cmds.bat file whenever the scope freezes during rebooting and if you are unable to reload the update file. Although it only happened to me that one time.
The Phoenixsuite_CN.msi is in Chinese, so if it does not install just try again by pressing other buttons ;D. The first time that I used the zadig_2,5 utility the scope came up as an unknown device and I had to re-install Phoenixsuite again and reloaded the win driver with zadig before it showed up correctly.
Here is the link to download the platform tools.: https://fil.email/OQeqFVAX
Best of luck!
Disclaimer: You use these at your own risk, if it does nor work, don't blame me, although according to them one cannot brick the Allwinner Controller. I don't know.
If anyone can figure out how to get the system info back again please let us know.
For me it never freezed. But with AWG on auto set doesn't works properly ( works fine with square wave out) but with any other type of wave form auto set is not working properly, especially at lower frequencies. With higher frequencies ,ie MHz range it's works.
-
Hi jobitjoseph1
Do you mean you did the platform tools. If so did did you run cmds.bat straight after loading the Android driver with sunxi-fel.
If I do that my scope,when it reboots, get as far as the 2nd Hantek logo then it does not boot any farther.
I have to restart it with pressing the button underneath and then run cmds.bat directly.
Is your System Info still displaying the model no etc.?
Mine displays everything as undefined, except for the software and firmware versions.
I still have a lot of problems with my Autorange setting.
-
Hi jobitjoseph1
Do you mean you did the platform tools. If so did did you run cmds.bat straight after loading the Android driver with sunxi-fel.
If I do that my scope,when it reboots, get as far as the 2nd Hantek logo then it does not boot any farther.
I have to restart it with pressing the button underneath and then run cmds.bat directly.
Is your System Info still displaying the model no etc.?
Mine displays everything as undefined, except for the software and firmware versions.
I still have a lot of problems with my Autorange setting.
Hi cmaas
I was talking about the dso3kb_20201221 update. The bugs you have mentioned .And after posting the previous reply, my scope just frozen when I pressed single seq button. As you mentioned earlier this build has more bugs than the previous one , the bugs aren't even consistent
-
Banggood shipment of the DSO2D10 was postponed again, now to January 12. This is a JOKE, already more than a month pass their original shipping date! I suspect it's Hantek problem not Banggood as they are trying to fix all their bugs.
-
Exactly jobitjoseph1, I find new and different bugs every time I try to use the scope.
If you guys get any bugs you can report it to support@hantek,com, they send it to wangshuang@hantek.com. This person will definitely get back to you and then you can email directly to him. but please send first to support.
He is very helpfull, it's him that has sent me all the software and updates.
-
Anybody received any new update?
-
No, no updates.
I saw that eventually Hantek is now displaying the DSO2000 series on their website, but the only download is a user manual so far, no firmware updates or any other software.
-
ahh, another Hantek to hack. I don't have it yet (still having the 10yrs old Tekway/Hantek, frack that, it works still) and probably will not buy it now (as my Siglent works better), but maybe will take a look on firmware.
To decrypt firmware use dso3000c as passpharse, e.g.
cmd.exe /C echo dso3000c| gpg --batch --passphrase-fd 0 --output decrypted.tar.gz -d dso3kb_20201207.upk
@cmaass can you upload the platform tools once again somewhere?
-
but maybe will take a look on firmware.
looks very similar to what i saw all the years on hantek, one can easily create own update file to dump everything to usb:
- create your own do_update.sh
- leave the "special" file in update, the firmware updater checks for it and let you do whatever you wish as long the file is there
- leave the manifes.xml as is, this one is new thing after Hantek changed their ui things, they even didn't edited it (it shows still dso4000 series)
- finally edit the upend file, to have only these files (in root of fw update file) and dirs you really have
- encrypt it with gpg and the dso3000c passpharse, tar/tar/gz and you're done with custom firmware update
-
Mine displays everything as undefined, except for the software and firmware versions.
yeah, probably something missing, in the bin file there is "undefined".
(https://www.eevblog.com/forum/testgear/new-hantek-dso2x1x-models/?action=dlattach;attach=1148514;image)
My proposal, make firmware update which will dump everything, and let someone else to dump his/her DSO, so you can compare to yours.
-
@tinhead
Right, will upload the platform tools once again to filemail
Will post the link as soon as it is finished.
-
OK, here is the download link for the Platform Tools.
It's only valid for seven days.
Remember to read the readme_English.doc file how to use.
Use at own Risk.
https://fil.email/b1bkxGX2
-
Either Banggood or Hantek, probably the latter have major problems shipping these new Hantek DSO2X1X scopes. I ordered mine on December 8 from Banggood and they have pushed back the shipping date more than a dozens of times, now it is "scheduled" for February 4. I am NOT holding my breath for this shipment date either. Banggood also raised slightly the prices of these scopes since December.
It looks like Hantek rushed the initial shipments of these scope and now they have stooped it completely. I believe they are trying to fix all their problems before resuming shipments.
-
It will be decent if you write your posts in the language the topic starts in
Будет вежливо, если вы будете писать сообщения языком топикстартера
Буде дуже ввічливо, якщо будете писати повідомлення мовою топікстартера
-
:clap:
-
I've got one of these (DSO2D15) on order as my first scope since College. Hoping it arrives today. Been curious about what's inside, considering the claimed specs vs unusually lower price than the 5000P series this unit claims to replace. So far I've only found few internal pics on an aliexpress review. Looks like Hantek has saved quite a bit on the design by going with some really off-brand chips. I'm most curious about their choice for an ADC in this unit.
Looks like an Allwinner F1C200s with an FPGA marked Lemontree 2090 along with a few other mysteries in there.. Tried to track down any information about this "Lemontree" FPGA chip, but it seem to be new to Hantek with this DSO2 series. Only references I could find were Hantek's Register Product links on hantek.com going to a "lemontreex" site that looks to be a potential online shop from Hantek themselves. I'm curious if Hantek has created their own "lemontree 2090" FPGA or rebadged something else low cost to fill the role.
That Allwinner chip itself looks interesting to explore. Even considering its datasheet mentions native touchscreen and video out support within the chip itself. Not expecting much as an entry level bench scope, but its implied data-sheet specs are impressive for the class / features / cost. Looking forward to a closer look.
Here is that "LemonTree2090" FPGA image saved from that online review I found:
[attachimg=1]
-
My new Hantek DSO2D15 arrived today after a few postal delays. Most issues I could find (so far) were greatly improved by applying the latest firmware update.
Of course its an entry level scope, but still offers far more than I could ever need at the moment. As long as I avoid pushing its maximum limits, it works exactly as expected for the price. It runs totally silent without any fans or heatsinks inside and only becomes slightly warm overall. Looks to be quite power efficient running off a simple 5V, +8V and -8V internal power supply. Most warmth seems to come from the power supply area. build quality looks pretty good with overall cost savings all kept within the reduced and simplified mainboard components.
Data acquisition engine looks quite unique, with Two big chips tightly interconnected together. The front ends feeds directly into the first large chip with all the numbers rubbed off. Only the last digit "3" remains. Two tiny caps sit directly across the input pins on the chip. everything links into the Lemontree 2090 that also controls the front panel inputs by the looks of it.
Can't beat the price for features considering the wavegen is also included, I'm more than happy to trade quite a bit of raw performance for all the same features, silence and efficiency at a such a lower price point, as I'm only using it for very basic troubleshooting. I could totally see this unit fully moddable to run from a 12v battery power, there is plenty of extra room for some nice big cells in there.
-
I'll break out the DSLR after work and try to get some good images. There are also a few small items on the underside of the board from what I can see.
U18 is a LMH6702MA with a National Semiconductor logo - (1.7-GHz Ultra-Low Distortion Wideband Op Amp)
U35 looks like potentially capture memory with its details scrubbed off.
-
@Algoma, I am curious when and from whom did you order your scope? I ordered mine from Banggood more than a month ago and still it wasn't even shipped.
-
@Algoma, I am curious when and from whom did you order your scope? I ordered mine from Banggood more than a month ago and still it wasn't even shipped.
Aliexpress Seller "Hantek Official Store"
Order was on Jan 19 - Their note said restock was on Jan 21, 2021,
Shipped Jan 22 2021 free shipping via DHL to Canada
Received Jan 26, 2021
Date of manufacture sticker on the unit said Jan 4, 2021, Firmware was still older 2020 version and needed to be updated to the Jan 2021 update.
-
When I bought my DSO2D10 through Aliexpress there was only one seller that had it in stock at that time and only the DSO2D10.
The DSO2D15 was not available yet. So i bought the D10.
A you can see on the attached photos the mainboard is exactly the same as that of the D15. The only difference is the clock number.
Here one can nearly see the number of the chip that goes with the Lemontree chip.
So I suppose the only difference is the software.
Where are the hackers so that I can change mine to a D15. ;)
-
Where are the hackers so that I can change mine to a D15. ;)
The numbers on your u35 (AWG DAC) are still intact, see if you can get a closeup of that (Above the Lemontree) along with the U18 Op Amp beside it.
Even that that big ADC is nearly readable still. I note that your D10 is missing the tiny little caps they tacked across the input pins of the ADC in my DSO2D15. The flux residue indicates this was a manual adjustment of the latest revision.
-
@Algoma. The DAC is a DAC902E.
Try to check the Square wave with your test probe switched to x10 and also earth the probe as well to the calibration signal earth. That should get rid of the ringing.
Max Frequency of the Square wave from the AWG is 10 MHz.
Do you have any problems with your Autorange settings.
I have lots of bugs with the 20210105 firmware. Inconsistent freezes for example.
The frequency measured on the DVM also changes fro MHz to KHz when I select Autorange.
The CH2 DVM measures in mVolts instead of volts.
CH1 DVM does not show the minus sign.
Its also difficult to auto measure a small AC signal that rides on a DC level since the scope locks to the largest signal in Auto Set mode and Autorange mode. Even if one selected AC coupling it will automatically switch it to DC coupling which is stupid. It should remain at the input coupling mode that one selected, as with an Analoque scope which has a hardware switch for that purpose.
Another thing that I don't like is when one set the trigger mode eg. to Video, it switches back to Edge when one presses Auto Set.
I informed Hantek Support about these but I don't know if they will do anything about it.
-
@Algoma The OpAmp U18 is a LMH67.
-
@cmaass Your PCB date code indicates 2034 (2020 Week:34) (Aug. 17, 2020-Aug. 23, 2020) - considering Initial Design Date 2020.8.17 marked on the board, yours seems to be from one of the very first batches.
I was feeding the output of the Wavegen into a BK Precision1590 100Mhz Analog Scope at 10X. Its only the Squarewave that showed the ringing. its likely my lack of proper measurement method. I think Dave had presented a video on this topic already. The December firmware had the square wave timing jumping the pulse width between two positions, like it was intermittently varying the duty cycle, the January Firmware update had resolved this.
-
Considering the Preference for TI parts, and the remaining partial digits in the image from @cmaass
I'm tossing in a guess of ADC08D502CIYB for that ADC. 500Msps, two channel. it seems to fit, but it doesn't meet the Single Channel 1Gsps specs.
I would expect to see a ADC08D500CIYB with its Dual Edge Sample Interleave feature, for the 1Gsps single channel mode. They're pin compatible, But the 502 would only have 500Msps in Single channel mode. Cost savings yes, but wrong part. Could that be a difference between the 100Mhz model and the 150Mhz model? or they put in the wrong part on the early models thinking of a bit of cost savings? .. that or the scratches just look like a 2 instead of a 0
Looking at the datasheet, It's quite a powerful ADC choice for this scope.
The Data acquisition engine alone shows so much potential, it just needs to be realized with software improvements. Considering the cost of some of these parts, Hantek must be currently selling these units on a razor thin margin. Seems like a great deal for this class of scope, especially given the Wave Gen feature.
-
Recently I have been considering purchasing the Hantek 51XX version but luckily fell upon this thread for the newer DSO2X1X which is seems obviously to be a better deal.
Can anybody suggest the best deal available out there including any possible discount coupons I may be overlooking?
Also what is the most recent operating system for this scope?
Regards
-
@xuraax
Banggood's new user coupon has the best discount, but their price has gone up due to demand. Generally Aliexpress sellers seem to have the fastest shipping options available, but watch DHL for their hidden brokerage fees after shipping, they usually add another $25 at delivery. I took DHL shipping cause I wanted to have it sooner, no matter the cost. I fully expect these to start appearing from Amazon sellers soon as stock gets into their hands.
http://hantek.com/products/detail/17182 (http://hantek.com/products/detail/17182) The latest firmware (Operating system) is available from Hantek's site, currently dated Jan 05, 2021 for the latest release.
The hardware looks good, while the software remains a work in progress. Its pretty easy to update the software from the front panel USB as improvements are released.
-
The best deal I found out to be from Banggood using this https://couponsfromchina.com/hantek-dso2d10-digital-oscilloscope-coupon-price/ (https://couponsfromchina.com/hantek-dso2d10-digital-oscilloscope-coupon-price/) 15% off coupon. The only problem is that they don't have any scopes in stock and I have been waiting since before Christmas for shipment as you can read in some of my previous posts. If you find anyone that still have these scopes in stock then they are Hantek's initial shipment which seems like they halted since then.
I believe the initial release of these scopes had some Hardware problems which cannot be fixed with software update by users and that is the reason for the shipments halting. At this point, I would wait with any new orders to make sure you get their latest versions.
-
I've updated my reply above about the ADC in this scope. There are two models of the chip, one ADC08D500 that meets the claimed specs. And another lower cost version (ADC08D502) that lacks the feature needed to achieve the 1Gsps in single channel mode. Trouble is that @cmaass 's picture appears to be the 502 in their first batch scope.
Is there a test anyone can think of to verify the actual single channel Sample rate?
I wonder if this could be related to the production halt.. getting the right chips in there, The two models are pin-compatible. could also explain why the model numbers are scratched off :-BROKE . The wholesale cost difference per 1K chips looks to be only $30ea cost savings between the two models. Or the difference between the D10 and D15 models.
???
?? D10 ~ 2x500Msps (100Mhz) = "1Gsps"
?? D15 ~ 1000Msps (150Mhz)= 1Gsps (@+$30)
???
-
Yes my DSO2D15 has 1Gsps in single channel mode, Answered my own question.
1) Set Display set to Dots to show sample points
2) Capture Single Sequence at 100ns / Div (Less than this, and it shows vectors instead of dots when you zoom in)
3) Zoom in and check the sample dots at 2ns/div
500Msps has sample period of 2ns (One dot per Divsion when viewed at 2ns/div)
1Gsps has a sample period of 1ns (Two dots per division when viewed at 2ns/div)
Must be the ADC08D500 in there.
-
I am looking for a beginner scope and came across the new Hantek DSO2X1X family. While comparing features I noticed that the feature sets listed on the web site and aliexpress do not list waveform capture rate. I found something in the manual in the downloads tab on this page http://www.hantek.com/products/detail/17182 (http://www.hantek.com/products/detail/17182)
The closest thing I have found in the manual was "Acquisition Rate, typical" which gives this description "Up to 2000 waveform per second per channel (Normal acquisition mode, no measurement)"
Can anyone confirm what the waveform capture rate on these scopes actually is? If it is really 2000wfms/s, isn't that really bad? Even the 6 year old Rigol DS1054Z does 30,000wfms/s.
Thanks,
David
-
@dmulligan Yes, the rate is lower compared to other scopes due to the Allwinner main CPU, but plenty fine for this class of scope. Its already far beyond the refresh rate of the display, and has minimal effect on single triggered captures. Waveforms per second are mostly useful for capturing unusual, rare and intermittent events. basically indicating how many times per second the main CPU can look through current data for interesting events and statistics while troubleshooting glitchy complex high speed circuits.
Simply measuring responses times and looking at waveforms have minimal need for the waveforms/s statistic. 2K waveforms is still quite a bit to look through in one second. There are dedicated special hardware triggers modes that make up it, by letting the Capture engine make the decision of what to trigger on and send only those to the CPU for review.
-
@upsss,
thank you for your reply. How would I know when the technical issues have been fixed?
-
I prefer HANTEK DSO4104B, those accessory are as same as agilent, looks perfect.
I heard about Hantek was the OEM of Agilent Oscilloscope.
Does somebody know how to hack these serial, the bandwidth and memory spec is a disaster |O.
-
@Algoma Your response led me to find an interesting article called "The Truth about Oscilloscope Waveform Update Rates (and why not to fall for it)". Obviously I need to do some more reading before I can choose the right scope for me.
Thank you.
-
@xuraax, I would wait until Banggood start to ship these scopes again. Like I said, I ordered my DSO2D10 more than a month ago and I am still waiting. Their latest shipment date is Feb. 4 but I would not count on that as they changed it in the last minute several times. They promised to notify me once they actually ship it so then I can post it here.
-
@upsss. OK. I will. In the meantime, this was the first time I heard about the site couponsfromchina.com. Are there any similar sites out there I should know about? thanks
-
I wouldn't wait too long, if this is the scope you choose. A pre order sould be fine. Or pick and AliExpress seller that already has them in stock. I've been seeing the prices rising since I got mine. slowly, but they're already $20 more than one week ago.
-
It looks like Banggood has now 25 prerecords for the DSO2D10, when I ordered mine they had only 2 or 3.
-
Bought mine (2C10) from Aliexpress "Hantek 'official' store".
Received it in a bit more than one week.
-
@Mark5 You're the first to report having a DSO2C10, suppose you could take a look inside and perhaps post a photo of that board. I'm curious what the differences might be to the D Series with / without the AWG, and if your board might still have the same hardware as the DSO2D15.
-
I'll try to do it this week end.
My bet is it's the exact same board as the 2D10 (and probably 2D15).
-
You can’t argue. Photos are already there. The boards are the same. With a good cable, my C10 has a frequency range of up to 200 MHz.
-
Yes my DSO2D15 has 1Gsps in single channel mode, Answered my own question.
1) Set Display set to Dots to show sample points
2) Capture Single Sequence at 100ns / Div (Less than this, and it shows vectors instead of dots when you zoom in)
3) Zoom in and check the sample dots at 2ns/div
500Msps has sample period of 2ns (One dot per Divsion when viewed at 2ns/div)
1Gsps has a sample period of 1ns (Two dots per division when viewed at 2ns/div)
Must be the ADC08D500 in there.
Sorry I didn't understand In DSO2C10 ADC08D500 or ADC08D502?
-
Most likely the ADC is the Texas Instruments ADC08D500
A previous picture from an early DSO2D10 seemed to show the other ADC model due to a few questionable scratches. The actual sample rate can be checked by looking at the sampled dots at the fastest time setting of 2ns/Div. At 1GSa/S the scope should record a data point every 1ns, and have some vertical variation to show that its not just averaging in an extra dot.
The datasheet shows ENOB @ 250 MHz Input 7.5 Bits (typ) .. That ADC can handle far more than its being used for, before it hits its limits.
-
I received my DSO2C10 last week and had a look inside, it has the same board as the others we've seen (eg. DS02D10, DSO2D15), the silk screen says 'DSO2D15_V1.0 2020.8.17'. The part number is scrubbed off one of the large ICs.
Some components are missing around the EXT TRIG/GEN OUT connector which I guess rules out a software change to enable the wave gen (without adding the missing parts). Edit: there are more missing parts above the main ICs.
-
Strange, the top photo must have a relay. Everyone has it.
-
Luckily, I was not holding my breath. New Banggood's shipment day moved again, now it is February 13. Next week it will be TWO months since my original order. Last time I checked they had 28 preorders of the DSO2D10.
I believe when Hantek finally starts shipping again these scopes (ver. 2.0), the new hardware will look a lot different.
-
I believe when Hantek finally starts shipping again these scopes (ver. 2.0), the new hardware will look a lot different.
That is a possibility. I have asked Hantek and their answer was that the models DSO2D10 and DSO2D15 are out of stock, apparently they (and many other manufacturers in China) are having trouble sourcing ICs for their products. The forecast is to start resuming the deliveries of these models in May.
-
The forecast is to start resuming the deliveries of these models in May.
Who said that?
-
The Aliexpress vendor I ordered and received mine from, now shows 180+ in stock for the DSO2D15 and DSO2D10. Thats +100 more from last week, and considering their page shows 170 orders.. Stock is moving. its likely that Banggood is fighting limited logistics on a large shipment for a far lower margin. It could be the supplier is fulfilling higher value direct orders first to make most profit on limited supply.
https://www.aliexpress.com/item/1005001844918818.html (https://www.aliexpress.com/item/1005001844918818.html) (Beware that DHL often adds a hidden brokerage fee on delivery.) .. but there is stock available, unfortunately now +$50 more than I paid two weeks ago.
-
Who said that?
My contact at Hantek
-
@Algoma,
The AliExpress site is interesting but I am worried one cannot use Paypal for safety. Unfortunately since Covid, buying from abroad has been quite erratic and I am not just referring to China but also to countries in Europe which for me are a lot closer to home. Many times I had to refer the issue to Paypal for a refund for items not delivered. What do you think?
regards
-
@xuraax Banggood still has the best deal, especially if you get ahold of the discount coupon that was posted earlier. Simply need to wait for them to get stock. The Aliexpress vendor simply offers DHL shipment for those that are willing to pay the extra to have it delivered within a week.
-
The problem with AliExpress, at least here in the US is that they are now charging US State Sales Tax which is illegal, they never did that before. They don't have any authority to collect US State Sales Tax, they do NOT give back these charges to the the US States and it is just a pure markup by AliExpress. Banggood does NOT charge these fake taxes and depend on the State this "Tax" could be as high as 10%.
-
@Algoma. When I tried to get to Bangood through the coupon link provided earlier Ban good ignored the coupon password completely.
In the meantime I found an Ebay seller who offered a decent price with reasonable DHL costs. The main problem here is that he asked me to wait until the 24th citing the Chinese New Year as the reason for the delay. I wonder if he was being honest?
-
Strange, the top photo must have a relay. Everyone has it.
I suppose the relay is used to swtch between AWG output or Trigger Input. That is why it is missing in the C series.
-
Hi there! im new here on EEVblog, I'm posting here because I'm interested in buying the DSO2D15. I have read all the other posts and I figured they went up in price over the past month (~70USD). Should I wait with preordering one and wait untill they get cheaper or should I place my order anyway?
Thank you in advance!
Vincent
-
@Vincentd The price is unlikely to go down until Banggood gets a restock and the other vendors need to compete for sales.
Banggood seems to have been raising their sell price as well.
-
@Algoma Thanks for your reply! I will have to think about it then if I'm going to wait for it until they get an restock or just buy it for an higher price and get it as soon as possible.
-
Strange, the top photo must have a relay. Everyone has it.
I suppose the relay is used to swtch between AWG output or Trigger Input. That is why it is missing in the C series.
So, without a relay, the external trigger is connected directly through the L11 jumper and is activated by software. With an internal trigger, the connector is connected via a relay to the generator output. On my C10, the relay is present and works when an external trigger is selected.
-
For anyone that owns an DSO2D1X, how does the AWG perform? Are the signals still good at 25Mhz? As example, does the square wave signal get distorted at higher frequency's? Thank you in advance!
-
@Vincentd Only the sinewave gets up to 25Mhz Everything else tops out at 1, 5 or 10Mhz. I think the limitation comes from the DAC and OpAmp being on the other end of the mainboard near the FPGA that drives it. Seems like such a long signal path before it reaches the BNC output. The signal looks a bit unsteady when the scope measures its own output, but the signal appears perfectly fine when viewed on an analog scope.. I think there is a bit of timing in the software / FPGA that can be improved. The 10Mhz Square wave looks fine on my analog scope as well (BK Precision 1590 @ 100Mhz)
Sin 0.1Hz~25MHz
Square/pulse 0.1Hz~10MHz
Triangular 0.1Hz~1MHz
Ramp/Noise 0.1Hz~1MHz
Exponent 0.1Hz~5MHz
Arb1 Frequency range 0.1 Hz to 10 MHz
Though I'm able to set my ARB to 25Mhz when I haven't created or uploaded any waveforms, it just outputs a steady negative DC voltage at the set amplitude.
I like the ability set a the square wave pulse to specific high and low millivolt levels, along with the offset, and nice slow output pulse frequency. If only it had a duty cycle sweep function.
-
@Algoma, does the Sinusoidal output have any sweep capability?
-
@upsss It does not have a sweep feature in these units. Hantek indicated this was only a feature on their 6000 series.
I can't imagine a basic sweep function (Step through a frequency range over a specified time period) would be impossible to add to the software, considering the hardware available inside this unit. Have the main CPU direct the FPGA to increase frequency of the AWG every few milliseconds. It doesn't have to be that fast of a step.. Timing of the step change is the most complicated bit, and seems to be the primary challenge Hantek struggles with.
I note on my analog scope that adjusting the frequency of the AWG causes it to totally stop output, then initialize a new waveform.. This could be vastly improved in software updates alone.
The hardware engineers at Hantek do a great job for the price point, but the software team needs a bit of improvement. :-/O
-
@Vincentd Only the sinewave gets up to 25Mhz Everything else tops out at 1, 5 or 10Mhz. I think the limitation comes from the DAC and OpAmp being on the other end of the mainboard near the FPGA that drives it. Seems like such a long signal path before it reaches the BNC output. The signal looks a bit unsteady when the scope measures its own output, but the signal appears perfectly fine when viewed on an analog scope.. I think there is a bit of timing in the software / FPGA that can be improved. The 10Mhz Square wave looks fine on my analog scope as well (BK Precision 1590 @ 100Mhz)
Sin 0.1Hz~25MHz
Square/pulse 0.1Hz~10MHz
Triangular 0.1Hz~1MHz
Ramp/Noise 0.1Hz~1MHz
Exponent 0.1Hz~5MHz
Arb1 Frequency range 0.1 Hz to 10 MHz
Though I'm able to set my ARB to 25Mhz when I haven't created or uploaded any waveforms, it just outputs a steady negative DC voltage at the set amplitude.
I like the ability set a the square wave pulse to specific high and low millivolt levels, along with the offset, and nice slow output pulse frequency. If only it had a duty cycle sweep function.
Thanks for the detailed explanation! I really appreciate it!
-
Would it be possible, by adding an extra BNC connector and tapping off at a suitable place in the circuit, to output the waveform gen signal at the same time as using the external trigger?
-
Received a 'VIP' discount link from Banggood and managed to order the DSO2D15 for under £180.00. Still somewhat dubious if and when it will ever ship but williing to take a bit of risk here as I can't afford much more for a scope. Will see after golden week if the order gets cancelled or not.
-
New firmware released today.
Will try it tonight.
-
A few kilobytes smaller than the January update, with yesterday's Date stamp (Feb23,2021), no release notes. Looking forward to testing for improvements.
So far the scope has done everything I've asked of it, and any quirks are quickly resolved with the restore defaults button.
-
@vistorik Did you populate the missing parts? Do you have a list of the parts and their approximate cost?
-
Tested the Feb 2021 firmware update, Noted improvements with sample rate selection, now keeping a 1Gsa/s at 40K memory points instead of dropping in half. Bit more responsive scrolling and moving waveforms. seems alright so far.
Trigger and display refresh seemed a bit changed in some way.. more 'reactive'?.
Still a bit questionable trying to navigate through single shot captured waveforms.. Overall you need to fit everything just right before taking a sample. Zooming and scrolling for additional data is unpredictable and seems to drop data that could have been sampled. It auto sets the sample rate to best fill the display, instead of capturing everything it COULD capture into memory. Its better to take another new sample than Trying to pan and zoom through data.
Measurements are based on what is displayed on screen instead of what is in memory. zooming in and out will change the calculations to be based on what is only DISPLAYED on screen instead of what is in capture memory.
-
@vistorik Did you populate the missing parts? Do you have a list of the parts and their approximate cost?
There is no need to populate the missing parts, if all parts of the AWG are already on the board. All you need to do is to modify the contents of the device memory WINBOND 25N01GVZEIG. It could be done with using eg of the CH341A programmer and the program NeoProgrammer. The picture shows that it is possible.
Any clue on who did that and what he modified to acheive this ?
-
Did the bandwidth increase from 100MHz to 150MHz when you changed the model number?
I wonder if there are other valid model numbers.
-
FWIW, here's the "scrubbed" version of the update script.
#!/bin/sh
WORKPATH=/dso/var/run
echo "-------------------update start------------------"
cp $WORKPATH/package/root/* -rf /
cp $WORKPATH/package/fpga_i2c_kb.ko /dso/etc
cp $WORKPATH/package/spi-fpga-tn652.ko /dso/etc
cp $WORKPATH/package/load_fpga_kb.sh /dso/etc
if [ ! -d /dso/app/home/ref ]
then
mkdir /dso/app/home/ref
fi
if [ -f /mnt/udisk/do_other_update ];then
chmod +x /mnt/udisk/do_other_update
/mnt/udisk/do_other_update
fi
echo "-------------------update end------------------"
sync
sync
sync
I wonder if there's something to do with the "do_other_update" (like dump the current full firmware or modify some parameters).
-
I just reread this thread and it seems that Hantek sometimes populates the relay X1. Does anyone have any guesses as to which units have this populated? Has anyone compared serial numbers or production dates?
-
Early production had all components populated. A more recent DSO2C10 didn't have them populated.
So far it only appears to be missing the DAC, OpAmp and Relay. Their related passives are already in place. While its still cheaper to buy the D10 model with them already populated, it looks to be quite possible to add the extra features as an DIY upgrade.
-
Bought 2c15 a few days ago.
There are no missing parts inside.
There is a 2D model part mentioned in a photo uploaded by another member of the previous article. :-+
After the firmware update, it has been changed from a012 to b000.
Thank you for uploading the firmware in the previous article. :clap:
The frequency measurement is close to 200 MHz. Of course not -3db.
This product is really good for the price. :-+
-
Has anybody who had placed an order back in December received their scope yet?
In the end I ordered mine through Aliexpress mainly because for the same shipping cost delivery was with DHL whereas Banggood didn't even commit to tracked.
-
I canceled my order from Banggood after waiting more than 2 months, I got tiered of their delivery lies!
-
Before going with Aliexpress I too ended up cancelling my Banggood order for the reasons mentioned above.
Aliexpress were delaying delivery too for me but after pointing out to them that their website showed a stock of above 70 they sent a mail saying that the scope was shipped...only to receive another mail a few hours later saying that the shipment will be delayed because "DHL considered it a dangerous package". Of course I don't believe this.
-
It is all BS, they are all LIARS! Who was the Aliexpress vendor you ordered from?
-
My order is with Aliexpress direct. I don't think they operate like EBay.
-
On Aliexpress there are at least a dozen different vendors that sell these scopes. They all have different prices and shipping charges, at last that is how Aliexpress works here.
-
Yet another update for the 2X1X series( 03/04/2021).
I took a quick glance at what's inside the archive and found an unusual file named system.inf.
I wonder if it's used and for what.
-
@upsss. You are right. I guess since I had assumed that Aliexpress is a single supplier I had not gone past the first vendor that came up following the search. Mine goes by the name " Hantek Direct" so I too am probably in trouble.
-
Banggood is is most like and Asian version of Amazon, They're a warehouse reseller with they own supply chain and support.
Aliexpress is more of an open Marketplace for any Seller / Reseller, More like Ebay. Except Aliexpress handles and holds the payment transactions in escrow, pending confirmation that you've received your product, and resolution of any disputes.
While Banggood has far better support for any issues. Aliexpress has their own guarantees that the order should be resolved as agreed. If you stick to the official vendors with high ratings you shouldn't have any issues. Just avoid the too good to be true deals on Aliexpress. Don't get the cheapest, go for the second cheapest at least. Or search for the one that has the most orders and reviews.
I had Ordered my DSO2D15 from Aliexress Seller: Hantek Official Store https://www.aliexpress.com/store/2792111 (https://www.aliexpress.com/store/2792111)
They now show over 260 orders these Scopes, and have plenty of stock, Simply beware of that DHL "free" shipping due to the hidden delivery fees DHL likes to add on.
-
@Algoma. Did you actually receive the scope from this vendor in the end? I paid about $35 for DHL shipping so don't expect to more on arrival besides local taxes.
-
Some progress here.
The updater runs as root (which means that it should have full rights on almost everything).
There's a file (/cache/system.inf) which contains the model number (DSO2C10 on mine)
Here's what the file looks like :
[machine]
Model=DSO2C10
Vendor=undefined
Product=undefined
Manufacturer=undefined
Serial=CN0000000000000
[version]
Pcb=000.000.000.000.000.000.000.000
Keyboard=undefined
[language]
Lans=65535
Language=2
[add]
Start=28
Update=0Note that this file is updated each time the DSO is booted.
I suspect that 2DXX models have a Pcb=000.000.000.000.000.000.000.001
I dumped the whole firmware but alas, my USB key decided to die before I can copy all the files.
For those interested, here's the mtd mapping :
dev: size erasesize name
mtd0: 00300000 00020000 "boot"
mtd1: 00a00000 00020000 "cache"
mtd2: 00200000 00020000 "dtb"
mtd3: 00600000 00020000 "kernel"
mtd4: 04f00000 00020000 "rootfs"
mtd5: 01c00000 00020000 "data"
I'll try to change the model number on mine this week end.
-
@xuraax on page 3 I listed the order, shipping and delivery dates of my order. It was generally within a week, actually most of the shipping time was due to delays through Canada Customs in Toronto.
Aliexpress Seller "Hantek Official Store"
Order was on Jan 19 - Their note said restock was on Jan 21, 2021,
Shipped Jan 22 2021 free shipping via DHL to Canada
Received Jan 26, 2021
4 days shipping by DHL (over a weekend). DHL likes to add their Brokerage fee to the taxes. They're like an airline collecting baggage fees that often exceed the original seat price.
-
@Algoma. I placed my order on the 12th Feb and since I knew this was during the Chinese New Year I did not much mind a certain amount of delay. However, when towards the end of the month I realised they had stock but still had not shipped I brought this to their attention. This is when I received a message with shipping details which was promptly followed by a "retraction" blaming DHL. The Aliexpress web site still shows my order as shipped but the DHL website does not recognise the tracking number the vendor provided.
I am relieved that you finally got yours. At least they are not a total scam. I will give this a few more days and then decide. Thanks for the info.
-
@xuraax If such a shipping issue occurred the sender is responsible to refund you, and open a claim with DHL for THEIR refund of a lost item.
If they've responded via messages in Aliexpress indicating an issue with DHL.. First SCREENSHOT the messages and save for evidence. When expected delivery time expires, immediately open a dispute for refund for item not received. DO NOT close/resolve your dispute, no matter what they ask, beg or plead. You can only ever open a dispute once. Aliexpress will mediate an unresolved dispute and check the tracking. The refund will settle in your favor, provided you give them the screenshots and non-tracking DHL. A vendor will get shutdown if they get too many disputes against them.
Again, DO NOT EVER close your dispute once opened.. ever. or it will auto-settles in the vendor's favor if you are the one to close it. Keep the dispute open, until either they ship you the item, or aliexpress refunds you for non-delivery. The vendor doesn't get paid until you verify receipt, or delivery confirmation time expires.
There are scammy sellers on Aliexpress, especially for high value items.. Check their recent feedback for recent negatives.
-
@Algoma. thank you for your advise. I am giving them till Tuesday to provide me with a real Tracking number which is recognised by the DHL tracking system. After that I will chase for a refund. Why do they do this?
-
Done !
100% software solution.
Unfortunately, my 2C10 doesn't have the required hardware for the AWG.
The way it works, it can also repair 2X1X where the serial/model has been wiped after a full restore.
-
@Vistorik Check your PMs.
-
Learnelectronics has done a review and teardown of the 2C10:
https://www.youtube.com/watch?v=5Pn5Mh791V8 (https://www.youtube.com/watch?v=5Pn5Mh791V8)
-
Anyone who has a DSO1X10 member can 1G sample on a single channel?
If possible, all four models are the same,
and I think the model is divided only by systemware or firmware.
Mine is DSO1C15, but all parts are included
and sampling is shown as 1G for single channel and 500M for dual channel.
I have attached a picture.
-
My 2C10 has 1Gs/s on one channel and 500Ms/s when both channels are activated.
-
The DSO2C10 is only available from China? Will it ever be sold in other regions by distributors?
-
Done !
100% software solution.
Mark5, it works. Thanks a lot for idea.
Lucky you. Yours has the components for the AWG.
-
And once again a new firmware for the DSO2X1X range (dated 03/11/2021).
Edit : Hack still perfectly works with this firmware.
-
And once again a new firmware for the DSO2X1X range (dated 03/11/2021).
Edit : Hack still perfectly works with this firmware.
Could you plz.. share on how you got it working.. I just got mine today and you like to try to get it working also...
Thx ... /Cheers!!!
-
I've installed the new 20210311 firmware... has anyone seen a change log? I haven't been able to find anything.
-
No changelog.
I guess they corrected a few bugs... and introduced some new ones of course.
-
From what I noticed, there are almost no freezes in the auto measurements mode. It hung once, when the voltage on the generator reduced to zero. Previously, it was enough to pull out the cord or press a button and there was a hang.
-
@Mark5,
After waiting for a whole month, I have received my scope today. I am pleased with my first impressions but a bit miffed that only one probe is included.
How can I get some info on what hardware is missing and on how to upgrade software and firmware?
-
Vistorik was kind enough to send me the list of missing components :
DAC : DAC902E
OpAmp : LMH6702
Relay : FD4/4.5-S |428||282| XA0920A
Hope this helps.
-
Parts cost in the US ~$25 not including Tax & Shipping, doesn't look like it is worth the trouble.
-
Parts cost in the US ~$25 not including Tax & Shipping, doesn't look like it is worth the trouble.
I guess those parts are needed for the AWG and since I have the DSO2C10 I don't have them. At the moment this is not a big loss for me.
However I am interested in upgrading the software. From the Hantek site one can download DSO2000Software.rar as well as dso3kb_202120311.rar. How does each affect the scope and can these be uploaded by just putting them on a USB stick? Also with the scope we get a disc which contains an .exe. I have yet to install this since this is a windows file and I normally use Linux. What is the use for this file? Finally reading back through this thread I understand that changes can be made possibly via a CH340 interface but I could not find proper details on how to go about it. Any help would be appreciated.
Thanks in advance.
-
The DSO2000software is, as it's name suggests, a software you have to install on windows that allows you to control the scope from your PC.
The firmware has to be first unrared then put on a USB stick.
You then insert your USB stick in the front USB port and navigate through the scope menu to launch the firmware update.
-
Besides x1, u18 and u35 mentioned above I also note that on my dso2c10, u1 and surrounding components are also missing. Any idea what these parts are for?
-
I don't think so. At least the 1000X series is very clearly Keysight's Infiniivision design, with all it's drawbacks and features.
The Hantek you mention has more memory which I think is impossible with the chip Keysight developed for this line of scope.
A second indicator is in my opinion the sample rate, the 1000X can do 2 GSa/s, Hantek only 1 GSa/s.
Hantek would probably not misss the chance to sell the scope as 200 MHz capable if it could do it.
I think this is just a case of copying the looks. And they'd be silly not to :P
-
u1 and surrounding components are also missing. Any idea what these parts are for?
U1 looks like a LAN port (RJ45 connector) related circuit. :popcorn:
-
I finally had the chance to test this new oscilloscope and I can say I am very pleased so far. It's clearly an entry level scope but it has all the basic functions that most users would need.
It's very usable and I found less bugs in the FW than I would have expected from such a new product from Hantek and the ones I reported, Hantek promptly fixed. Although, I didn't have the time to test all functions, specially the serial decode. Has anyone used this? Does it work well?
The hardware is simple and the board has a lot less components than other models from Hantek, but it does the job. As already pointed by another user, the UI is not the most responsible but it's tolerable, specially considering the price range of this device. Apparently, Hantek is trying to use as many Chinese made ICs as possible. The ADC's marking are completely erased and the main processor is a Lemontree FPGA (???).
The DAC for the AWG had also its marking removed, but I believe it could be the Chinese 3PD5651E (http://www.3peakic.com.cn/En/product/inproduct/catid/147/id/189.html). This is the same IC used in their handheld scopes (HT2000) and it's a 10bit DAC. That would explain why they are trying to hide it's specs. It's claimed the awg has a 12bit resolution, but the DAC is only 10bits. They must use some software trickery to increase the resolution. It could be the same reason why the ADC's marks were erased. Maybe they are using a cheaper and slower DAC and overclocking it to get the claimed 1GSa/s specs. Hantek made that with the HT2000 as well.
The color display is very nice but the view angle is a little poor. The big fonts make it easy to read the information on the screen. The push buttons are good enough but the rotary encoders fells cheap and a bit dicky, time and use will tell how reliable they are.
All in all, it's a fairly decent oscilloscope, considering that Hantek advertise it as "cost-effective economy" and some compromised had to be made.
-
Besides x1, u18 and u35 mentioned above I also note that on my dso2c10, u1 and surrounding components are also missing. Any idea what these parts are for?
U1 must be the magnetics for a LAN port, something like this: https://www.mouser.com/pdfdocs/Pulse_1198.pdf (https://www.mouser.com/pdfdocs/Pulse_1198.pdf)
No need to bother with that, there's a lot of other components missing in the circuit and, if LAN support is not implemented in the firmware, there's no point in try to install that.
Vistorik was kind enough to send me the list of missing components :
DAC : DAC902E
OpAmp : LMH6702
Relay : FD4/4.5-S |428||282| XA0920A
Hope this helps.
I think the DAC is in fact a 3PD5651E, but it's pin compatible with the DAC902E and it should work fine. Maybe you will need to play a bit with some resistor values to adjust the AWG amplitude though.
-
Not all of them have erased the markings, I definitely have DAC902E.
-
@Vistorik. Ok. I would be happy just to upgrade the software. How can we make it go to 150mhz?
-
There is a suspicion that all have frequencies up to 150 MHz, the only difference is in the presence or absence of a generator.
-
There is a suspicion that all have frequencies up to 150 MHz, the only difference is in the presence or absence of a generator.
I did a quick test and I had the same impression. All model seems to have the same BW, a little over 150MHz.
Not all of them have erased the markings, I definitely have DAC902E.
What's your board revision? Did you get the oscilloscope recently?
-
Vistorik was kind enough to send me the list of missing components :
DAC : DAC902E
OpAmp : LMH6702
Relay : FD4/4.5-S |428||282| XA0920A
Hope this helps.
The relay should be HFD4/4.5-S
-
Microcheap, the oscilloscope received about three months ago at a price of $ 174 and with free shipping, now there are no such prices. The version is like everyone else's, there hasn't been a new one yet.
-
I opened a new thread dedicated to hacking the DX1X.
https://www.eevblog.com/forum/testgear/hacking-the-dso2x1x/ (https://www.eevblog.com/forum/testgear/hacking-the-dso2x1x/)
-
From the reports here it looks like some of the DSO2C10 have the (X1) Ext. Trigger/AWG relay and some don't.
How does the Ext. Trigger work on DSOC10 without the relay? I don't see any jumpers across the missing relay contacts to enable the Ext. Trigger without the relay.
-
I wrote about this in message # 10.
-
Where is your "message # 10"?
-
Sorry. answer # 103
-
I don't see any jumper across L11 on the picture I posted!
-
Check with a tester, it should be without a relay, it connects the external synchronization connector to the controller.
-
Must be an imaginary jumper.
-
I would guess that the EXT trigger input is always connected, it's simply disabled in software as the relay is used to also connect the function generator onto the shared BNC connector. While this saves on design, it does leave that EXT TRIG input vulnerable to damage, if the output rises above the 5V limits.
IF this is the case, This could also open up future mods to drive the EXT trig directly from the function generator, or split them onto separate BNC connectors..
-
@Algoma, I think you are right about the AWG relay. I don't believe that there are any 2C1x just with the AWG relay and without the AWG DAC and OpAmp. Some early 2C1x with the relay must also have the DAC & OpAmp and the AWG was just disabled in software.
-
If there is no relay, then the connector must be connected via a jumper directly to the controller and activated by software, or it will not work at all. Check your external trigger is working.
-
I would guess that the EXT trigger input is always connected, it's simply disabled in software as the relay is used to also connect the function generator onto the shared BNC connector. While this saves on design, it does leave that EXT TRIG input vulnerable to damage, if the output rises above the 5V limits.
IF this is the case, This could also open up future mods to drive the EXT trig directly from the function generator, or split them onto separate BNC connectors..
When the oscilloscope is turned on, the relay connects the connector to the generator output, and when an external trigger is activated, to the controller.
-
@piton The question was how the Ext trigger line remains connected while the relay isn't populated and no visible jumper is installed in its place in any of the photos we've seen so far, unless its hidden on the underside of the board.
I suggested that the EXT trigger's line always runs straight through where the relay is installed and the Relay's NO (Normally Open) contacts are used to tap the Function generator onto that shared trace. Then the system simply ignores the state of the EXT trigger and doesn't actually disconnect it. There are plenty 74HC Analog switches in there that could disable the EXT trigger without using the relay's other contacts to actually disconnect it.
Of course this simply a theory based on lowest cost design, for ease of manufacture for all the various models. It would all need to be traced out to verify how it all actually connects.
-
was how the Ext trigger line remains connected
I don't understand either. Jumpers L11 and L9 are connected in parallel to the relay contacts, and in its absence, one of them (L11, if I remember correctly) connects the connector to the controller, and the second to the generator output. I checked it with a tester, and the relay works as described earlier.
-
@VISTORIK, the Amplitude Calibration does nothing, When I queried HANTEK about this they told me its only necessary to do the the Offset.
Answer from wangshuang@hantek.com "Users don't need to perform amplitude calibration."
-
Judging from the firmware inside, the scope has a GOWIN FPGA which is probably the lemontree part
-
Judging from the firmware inside, the scope has a GOWIN FPGA which is probably the lemontree part
GOWIN does have a few LQ144 size chips that could handle the task. Perhaps it was a custom version for Hantek. Some have 64MB of SRAM, far more than the 8MB Hantek is using as capture memory in this scope.
There was some discussion over here about GOWIN:
https://www.eevblog.com/forum/fpga/gowin-fpga/ (https://www.eevblog.com/forum/fpga/gowin-fpga/)
-
Specifically the image from this post:
https://www.eevblog.com/forum/fpga/gowin-fpga/msg2647989/#msg2647989 (https://www.eevblog.com/forum/fpga/gowin-fpga/msg2647989/#msg2647989)
The GOWIN FPGA, compared to the Lemontree 2090: the package, printing and Model codes printing are a VERY close match.
[attachimg=1]
Now we just need to pin down a possible model, Many GOWIN chips are pin compatible.
-
Finally I got my DSO2D10. It came with Firmware "3000" and Software "2020 1221.00".
I Downloaded from Hantek Firmware dso3kb_20210311.upk and DSO2000 Software.
What is the difference between the Firmware download and the Software download?
Which one do I install first, does it matters?
-
The firmware file is the download you want. The firmware file (dso3kb_20210311.upk) is extracted to a USB drive to update the Oscilloscope to the latest Firmware version from the front panel.
The Software is for controlling the scope by the rear USB connection, more like Hantek's other USB oscilloscopes.
-
Thanks for the info, so when I update the firmware it will update my "Frmware 3000", then what is the "software 2020 1221.00" I have now?
-
They call in Firmware on the website, and when its then loaded into the oscilloscope. its then shown as the "Software" version on the info screen.
-
Hi.
Which firmware do you recommend for the DSO2D15?
Thanks.
-
Hi, CH2 Menu button light is green and the CH2 trace is green, as it should be. However, CH1 Menu button light is orange and the CH1 trace is yellow, are they color blind?
Are the traces colors somehow programmable?
-
Are the traces colors somehow programmable?
At the moment it would be far easier to change the LED on the board itself. .. Even the new Keysight Entry Scopes carry that odd Orange/Amber button color on Channel one, certainly another an uncanny match with the Hantek scopes.
-
I am pretty happy with my new scope which I have upgraded with the new firmware about a month ago. However I do get the occasional freeze generally when I expand the time base to study the finer detail of a waveform picked in "normal" mode. To get going again I switch off and start afresh. Is this a known bug or am I doing something wrong?
-
I am pretty happy with my new scope which I have upgraded with the new firmware about a month ago. However I do get the occasional freeze generally when I expand the time base to study the finer detail of a waveform picked in "normal" mode. To get going again I switch off and start afresh. Is this a known bug or am I doing something wrong?
I had a similar experience. In my case, the screen freezes when I press the zoom button.
I did a simple firmware update with a usb memory.
As a result, the freeze symptom disappeared, but only half of the trigger on the screen was caught, and the rest of the screen continued to shake.
So I made a full update using sunxi-fel (see previous posts from other members).
Update result:
1, all functions worked normally. :-+
2. Mine is 2C15, the pulse genenrator is alive and can be used. In other words, it became 2D15. :-+
3. Software, firmware version information, etc. It is no longer displayed. (This needs to be fixed by hacking. Also, see other members' posts before, but I didn't do it because there was no problem in using it.) :--
-
Looks like a new firmware update has been released. (April 20, 2021)
-
Updated to firmware 20210416 and system info is now showing UNDEFINED in Model Serial and Hardware, although the system was overall unmodified before the update.
Anyone else showing this after the update? Still running full features of the DSO2D15 .. Should be simple enough to restore the values, but curious they would disappear during a normal update.
System.INF is showing: (all seems to work normally)
[machine]
Model=undefined
Vendor=undefined
Product=undefined
Manufacturer=undefined
Serial=undefined
[version]
Pcb=undefined
Keyboard=undefined
[language]
Lans=65535
Language=2
[add]
Start=5
Update=0
Update: Restored successfully, I had taken a backup photo of the system settings when I received the unit.
As per thread: https://www.eevblog.com/forum/testgear/hacking-the-dso2x1x/ (https://www.eevblog.com/forum/testgear/hacking-the-dso2x1x/)
Create a text file named do_other_update along with the firmware file on a blank USB drive
The do_other_update file is executed, and runs any Linux commands you've entered in it, after a the firmware update has completed.
When editing do_other_Update with Notepad++ use EDIT -> EOL Conversion -> Unix (LF) to make the file Linux compatible.
1) Use this command in do_other_update to copy the /Cache/ folder to your USB drive. This folder contains system settings and calibrations. Its good to have a backup copy of these.
cp /cache/* /mnt/udisk
2) Re-run a firmware update, with the modified do_other_update script file to collect the contents of that cache folder to your USB
2) Edit system.inf file in notepad++ and restore the missing values.
[machine]
Model=DSO2D15
Vendor=Hantek
Product=undefined
Manufacturer=undefined
Serial=CN0000000000000 (Restore your serial# as per the Label on the back)
[version]
Pcb=00.000.000.000.000.000.000.001
Keyboard=undefined
[language]
Lans=65535
Language=2
[add]
Start=5
Update=0
3) modify the do_other_update script to restore (copy) the modified system.inf file back into the /cache folder of the scope.
cp /mnt/udisk/system.inf /cache
4) Repeat the firmware update procedure again, with the modified system.inf and do_other_update files on the root of your USB, (along with the latest firmware UPK file) to execute the changes.
-
Hi, I have the DSO2D10, which I received about a month ago. I see about 1.5 small divisions (0.3 large division) negative offset on both channels traces when the channel input is set to GND compare to DC coupling without any probes attaches or probes attached and shorted. Changing the channel VOLTS/DIV, does not change the displayed offset.
I am running the latest April software and I recalibrated the scope several times without any change in this offset. Can someone see if they can duplicate this problem and any way to fix it?
-
Part of the self calibration is its quite often affected by overall system temperature. the whole system needs to warm up properly to a "normal" operating temperature before running the calibration, with no leads attached.
I had such a positive voltage offset on channel1, until I let the device sit and warm up for a half hour, then it settled out to a proper zero value. Running a calibration too early can cause further offset, while its still warming up.
-
I did a full recalibration on mine,
Yes, its seems to calibrate for DC = 0V, But when coupled to ground, its also sitting at -200mv @ 1V/div setting. I'm suspecting its perhaps something within the input protection, there's a solid state relay at the input that does the connection to ground, perhaps could be that too. I'm not expecting much from the GND coupling in this scope.
-
My CH1 has a negative offset of 0.3 division and CH2 has a negative offset of 0.2 division regardless of the VOLTS/DIV setting. Therefore @50V/DIV setting the offset will be 15V which is ridicules and totally unacceptable. I have been using scopes for the past 50 years and on the crappiest scope, I never seen such an offset between GND and 0V input. This offset exist whether you calibrate the scope after 20 minutes of warm up as the manual suggest or calibrating it after one hour of warm up. I would like to hear how Hantek justifies that, it’s POS.
-
It does seem like something that can be sampled and corrected in software during calibration.. they did seem to make the calibration procedure longer in this latest update.
I like the hardware design from Hantek, considering the price point, but it's the software team that seems to lack skill and attention to detail when compared to all the others.
-
Does anyone have a direct email address for product/technical support at Hantek so I can find out what they say about this offset problem.
Even my $25 DSO150 scope doesn't have such an offset problem!
-
https://www.eediscuss.com/forum.php?mod=forumdisplay&fid=44&filter=author&orderby=dateline. (https://www.eediscuss.com/forum.php?mod=forumdisplay&fid=44&filter=author&orderby=dateline.)
Here you can ask a question to the representative of Hantek.
-
@vistorik, can you confirm this offset problem on your scope? If this problem is common to all the DSO2x1x scopes then this is totally unacceptable regardless of the scope price.
-
I got this scope (2C15) a couple days ago. The main reason I bought it was its cheap price and large memory, 8M max. It was the second cheapest 100MHz or above bandwidth scope that I could buy. The cheapest one was the OWON SDS1102, it was around $325, and it had 10K memory, which is, I don't want to use strong words but, complete trash. It seems like they've cut a lot of corners, all the buttons are the same size. Internals didn't look very good in reviews either. But anyways, this is not about OWON, this is about HANTEK 2C15.
First let me discuss my expectations from an oscilloscope. Before this one my only scope was a 20MHz analog scope. It was pretty shitty and basically useless for high speed stuff, which is pretty bad when all you do is high speed or radio stuff.
When I started to look for a new scope, my needs were;
-something that isn't a museum piece, which means no second hand analog scopes,
-at least 100MHz bandwidth for HF radio and high speed stuff,
-decent memory so that sample rate won't drop at larger timebases.
That's basically it. I didn't care about FFT for example, because 8 bit resolution means very low dynamic range anyway. I didn't care about decoding because all I do is analog stuff, other than some FPGA stuff. I didn't care about input min/max voltage range because I don't really use the lowest/highest voltage ranges.
So I got this one for $385. My benchmark was the Siglent SDS-1202X-E, which was at $500. The main reason I bought this one and not the Siglent is because the memory and bandwidth was good enough. However, it kinda disappointed me.
Let me discuss some features so that you can see why I'm disappointed.
-I know that I said FFT is not something I care about, because most of the times I need to see a frequency spectrum of a signal I also need high dynamic range, which this scope doesn't have, that being said, if you are buying this scope because you have some need for FFT and don't mind the low dynamic range, don't.
The FFT max points is a comical 2048pts. Combined with the limited dynamic range, I honestly can't see any use case where the FFT could be useful.
But maybe you are thinking that you could capture 8Mpts and do the FFT on the computer or something. Well, this brings me to my second and biggest disappointment.
-You can't sample at full speed when you are between 8Mpts-400kpts memory setting. It drops down to 250MSa/s when you set the capture memory higher than 40kpts, and it halves again to a comical 125MSa/s when you enable both channels!
As far as I know, this is not mentioned anywhere in the specs. I have to disclose that I haven't read the entire manual and maybe you have to change some settings or something, but I think such an important detail should be mentioned in the spec sheet, shouldn't it?
Now, I'm not going to return the scope. Even if it limits me to 40kpts sample memory, it's the second cheapest scope I can find. It would be too much of a hassle to return the scope. And I don't wanna give an extra $100 for an SDS-1202X-E just to get more memory at full speed and some more bandwidth. All I care is bandwidth and sample speed, and this thing has both of them. I'll have to hope that it's a bug and they'll fix it in a future update.
If you have any features or something else that you want to try on a DSO2C15, please send me a PM. I would be happy to try it for you.
-
So I got this one for $385. My benchmark was the Siglent SDS-1202X-E, which was at $500. The main reason I bought this one and not the Siglent is because the memory and bandwidth was good enough. However, it kinda disappointed me.
Let me discuss some features so that you can see why I'm disappointed.
-I know that I said FFT is not something I care about, because most of the times I need to see a frequency spectrum of a signal I also need high dynamic range, which this scope doesn't have, that being said, if you are buying this scope because you have some need for FFT and don't mind the low dynamic range, don't.
The FFT max points is a comical 2048pts. Combined with the limited dynamic range, I honestly can't see any use case where the FFT could be useful.
But maybe you are thinking that you could capture 8Mpts and do the FFT on the computer or something. Well, this brings me to my second and biggest disappointment.
-You can't sample at full speed when you are between 8Mpts-400kpts memory setting. It drops down to 250MSa/s when you set the capture memory higher than 40kpts, and it halves again to a comical 125MSa/s when you enable both channels!
As far as I know, this is not mentioned anywhere in the specs. I have to disclose that I haven't read the entire manual and maybe you have to change some settings or something, but I think such an important detail should be mentioned in the spec sheet, shouldn't it?
Now, I'm not going to return the scope. Even if it limits me to 40kpts sample memory, it's the second cheapest scope I can find. It would be too much of a hassle to return the scope. And I don't wanna give an extra $100 for an SDS-1202X-E just to get more memory at full speed and some more bandwidth. All I care is bandwidth and sample speed, and this thing has both of them. I'll have to hope that it's a bug and they'll fix it in a future update.
You need use it more and understand how it works. ;)
FFT is certainly 1 Mpts max and FFT speed is related to memory depth and/or FFT pts selected and FFT accuracy is related to your timebase selection and in general use a slower timebase for more waveforms displayed rather than less.
Sample rate is also related to timebase setting so to maintain good WFPS rates.
Oh and welcome to the forum.
-
» Readme first! «
Before following any instructions described here, please read:
This information was obtanied based on my own testings and forum users feedback.
I've put my best efforts on making this information accurate and valuable, but it might not be 100% correct.
Having said that, I don't take any responsability, if you proceed, it'll be at your own risk.
Before doing anything, save your important data!
- Make a flash backup (Check DSO Flash Tool below)
- Run Backup Builder (In Mods section)
Also, it's always a good idea to take a picture of Utility->System info screen.
Some updates might erase and/or break some features, and you'll need to restore the system.
Read carefully: There's a big difference between "FW version" and "SW version".
SW version refers to the software running inside the CPU(Phoenix).
FW version refers to the firmware running in the internal FPGA.
Higher FW version doesn't mean it's compatible or better!
Do not change your FW version unless specifically told you to do so!
Some updates can do it, so don't update with anything you find over internet unless you have a backup!
Check the section "FW versions" for more details.
» Quick glance «
This section summarizes few quick references.
» For scopes coming with FW30xx-31xx, update to FW3102.
» For scopes coming with FW320x, update to FW3208, try older 32xx versions if having issues.
FW3204 seems to break the decoder, avoid it.
» Latest software release is 2024.02.02.
» If USB is not working properly (Drive not being recognized until pressing update), apply Hantek's USB fix (https://drive.google.com/file/d/1-lL1udVQnWhrlzwnvy347DwVh5zhaobB).
» The system only has one USB interface, shared with 2 ports. So you can't use both at the same time!
» If the scope isn't being recognized properly in IO Lib Suite, uninstall it and install the latest version (https://www.keysight.com/us/en/lib/software-detail/computer-software/io-libraries-suite-downloads-2175637.html) from Keysight.
» Also using Rohde & Schwarz Driver (https://www.rohde-schwarz.com/ca/driver-pages/remote-control/3-visa-and-tools_231388.html) seems to work (Tested v5.12.8). (Link to original post (https://www.eevblog.com/forum/testgear/new-hantek-dso2x1x-models/msg4761820/#msg4761820)).
» If the scope is randomly crashing when handling the controls, ensure you have latest FW (B102/3102 or B202/3202).
» Additionally, if calibration fails with an error, probably your FW version is incorrect, check "FW versions".
» You can upgrade and downgrade to any FW and SW version you want, ex. you can apply an older version if the newer one isn't stable or compatible, there's no known risk of permanent damage.
» Sometimes the settings get corrupted and the scope gets stuck in the boot logo or the interface becomes unresponsive. If this happens, check "Recovering" section.
» Rotating encoders unresponsive but buttons working? Check this solution (https://www.eevblog.com/forum/testgear/new-hantek-dso2x1x-models/msg5068099/#msg5068099).
» To quickly upgrade to 2D15, run 2D15 conversion, available at the bottom of this FAQ.
Ensure to make a backup first with Backup builder!
» What not to do «
» Screwing up your system because you thought you were smarter than anyone, so no reading of any kind was needed.
» Coming here to blame us for your fuck-up because of the above.
» DSO Flash Tool «
This tool can backup and restore the flash without opening the scope.
- Download DSOFLASH (https://drive.google.com/drive/folders/13hwsIJd3eGrnHWCLPcQrPQiAb7rRx3W0)
- Open the readme and folllow the instructions.
» Firmware versions «
It's not a good idea to change it unless stated to do so.
Calibration will fail if the wrong version is used, but else than that, there's no risk of permanent damage.
Available FW versions
They're UPK packages, you can install them like a normal update.
If your version is not listed there, please make a backup using Backup Builder (In Mods section) and send me the file dso3kb_CNxxx_FPGA.tar.bz2.
You can upload it to my public writable folder (https://drive.google.com/drive/folders/1-7LKegzzLL4l98FkffZggu0jdSlD_a5E), please add some txt describing yor upload!
» 2013_A013 (https://drive.google.com/file/d/17FsxLOGARaSvlB5CnZ9laWueoNyAYXKS)
» 2015_A015 (https://drive.google.com/file/d/16kckHIS919AGPq8PaiRuwyg2bYnZ8LwR)
» 3000_B000 (https://drive.google.com/file/d/17C5ciF4CLZ21a4_oO1UydX1HfAk0AzFs)
» 3101_B101 (https://drive.google.com/file/d/177V_-znRM0d_9CYKmkf0QJHWjH-TmFYz)
» 3102_B102 (https://drive.google.com/file/d/17LfxjMrds1QI6p5ygnTCopgBdTldLhlR)
» 3200_B200 (https://drive.google.com/file/d/1705idYvu-vcu5EmOK889ab2EkzzJZ5gk)
» 3202_B202 (https://drive.google.com/file/d/178PFMkfjEzyxTW8K2WwaxZzkbotUKZmu)
» 3203_B203 (https://drive.google.com/file/d/16kN77g9-MILRLC2hh_lbvUEgqKn8CaZo) (3202 fix for noisy signal in higher memory depts, ex. 4M, 8M)
» 3204_B204 (https://drive.google.com/file/d/17JrwflAP3dDm8LeqMSSNBR_56wUTGrsE) (Seems to break decoding, try FW3202 if having issues)
» 3205_B205 (https://drive.google.com/file/d/17OaAF9Q0a5JJPQIf9RJ-Dsh28hFiOTRn) (Supposedly it fixes the decoding problems from 3204)
» 3208_B208 (https://drive.google.com/file/d/18kIhrKJ1aVUrSgCb2NDZCk81qRvw_hlL)
» Updating «
There are two kind of updates: Regular system updates and low-level firmware packages.
» Regular system updates are the UPK files. These are installed from the usb drive.
» Low level firmware packages are flashed using platform-tools. They will overwrite the whole filesystem.
» Check "Recovering" section.
» System Updates «
This is a collection of the up-to-date known updates.
If your version is not listed there, please make a backup using Backup Builder (In Mods section) and send me the file dso3kb_CNxxx_Software.tar.bz2.
You can upload it to my public writable folder (https://drive.google.com/drive/folders/1-7LKegzzLL4l98FkffZggu0jdSlD_a5E), please add some txt describing yor upload!
These can be applied safely:
» 2020.11.18 (https://drive.google.com/file/d/11PxjUeAhygfi3i5fLx3cpSAjnrYGi0NQ) (These older versions had trouble at triggering on fast and small spikes)
» 2020.11.21 (https://drive.google.com/file/d/11A6UJPfru08bQO8xsYqhX4Nc5XVyKFqm)
» 2020.12.07 (https://drive.google.com/file/d/11DNQCgUJHX1_6RAIqp7zjuwJXpBHatHv)
» 2021.01.05 (https://drive.google.com/file/d/10jpayPBk5wF5D5oSwYp8HaMRkOiJMnAA) (Zoom bug started from this version, not fixed)
» 2021.02.23 (https://drive.google.com/file/d/115K1qRP3eDXahJ0KjfMQabPDj3pc3t7o)
» 2021.03.04 (https://drive.google.com/file/d/11ZaAXhNZ6eO1pNApGdjt5t8EBLpdgX1n)
» 2021.03.11 (https://drive.google.com/file/d/1-q_kuzSDqiyrPKdTOvXz3RUjHIwdFCv4)
» 2021.04.16 (https://drive.google.com/file/d/11Q_ZEC88nZmGNLSKE5nWK4CJ8okB9fOU)
» 2021.07.05 (https://drive.google.com/file/d/11VzxYQfwNXv5RC7UC6ISv_Rz5yyKWr9c)
» 2021.07.14 (https://drive.google.com/file/d/10vE1zbHcKhFkEVcrMIuuvEvn1MaOMdnd)
» 2021.07.26 (https://drive.google.com/file/d/11A5E8UBmrRXUcRXW2Nt3iXXisYdVX2Q7)
» 2021.08.14 (https://drive.google.com/file/d/10VwKE9TDVy05qD4m4ZPbwZ80ZyyodMne) (Has a bug in the generator, DC offset not applied in real time)
» 2021.11.08 (https://drive.google.com/file/d/11br6nnBGK1UT2vU98ymgGzQ5mHIVckzp) (Also includes USB fix)
» 2021.12.17 (https://drive.google.com/file/d/10Y0tkdnRJ45IDxP27Fdm4FL5vqhlNzSW)
» 2021.12.21 (https://drive.google.com/file/d/10cHenFU0FjdJdTfqa8WN_h_3soQjodtD)
» 2021.12.30 (https://drive.google.com/file/d/11LT0P-LzRtIm5yiS1OJ0WKRl4pDdoyBp)
» 2022.01.05 (https://drive.google.com/file/d/11UzFTcOKKBZ1wqt1nLe4Xu9_FoFTAk9d)
» 2022.01.18 (https://drive.google.com/file/d/11aMSX4qU_COMexN8bJJXLlXOSZ3ApXsJ)
» 2022.01.24 (https://drive.google.com/file/d/11XF73p6yjZ1hfTSDBLJuJZv3SysbhN8H) (Starting this version, gnd coupling offset calibration was added, needs running a new calibration)
» 2022.02.10 (https://drive.google.com/file/d/10D52kHLGOCbhTpjHq2TDDTs8VGGmON_i)
» 2022.05.17 (https://drive.google.com/file/d/11sL77WmEO_IpHnrX25okbV594dqnrqSS)
» 2022.08.19 (https://drive.google.com/file/d/1dJAc-jnA0TXQLv1zuWe3rKztWCwwKcFl)
» 2022.09.21 (https://drive.google.com/file/d/11mM_DHPyZBg95St-6twJwgVSH9ISL99e) (Only fixes Russian translation?)
» 2022.10.28 (https://drive.google.com/file/d/1-0D0OB4s0faJ97lmVVcZQEwfOxHDHAU-)
» 2023.03.27 (https://drive.google.com/file/d/16oMclbwruL-_ZH0Bx1wCLsNf47X_FqSc)
» 2023.08.31 (https://drive.google.com/file/d/14v9AkTTr-HDbLTVIDO6USTtUriHS2J5a)
» 2024.02.02 (https://drive.google.com/file/d/1i5pKBkqZWpgScXEeQ69Sm-QarDbt61s5)
These will update the fpga FW version:
» 2020.12.21_fpga_3000 (https://drive.google.com/file/d/11DoANm4mpwbxMJvHid7fSZU727c4exl-) -> Sets FW3000
» 2021.05.10_fpga_3202 (https://drive.google.com/file/d/112pwE12vgyKkw6sI46Z9GnQVoZzv1aJD) -> Sets FW3202
» 2021.06.01_fpga_3102 (https://drive.google.com/file/d/10CVDMFK73kyHM7IEGQuPbPoCwP4VzQ0r) -> Sets FW3102
» 2021.06.30_auto_update_fpga(3102-3202) (https://drive.google.com/file/d/10cJ-efkjltLoIKIBbjohQ0pDT5B3vEro) -> Auto-updates 3000->3102 or 3200->3202, else leaves it unchanged
» 2022.02.18_fpga_3203 (https://drive.google.com/file/d/1-knNxKPrMJF1Tvo7rURaykMOfPACtG6c) -> Sets FW3203 (2022.02.10 sw, fpga fix for noisy signal in higher memory depts, ex. 4M, 8M)
» 2022.09.21_fpga_3205 (https://drive.google.com/file/d/11nBDW1f1jOYNZwqIuZHKE-2VZEBQs9yr) -> Sets FW3205
» 2024.02.02_fpga_3208 (https://drive.google.com/file/d/19Q1V52XrAPduTIcd-FpF79prOrcXdW32) -> Sets FW3208
There's a Hantek solution for the USB problem:
» USB_fix (https://drive.google.com/file/d/1-lL1udVQnWhrlzwnvy347DwVh5zhaobB) -> Resets the system settings and deletes a small file causing the issue, FW and SW versions remain untouched.
» FEL mode and driver installation «
- Connect the scope to the computer, hold FEL button down and turn it on, keep holding the button for 2 seconds and release.
(https://www.eevblog.com/forum/testgear/new-hantek-dso2x1x-models/?action=dlattach;attach=1613437)
Automatic installer
- Download FEL / Fastboot Driver Installer (https://drive.google.com/file/d/1ClBnWNCki6yvNxTzKuZpO8ujkiu8wgWK) and follow the included instructions, also available here (https://drive.google.com/file/d/1-WBzcB-T_JV37i9rH_lYY9kgVCjKZm91).
Manual method
- Install PhoenixSuite_CN.msi (https://drive.google.com/file/d/1VvX-tAnYhDXCpBNVLN0BxuhhcaLkpBk9/view?usp=share_link).
- Download Zadig (https://zadig.akeo.ie/) and follow this steps:
(https://www.eevblog.com/forum/testgear/new-hantek-dso2x1x-models/?action=dlattach;attach=1613431)
-After that, you should see the device driver installed:
(https://www.eevblog.com/forum/testgear/new-hantek-dso2x1x-models/?action=dlattach;attach=1522693)
» Recovering «
In the case anything went wrong and the system cannot longer boot or run normally, normally this is caused by corrupted settings, there're several options to recover:
There's a mod, "Factory Reset Daemon", that will do this automatically when doing a sequence of several power-off actions manually.
System shell
If you have access to the serial port or the USB Console is working, enter the shell and run these commands:
pidof dbus-daemon phoenix | xargs kill -9
rm -rf /data/setup/last.pho /dso/etc/aslf/*
reboot -f
If still not working, use Platform-tools method.
SCPI
- Install latest IO Lib Suite.
- Connect the scope to the computer.
- Open the Device Manager, if the scope appears under "USB Test and Measurement Devices" proceed with next step.
- Open Keysight Connection Expert, click Interactive IO, write "PRIVate:FACTORY:RESET" in the command and click "Send Command"
- All setting will be erased, the scope will reboot automatically.
- If not working or not recognized, then Platform-tools will be the only way of recovering.
(https://www.eevblog.com/forum/testgear/new-hantek-dso2x1x-models/?action=dlattach;attach=1626457)
(https://www.eevblog.com/forum/testgear/new-hantek-dso2x1x-models/?action=dlattach;attach=1626433)
Platform-Tools system flashing
This will completely wipe your system, erase serial, model and signal generator calibration!
So better you have a backup, otherwise you might lose the generator calibration.
Newer versions of the scope store the calibration values in the eeprom, while older versions didn't had them.
There's a calibration script in Mods section that will both calibrate and update the eeprom, so it never gets lost again.
Boot into FEL mode (Check upper section), then run "cmds.bat" or "recover.bat" depending on the version downloaded.
The screen will appear distorted, and/or with random colors, that's normal!
After a moment the process will finish and the scope will boot normally.
Important: Connecting it to usb 3.0 ports seem to cause some issues. Use a 2.0 port when possible.
Always apply the USB fix after recovering using this method!
If getting “api-ms-win-crt-runtime-l1-1-0.dll missing” error, install Update for Universal C Runtime in Windows (https://support.microsoft.com/en-us/topic/update-for-universal-c-runtime-in-windows-c0514201-7fe6-95a3-b0a5-287930f3560c).
Platform-tools versions:
» Unified platform-tools package (https://drive.google.com/drive/folders/1-J-Dz7aB6hV3MmuJj-t_35cBSadiGHVF)
- 2020.12.21, FW3000
- 2021.01.29, FW3101
- 2021.05.17, FW3102
- 2021.07.26, FW3202
- 2022.07.07, FW3205
Now, your scope will show "undefined" under model, hardware and serial number, also the generator calibration will be gone.
You should now apply the backup package "dso3kb_CNxxx.upk" to restore them.
If you didn't made backup, the FW version might not be correct for your model.
Check "FW Versions", "Quick glance" sections to apply the correct FW.
To manually restore the HW, Model and serial check Scripts and Script Launcher in "Mods" section.
If you have lost your Generator calibration, it's gone forever, there's no known way to calibrate it.
You can try "Generator calibration fix", which will restore a calibration taken from another scope, it will be better than nothing.
» Model modification «
You can "upgrade" the scope ex. from a 2C10 to a 2D15 by simply modifying the model strings.
Keep in mind not all 2C1x models have the wave generator parts mounted.
Some do, other doesn't, the only way to know is to open it, or simply upgrade it and check if the generator works.
There's the package "2D15 conversion", available in Mods section, to make the conversion in a very simple manner.
Alternatively, you can also do it by yourself with these simple SCPI commands.
The SCPI commands are applied instantly, not requiring rebooting to take effect.
Remember to use your PCB number, modifying only the last digit to "1".
PRIVate:SET:MODEl1 DSO2D15
PRIVate:SET:PCB "000.000.000.000.000.000.000.001"
You can also modify the Serial and other strings:
PRIVate:SET:SERIal CN2101029000000
PRIVate:SET:VENDor Hantek
(https://www.eevblog.com/forum/testgear/new-hantek-dso2x1x-models/?action=dlattach;attach=1626442)
What we know so far is the software reads both the model and the PCB versions to check whether to enable the generator or not.
It willl enable the generator if the model contains 2D10 or 2D15, or if the last number of PCB model is "1".
» Mods «
Ensure to read Readme.txt before doing anything!
» Backup Builder (https://drive.google.com/drive/folders/18C4vPyFdurmI5mHTYQCSHOpPtgwdx9OK): Backups all important system data and builds three main update packages, so you can quickly restore them:
» dso3kb_CNxxx.upk: Restores Model, Serial, HW, FW, Generator calibration, preserving the existing software.
» dso3kb_CNxxx_FULL.upk: Restores Model, Serial, HW, FW, Generator calibration and dso, overwriting the existing software.
» dso3kb_CNxxx_EE.upk: Restores system EEPROM.
Extra packages:
» dso3kb_CNxxx_FPGA.upk: Restores only the FW (fpga).
» dso3kb_CNxxx_Calibration.upk: Restores only the Generator calibration.
» dso3kb_CNxxx_Model.upk: Restores only the Model, Serial, PCB.
» dso3kb_CNxxx_Software.upk: Restores only the software.
Additionally, it will create a tar.bz2 for each package to allow easy inspection of the files.
All packages include the USB fix, also the builder itself will apply the fix before making the backups.
» 2D15 conversion (https://drive.google.com/drive/folders/1AbaHXFGgBeKaUuzLmC5P5jtotScjxTgf): Sets your model as 2D15.
» bmp2png (https://drive.google.com/drive/folders/1_rFbaj1vycflRAPRTOp5f8PQxQyEvHfG): Automatically convert the screenshots into much smaller pngs.
» Doom (https://drive.google.com/drive/folders/16jy_EqNqiBZiG7SCuQ5_gNHrqLmivUHS): Needs further explanation? Yes, you can run Doom!
» Factory Reset Daemon (https://drive.google.com/drive/folders/1BF4cnQXYHPw5Sy9HccncGCQkBNM03ldj): Daemon that detects early reset/power off, will trigger a factory reset on the third time the system is quickly resetted. Video (https://www.eevblog.com/forum/testgear/new-hantek-dso2x1x-models/msg4491475/#msg4491475).
» FW Changer (https://drive.google.com/drive/folders/16iwDpueLSkf229hreaa-1-S4VdtjSc3k): To change any FW version. Run backupFW and send me the bin file if you FW version is not there!
» Generator calibration (https://drive.google.com/drive/folders/1BKoQdmdGaoxBTRvgIrXzipTrpXUJBqjg): If you lost the calibration and didn't back it up, this package will restore it.
» Overclocking (https://drive.google.com/drive/folders/18mhrIfJovlVe6pkEUpoOIDCQ6hmC-BEh): Applies overclock to the system for better response, without any overheating issues.
» Patched english font (https://drive.google.com/drive/folders/1AOL4hWLuxakm2tqgRLGRKz7efeKV9zkc): Original font is bulky and ugly, this font is patched and uses a smaller font already present in the file.
» Patcher (https://drive.google.com/drive/folders/18kLCiv3E7FusO-ioO8oENj5oUiyYId_8): At the moment, it's able to enable uart ascii decoding and change plot colors.
» Theme for visually-impaired (https://drive.google.com/drive/u/1/folders/18nUXtg9fLXprGqtXjuBw75cyzFx3d1FK): Changes the default Yellow/Green plot colours to Yellow/Purple. Math is Cyan. See included picture.
» RTC mod (https://drive.google.com/drive/folders/19fTCsejid1gkRd03zvPECYRLOQb93c6G): Mod adding DS1307 or DS3131 RTC to keep the date, so the screenshots aren't always dated to 1970.
» Date daemon (https://drive.google.com/drive/folders/1pBjFd9OFmrmI-2iKUzKJKDr6CdEYzODl): Mod adding track of the date while the scope is on, restored at boot and updated every minute. Date doesn't increase while the scope is off.
» Scripts (https://drive.google.com/drive/folders/18HUbHFsNe4chJvYN4UdafxkK6vtjTlC8): Script collection. Use Script launcher to run them.
» Script launcher (https://drive.google.com/drive/folders/17hFROHhYxMNqyQbFleXS8SAkB-Ab3_nz): Runs any bash script in the usb drive called "do_other_update".
» Static compiled binaries (https://drive.google.com/drive/folders/147Hl8iw8iXU0lWJ4QgGAB4iWrMvEOvTc): Custom cross-compiled binaries that can be run in the hantek system. For the hacker only!
» USB Console (https://drive.google.com/drive/folders/17_FjyXQ8vsaD5K8ToU_6ASipgmaCOvNJ): Creates a USB serial port to access the Linux shell, keeping all the original functionality.
» UPK Build / Extract tools (https://drive.google.com/drive/u/1/folders/141BF7rYJTkvPYzBgU1UOxY9XIT8n_W5t): Scripts to decrypt/encrypt update packages.
» source code (https://drive.google.com/file/d/1gZkmB5yC0EUMcqwdEsGccjX9LU5HAXN0): Kernel/uboot source code.
» Live Linux (https://drive.google.com/drive/folders/16Y6zxyLnwOZfcAuJ7SWbK4XU2AUZP9QM): A compiled version of linux made to be loaded in FEL mode. Just a proof-of-concept.
» Debian Virtual machine (https://drive.google.com/drive/folders/15OREGs6KVif6BJ5OTiZX5YuI6jSQF-CS): Debian 10 Virtualbox machine for compiling stuff for this device, arm-gcc-linux-eabi and lots of build dependencies already installed, ready to use.
» Links «
» DSO2x1x hacking thread (https://www.eevblog.com/forum/testgear/hacking-the-dso2x1x/)
» Everything is available in my Google Drive folder (https://drive.google.com/drive/folders/18hlxm84RwWpsml4CEz2QG75YZiT5vIMI)
» Hantek DSO2000 schematics (https://github.com/pecostm32/Hantek_DSO2000), thanks @pcprogrammer!
-
@tautech I think you were referring to the SDS-1202X-E when you mentioned the 1Mpts FFT right? It certainly is an excellent scope, I just couldn't justify spending more on features that I probably won't need, however, seeing how this one turned out, I guess I made a mistake.
Unfortunately, there are literally no "serious" scopes in my country under $300. I wish there were...
@DavidAlfa I think there are already a couple of people who hacked it to get the higher bandwidth/sig gen on this thread and another one. Just be aware that, as far as I can tell, the DSO2000 series currently can't do 8Mpts at full sampling speed.
-
Beware of the “ Hantek Official Store” as they do not play by the AliExpress rules. I ordered a DSO2D10 from them 72 days ago and it is yet to be shipped. Immediately upon placing my order, AliExpress sent me an email indicating that my order will be shipped within 10 days or they will issue a full refund. They also give the option to wait longer if you choose. I never chose the option to wait.
Just before this 10 day period is up, I got a second email from AliExpress relaying seller information that my order was being shipped and provided a DHL tracking number. The tracking information turned out to be fake.
No more emails. After a month or so I chose to contact the seller and inquire about my order. This is when I find a posted message on the vendor site that I should wait another 14 days as stock is low. Later on, I am told to check with DHL as there is an issue with my address. DHL can not help me as the tracking information is invalid.
I notice on a low resolution photo of a DHL shipping label provided by the seller, to prove issues with my address, that only 5 of the 6 characters in my Canadian postal code are shown. Perhaps the seller is trying to ship my order to the United States where zip code is only 5 numbers. The seller thanks me for informing them that my province is in Canada and not the US. Canada was shown on my address all along.
Several days later, a message on their “contact seller” informs me that I must wait my turn as stock is low. Later, I must wait another 14 days. Then, I have to wait some more as Hantek is having a chip shortage problem. Oh yes, they are offering a $5.00 coupon towards a future purchase to compensate for the long wait. I turned down their coupon offer and explained I would never buy anything from them again.
I am then informed via their “contact seller” that my order would be shipped “this week”. They continually refer to me as “friend”.
After a week I open a dispute with AliExpress, requesting a refund. The seller immediately provides me with a new tracking number, this time with FedEx. They also request that I close my dispute with AliExpress. I respond that I simply want my refund in order to purchase the oscilloscope from a more reputable seller. I did not close my dispute. The seller has not responded further to my request.
-
Do not close your dispute, ever.. Until its resolved to your satisfaction. It can only be opened once.
It can stay open until you receive your product, or refund.. Aliexpress will arbitrate the dispute if it stays open without resolution. If the Seller isn't playing by the rules, it goes against them.. and their store can get shut down if they get too many disputes. Aliexpress is holding your funds, The seller doesn't get anything as long as your dispute is open.
Sounds like they're gambling with trying to sell products they don't yet have on hand. Huge mistake from them, driven by fear of missing out potential on sales. Their delay tactic to avoid automatic refunds is going to earn them both lost product, income and a ban.. You could entirely end up with a both a scope and a refund if they can't prove proper on time shipment to Aliexpress.
-
Beware of the “ Hantek Official Store” as they do not play by the AliExpress rules. I ordered a DSO2D10 from them 72 days ago and it is yet to be shipped. Immediately upon placing my order, AliExpress sent me an email indicating that my order will be shipped within 10 days or they will issue a full refund. They also give the option to wait longer if you choose. I never chose the option to wait.
Just before this 10 day period is up, I got a second email from AliExpress relaying seller information that my order was being shipped and provided a DHL tracking number. The tracking information turned out to be fake.
HI. I faced similar issues when I placed my order with this vendor back in January. However I did not accept their DHL excuse and kept pestering them to ship pointing out that their site still indicated they had stock so excuses were not acceptable. They eventually shipped via EMS about 10 days later. Good luck with your purchase.
-
I ordered a 2D10 from Hantek Official Store. (290 CDN) The status reads:
Your order will be automatically cancelled if the seller fail to ship your order in: 8days 09hours ...
Will be shipped within (Business days)7 Days
I'll update as things go.
-
The store shows the following inventory (316 pieces available):
DSO2C10 - 100 pieces available
DSO2D10 - 106 pieces available
DSO2C15 - Only 10 left
DSO2D15 - 100 pieces available
-
Just received shipping notification and tracking:
May, 13 2021 - 00:18 Local time | Shipment picked up
May, 13 2021 - 00:21 Local time | Processed at HONG KONG - HONG KONG SAR, CHINA
The store shows the following inventory (312 pieces available):
DSO2C10 - 99 pieces available
DSO2D10 - 105 pieces available
DSO2C15 - Only 9 left
DSO2D15 - 99 pieces available
Curious that inventory is down by exactly qty 1 of each. ???
-
Beware of the “ Hantek Official Store”--update
I wrote to customer service at Hantek and made them aware of my unsuccessful attempt to purchase and oscilloscope from the “ Hantek Official Store”. Han from Hantek responded, asking for my order number with AliExpress as he was going to look into my order.
Then AliExpress, acting as arbitrator, sent me an email on May 6th indicating the “ Hantek Official Store” was refusing to refund me and were asking if I would accept immediate shipping by FedEx. I refused the seller’s proposal. Simply wanted my refund so I could buy from someone else.
Fedex Tracking information had not changed between April 30th to May 8th . A package was waiting 9 days to be picked up by FedEx? On May 8th, it was supposedly picked up.
Today’s tracking update shows a Fedex package in Mirabel, Quebec. Is it a Hantek DSO2D10 or a $5.00 coupon?
-
I received the 2D10 in Calgary today from Hantek Factory store.
Somewhat similar to your experience: they first posted a dummy tracking number, didn't ship for almost a month, then about 2 weeks ago the Fedex number that didn't update for over a week, then went from Singapore to my doorstep in just a few days. Before this I dealt with a different story that held the order for over a month because it was out of stock, then in the end I had to cancel that one. At this point I'm just happy to have receive the actual unit, and it's fully working :)
-
Just received this shipping update:
2021-05-14 13:20
Arrived at Sort Facility NEW YORK CITY GATEWAY,NY-USA
Current inventory of the store (cause ... why not?):
307 pieces available
DSO2C10 - 99 pieces available
DSO2D10 - 105 pieces available
DSO2C15 - Only 7 left
DSO2D15 - 97 pieces available
-
Shipment arrived with a fee of $25.50. A bit confusing as the last notice said:
Notification for shipment event group "Out for Delivery" for 16 May 21.
Estimated Delivery Date: 2021-05-18 23:59:00
(May 18 is Tuesday, two days from now)
Regardless, it's 'here', and now to see if everything is in order.
-
I've run through a few basic tests and calibration and everything looks in order. Here's what I received:
DSO2D10
Software: 1.0.1.1.0 (20210416.00)
Hardware: (too many zeros).001
Firmware: 3200
Ordered on May. 10 2021
Arrived on May. 16 2021
Current firmware:
http://hantek.com/products/detail/17182 (http://hantek.com/products/detail/17182)
2021-04-20 dso3kb_20210416.rar
-
Beware of the “ Hantek Official Store”--last update
Scope was delivered. I had to put up with almost 3 months of waiting plus a lot of lies and deception. I should be happy, I guess!
-
Anyone else have their screen protector sheet fitted such that its underneath the front panel and impossible the peel off? |O
Has anyone taken one of these apart enough to know if I can get inside enough to remove it, or send the scope back?
-
It sounds like the problems I had were very minor compared to others. Even quite amusing.
28th April Ordered a DSO2D15 from Hantek Factory Store on Aliexpress.
Several msgs accumulate in Aliexpress from seller, querying that postcode 2213 doesn't match 'Sydney'.
5th May I didn't see those till then, when I logged in to find out what was happening.
I replied that 2213 East Hills is a suburb in Sydney, my address in their 1st message is correct.
6th May, they again insisted my address can't be Sydney. I replied same day to clarify.
They STILL insisted that can't be right.
7th - I wrote lengthy explanation. Included map. "send it now to that address or I cancel the order."
7th - they say "we will send today, tell you the tracking number"
11th - I comment the UPS tracking shows UPS still have not received the parcel.
12th - they bitch they asked about my address but I didn't reply till the 5th, ie delay is my fault.
17th - It arrives here.
See https://www.eevblog.com/forum/chat/what-did-you-buy-today-post-your-latest-purchase (https://www.eevblog.com/forum/chat/what-did-you-buy-today-post-your-latest-purchase)!/msg3571806/#msg3571806
The screen protector sheet - the edges were a little bit overlapped by the case plastic, but pulling harder detached it fine, none tearing off and left stuck under the bezel.. My only gripe so far, is there was only one real probe included. The advertising pics and list had made that clear, but I wasn't sure I believed them. Anyway, not a problem.
It's amusing to look in through the case air vents, and realise the internal space is about 70% empty. They could have made it MUCH thinner. But then it would fall over too easily.
I have screen shots of the entire comical message series about postcodes, but need to stitch them into a single image. Not sure it's worth it.
-
While waiting for my DSO2D10, I ordered a Hantek PP-150 from the Hantek Global Factory Direct Store to see how quickly they would deliver. They immediately shipped the probe and it was delivered in less than 2 weeks. It is exactly like the x10 probe included with the oscilloscope. My intention was to reorder the scope from them if I was ever refunded.
-
I got 2 probes for $10 from eBay https://www.ebay.com/itm/301845153341 (https://www.ebay.com/itm/301845153341)
-
Is there any way to set the Trigger coupling? The 5000P series has AC, DC, HF Reject & LF Reject options.
-
I'm really in two minds as to keeping or sending this back as of right now. There are just way to many bugs and things wrong with it.
Notwithstanding the regular freezing up requiring a power cycle reset here's a short list of problems I've noticed in the few hours of testing:
Using the latest update of 20210416.
Turing almost any encoder a "bit too fast" can result in the scope locking up. It still responds to some keypresses for a while after, but with no screen updates, then it freezes completely needing a power cycle.
Power cycleing doesn't always reset enough to get the scope working again, sometimes a cople of cycles, pressing "default setup" or Autoset are needed.
Autoset 50% of the time locks up the scope.
As noted by others, there's an voltage offset between DC/AC/GND coupling, different between channels.
Exact trigger point seems to be somewhat random resulting in jittery waveform display. Channel 2 trigger in particular seems awful. There doesn't appear to be anywhere to set the trigger coupling.
(scope has just locked up AGAIN because I dared to alter the VOLTS/DIV while displaying a wave)
Timebase below 100ms results in the display being "buffered" for the first half of the screen, displaying all at once, then the second half displayed as a rolling display, updating in odd steps every couple of seconds. Timebase of 10 seconds or slower just gives a small wave in the centre of the screen..?
The Protocol decoder is best described as useless. It misses more than it captures and what it does get is limited to just a few characters.
Wave generator has a lot of jitter once you get above a Mhz or so. There's lots of ringing and roughness to the generated waveforms. No sweep function. Modulation frequency only as low a 100Hz
I was hoping this would be as "good" as my DSO5102P, but with the useful waveform generator and larger memory depth. As things currently stand its very very much worse to the extent its practically unusable.
Oh, did I mention it freezes a LOT?
-
I had a similar problem with freezes and I was able to solve that reprogramming the system images with some files sent by Hantek's support.
If you dare, you can try it yourself. I've uploaded the files to a temporary file sharing page, the link will be valid for only 7 days before it expires:
https://www.filemail.com/d/mmnhoxtbjdututb (https://www.filemail.com/d/mmnhoxtbjdututb)
In the downloaded file you will find included a .doc text with the instructions on how to proceed.
Note 1: this procedure will blank some details on the system info screen of the scope, but that is easily fixed later if you mind the missing information. I would just recommend that you take a picture before to have as reference.
[attach=1]
Note 2: this images install the firmware 3101 on the oscilloscope, looks like there's already newer scopes with version 3200. Which version yours scope is running now?
-
Mine is only Firmware 3000.
[attach=1]
I did manage to get the screen protector detached in the corner after a bit of messing about - that red tab was almost entirely under the front panel.
Here is a video showing how odd the screen updates are at slow timebases. https://imgur.com/a/aBADJlb :wtf:
-
Before the update, mine was Firmware 3000 as well, and the freezing symptoms were exactly the same.
-
Mine came with firmware 3200, and I haven't noticed any scope lockups so far.
The data decode shortcomings mentioned... I haven't experimented with that yet. Those would be a serious fail, if still a problem with the newer firmware.
About trigger coupling (AC, DC, etc), it clearly is applying trigger logic to the sampled datastream. Hence that it can trigger on things like decoded data patterns. Since the data stream is already normalized by the channel input AC/DC coupling and sampler range, it doesn't make sense to have separate AC/DC coupling settings for the trigger level.
-
When I got my DSO2D10 with dso3kb_20210416 installed i was having BIG lockup problems.
I have received from Hantek an download link to dso3kb_20210510 IT IS MUCH BETTER.
I did try really hard by rotating the Sec/Dev control to crash it i only managed it once.
I am soooooooooooo pleased with this little scope,i am thinking of buying another as a spare. :-)
-
I got a 2d15 the other day. firmware 3000. january software. Updated to latest, no issues thus far....
but i did reach out to hantek. "why do some have firmware 3200 and mine 3000?"
The answer is simple: different board revision....
-
I have received from Hantek an download link to dso3kb_20210510 IT IS MUCH BETTER.
Hantek web site still proposes the April 20th version of the software.
Can you please share your link?
thanks
-
Please note when i downloaded it, it is dso3kb_20210510 by name
However after installing it it reports 20210416 in the scope util system menu
It is however 5kb smaller on disk according to my PC than dso3kb_20210416
So make of that what you want and don't blame me if it bricks your scope
Lastly this link is TWO days old now and no idea how long it will be about.
https://www.filemail.com/d/qcmkjdtleqlkhpb (https://www.filemail.com/d/qcmkjdtleqlkhpb)
-
@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. 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?
-
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 :-DD)
But the extra 13€ for the gen absolutely worths it.
Just in case anyone wants the link:
https://www.aliexpress.com/item/1005001632337246.html (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?
-
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.
-
They could have pulled that latest firmware off their website if there was a critical issue found within it.
-
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, 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.
-
No need to remind to always make a full backup, and all the hacking goes at your own risk :D
Specially having these (apparently) easy to use platform tools for making the backup...
Waiting for mine impatiently!
-
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?
-
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.
-
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/1005002636631647.html)
https://www.aliexpress.com/item/1005002036920820.html (https://www.aliexpress.com/item/1005002036920820.html)
-
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/1005002636631647.html)
https://www.aliexpress.com/item/1005002036920820.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 :-DD
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 :-DD
-
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...
-
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
-
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?
-
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 (https://www.eevblog.com/forum/testgear/new-hantek-dso2x1x-models/msg3432650/#msg3432650)
The leds, probably simple as replacing some resistors to lower the current.
-
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 (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
-
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 :-+
-
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.
-
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?
-
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.
-
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.
https://www.youtube.com/watch?v=L2TrkwVndsY (https://www.youtube.com/watch?v=L2TrkwVndsY)
-
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
-
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
-
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 (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.
-
I made a folder with all I could find about the DSO2x1x.
https://drive.google.com/drive/folders/1Tqk8YbL_M3S0vtk7h_cZ-01U2idIaqqx
Original dumps are welcome!
-
Guys, I found it so laggy and bugged that I'm thinking on returning it and buying the DSO4102C.
Seems way better on the video reviews I found. Also allows 200MHz hack.
Any thoughs?
-
Guys, I found it so laggy and bugged that I'm thinking on returning it and buying the DSO4102C.
Seems way better on the video reviews I found. Also allows 200MHz hack.
Any thoughs?
Hello David
Well i sounds like you have received your DS02xxx and not so happy with it, i am sorry to hear that.
Did you apply that fix that HanTek sent to me as i found it helped, also I just did a calibration and it went thru without error (Although it did take a few minutes).
As for buying another Hantek I have seen on other threads people saying they are buggy.
So to changing model may just result in less functionality and just as buggy, maybe the devil you know rather than the devil you don't.
Maybe a better solution is to get on Hanteks case for a fix and remind them of these forum threads.
Remind them that these threads will damage there reputation and future sales.
Maybe threaten them with a really bad video YouTube review.
Maybe post a letter to David Hoo (Head of Sales) at #35 Building, No. 780 Baoyuan Road,High-tech Zone, Qingdao, Shandong, China 266114
Mentioning the above, I think i will be dropping them a letter, only going to cost a a pound of two for postage and a "Letter Often Means Something"
imk
-
What is the direct email address technical support at Hantek for on these DSO2X1X scopes?
-
What is the direct email address technical support at Hantek for on these DSO2X1X scopes?
http://www.hantek.com/About#hantek_contact (http://www.hantek.com/About#hantek_contact)
Bottom of page
-
Hantek have a "support" forum at https://www.eediscuss.com/forum.php?mod=forumdisplay&fid=44
Maybe we should start some threads there detailing the bugs we're finding...
-
Really? In 5 minutes the bugs are countless.
They have spent hundreds of hours developing it. Or do they have blind or impaired engineers?
-
I like Hantek's Hardware design for the given price, its the software guys that need some new Talent on their team.
There are references in the firmware to other (previous) models, it very much looks like they're re-using an existing core firmware that hails from their USB scopes at its core, kludged together to work with the newer hardware.
The software guys seem to be having a hard time, especially when the CPU is far weaker processing wise than the capture engine itself. Many of the bugs appear to be mostly timing related towards missed events.
-
I like Hantek's Hardware design for the given price, its the software guys that need some new Talent on their team.
There are references in the firmware to other (previous) models, it very much looks like they're re-using an existing core firmware that hails from their USB scopes at its core, kludged together to work with the newer hardware.
The software guys seem to be having a hard time, especially when the CPU is far weaker processing wise than the capture engine itself. Many of the bugs appear to be mostly timing related towards missed events.
Hello Algoma,
Software eventually works and hardware breaks down, the trick is to ensure the former happens before the later. :-)
This can only be achieved by rigorous testing which I am afraid is driven out at this price point.
Best we can do is Name and Shame them into doing something about it.
imk
-
Guys, I found it so laggy and bugged that I'm thinking on returning it and buying the DSO4102C.
Seems way better on the video reviews I found. Also allows 200MHz hack.
Any thoughs?
You are disappointed with Hantek and hence are considering to buy another Hantek? ???
Assuming you are based in Europe and mail-ordered the scope from a European vendor, can't you just return it and look for a different brand (from the same vendor or elsewhere)?
-
Well, I've seen videos of the DSO4102C in youtube and it seems a lot more stable and responsive.
I don't mind some sluggish performance or ocassional lockups if I can save a lot of money, since it's for hobby use.
But the 2xxx is too much! |O Just change the time base few times...bang!
I have to reboot it every 2 minutes.... absolutely unacceptable.
This is worse than Windows 95 era jokes, "Now includes a bag of reset switches for free!"
-
David,
I am testing with my DSO2D10 ch1 off ch2 on and wired to Gen Out.
The Gen i have tested with Sine, Square and Ramp from range 100hz to 1mhz and can cause the scope to freeze by rotating the Sec/Dev timebase knob more rapidly than the display is refreshed at. If however I rotate the Sec/Dev one click at a time and await for the display to refresh and settle then the scope does not seem to freeze.
As you know i have upgraded from dso3kb_20210416 to dso3kb_20210510 and the situation has now improved.
As when i was on dso3kb_20210416 I could crash the scope buy adjusting trace Vertical Position or Vertical Volt/Dev or V0.
So it seems Hantek has made some progress, so maybe if we get on there case they will fix the worst of these and other bugs.
I think too early to give up as this DSO2D10 is lot of bang for buck :-)
What you think?
IMK
-
I don't know what to think. Hantek has been selling it for 6 months.
The development might have took months or even years (F1C200s came out in 2017).
But they released a big pile of **** that couldn't even be called "beta".
Maybe alpha-1. Which means it boots and does something.
And then very slowly start fixing things. I just hate the sell-now, maybe-fix-later thing.
Decided to flash sw 20210517 and stop the hacking for a while.
It seems prety stable. I've hit the buttons and knobs like there was no tomorrow, no lockups for now.
Undefined settings doesn't seem to cause any trouble. Signal gen works too.
Did they hack themselves? It's "undefined" the master hack that enables everything? :-DD
I think someone complained about the signal gen not going below 100Hz.
Well, at least in 20210517 version, it goes down to 0.1Hz.
However Fmax is different for each wave type:
- Sine: 25MHz
- Square: 10MHz
- Ramp: 1MHz
- Exp: 5MHz
- DC mode works.(Previously greyed out). Amplitude is disabled, and you adjust offset.
But the offset is way off!
- 1V=1.2
- 2V=2.4
- 3V=3.6
- 3.5V=3.9
It happens in all gen modes.
Calibration: In DC and AC modes it seems ok. But setting coupling ton GND the signal goes negative, 1/2 division below ref.
Trigger works pretty nice, but not perfect. Ex. 1Vpp test signal:
In 50mV/div or more it shows great.
In 20mV/div and below it moves like crazy. Clearly trigger not doing ok.
The decoders work really bad. Most of the time they don't find anything, or they're wrong.
A big issue there: Memory depth is limited to 4K in when decoder is enabled. So you won't get more than few bytes...
Zooming causes a line to be drawn over the decoded data.
PC software: I installed the drivers, windows recognized the device as "USB Test and Measurement Device (IVI)".
But neither DigitalScope or WaveEditor were able to connect, complaining with message "The device is not connected".
Edit: After reinstalling the driver with the scope already connected, it worked.
The custom waveforms can be set up to 25MHz too.
HR mode looks a lot better!
(https://www.eevblog.com/forum/testgear/new-hantek-dso2x1x-models/?action=dlattach;attach=1224189)
-
...
The decoders work really bad. Most of the time they don't find anything, or they're wrong.
A big issue there: Memory depth is limited to 4K in when decoder is enabled. So you won't get more than few bytes...
Zooming causes a line to be drawn over the decoded data.
...
First, thank you for your detailed review of what works and what doesn't on this $200 DSO.
Regarding the protocol decoders, I have found that an incredibly cheap $8 USB logic analyzer + open source sigrok software is a much better tool than any MSO/DSO: you get a much larger and better screen, many, many more protocols and more flexibility in how the data is displayed, a huge memory depth, etc.
So I think it's a matter of using the right tool for the right job. Likewise for the function generator. If you really need one, it's much better to have a separate instrument on your workbench.
Apart from that, it's undeniable that this relatively new Hantek DSO has a few firmware issues, but Hantek has been coming out with firmware updates quite regularly, so I would expect these bugs to be ironed out over time, and they have not prevented me from using the DSO for its original basic purpose, which is observing waveforms.
-
David, many thanks for detailed report.
Your finding pretty much same as mines after installing dso3kb_20210510.
As far a Decode function is concerned I have only used it on a sort UART message of twenty bytes or so and it works well after bit of setup fiddling.
If you can't get Decode to sync up try power off, sometimes you have to do it twice to get the scope to start up cleanly.
One thing that really messes up the decode function is Auto Set eg. Get Decode setup and working then press Auto Set.
And i have twiddled for ages trying to get Decode to work properly again, power cycling scope twice and Decode works again.
I think accepting scope performance for what it is price limited and hassle HanTek to fix these reliability issues is a good approach.
And little logic analyzer if you want to decode big data streams.
imk
-
Yeah, I have one of these 24MHz cheap analyzers since long time ago.
Sigrok does great, also sealae sw 2.x (Big improvement over 1.x)
-
Yeah, I have one of these 24MHz cheap analyzers since long time ago.
Sigrok does great, also sealae sw 2.x (Big improvement over 1.x)
David i think you are in good position to do serial decoding job etc.
So you need to decide if you want to exchange your DSO2 for something better and get a separate signal generator.
Or hang on to the DSO2 and bagger hantek into sorting the unwelcome features.
I think i am sticking with the DSO2 as is ok go no go scope for me as now i have resized on the house my man cave has limited space.
So this little all in same box really suits my needs now.
I'll start this afternoon to write letter to HanTek as this morning am going to meet electronic friend i have known for 50 plus years.
To take a look at this old cossor scope he has found in loft, seems to lack protocol decoding :-)
imk
-
Protocol decoding was not the main reason to buy it. It just was a nice plus.
The usb analyzer can do a lot better, with no limits at all. You can capture huge data frames as long as you have enough memory.
But the other bugged stuff do need fixing!
Thats scope might be the oldest I've ever seen! Not even BNCs! 1KHz BW? :-DD
-
Iv'e just been having a peek though the xml files and notice there's a calibrate and a calibrate_user mentioned in the files.
I've now got the feeling we as users shouldn't be touching the two calibrate setting we see in the updated firmwares and we've (thanks to Hantek) have screwed up the factory calibrations of our scopes.
:-/O |O
I think I'll return mine. There's a lot to like about these scopes, but until such time as Hantek can get a working firmware its not worth the struggle.
-
In case anybody wants to try recompiling the kernel, here is a possible config file:
https://raw.githubusercontent.com/thirtythreeforty/businesscard-linux/master/board/businesscard/v1/linux_defconfig
The patched linux kernel version 5.2.2, a dtb, and lots more information can be found here: https://github.com/thirtythreeforty/businesscard-linux
If you are stuck at any step, PM me and I'll do my best to help.
-
Stuck at step 0! I know nothing about kernel compìling.
-
Iv'e just been having a peek though the xml files and notice there's a calibrate and a calibrate_user mentioned in the files.
I've now got the feeling we as users shouldn't be touching the two calibrate setting we see in the updated firmwares and we've (thanks to Hantek) have screwed up the factory calibrations of our scopes.
:-/O |O
I think I'll return mine. There's a lot to like about these scopes, but until such time as Hantek can get a working firmware its not worth the struggle.
I only see one calibrate options in my menus?
I have been testing my scope with dso3kb_20210510 most of afternoon displaying simple sine and square waveforms over wide range of speeds and haven't been able to crash it.
Yesterday when testing UART triggering and decoding a 1hz refresh rate short serial message i could crash the scope regularly in RUN mode by adjusting Dev/Sec rapidly.
It didn't happen in Single Seq trigger mode, so it seems that during a re-display if i changed the dev/sec i could cause it to hang.
Hence I think this is a repeatable bug that should be easy to fix, anyone else done similar test and have repeatable hang.
imk
-
...
Yesterday when testing UART triggering and decoding a 1hz refresh rate short serial message i could crash the scope regularly in RUN mode by adjusting Dev/Sec rapidly.
It didn't happen in Single Seq trigger mode, so it seems that during a re-display if i changed the dev/sec i could cause it to hang.
Hence I think this is a repeatable bug that should be easy to fix, anyone else done similar test and have repeatable hang.
imk
Well done, imk. :-+
I think finding reproducible bugs and reporting them to Hantek politely is more likely to get them fixed than simply returning the DSO to China. :scared:
-
...
Yesterday when testing UART triggering and decoding a 1hz refresh rate short serial message i could crash the scope regularly in RUN mode by adjusting Dev/Sec rapidly.
It didn't happen in Single Seq trigger mode, so it seems that during a re-display if i changed the dev/sec i could cause it to hang.
Hence I think this is a repeatable bug that should be easy to fix, anyone else done similar test and have repeatable hang.
imk
Well done, imk. :-+
I think finding reproducible bugs and reporting them to Hantek politely is more likely to get them fixed than simply returning the DSO to China. :scared:
Hello Andrew, Many thanks for the thanks.
Spent couple of hours this morning testing this lockup and on simply sine/square waves NOT ONE SINGLE LOCKUP so dso3kb_20210510 is much better than dso3kb_20210416 :-)
Then setup DSO2D10 in RUN MODE UART Trigger/Decode on a changing 20 byte serial message repeated ever second.
===== Thank you Arduino for great little IDE that makes writing testing jigs soooooooo easy =====
Left it running for hour or so and NEVER locked up once, then slowly (One Click Per Msg Refresh) twiddled the Dev/Sec for ages and NEVER locked up once.
Then twiddled the Dev/Sec rapidly and within a few seconds I could cause the DSO2D10 to lockup, powered off/on and fault is repeatable.
Then repeated the above in STOP MODE and manually armed the trigger and could NOT get the DSO2D10 to lockup.
So it seems that if the DSO2D10 is refreshing the display/prepping the view post trigger in RUN MODE then it is sensitive to rapid changes to the timebase Sec/Dev control.
I have in much more detail with photos sent it of to Amy at Hantek and am looking forward to a positive response.
Next I shall test the other serial protocol trigger/decodes starting with i2c.
But i think i deserve respite from scope testing for few hours so getting the solder iron out as getting flux fumes withdrawals :-(
All best imk
-
I found a little annoying bug. The usb drive doesn't get mounted automatically in 20210517 SW.
However when you go to Utility menu and click Update, it gets mounted.
This can be seen on the console. The usb drive was plugged for a while (+1minute) and nothing happened.
After pushing update:
[ 427.926037] phy phy-1c13400.phy.0: Changing dr_mode to 1
[ 427.931558] read not supported msg id 2
[ 428.582770] usb 1-1: new high-speed USB device number 2 using musb-hdrc
[ 428.809222] usb-storage 1-1:1.0: USB Mass Storage device detected
[ 428.872963] scsi host0: usb-storage 1-1:1.0
[ 429.926631] scsi 0:0:0:0: Direct-Access Kingston DataTraveler 2.0 PMAP PQ: 0 ANSI: 6
[ 429.939195] sd 0:0:0:0: [sda] 30240768 512-byte logical blocks: (15.5 GB/14.4 GiB)
[ 430.019892] sd 0:0:0:0: [sda] Write Protect is off
[ 430.030880] sd 0:0:0:0: Attached scsi generic sg0 type 0
[ 430.102795] sd 0:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[ 430.333670] sda: sda1
[ 430.353794] sd 0:0:0:0: [sda] Attached SCSI removable disk
[ 431.295795] FAT-fs (sda1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
0:Got Signal with value mount
It doesn't even appear in the system.
It's like the USB controller is disabled, or stuck in device mode, not noticing a USB was connected and changing to Host mode.
After boot:
# lsusb
Bus 001 Device 001: ID 1d6b:0002
After clicking update:
# lsusb
Bus 001 Device 001: ID 1d6b:0002
Bus 001 Device 002: ID 0930:6545
-
I found a little annoying bug. The usb drive doesn't get mounted automatically in 20210517 SW.
However when you go to Utility menu and click Update, it gets mounted.
This can be seen on the console. The usb drive was plugged for a while (+1minute) and nothing happened.
After pushing update:
[ 427.926037] phy phy-1c13400.phy.0: Changing dr_mode to 1
[ 427.931558] read not supported msg id 2
[ 428.582770] usb 1-1: new high-speed USB device number 2 using musb-hdrc
[ 428.809222] usb-storage 1-1:1.0: USB Mass Storage device detected
[ 428.872963] scsi host0: usb-storage 1-1:1.0
[ 429.926631] scsi 0:0:0:0: Direct-Access Kingston DataTraveler 2.0 PMAP PQ: 0 ANSI: 6
[ 429.939195] sd 0:0:0:0: [sda] 30240768 512-byte logical blocks: (15.5 GB/14.4 GiB)
[ 430.019892] sd 0:0:0:0: [sda] Write Protect is off
[ 430.030880] sd 0:0:0:0: Attached scsi generic sg0 type 0
[ 430.102795] sd 0:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[ 430.333670] sda: sda1
[ 430.353794] sd 0:0:0:0: [sda] Attached SCSI removable disk
[ 431.295795] FAT-fs (sda1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
0:Got Signal with value mount
Hello David, good find re this bug are you going to report it to Hantek? at 'support@hantek.com'
I think the more we bring this stuff to there attention the sooner we will have a great little not big bucks scope!
imk
-
Is anyone here already being in contact with Hantek?
I think it's better to have just one person updating them with the news in this thread, instead a dozen people spamming their support mail.
I sent an email to them asking if it was posssible to help by testing their new firmwares and giving feedback about the results.
If they agree ( I don't think so) it would be great!
-
Is anyone here already being in contact with Hantek?
I think it's better to have just one person updating them with the news in this thread, instead a dozen people spamming their support mail.
I sent an email to them asking if it was posssible to help by testing their new firmwares and giving feedback about the results.
If they agree ( I don't think so) it would be great!
David I contacted Hantek on 25/May and have received as you know dso3kb_20210510 which is better than the installed dso3kb_20210416
I have today sent them the latest bug report as outlined in previous post.
I am not sure if one person reporting bugs or multiple people the same bug will return the best result?
I am open to either, but do we all have the same scope e.g same model, board version and unhacked etc
imk
-
Did you try 20210517?It's been there for a long time
-
Hello.DSO2D15
I installed the firmware dso3kb_20210510 Firmware: 3200.
there was a firmware dso3kb_20201118
Firmware: 3000.
how to get back Firmware: 3000?
-
Did you try 20210517?It's been there for a long time
David
20210517 I can only see dso3kb_20210416 on Hantek site and dso3kb_20210510 is one they sent me a link to (think it maybe beta)
where did you find 20210517?
imk
-
Hello.DSO2D15
I installed the firmware dso3kb_20210510 Firmware: 3200.
there was a firmware dso3kb_20201118
Firmware: 3000.
how to get back Firmware: 3000?
You have to use platform tools. Check my google drive folder.
Some will change your FW to 3101 or 3102, but they all work ok if you had FW3000.
The only fw making trouble is 20210510, that changes it to FW3200 and breaks calibration.
Mine was 3000, I installed 20210517(FW3102) and it works a lot better than the old versions.
If you have any issues, you can flash 20201221(FW3000) that will completely restore it.
Serial, model and HW will be undefined after flashing platform tools, but it doesn't seem to matter.
If you want restore them, copy the script do_other_update(Edit Model-Serial-Hardware) to the root of the usb drive.
Rename it to do_other_update. Edit and change the model and serial number.
Then you can update throught the system menu to the latest compatible version (actually 20210416).
If "do_other_update" is present, the system will run it automatically.
where did you find 20210517?
Someone sent be a PM with that fw. It's not an update, but a full fw, it's in platform tools.
-
David thanks for the platform-tools-20210517(FW3102) info.
I had a look and think i'll await reply from Hantek rather than brick my scope.
imk
-
Thank you, your firmware helped.
-
I had a look and think i'll await reply from Hantek rather than brick my scope.
They're unbrickable, don't worry about that, FEL mode is a low level boot mode linked to the SOC itself.
No matter what, you can always enter FEL mode by pushing the button below the DSO and powering it on, then flash anything.
I erased the whole flash. I even removed it physically. It always works.
Thank you, your firmware helped.
Nice! But that fw is old and very unstable. It has a lot of issues. Try without fear the 3102 version!
-
Hello followers of this thread,
Re my previous post re UART Trigger/Decode locking up the scope when adjust the timebase Sec/Dev.
I have just completed testing with i2c Trigger/Decode and problem is the same sorry to report, hence i think there is some generic refresh serial trigger issue.
Also when i was testing the i2c serial trigger I adjusted the Acquire->Mem Depth from 4k to 4m and scope locked up :-(
However a simple power off/on cycle does not fix the problem as when the scope starts up it is still in 4m mode and immediately crashes again.
So i had to unplug the leads to remove input signals, reset mem depth to 4k, then plug the leads in again.
I have reported this and previous UART serial trigger/decode to Hantek.
Lastly the i2c Sync Decode is terrible, monitor mode is not too bad, but analyzing a complex i2c data sequence will be difficult as only a few bytes of data is displayed.
Even i am beginning to lose faith in this scope, or maybe my expectations were simply to high.
I still think as a simple waveform (sine/square bit of audio ) scope with integrated signal generator it seems to work well and is probably good value for monies.
But for protocol decoding I will be using my DreamSource Lab logic analyzer.
As I don't think this range of scopes has enough horse power or software sophistication to handle serial protocol triggering/decoding.
I hope Hantek fix the problems and prove me wrong :-)
imk
-
Tell me where to download version 3102?
Thanks a lot in advance.
-
after the firmware(dso3kb_20210416) usb stopped working.
Sorry for my English.
https://youtu.be/8ov14v8Vshg
-
Yes, that's something I noticed too!
A fix is going to utility/update, without updating.
It will enable de USB and start working.
-
//Hi David.
//Can you find out in more detail what I need to do?
//After all, the usb port does not respond to usb memory.
//maybe others already had such a problem and it was already mentioned on the forum?
-------------------------------------------------------------------------------------------------------------------
Thanks, I figured it out by reading the forum and working with your files.
Version 3102 did not work, and now version 3101 has been installed and is being calibrated.
-
Dude, let's keep that stuff in the hacking thread!
I also made the same mistake... deleted that :D
-
:popcorn: :popcorn: :popcorn:
https://m.youtube.com/watch?v=9V23MEiwmZ8
-
Well, nobody can say this scope is a useless toy anymore... :-DD
-
:-DD
-
It gives an idea of the poor performance of the CPU...
At default CPU speed the game runs pretty choppy, it needs almost 700MHz to run properly.
The stm32F429 does a lot better at 168MHz, that's the difference of having a FPU!
-
OMG this is just A-M-A-Z-I-N-G! :-BROKE :scared: :scared: :scared: :popcorn:
-
It gives an idea of the poor performance of the CPU...
At default CPU speed the game runs pretty choppy, it needs almost 700MHz to run properly.
The stm32F429 does a lot better at 168MHz, that's the difference of having a FPU!
Yes, the ARM926 CPU in the L2C100s is a 20-year old design from 2001(!), while the Cortex-M4 in the STM32F429 is a much more recent architecture. I think AllWinner went with the ARM926 for this chip because they got the IP for next to nothing. This CPU is supposed to cost $1 in quantity, while the STM32F429 costs around $5.
-
I wanted to make an update package that simply runs Doom, but there's a problem.
Whenever you start the update process, the keyboard is disabled on purpose to force rebooting.
So it would work but no way to play.
What I did was to install a daemon that monitors the Doom files, once the USB is plugged, it will stop Phoenix, start Doom, and wait for it to exit, then restart Phoenix.
The modification can be easily reversed.
I'll upload the files in a moment
-
I wanted to make an update package that simply runs Doom, but there's a problem.
Whenever you start the update process, the keyboard is disabled on purpose to force rebooting.
...
Hmmm, I think there is a good chance that what happens when you start the update process is that the USB keyboard driver (or some other keyboard driver) kernel module is unloaded, not that the keyboard is disabled per se.
As usual, you can check that quite easily with a simple lsmod command, before and after the update process is started.
-
Not exactly, because they key presses are still shown in dmesg.
It's something related to the shell.
The only thing I know is that libanolis starts the update package with "sh -c", which probably affects it.
I'm not a pro at linux
-
Not exactly, because they key presses are still shown in dmesg.
It's something related to the shell.
The only thing I know is that libanolis starts the update package with "sh -c", which probably affects it.
I'm not a pro at linux
When the shell is started with "sh -c <string>" then the shell does not accept input from the keyboard but instead takes the string and processes it as a command.
-
Not exactly, because they key presses are still shown in dmesg.
It's something related to the shell.
The only thing I know is that libanolis starts the update package with "sh -c", which probably affects it.
I'm not a pro at linux
When the shell is started with "sh -c <string>" then the shell does not accept input from the keyboard but instead takes the string and processes it as a command.
And as that's done by the updater process, I guess it's impossible to escape that.
I mean, the updater script is executed inside that shell.
In the end I made a doom package anyways, but it runs automatically when the doom files are found.
You can see my issue more detailed in the hacking thread.
To run doom, check my drive folder! (Fixed the link in my profile) :box:
-
after the firmware(dso3kb_20210416) usb stopped working.
Sorry for my English.
https://youtu.be/8ov14v8Vshg
Sergey,
I have the same version of DSO2D15 - ordered it earlier in the week and it arrived yesterday.
I put the latest version of the firmware from the hantek.com website on it without issues except I didn't know that the .rar file has to be unpacked to be a .upk file before it becomes accessible. Not had any issues with the old firmware or the new one. USB stick continues to work and I saved some .bmp (see the attached) when learning how the scope works.
Are there different versions of the hardware as I see references to 3000 and similar numbers of the forum?
Simon
[attach=1]
-
It appears there're 3000, 3101, 3102 and 3200 versions.
Apparently 3200 breaks calibration on other versions. Nothing to worry about, as it's easy to restore it.
But none of the system updates from hantek changes that (except 20210510, which was removed fron Hantek site)
-
after the firmware(dso3kb_20210416) usb stopped working.
Sorry for my English.
https://youtu.be/8ov14v8Vshg
Sergey,
I have the same version of DSO2D15 - ordered it earlier in the week and it arrived yesterday.
I put the latest version of the firmware from the hantek.com website on it without issues except I didn't know that the .rar file has to be unpacked to be a .upk file before it becomes accessible. Not had any issues with the old firmware or the new one. USB stick continues to work and I saved some .bmp (see the attached) when learning how the scope works.
Are there different versions of the hardware as I see references to 3000 and similar numbers of the forum?
Simon
(Attachment Link)
Hello SimonM
I have the DSO2D10 and if you follow this thread you will see i only received my scope couple of weeks ago and have found some very annoying bugs
The most significant of these was it crashed and had to be power cycled to get it going again.
What caused it to crash was using the rotary encoder controls like Vertical Position, Volts/Dev and timebase Sec/Dev.
My scope came with installed Software 20210416, i contacted Hantek about this lockup issues and they sent to me a link to download dso3kb_20210510 from.
After installing dso3kb_20210510 it still shows up in the info screen as 20210416 (I guess an oversight when they rebuilt the code in a rush)
dso3kb_20210510 has significantly improved my DSO2D10 with respect the the crashes in normal waveform use Sine/Square etc in fact it hasn't crashed once.
However dso3kb_20210510 still has significant crash/lockup issues when using UART/i2c Serial Triggering/Decoding in RUN Mode.
Inasmuch as i you rapidly operate the Sec/Dev timebase control during Serial Trigger/Refresh cycle it locks up, so rotate Sec/Dev with care and you maybe ok.
So i have emailed Hantek again and am looking forward to another software upgrade in the no to distant future i hope.
However, I don't think dso3kb_20210510 was well tested as it seems to have caused several other issues so upgrade to it with caution.
You can see on my previous posts some of the issues I have reported to Hantak.
Hope it works out for you imk
-
However, I don't think dso3kb_20210510 was well tested as it seems to have caused several other issues so upgrade to it with caution.
You can see on my previous posts some of the issues I have reported to Hantek.
Hi Imk,
You can see that I only made one post before today and I'm still trying to figure out some things about the scope.
It has been 40 years between using a scope at university and now when I wanted one. For a while, at work, I used logic analyzers, but it has been a software-only world for me for the last 30+ years. For what I want now - using Raspberry Pi and Arduino the 10 version would have more than met my requirements but was out of stock so that's why I have the 15 version. It was also a gift so the additional small cost was covered by the giver!
The version of the software on mine was older than yours and I did consider leaving it ASIS but eventually decided that it made sense to use the latest published version. It may have been a mistake as I didn't have any problems and I still can't find issues with the current version. I have tried the timebase and voltage sensitivity changes but don't get any kind of lockup.
You mentioned a newer firmware version and I notice that this was initially put on the Hantek site and then withdrawn. I know from writing and supporting software that fixes are published and eventually "rolled" into a new release. Since it can be difficult to build fixes for everyone there seems to be a tendency to roll up support updates for several issues and there may be problems resolved but also new undesirable "features" (bugs) that also get introduced.
If I had an issue that required an update and I could be sure that I could revert to a previous version then I would take an update to verify that something could be fixed but probably go back to a known version and wait for the official release. I would also wait a time to see if the new version is deemed a success by the community. It seems this later version was rushed out to please a few folks but also regressed a few things (I also don't want to be a long-term beta tester...). Perhaps you know that it is possible to go back to a previous version?
The FFT for analyzing harmonics looked interesting and I realize that the number of samples points is limited (compared to a dedication SA), so I was initially disappointed that I couldn't look at a square wave and set the "span" to show just a few of the odd harmonics. I was going to write it off until I realized that the calculation requires thoughtful selection of timebase e.g. garbage in = garbage out (user error). Now that I have a better understanding, all is well and the results are what you expect. I haven't noticed a delay from setting it up to seeing the result and I do like the immediate feedback of twiddling knobs rather than clicking software and simulating things with software. That's also why I wanted a "bench" scope and not a unit that needs to be connected to a PC. For me, that would just be too convoluted. The signal generator function is more than I might need and I don't already have one to experiment with.
Is there any difference with the B probes? I see the spec for PP-150B and PP-150 and they seem the same? They are also both 100 Mhz probes so I can't see any reason to use 150 in the name. The same thing for the other probes, as the naming doesn't match the -3dB response of the (theoretical) spec. To match a probe to a scope, isn't it necessary to use a much higher rated probe as the response is something like the square root of the sum of both probe and scope. I noticed that the response of a PP-150 doesn't fall off much to about 350 Mhz e.g. is probably better than you might think. In fact, I do wonder if there really is much difference with the more expensive probes (except, they keep more of your dollars).
One thing about a probe, when the clip is removed, should there be a probe point? I am probably doing something wrong because the probe tip is in the hook part and so the probe accessories like the spring and yellow covers etc. have no use, and the probe can't be used without the hook. Perhaps the PP-150B just means PP-150 (broken version). Perhaps my understanding falls a bit short and you can of course forget a lot in 40 years!
Simon
-
Hello Simon,
So which version did you install the dso3kb_20210416 or dso3kb_20210510 my scope came with dso3kb_20210416 and was crashing all the time.
I notified Hantek and couple of days later they sent me a link to download dso3kb_20210510.
After installing it the situation has improved as and now only seems to crash when serial triggering and protocol decoding.
Although when serial triggering I changed the memory depth from 4k to 4m and it crashed.
It is interesting to note that after installing dso3kb_20210510 it still shows in the utility menu that dso3kb_20210416 is installed.
However there is a 5k size on disk difference between the dso3kb_20210416 and dso3kb_20210510 plus it is more stable on my scope.
Which raises an interesting question, are there different hardware versions of this scope and there will there ever be a firmware that works well on all versions.
As for me and my scope, i am still wondering whether to keep it or get the siglent SDS1202X-E and a separate waveform generator which was something i was really trying to avoid as i have limited space these days.
imk
-
Simon I think the B is just for the "black" aesthetic to match the scope styling. There is a PP200B as well in the black style.
The probes are physically different - the compensation adjustment on the B ones is at the probe, on the non-B it is at the BNC end. And the ground clip is shrouded on the B. No idea if they perform differently though.
-
I found that anything over 40K limits to 250Msps.
Also, I'm starting to think that the 1Gsps is BS.
Reading a 160MHz signal, the result is the same whether CH2 is enabled or not...
-
Good analysis Simon. It would make sense for there to be faster caching for short bursts, but then a reduced rate for extended memory access once the cache area is exceeded.
Interesting that the memory can be overclocked so much though (see the hacking thread) to the point where the larger storage sample rate could potentially be doubled.
-
My DSO2D15 is a lemon and Hantek’s support sucks
In March I bought a DSO2D15 having read the posts on various forums which gave the consensus that the Hantek hardware was acceptable but the software was rather buggy. On receiving the DSO and exploring is features various software bugs that locked up the machine were experienced but as Hantek were issuing firmware updates I expected they would eventually have fixes for major software problems.
Unfortunately I then begin to find that my unit exhibited a number of significant problems in its basic operation.
• Traces exhibited phantom noise on signals. I don’t mean digitation noise of a minor division or so, but random spikes that can be up to 1 major division high on displayed waveforms, including those directly from its internal signal generator.
• Poor triggering. The unit is unable to sync stably on just basic waveforms, even its calibrator and its internal signal generator.
• Significant offset on channel traces after zeroing. The voltage measurements displayed are affected by these DC offsets. On attempting calibration to correct the problem the calibration procedure usually failed with varying error messages. Even if successful the offsets remained.
These problems mean that the scope cannot be relied on to stably or accurately display even basic signals.
After trying a number of the firmware up-grades without any success in resolving these problems I contacted Hantek support. In describing the problems, I mentioned that I had observed the waveforms from the internal generator and from external circuits with my analog scope and that the waveforms appeared clean and were able to stably trigger.
Hantek asked me to send them comparative videos of the DSO and the analog scope to show the problems described. I sent the videos. Now after 4 weeks I have received no response, even though I sent weekly follow up emails. In my last email I advised Hantek that if I did not receive a response I would post the problems with their instrument to the EEVBlog Forum for all to see. No reply was received.
It appears to me that these problems are either hardware design issues or a manufacture problem with my particular unit.
I would therefore suggest to those contemplating the purchase of a DSO2x1x to be aware that they could also receive a lemon and if so will get poor/no support from Hantek.
If anyone is interested in seeing the videos and screen captures of the problems, they are at https://drive.google.com/drive/folders/1MrwXf4mSIksYND4oyVKzrqQihpCTnqy2?usp=sharing
Sorry about the x-post but I originally posted to a less visited topic.
-
I too am returning the scope to Amazon. I've been emailing Hantek about the calibration problem for a few weeks and each time I get the same reply about letting the device warm up for half a hour before calibrating.
It just isn't getting though to them that there's a fault with these scopes that needs addressing.
Marvinmg - what version of the firmware are you running? All the ones I've tried show "DC, AC RMS and DC RMS" on the DVM.
I also have a fault with captures that fill the acquire buffer. If I scroll to the end of the capture there's a massive amount of noise at the end of the buffer. Attached pic shows input from signal generator, CH1 is clean, CH2 is full of noise.
-
MarvinMg
I noticed on one of your videos you had the trigger mode set to Auto, do you find it more reliable in Normal.
I am going to make a video of the Serial Trigger/Decode lockup problems i am having later this evening, i'll post again when done. .
imk
-
As promised here is link to lockup video while adjusting the timebase sec/dev during Serial Trigger/Decode.
As in the video sometime it takes only a turn or two of the Timebase other times it takes a bit more effort to expose the problem.
When i originally received the scope about two weeks ago, adjusting almost any of the Rotatory Encoders would cause the scope to freeze.
So i contacted Hantek support and the sent to me dso3kb_20210510.zip which has helped a lot.
Inasmuch as much as i can display normal waveform sine/square on both channel over a wide frequency range without issues
However as can be seen the scope freezes during serial trigger decodes for the two serial protocol I have tested UART and i2C
Plus i have had lockup issues when adjusting the Acquire->Mem Depth to 4m
Also sometimes the SDA goes nuts and just displays Noise Spikes at high Mem Depth's
https://www.youtube.com/watch?v=xjrnT3Fk-yE (https://www.youtube.com/watch?v=xjrnT3Fk-yE) (Filmed Entirely On Location "My Man Cave" )
imk
PS I just did same test again and in first click on the Timebase Sec/Dev it locked up :-)
It is random inasmuch as it happens just when you catch the refresh at the wrong time, ouch!
-
Sometimes when display serial protocol triggering the display goes noisy.
Sometimes the SDA of i2c get completely distorted and almost looks like it is displaying some other protocol
https://www.youtube.com/watch?v=e6Vp4lDu_QE (https://www.youtube.com/watch?v=e6Vp4lDu_QE)
-
Simon,
I2c is bit trick to setup, so us UART serial trigger decode
Write a simple Arduino app to send "Hello World" to the serial port at 9600 bps every second
and setup scope to Serial Trigger off that and problem is same one my scope.
Tricky bit to setup on the scope is the Data Byte to trigger off Look For The Two Little Red Dots, took me two hours to spot them, tired eyes :-(
-
Simon,
Did you go through the calibrate process on your scope?
As far as serial trigger is concerned when you have your Arduino app sending.
Trigger off falling edge first (the start space)
When you have that working, move on to trigger of a data byte in the message, it is bit more trick to setup
I am out this morning to mid afternoon so will catch up with progress early evening.
Sent the two video links to hantek but no reply yet.
imk
-
I noticed that after warming up and calibrating the device, version 3101 of the signal generator works with overvoltage.
And the instrument has stopped copying the image to USB.
-
I noticed that after warming up and calibrating the device, version 3101 of the signal generator works with overvoltage.
And the instrument has stopped copying the image to USB.
Is it the signal generator or the scope's voltage reading that's wrong?
-
Shows exactly 5 v from the calibration output
-
RE: My DSO2D15 is a lemon and Hantek’s support sucks
A few clarifications to questions I have been asked on the setup and software version of my problem scope.
Software 1.0.1.1.0 (20210416.00)
Hardware 000.000.000.000.000.000.000.001
Firmware 3000
I have not updated the software past the mid-April version expecting that Hantek would ask for further clarifications and did not want to introduce new variables.
I believe that I did my due diligence before purchase. I was prepared to put up with some software bugs but not for this lack of basic functionality. We use a number of earlier model Hanteks where I work and they are fit for purpose.
Wherever possible the tests were undertaken with the scope’s default setup settings and the recordings used the internal generator’s default 1KHz sine/square wave output.
I also checked with the output from a Tektronix ARB and saw the same problems.
I usually use Manual trigger settings on a scope but the Hantek defaults to Auto. Trying Manual makes no improvement though. The scope often would not trigger at all or freezes after selecting manual.
The error messages received on calibrate were 51126 and 50081. Hantek has not told me what these codes mean. Up to now I have been dealing with caiyijun@hantek.com so if anyone knows of someone at Hantek who is helpful I would appreciate an email address.
-
Mine also has the Lemontree 2090, came with SW 20201221 and had a lot of crashing too, it was so bad that I almost returned it.
Since I overclocked it, the crashes are very rare. Even with the same factory fw. So I guess the main issue is the CPU not being fast enough to react to the events.
I finger-probed the soc while running pi bechmark. The temperatures were warm, not burning hot. So it's ok.
Also, the CPU voltage is untouched (Although I will look into this, reaching 1GHz would be great :-DD)
After a week of using it with no major issues at all (Except crappy decoders and defficient trigger detection in some Vdiv modes), yesterday I crashed the system because I forgot a " in a boot script, causing the system to hang in the middle of the boot process.
I flashed with platform tools, and didn't remember to apply the overclock script. It felt like a gameboy minning bitcoins!
After reinstalling it, it was much better. It'll never perform like a $1000 DSO, but at least it's better than factory.
I made a safe update script to apply overclock at boot time, check my GDrive folder!
- Unzip the file into the root of the usb drive
- The overclock folder should be in the root of the drive
Install
- Run system update and select "dso3kb_install_overclock.upk" file.
- The system will reboot automatically.
Uninstall
- Run system update and select "dso3kb_remove_overclock.upk" file.
- The system will reboot automatically.
Notes:
- The update consists on 2 files: S99overclock.sh (Runs last at system boot) and oc_manager (Executed as daemon by S99overclock).
- Before applying overclock, it will ensure the system clocks are unmodified.
- There's a delay of 15 seconds to let the FPGA init, so the keyboard works. To abort overclocking press F0 key within that time.
- If you modify any file inside overclock folder, run the install package again!
-
I found that anything over 40K limits to 250Msps.
Also, I'm starting to think that the 1Gsps is BS.
Reading a 160MHz signal, the result is the same whether CH2 is enabled or not...
I was looking at a signal with the timebase turned up (to 2ns a division) at an edge. To see the individual dots it helps to have a single shot trigger enabled otherwise it can start to look like vectors.
In the "acquire" screen you can select the memory depth. The 8M option disappears with two channels operating. That seems reasonable because there is only so much memory and so the depth is limited. With the other options, the depth doesn't differ, but then you are not using all the memory anyway.
In the 'display" memory, you can switch between "vector" and "dot". Since the vector mode joins the dots it can be difficult to know when sampling is done. With the dot mode, you will see each dot, and switching the 2nd channel off has several effects:
1. The number of dots doubles e.g. with a 2ns a division showing you will see an edge with dots increasing in Y and placed every 1/2 division.
2. Sampling says 1gs/s e.g. it agrees with what you see. With the second channel on the intermediate dots disappear and the sampling drops from 1 g/s to 500m/s.
When you increase the memory to 400k or higher then the sample rate drops back to 250 m/s or 125 m/s. This suggests that there are two types of memory e.g. a smaller and faster cache and slower memory. Again, that seems reasonable as something has to give when you have access to more memory.
Simon
You're right. The problems comes else from the resolution or the processing. It's so rough that it barely makes any difference.
I guess if the lowest V/div settings are not being amplified, directly feeding the ADC (using less bits).
Because it has more steps than my 5th floor without elevator! All the steps are done in the same y positions, so it's clearly a bit resolution thing.
Check the attached pic. All the steps are exactly at the same Y position. I counted a total 40 vertical steps for the 8 vertical divs.
It would be ok-ish if at least, when zooming out the voltage, you could see the whole signal.
But saturating the signal in 2mV mode and going back to 5mV, you get a square signal of 4 divs. That means the signal was clipped to 200mV.
200mV would be 10 vertical divs in 2mV mode, which would make a total of 50steps and just 5.6 bits resolution.
I think I'll return this crap!
-
It felt like a gameboy minning bitcoins!
Did overclocking help with Roll mode? Roll mode is horribly jerky and shows just how woefully underpowered the CPU is.
(Mine has been returned, I'm not convinced the problems will ever get properly fixed)
-
It helps a bit. It's extremely laggy by default, with oc it gets just crappy, but not that terrible ;D
-
Check the attached pic. All the steps are exactly at the same Y position. I counted a total 40 vertical steps for the 8 vertical divs.
It would be ok-ish if at least, when zooming out the voltage, you could see the whole signal.
But saturating the signal in 2mV mode and going back to 5mV, you get a square signal of 4 divs. That means the signal was clipped to 200mV.
200mV would be 10 vertical divs in 2mV mode, which would make a total of 50steps and just 5.6 bits resolution.
I think I'll return this crap!
When I try that I don't see the same jagged stepped output (see attached) - what do you get in dots rather than vector mode? What s/w f/w versions are you using?
I do see the same clipping on saturation, though.
-
Wtf, yours is a lot better! Will look into this. Mine is FW3000, running 20210416 SW.
Edit: It seems it was a calibration issue. Ran calibration again and it got much better! Not so angry now haha
-
Check the attached pic. All the steps are exactly at the same Y position. I counted a total 40 vertical steps for the 8 vertical divs.
It would be ok-ish if at least, when zooming out the voltage, you could see the whole signal.
But saturating the signal in 2mV mode and going back to 5mV, you get a square signal of 4 divs. That means the signal was clipped to 200mV.
200mV would be 10 vertical divs in 2mV mode, which would make a total of 50steps and just 5.6 bits resolution.
I think I'll return this crap!
When I try that I don't see the same jagged stepped output (see attached) - what do you get in dots rather than vector mode? What s/w f/w versions are you using?
I do see the same clipping on saturation, though.
(https://www.eevblog.com/forum/testgear/new-hantek-dso2x1x-models/?action=dlattach;attach=1226858)
I'd be far more worried about the triggering as the trigger points in that image ^ don't line up with the waveform. :-//
-
I tried the same thing.
No, you tried with 4k capture buffer. Try with 4M and a signal on both channels. That's where it showed for me.
-
My final words for a while re my DSO2D10 issues.
I just sent letter to David Hoo Sales Manager Hantek, China 266114
With copy to BangGood who i am very happy with, but they need to know about these Hantek problems.
As hopefully BangGood will stop selling Hantek products, along with all other Hantek distributers and it two years Hantek will be little more than a bad memory!
Imk
-
After overclocking, it became worse for me - it freezes constantly, and the amplitude of the generator increased by 25%. After removing the overclocking and flashing the platform, the amplitude did not change. How do I calibrate it now? But at what point it increased - I can't say for sure, perhaps before overclocking, but after the hack it was normal.
-
Try with 4M and a signal on both channels. That's where it showed for me.
Just tried with 2 channels, 4Mpt @ 125MSa/s and that also looks fine. Did crash the scope a few times getting there though.
Firmware 3200 s/w 20210416.00
I'd be far more worried about the triggering as the trigger points in that image ^ don't line up with the waveform. :-//
The triggering on these scopes is pretty abysmal for anything other than a sharp rising or falling edge.
-
My final words for a while re my DSO2D10 issues.
I just sent a letter to David Hoo Sales Manager Hantek, China 266114
With a copy to BangGood who I am very happy with, but they need to know about these Hantek problems.
As hopefully BangGood will stop selling Hantek products, along with all other Hantek distributers and in two years Hantek will be little more than a bad memory!
Imk
Good for you.
I have been enthusiastic about the DSO2D15 for seven days but I have absolutely lost my patience with it and it is going back to Amazon. They ask what is wrong in just a few words, my summary (did I miss anything?): "Scope issues: often loses sync between AWG, scope & Hantek's probes. Input is very noisy. The calibrated channel has DC offset. Scope hangs using knobs e.g. turn off/on [again]. Protocol decoding unreliable".
Simon
-
So this thread now becomes...
sds1202x-e OR ds1202z-e OR... :popcorn:
-
With the price of these DSO2X1X Series rising, Hantek best fix their software right. Considering OWON and FNIRSI have already put out their competing scopes on a similar platform / market.
Although more basic build quality (and matching price advantage), OWON and FNIRSI's software appears to actually work well enough for the entry level functions, Compared to the basic things that Hantek seems to struggle with maintaining in their software. I still feel Hantek has the most potential hardware wise (especially reading the datasheets for the chips they used), they really need push harder to fix their software.
-
It's too bad Hantek isn't willing to open source the software for this DSO. Imagine what the development community could do with it.
I know it's not as easy as my statement makes it sound but it would probably be easier than the way they are going at it now.
-
My final words for a while re my DSO2D10 issues.
I just sent a letter to David Hoo Sales Manager Hantek, China 266114
With a copy to BangGood who I am very happy with, but they need to know about these Hantek problems.
As hopefully BangGood will stop selling Hantek products, along with all other Hantek distributers and in two years Hantek will be little more than a bad memory!
Imk
Good for you.
I have been enthusiastic about the DSO2D15 for seven days but I have absolutely lost my patience with it and it is going back to Amazon. They ask what is wrong in just a few words, my summary (did I miss anything?): "Scope issues: often loses sync between AWG, scope & Hantek's probes. Input is very noisy. The calibrated channel has DC offset. Scope hangs using knobs e.g. turn off/on [again]. Protocol decoding unreliable".
That about sums it up for me, unreliable, software full of bugs, unresponsive Hantek support.
Interesting is when i initially complained they had a fix in two days, makes me think they new about the problem and had a bodge ready for those that reported the issue!
-
Simon,
I asked same question Siglent or Rigol https://www.eevblog.com/forum/testgear/siglent-sds1202x-e-or-rigol-ds1202z-e/new/?topicseen#new (https://www.eevblog.com/forum/testgear/siglent-sds1202x-e-or-rigol-ds1202z-e/new/?topicseen#new)
I think my money is on the https://siglent.co.uk/product/siglent-sds1104x-u-4ch-100mhz-1gsa-s-14mpts-super-phosphor-oscilloscope/ (https://siglent.co.uk/product/siglent-sds1104x-u-4ch-100mhz-1gsa-s-14mpts-super-phosphor-oscilloscope/)
Plus chk out eevblog reviews and you'll find a video on it that it not too damming
But i am going to wait a week to see what Hantek does, as i think my returning it door has closed due to waiting for Hantek support.
================ I should have returned it day one, rather than mess with support, if its bad, its bad :-( ===========
If Hantek don't come up with anything i'll ebay it and order a siglent, pity it doesn't have a simple sig gen.
Good luck imk
-
Simon,
I asked same question Siglent or Rigol https://www.eevblog.com/forum/testgear/siglent-sds1202x-e-or-rigol-ds1202z-e/new/?topicseen#new (https://www.eevblog.com/forum/testgear/siglent-sds1202x-e-or-rigol-ds1202z-e/new/?topicseen#new)
I think my money is on the https://siglent.co.uk/product/siglent-sds1104x-u-4ch-100mhz-1gsa-s-14mpts-super-phosphor-oscilloscope/ (https://siglent.co.uk/product/siglent-sds1104x-u-4ch-100mhz-1gsa-s-14mpts-super-phosphor-oscilloscope/)
Plus chk out eevblog reviews and you'll find a video on it that it not too damming
But i am going to wait a week to see what Hantek does, as i think my returning it door has closed due to waiting for Hantek support.
Hi Ian
Good luck with extending the returns window. My eyes are open to buying through the company you bought the scope through. So I'm following your story with interest. How you get on may determine how I shop in the future.
I think you could argue that you started the process of determining what was wrong with Hantek early and you did it politely too. Getting a resolution from the company also helps the company you bought it from because sending it back ultimately costs them money and they work on small enough margins. They should not be penalized for something they have limited control over.
You are giving Hantek an opportunity to fix things before you invoke a returns clause. It is not your fault if they dither or throw up a smokescreen in the hope that you will quietly accept the product ASIS.
I'm going to sign off on this topic/thread and move across to your thread. I have some links you may find interesting. With hindsight, I could have observed that issues with Hantek have been known for six months and the old Hantek 5000 series of products has not been successfully replaced with the 2000 series for home/hobbyist/enthusiasts who want good quality at a reasonable price. The price may be reasonable but there are two sides to this...
Hantek was a bit mean in only providing one probe. I bought a second Hantek probe to complement their scope - no surprises etc. I actually quite like the probe but I also think it is responsible for some noise issues and I will request a return to Amazon. I'm not clever enough to be able to distinguish issues between AWG, Hantek scope, and Hantek probes.
The promised replacement for the duff probe didn't materialize. The cynic in me makes me think that this is a ploy to delay returning the product until it is outside of a returns window. With good customer service I could forgive some minor issues but alas the walk and the talk don't coincide.
I can return a product that is obviously broken e.g. damaged. It is much harder to admit that one's own judgment was swayed by the promise of something that appeared to be "too good to be true". Of course, I didn't have any knowledge or experience of the products before buying, I should have been more diligent. Lesson learned.
Simon
-
I also opened a claim in Aliexpress. Conditions were clear, 15 days free return.
Since the products is unreliable, that's more like a warranty than a "I don't like it".
-
If the problems are minor, or you don't like something about the oscilloscope, it is easier to sell it than to return it back. In case of serious problems, there is only one way out - return. I had a sad experience of returning, I no longer want to repeat. In general, it works fine for me, hangs are only in the automatic measurement mode when the signal amplitude drops to zero, or when the cable is pulled out and then connected.
I returned my native memory, updated the hack and the amplitude of the generator was restored. I suspect that the reason was still overclocking.
-
I'd be far more worried about the triggering as the trigger points in that image ^ don't line up with the waveform. :-//
I've emailed Hantek to ask about triggering and sent them the attached "single seq" trigger as an example of how bad it can be. Will see what they say.
-
===== failed on self calibration ======
Maybe not unique to DSO2xxxx
https://www.ebay.co.uk/itm/393389306885?hash=item5b97d47405%3Ag%3AExcAAOSw6axgwxI7&LH_ItemCondition=3000 (https://www.ebay.co.uk/itm/393389306885?hash=item5b97d47405%3Ag%3AExcAAOSw6axgwxI7&LH_ItemCondition=3000)
-
So this thread now becomes...
sds1202x-e OR ds1202z-e OR... :popcorn:
OR SDS1104X-U ! :P
-
Hello tautech, I see NZ is awake, Saturday morning lay in over and breakfast on the table :-)
Ya i think the SDS1104X-U looks about best bang for buck up here, what is scope shopping like in NZ
-
Hello tautech, I see NZ is awake, Saturday morning lay in over and breakfast on the table :-)
Ya i think the SDS1104X-U looks about best bang for buck up here, what is scope shopping like in NZ
:)
PM returned and my advice is to get one locally.
-
And don't ever make single shot, and then slighly zoom the voltage in.
I got confused, wasn't sure about what I was seeing, bathroom tiles or a waveform!
A slow cpu, not the best ADC frontend, laggy response... all that is completely acceptable for the price.
It's their software what sucks. I was trying to figure out the noise in an audio signal. No way, the waveforms are thick as car battery wires!
-
I was trying to figure out the noise in an audio signal. No way, the waveforms are thick as car battery wires!
Did you try HF reject or any of the other acquire options?
-
Yes. Not a big difference.
Doing the average of 128 did a little better, but that will filter the signal, removing the real noise.
If you make a single shot, them zoom in 2-3 timesteps, you stretch the timebase with the same samples, so you get a clean, sharp waveform, although lacking precision.
-
NOTE: This message has been deleted by the forum moderator Halcyon for being against the forum rules and/or at the discretion of the moderator as being in the best interests of the forum community and the nature of the thread.
If you believe this to be in error, please contact the moderator involved.
An optional additional explanation is: Please post in English only. Moderators and admins cannot read Russian.
-
I had the same problem (answer 370) after overclocking (maybe, but not 100%). Re-flashing by the platform did not give anything, I tried different versions. Before hacking my C10, I dropped the memory, copied and saved, and used another memory to hack, as Vistorik advised. I returned my native memory, tk. This one was not stitched with a clothespin, but I do not have an adapter and everything fell into place. Now you have to upload someone's dump.
-
Read the thread. Did you flash fw3000 with platform-tools?
-
If the question is for me, then yes, I stitched it with different versions, this did not affect the generator.
-
Before that, I also flashed versions from DavidAlfa, it is possible that this is the reason for the generator failure. But after that I flashed with the original platform, but it didn't help.
-
Are you sure it was working well before?
Or noticed later and you thought it was a firmware thing?
Because my generator output has been always 15-20% higher than the target.
Ex. 2v setting=2.4V output.
If you ever flashed a version that changed your FW, It could be the culprit.
I have full backup. It's been always the same.
About the overclocking, it doesn't modify anything in the EEPROM or anything. It just sets a register value in the CPU PLL at every boot. But I will make more tests.
You can easily see the difference, skip the oc by pressing the F0 key few times, just after the DSO interface starts working (usually few seconds after the relay clicking).
That way the DSO boots completely normal.
And it's not my firmware, I just got all the available data and made a proper compilation, it was annoying to search inside 20 pages to find half of the links had expired.
They all came from Hantek.
-
Самое интересное заключается в том, что показания калибровочного тестового сигнала 5V измеряет точно и показывает 5V! А когда выставляешь такое же напряжение и частоту в генераторе, то показывает 5,9V! Значит сам осциллограф меряет без ошибок. А вот сам генератор выдаёт завышенное значение напряжения на выходе чем то, что устанавливаешь вручную.
This is an English forum so please use a translator or the moderators will ban you.
-
That's because you changed FW.
FW version is related to the hardware, It breaks some things in FW3000 models.
But after flashing FW 3000 again everything should be working again.
-
International problems have no language!
-
The trouble is that when I rolled back to 3000, the problem remained ... ((. I wonder if there is a way to format the memory without soldering it out of the board via usb in order to flash it onto an open field again?
-
International problems have no language!
Doesn't work like that here.
EEVblog is an English only forum where the greatest readership are at least English readers and everything we post is there as a record for later readers that come along maybe years later.
Since 2013 when I joined I've seen the odd new member get banned for continued failure to use English.
-
we try to convey the idea of the problem, that's all.
The site must be done for all users, not for the chosen ones !!!
-
Самое интересное заключается в том, что показания калибровочного тестового сигнала 5V измеряет точно и показывает 5V! А когда выставляешь такое же напряжение и частоту в генераторе, то показывает 5,9V! Значит сам осциллограф меряет без ошибок. А вот сам генератор выдаёт завышенное значение напряжения на выходе чем то, что устанавливаешь вручную.
This is an English forum so please use a translator or the moderators will ban you.
Gerasim: English only please. I've removed your posts.
-
Aha !!!, you can't resent us with sanctions !!!
:-DD
-
Aha !!!, you can't resent us with sanctions !!!
:-DD
Please don't antagonize the mods especially as Halycon is one of the more lenient ones.
Butt heads with Simon and you'll be gone !
-
Looking at sunxi-fel souce code, most is done at computer side.
The sunxi cpu only does what sunxi-fel tells him to do.
Ex. "send '0x00 0x9f 0x00' through spi and tell me the response."
The code is not prepared for spi nand devices, so I'm trying to modify it.
If it works, we'll be able to fully backup and restore the flash within minutes :P
-
I'll poke it again, an allwinner chipset (R16) was also recently used as part of those mini consoles from Nintendo.. it's FEL mode is similar to the F1C200s in these Hantek Scopes. Possible relavant FEL mode reading and writing examples may be available within the Hackchi2 mod found on GitHub.
-
I'll poke it again, an allwinner chipset (R16) was also recently used as part of those mini consoles from Nintendo.. it's FEL mode is similar to the F1C200s in these Hantek Scopes. Possible relavant FEL mode reading and writing examples may be available within the Hackchi2 mod found on GitHub.
The R16 (A33) uses a relatively modern Cortex-A7 core, the F1C200s uses an outdated ARM926 core, so I very much doubt the same code can be used for both devices.
Note this page has both the datasheet and user manual for the F1C200s: https://linux-sunxi.org/F1C100s (https://linux-sunxi.org/F1C100s)
Also this page describes a small Linux distribution compiled from scratch for the F1C200s: https://www.thirtythreeforty.net/posts/2020/02/trying-the-allwinner-f1c200s/ (https://www.thirtythreeforty.net/posts/2020/02/trying-the-allwinner-f1c200s/)
Apparently sunxi-fel already recognizes the F1C200s/F1C100s, so it's definitely the tool to use if you want to hack your Hantek DSO.
sunxi-fel is part of the sunxi-tools suite, documentation here: http://linux-sunxi.org/Sunxi-tools (http://linux-sunxi.org/Sunxi-tools)
Some Linux distributions already include sunxi-tools (e.g. Ubuntu 20.10, which I am using).
To boot the DSO into FEL mode, just press the FEL button on the bottom of the main PCB (you don't need to open the DSO, the button is visible from the bottom of the DSO) while powering on the DSO.
To use sunxi-fel, you need to connect your DSO to your PC using the provided USB cable.
Connect your PC running Linux to the DSO, launch sunxi-fel in a terminal window, power on the DSO with the FEL button pressed, then type sunxi-fel version <Enter> and you should see:
$ sunxi-fel version
AWUSBFEX soc=00001663(F1C100s) 00000001 ver=0001 44 08 scratchpad=00007e00 00000000 00000000
Note the F1C200s is recognized as a F1C100s, because both chips are identical except for the amount of DRAM on the SOC.
At this stage you have all the sunxi-fel commands available:
Usage: ./sunxi-fel [options] command arguments... [command...]
-v, --verbose Verbose logging
-p, --progress "write" transfers show a progress bar
-l, --list Enumerate all (USB) FEL devices and exit
-d, --dev bus:devnum Use specific USB bus and device number
--sid SID Select device by SID key (exact match)
spl file Load and execute U-Boot SPL
If file additionally contains a main U-Boot binary
(u-boot-sunxi-with-spl.bin), this command also transfers that
to memory (default address from image), but won't execute it.
uboot file-with-spl like "spl", but actually starts U-Boot
U-Boot execution will take place when the fel utility exits.
This allows combining "uboot" with further "write" commands
(to transfer other files needed for the boot).
hex[dump] address length Dumps memory region in hex
dump address length Binary memory dump
exe[cute] address Call function address
reset64 address RMR request for AArch64 warm boot
readl address Read 32-bit value from device memory
writel address value Write 32-bit value to device memory
read address length file Write memory contents into file
write address file Store file contents into memory
write-with-progress addr file "write" with progress bar
write-with-gauge addr file Output progress for "dialog --gauge"
write-with-xgauge addr file Extended gauge output (updates prompt)
multi[write] # addr file ... "write-with-progress" multiple files,
sharing a common progress status
multi[write]-with-gauge ... like their "write-with-*" counterpart,
multi[write]-with-xgauge ... but following the 'multi' syntax:
<#> addr file [addr file [...]]
echo-gauge "some text" Update prompt/caption for gauge output
ver[sion] Show BROM version
sid Retrieve and output 128-bit SID key
clear address length Clear memory
fill address length value Fill memory
-
One more note for anybody that wants to pursue hacking their Hantek DSO: :-BROKE
You don't even have to open your DSO! :o And you certainly don't need to solder / unsolder the flash NAND memory chip inside your DSO, which voids your warranty btw. |O
In principle you can just boot George Hilliard's small Linux distribution (available here: https://github.com/thirtythreeforty/businesscard-linux ) directly on your DSO (by pressing the FEL button underneath and booting over the USB port on the front) and it provides a virtual serial console over the USB port at the back of the DSO. The DSO serial console should show up as /dev/ttyACM0 or /dev/ttyUSB0 on your Linux PC. The DSO file system should also show up as a USB storage device.
So you can just login as root, and then exchange files between your PC and the DSO file system, and run whatever programs you want to debug / hack. :phew:
Conclusion: you can safely have fun hacking your DSO, without opening it or even touching the original installed firmware. Just use the right tools (sunxi-tools and George Hilliard's Linux F1C100s distribution) for the right job.
Attached is a picture showing where the FEL button is located on the bottom of the DSO. Use a thin screwdriver to press it while powering on the DSO to enter FEL mode or boot over USB.
-
According to all the dates on the DSO3KB files for the DSO2xxx DaveAlpha has most kindly posted on his GDrive.
Hantek have released a new version about ever twenty days.
So given the last was 20210416 (excluding the not listed 20210510) Hantek are three or fours late for the next release.
Does the team think they have abandoned the DSO2xxx and just dumping there stock as door stops/land fill or are they planning a major FIX IT?
As we need to start planning ahead what to do with them as unfit for purposes as a scope, I was thinking of converting my one into a toilet brush!
imk
-
...
I am soooooooooooo pleased with this little scope,i am thinking of buying another as a spare. :-)
...
As we need to start planning ahead what to do with them as unfit for purposes as a scope, I was thinking of converting my one into a toilet brush!
imk
It seems you changed your mind over a few days... ::)
If you really think your Hantek DSO is "unfit for purposes as a scope" you should just return it and ask for a refund (unless you have voided the warranty). In my case it has been working flawlessly since I received it a few months ago. I am still on the march 2020 firmware update.
And as I have explained above, it's possible to hack it without even opening the case.
Hantek will certainly release further firmware updates, but I am not sure they will satisfy your expectations/needs. Perhaps you could try another DSO from another brand and tell us how that goes?
-
@imk
If you really think your Hantek DSO is "unfit for purposes as a scope" you should just return it and ask for a refund. In my case it has been working flawlessly since I received it a few months ago. I am still on the march 2020 firmware update.
And as I have explained above, it's possible to hack it without even opening the case.
Hantek will certainly release further firmware updates, but I am not sure they will satisfy your expectations/needs. Perhaps you could try another DSO from another brand and tell us how that goes?
Andrew well i guess you are the lucky one if your runs flawlessly, why are you on this thread?
My one was failing out of the box on day one, i waited few days for reply from hantek support and they provided the 20210510 fix.
Since then i have gone deeper into the scopes features and functions and it is full of lockup bugs, i am again waiting for reply from hantek.
While waiting for hantek and chatting on this forum my opportunity for returning timewise is just about past given you have 30 days for the seller to receive it in CHINA.
They say don't send it express as gets stuck in China customs, so send it snail mail and you miss the 30 day window.
Either which way I am out of pocket as i will never get the busted scope returned to me and they never issue a refund.
This is a catch 22 situation for me, i have not overclocked or messed with the scope in anyway other other than do the less than perfect upgrade.
So now i have choices ebay it and risk getting it sent back to me as faulty! Or live with then bugs that other on this thread have experienced.
Maybe a third options would be to send it back to Hantek hoping they will even bother to collect it from customs.
Await for them fix it then charge me $50 to send it back and get a VAT import hit here.
Or cut my losses and use it as a toilet brush.
And yes i have already specked out something else i wish to buy and am this time even more carefully checking out it quality.
Maybe best option of all is just carry on with my old Tektronix 2236 + Opt 14, sell duff hantek on ebay spares or repair and lose £150
Either which way i'll continue to publish the issues of this scope on youtube as Hantek need to know in times that producing Land Fill is simply unactable!
I hope your DSO2xxx works flawlessly for you for the rest of your very long life.
imk
-
...
Andrew well i guess you are the lucky one if your runs flawlessly, why are you on this thread?
...
Sorry, I didn't know this thread was only for people who intended to use their new Hantek DSO as a toilet brush, after saying that they liked it so much they were thinking about buying a second one.
:blah: :rant:
In case you didn't notice I am actually contributing some real information about hacking this little 180€ DSO without voiding the warranty, in this thread... :P
-
In principle....
Easy to say. When you get that working, tell us! Because there're a lot of differences. Different flash, different filesystems... Not easy.
At this stage you have all the sunxi-fel commands available:
Usage: ./sunxi-fel [options] command arguments... [command...]
-v, --verbose Verbose logging
-p, --progress "write" transfers show a progress bar
-l, --list Enumerate all (USB) FEL devices and exit
-d, --dev bus:devnum Use specific USB bus and device number
--sid SID Select device by SID key (exact match)
spl file Load and execute U-Boot SPL
If file additionally contains a main U-Boot binary
(u-boot-sunxi-with-spl.bin), this command also transfers that
to memory (default address from image), but won't execute it.
uboot file-with-spl like "spl", but actually starts U-Boot
U-Boot execution will take place when the fel utility exits.
This allows combining "uboot" with further "write" commands
(to transfer other files needed for the boot).
hex[dump] address length Dumps memory region in hex
dump address length Binary memory dump
exe[cute] address Call function address
reset64 address RMR request for AArch64 warm boot
readl address Read 32-bit value from device memory
writel address value Write 32-bit value to device memory
read address length file Write memory contents into file
write address file Store file contents into memory
write-with-progress addr file "write" with progress bar
write-with-gauge addr file Output progress for "dialog --gauge"
write-with-xgauge addr file Extended gauge output (updates prompt)
multi[write] # addr file ... "write-with-progress" multiple files,
sharing a common progress status
multi[write]-with-gauge ... like their "write-with-*" counterpart,
multi[write]-with-xgauge ... but following the 'multi' syntax:
<#> addr file [addr file [...]]
echo-gauge "some text" Update prompt/caption for gauge output
ver[sion] Show BROM version
sid Retrieve and output 128-bit SID key
clear address length Clear memory
fill address length value Fill memory
That's useless. You can write to the ram, but not to the flash. Otherwise I wouldn't have spent the night on it!
After a lot of debugging, I made sunxi-fel work with the nand flash. Still needs work but that's something.
Althought the interface is terribly slow... You don't have DRAM working, only internal SRAM, so you're limited to very small buffers (4KB).
(https://www.eevblog.com/forum/testgear/new-hantek-dso2x1x-models/?action=dlattach;attach=1227383)
-
...
Andrew well i guess you are the lucky one if your runs flawlessly, why are you on this thread?
...
Sorry, I didn't know this thread was only for people who intended to use their new Hantek DSO as a toilet brush, after saying that they liked it so much they were thinking about buying a second one.
:blah: :rant:
In case you didn't notice I am actually contributing some real information about hacking this little 180€ DSO without voiding the warranty, in this thread... :P
Andrew may i ask which version of the firmware you have as maybe better than my dso3kb_20210510
And yes was so pleased i almost bought another, but now my disappointment grows as i find more and more bugs and lockup problems
-
Andrew may i ask which version of the firmware you have as maybe better than my dso3kb_20210510
...
As stated above, I am still using the march 2020 firmware update, dso3kb_20210311.
-
I was thinking of converting my one into a toilet brush!
I guess its not handy enough..;)
Bofore you do so, I'll take it for about 100€ :).
Indeed, I was thinking on buying one but was waiting do to the reported pbroblems with the usage of a large buffer.
Last night i must learn, the the Allwinner SOC was designed for some Kiddies toys, no GPU, no FPU
So I'll wait for some more monthsm, now its summer and the sun is shining 8)
@AndrewBCN
TNX for the hint!
Sunxi tools are installed on my Ubuntu 20.10, of course!
-
...
That's useless. You can write to the ram, but not to the flash. Otherwise I wouldn't have spent the night on it!
DavidAlfa,
The boot rom (BROM) environment that FEL mode gives you access to is not the right place to mess with the SPI nand flash, as you have noticed.
What the BROM is useful for, is to load a recent version of u-boot, and from u-boot you can load the linux kernel and a root filesystem from a connected PC with a proper virtual console over USB OTG, and then you have tons of tools to examine/read/write/backup your SPI nand flash, all that without opening the DSO.
When/if I have the time (no guarantees of any kind) I'll prepare an image with u-boot, the Linux kernel, a DTB file and a root filesystem that can be loaded and started using sunxi-fel, based on the work of George Hilliard.
-
@imk
If you really think your Hantek DSO is "unfit for purposes as a scope" you should just return it and ask for a refund. In my case, it has been working flawlessly since I received it a few months ago. I am still on the march 2020 firmware update.
Since then I have gone deeper into the scope's features and functions and it is full of lockup bugs.
Either way, I am out of pocket as I will never get the busted scope returned to me and they never issue a refund.
This is a catch 22 situation for me, I have not overclocked or messed with the scope in any way other than do the less-than-perfect upgrade.
You have raised some interesting points.
If Hantek releases a new version of the firmware every 20 days, is it also possible that they are also frequently altering/tampering with the hardware? Perhaps putting the original code back would help alleviate some of the problems until they figure out how to stabilize it? The reference above is to March 2021 firmware?
I also didn't attempt to overclock or hack the unit to the next level, so I'm basically expecting it to work. My flawed logic was to take the 5000 series scopes and infer that the 2000 series would be as good but based upon newer hardware.
What was the "straw that broke the camel's back" for you?
Simon
-
Andrew may i ask which version of the firmware you have as maybe better than my dso3kb_20210510
...
As stated above, I am still using the march 2020 firmware update, dso3kb_20210311.
Andrew
I just installed 20210311 and see 3202 firmware.
In two previous versions dso3kb_20210416 and dso3kb_20210510 scope crashed when i selected Acquire->Mem Depth 8m in all the trigger modes i tried.
Scope would lockup, probe needed to be removed and scope power cycled
I just did same test with dso3kb_20210311 and 8Mpt running just fine! with serial trigger 9600 bps 1 sec msg rep rate :-)
Scope still has issues displaying UART serial decode in Sync mode but ok in monitor mode.
More testing to do, thanks for heads up :-)
imk
-
Simon,
What was the "straw that broke the camel's back" for you?
Is Having to Power Cycle hardware to get it working again!
I can just about live with hitting a reset button, but the power switch is a No No.
As too many times in 60 years of electronics I have powered stuff off and when it came to powering it on again, I had to get the tools out :-(
Problem is if I smoke this scope it is likely to be total loss given the return issues.
I think in one of my early posts i asked about fitting a reset button to the scope.
Chk my previous post re falling back to dso3kb_20210311 firmware. seems better :-)
As for your next scope i was chatting on another thread to distributer of Siglent equipment.
All seem to be very well tested, no warranty claims and good tech support.
So for you maybe either of the below, neither have a signal generator so maybe next project is to make one :-)
Based on https://www.analog.com/en/products/ad9833.html (https://www.analog.com/en/products/ad9833.html) and Nextion Display :-) is way i would go powered from re chargeable batteries
https://siglent.co.uk/product/siglent-sds1202x-e-super-phosphor-oscilloscope/ (https://siglent.co.uk/product/siglent-sds1202x-e-super-phosphor-oscilloscope/)
or
https://siglent.co.uk/product/siglent-sds1104x-u-4ch-100mhz-1gsa-s-14mpts-super-phosphor-oscilloscope/ (https://siglent.co.uk/product/siglent-sds1104x-u-4ch-100mhz-1gsa-s-14mpts-super-phosphor-oscilloscope/)
Or sit it out and wait for Hantek to exonerate themselves with a completely bug free firmware release next week.
imk
BTW where in UK are you, i am in midlands now.
-
...ad9833
I have one of those little chips. Its OK for the price but very limited and not very clean output once you get ~ >1Mhz sine.
If you want to spend a little, the "Feel Tech" FY2300 and its clones looks decent for the price, provided you accept its limits.
https://www.youtube.com/watch?v=5cGfk6LZmHM (https://www.youtube.com/watch?v=5cGfk6LZmHM)
-
...
If Hantek releases a new version of the firmware every 20 days, is it also possible that they are also frequently altering/tampering with the hardware? Perhaps putting the original code back would help alleviate some of the problems until they figure out how to stabilize it? The reference above is to March 2021 firmware?
...
Simon
Hi Simon,
I don't think Hantek is changing the hardware that fast. Or even the firmware. I think we should just cool down a little bit and wait patiently for the next two or three firmware releases and see if Hantek is making some progress in ironing out the most obvious bugs.
In the meantime I have been using the DSO and it works well enough for my needs. Yes, I am using the march 11, 2021 firmware.
-
...wait patiently for the next two or three firmware releases and see if Hantek is making some progress...
Hantek took 5 years or so to fix some of the bugs in the DSO5102P, so don't hold your breath waiting for fixes.
I've just uploaded dso3kb_20210601.upk to DavidAlfa's GDrive, which Hantek sent me. I didn't try it as by the time they replied I'd decided to return the scope. It could change your serial number as that's what I was emailing about at the time.
Hantek have just replied to my question about the failed calibration asking for video to show the problem... so maybe they are unaware of this error and/or can't reproduce it or have made some hardware change to the newer versions that's causing this error on the ones we have/had.
Who knows.. and quite honestly who cares. I know I don't. :popcorn:
-
Andrew,
Waiting it out (firmware update) i think is my only option I have as my 30 day returning it windows has just about closed.
I to have moved back to dso3kb_20210311 and it seems better than the later two updates, although it crashed for me the third time i set Mem Depth 8m.
So as you know the hardware better than I, is there a way (chip leg) I can ground to cause a scope reset rather than have to power cycle it please?
If so i'll fix up a wire/button via one of the air vent holes and live with it until Hantek catch up
Thanks in advance imk
-
DavidAlfa has provided a neat solution for the "DSO freeze bug": a watchdog daemon that monitors the phoenix process and relaunches it automatically. :-+
-
DavidAlfa has provided a neat solution for the "DSO freeze bug": a watchdog daemon that monitors the phoenix process and relaunches it automatically. :-+
How do i implement this daemon fix please?
-
...wait patiently for the next two or three firmware releases and see if Hantek is making some progress...
I've just uploaded dso3kb_20210601.upk to DavidAlfa's GDrive, which Hantek sent me. I didn't try it as by the time they replied I'd decided to return the scope. It could change your serial number as that's what I was emailing about at the time.
Serial number unaffected by this update, but it did push the firmware version to to 3102 (previously I was on 3200) and I was left with a big offset on the second channel. With no probe connection, adjusting the Y position resulted in random offsets on the trace.
Anyone got platform tools for 3200?
-
Try any platform-tools version. Then install dso3kb_20210510, which changes FW to 3200.
-
...wait patiently for the next two or three firmware releases and see if Hantek is making some progress...
Hantek took 5 years or so to fix some of the bugs in the DSO5102P, so don't hold your breath waiting for fixes.
I've just uploaded dso3kb_20210601.upk to DavidAlfa's GDrive, which Hantek sent me. I didn't try it as by the time they replied I'd decided to return the scope. It could change your serial number as that's what I was emailing about at the time.
Hantek have just replied to my question about the failed calibration asking for video to show the problem... so maybe they are unaware of this error and/or can't reproduce it or have made some hardware change to the newer versions that's causing this error on the ones we have/had.
Who knows.. and quite honestly who cares. I know I don't. :popcorn:
Interesting. Was your's a DSO2C10? And that SN? Or is this some obscure hack?:
[machine]
Model=250M$DSO2C10
Vendor=hantek
Product=DSO
Manufacturer=hantek
Serial=CN2104029002907
[version]
Pcb=501.001.001.000.000.000.000.000
Keyboard=1
[language]
Lans=65535
Language=3
[add]
Start=0
Update=0
-
What was the "straw that broke the camel's back" for you?
I can accept slower operation for the price but not the "hangs" and power off/on to recover.
I will be (almost certainly) ordering a Siglent sds1104x-e from a UK distributor tomorrow (there is no rush, but I'm also not getting any younger). I will be making up the difference. Almost certainly the sds1104x-u or the sds1202x-e would both be more than adequate. I'm taking the opportunity to get 4-channels e.g. better for spi: clock, cs, miso and mosi.
Simon
-
I will be (almost certainly) ordering a Siglent sds1104x-e from a UK distributor tomorrow (there is no rush, but I'm also not getting any younger). I will be making up the difference. Almost certainly the sds1104x-u or the sds1202x-e would both be more than adequate. I'm taking the opportunity to get 4-channels e.g. better for spi: clock, cs, miso and mosi.
You can just use 2 channels with a Clock Timeout setting on one and either Miso or Mosi on the other.
Not perfect for sure but Siglent's 2ch DSO's will at least give a good peek at SPI.
-
You can just use 2 channels with a Clock Timeout setting on one and either Miso or Mosi on the other.
Not perfect for sure but Siglent's 2ch DSO's will at least give a good peek at SPI.
Yes - the manual covers it (on page 99 of UM0101E-E05A July，2020). CS Type can be set to CLK Timeout for 2-channel scopes.
I'm buying for more than my current requirements. 2-channel would be fine, the 4-channel U version does not appear to have any lack of processing although the FFT (hardware-assisted) comes down from 1M to 128K (current scope is 1K) points, but that doesn't say if that's a marketing rather than a technical limitation. They both (all) use Zynq-7020 SoC - perhaps some models switched to using the single-core 7000s version to save $$$ ?
Marketing IMHO.
Breaking the holy grail of $400 for a true 100 MHz 4ch DSO would have been the target and loss of the 2nd ADC and its additional memory, MSO capability, rear USB A socket and a front end redesign and reuse of the X-E enclosure all helped Siglent to pull back the X-U price.
Obviously retention of 1 Mpts FFT, Bode plot and the webserver wouldn't provide sufficient differentiation between X-U and X-E for X-U to get a foothold in the marketplace or maintain sufficient sales volumes.
Initially I had mixed feelings about X-U however the market here in NZ has proven it has its place.
-
I'm never sure I understood the reasoning for 4 channels just for SPI work. A logic analyser like the DSLogic Plus does a much better job than any scope in terms of advanced triggering and stacked protocol decoders (and can do QSPI, flavours of Manchester coding etc) all for a price that is less than the differential in cost between 2 and 4 channel scopes. And you can trigger your scope from the logic analyser if you really want to see the analogue aspect of a bus line.
I2C on the other hand, that has significant analogue elements associated with rise times (should be constant current source pull up, but of course everyone uses a resistor for cost reasons, making it more of an RC circuit). But then you only really need two channels for that on a scope.
Just some thoughts. 4 channels do add significant expense so it is worth assessing what you'll actually use them for.
-
Definitely, get the right tool for the job.
The AliExpress $4, 8ch, 24MHz analyzer will do way better.
No memory depth issues. No triggering issues. No messy controls.
A $1000 dso won't better, for that is just stupid
-
Try any platform-tools version. Then install dso3kb_20210510, which changes FW to 3200.
Thank you for that. Actually I only had to upgrade with dso3kb_20210510 (applied FW 3202) and then upgrade with dso3kb_20210416 (which does not apply any FW changes) and it's back to "working" in so far as the CH2 strange Y offset has disappeared. Why Hantek ship upgrades without the "paired" associated firmware is bit of a mystery - surely they would want to guarantee the API between firmware and software remains in lock-step?
And as for why dso3kb_20210601 contains 3102 and not 3202 - did someone slip on the keyboard when they were making the upgrade? :-//
-
...
Why Hantek ship upgrades without the "paired" associated firmware...
Apparently this is because not all upgrade+firmware combinations work well with all hardware versions.
My suggestion is that people keep the original software + firmware versions that they got with their DSO in the first place and with caution apply only the upgrades that Hantek publishes on their website - not the ones that Hantek support sent by mail to solve a specific query by a specific user.
Unfortunately the situation now is that there are numerous software + firmware versions floating around and people are just trying them in an unsystematic way, iow Hantek support has lost control of the situation. They should come up with a "works for everybody" software + firmware upgrade and publish that on their website ASAP to stabilize things.
-
Apparently this is because not all upgrade+firmware combinations work well with all hardware versions.
My suggestion is that people keep the original software + firmware versions that they got with their DSO in the first place and with caution apply only the upgrades that Hantek publishes on their website - not the ones that Hantek support sent by mail to solve a specific query by a specific user.
Unfortunately the situation now is that there are numerous software + firmware versions floating around and people are just trying them in an unsystematic way, iow Hantek support has lost control of the situation. They should come up with a "works for everybody" software + firmware upgrade and publish that on their website ASAP to stabilize things.
:palm: Not good. Not good... :palm:
-
As far as I understand, the only firmware-thing here is the FPGA. Which is loaded at every boot. There's a bin file in the dso folder.
What I didn't figure out yet was what actually stores the FWxxxx version.
-
As far as I understand, the only firmware-thing here is the FPGA. Which is loaded at every boot. There's a bin file in the dso folder.
What I didn't figure out yet was what actually stores the FWxxxx version.
I'm not convinced that's it.
If you look at the diffs between 20210416 and 20210510 (that bumped firmware to 3202 when applied to my scope) the only files different are:
- package/do_update.sh (comments out a copy line, so not that)
- package/system.info (just some string tweeks)
- package/fpga/psram_board_test.fs.bin
There's a few more between 20210510 and 20210601, most of which look like string changes, but with the addition of an update to phoenix binary. And again, that package/fpga/psram_board_test.fs.bin file.
Cynically I doubt very much that Hantek are using these upgrades to improve their psram test every time, I very much suspect that this is a file they used for initial bringup and never bothered renaming, that possibly includes the FW. Just speculation.
This speculation is possibly further supported by "load_fpga_kb.sh" which has line: /dso/app/cfg_fpga /dev/tn652_fpga_cfg psram_board_test.fs.bin
...right before loading some kernel modules. Googling tn652 fpga turns up some links to the GoWin FPGAs that it has been speculated that these scopes populate.
https://www.gowinsemi.com/en/product/detail/2/ (https://www.gowinsemi.com/en/product/detail/2/)
This page mentions "Embedded pSRAM (GW1NR/1NSR only)" - a coincidence with the psram_board_test.fs.bin filename? I think not.
I tried putting the 20210510 psram_board_test.fs.bin into the 20210601 filesystem, overwriting the one there, re-packing and re-encrypting the tar.gz into a .upk. When I run the upgrade on the scope the progress bar moves, it says success and to reboot, but when I reboot, nothing has changed. Not the software version or firmware.
But it could be a problem with the signing or something else in the file structure.
-
WHat I meant wass there's nothing else programmable that storing the data, the fpga is loaded at every boot, not flashed (I might be wrong, but I'm 99.9% sure).
Yep, I tried too. There's something else. Clearly, it's in the flash. I'm not sure what the 24C02 i2c memory does.
Maybe the phoenix binary checks checks something inside tn652_fpga_cfg psram_board_test.fs.bin, and doesn't allow downgrading?
First, check if they're different . Run md5sum or similar.
Also, runnign strings in the update files might reveal the if the FW3202 string is somewhere
-
I would agree, I think they are loaded over SPI on every boot, as shown in this datasheet for the part, which is probably one of GW1NR/GW1NSR:
https://www.gowinsemi.com/upload/database_doc/42/document/5b96382ad5a52.pdf (https://www.gowinsemi.com/upload/database_doc/42/document/5b96382ad5a52.pdf)
-
Maybe the phoenix binary checks checks something inside tn652_fpga_cfg psram_board_test.fs.bin, and doesn't allow downgrading?
I think you're right. Now that my FW is on 3202, I can't reapply the original 20210601 that downgraded my firmware from 3200 -> 3102. So I may have to go via an older .upk or apply platformtools first.
The logic is probably like this: don't upgrade the software unless the firmware is <= x, where X is the latest version the software can drive.
-
You have very simple ways. Download "dso3kb_do_other_update.upk" which does absolutely nothing to the system, only runs the script "do_other_update" in the usb root if present.
Write whatever in do_other_update file (ex. cp /mnt/udisk/psram_board_test.fs.bin /lib/firmware/ ) and then run the update package.
Then check if it made any difference.
-
I've just done that, taking the psram_board_test.fs.bin from 20210416 and overwriting the one in my filesystem. Scope then showed "3200" on the info page on next boot (it was "3202") - a successful downgrade proving that this is, indeed, the file in question.
Oddly, I am unable to apply the 20210601 update again, despite downgrading the psram_board_test.fs.bin to 3200, to match the previous conditions.
-
Wow what a busy posting on this thread night it has been, lots and lots to mull over :-)
But i am said to say that i have given up with this DSO2D10, great functionality but just too flaky for me.
Hence I opened a return REFUND request to Banggood this morning and am awaiting a reply.
Even made for them a NEW video for all to enjoy :-)
https://youtu.be/7G36bSCO3Og
Don't care if it gets lost in post and I am £200 out of pocket!
I just know that this World Of Pain Hantek Rubbish (Toilet Brush) is Out Of My Home!
Wish me luck with the return imk :-)
-
I've just done that, taking the psram_board_test.fs.bin from 20210416 and overwriting the one in my filesystem. Scope then showed "3200" on the info page on next boot (it was "3202") - a successful downgrade proving that this is, indeed, the file in question.
Oddly, I am unable to apply the 20210601 update again, despite downgrading the psram_board_test.fs.bin to 3200, to match the previous conditions.
As DavidAlfa noted in the hacking thread, the Winbond SPI NAND chip includes a small OTP memory area (One Time Programmable), it's very possible that firmware updates get somehow recorded, we just don't know.
We'll only know more once we have a working u-boot + DTB + Linux kernel + root filesystem that we can boot on the DSO and use to analyze the SPI NAND contents in more detail (without blowing things up, preferably).
-
Winbond SPI NAND chip includes a small OTP memory area (One Time Programmable), it's very possible that firmware updates get somehow recorded, we just don't know.
I don't believe that they would go to all that trouble with such a device. Bigger brands don't do it...
-
It seems unlikely. But there may have been a flag file or other metadata created or modified in the filesystem as part of the original upgrade.
I was a little suspicious of /dso/etc/check_sys_inf executable but it turns out it's just a helper to extract values given a key from the .inf file. For example from my filesystem dump running it on an Raspberry Pi:
pi@raspberrypi:~/tmp/backup $ ./filesystem/dso/etc/check_sys_inf ./config/system.inf Model
DSO2D15
There is also an intriguingly named executable /dso/app/spi containing strings like "fpga dev open failed" which I assume is used for some FPGA actions.
-
Hi guys I'd like to share my experience with my new DSO2C10, which I bought on 20.04.2021 from Aliexpress for 202$.
When I received it it was showing : Software-1.0.1.1.0(20210416.00),hardware-000........000,Firmware-3200. After the
latest update I downloaded from the Hantek site , which was 20210416, firmware changed to 3000 and calibration broke
giving every time error 511d1 when I try to caliblrate, then I did the following thing to restore it and even make it DSO2D15.
First I opened it to confirm the mainboard is model DSO2D15_V1.7 2021.1.14 and all parts regarding GEN are present.
Second I downloaded from https://drive.google.com/drive/folders/1Tqk8YbL_M3S0vtk7h_cZ-01U2idIaqqx, provided by "DavidAlfa"
"filesystem_20210416 backup" , "do_other_update(Restore filesystem)" from scripts forlder and "dso3kb_20210510" from
firmware folder, all these files unzipped on root dir of usbdrive.
Rename "do_other_update(Restore filesystem)" to "do_other_update"
Create folder "backup"insert in this folder unzipped "filesystem_20210416" and raname it to "filesystem"
in "filesystem" folder find two files (sys_inf.new and system.inf) and edit them with Notepad++ as described earlier
to give it model 2D15, serno (yours) ,maker(hantek) and pcb 000...001 , then save both files, insert usbdisk and make
firmware upgrd, after finish restart and you got 2D15, but still calibration don't work and gives error 511d1.
Unzip firmware "dso3kb_20210510" and make the upgrade, after finish you can go thrue calibration with no problem, remember
to remove any leads from the device before calibration.
Now the only problem remain for me is the noise the device have, which is unacceplable. My suspect for that noise is
the internal switched power supply, but will take some time to create and install analog power supply and check.
At the same time I bought Fnirsi1014D scope, which uses power adapter 5V/2A far enough from the device, this one don't have
such noise and the line is "clear" like it should be.
The generator works fine at output levels above 500mV, below this the sinusoide is "stepped".
-
Sorry but, might I ask why the f*** you did all that?
latest update I downloaded from the Hantek site , which was 20210416, firmware changed to 3000 and calibration broke
20210416 doesn't change the FW, so you clearly messed up by flashing something you shouldn't.
That's what happens when you go at your own without reading anything.
Either you ran update on dso3kb_20201221 or flashed it with platform-tools FW3000 version.
-
One thing about a probe, when the clip is removed, should there be a probe point? I am probably doing something wrong because the probe tip is in the hook part and so the probe accessories like the spring and yellow covers etc. have no use, and the probe can't be used without the hook. Perhaps the PP-150B just means PP-150 (broken version). Perhaps my understanding falls a bit short and you can of course forget a lot in 40 years!
Simon
Seems you are not the only one with probes that break. These probes look the same as what I had supplied with my 'scope.
https://youtu.be/z96tFMKTDww?t=940
-
Today I accidentally discovered that when you press the "Default Settings" button for a long time, new options for setting up and checking the parameters of the oscilloscope appear. It looks like there is also a generator calibration.
-
Nice!
I pressed Default setup for more than 30 seconds...Not happening here.
Maybe it needs to be in a specific screen/option?
How are you doing It exactly? What SW?
-
I have version b000. The device is at work, I'm at lunch. Later in the evening I will take a picture and post it.
-
Everyone, please check this folder:
https://drive.google.com/drive/folders/12kRZ7GMdFLtON1bypmu-cVSbZOG2Qdtg
If you have a FW version not listed there, please run the update "BACKUP FW".
It will backup your fgpa config file into the usb. Then upload it to my writable folder in Gdrive (Add a prefix describing the FW version).
That file seems the most important file of the scope, so better to have backups of all types.
-
Does Waveform saving work for anyone? No matter the SW version, it's always disabled. Either for internal and external.
-
I'm using the SDO2D15 AWG as a signal generator to a separate scope. The sinewave is 1Mhz which is well within what's possible with the AWG. There is no modulation and so you would expect to see almost a pure sine wave.
I noticed that there is a burst of noise in the same position on many (but not all) cycles. If I switch to a square wave the result is the same and there is a burst of noise which is at the same point on many of the square waves e.g. about 3/4 of the way through.
I'm triggering a single shot with the trigger starting below the square wave and lifting the trigger point until it triggers. It's easier to trigger it with the square wave, but forcing trigger catches it, almost every time too.
I can use the SDO2D15 to also capture the square wave, but then I don't know if it's from the AWG or the scope or crosstalk, etc. Using the second scope shows it is from the AWG. I'm not sure if the AWG is updated with the firmware (April 21 release and 3000 version).
The attached shows what you get and the duration of the "noise" (1/10 of a cycle).
[attachimg=1][attachimg=2]
Simon
-
Simon,
Is the glitch the switching psu in the Hantek?
BTW i just downloaded a nice little app for Android Phone by
https://play.google.com/store/apps/details?id=com.keuwl.functiongenerator&hl=en_GB&gl=US
Works well 10khz plus on Sine wave, but sq wave has much ringing but is ok for free pocket wave gen with two channels.
imk
-
Does Waveform saving work for anyone? No matter the SW version, it's always disabled. Either for internal and external.
Yes with SW 20210517 / FW 3202. I can save waveform to internal memory and recall correctly. And save/recall from USB. First time I've seen the on-screen keyboard for file naming.
"Save to USB" button does not work any more, though.
-
Simon,
Have you tried getting a few feet of wire (single core probably best) and wrapping some turns around a former like middle of kitchen towel roll.
And use it as an aerial to see what is radiating at that Hz
imk
ps how do you like new scope?
-
Simon I see the same noise burst on mine. Most often in the position you identify but it also shifts elsewhere in the cycle.
If I clip my probe ground to the tip to form a loop, I see the same, little 100MHz bursts singing away. And this is with the AWG switched off. I can trigger on them quite easily.
I put this down to being in an electrically noisy environment (laptop, monitors, network switches etc) but if you are seeing the same then maybe it's the scope itself?
-
Yeah I also get that terrible noise even when coupling to GND! No matter if the probe is shorted or removed.
Hmmm, the 5G is destroying our lives ;D
To make it worse, I'm taking the Covid shot in 3 days, I hope the nanobots are EMI friendly!
Jokes appart, that's really annoying.
I'd blame the on-board buck regulators that provide 1.1V & 1.9V (SIK, TLV62565 1.5MHz).
Would it get better by replacing R83 and R174 with chokes?
Also, the display has 2 switching regulators for the bias (TPS65150, 1.2MHz) and the backlight (SZL, TPS61169, 1.2MHz).
So there are a lot of switchers there. I guess if they should have shielded them, I don't think it's nice when you chase mV accuracy.
Also I don't like the switched +-8V outputs directly feeding the analog. It's screaming for some filtering.
-
There are also happy owners of the "Default Settings" button with additional functions, or am I the only one?
-
There are also happy owners of the "Default Settings" button with additional functions, or am I the only one?
Piton,
I was a very happy owner of this little scope and can live with the features like noise, offset errors and display going nuts at 8meg mem depth etc.
As it is a cheap scope that has a lot of function, hence for what i need it for i can forgive a lot, what does it for me is it locking up and have to be power cycled.
(Power cycling is a killer e.g. my workshop PC i use for 3D printing is getting old, runs all day without a glitch, yesterday powered it off this morning powered on and dead :-( )
If Hantek would fix all these lockups so i didn't have to power cycle it i would not be too unhappy.
I have opened a return with banggood but it is near the end of 30 day return window so a return might not happen, what then i don't know.
imk
PS did you try the 30 sec press of Default test again?
-
So I'm pulling the trigger on a return and have ordered a Siglent SDS1202X-E instead.
My cat is currently trying to get inside the box my SDS1104X-U was supplied in :-+
First Impressions? OOOh nice display!.. Gah! Fan!
Is there a thread for the SDS1104X-U? I have a few questions (one being why I'm struggling with a simple serial decode, lots of "Over length" message).
:-+ :-+ :-+
-
It costs twice as the hantek, but the reviews look a lot better!
-
So I'm pulling the trigger on a return and have ordered a Siglent SDS1202X-E instead.
My cat is currently trying to get inside the box my SDS1104X-U was supplied in :-+
First Impressions? OOOh nice display!.. Gah! Fan!
Is there a thread for the SDS1104X-U? I have a few questions (one being why I'm struggling with a simple serial decode, lots of "Over length" message).
:-+ :-+ :-+
Why not start a new thread and post the link as i am interested in one.
As for over length msg, maybe it has inbuilt serial msg buffer and your serial msg is blowing it, maybe try a shorter msg.
(My cat cry for dinner, FEEDING TIME AT THE ZOO!)
-
Donate one to me, I'll start the hacking right now :-DD
-
So I'm pulling the trigger on a return and have ordered a Siglent SDS1202X-E instead.
My cat is currently trying to get inside the box my SDS1104X-U was supplied in :-+
First Impressions? OOOh nice display!.. Gah! Fan!
Is there a thread for the SDS1104X-U? I have a few questions (one being why I'm struggling with a simple serial decode, lots of "Over length" message).
:-+ :-+ :-+
google this: "site:eevblog.com SDS1104X-U". You will get several results..
-
Donate one to me, I'll start the hacking right now :-DD
Catch your own :-)
https://www.youtube.com/watch?v=M0sSoZHaW-E (https://www.youtube.com/watch?v=M0sSoZHaW-E)
-
imk, i agree with you that this model does not work properly yet, although my copy works well, except for one freeze (during auto measurements with 2 channels, one does not freeze) and is not very stable in some synchronization modes. Maybe Hantek will fix everything, or the guys from EEVblog who have already done a lot of things here. Therefore, I have already ordered RIGOL DS1102Z-E, and I will sell this one. Although a little sorry, I would be completely satisfied with it, especially for the money that I spent on it.
-
The Hantek has some corners cut to get the price down. Is it still useful? Definitely. But I have a long career in embedded electronics and my new day job is full time WFH embedded development without access to a company lab, so I really need something a bit more precise. It's a shame, I really liked the Hantek styling and specs on paper. But I suspect the Siglent with its advertised low noise inputs and 500uV/div sensitivity is probably where I should have started instead. Hantek tempted me in with a scope half the price but failed to deliver the level of quality I hoped it would have.
-
Is it still useful? Definitely.
I'm not sure it is tbh. I've had a Hantek DSO5102P for the last few years, which, lets be honest, is pretty terrible compared to anything more pricey, but it does the job if you just want a basic modern-ish scope to check go/no go function for fault finding. Its somewhere neartm the correct readings, doesn't crash too much and for the price its useable (with patience).
I was hoping, as many of on this thread where, that the 'new' DSO2X1X would be little bit of an upgrade, probably no faster but still usable, and "near enough" accurate for hobby use and so on.
On the face of it it looks good. Nicer display, nicer spec that the DSO5102P, more memory, wave gen.. etc. etc.
:palm:
Nope. Anyone reading this thread will know just some of the issues.
Will they get fixed? I'm not convinced. This thread says its a way underpowered CPU to do what its trying to do, its got a number of design issues that can't be fixed in firmware, and even if it could be fixed, Hantek don't seem to even be aware of the problems with it.
Total lemon. :-// :-- :-BROKE
-
So I'm pulling the trigger on a return and have ordered a Siglent SDS1202X-E instead.
My cat is currently trying to get inside the box my SDS1104X-U was supplied in :-+
First Impressions? OOOh nice display!.. Gah! Fan!
Is there a thread for the SDS1104X-U? I have a few questions (one being why I'm struggling with a simple serial decode, lots of "Over length" message).
:-+ :-+ :-+
QuitButton,
Think the fan was mentioned in a review, is it really that bad?
As SDS1104X is what I was thinking of getting, i guess i could change the fan but then warranty is gone i guess.
imk
https://www.eevblog.com/forum/testgear/siglent-1104x-e-noisy-fan-replacement/ (https://www.eevblog.com/forum/testgear/siglent-1104x-e-noisy-fan-replacement/)
-
The two channel SDS1202X-E is supposedly quieter as there is less to cool. Well, fingers crossed for that. I already swapped a passively cooled 15V 4A supply for a 30V 10A programmable one with fan, which is silent until it gets warm, then you know it's there. Can do without the scope competing with it.
One thing going for the Hantek, no fans!
-
The two channel SDS1202X-E is supposedly quieter as there is less to cool. Well, fingers crossed for that. I already swapped a passively cooled 15V 4A supply for a 30V 10A programmable one with fan, which is silent until it gets warm, then you know it's there. Can do without the scope competing with it.
One thing going for the Hantek, no fans!
Much much quieter than any of the 4ch models certainly.
-
Had a fan noise google for siglent and found this thread, might be interesting.
https://www.mikrocontroller.net/topic/484937 (https://www.mikrocontroller.net/topic/484937)
BTW does the Siglent have a warranty seal on it? If not i guess i could swap fans out with quiet ones :-)
-
Think the fan was mentioned in a review, is it really that bad?
Bad? No. Unexpected? Yes.
Is kind of.. "Old Laptop on medium speed" noise, or "PC PSU from 10 years ago on the desk", or "noticeable and could be annoying in a quiet room" volume.
-
I sincerely hope this thread can go back to a discussion of the Hantek DSO2X1X models, or perhaps I should start another thread?
If you know anything about electronics manufacturing, then you know that comparing a $200 entry-level Hantek DSO to one from any other brand costing twice as much is totally meaningless ("comparing apples to oranges").
Another thing some people seem to have fixated upon is the fact that the little 32-bit ARM SOC inside these Hantek DSOs does not have hardware floating point: it's an ARM926EJ-S without a hardware floating point coprocessor. But the fact is that for processing and displaying 8-bit integer data samples, there is simply no need for floating point code. And for the occasional FFT, the Linux kernel-provided floating point emulator is more than adequate performance-wise. The advantage of this lower performance ARM SOC is its low power dissipation, so there is no need for a fan in these Hantek DSOs.
Now, as far as I can tell, there is a lot of room for improving the firmware in these little scopes*, and I sincerely hope Hantek gets its act together on delivering significant firmware upgrades ASAP - which I hope we can continue to discuss here in this thread. Providing effective feedback on firmware issues to Hantek can only help them and accelerate the firmware revision process, but I don't see how all the whining and bitching can have any positive outcome.
*: I have determined that Hantek programmers used a 2017 version of Buildroot and gcc version 5.4.0 to build u-boot (also from 2017), the kernel (5.2.0) and the root filesystem. Without any particular difficulty, in a couple of hours I was able to use a 2019 version of Buildroot and gcc version 8.3.0 to build u-boot (from 2019), the kernel (5.2.4) and a more complete root filesystem - with room to spare. I intend to write to Hantek providing them with this information.
-
Threads often drift to and from topic, but you right to try and keep the DSO2x thread alive.
My Banggood return request is stuck at "Solution under comfirming" at 28.8 days used up of 30 days.
Hence i look the hantek site everyday for a new stable software release as potentially great little scope for the monies.
But as mentioned these dozen lockups a day are its nemesis for me :-(
Good luck with you software rebuild imk
-
While on the issues of heat in scopes.
I ran my little DSO2xxx all day, it got warm on the left side above the power supply but noting i would consider excessive.
From videos i have seen of them with back removed there seems to be a place to add a small fan.
So has anyone added a small fan to the DSO2xxx?
-
It's not that hot. Might be 50ºC inside, not more.
Some heat is actually good! Keeps the moisture out and helps with the accuracy by preventing huge temperature differences between runs.
Is this the noise we are all talking about, right? Do3esn't seem to come from the regulators, but from the ADC itself.
The actual noise frequency might be much higher, but appears modulated due aliasing artifacts.
-
So I'm pulling the trigger on a return and have ordered a Siglent SDS1202X-E instead.
My cat is currently trying to get inside the box my SDS1104X-U was supplied in :-+
First Impressions? OOOh nice display!.. Gah! Fan!
Is there a thread for the SDS1104X-U? I have a few questions (one being why I'm struggling with a simple serial decode, lots of "Over length" message).
:-+ :-+ :-+
Yep here:
https://www.eevblog.com/forum/testgear/siglent-1120-new-sds1104x-u-4-channel-100mhz-1gsas-economy-oscilloscope/ (https://www.eevblog.com/forum/testgear/siglent-1120-new-sds1104x-u-4-channel-100mhz-1gsas-economy-oscilloscope/)
Post some screenshots first saved to USB with the blue Print button but be sure to have decoding menus showing so to see some of your settings.
-
It's not that hot. Might be 50ºC inside, not more.
Some heat is actually good! Keeps the moisture out and helps with the accuracy by preventing huge temperature differences between runs.
True, but the bigger the thermal cycle the bigger the overall stress on components and the sooner it will fail.
-
Threads often drift to and from topic, but you right to try and keep the DSO2x thread alive.
My Banggood return request is stuck at "Solution under comfirming" at 28.8 days used up of 30 days.
Hence i look the hantek site everyday for a new stable software release as potentially great little scope for the monies.
But as mentioned these dozen lockups a day are its nemesis for me :-(
Good luck with you software rebuild imk
If you paid through Paypal, you can invoke the buyer protection by starting a dispute. For my Banggood purchase, taking that action does not expire until November. Record all communication with Banggood and the seller (if they ever respond) in order to document it with Paypal. If you e-mailed Hantek support before invoking the Banggood return, include that too with dates, even if Hantek did not respond. It builds an irrefutable case with Paypal that shows that you, as the consumer, have acted reasonably.
I sincerely hope this thread can go back to a discussion of the Hantek DSO2X1X models, or perhaps I should start another thread?
If you know anything about electronics manufacturing, then you know that comparing a $200 entry-level Hantek DSO to one from any other brand costing twice as much is totally meaningless ("comparing apples to oranges").
Another thing some people seem to have fixated upon is the fact that the little 32-bit ARM SOC inside these Hantek DSOs does not have hardware floating point: it's an ARM926EJ-S without a hardware floating point coprocessor. But the fact is that for processing and displaying 8-bit integer data samples, there is simply no need for floating point code. And for the occasional FFT, the Linux kernel-provided floating point emulator is more than adequate performance-wise. The advantage of this lower performance ARM SOC is its low power dissipation, so there is no need for a fan in these Hantek DSOs.
Now, as far as I can tell, there is a lot of room for improving the firmware in these little scopes*, and I sincerely hope Hantek gets its act together on delivering significant firmware upgrades ASAP - which I hope we can continue to discuss here in this thread. Providing effective feedback on firmware issues to Hantek can only help them and accelerate the firmware revision process, but I don't see how all the whining and bitching can have any positive outcome.
I agree. The Siglent scopes use components that add significantly more BOM cost than the Hantek and it is unfair to compare the two. But it is useful for anyone considering purchasing the Hantek to go in "eyes open" to what they are getting, which can only be achieved by examining its shortcomings.
For the money, what it offers is a remarkable amount of technology, it seems to come with an "OK" front end and well laid-out application user interface. Things like resolving crashes, DC offsets, scaling issues from calibration, some trigger filtering can potentially be fixed with updates. Whether the noise level is tolerable comes down to what each user's expectations are, and how they intend to use it. I still stand by my statement that it's a useful bit of kit - just not for what I need.
As for the cooling arrangement, it does get warm but the case slots top and bottom indicate that the design was intended for passive convection cooling. Perhaps with an added fan overclocking the SoC and memory without shortening lifespan/crashing becomes an option for the hardcore Hantek hacker. I also agree that the SoC is about what I'd expect given the price range.
My Siglent has arrived and first impressions are OK. I actually prefer the button layout on the Hantek and elements of the Hantek UI (from a background of using many different scopes, that's saying a lot). On the Siglent the knobs feel less substantial and "wobble" - the Hantek knobs are more solidly connected to the scope. The buttons on the Hantek have a decent "clunk" when you depress them - the Siglent is like pressing foam with little feedback (when the key beep is off) to know that you've pressed it hard enough.
Noise and signal quality I have yet to assess (one for this evening) but first impressions are favourable. I can still see some 100MHz pulses and trigger on them, the signal looks better. But that might be an implementation detail in how the Siglent decimates the capture buffer for display vs the Hantek. It could be the Hantek SoC does simpler decimation due to more limited processing, and that just looks worse. I will do a more thorough assessment later.
Fan noise is a quiet murmur that is only noticeable when listening for it. Not a patch on my programmable PSU that lets you know when it's cooling.
So it's not all rainbows and sunshine in Siglent vs Hantek land, but it's early days for comparison yet.
Edit: oh yes and my cat loves the Siglent box too. Must be something about the shape that's optimised for cat brains.
-
...
So it's not all rainbows and sunshine in Siglent vs Hantek land, but it's early days for comparison yet.
...
Apart from comparing aesthetics (see attached pictures - in my totally subjective opinion, the Hantek looks better) and perhaps the feel of the buttons, I don't think it makes much sense to compare the technical performance of the 200MHz Siglent SDS1202X-E (a $400 DSO) to the 100/150MHz Hantek (a $200 DSO). Again, that's a typical case of "comparing apples to oranges".
At these price levels, they just can't perform the same - and obviously they don't. Just as an example: the Hantek uses an ARM926 processor in a $1.40 SOC, the Siglent uses a $25 Zynq 7020 which has two ARM Cortex A9 processors. The main board on the Hantek is probably 4 or 6 layers, whereas the main board on the Siglent is 8 or 10 layers (i.e. much more expensive). There is simply no comparison.
-
But the fact is that for processing and displaying 8-bit integer data samples, there is simply no need for floating point code. And for the occasional FFT, the Linux kernel-provided floating point emulator is more than adequate performance-wise. The advantage of this lower performance ARM SOC is its low power dissipation, so there is no need for a fan in these Hantek DSOs.
Meh. Do you see stm32 burning because of having FPU?
AllWinner has the LicheePi zero, based on the V3s, much powerful, not only die faster clocks, but also has FPU.
And the "ocassional" FFT.... I think it does a lot more work in floats than you might think. For sure, there're some algorithms behing the drawing functions.
Find/do some performance tests with and without fpu. It's easily 20x slower... or more!
-
...
Meh. Do you see stm32 burning because of having FPU?
That's not the point.
AllWinner has the LicheePi zero, based on the V3s, much powerful, not only die faster clocks, but also has FPU.
And the "ocassional" FFT.... I think it does a lot more work in floats than you might think. For sure, there're some algorithms behing the drawing functions.
Find/do some performance tests with and without fpu. It's easily 20x slower... or more!
Usually 2D display algorithms need exactly zero floating point code. So the performance difference will be exactly none. Obviously I can't vouch for the quality of the programming in these little scopes, but as I wrote, there is a lot of room for further improvements, from what I have seen until now.
-
The 2D drawing algorithms can be escalated using fixed point, for sure.
But you'd be surprised how today's programmers take the floats for granted, and use them even for storing "1" :-DD.
I doubt it's only drawing simple xy plots. Probably there's a lot more behind.
I found another serious bug. It only happens below 500mV (When the relay clicks)
If you saturate the signal it goes completely nuts.
Easy way of testing: Set the AWG to square wave, 1KHz, 1.5Vpp and 250mV offset.
Set the channel (1x Mode) to 200mV/div. You see a zoomed square sigbnal, no problem.
Now start rising the offset. What the *** happens to the signal?
It's not the AWG. Anything saturating the input in modes under 500mV/div do that.
-
That's odd. The slope doesn't look linear, as though there is some form of AC decoupling. If you slow down the AWG is the slope more pronounced?
-
tttonyyy,
Re paying for the hantek, yes i did pay with paypal and thanks for the reminder about my rights.
However Banggood have a Get Out Of Jail Free clause.
Have you contacted Hantek about this problem, Yes
Did you follow their advice, Yes i uploaded the new firmware.
Sorry will don't accept returns of modified products. :-(
Have you contacted Hantek about this problem, Yes
Did you follow their advice, No.
Follow their advice and get back to us. :-(
This is the Kobayashi Maru scenario, anyone know James T Kirk's number :-)
I think the way the return request is going I shall be out of time on Midnight Friday.
Not too worried, either ebay it, or await next firmware from Hantek which is few weeks overdue.
Maybe they are feeling the flak from these threads and having a do or die last push.
Has anyone checked the job adds for programmers at Hantek :-)
BTW when reporting new DSO2xxx features would it be worth noting the firmware release number/date?
all the best imk
-
It's not the AWG, anything you throw there with too high level and 20mV/div setting(1x) or less, makes it!
Will flash it again and ensure it's not a software issue, but...
-
My Hintek DSO2D15 is OK
-
My Hintek DSO2D15 is OK
What firmware version are you on please?
-
I have a question?
Unintentionally installing the update dso3kb_20210510. On the FW (3000) software. The oscilloscope stopped working as it should !!! How can I become a licensed owner of this device? (DSO2D15)
-
DSO2000 Firmware
2021-04-20
-
DSO2000 Firmware
2021-04-20
From Hantek site download firmware http://www.hantek.com/products/detail/17182 (http://www.hantek.com/products/detail/17182) 20210420
Or David Alpha gdrive https://drive.google.com/drive/folders/1iw9BOnvxNOd0f_2uvGwGSHmnjP4TrG4f (https://drive.google.com/drive/folders/1iw9BOnvxNOd0f_2uvGwGSHmnjP4TrG4f)
Has most/all the previous versions, apparently 20210304 is fairly reliable although I have crashed it and had Mem Depth 8M issues.
I think all are awaiting the next exciting chapter in the saga known as Hantek DSO02xxx firmware releases :-) enjoy, it is marginally better that toothache!
imk
-
From Hantek site download firmware http://www.hantek.com/products/detail/17182 (http://www.hantek.com/products/detail/17182) 20210420
Inmcorrect, that update doesn't change Fw version!
I have a question?
Unintentionally installing the update dso3kb_20210510. On the FW (3000) software. The oscilloscope stopped working as it should !!! How can I become a licensed owner of this device? (DSO2D15)
I will delete that version as it only changes the fpga firmware, nothing else!
Check my GDrive folder, go to Mods/FW changer, download and run FW3000 update. Done!
These important details shuld be in the first post, actually the info is spreaded all over 20 pages (and rising), making it hard to find.
However, thread starter seem to have gone long time ago (Last login: December 30, 2020), making most important post completely useless.
People willl keep flashing wrong versions because of this.
Moderators: Can we take control of the first post to use it as an index / summary?
-
@DavidAlfa,
That is the best advice to date.
As an obvious newbie on these topics I am in awe at the depth of knowledge possessed by some of you.
As a newbie it is actually confusing to draw any sort of conclusion from the 20 odd pages of comments put forward so far.
A summary of what has been learned so far from you guys will be greatly appreciated. For example the implication of the various firmwares 3000, 3100....3202 on the scope and which one to choose for a particular model!!!
Thanks for ALL your input.
Regards
-
The problem with the generator remained unresolved.
FW(3000).dso3kb_20210416.(DSO2D15)
-
I would suggest locking this thread and creating a new one with a first post that clearly explains the firmware update process, but still references this "old thread" for those who want the complete details, and also references the "hacking" thread for those who want to explore their Hantek DSO2X1X.
And perhaps in the new thread we can move on to comments about using these DSOs instead of bitching and whining about them (including by people who don't actually own one)?
EDIT: done creating the new thread, and I have reserved and will curate the first five posts with essential information and facts. The new thread is here: https://www.eevblog.com/forum/testgear/hantek-dso2x1x-firmware-updates-and-best-use-practices/ (https://www.eevblog.com/forum/testgear/hantek-dso2x1x-firmware-updates-and-best-use-practices/)
-
The sooner you create the thread, the sooner people move there.
Regarding the "bitching and whining", it will continue to happen on BOTH threads. It's a feature.
-
I have also written here more than once about the problem with the generator. Rollback to the previous firmware does not help. But apparently few people are interested in this))
-
Let them work! Let's not get distracted by trifles. I hope they heard us.
-
Sergey_Malyshev, try long pressing the "Default Settings" button, there are options for a generator and maybe a calibration. I fixed this problem by soldering the memory and only then did I find this feature. But, as it turned out, it does not work for everyone.
-
It seems to work after you entered Utility menu first. The older sw versions have more options.
-
I also thought that in later versions they either removed it, or hid it somewhere. I have a very early version.
-
This menu also opens for me. But unfortunately, the generator calibration does not work and gives errors
-
So you need to restore your version. I didn’t have any errors on the error generator, I only had one of those points, but this was after recovery.
-
I originally had version 3000. The generator worked without errors. And there was only one calibration item in the menu. After installing versions 3101 and 3102, two calibration items appeared in the menu and a generator error appeared. When I installed my native 3000 version back, the problem did not disappear, but these two calibration items remained in the menu. Apparently the new firmware 3102 registered something in the flash and rollback to the old firmware does not completely erase the 3102 firmware data from the memory. So which version do you say I should still rollback to?
-
If there is no way to format the flash via USB without unsoldering it from the board in order to write the firmware to a clean flash, then you will have to order a new flash on Ali and try to upload the image to it.
-
I found few things:
- The fpga file from platform tools fw3000 is not the same as my factory fw3000 backup.
- Generator amplitude is fixed after restoring my files "/cache/cali.dat" and "/cache/dds_calbration.dat"
- Made a custom update package that replaces all /dso and /cache files with my factory ones. Worked.
Gerasim, try the attached update and tell if it makes any difference.
-
If there is no way to format the flash via USB without unsoldering it from the board in order to write the firmware to a clean flash, then you will have to order a new flash on Ali and try to upload the image to it.
See the hacking thread. DavidAlfa and I are working on two different solutions to read/write/backup/restore/modify the SPI NAND flash. DavidAlfa is writing a low-level program that reads and writes the SPI NAND flash through FEL. I am working on a small Linux distribution that can be loaded through FEL and uses the Linux kernel SPI NAND driver.
-
David is actually waiting for the ram linux method! :popcorn:
-
Apparently the new firmware 3102 registered something in the flash and rollback to the old firmware does not completely erase the 3102 firmware data from the memory. So which version do you say I should still rollback to?
The calibration data is stored in file /dso/etc/data/cali.dat (did you back up your filesystem first?)
It is cached in /cache/cali.dat and on my system both files were binary different after recalibration. You could try (with the older firmware) calibration, power cycle, calibration, power cycle and see if the problem remains. I doubt that the FPGA image retains anything, it is loaded over SPI every time pheonix app starts at boot (or crashes and is restarted by David's restart script).
Calibration itself is another app /dso/app/dso3000c_calibration that is invoked by phoenix, as far as we know it generates the cali.dat files based on values determined by the current FPGA image.
-
So, in the end the only files that matter are /cache, /data and /dso.
I will make a custom update that automatically backups and creates an UPK file for restoring your system back.
The rest, like Boot, kernel... doesn't matter because can be restored using platform tools.
Edit: Done! Check the Mods folder. It was never so simple!
- Download and run "dso3kb_BackupBuilder.upk".
- The scope will freeze ~2 minutes while compressing the data and building the package. Be patient!
- After the automatic reboot, you will have "dso3kb_CNxxxxxxxxxxxxx.bak.upk" in you usb drive.
- Put that file in a safe place. If any update breaks something, run that package to restore.
If the system no longer boots correctly or whatever, install any platform tools version, and then run the package.
-
- Generator amplitude is fixed after restoring my files "/cache/cali.dat" and "/cache/dds_calbration.dat"
Could this be the reason for Amplitude calibration option?
-
DavidAlfa Respect and esteem!!!
AWG OK!
FW(3102) calibration Ok.
:popcorn: :-+ :phew:
-
Great!
I finished the backup builder. It works really, really nice!
Run the builder, it will make the update package for you, then run the new package whenever you want to restore the system :-+
-
David! Thank you! Everything worked out! You are a true master! Now the generator is showing great! :-+ :-DMM
-
Apparently the new firmware 3102 registered something in the flash and rollback to the old firmware does not completely erase the 3102 firmware data from the memory. So which version do you say I should still rollback to?
The calibration data is stored in file /dso/etc/data/cali.dat (did you back up your filesystem first?)
It is cached in /cache/cali.dat and on my system both files were binary different after recalibration. You could try (with the older firmware) calibration, power cycle, calibration, power cycle and see if the problem remains. I doubt that the FPGA image retains anything, it is loaded over SPI every time pheonix app starts at boot (or crashes and is restarted by David's restart script).
Calibration itself is another app /dso/app/dso3000c_calibration that is invoked by phoenix, as far as we know it generates the cali.dat files based on values determined by the current FPGA image.
/dso/etc/data/ is empty in my filesystem. I think only /cache matters.
Definitely, the generator file is "dds_calbration.dat". Deleting it creates a new, empty 0-byte file and amplitude gets way higher.
Made another update package than only restores this file (For people whio didn't made a backup).
-
I am very poor at programming and therefore I have a question for you. Is it possible to programmatically change the color of the rays? I have some eye problems and it is difficult for me to distinguish between light green and yellow rays on the oscilloscope screen, since they are very close in spectrum. It would be great if it would be possible to replace, for example, yellow with blue or red, etc.
I was a little confused. Maybe this question should have been asked in a new thread?
-
I looked at that some days ago but didn't success.
I keep researching, time will say if there's a way.
-
Because the system stores and runs the update from the flash. So the filesystem changes, but not its files.
That's how Hantek made the update function.
-
I have the dso2d15, never saw any voltage spikes like described, maybe by lack of times measuring different signals.
Checked with another scope and my dso2d15 reliable on what it shows me on the display.
Is the noise all from dso2x10 versions?
For colors of the signal drawings I will later today look into the xml files and the phoenix app, at least some sort of hex edit should be done easy (my intention for later is to have a menu for changing it on the scope itself. And later like in 2-3 months) .
saving to internal and external memory just works here aswell, doesnt matter if its picture, waveform, setup.
fw3000, update from 20210416.
#2nd CoVid-19 got me some symptoms I'm recovering from, more or less like a mild flue, however the ear pain irritates my thinking a lot, hope to get rid of it this week.
-
I already checked every XML file. Seems to be hardcoded in Phoenix app.
The graphics library is libanolis, if you check the strace log you'll find drawing calls to it, ex. Draw string, draw line...
I'm looking into a specific function, "anolis_wave_plot_set_chn_wave_color".
It would be nice to run the backup builder and post it here to check if the noise gets any better on other dso.
Also, run the read EEPROM command from Keysight app, like escribed here:
https://www.eevblog.com/forum/testgear/hacking-the-dso2x1x/100/ (https://www.eevblog.com/forum/testgear/hacking-the-dso2x1x/100/)
Maybe there's also some difference in the memory between models
-
DSO2D15 - Firmware 1.0.1.1.0 Issues
Hello everybody. I just signed up to be able to reply in this thread.
I recently purchased a DSO2D15 in Aliexpress with this firmware/software factory installed:
Software: 1.0.1.1.0 (20210416.00)
Hardware: 000.000.000.000.000.000.000.001
Firmware: 3200
I have tried posting these issues on the Hantek web discussion forum, but the link on the registration page does not work.
I found following issues I want to publish:
Issue 1)
- I turn off channels 1 and 2
- I press the MEASURE button, and then I press F1 (Source)
- When I move the Menu knob to try select CH1 or CH2 (that are deactivated on the screen), the scope freezes and only works again if I turn it OFF and ON.
This issue not appear if CH1 or CH2 (or both) is active.
I think the problem is that when channels 1 and 2 have been deactivated, it should not be possible to choose them in the Source field. However, if only one channel is active, in Source you can only choose that one, but not the one that is deactivated.
Issue 2)
- I used only CH1, configured in AC coupling.
- I switch ON the Wave Gen, and configure the type of signal to Sine, Square, Exp, etc. (tested at 100Khz, 1MHz and 5MHz).
- I connect the signal output of the WG (at 1MHz for example) to the input of CH1, and press the Auto Set button (so at 1MHz it is autoconfigured in 500.00MSa/s and 4Kpt).
- If we now move the CH1 Position knob too fast (ahead of the trace's on-screen refresh rate), the oscilloscope hangs completely.
This problem appears to only affect CH1. I have repeated the same tests on CH2 and it has never hung up on me. But if I keep CH1 active (although without an input signal), I put the signal in CH2 and move the Position knob of CH1, it hangs too.
Issue 3)
Probably the same issue as 2. The underlying problem appears only when the wave generator is on, and only when the CH1 position knob is manipulated.
- Only CH1 active (with or without signal probe connected).
- The Wave Generator is also active.
- If we now move the CH1 Position knob too fast, the oscilloscope hangs completely.
This problem does not appear if only channel 2 is active, but it does appear if channel 1 is also active, and as long as the Wave Generator is on.
Best regards.
-
Where to Add Software Reboot/Reset Button to DSO2x1x
As i have not had back off this scope to look inside yet, does anyone know where to wire in a button to reset/reboot the scope?
Think this you be better solution to the lockups, than power cycling it until Hantek come up with a more stable firmware release.
Pictures would be a great help please :-)
imk
-
Where to Add Software Reboot/Reset Button to DSO2x1x
As i have not had back off this scope to look inside yet, does anyone know where to wire in a button to reset/reboot the scope?
Think this you be better solution to the lockups, than power cycling it until Hantek come up with a more stable firmware release.
Pictures would be a great help please :-)
imk
As I have already explained there is no need to add a reset button, DavidAlfa has a small program to relaunch the phoenix app when it locks up. So there is no need to take the back off the scope and void your warranty, This is the second time I write to you the same answer. |O
-
Where to Add Software Reboot/Reset Button to DSO2x1x
As i have not had back off this scope to look inside yet, does anyone know where to wire in a button to reset/reboot the scope?
Think this you be better solution to the lockups, than power cycling it until Hantek come up with a more stable firmware release.
Pictures would be a great help please :-)
imk
As I have already explained there is no need to add a reset button, DavidAlfa has a small program to relaunch the phoenix app when it locks up. So there is no need to take the back off the scope and void your warranty, This is the second time I write to you the same answer. |O
What is the pheonix thread how is it accessed how do i go about doing it.
All of this i guess is going to take me DAYS maybe WEEKS to learn, i am busy!
Up to my eyes in real jobs not hacking jobs and i have already wasted hours on this scope as it is!
5 min job to solder couple of wire, while i wait for Hantek to fix the problem or i ebay it.
That is why i ask again, as i have ZERO interest in HACKING the software with some fix from some third party hacker.
So do you know where to solder couple of wires on or NOT?
-
@AndrewBCN, @DavidAlfa
I would like to delve into my Hantek further but it seems that the Platform Tools only work in a Windows environment. Is there a Linux equivalent to this yet? I read in the DSO hacking thread that you guys are working on some Linux interface, but my limited knowledge of the subject leads me to conclude that this is still in development phase.
Any advise will be appreciated.
-
Platform-tools are made of sunxi-fel (from sunxi-tools) and fastboot binaries.
You can get them for Linux very easily.
Then copy the commands inside cmds.bat and paste them in a bash script
-
imk,
for your reset button, pin 70 on f1c200s (info taken from f1c200s datasheet, page 11)
reset circuit (info takes from lichee_zero_schematics, page 2)
but still the software version from DavidAlfa i would prefer over any hardware hack which isnt necessary.
especially when its made so simple to just run an upk through update.
files for it found on the google drive -> Mods/Hacks - > Lockup-Fix...
-
so i tested my dso2d15 for voltage spikes.am i missing something?
picture 1 shows the noise with the PP150B probe 10cm or more away from the scope, persist data is from when i move the probe around the LCD screen of it.[edit probe tip shorted with the probe gnd alligator clip simulating antenna loop]
is this supposed to be a lot of noise ?
[attach=1]
picture 2 shows lowest trigger for the ref signal, same result on mode 'auto' and 'normal' for trigger, trigger set to 'either'
[attach=2]
picture 3
DavidAlfa
AWG test signal from AWG 1KHz,1.5V, square and no offset. [edit obviously it's +1.3v offset]
green is connected just with a bnc cable (shows flaw as expected), the yellow one however is displayed when i terminate the signal with 50 \$\Omega\$ or use proper probe.
[attach=3]
i have to say i dont like the PP150B probe, my cheap P6100 are better than that
-
imk,
for your reset button, pin 70 on f1c200s (info taken from f1c200s datasheet, page 11)
reset circuit (info takes from lichee_zero_schematics, page 2)
but still the software version from DavidAlfa i would prefer over any hardware hack which isnt necessary.
especially when its made so simple to just run an upk through update.
files for it found on the google drive -> Mods/Hacks - > Lockup-Fix...
aika
Many thanks for the heads up re the reset line to the CPU.
The situation at this time is i am awaiting an update from banggood re returning this scope.
If that turns into a return i will sadly be saying goodbye to this little scope.
As i really believe that is it didn't crash/hang all the time it would be enough for my needs and i have a logic analyzer for detailed serial decoding.
If it turn into a keep it situation I will look in detail on how to implement a reset/reboot rather than power cycling it, while awaiting new firmware from hantek.
Also many thanks for the heads up re the dso3kb_install_lock_monitor.upk.
I had a look at DaveAlph's gdrive and it seems as simply as dropping the dso3kb_install_lock_monitor.upk onto a flash drive and installing it.
Hence I ask how many people have install this fix and does it work as expected please?
Many thanks imk
-
It will only work when the process crashes. If it simply hangs, the only way will be the button.
Anyways, I'm here to announce that I'm done with this scope...Not going to spend any more time with it!
You have the Files (https://drive.google.com/drive/folders/1Tqk8YbL_M3S0vtk7h_cZ-01U2idIaqqx), everything has a readme, if you crash the system just follow the FAQ (https://www.eevblog.com/forum/testgear/hantek-dso2x1x-firmware-updates-and-best-use-practices/msg3590160/#msg3590160)
Cya! :-+
-
It will only work when the process crashes. If it simply hangs, the only way will be the button.
Anyways, I'm here to announce that I'm done with this scope...Not going to spend any more time with it!
You have the Files (https://drive.google.com/drive/folders/1Tqk8YbL_M3S0vtk7h_cZ-01U2idIaqqx), everything has a readme, if you crash the system just follow the FAQ (https://www.eevblog.com/forum/testgear/hantek-dso2x1x-firmware-updates-and-best-use-practices/msg3590160/#msg3590160)
Cya! :-+
Thanks for all the good work Dave and hope your next project is just as rewarding for all.
Ian
-
It will only work when the process crashes. If it simply hangs, the only way will be the button.
Anyways, I'm here to announce that I'm done with this scope...Not going to spend any more time with it!
You have the Files (https://drive.google.com/drive/folders/1Tqk8YbL_M3S0vtk7h_cZ-01U2idIaqqx), everything has a readme, if you crash the system just follow the FAQ (https://www.eevblog.com/forum/testgear/hantek-dso2x1x-firmware-updates-and-best-use-practices/msg3590160/#msg3590160)
Cya! :-+
David Alpha! It is a pity that you are leaving us! You didn't have enough time to figure out how you can change the color of the rays. But all the same, thank you very much for the colossal work you have done to improve our long-suffering device! Thank you!!!
-
Yes, I did! Read the hacking thread! :-+
-
Hi everyone !
Can you guys tell me if this is normal for this scope to display waveforms like this in the ROLL mode ?(HORIZ MENU)
I attached two screenshots , one 1 kHz sine wave and the other one 50 Hz. Maybe there are some settings I missed
so that I can watch it in more human readable manner?
My scope is DSO2D15
In short, managed to update from original 20201221 to version 20210416(with adventures...)
Running firmware 3000.
-
michal_nt1
turn the timebase knob clockwise
imk
-
Hi imk
it looks like I can move only counter clockwise using the nob described as SEC/DIV on the phisical panel, turning clockwise
dosent seem to change anything in regard of solving the problem.
-
michal_nt1
My scope is all boxed up, so i can't easily test what you're trying to do.
Have you tried the Auto Set button, it generally finds a fairly good waveform display starting point.
-
Hi imk
of course I did,
I ran mutiple checks with diffrent settings before posting , what I recall( but im not 100 % sure) that it displayed
right before the update . Thats the reason why I asked on the forum if its normal. Anyways, thanks a lot imk for
super quick replies.
-
michal_nt1
Ah did not realize you had it working before you did an update.
So are you saying is it worked as you expected it to do, then you have done an update and now the timebase control does not seem to work correctly?
If so on DaveidAlph's gdrive, see his post you will find his archive of all the work he has done on this scope.
There you should find some very useful information and various firmwear updates and his recommendations.
-
Hi Imk,
The thing is that Im not really sure if the device was working ok or not, I recall some things but I cant tell for sure...
I wish that the owners of this scope would make a check in the ROLL mode in frequencies lets say between 50 Hz and 2 kHz and share their results . Whats funny when I go above about 100 kHz the waveform becomes "human readable" but it
looks like the trace expands or shrinks depending on the frequency.. I think that what I should see in the roll time is a period passing by from right to left with given time by the sec/div knob ...
Correct me if Im wrong .
-
Another really annoying issue I found today.
If you set adquisition in average mode (ex. to clean up the signal), when you save the picture it will save the last, non-filtered snapshot!
Damn you Hantek!
Edit: It turns out it was the avg is resetted inmediately after saving, but the picture is ok.
But if you push stop, then yes, it will be resetted!
michal, the wave issue is because you're breaking nyquist (sampled signal frequency/ adcs ample rate), and hantek does pretty much nothing to filter it.
You can see that with the wavegen...ex 1KHz, it will look ok at 200uS/div, but if you go back to 10...100mS range, it will show a completely different signal.
-
DavidAlfa, thanks for a comprihensive answer :-+
-
Hello Michal! I have a big request for you. Can you back up your 2d15 for me? It’s very simple. Go to the DavidAlf folder with the name GDrive. There you will find the file "dso3kb bakup builder.upk". Copy it to your USB stick and run it on your device. After that, a new file will appear on your flash drive - your backup copy. I would really like you to send it to me, but rather leave a download link in this thread. At one time I did not create such a copy and now I am suffering. Thank you!
-
What issues are you having?
The serial, model, HW, FW version, wavegen calibration... All can be restored easily with the available mods.
-
Hi Gerasim,
The problem is that I dont have original files either... Briefly, my scope came with version 20201221 and FW 3000, then I upgraded it to dso3kb_20210416,
then downgraded to dso3kb_20210311 (for testing purposes) and the scope started to freeze. After couple of restarts it became nonresponsive.
( I could see the screen, like 2 relay cliks on start and beeps when keys pressed and that was about it ... .) To fix the scope I used platform tools 20201221,
it fixed it but some ID's were removed like model and serial, so I used the script form DavidAlpha to change ID's. Luckly I had pictures of ID's taken before. Then I realized that there was an issue with calibration , because platform tools uses diffrent FW so to fix calibration upgraded from utility menu using the firmware changer dso3kb_FW3000 in DavidAlfa's folder, that changes FW to original 3000. Now I hope everything is as it was before upgrades. Who knows... Everything you need with instructions is in DavidAlfa's google drive.
-
Check the FAQ in my signature to see what updates can be applied safely. As long as FW is not changed, everything will be ok :-+
Platform-tools 20201221 also uses FW3000, so there shouldn't be any issues?
I also had a lot of freezing 2 weeks ago.
All seemed correct, fw , model were ok, but it freezed very easily. I'm pretty sure I had flashed platform-tools 20201221 and then upgraded to 20210416.
Since then I flashed it few times already.
Currently, everything is undefined, I only bothered to restore the wave gen calibration... and no freezing!
-
Thank you for your answers! But I know all this and at the moment I have a copy, which was provided to me by DavidAlfa. I also used the generator calibration file. In principle, everything suits me, except for small moments. The generator works quite well at voltages above 1v, but as the voltage drops, the shoulder skew increases greatly. So everyone? It is possible that Hantec calibrates the generator separately for each scope and therefore the calibration files of different devices may not match. So I wanted to try installing a backup from other devices, hoping that the result would be better.
-
That's because your calibration is wrong, make a new one!
The same happened to me:
https://www.eevblog.com/forum/testgear/new-hantek-dso2x1x-models/msg3585539/#msg3585539 (https://www.eevblog.com/forum/testgear/new-hantek-dso2x1x-models/msg3585539/#msg3585539)
-
We probably didn't understand each other). I meant the offset of the generator amplitude in min and max. I've calibrated many times and reset the scope to default. It does not help. Only by manually shifting the amplitude can you more or less achieve some result and set the signal to the center. But I wish I didn't have to do this. But that's okay! Will live!)) :popcorn:
-
I've been debugging i2c signals. Must say that at least this decoder work great!
Here the overclock makes a brutal difference:
https://www.youtube.com/watch?v=CKMDma6xilY (https://www.youtube.com/watch?v=CKMDma6xilY)
-
I've been debugging i2c signals. Must say that at least this decoder work great!
Here the overclock makes a brutal difference:
https://www.youtube.com/watch?v=CKMDma6xilY (https://www.youtube.com/watch?v=CKMDma6xilY)
Hello David,
I found the i2c decoder worked VERY well at times, but sometimes I have lockup issues and had to power cycle, then after restart the i2c decoder would not sync correctly so i had to power cycle it a second time to get it to work correctly , most odd.
So are instruction for the overclock on your gdrive and how much did you overclock by please.
ian
-
Everything is inside Mods / Overclocking folder.
By default it's set to 696MHz(CPU) / 192MHz (RAM). More than that crashed for me.
To change the multipliers, check the script "oc_manager", edit it before running the update package, as thefiles in the usb/overclock folder are copied to the system.
If you want to change the multipliers after installing, just edit the usb files and run the installer again, no need to remove first.
However, I found an issue, only if you flashed platform-tools 20210517. 20201221 and 20210129 are ok.
The keyboard kernel module doesn't output keyboard messages like previous versions, so the overclock script won't be able to detect if you pushed F0 key to skip it.
If the system hangs, then the only way to recover will be platform tools.
However I tested replacing that file (/dso/etc/fpga_i2c_kbd.ko) with the 20210129 version, and it works.
Last update that changes that file is 20210311.
-
I'm new to this community. I started running into some issues with my new DSO2C10 today. It started freezing a lot trying to decode some I2C to the point where it would not respond at all after a reboot; the default setup button did not respond at all.
After a few hours of reading around the forum, I decided to try the platform-tools but it seems that the ones available at DavidAlfa's Gdrive are not suitable for my FW version. :-//
I think I need the platform tools for FW3200, does anyone have it?
I tried the three available in the Gdrive and after restarting the scope it will just show the Hantek logo...
Thanks
-
I'm new to this community. I started running into some issues with my new DSO2C10 today. It started freezing a lot trying to decode some I2C to the point where it would not respond at all after a reboot; the default setup button did not respond at all.
After a few hours of reading around the forum, I decided to try the platform-tools but it seems that the ones available at DavidAlfa's Gdrive are not suitable for my FW version. :-//
I think I need the platform tools for FW3200, does anyone have it?
I tried the three available in the Gdrive and after restarting the scope it will just show the Hantek logo...
Thanks
Forgot to mention that my scope was running FW3200, 20210416 before all this.
-
Try flashing any platform tools version you like. I'd try the latest. Then use FW changer to restore FW3200.
But before flashing anything try to backup your system with the backup builder!
If it hangs shortly after boot, try pressing quickly default setup button, hopefully it will be enought to run the mods.
-
Try flashing any platform tools version you like. I'd try the latest. Then use FW changer to restore FW3200.
But before flashing anything try to backup your system with the backup builder!
If it hangs shortly after boot, try pressing quickly default setup button, hopefully it will be enought to run the mods.
Thanks for getting back to me. I actually tried the latest platform-tools 20210517 and wanted to clarify that after it finished flashing, the scope rebooted as expected but it's now stuck with the Hantek logo so I have no way to get to the system update menu unfortunately.
I think I soft bricked it by using the wrong platform tools for my fw version 3200.
I will appreciate any further insight.
-
I'm pretty sure it failed uploading some file and you didn't read the update window.
First remove the USB drive, you can't have both plugged in.
As far a I know it's impossible to brick it.
Read my FAQ. USB 3.0 ports give problems.
Read carefully the output of the update process.
-
rtausx I, too, a couple of times after using platform tools, the scope showed only a splash screen. Repeat the procedure one more time. Make sure that the driver is displayed correctly in the device manager and immediately run cmds.bad. And if the driver is not detected, then reinstall it using zadig.exe. And run cmds.bad right away. Good luck!
-
DavidAlfa and Gerasim you guys rock!! I tried with another computer and it worked now. It was either driver not installed correctly or because of USB 3.0 on my laptop (I tried 2.0 now).
To my surprise, my DSO2C10 has all the components for the function generator and it works like a charm. What a steal for $185!!!
Now that I feel safe with tinkering a bit more, it's time for OC.
Thx again
-
I increased Vcore slightly over specifications.
Nominal is 1.1V, max 1.2V, I got 1.25.
I'm currently testing and modifying the overclocking script, because I had to use the second PLL_K multiplier to go over 768MHz.
But it seems stable at 912MHz :-DD
And factory default is 408MHz, not 384, I had missed that multiplier = Val+1 (default value16, but effectively 17)
-
I increased Vcore slightly over specifications.
Nominal is 1.1V, max 1.2V, I got 1.25.
I'm currently testing and modifying the overclocking script, because I had to use the second PLL_K multiplier to go over 768MHz.
But it seems stable at 912MHz :-DD
And factory default is 408MHz, not 384, I had missed that multiplier = Val+1 (default value16, but effectively 17)
David
The overclock interests me, but i am little concerned about temperature rise.
Did you happen to do a pre and post overclock temperature check?
imk
-
I already said a few times. It barely gets warm.
The worst that can happen woudl be a system crash, requiring reboot.
Don't try it yet,.I'm updating the overclocking script.
-
Ok David
Thanks for info, i'll await an update.
Ian
-
Achieved 1GHz at 1.35Vcore! 250% original speed! :-BROKE
# pi 1000000
Starting PI...
Pi: 3.141592653589794004176383168669417500495910644531250000000000
Loops: 1000000
Time: 9935mS
# oc_manager
[ 191.748086] Overclocking CPU to 1044MHz...
# pi 1000000
Starting PI...
Pi: 3.141592653589794004176383168669417500495910644531250000000000
Loops: 1000000
Time: 3878mS
And the Voltage/Frequency table I found in my tests:
1,1V 720MHz
1,15V 792MHz
1,2V 864MHz
1,25V 936MHz
1,3V 972MHz
1,35V 1044MHz
About 70MHz gain per 50mV step. Except the weird spot at 1.3V.
-
I discovered a strange thing - I have 2 capacitors soldered to the legs of an unnamed chip. I have not seen this in other photos of this board. Does anyone have this? I wonder what the Chinese wanted to adjust in my scope?
-
Those are across each of the ADC's differential input pairs from the front end. I have these on my DSO2D15 from January. They're noted in the photos I posted back on page 3 or so. Some units have them.. the flux residue indicates they're installed by hand after manufacture.
-
Sure, probably a later revision of the board, to avoid noise or enhance signal integrity.
https://www.eevblog.com/forum/testgear/new-hantek-dso2x1x-models/msg3434052/#msg3434052 (https://www.eevblog.com/forum/testgear/new-hantek-dso2x1x-models/msg3434052/#msg3434052)
Mine also does have them.
I updated the overclocking script, now it allows to fully customize PLL N/K/M parameters.
There's a new test mode that loads the script from the usb drive, so you can try anything without fear, if there's no drive, there's no overclock.
When you find a stable overlock, then run the permanent installer, and it will load automatically from the internal memory.
I also made a fix for the platform-tools 20210517 version. The usb problem is purely caused by the phoenix app.
Replacing it with the previous version (Phoenix-20210416) completely fixes the issue. You can also run the 20210416 update.
I used it in my FW3000 scope, worked perfectly
- Install platform tools 20210517. Don't worry about the usb issue, it will start working when you hit Utility/Update few times.
- Install usb fix (Phoenix-20210416 mod package)
- Install Backup-CNxxxxxxxxxx.upk (Read above).
I also modified backup builder. Now generates two files:
- dso3kb_CNxxx.upk: Restores Model, Serial, HW, FW, Generator calibration, but skips dso, preserving the existing dso software.
- dso3kb_CNxxx_FULL.upk: Restores Model, Serial, HW, FW, Generator calibration and dso, overwriting the existing dso software, almost like restoring the original system.
-
I discovered a strange thing - I have 2 capacitors soldered to the legs of an unnamed chip. I have not seen this in other photos of this board. Does anyone have this? I wonder what the Chinese wanted to adjust in my scope?
My DSO2D15 must be a revised later hardware version because it does not have the capacitors soldered on the pins of the chip U38 (they will now probably be C38 and C49), and the capacitors C439 and C440 are now in a different position relative to U38.
-
Seems so. Check the pcb version, it comes with the date.
-
My main pcb: DSO2D15_V1.7 2021.1.14
Secondary pcb (knobs/leds/...): KB3000C V0.5, probably manufactured in week 47 of the year 2020.
-
Fw3200 ?
-
Yes, with software version 1.0.1.1.0 (20210416.00)
-
I suspected it, but now it's clear that fw3200 is for a different hardware than fw3000 :-+
-
Apparently, this is why Hantec has not been releasing official firmware for so long. He's now confused to release a universal firmware that fits both fw3000 and fw3202
-
I don't think so.
The firmware updates usually update the dso app but not the libraries(which interface the hardware).
The calls will probably be the same. You can run any software version, as long as the FW (fpga programming) is correct.
Confused? Maybe you meant incompetent.
I'm pretty sure that most issues could be fixed in some weeks with a proper team of experienced people.
The fact that they started selling it with a software that crashed every 2 minutes says a lot about them.
If the average user knows these issues, what will hantek people know!
Maybe it was targeted to a more expensive market, but they screwed up the design and had to get rid of them by selling at low lost? :-DD
-
DavidAlfa, i tried to install yours Lock-ap fix. When freezing, the monitor readings are restored, there is a reaction to the input signal, but everything else is blocked, you still need to reboot. Is that how it should be?
-
Yes, I know it happened, it was caused by another process locking the keyboard (dbus-daemon).
I thought I had updated the file, but it seems I forgot. Updated now.
Download it and install again (No need to remove first) .
-
DavidAlfa
It looks like i'll be keeping this DSO2D10 for awhile, hence i have taken the back off to see what board versions it is; DSO2D15_V1.7 2021.1.14
So i am wondering what you think will be the best .upk version for it will be, plus with your crash detection reboot solution please?
imk
-
I don't know? I don't have 20 hanteks at home :-DD
You can install any firmware without fear. First run backup builder and store the files.
Then you can try update. If any changes your fw, restore it by running the restore packages.
Crash solution? Did you see my Gdrive?
-
DavidAlfa
Ok i'll see which update is most stable, but am hopping hantek are going to release big fix all update soon.
I download dso3kb_install_lockup_monitor week or so ago, but i noticed in previous post you had new version so i'll get pull that down.
thanks again imk
-
I sent to Hantek support the report of the errors that I detected up to date in my scope (see message https://www.eevblog.com/forum/testgear/new-hantek-dso2x1x-models/msg3591243/#msg3591243 (https://www.eevblog.com/forum/testgear/new-hantek-dso2x1x-models/msg3591243/#msg3591243)) and they have responded that as soon as the responsible engineer solves the first issue, they will contact me again. But for issues 2 and 3 they tell me they are resolved by the following firmware update file that they have sent me:
dso3kb_20210630_auto_update_fpga.upk
In case someone else might need it, I've already uploaded it to the public folder of DavidAlfa's GDrive ('popy5_dsodso3kb_20210630_auto_update_fpga' folder).
Please note that my DSO2D15 scope comes standard with the following software/hardware/firmware:
Software: 1.0.1.1.0 (20210416.00)
Hardware: 000.000.000.000.000.000.000.001
Firmware: 3200
Update: after updating the scope, my firmware version is now 3202.
-
popy5
Thanks for the dso3kb_20210630_auto_update_fpga I'll try it out later tonight or in morning.
DavidAlfa Question:
I have run the backup upk and installed the lockup monitor successfully, I'll try the overclock a little later this evening or tomorrow :-)
Question will lockup monitor and/or overclock util be overwritten by a Hantek provided upk update?
Or should i remove them first, do the new Hantek update then reinstall your utils?
imk
-
No. At least until now, Hantek updates only affect the dso folder and the fpga firmware.
-
No. At least until now, Hantek updates only affect the dso folder and the fpga firmware.
Thanks for that David, I shall be mindful accordingly.
Interesting; I am running the Hantek upk that was originally installed (dso3kb_20210416) it was so easy to get it to lockup that Hantek sent to me dso3kb_20210510 which was somewhat better.
However since i installed dso3kb_install_lockup_monitor I can't get dso3kb_20210416 to lockup at all :-// the ghost in the machine
ian
-
I sent to Hantek support the report of the errors that I detected up to date in my scope (see message https://www.eevblog.com/forum/testgear/new-hantek-dso2x1x-models/msg3591243/#msg3591243 (https://www.eevblog.com/forum/testgear/new-hantek-dso2x1x-models/msg3591243/#msg3591243)) and they have responded that as soon as the responsible engineer solves the first issue, they will contact me again. But for issues 2 and 3 they tell me they are resolved by the following firmware update file that they have sent me:
dso3kb_20210630_auto_update_fpga.upk
In case someone else might need it, I've already uploaded it to the public folder of DavidAlfa's GDrive ('popy5_dsodso3kb_20210630_auto_update_fpga' folder).
Please note that my DSO2D15 scope comes standard with the following software/hardware/firmware:
Software: 1.0.1.1.0 (20210416.00)
Hardware: 000.000.000.000.000.000.000.001
Firmware: 3200
Update: after updating the scope, my firmware version is now 3202.
Tried it. It just changes the fpga fw and the allwinner ADC keypad kernel module (strange because as far as I know it's not used here).
It includes FW 3102 and FW 3202, and a binary that detects the fpga version (I guess if the correct fw was loaded in first place).
Curiously, FW3102 is named 3002. Mi FW3000 changed to 3102. Calibration works correctly, so I wonder if 3102 is just an update for the FW3000.
FW32000 is clearly a different hardware.
-
They have contacted me again from Hantek support. The new update file resolves the issue 1 sended to Hantek support few days ago (see message https://www.eevblog.com/forum/testgear/new-hantek-dso2x1x-models/msg3591243/#msg3591243 (https://www.eevblog.com/forum/testgear/new-hantek-dso2x1x-models/msg3591243/#msg3591243)):
Issue 1)
- I turn off channels 1 and 2
- I press the MEASURE button, and then I press F1 (Source)
- When I move the Menu knob to try select CH1 or CH2 (that are deactivated on the screen), the scope freezes and only works again if I turn it OFF and ON.
This issue not appear if CH1 or CH2 (or both) is active.
I think the problem is that when channels 1 and 2 have been deactivated, it should not be possible to choose them in the Source field. However, if only one channel is active, in Source you can only choose that one, but not the one that is deactivated.
The update file is called dso3kb_20210705.upk, and it is already available in the public folder of DavidAlfa's GDrive (folder 'popy5_dso3kb_20210705').
Direct link:
https://drive.google.com/file/d/1o3dSo3dVEcPRq6x6YFAccuV6nTTat9ke/view?usp=sharing (https://drive.google.com/file/d/1o3dSo3dVEcPRq6x6YFAccuV6nTTat9ke/view?usp=sharing)
Update: my software version changed from 1.0.1.1.0 (20210416.00) to 1.0.1.1.0 (20210705.00)
-
excellent news re the new firmware, two in a few days.. Me think hentek about to a new official release :-)
BTW When i took back off my scope I forgot to measure the PSU voltages.
Anyone know what they are as was thinking as soo much spare space inside the back I could add battery's to make it a portable scope?
imk
-
5 for digital , +-8V (symmetric) for analog
-
I also have this dependence of channels on each other. It appears in the trigger and in automatic measurements.
-
DavidAlfa many thanks for the volts :-)
Says on back of scope max 50w and can get off hobbyking 50w 3 cell lipo for $25 or so.
That with few buck convertor and few 3D printed supports should fit nicely inside and give maybe one hour plus of No Mains Required.
Maybe put the buck convertors inside the box and battery in a cradle on the back of case so could easily swap battery out. :popcorn:
Or maybe even easier to get a pure sine 100w inverter and have external mains supply...
--- Ideas welcome ---
Thinking, thanks again ian
-
20210705 is safe to apply, doesn't modify the FW :-+
Also, I don't know if it was the FW3102 update or the dso app, but the problem when saturating the input at low levels, distorting the signal ang losing the DC coupling, is gone!
However the usb has the issue like 20210510.
popy5, does the usb work correctly for you? Power up the dso with no usb, when it's running plug it in and try hit the save to usb button.
Should simply complain about no usb present. And will start working when you go into utility and hit Update 2-3 times.
Edit:
I restored app 20140416, usb works again as expected. But keeping FW3102, the channel problem is still fixed. So it's the FW3102 what fixes it.
-
David thanks for update on 20210705 will try it later.
Now i have had my DSO2D10 on for two days solid, ch2 input jumpered to gen out.
Every few minutes sitting at my desk i would adjust some function and scope never locked up once in two days.
Then about 4pm yesterday the reinitialization message popped as your reboot mod kicked in.
After the first reboot the scope was very sensitive to any adjustment crashing all the time.
Then the ch2 trace disappeared and displayed an offset voltage of 170 volts.
Then no amount of knob twiddling could i find the trace, so i pressed "Auto Set", normalcy returned and scope was stable for rest of the evening.
Just thought you would like to know your reboot mod works just fine, well tested here :-)
imk
-
Hello everyone, I decided to join too. I have a 2D10 converted to 2D15, the initial FW 3000. After installing dso3kb_20210630_auto_update_fpga.upk, no changes occurred, the FW version is still 3000. After installing dso3kb_20210705. upk, the SW version became 1.0.1.1.0 (20210705.00), there is no problem with USB.
-
Hi, do you think we should go through ...0630... before installing ...0705...? I current have FW3000 displayed and the April update.
-
...
However the usb has the issue like 20210510.
popy5, does the usb work correctly for you? Power up the dso with no usb, when it's running plug it in and try hit the save to usb button.
Should simply complain about no usb present. And will start working when you go into utility and hit Update 2-3 times.
...
Yes, in my case the usb has always worked fine for me, and now after updating to the dso3kb_20210705.upk, it detects the inserted flash drive without problems (formatted in FAT32), and the captures in BMP format are correctly recorded in it.
-
David,
I just ran dso3kb_backup_builder util but it didn't produce any backup files, mem stick was unchanged.
It went through the motions progress bar and hardware re init but zero change to the mem stick is 4gb
Photo of my system info below, only deviation is it has the reboot util installed
2nd try, I just tried it again from mem stick i used to bkup from successfully the other day and bkup didn't work again?
Only change is that the lockup monitor is installed, could it be the issue?
Opps, sitting watching the scope and i just did what looked like a power on up sequence Hantek logo full initialization etc.
Didn't look like the locked reboot i had the other day, this was like a power on sequence, any ideas?
Update, removed reboot monitor and backup worked
Final 1145 update installed 0630 then 0705, reboot and recal. Scope for 5 min and locked up, install lockup monitor and testing see 2nd photo 5573.
ian
-
DavidAlfa
Have you tested the overclock with dso3kb_20210630_auto_update_fpga and/or dso3kb_20210705
If so at what oc speed please?
ian
-
Will be the same. Oc won't change.
-
Will be the same. Oc won't change.
David, thanks for that.
BTW reading your script, i can't see where you set the core volts could you give me a pointer please?
ian
-
You can't. You have to modify the board regulator feedback resistor network. I don't recommend doing so.
-
You can't. You have to modify the board regulator feedback resistor network. I don't recommend doing so.
Thanks David, that explains why i could fine it. ^-^
There was a time when i could solder 40 gauge wire without any aids; glasses etc.
But some years on soldering really fine stuff is now not so easy, hence i'll be keeping to stock vcore.
Ian
-
============ DSO2xxx range ON SALE AT BANGGOOD ==========
https://www.banggood.com/Hantek-DSO2D10-Digital-Oscilloscope-2CH+1CH-Digital-Storage-1GS-or-s-Sampling-Rate-100MHz-Bandwidth-Dual-Channel-Economical-Oscilloscope-with-Signal-Source(AWG)-p-1765904.html?cur_warehouse=CN&rmmds=search (https://www.banggood.com/Hantek-DSO2D10-Digital-Oscilloscope-2CH+1CH-Digital-Storage-1GS-or-s-Sampling-Rate-100MHz-Bandwidth-Dual-Channel-Economical-Oscilloscope-with-Signal-Source(AWG)-p-1765904.html?cur_warehouse=CN&rmmds=search)
Is this a clue to what happens to the DSO2xxx next, as no new software release for ages!
Pity as I still think it is great little scope for the monies if is was not for all the bugs.
Buy a spare now before they are all gone!
-
BangGood "Flash Sale" on the DSO2D10. The price they're showing to me is the same price as it was before. All they did was raise the "Normal price" to show a bigger discount. Still a better price than most other places. Likely flushing out old stock, now that there are other competitive options at the entry level of this scrap pile. If Hantek can just fix their firmware a bit more, they've got a chance to float theirs back to the top.
-
Hello David,
I have installed 0603 then 0705 updates and this DSO2D10 seems pretty stable with your LockUpMonitor as in two day has only rebooted once, many thanks :-)
So my next DSO2D10 adventure is going to be the overclock, so could you let me know please what OC you are happy with, with respect to best performance/reliability please.
As no point me repeating all the good testing you have done and me locking scope up and having to Platform Tool It etc
Thanks Ian
-
imk, and in the mode of automatic measurements was checked? Everything is stable for me, except for this mode, and the instability is given by a horizontal scan. If you use only vertical, then there are no freezes.
-
imk, and in the mode of automatic measurements was checked? Everything is stable for me, except for this mode, and the instability is given by a horizontal scan. If you use only vertical, then there are no freezes.
Piton,
That is about what i am finding with present updates, originally vertical changes would cause lockups.
Now i am finding that only changes to sec/div horizonal timebase changes seem to cause lockups.
However i think running scope in high Mem Depth may also still cause issues.
We are making progress, let us hope Hantek are watching and will release new fix all bugs upk soon :-)
imk
-
Read the FAQ.
That file just copies the file to the USB, it's not for restoring purposes but for sending it to me in the case your fw version is not in the list.
For backup purposes just use backup builder.
-
New version 20210714 seems to solve the usb issues caused by updates >20210416.
Also menu calibration is different, like old versions that only had "Calibrate" button.
-
New version 20210714 seems to solve the usb issues caused by updates >20210416.
Also menu calibration is different, like old versions that only had "Calibrate" button.
On the contrary, I have a problem with this firmware - the front USB is blocked until you press "update", and the rear USB icon is constantly on.
-
@DavidAlfa, Where do you get the 20210714 update? The latest update on the Hantek download is only 20210416.
-
I'd like to have a file like dso3kb_FWxxxx.upk to change only FW version. My FW version is b000. So I attach the file backup_psram_board_test.fs.bin to this message. Thank's a lot.
Done! :-+
On the contrary, I have a problem with this firmware - the front USB is blocked until you press "update", and the rear USB icon is constantly on.
Let me guess, is yours FW3200?
Because that's exatcly what happens to me with the latest versions, having FW3000.
@DavidAlfa, Where do you get the 20210714 update? The latest update on the Hantek download is only 20210416.
These updates come from hantek support email. People complain, hantek sends a test/updated FW, and it arrives to me somehow :D.
-
Hi all,
would it be safe to assume that with the latest updates, the lock-ups should at least be much reduced? I received my DSO2D10 yesterday, and the best way to describe it is unusable. It freezed so frequently as to be essentially useless (basically all I had to do was change the vertical position of CH1 a bit to trigger a freeze fairly reliably). So I updated, first with the latest version from the Hantek site, then with 20210714. I also installed the lockup monitor hack.
All this seems to have made no difference at all. It will still lock up in the same way, and just as often. The lockup monitor does not seem to do anything; I still need to power cycle every time.
Is it possible that I've got myself a particularly bad lemon here?
The FPGA bitstream revision is 3200.
Cheers,
nodi
-
Did you make a backup with backup builder before anything else, right?
What's yoru FW version in utility /system info? I guess is FW3000, seem to be the problematic ones.
Try flashing platform-tools-20210129.
After that run the backup package (Not the FULL one) to restore fw, sn, model...
Then:
- For FW3200, run 20210510, then 20210705. Your fw will change to 3202, it's ok.
- For other FW version, run 20210416. You might also try 20210714.
Lockup monitor only works when the process crashes and closes, which is the most common.
But sometimes it hangs instead crashing, so it won't detect the issue.
-
Hi all,
would it be safe to assume that with the latest updates, the lock-ups should at least be much reduced? I received my DSO2D10 yesterday, and the best way to describe it is unusable. It freezed so frequently as to be essentially useless (basically all I had to do was change the vertical position of CH1 a bit to trigger a freeze fairly reliably). So I updated, first with the latest version from the Hantek site, then with 20210714. I also installed the lockup monitor hack.
All this seems to have made no difference at all. It will still lock up in the same way, and just as often. The lockup monitor does not seem to do anything; I still need to power cycle every time.
Is it possible that I've got myself a particularly bad lemon here?
The FPGA bitstream revision is 3200.
Cheers,
nodi
Hi nodi75,
my DSO2D15 that also came with v3200 firmware had the same problems (see here: https://www.eevblog.com/forum/testgear/new-hantek-dso2x1x-models/msg3591243/#msg3591243 (https://www.eevblog.com/forum/testgear/new-hantek-dso2x1x-models/msg3591243/#msg3591243)). So I contacted Hantek with the first three bugs I found and they sent me some updates which solved those crashes by moving the channel 1 position knob.
Both the firmware update and the software update that they sent me (first I applied the firm one, then the soft), are the following (all of them and some more are compiled in DavidAlfa's GDrive):
fpga fw update (solve my issues 2 and 3): dso3kb_20210630_auto_update_fpga.upk (updated from 3200 to 3202)
https://drive.google.com/drive/folders/1HWxfuqWcFdJljvUTQCt1FOSJr9wd6un9 (https://drive.google.com/drive/folders/1HWxfuqWcFdJljvUTQCt1FOSJr9wd6un9)
I think there should be no incompatibility for you to install it... as I say, in my case it solved the crashing issues by moving the channel 1 position knob.
-
Hi popy5 - thank you very much, as opposed to various software revisions, updating to FPGA 3202 seems to have done the trick - the constant lock-ups appear to have gone - brilliant! I'm now on software 20210705 and FGPA 3202. Fingers crossed!
Cheers,
nodi
-
An lemon alright. After the FPGA update it worked like a charm - for a while. Now it's just dead. I must have power cycled it about 20 times since my last update - without a single problem. Now it suddenly won't power up any more. And by that I mean not so much as a peep or one lit up pixel.
I'll open it up and check the basics tomorrow, but this is beyond all reasonable pessimism. I mean I know this a low end product targeted at hobbyists. I can live with a few quirks. But this?
And WTF were they thinking shipping this to the UK with a Schuko plug and and an ungrounded adapter? Is this even legal? I’m using my own grounded UK to C13 cable obviously, so that’s not the problem here, but that doesn’t seem right.
-
That's werid. The hw design is pretty acceptable. I mean no crazy hacks like most chinese cheap market.
Before opening anything... check that you have voltage at the connector! Sometimes the most simple things are done last... :-DD
-
An lemon alright. After the FPGA update it worked like a charm - for a while. Now it's just dead. I must have power cycled it about 20 times since my last update - without a single problem. Now it suddenly won't power up any more. And by that I mean not so much as a peep or one lit up pixel.
I'll open it up and check the basics tomorrow, but this is beyond all reasonable pessimism. I mean I know this a low end product targeted at hobbyists. I can live with a few quirks. But this?
And WTF were they thinking shipping this to the UK with a Schuko plug and and an ungrounded adapter? Is this even legal? I’m using my own grounded UK to C13 cable obviously, so that’s not the problem here, but that doesn’t seem right.
Try to send a message (with your oscilloscope serial number, firm and sof versions) to support@hantek.com.
In the forum at EEDiscuss (https://www.eediscuss.com/forum.php?mod=viewthread&tid=15609&extra=page%3D1 (https://www.eediscuss.com/forum.php?mod=viewthread&tid=15609&extra=page%3D1)) there is a message with problems like yours and someone "from hantek" has asked for that information.
-
@DavidAlfa @popy5
Cheers guys. The thing's definitely gone AWOL; not a peep from it. I already tried mailing Hantek support but no response so far. I'll try to invoke warranty first, so I won't open it for the time being.
-
Got a response from Hantek support! They are trying to help and they're very liberal with inofficial/unreleased software versions, I have to give them that.
And they have a sense of humor too! I explained that the device does not power on any more, neither in regular mode, nor does it show up on the USB in FEL boot mode. It's just dead.
Whereupon they sent me an .upk to install. :palm:
-
Let them also say thanks to DavidAlfa for doing the work for them to curb this wild creature.
-
if they released the source code we would make a truly beast :-+
-
if they released the source code we would make a truly beast :-+
I bet the annoying quirks such as the freezes would be flushed out in no time.
You've ported all sorts of things to this SoC as I understand. Forgive my ignorance, but I have to ask - there is a linux kernel, a toolchain and access to the graphics stack available for the Allwinner then? And it doesn't all seem to be terribly well hidden away either, the .upks appear to be just archives with binaries and shell scripts in them. From your doom demo it is obvious that you can even query the buttons/encoders. Is it just the FPGA bitstream and interface to the AFE then that is the missing magic spice here?
And yes, thanks for all your work in getting these things up and running :-+
-
I really have very little knowledge about Linux.
Neither I ported anything, just cross-compiled code using arm-linux-gnueabi toolchain, but modifying little to nothing.
I've drop a lot of hours over it, definitely not my place.
Graphics stack? Toolchain? As far as I know there's nothing official, allwinner drivers are usually non-existent, as well as their support.
I doubt hantek is using the graphics hardware, it seems it's a plain frame buffer, and all the work is done by the CPU.
It doesn't even support double buffering, so I'm 99.9% sure.
I've played with few graphics libraries in this thing...
LVGL seems to be the fastest. I just ran some demos.
And that already required a lot of time because the documentation was obsolete, so the variables, functions, were named differently. Argg the Linux thing... |O
-
I really have very little knowledge about Linux.
........
LVGL seems to be the fastest. I just ran some demos.
And that already required a lot of time because the documentation was obsolete, so the variables, functions, were named differently. Argg the Linux thing... |O
I hear you ;D That is why I wrote my own simple display lib for the FNIRSI-1013D reversal. Have looked into SDL and LVGL but that would also have taken its time to get up and running. As for linux on such a light weight cpu, it works but not my thing.
-
Oh, Lvgl is really nice! I might use it to make a gui for updates and patches.
Have you tried the demos? Compiling is easy once you properly found the correct defines and set up the project.
I'm using eclipse. I can send you the compiled files and rready to import eclipse project if you want to try.
You'll only need to install the compiler (sudo apt install gcc-arm-linux-gnueabi), eclipse and maybe java.
-
Hi David, I'm sure it is a nice lib. Have looked at the demo's but did not try them. I have the necessary software running on one of my machines, so can play with your files. I will send you my email via a personal message.
Thanks,
Peter
-
I'll send you the project later, can't do it right now.
But you can download the compiled lvgl demo in my GDrive, it's in mods... / static compiled binaries folder.
It's made for 800x480 screen.
Edit: Uploaded the project. It's inside Mods... / misc. Use the option in eclipse Import... existing project... select file.
It's made for linux framebuffer!
-
Hello,
I was filming the review for the 2D10 in DSO2000 series and I got a crashed oscilloscope for 2 times, look around minute 26:
https://www.youtube.com/watch?v=2xRvbORAahM&pp=sAQA (https://www.youtube.com/watch?v=2xRvbORAahM&pp=sAQA)
Anyway, I manage to trace it to the "Persist" function being on and I later after puting the video online tried again
and manage to replicate the problem again, so it seems if the "Persist" mode is on, you will have a crash in a few minutes of usage.
I first detected this while demonstrating the XY mode with the persist mode one (Display->Page 2->Persist = Infinite)
but was able to replicate just with sine waves on the screen... nothing fancy. Anybody with the same issue?
Cheers,
Hugo
-
Sure, update the firmware. Post your FW version!
-
Hi,
The software version is 1.0.1.1.0 (20210416.00) and the firmware version 3200.
I didn't update yet because there is also a line DSO2000 of handheld devices and the website only says DSO2000 not being very specific about the covered models. :palm:
But I'll update the firmware.
Thanks m8.
Cheers,
Hugo
-
Hi,
The software version is 1.0.1.1.0 (20210416.00) and the firmware version 3200.
2021 0416 is the most recent version on the Hantek website. There are newer versions you can get from Hantek support. Send them a bug report.
I don't know why it isn't on their website.
-
But I'll update the firmware.
From DavidA's FAQ: (link is in his signature)
Read carefully: There's a big difference between "Firmware version" and "Software version".
Firmware version refers to the firmware running in the internal FPGA.
Some updates will change it, so don't flash anything you find over internet unless you have a backup!
Software version refers to the actual software running inside the CPU(Phoenix).
DO NOT change your FW version unless specifically told you to do so!
-
Update to fw3202. Check the FAQ.
-
At least I ordered one last week at Aliexpress. The order was confirmed first, two days later I received a messageto confirm the new EU VAT handling. Today I got the message that the item is out of stock and and will not be produced by Hantek before end of September, I was pleased to cancel the order.
-
Apparently, we won't see the new firmware before September either.
-
My DSO2D10 arrived today. Came with an unbranded 150MHz probe. I suppose they know we are all going to hack them.
From the tape, I could tell the box had been opened twice. I was a bit concerned but the scope looks to be entirely untouched. My guess it was opened for export customs in China and then again by UK customs. - There were delays at both.
I've only had time for a quick power on check. So far it works as expected.
Shipped with:
Software 1.0.1.1.0 (20210416.00)
Hardware 000.000.000.000.000. ..... .001
Firmware 3200
I'll be making backups before doing anything else.
-
On my oscilloscope hardware all zeros:
Hardware 000.000.000.000.000. ..... .000
At the same time, all other data is normal,
the firmware was 20210416, the hardware version is 3200, the serial number is correct.
What is the reason for this. Who knows?
-
Your's must be a DSO2C1x model, .000 is no wave gen, .001 is with wave gen
-
Yes. and there is. I have already changed the model to 2D15 according to your recommendations. And how can I change this number? Suddenly, in further software updates, the manufacturer will make a check on it.
-
There's no need todo so. Any of these options (Model or HW) matching the wage gen model will enable it.
So you can enable it by changing hw to .001, setting model to 2Dxx, or both.
If you want to change it so badly, use the script from Drive and run it with the script launcher package.
Check the FAQ.
-
Understood. Thanks.
-
Hi all, new soon-to-be owner of a Hantek DSO2C10 here. Active in other hacking communities but never on oscilloscopes.
I have CAREFULLY read all the recommended posts here and on the continuation thread (https://www.eevblog.com/forum/testgear/hantek-dso2x1x-firmware-updates-and-best-use-practices/). I'm posting a question here simply because this one seems more active.
Questions:
1. The latest Hantek firmware on their site is dated 20/4/2021, but user @DavidAlfa lists firmware versions up to 14/7/2021 on his Google Drive repository (https://drive.google.com/drive/folders/1Tqk8YbL_M3S0vtk7h_cZ-01U2idIaqqx). Are these ones similar to that mentioned below? Or are these simply versions found in the wild and submitted by users?
These will overwrite you FW version, so don't apply unless you run the same FW version!
- 20201221 -> Sets FW3000
- 20210510 -> Sets FW3202
- 20210601 -> Sets FW310
2. Are there any changelogs for any of the updates?
3. I gather that there is some user-made firmware out there. The Google drive repo is not helpful here. The continuation thread (https://www.eevblog.com/forum/testgear/hantek-dso2x1x-firmware-updates-and-best-use-practices/) has a section promising note "List here the firmware updates available and recommendations." but has no content yet. Is there such a list?
Thank you for any helpful advice.
-
Hi guys.
So today I received my 2C10 and came with the missing components populated:
[attach=1]
[attach=2]
Board:
[attach=3]
Have anyone who has changed his C10/C15 noticed misbehavior? or anyone have tested if the 150MHz bw it's really there?
-
With DSO2D15 written on the PCBA then you'd hope so! I hope mine arrives with the same.
-
With DSO2D15 written on the PCBA then you'd hope so! I hope mine arrives with the same.
I think that all 4 models share the same board it just hardware arrangement differences, but I don't know if there's a hardware difference to achieve the 150MHz bw.
It be really nice I the C10 can be converted to the D15 ;D
Still, it's a really nice scope for the price.
Hope that your scope also comes with the goodies :-+
-
I see the didn't scratch off the brand on that DAC. Curious they would use such a quality brand part as a Burr-Brown DAC (if it's genuine), especially considering the price point of these scopes. I think Hantek was aiming for a step higher class with these scopes (Undercut the $400 market) , but software and front end held them back so far.
-
Hi.
I have Model DSO2D15
Software 1.0.1.1.0 (20210416.00)
Equipment 000.000.000.000.000.000.000.001
Firmware 3000
Unstable sync
Applied dso3kb_20210714.
Hanging issues disappeared, but not stable signal sync in Falling mode.
Do I need to apply dso3kb_20210630_auto_update_fpga or should I not?
-
There are no changelogs. Let me explain:
User A complains to hantek for specific issue. Hantek sends custom update to the user A.
The update migh or might not solve anything. There's no changelog. Just "Try this" from Hantek.
Then user A sends this update to me and I add it to the list.
All I can say is: Once you made the backup, you can mess with it as much as you want, these things are undestructible.
In the worst case you'll need to recover using platform-tools and restoring your backup.
-
I tested my 2C10 before hacking. After hacking, I did not notice the difference.
-
I tested my 2C10 before hacking. After hacking, I did not notice the difference.
This surely gives us confidence... :-DD
Well, we get what we pay for.
-
Hi all, new soon-to-be owner of a Hantek DSO2C10 here. Active in other hacking communities but never on oscilloscopes.
I have CAREFULLY read all the recommended posts here and on the continuation thread (https://www.eevblog.com/forum/testgear/hantek-dso2x1x-firmware-updates-and-best-use-practices/). I'm posting a question here simply because this one seems more active.
Questions:
1. The latest Hantek firmware on their site is dated 20/4/2021, but user @DavidAlfa lists firmware versions up to 14/7/2021 on his Google Drive repository (https://drive.google.com/drive/folders/1Tqk8YbL_M3S0vtk7h_cZ-01U2idIaqqx). Are these ones similar to that mentioned below? Or are these simply versions found in the wild and submitted by users?
These will overwrite you FW version, so don't apply unless you run the same FW version!
- 20201221 -> Sets FW3000
- 20210510 -> Sets FW3202
- 20210601 -> Sets FW310
2. Are there any changelogs for any of the updates?
3. I gather that there is some user-made firmware out there. The Google drive repo is not helpful here. The continuation thread (https://www.eevblog.com/forum/testgear/hantek-dso2x1x-firmware-updates-and-best-use-practices/) has a section promising note "List here the firmware updates available and recommendations." but has no content yet. Is there such a list?
Thank you for any helpful advice.
1. See DavidAlfa's answer above.
2. No!
3. No, there is basically no list of recommended firmware updates because right now the situation regarding updates is as confusing as it could get. My personal recommendation at this stage and until Hantek really gets its act together, is to keep whatever firmware you get with your DSO. Or if you want to try various updates, you can follow DavidAlfa's guidelines to backup and restore the firmware you got with your scope, but that might just end up being a huge waste of time with little benefit.
Until Hantek publishes a new firmware update and various DSO2X1X owners test it and declare it good to go, I will continue to recommend avoiding any updates. Enjoy your DSO once you receive it and don't worry about updating it for now!
-
Goes to show the issues Hantek is fighting with appear to remains the CPU bound software trying to keep up with the capture engine's timing and status.
I can only imagine where the capture memory buffer is stored. While the GOWIN FPGA can have RAM options, the CPU has plenty more than 8MB available for Buffer Space. Either case there is definitely some improvements to be made between capture memory and display memory timing. Zooming and panning too much seemed to eventually cause display issues, like it lost track of some of the original captured data. This may be have been resolved in more current updates.
-
The CPU is connected to the fpga via spi, so that's a huge bottleneck.
You're limited to the fpga dram memory at normal sampling rates, while only the sram can follow the fastest rates.
I don't think it's a bad scope. It's really good for the money.
It's the software what needs some fixes, mainly in the decoders and trigger detection.
Otherwise it has proven to be very useful.
-
Until Hantek publishes a new firmware update and various DSO2X1X owners test it and declare it good to go, I will continue to recommend avoiding any updates. Enjoy your DSO once you receive it and don't worry about updating it for now!
Thanks for taking the time to answer my questions. I'd still like to try to do the DSO2C10 -> DFSO2D15 conversion (assuming H/W fitted to PCBA) and I think there is just enough info posted to do that update. I'll do my best to process the instructions and come back if I run into trouble.
-
So, for some reason, I was thinking that in order to do the conversion you'll have to get/install a few utils and edit a few files and it turns out that you only need to create a single file with 2 lines :P
I did it and the fungen works now:
[attach=1]
[attach=2]
[attach=3]
[attach=4]
[attach=5]
Test setup it's a bnc-bnc home-made using RG316 wire, length: ~50cm
Love the scope but the fungen seems pretty basic.
Many thanks to all people involved on the hacks/discovery.
-
...
Love the scope but the fungen seems pretty basic.
Many thanks to all people involved on the hacks/discovery.
The function generator in the DSO2X1X scopes is indeed pretty basic and limited, as expected for a $20 option (or free in your case) on a $200 DSO. If you really need a function generator for lab work, a standalone, separate function generator is recommended, and you can get a pretty good one for less than $100 these days. The same applies for the protocol decoders on the DSO2X1X scopes: they are there, but even a $5 USB logic analyzer + sigrok free software do a much, much better job.
https://sigrok.org/
Enjoy your new DSO!
-
current general thoughts on these models? i need a second scope but i dont want to spend as much as my main bench one at the other office. if you have to buy again would you choose this one again? if not what would you look to? i have not bought a scope in a while even my other one is a bit outdated but its built like a tank. this is for a second setup for quick use normally a few times a week. id spend up to maybe 350$ or so of course less is better IF it performs well enough.
-
Hi .rpv, so did you make a USB drive with the dso3kb_do_other_update.upk file and the dso3kb_do_other_update file with your serial number added and preferred model number and HW ID etc? That's how I understand it and hope to try. Did you run the backup-builder first to save the firmware?
-
...
Love the scope but the fungen seems pretty basic.
Many thanks to all people involved on the hacks/discovery.
The function generator in the DSO2X1X scopes is indeed pretty basic and limited, as expected for a $20 option (or free in your case) on a $200 DSO. If you really need a function generator for lab work, a standalone, separate function generator is recommended, and you can get a pretty good one for less than $100 these days. The same applies for the protocol decoders on the DSO2X1X scopes: they are there, but even a $5 USB logic analyzer + sigrok free software do a much, much better job.
https://sigrok.org/
Enjoy your new DSO!
You are right , what I was trying to say it's that hantek loaded the scope with tons of functionality but they leave the fungen with the basics, but that's not saying that it won't be useful, of course, I mean I was using a bare AD9833 module+arduino as a fungen ^-^ and even that was useful, the scope's fungen it's like 1000 times better :-+
I was already really happy with the scope as it is, the free fungen and (maybe) the extra 50MHz bw was just the cherry on the cake ;D
-
Hi .rpv, so did you make a USB drive with the dso3kb_do_other_update.upk file and the dso3kb_do_other_update file with your serial number added and preferred model number and HW ID etc? That's how I understand it and hope to try. Did you run the backup-builder first to save the firmware?
Hi, yes, it's just the uncompressed firmware file on the root of the usb stick with the "do_other_update" file with the 2 lines (https://www.eevblog.com/forum/testgear/hacking-the-dso2x1x/msg3517684/#msg3517684) and that's it, I didn't added any S/N and this didn't change it, for what I understand on the hacking info you may need that for the extra mods not for the conversion to 2D15.
-
current general thoughts on these models? i need a second scope but i dont want to spend as much as my main bench one at the other office. if you have to buy again would you choose this one again? if not what would you look to? i have not bought a scope in a while even my other one is a bit outdated but its built like a tank. this is for a second setup for quick use normally a few times a week. id spend up to maybe 350$ or so of course less is better IF it performs well enough.
You get what you pay for. A $200 scope is never going to be as good as a $350 scope. So if your budget is $350 I would suggest you look at other scopes in that price range.
Just my $0.02.
-
That’s interesting. On the google drive there are some preformed files and an .upk that doesn’t need you to reflash the firmware. That’s the one I plan to try. Good to know that way works too.
-
Yes, I downloaded the firmware from the hantek website and that's what I used, I think that was the same loaded on my scope, I saw the drive but I didn't see anything related to the 2D15 conversion, you should double check what script you'll be using, there are stuff on the drive that's very specific for certain scopes.
-
current general thoughts on these models? i need a second scope but i dont want to spend as much as my main bench one at the other office. if you have to buy again would you choose this one again? if not what would you look to? i have not bought a scope in a while even my other one is a bit outdated but its built like a tank. this is for a second setup for quick use normally a few times a week. id spend up to maybe 350$ or so of course less is better IF it performs well enough.
It depends entirely on what you mean by well enough. I've had my 2D10 for a week now and it works as well as reported here. For basic use it works just fine.
Pro:
I don't think I could have done better for $230 including shipping and UK taxes.
Cons:
The external trigger input is limited to CMOS 0-3.3V ONLY and edge triggering. I've had to use channel 1 or 2 for triggers. The external trigger is nearly useless to me. This effectively costs me a channel.
The protocol decoder is slow.
There is a lot of noise, even at 500mV / div.
If I had the funds, I would have gotten a Siglent SDS1104X-U or X-E but they are double the price or more.
-
You've already successfully done the mod I know, but check out the "Script launcher" and "Scripts" folders under Hantek DSO2x1x -> Mods/Hacking section to see what I mean. I gather that a "do nothing" .upk file was made so that you could update details like this without the need to reflash firmware.
-
You're right, so you only need to execute the dso3kb_do_other_update.upk wih the do_other_update file, still just the two lines, not S/N should be required, that's pretty cool.
If you want to know if you C10 scope came the fungen parts populated without open it out just change the trigger source to external, if the scope has the parts you should hear a relay clicking.
-
If you want to know if you C10 scope came the fungen parts populated without open it out just change the trigger source to external, if the scope has the parts you should hear a relay clicking.
Oh, that's a great tip. Fingers crossed!
-
You've already successfully done the mod I know, but check out the "Script launcher" and "Scripts" folders under Hantek DSO2x1x -> Mods/Hacking section to see what I mean. I gather that a "do nothing" .upk file was made so that you could update details like this without the need to reflash firmware.
That's what "script launcher" does. Read the fu... I mean the FAQ! :D
-
You need to keep up with the conversation. I’m helping another reader do exactly that. While the FAQ needs a lot of work, I read through it and worked it out. It’s nowhere near as clear as it could be though.
-
My oscilloscope arrived last night! I first did your suggested check with the external trigger source setting to hear the relay clicking - and it was there. I then did the quick update that just sets the model name and HW type, keeping my existing serial number and hey presto - I now have a fully functional DSO2D15. Thanks for everyone's help!
-
Added 2D15 conversion package for making it even easier
-
Good job. Here's a link for anyone looking for it https://drive.google.com/drive/folders/1GkQ58OpYthIJsy-mMDN6FkS06qFK5u2J
-
I have get new DSO2D10 A015. As Hantek recommend me I updated it by
dso3kb_20210714
dso3kb_20210601_sets_FW3102.upk
|O They said I wiil get FW 3102 or B102. I have B102 now.
How can I roll back to A015 or update to 3102?
Because I have DC offset in DC/AC coupling for both channels about 40-80mv@1V/div. Calibration do not changed it. Coupling to GND: -400mV@1V/div
PCB: DSO2D15_V1.0 2020.8.17 - is it so bad?
SW: 0.0.1.1.0 (20210714.00)
HW: ...001
FW: B102
-
I guess you didn't read the FAQ.
-
I read "how to do", but there is no A015 version or information about it.
-
Then you must have seen that you should always make a backup? And that backup can restore that among other things?
And that also you're invited to share your fw file if not found on the current fw list, to have a backup of it!
-
I read "how to do", but there is no A015 version or information about it.
I answered you on the 4pda forum.
-
DavidAlfa Agree with you. Instead of this I read almost 27 pages of this topic. My opinion: what you pay is what you get. 150Mhz, 8M, AWG, logic analyzer, and the top is flavored with the buggest "Hantek" logo.
I found reaction to temperature for area around input IC's under metal cover (op amp and "095R AU1A"): offset voltage is changeing.
Sligtly freeze (around zero C): +200mV @ 1V/div
Slightly heat (50-60C): -200mV @ 1V/div
I don't care about vertical position of the line, I can change it with knob, but scope measure voltage level with "Measure" function with absolutely value with offset and it can't be zeroing. That a big problem.
Calibration won't help a lot.
Also without metal cover there are a lot of spikes on signal line that I have read in this topic.
-
I'm curious if There are any significant changes in the front end between v1.0 and the v1.7 Boards to try to adjust for such temperature sensitivity.
v1.0 Front End Posted by Microcheap
https://www.eevblog.com/forum/testgear/new-hantek-dso2x1x-models/msg3515614/#msg3515614 (https://www.eevblog.com/forum/testgear/new-hantek-dso2x1x-models/msg3515614/#msg3515614)
-
DavidAlfa Agree with you. Instead of this I read almost 27 pages of this topic. My opinion: what you pay is what you get. 150Mhz, 8M, AWG, logic analyzer, and the top is flavored with the buggest "Hantek" logo.
I found reaction to temperature for area around input IC's under metal cover (op amp and "095R AU1A"): offset voltage is changeing.
Sligtly freeze (around zero C): +200mV @ 1V/div
Slightly heat (50-60C): -200mV @ 1V/div
I don't care about vertical position of the line, I can change it with knob, but scope measure voltage level with "Measure" function with absolutely value with offset and it can't be zeroing. That a big problem.
Calibration won't help a lot.
Also without metal cover there are a lot of spikes on signal line that I have read in this topic.
Interesting. Could be happening on purpose? That's a really huge offset.
Someone with fw3200, see what's under the analog front-end cover! :D
I still wonder if the 150MHz bw is just marketing bullshit or if there's actually something real.
Might be those caps in the ADC?
Didn't see any proper tests yet.
-
Fun facts: I received DSO2D10 with sticker for "DPO6102B" model on the box. Serial number on sticker is the same as in my system information for DSO2D10.
I waited almost 1 year to buy this model with latest improved PCB version, and they sent me v1.00 PCB with initial bugged FW from their warehouse.
I checked AWG: minimum step is about 2.5mV, "microvolts" fine adjust is fake.
I asked Hantek's Emergency Psychological Support.
They said 5% accuracy for DC offset is very good :D. And their engineers are adjusting hard :scared: to fix very important problem for one of the useful thing in this scope after 1 year: "GND coupling" offset.
For AC/DC coupling offset I calibrated scope to +80mV@1V/div at start up, and this drop to about 0 after 10-15 minutes warming up.
Please wait for the new firmware, be patience, and buy more Hantek. Yet more! :-DD
-
Just a heads up as two Hantek DSO2X1X reviews on YouTube popped up a few days ago:
1. Review/Teardown of a Hantek DSO2D10 Oscilloscope - It Has Builtin AWG, Does Protocol Decoding Too!
Unfortunately the reviewer wastes a lot of time with the AWG and the protocol decoding, which are two of the weakest features of the DSO2X1X series, as already discussed here many times.
Still, a good, informative review:
https://www.youtube.com/watch?v=Mmx7eo9STXE&ab_channel=KerryWong (https://www.youtube.com/watch?v=Mmx7eo9STXE&ab_channel=KerryWong)
2. FNIRSI 1014D vs OWON SDS1104 vs Hantek DSO2D10 ⭐ Entry Level Oscilloscope Showdown!
An interesting comparison of these three "budget" DSOs.
https://www.youtube.com/watch?v=iqfm1pN2Uac&ab_channel=TechCornerTVElectronics%2CProjects%26Tutorials (https://www.youtube.com/watch?v=iqfm1pN2Uac&ab_channel=TechCornerTVElectronics%2CProjects%26Tutorials)
-
The reviewer of the hantek should have read this thread before his tear down. :)
The ADC and FPGA are identified and give far better options then the FNIRSI-1014D. With a price difference of around 25 euro's it should be a no brain-er to go for the hantek DSO2C10, especially since the chance is very high you get the D15 hardware.
FNIRSI-1014D has an 8 bit no DAC AWG. It uses an r-2r network connected to the FPGA to make the AWG signals. It also fails in the sample rate. Only 200Msa/s per channel, if that is even actually used. In the 1013D version I have the feeling it only does 100Msa/s even though there are four ADC in it running at 100Msa/s each. It has two paired per channel, but having studied the software and analyzed a pulse signal I'm not seeing the 5ns resolution.
So with 1Gsa/s for 1 channel and 500Msa/s for 2 channels the hantek wins. Also on the FNIRSI only 30KB of sample memory for both channels. (Label says 240Kb(it))
Hantek should make a tablet version with this hardware. Think it would sell quite good.
-
...
Hantek should make a tablet version with this hardware. Think it would sell quite good.
Before they design a tablet around the same hardware, they should really spend some time fixing the software/firmware. The DSO2X1X hardware has a lot of potential, but it is clearly let down by the numerous bugs in the current software.
-
...
Hantek should make a tablet version with this hardware. Think it would sell quite good.
Before they design a tablet around the same hardware, they should really spend some time fixing the software/firmware. The DSO2X1X hardware has a lot of potential, but it is clearly let down by the numerous bugs in the current software.
Which is the same for a lot of these cheap devices :-DD
Edit: They should open source them. There are enough enthusiast out there willing to fix the bugs :)
-
F*** hantek and their marketing ways.
Buy it now, it's cheap!
Arrives full of bugs...WTF?
Don't worry! We will fix it :-+ (Translation: Maybe in 5 years, or just forget bout it and release a new product).
-
F*** hantek and their marketing ways.
Buy it now, it's cheap!
Arrives full of bugs...WTF?
Don't worry! We will fix it :-+ (Translation: Maybe in 5 years, or just forget bout it and release a new product).
Alternate Translation:
Buy it now, cheap! It has well known bugs but you can work around most of them. Not good enough? Pay 3x more and get a better product from another company.
-
...
Edit: They should open source them. There are enough enthusiast out there willing to fix the bugs :)
Most companies have a very hard time understanding the advantages of open sourcing their hardware and software. In the case of the Hantek DSO2X1X, they would clearly have a large community that they could rely upon to improve the software. And they could keep most of the hardware IP protected. So yes, I would suggest to them to open up the software and enough details about the FPGA operation that the community could start working on improving the product.
As I wrote before, the hardware has a very good potential, but the buggy software/firmware makes these DSOs much less competitive.
If they made the software/firmware open source they would dominate the market for hobby two channel scopes. :-BROKE
-
Alternate Translation:
Buy it now, cheap! It has well known bugs but you can work around most of them. Not good enough? Pay 3x more and get a better product from another company.
I disagree. I have been looking at the range of budget scopes and the difference in price between a Hantek and a Rigol or a Siglent isn't that big. Yes Rigol and Siglent aren't the big boys you are talking about when you say 3x the price but they are not that much more expensive and are less buggy than Hantek's current offerings. The Hantek DSO2C10 is 272 CAD + ~30 in brokerage fees delivered to Canada. The Rigol DS1102Z-E is 314 CAD + 5% tax delivered. The Siglent SDS1102CML+ is 359 + 5% delivered. The difference is even smaller when you consider the Hantek only comes with one probe but the Rigol and the Siglent come with two.
The only thing that keeps Hantek interesting is the DSO2D10 model with it's integrated AWG for just 18 CAD more. If Hantek would open source even just the ARM side of this scope, it would become a lot more interesting. Has anyone dropped the hint to them that this would create an ongoing demand and help them to fix their bugs.
FYI $1 CAD is about $0.80 USD.
-
The Rigol DS1102Z-E (hackable to 200MHz)
Where did you find information about hacking Rigol 1102Z-E up to 200 MHz? It says here https://www.eevblog.com/forum/testgear/rigol-ds1102z-e/75/ (https://www.eevblog.com/forum/testgear/rigol-ds1102z-e/75/) that this is not possible.
-
The Rigol DS1102Z-E (hackable to 200MHz)
Where did you find information about hacking Rigol 1102Z-E up to 200 MHz? It says here https://www.eevblog.com/forum/testgear/rigol-ds1102z-e/75/ (https://www.eevblog.com/forum/testgear/rigol-ds1102z-e/75/) that this is not possible.
I could swear I found that it was possible. My notes are obviously wrong and I have corrected my post. Sorry about that, I have been more focused on the 4 channel models or the Hanteks. Well until I found the two mentioned models and prices I have become less interested in the Hanteks.
-
I agree as well. This is a great DSO for those of us that are electronic "hobbyists". I purchased my Hantek 2D15 a little over a week ago and I have had only one issue. That being the standard, locks-up if you change adjustments to quickly. BIG DEAL to that, I say! Switch a little more slowly and avoid the lock-ups.
Seems too many guys are picking the Hantek 2X1X DSO's apart and trashing it. If they are that pissed or unhappy with theirs, then RETURN it and buy a Tektrronix! Christ ALMIGHTY!
-
Just update it and no more locks!
-
Just update it and no more locks!
I did. I updated it as soon as it did it and, yes......no more locking up.
Not an idiot!
-
Nobody said you were an idiot, but your post suggested to rotate slowly as a workaround, I just told you that updating would fix that! :D
Stupidity and not knowing everything are different things ;)
-
Alternate Translation:
Buy it now, cheap! It has well known bugs but you can work around most of them. Not good enough? Pay 3x more and get a better product from another company.
I disagree. I have been looking at the range of budget scopes and the difference in price between a Hantek and a Rigol or a Siglent isn't that big. Yes Rigol and Siglent aren't the big boys you are talking about when you say 3x the price but they are not that much more expensive and are less buggy than Hantek's current offerings. The Hantek DSO2C10 is 272 CAD + ~30 in brokerage fees delivered to Canada. The Rigol DS1102Z-E is 314 CAD + 5% tax delivered. The Siglent SDS1102CML+ is 359 + 5% delivered. The difference is even smaller when you consider the Hantek only comes with one probe but the Rigol and the Siglent come with two.
The only thing that keeps Hantek interesting is the DSO2D10 model with it's integrated AWG for just 18 CAD more. If Hantek would open source even just the ARM side of this scope, it would become a lot more interesting. Has anyone dropped the hint to them that this would create an ongoing demand and help them to fix their bugs.
FYI $1 CAD is about $0.80 USD.
I did the same and came to a different conclusion -- It may have something to do with market segmentation, variations in exchange rate, import duty and shipping fees.
All Prices including 20% VAT and shipping to my home in North Wales. - Prices in USD
DSO2D10 $230 (Aliexpress seller) I own this one. Need to add the cost of a second probe unless you already have one.
Rigol DS1102E £312 $429
SDS1102CML £319 $439
SDS1202X-E £360 $495
SDS1104X-U £409.20 $562
SDS1104X-E £454.80 $624
Pico 2208B £519.00 $714
Most of the Siglents and the Rigols are from Telonic - a reputable UK reseller. There is value in this, as they have good customer service and will replace a DOA unit.
I would prefer a SDS1104X-? but couldn't justify the expense. The DSO2D10 has been fine so far. I haven't had problems with it crashing. My biggeset complaint is the external trigger is limited to 3.3V logic levels.
-
And the hantek dso2d10 for 189.04 euro. https://nl.banggood.com/Hantek-DSO2D10-Digital-Oscilloscope-2CH+1CH-Digital-Storage-1GS-or-s-Sampling-Rate-100MHz-Bandwidth-Dual-Channel-Economical-Oscilloscope-with-Signal-Source(AWG)-p-1765904.html?cur_warehouse=CZ&rmmds=search (https://nl.banggood.com/Hantek-DSO2D10-Digital-Oscilloscope-2CH+1CH-Digital-Storage-1GS-or-s-Sampling-Rate-100MHz-Bandwidth-Dual-Channel-Economical-Oscilloscope-with-Signal-Source(AWG)-p-1765904.html?cur_warehouse=CZ&rmmds=search)
-
does anyone have recent valid link for the platform_tools, all the previous links have expired.
cheers and thanks
NicW
-
NicW,
You can find it at the end of DavidAlfa's messages in the drive link.
Read the FAQ first
Gyula
-
Hello.
Thank you everyone for this useful thread. I've got a 2D15 and thanks to post #643 I could cross-check that I get more-or-less the same response (IMHO the most interesting is the 10 MHz squarewave). I have updated to the latest official firmware, that is 04-2021, and recalibrated the oscilloscope.
I would like to ask a comparison of what you get when channels are set to GND. In my unit, regardless of the V/div setting, CH1 is about 1/5th of division above 0V and CH2 is about 1/5th of division below 0V. See the attached pictures.
With DC coupling the offset is equally present and impacts DC readings. With AC coupling it goes away.
What kind of GND do you get on yours?
Thanks!
-
Same ***. I recall getting it correctly shown at some point, in one of my 16882312 tests.
Then I lost interest and that was all :-//
-
Hello.
Thank you everyone for this useful thread. I've got a 2D15 and thanks to post #643 I could cross-check that I get more-or-less the same response (IMHO the most interesting is the 10 MHz squarewave). I have updated to the latest official firmware, that is 04-2021, and recalibrated the oscilloscope.
I would like to ask a comparison of what you get when channels are set to GND. In my unit, regardless of the V/div setting, CH1 is about 1/5th of division above 0V and CH2 is about 1/5th of division below 0V. See the attached pictures.
With DC coupling the offset is equally present and impacts DC readings. With AC coupling it goes away.
What kind of GND do you get on yours?
Thanks!
On mine
As it came from Hantek (20210416.00, Firmware 3200), no hacks, no firmware changes and no calibration:
CH1 is 2 5ths above 0V and CH2 is within 1 point of 0V.
The DMM function reads 3.29mV DC for CH1 and 480-500µV for CH2.
(https://i.imgur.com/z736793.png)
Power on for 15 minutes. Disconnect probes, then run internal calibration:
Ch1 is -1.0mVDC Ch2 is 3.05mVDC
Wait 10 minutes, run calibration again.
Ch 1 is 2.95mVDC Ch2 is -1.1mVDC
(https://i.imgur.com/LDmjPWB.png)
Connect probes hooked to front panel ground post. Similar offsets but nearly 500mV p-p noise.
Connect probes to 2.5000VDC reference. Set vertical to 1V/div. Internal DMM - Ch1 2.47VDC Ch2 2.52VDC. Traces are within 1 line width of each other. I let it run for several minutes. No change.
(https://i.imgur.com/FGTmYad.png)
-
TLDR; Good enough for me. I let mine sit on the 2.5V ref for about 30 minutes and did not see any drift.
-
I agree. I absolutely LOVE my 2D15.
It's my first DSO and I am very happy with it.
-
I got this
[attachimg=1]
[attachimg=2]
[attachimg=3]
[attachimg=4]
I did the calibration process a few days ago, I let it sit for about 30minutes (the manual says that you have to wait 20mins) and then launched the calibration process.
For this test I just turn the scope and did the test... I didn't wait anything.
The scope it's a 2C10 converted into a 2D15 (again... thanks forum!).
My channel 2 seems to have a considerable offset.
Still pretty happy with it.
-
Caught same thing with own scope (2c10->2d15), the visual level of traces did not change in all ranges, and measured voltage changed proportionally.
P.S thanks everyone for hacks and other useful information.
-
Hello,
I reviewed the information on the DSO2x1x topic and found some discrepancies. For PC programs, DSO2000 v1.0.1 is included in the v1.0.3 package. I also found v1.0.0.1 from Arbitary Function Generator - Wave Editor.
All of these were made in 2017, hasn’t changed since then?
Anyone who would now install the IOLibSuite_17_2_20605_2.exe required for operation on their PC or the IOLibSuite_18_2_27115.exe currently available for download from the website can use any of them.
It is advisable to install as an administrator.
Anyone who just bought like me - don’t look for the Warranty in the package. I think because the product travels in one direction and the cost of returning it to the manufacturer is very high i.e. not economical.
Thanks for the selflessly published information that helps users get to know the product better.
-
Probably all Hantek scopes use the protocol, so the computer software works with all.
-
Hi everyone! This is my first post on the forum (hope not posting in the wrong one). I also took the chance with the DSO2D10 and was quite impressed the first few minutes until I managed to lock it by changing the vertical pos of CH1?. When I realized that this is perfectly repeatable and reading this forum I decided to cautiously apply some of the update packages, then tried all, ending up with DC random offset and calibration error. Took a deep breath and then gave it a try with the platform tools. Got the same issue as some of you here the scope stopping after reboot at the second screen. Have repeated the process several times without being able to pass by the stop after reboot. Have tried other PC-s and USB 3 & 2 with the same result. Everything works as described in the docx, until the first command in cmds.bat, "sunxi-fel uboot images/uboot_fb.bin". sunxi-fel responds to all commands (ver, dump, etc) if run before the cmds.bat. When executing cmds.bat, it replies first "ERROR: Allwinner USB FEL device not found!" - the following fastboot commands will execute with no issues, including the reboot. If after restart I run directly the cmds.bat without first running sunxi-fel uboot images/uboot_fastboot.bin, the commands will throw error directly or after a couple of rows. PhoenixSuit is installed, the scope is showing up as an android bootloader interface as described in the doc. So I am at a loss with a scope that I am not able to restore.. :( (sadly, I have no backup, but have the information of initial SW/FW). Any suggestions?
-
nemos58
https://www.eevblog.com/forum/testgear/hantek-dso2x1x-firmware-updates-and-best-use-practices/ (https://www.eevblog.com/forum/testgear/hantek-dso2x1x-firmware-updates-and-best-use-practices/)
-
First of all, make a backup using Backup Builder.
This is what it seems to work best:
- If you have FW3200, update to 3202, install 20210714 update.
- If you have FW3000, update to 3102, install 20210416 update.
After updating, remove all probes, let the scope to warm up for 15-20minutes, and run offset calibration.
-
I noticed the user manual has been updated. Creation date is:
9/3/2021, 4:00:18 AM
I don't see any update notes or version references, just thought I'd mention it.
http://hantek.com/products/detail/17182 (http://hantek.com/products/detail/17182)
-
run offset calibration.
Is this in the Utility Calibration or is there another calibration process specifically for offsets?
Thanks!
-
When you go to utility menu, you have offset and amplitude calibration entries.
Amplitude calibration is simply useless, it doesn't work, so run only offset calibration.
-
Algoma wrote this earlier:
"Yes my DSO2D15 has 1Gsps in single channel mode, Answered my own question.
1) Set Display set to Dots to show sample points
2) Capture Single Sequence at 100ns / Div (Less than this, and it shows vectors instead of dots when you zoom in)
3) Zoom in and check the sample dots at 2ns/div
500Msps has sample period of 2ns (One dot per Divsion when viewed at 2ns/div)
1Gsps has a sample period of 1ns (Two dots per division when viewed at 2ns/div)
Must be the ADC08D500 in there."
my question is that a DSO2C10 after changing to DSO2D15 or DSO2C15 has it 1Gbps samping rate or how could I know it before I buy one? As I read the DSO2C10 could not generate signal as it has not some parts soldered on the board, am I right?
-
I read both threads about the Hantek DSO2xxx and some people state that the newer C10 models come with fully stocked D15 PCB. I bought the D10 since it was on sale, but it also has the D15 PCB. So it is a gamble. Buy the ~25-35 euro cheaper C10 with the risk it does not have the components.
-
I would say the hardware is likely the same for all versions, only limited by software (At this time).
Its the extra Signal Generator components being included on the lower cost models that is a gamble. Likely they're shifting stock of already completed PCBs to meet demand for the lower cost models. In the future those extra Signal Generator components will be less likely to get on the DSO2C10.
-
When you go to utility menu, you have offset and amplitude calibration entries.
Amplitude calibration is simply useless, it doesn't work, so run only offset calibration.
Fascinating. Mine has only a single Calibration entry in the utility menu. SW 20210814, FW 3202. It is F1 on the second page of the utility menu. It seems to run three passes. The first adjusts both Ch1 and Ch2 volts per division from 10V to 2mV in 12 steps. Then the same for Ch1 alone, then Ch2 alone. Takes about 2 minutes total. No idea what it is actually doing.
-
So does mine and I am on SW 202104xx and FW 3000
-
Hi.
Hantek finaly have new firmware. Onyone tested it?
http://www.hantek.com/uploadpic/hantek/files/20210915/dso3kb_20210630_auto_update_fpga.zip (http://www.hantek.com/uploadpic/hantek/files/20210915/dso3kb_20210630_auto_update_fpga.zip)
Tomi
-
Ok - not bricked. So one + for Hantek. :-\
-
Ok - not bricked. So one + for Hantek. :-\
Is that before and after you tried the update?
-
New software?
http://hantek.com/uploadpic/hantek/files/20210915/HantekDSO2000_Ver1.0.3.zip (http://hantek.com/uploadpic/hantek/files/20210915/HantekDSO2000_Ver1.0.3.zip)
-
This serial? I never make update exept from hantek web. I'm fink I lost serial when my DS hang and I try to reboot him, but again it hang whitin seconds. That was a two months or something...
-
"New software?
http://hantek.com/uploadpic/hantek/files/20210915/HantekDSO2000_Ver1.0.3.zip (http://hantek.com/uploadpic/hantek/files/20210915/HantekDSO2000_Ver1.0.3.zip)"
This package has just been relabelled.
What is included corresponds to version 1.0.1.
So nothing new.
I have previously installed this (HantekDSO2000_Ver1.0.3 \ DSO2DXX.EXE dated 25.03.2021)
-
Instead trusting a simple version number, check if they binaties are different by computing the md5sum.
We already had the 20210630... So nothing new.
-
Strange.
In fact nothing (in version nomber) was change. This is old firmvare? I don't look in that screen exactly.
-
Because that update only changes the fpga firmware. That's the number you see in FWxxxx (ex. FW3000)
-
OK - but WHY i have out of the box? |O |O |O
-
No worries. Update it and done!
-
Hi!! I have a 2c10 and as soon as I received it i "hack" it to, following davidalfa method for turning into a 2d15 to see mainly If I had wave gen componentes placed in. But no. Now a few months later I bought a rigol dg811 wavegen and I want to restore the state of my scope at its original statee. Return to 2c10.
How can I do it??
-
I gues you didn't made a backup... Then with "edit model" script, and script launcher.
-
They've updated the software and firmware listings again. They got a rookie working over there?
http://hantek.com/uploadpic/hantek/files/20210916/HantekDSO2000_Ver1.0.3.zip (http://hantek.com/uploadpic/hantek/files/20210916/HantekDSO2000_Ver1.0.3.zip)
http://hantek.com/uploadpic/hantek/files/20210916/dso3kb_20210714.zip (http://hantek.com/uploadpic/hantek/files/20210916/dso3kb_20210714.zip)
The firmware matches the 0714 posted previously.
The software matches the 103 posted previously.
Nothing to see here!
-
Someone could have already published the multi-referenced 1.0.3 because the one just published is still 1.0.1.
It would be nice if you check what you publish before publishing.
http://ha3hz.hu/images/ScreenHunter_02 Sep. 16 21.45.jpg (http://ha3hz.hu/images/ScreenHunter_02 Sep. 16 21.45.jpg)
-
Someone could have already published the multi-referenced 1.0.3 because the one just published is still 1.0.1.
It would be nice if you check what you publish before publishing.
I already checked and posted as such but thank you for the valuable information.
-
I agree as well. This is a great DSO for those of us that are electronic "hobbyists". I purchased my Hantek 2D15 a little over a week ago and I have had only one issue. That being the standard, locks-up if you change adjustments to quickly. BIG DEAL to that, I say! Switch a little more slowly and avoid the lock-ups.
Seems too many guys are picking the Hantek 2X1X DSO's apart and trashing it. If they are that pissed or unhappy with theirs, then RETURN it and buy a Tektrronix! Christ ALMIGHTY!
Patrick, your absolutely right this is great little scope for the monies.
But the lockup is problem for me is big issue as i don't like having to power cycle electronics, too many times stuff has not powered up again. :-(
Dave's reboot fix is a really good contribution and for me pretty much settles this issues, one day when not so busy i'll try the OC as it seems to help to.
As for returning it I tried but post back to Banggood in China was £100 and only paid £175 for it.
Ok they may refund the postage when received and sorted.
But many returns seem to go unclaimed in China customs, hence you are now £300 in the hole and no scope :-)
That said, local Amazon returns seem to result in a better resolution, I guess you save a few bucks here and loses a few there.
I have installed 0630 and then 0705 and after recal i think is unbeatable for the monies, MUCH MORE function than my trusty Tek 2236 :-)
Little is disappointed that 210916 is just a rehash of what we already have, maybe Santa Claus will bring an all bugs fixed release :-)
Enjoy your DSO2xxxx, imk
-
Lockups are mostly gone after updating (run 210416 and 210630-auto_update_fpga).
So just update it and stop crying :D
-
Lockups are mostly gone after updating (run 210416 and 210630-auto_update_fpga).
So just update it and stop crying :D
Don't tell me to stop crying, idiot!
This is about expectation of good reliable quality as you can never know the results of failure.
One project I was involved in years ago was doomed to failure because of it's poor design, I told them not to do it, but was ignored.
The night it failed it almost cost 600 people their lives!
Ask the relatives and loved ones of the NASA Challenger tragedy and Boeing Max 8 flights etc. what they think about poor design and testing
I hope the car you drive has well designed and tested breaks and steering!
Suddenly I have ZERO respect for the words you write and any work you.
Grow and get real Dave.
imk
-
I see someone can't take mild jokes :-DD
Comparing a cheap DSO (targetted for hobby use) with space/critical care equipment is a bit out of context, isn't it?
The day I see Hantek anywhere in a plane, I'll jump right away. It'll be safer!
-
Comparing a cheap DSO (targetted for hobby use) with space/critical care equipment is a bit out of context, isn't it?
Good point David. Bringing NASA into a subject related to Hantek is ludicrous.
-
Hello Guys,
I just received the DSO2C10 from Banggood. It cost me 180,3USD
FW 3202
Software: 1.0.1.1.0(20210726.00)
I made a backup.
I upgraded to DSO2D15 and et voilá -> the function generator WORKING!!!
Meanwhile I ordered the 3 parts to solder onto the board from Farnell, but they didn't ship it yet, so I cancel the order ;D
******************
"Yes my DSO2D15 has 1Gsps in single channel mode, Answered my own question.
1) Set Display set to Dots to show sample points
2) Capture Single Sequence at 100ns / Div (Less than this, and it shows vectors instead of dots when you zoom in)
3) Zoom in and check the sample dots at 2ns/div
500Msps has sample period of 2ns (One dot per Divsion when viewed at 2ns/div)
1Gsps has a sample period of 1ns (Two dots per division when viewed at 2ns/div)
Must be the ADC08D500 in there."
-
I still question the ADC model I wrote as a guess. While its the right pinout, feature and value seems to match, and the CIYB that wasn't scratched off on the end of the part number is also a match. But the cost alone for a single chip of this model from any supplier I can find, is generally nearly the same as this whole scope itself. Even that DAC on the wavegen isn't a cheap part on its own, let alone the LCD, FPGA and every other bit in there... Hantek must be nearly giving these things away at a really thin margin. Hopefully they're getting enough to keep working on the software.
Edit: .. Found the chips for <$60 from a supplier in China. Perhaps there is a cheaper clone version out there.
-
I still question the ADC model I wrote as a guess. While its the right pinout, feature and value seems to match, and the CIYB that wasn't scratched off on the end of the part number is also a match. But the cost alone for a single chip of this model from any supplier I can find, is generally nearly the same as this whole scope itself. Even that DAC on the wavegen isn't a cheap part on its own, let alone the LCD, FPGA and every other bit in there... Hantek must be nearly giving these things away at a really thin margin. Hopefully they're getting enough to keep working on the software.
Edit: .. Found the chips for <$60 from a supplier in China. Perhaps there is a cheaper clone version out there.
Most likely they buy in bulk and get the parts cheaper then what you found.
For the software they should really consider making it open source and let the community do the development. Cheap for them and good for us.
-
Interesting.
If that's really a new sw version, I can extract it from the backup (Use Backup builder) and make a custom update package, stripping your scope unique settings (Serial, calibrations...).
-
Yes. That is what I see, but the real data I don't know.
-
So what about sending me the full backup so I can extract the software from it? :popcorn:
-
sent pms
-
Hello Guys,
I recently purchased DSO2D10, device came with this firmware/software factory installed:
Software: 1.0.1.1.0 (20210416.00)
Hardware: 000.000.000.000.000.000.000.001
Firmware: 3200
of course I had problems with constant freezes of the device and I updated it to the latest firmware:
dso3kb_20210630_auto_update_fpga.upk
dso3kb_20210714.upk
After that, the freezes seem to have disappeared, but I got a problem with the USB ports
Rear USB port activity icon is constantly displayed, and the front USB port is blocked when the device is turned on with the message "Front panel USB lock"
I found out that if I click "Update firmware" without doing the actual update, the front USB will be unlocked, but to do this every time you turn on the device is some kind of stupidity and an obvious bug
I described this situation to Hantek support and they sent me a new firmware: dso3kb_20210816.upk, after the update, software version became 1.0.1.1.0 (20210814.00)
But this firmware did not solve the problems with the USB ports, just the message "Front panel USB lock" disappeared ;D, but the problem itself did not disappear, fantastic bug fixing from Hantek
After contacting the support again and asking them to pay attention to their bug, I received an excellent answer "Regarding the USB ports on the front panel and the rear panel you mentioned, it is normal. We will better improve the function." :palm:
Has anyone encountered a similar problem with ports and can suggest a solution? Unlike Hantek, I do not think that this is normal, although, to be honest, this is a small problem, compared to the rest of Hantek's bugs
-
For the USB bug, use 20210416.
Or go to System menu and hit Update few times.
Can you send me the update?
-
unfortunately if I use 20210416, sometimes I get freezes in "Auto Set" mode, and the new firmware solves this, so I'll have to use the hack with hiting Update
of course I can send an update, sent pm about this
-
sent pms
Thanks. Had a quick look.
Interesting: Pcb=003.002.001.000.000.000.000.000
Never seen that on this models.
-
I guess you have two calibration entries in utility menu: offset and amplitude. Is it so?
This is a known problem. You'll get usually two Calibration entries after using a platform-tools. Sometimes you could get this from Hantek. The last is your case - you've got this from Hantek.
Solution. You need the full backup upk-file from someone who has only one calibration entry in utility menu: offset and the same FW - 3200. I have such backup upk-file but with FW - b000.
Many thanks :-+
Yes, you're right, I have two Calibration entries in utility menu and I've got this from Hantek.
I will try to apply your solution, but I need full backup upk-file from someone who has only one calibration entry in utility menu: offset and the same FW - 3200
Guys, can someone send me such backup? ;)
-
Has anyone encountered a similar problem with ports and can suggest a solution?
The rule of thumb here is: USB will fail if using software made for FW3200 in a FW3000 oscilloscope, and the other way around, also calibration will fail if using the wrong FW for your scope.
Interesting update! USB works great in FW3000/FW3102 and 20210814 software!
Given your's is a FW3200, ensure you have updated to 3202, then try 20210726 I've just extracted and uploaded, which breaks USB for me(mine is FW3000), so it should work for you :D.
As usual, the files are available in my Google Drive "Firmware/Firmware updates" folder.
Updated the FAQ (https://www.eevblog.com/forum/testgear/hantek-dso2x1x-firmware-updates-and-best-use-practices/msg3590160/#msg3590160), enhancing the format, including recent updates, compatibility details and few quick references.
-
Calibration worked flawlessly in my Fw3000 (Fw3102) and 20210814. DC offsets are spot-on in any voltage range.
The interface seems smoother and more responsive, the wave Y position doesn't move at 2FPS in some timebase settings like it did before.
GND coupling still has usual negative offset problem.
-
Given your's is a FW3200, ensure you have updated to 3202, then try 20210726 I've just extracted and uploaded, which breaks USB for me(mine is FW3000), so it should work for you :D.
I have FW3202 and tried 20210726, but unfortunately it didn’t solve the problem with USB :(
by the way, on my FW3202 and 20210814 the calibration didn't break, everything works well, I don't see any new problems yet, except for USB
USB only works properly with 20210416
-
blackbile has the FW 3200. His full update upk-file you can download from David Disk as zip-file. The only thing you need is a password for this zip-file. Ask him to tell you the password and you can try to solve the problem with USB. Don't forget to make a full backup before you change anything.
Thanks! will do it.
-
New mod available, "USB fix".
I made a very small script that polls the pin which detects the presence of external power at the rear port.
Once a second, it checks the value and switches the controller between host and peripheral modes.
Of course, it takes care of the signal, ensuring it's not a noise.
For me, it works great. No issues so far. Like it should have been for all this time.
No longer needed. Uninstall the mod and check this (https://www.eevblog.com/forum/index.php?topic=257914.msg3710809#msg3710809).
-
New mod available, "USB fix".
I made a very small script that polls the pin which detects the presence of external power at the rear port.
Thanks David for what you are doing :-+
In the meantime, I continued my communication with Hantek and they sent me a small. upk file with a fix for the USB problem
I ran it on my device FW3202 and 20210814 and it really fixed the USB, and yes, after this update, I now have one calibration entry in utility menu instead of two, as it was before ;D
I will send pm to you with this update so that you can upload this file to your disk, maybe it will be useful to someone who also has problems with the USB
-
Interesting. The problem comes from the file /dso/app/Square_cusp.tmp.
Deleting that file completely fixes USB for me, too.
Not even need to restart, the changes are applied instantly, Phoenix is constantly checking for it.
When present, the usb is forced to be in peripheral mode, and the weird calibration menu appears.
Deleting it instantly restores the normal menu and usb behavior.
The strange thing is that it came from nowhere. Some updates include that file, but they don't copy it.
So where did it came from? Is it self-generated under certains conditions?
Why are older software versions unaffected by this file?
Maybe it was there from the beginning (This begins to seem an Alien movie :D) and then they added a new "feature"?
So the software compatibility war is over. Any update should work now after applying this.
In the worst case, the FW version will change, requiring to be restored, but as every update is documented in the FAQ, there won't be any problem.
Added the file to the system updates section. Since it's not a software update, I renamed it to usb_fix to avoid confusion.
-
I know it's empty, it's just a test file. There's code inside Phoenix that checks if exists and proceeds with a different path if detected, but doesn't read its contents.
Dang! Was caused by platform-tools then! I missed that possibility. Now everything makes sense.
-
Does one need to use this fix when upgrading to the latest upk EVEN if he has never used platform tools?
-
If the USB works correctly, you don't need to.
In any case, it won't cause any harm.
-
That's what the USB fix does, why complicate it so much?
Run the upk and done :-//
If the file isn't there, then there's nothing to delete.
In any case, if you want to do it manually, do it in one operation:
if [ -f /dso/app/Square_cusp.tmp ]; then
rm -rf /dso/app/Square_cusp.tmp
if [ $? -eq 0 ]; then
echo "Succesfully deleted Square_cusp.tmp" >/mnt/udisk/log.txt
else
echo "An error ocurred while deleting Square_cusp.tmp" >/mnt/udisk/log.txt
fi
else
echo "The file Square_cusp.tmp was not found in the system" >/mnt/udisk/log.txt
fi
-
Another step forward thanks to great work of DavidAlfa, thank you! Is there any possibility for activation of some hidden features, i dream about Bode plot, it is shame to have internal generator and not have a Bode plot.
-
Give them to @hcp, who complained to Hantek and received the fix ;D
I'm not hacking this thing anymore, only quick checks, maintaining the FAQ, testing new updates and such.
-
Vistorik, are you Vitroks in 4PDA?
21.08.16 and USB fix (Was called 21.09.25, I renamed it because it's not a software update) came from Hantek, not done by me.
The only "custom" version is 21.07.26 extracted from the user backup, copies exactly the same files as other updates.
Backup builder is safe, it's extensively tested (Although I'll never take any responsability), I've flashed my scope 100s of times, completely erased the flash, restored with any platform-tools and then ran the backup, it worked every time.
There's no need of take the risk of damaging something by desoldering the flash, also you'll void the warranty.
In the other hand, using their own tools (platform-tools) shouldn't, the backup restores the original files, so it's like factory.
Some people said that the flash contents changed after restoring: It's a live system. Everytime it boots it'll change some files in the flash. The system uses flash wear leveling algorithm, so every change will be written into a different place.
So you'll never get the same data if the system was booted between one flash dump and another.
Every scope seems to exit the factory with different software, I doubt they even know what's going on :-DD.
-
21.08.16 and USB fix (Was called 21.09.25, I renamed it because it's not a software update) came from Hantek, not done by me.
Yes, I can confirm that 21.08.16 and USB fix on David's disk are the original and unmodified files that were received from Hantek, without modifications, "as is" :D
-
So you needed confirmation? Why the mistrust?
Isn't enough if I say that a package is unmodified? What the hell?
Who ever uses "RUN" to execute scripts?
You use "./extract.sh" or "sh extract.sh"
Also, all update are already extracted, check "Decrypted" folder.
I don't understand why you keep complicating things, running the upk does exactly the same, but you keep insisting in doing via the script method.
The upks are cleaner, safer, and integrity protected, it will be aborted if the file is corrupted.
Meanwhile, a single symbol in the wrong place of the script can cause a lot of trouble.
-
So, DavidAlfa, after running on my device DSO2C10 packages dso3bk_backup_buider.upk, dso3kb_fix_generator.upk, dso3kb_2D15_conversion.upk, dso3kb_CNXXXXXXXXX.upk and dso3kb_CNXXXXXXXXX_FULL.upk the device screen becomes black, but the device does not reboot and remains constantly in this state, regardless of whether the flash drive remains in the device or I take it out (see the photo). After that, the device must be turned off and on again, then it starts working again. I tested my device on versions 416 and 816, FW b000. The issue I have found I guess is connected with the firmware like that hcp has, that has the USB-port problem. After running dso3kb_usb_fix.upk the reboot-issue is not disappeared. I have not the firmware from hcp, but I've tested the device with the similar firmware from one guy in 4PDA. So with such firmware the reboot command does not work. With my native firmware I have not this issue. interesting: whether hcp has this issue.
-
and why did you run all of the upk files?
-
The firmware from HCP hasn't any usb problem, it comes from platform-tools firmware having a file that shouldn't be there.
Any software version later than 21.04.16 causes the usb issue if the file is present.
So your device does never reboot by itself? That's weird. Never seen that.
Maybe that's why Hantek never reboots after the updates, they might have had issues?
If the screen turned off, then it clearly stopped most functions, but something happened in the last instance.
You would need to access the serial console to see the error.
I would run platform-tool to wipe the filesystem, restore your backup, run usb fix (Remember, the usb still works, you only need to push several times the update button), and update to the latest software.
-
The firmware from HCP hasn't any usb problem, it comes from platform-tools firmware having a file that shouldn't be there.
Any software version later than 21.04.16 causes the usb issue if the file is present.
So your device does never reboot by itself? That's weird. Never seen that.
Maybe that's why Hantek never reboots after the updates, they might have had issues?
If the screen turned off, then it clearly stopped most functions, but something happened in the last instance.
You would need to access the serial console to see the error.
I would run platform-tool to wipe the filesystem, restore your backup, run usb fix (Remember, the usb still works, you only need to push several times the update button), and update to the latest software.
Posted by: hcp
« on: September 24, 2021, 12:50:45 pm »
Hello Guys,
I recently purchased DSO2D10, device came with this firmware/software factory installed:
Software: 1.0.1.1.0 (20210416.00)
Hardware: 000.000.000.000.000.000.000.001
Firmware: 3200
of course I had problems with constant freezes of the device and I updated it to the latest firmware:
dso3kb_20210630_auto_update_fpga.upk
dso3kb_20210714.upk
After that, the freezes seem to have disappeared, but I got a problem with the USB ports.
The auto-reboot problem in scripts is definitely related to the firmware that initially had problems with the usb port. I checked this on the original dump of one of the 4PDA forum participants. With this original damp flashed to the memory chip I made a full backup (during this there was already a auto-reboot problem), completely erased the memory chip, ran the platform-tool and ran the full-backup upk-file. After that the problem with the auto-reboot in scripts disappeared. So, thank you very much David for this solution.
-
and why did you run all of the upk files?
I am learning to write scripts for upk packages because I completely agree with David's opinion that it is much more convenient and save. I wanted to create a upk-package with a script that would allow changing the model number not only to 2D15 but also to any other of the four, because sometimes after changing the number to 2D15 there is a need to restore the original model number. I used David's dso3kb_2D15_conversion.upk package script as an example. In my script, I left at the end of the script the reboot command, which was also in David's script and which, as I understand it, should reboot the device after the upk-package was executed. And faced the described situation. I could not understand what I was doing wrong and decided to check it on some of upk-packages of David which also have the reboot command, and I saw the same situation. Then I realized that I was running all this upk-packages on the firmware that initially had a problem with the USB-port and I decided to check the execution of these packages on my firmware, which initially had not USB-port problem, and I saw that this auto-reboot problem was not on it. So it became clear that this auto-reboot problem by executing the reboot command in scripts was in the firmware.
-
Is there something you didn't understood yet about the presence of that file and software versions newer than 210416? Hcp had the problem because it was probably updated using platform-tools by the seller or someone else.
The reboot comand has worked always, no matter if the USB problem was present or not.
Try "reboot -f"
You keep complicating things. Restoring the backup will also restore the model and serial number.
That'w why there're two backups types, one overwriting the software version and the other preserving it.
-
Hcp had the problem because it was probably updated using platform-tools by the seller or someone else.
The reboot comand has worked always, no matter if the USB problem was present or not.
Immediately after restoring the system using the platform-tools, there are no problems with auto-reboot. How the factory firmware that causes this problem was obtained by Hantek, I do not know. In this firmware (SW version 0.0.1.1.0(20210311.00, FW b000) there are 2 problems, one is usb (caused by the file Square_cusp.tmp) and the second is auto-reboot. The usb problem may be related to the seller's using of the platform-tools, the auto-reboot problem is not related with using of the platform-tools. After removing the file Square_cusp.tmp the auto-reboot problem still remains. The question is how to fix this problem without using platform-tools. If you want I could send you the damp of this firmware.
-
Maybe some file was damaged in your system.
Why don't you just run platform-tools and then restore your backup?
It will refresh everything, wipe de data, create and format the partitions... it's the best way to clean up problems.
Sorry, but I'm not going to spend days finding what could be wrong, when it has such easy solution...
-
Hcp had the problem because it was probably updated using platform-tools by the seller or someone else.
I don't think the seller or someone else used the platform-tools. I bought my scope not from an Aliexpress/Banggood seller or similar, but from a big Polish supplier of electronic components, it is a large company that supplies all kinds of electronics to many European countries and I don't believe that they waste time flashing cheap oscilloscopes ;D
Most likely it comes from the Hantek factories, where I suspect a complete mess with firmware and software in general.
-
Oh, Aliexpress sellers do that a lot.
Ex. A lot of Xiaomi phones were shipped with modified fw, adding malware, ads... And disabled OTA so it would stay like that forever.
-
Hcp had the problem because it was probably updated using platform-tools by the seller or someone else.
I don't think the seller or someone else used the platform-tools. I bought my scope not from an Aliexpress/Banggood seller or similar, but from a big Polish supplier of electronic components, it is a large company that supplies all kinds of electronics to many European countries and I don't believe that they waste time flashing cheap oscilloscopes ;D
Most likely it comes from the Hantek factories, where I suspect a complete mess with firmware and software in general.
When you did not change the model number of your device from 2D10 to 2D15 could you please try to do it using the dso3kb_2D15_conversion.upk and say if there is the auto-reboot problem with black display? Thanks.
-
Interesting: the generator starts to work if change the model number from 2C10 to 2C15 - see the photo. Is it known? I used the dso3kb_2D15_conversion.upk with changed sed command:
sed -i "s/Model=.*/Model=DSO2C15/g" /cache/system.inf /dso/app/sys_inf.new
-
Did you change the Hardware number? 001 means generator present, and will work in any model.
Original "C" models have HW version .000
So you can enable the generator in both ways.
-
When you did not change the model number of your device from 2D10 to 2D15 could you please try to do it using the dso3kb_2D15_conversion.upk and say if there is the auto-reboot problem with black display? Thanks.
Sorry, I would not like to do any experiments with my device now, since I am using it intensively right now and I definitely need it on the weekend :D
So even the smallest probability of getting problems is not acceptable to me.
-
I noticed something weird: The smallest X step is 8 ns?
In <100ns modes this is very noticeable. Specially in 2ns, where it jumps 4 divisions!
Is it like that or did I mess something up?
-
Did you change the Hardware number? 001 means generator present, and will work in any model.
Original "C" models have HW version .000
So you can enable the generator in both ways.
Yes, you are absolutely right. 2C10 with HW .001 has generator. I did not know this. And changing the model number only to 2D15 without changing HW number from .000 to .001 - 2D15 with HW .000 also enable generator. So to enable generator on 2CXX devices it's enough to change model number to 2D15 or to change HW number to .001. Thanks.
-
Another weird thing: 55 dots / division at 2ns.
That's 25GSps, something went crazy here!
-
Another weird thing: 55 dots / division at 2ns.
That's 25GSps, something went crazy here!
Perfectly normal for a Run/Stop capture. Try a Dot mode Single shot if you really want to see what's going on.
-
That was a single shot...
-
That was a single shot...
So what does a capture slow and then zoom in show ?
Here's a couple from a SDS1104X-E.
-
Hi guys, new to the forum. I'm in the market for an O-scope mainly for NTSC analog video. I wanted to see how the Hantek performs in this regard, displaying a CVBS signal. I want to see how good the resolution is in displaying it for noise issues and such. Thank You in advance.
-
Another weird thing: 55 dots / division at 2ns.
That's 25GSps, something went crazy here!
I think all is ok, except strange shift of waveform to the right from trigger position.
-
When you did not change the model number of your device from 2D10 to 2D15 could you please try to do it using the dso3kb_2D15_conversion.upk and say if there is the auto-reboot problem with black display? Thanks.
Sorry, I would not like to do any experiments with my device now, since I am using it intensively right now and I definitely need it on the weekend :D
So even the smallest probability of getting problems is not acceptable to me.
I understand. I send you a package dso3kb_reboot.upk which script has only one command - reboot
#!/bin/sh
reboot
This package does nothing - only reboots device. if you find a couple of minutes and run this package I would be very grateful to you.
-
Reboots correctly, as expected.
-
I think all is ok, except strange shift of waveform to the right from trigger position.
Yeah, mine was like, then at some point something weird happened. As you see it shows 25x more dots.
What about the 8ns steps when moving the Horizontal position? Does yours move in ~1 pixel steps?
-
Reboots correctly, as expected.
I would be happy to hear the same from hcp.
-
My device reboots correctly with dso3kb_reboot.upk :)
-
My device reboots correctly with dso3kb_reboot.upk :)
Thanks a lot.
-
Yeah, mine was like, then at some point something weird happened. As you see it shows 25x more dots.
What about the 8ns steps when moving the Horizontal position? Does yours move in ~1 pixel steps?
Yes, looks like minimal X step is really equal to 8ns..
Another question: what means"Realtime" and "Equ-time" option in dso2x1x? In many attepmts to use "Equ-Time" I found that it makes.. nothing. :o
-
No idea, I also asked that myself when I got the dso, but the manual doesn't say a word about it.
-
Another question: what means"Realtime" and "Equ-time" option in dso2x1x? In many attepmts to use "Equ-Time" I found that it makes.. nothing. :o
Interesting. Equivalent time sampling would mean phase shifting the sample moment over time to obtain a higher sample rate. Only works on repetitive signals. In this case of the Hantek hardware the question is if the FPGA is capable of making a small enough phase shift to make it worth while. With the max sample rate being 1GHz the phase shift needs to be in the order of 100 pico second range to make it usable. All depends on the PLL's and the speed of the interconnect fabric in the FPGA if this is possible. The external clock is most likely 50MHz, so the PLL has to crank this way up.
-
In the end I decided to make something with the unused Ethernet port.
-
I tried to run the Phoenix binary from another hantek model (4072C I think).
As expected, lots of errors happened, but it had enough time to wipe my eeprom.
Luckly I had a backup. In any case, I made a new package, "Eeprom backup".
It's similar to Backup builder, packs the required binaries and builds a restore package to make it simple.
Also added compiled i2c-tools and eeprog to the binaries section.
-
Signal generator square wave - is it normal ???
-
Signal generator square wave - is it normal ???
Well, "normal" depends on your measurement setup. Can you show a picture of it, and the specs of the probe?
See this thread I started on that subject https://www.eevblog.com/forum/programming/oscilloscope-bandwidth-simulated-with-octavematlab/ (https://www.eevblog.com/forum/programming/oscilloscope-bandwidth-simulated-with-octavematlab/). It ended that I understood few important things about DSO and high-frequency measurements (and other about simulations).
Last but not least, I am building a 1 ns rise-time test generator 8) (according to the chip datasheet, an ICS512 that popped out a small drawer). BTW, ideas for a faster DIY rise-time test generator are welcome.
Paolo
-
David, I send you FW b101 to update the list. This FW I've got from Hantek platform-tools. Thanks.
-
bxxx firmwares are the same as 3xxx.
Ex. b000=3000, b101=3101. 3102 will probably show b102.
This must be something related to the fpga itself.
Today I was fighting with the SPI decoder, which decided to not work under any circumstances. Finally, I found it to only work at 5V/div.
Not really a problem, but HANTEK COULD TELL THAT in their manual so we don't lose hours figuring out how to make it work.
-
3102 will probably show b102.
Yes, 3102 shows b102. Initially b000. Calibration OK.
-
Yep. Clearly, there're 2 FPGA types.
Copied from my FAQ, these are equivalent:
» 2013_A013
» 2015_A015
» 3000_B000
» 3101_B101
» 3102_B102
» 3200_B200
» 3202_B202
-
Yep. Clearly, there're 2 FPGA types.
Copied from my FAQ, these are equivalent:
» 2013_A013
» 2015_A015
» 3000_B000
» 3101_B101
» 3102_B102
» 3200_B200
» 3202_B202
If I change initial b000 to 3200 or to 3202 I've got b200 or b202 and calibration error. Only 3000, 3101 and 3102 - b000, b101 and b102 are without calibration error.
-
Yes, 320x versions are only for models coming with that version from factory.
Read the FAQ.
-
I am confused. So what is the difference between 3000, 3101 and 3102?
-
I think they're updates, like 3200 and 3202
-
OK. Are the 31xx upgrades to the 3000 or does it not matter?
For sure changing the 3000 to 3200 causes calibration to fail at the very least.
-
There is a chance to get an reply and possibly some major bugs to be fixed, if more people report them on this almost official hantek forum:
https://www.eediscuss.com/forum.php?mod=forumdisplay&fid=44&page=1 (https://www.eediscuss.com/forum.php?mod=forumdisplay&fid=44&page=1)
-
LZ4TU,
Interestingly, they also link to this blog, so read on.
Gyula HA3HZ
-
in Follow-up to the SoC (AllWinner F1C200s) in these scopes.. Looks like a few potential alternate dev boards to test things with, and perhaps find better Documentation:
Another F1C200s Development board, (Other than the Lichee Pi Nano from Seeed Studio that I've found stocked at Digikey,)
MongoPi-R3 Development Board
https://www.dfrobot.com/product-2274.html (https://www.dfrobot.com/product-2274.html)
Includes an well documented Wiki of related tools and procedures that may be useful for poking deeper into these F1C200s.
https://wiki.dfrobot.com/MangoPi_R3_SKU_DFR0780 (https://wiki.dfrobot.com/MangoPi_R3_SKU_DFR0780)
-
Found them on aliexpress too:
https://nl.aliexpress.com/item/1005002570534332.html (https://nl.aliexpress.com/item/1005002570534332.html)
https://nl.aliexpress.com/item/1005002527296059.html (https://nl.aliexpress.com/item/1005002527296059.html)
Shipping and tax raises the price, compared to what I paid for my lichee nano's. (Back in may, so no vat, euro 7.38)
https://nl.aliexpress.com/item/4001150568609.html (https://nl.aliexpress.com/item/4001150568609.html) But euro 12,37 now :o
Means about 7 euros for the extra 32MB of ram.
-
hello, can anyone tell me what's the "waveform refresh rate" (wfms/s) of these oscilloscopes?
Thank you
-
In the Manual, Page 62:
"Acquisition Rate, typical: Up to 2000 waveform per second per channel (Normal acquisition mode, no measurement)"
Its limited by the CPU's interface with the FPGA, pretty typical of an entry level scope. Only issue it might miss triggering on short duration, intermittent, transient signals if you're troubleshooting for some rare, specific event. Certainly if you're troubleshooting for such issues, you'll want a higher end scope with more wfms/s.. I feel 2K has been plenty for my basic use needs, certainly well faster than what it can display on screen.
-
In the Manual, Page 62:
"Acquisition Rate, typical: Up to 2000 waveform per second per channel (Normal acquisition mode, no measurement)"
The manual I downloaded doesn't have page 62, that's why I couldn't find it. Downloaded the complete manual now from hantek. Thank you for the info :-+
... it might miss triggering on short duration, intermittent, transient signals if you're troubleshooting for some rare, specific event. Certainly if you're troubleshooting for such issues, you'll want a higher end scope with more wfms/s..
That's exactly what I need it for to capture short duration, intermittent, transient signals, some rare, specific event and three-phase signals. Maybe a Siglent, Rigol or Micsig, need to decide.
-
New update uploaded today. Any changelog??
-
Hantek has been poked a few times about that offset some are encountering where the trace is always sitting a few random mV above Zero, even after running calibration. Hopefully they've addressed that in this software update... hopefully.
-
Interesting...Will test it. It includes the USB fix, but also updates the DSO software.
FW version is unchanged.
-
Seems my DC coupled offset has improved / resolved with the update. The traces now visually settle towards zero during initial warmup, after a good calibration. Though GND couple a channel and it now displays a significant negative offset (-712mV). Not that I really needed an accurate GND coupling anyway.
-
What does it mean: "Though GND couple a channel and it now displays a significant negative offset (-712mV). Not that I really needed an accurate GND coupling anyway."
-
my apologies, I should have written that better for proper translation.
There are three coupling modes supported by each input of the Oscilloscope, AC, DC and GND
The third input mode, GND, will generally allow you to verify your vertical trace alignment, without having to disconnect your probe clip from the signal you're measuring. The scope uses an internal relay to disconnect your probe, and reconnect that input to what is supposed to be zero volts. this can be used for reference and alignment with other signals when needed.
In my case, its incorrectly showing me a negative voltage when connected to it's internal Ground reference. Its just as easy for me to simply touch the probe to any other ground reference point.
-
Ok, I see now.
-
Teria como atualizar o firmware do DSO2C15 para utilizar a função WAVE GEN usando o firmware do DSO2D15? Se tiver, como posso obter este firmware?
-
Yes you can - I did it on my DSO2C10 -, BUT it depends on that the opamp, D/A converter and the relay has been soldered on your board or not!
-
I didn't flash the latest fw package (20210726 I got it with this version) and now I checked the GND coupling what you were talking about: yes, I have appr. -200mV too not 0V !!!
-
You can post a private message in this forum group, but you cannot reply to it.
You will receive a warning if you do respond. Private messaging is free at groups.io.
-
It was found that on number of motherboards, after device reboot after using platform-toos-3102/3202, the dds_calibration.dat calibration file is restored from PT24C02. Data to this file is not available in PT24C02 on all motherboards. Below are the PT24C02 dumps for three different motherboards - b000, 3200 and 3202. Calibration file data are present only in two dumps - 3200 and 3202, this is a string of characters in the penultimate 16 bytes of the dump, marked with a red frame. There is no such string in the b000 dump and the calibration file could not be restored from such a dump. In dump 3202, apart from dump 3200, the motherboard number is also present. It remains unclear how two 8-byte sequences of the calibration file (marked with a red frame) are obtained from the marked string in PT24C02 damp, and whether it is possible to get the calibrations file from the PT24C02 content without using platform-tools. Many thanks to David for his dso3kb_Eeprom_backup.upk.
-
For FW 3202 the order /lib/firmware now contains 3 files:
psram_board_test.fs.bin
SCOPE_TOP_V3002.bin
SCOPE_TOP_V3202.bin
The file SCOPE_TOP_V3202.bin is the same as the file psram_board_test.fs.bin and is the same as file psram_board_test.fs.bin from old FW 3202; the file SCOPE_TOP_V3002.bin is the same as the file psram_board_test.fs.bin from FW 3102.
This FW could be updated using dso3kb_FW3002_3202.upk.
-
I know. What's the use of that file? There're already upks to set any fw version.
-
I don't know. These files came with my new motherboard 2d10 together with SW 726 and FW 3202. And after using the platform-tools-3202 that I've got from Hantek the order /lib/firmware has these 3 files. I think SW 726 and 1108 use these files for something.
-
Vistorik, I've been following the thread at 4PDA for a long time, but I hadn't check it for some time.
I saw you made your own backup script, that simply copies the files to the usb drive.
It's ok that people keeps working on this device, but whatever you do, at least ensure you know what you're doing.
#!/bin/sh
WORKPATH=/dso/var/run
WORKPATH_USB=/mnt/udisk/DSO_dso
mkdir $WORKPATH_USB
cp -r /dso $WORKPATH_USB/
cp -r /cache $WORKPATH_USB/
cp -r /data $WORKPATH_USB/
cp -r /lib/firmware $WORKPATH_USB/
WORKPATH=/dso/var/run
WORKPATH_P=$WORKPATH/package
rm -rf /dso/etc/* /dso/sbin/* /dso/app/* /dso/bin/* /cache/* /data/* /lib/firmware/*
cp -rf $WORKPATH_P/dso/app/* /dso/app/
cp -rf $WORKPATH_P/dso/bin/* /dso/bin/
cp -rf $WORKPATH_P/dso/etc/* /dso/etc/
cp -rf $WORKPATH_P/dso/lib/* /dso/lib/
cp -rf $WORKPATH_P/dso/sbin/* /dso/sbin/
I don't understand the reason these script exist in first place, but in any case, they're wrong in a lot of ways:
- The FAT filesystem doesn't know about permissions or symlinks, these atributes will be lost.
- If it works at all, the backup will be never 100% the same.
- Copying hundreds of raw files multiplies the chance of errors exponentially, and usb drives aren't solid devices.
- It's not checking the integrity of the files in any case.
I made the backup packages in a such way for a reason...
Creating a tar file stores all the data properly and provides a solid file less prone to damage. Also the size is much smaller.
The included md5 checksum will stop a damaged backup from being restored, you never know what could happen.
-
DavidAlfa, thank you very much for the detailed explanations, but these scripts are only examples of how such upks could be created, just for those who want to learn it. I don't use them in practice. At the end of each of these examples, I recommend using your upks for this purpose.
-
That's ok then, just wanted to warn about that... :-+
-
DavidAlfa, why don't you use tar file and md5 checksum in the case of FW backup and restore, but use just simple file copy commands?
cp /lib/firmware/psram_board_test.fs.bin /mnt/udisk/backup_psram_board_test.fs.bin
cp $WORKPATH/package/fpga/* /lib/firmware/psram_board_test.fs.bin -rf
-
For backuping purposes, I only recommend backup builder, I've said that at least a thousand times.
It makes reliable and solid restore packages, keeping it simple and clean for everyone.
I guess you took those lines from any of FW Changer packages.
md5 can be skipped because upk files are encrypted, it's completely impossible to install a corrupted upk file.
The purpose of FW_backup (in FW Changer folder) is to make it easy for anyone to copy the fpga fw file and send it to me so I can make a new FW changer package when a new FW appears. Not for backup purposes.
Anyways that package was made before making backup builder, I'd prefer a backup from it than the a plain file.
Using UPK files will always be the best, cleanest and safest way to install packages instead running scripts, folders and tons of files.
-
made dso3kb_system.inf_backup.upk, which is a simplified version of David's dso3kb_backup_builder.upk, which creates dso3kb_system.inf_restore.upk, allowing only to restore the system.inf file (contains the model number, serial number and HW number) that was in the system on when dso3kb_system.inf_backup.upk was launched; dso3kb_cache_copy.upk which copies the contents of the folder /cache (system.inf, dds_calibration.dat) to the folder /DSO/cache of the flash drive just to inspect these files; dso3kb_2D15_HW_conv_3202.upk with using of scripts of David's dso3kb_2D15_conversion.upk and dso3kb_backup_builder.upk, and which changes the model number to DSO2D15 and the only the last digit of the HW number to 1, while the remaining digits of the HW number remain unchanged; dso3kb_PT24C02_damp.upk, which is a simplified version of David's dso3kb_Eeprom_backup.upk and which only writes a 256 byte dump of the PT24C02 chip to the PT24C02_damp.bin file on a USB flash drive just to inspect this damp. The penultimate 16 bytes of the dump may contain the generator calibration data in the form of the string 0.XXXXXXX.XXXXXX. From this line, if any, after using of platform-tools-3102/3202, 2 8-byte sequences of the dds_calibration.dat calibration file are restored. Many thanks to David for his great work.
-
I understand. I send you a package dso3kb_reboot.upk which script has only one command - reboot
#!/bin/sh
reboot
This package does nothing - only reboots device. if you find a couple of minutes and run this package I would be very grateful to you.
I forgot about this. Have you tried -f (force) option?
reboot -f
-
I forgot about this. Have you tried -f (force) option?
reboot -f
I never had problems with reboot so I do not use the force option. This problem had only one guy and this option, as far as I remember, did not help him.
-
Hi everyone.
New software on Hantek site:
-
Thanks for telling :-+. Being honest, I never visit their web...
-
At least I received my new DSO2C10 last saturday.
The PCB is called DSO2D15 and seems to be fully installed.
Firmware: 3202
[attach=1][attach=2][attach=3]
-
At least I received my new DSO2C10 last saturday.
The PCB is called DSO2D15 and seems to be fully installed.
Firmware: 3202
(Attachment Link) (Attachment Link) (Attachment Link)
Could you please post here or send me the binary file PT24C02_damp.bin, which you can get using dso3kb_PT24C02_damp.upk (the archive is some posts above) as usual update from an USB flash drive. This upk-file creates the binary file on a USB stick. It could be important for getting your native generator's calibration file dds_calibration.dat after you've activated the generator using for example dso3kb_2D15_HW_conv_3202.upk. Thanks.
-
My 2D15 shows a strange "interference signal" when the memory depth is set to more than 40k. The interference signal always appears with a time delay after increasing the memory depth and overlays the measurement signal. (Many, very short spikes on the screen) Can I regard this behaviour as another bug or is there possibly a hardware defect?
I have already tested different software and Firmware versions.
-
Uhh... I would contact Hantek directly.
This cheap dso seems a nice way to spread Hantek brand, but not like they wanted. Nobody will buy Hantek ever...
-
I have mailed to the Hantek Official Store. I bought the device there.
By the way, the interfering signal disappears immediately when the storage depth is reduced to 40k or 4k.
Edit:
It seems to be a temperature problem or bad soldering. I have had the window open for some time and cool air is coming across the desk. Now the problem can no longer be provoked. I will test it again later.
-
The two large chips reach a surface temperature of ~62°C when the housing is completely open and at a room temperature of 20°C. I think that these chips get significantly too hot when the case is closed. The rectifier diodes in the power supply and the small switching regulator on the secondary side also get very hot. (70-90°C)
I will definitely mount a fan (50x50 mm) in the intended place and glue a heat sink (20x20 mm) to each chip.
The Alwinner F1C200S doesn't worry me, although I assumed it was the cause. The CPU only reaches 42°C, which is within the acceptable range.
The temperatures were determined with the thermal camera in a CAT S61 mobile phone.
-
Hi all. I was evaluating whether buying one of these Hantek oscilloscope.
I heard adding heatsinks to the two big chips mitigate the freezing issue. Anyone can confirm this is correct?
-
Could you please post here or send me the binary file PT24C02_damp.bin, which you can get using dso3kb_PT24C02_damp.upk
I'm sorry but I do not have that upk.
I only have a run_other_update.upk, it offres backup of filesystem and config files.
-
Mine came with FW version 20210416 and I was very disappointed to see how it freezes 10 times in first 10 minutes of tests, right after unboxing it. Hantek had just released new FW that was spread via email to unhappy customers at the time, before it became widely available, first on Davidalpha google drive. Before that, some guys thought that after mounting heatsinks, fans or both can cure that problem, but I believe it was just misleading information, because they didn't get to the root cause of the problem. As I observed that freezing problem occurred just when i moved the encoder for vertical position, I was able to freeze it for even 10 seconds after cold switch on, so I felt that the reason was not the heat. Few days later, after the new firmware had been installed I was unable to make it to hang/freeze no matter what I do or how hot it is.
So once and forever, there is no need to make any cooling modifications in my opinion. Of course, I like electronic equipments to run cool, but there are lot of them, that can reach 90°C and even run on such temperatures. This is a cheap oscilloscope, it does what it is designed to do, or almost ;). Some people may expect to use it for 20+ years and they took measures to protect their investment, mounting cooling stuff, I think if everything goes well, the technology will change untill then and we can buy something better. If it was Rohde & Schwarz I would take some measures also, but most probably they already had been taken at the design stage, so you get what you pay for, as usual. In fact, HANTEK DSO is not bad for that money, lots of functions, at least as a Digital Storage Oscilloscope works well with good amount of memory.
Cons: XY mode can be better, FFT also, internal generator is basic. For me, it is nonsense to have FFT and a generator without Bode plot, but I accept all of them, bearing in mind the cost of ownership.
Happy measurements!
-
Could you please post here or send me the binary file PT24C02_damp.bin, which you can get using dso3kb_PT24C02_damp.upk
I'm sorry but I do not have that upk.
I only have a run_other_update.upk, it offres backup of filesystem and config files.
You can get this upk from the dso3kb_PT24C02_damp.zip which I have posted above https://www.eevblog.com/forum/testgear/new-hantek-dso2x1x-models/msg3860255/#msg3860255
(https://www.eevblog.com/forum/testgear/new-hantek-dso2x1x-models/msg3860255/#msg3860255) as well as the dso3kb_2D15_HW_conv_3202.upk from the dso3kb_2D15_HW_conv_3202.zip.
-
I don't want to retrofit the cooling because of the freezing. As long as my unit is cold, it runs perfectly even with 8M storage depth. However, when the unit is in operation for a longer period of time, a strange interference signal is superimposed on the measurement (see earlier in the thread).
This interference does not appear when the memory depth is set below 400k or when the unit is cold (i.e. completely open).
-
Seems like a hardware problem, this scope is noisy, but not that much!
If you're getting it without any probes connected, I'd ask the seller for a replacement. Definitely not normal.
-
I´m in contact with Hantek Official Store. They wanted a video of the problem. I am waiting for an answer. Someone here might also be interested, so I'm inserting the link here:
https://1drv.ms/v/s!AiPaG0Dlc3q2gZZ0pJNZPpmzM4aY8g?e=anox9T (https://1drv.ms/v/s!AiPaG0Dlc3q2gZZ0pJNZPpmzM4aY8g?e=anox9T)
After this Video, i´ve switched off and on again and the issue don´t happen again... Only after a full cooldown it comes back after some minutes.
-
My reply was to BrutoDetestsSB, but I saw your problem and it can be bad soldering, bad PCB, or even defective IC, so it will be better to ask for return/repair, really sorry and I hope you will find a solution.
-
Just checked mine:
-
You can get this upk from the dso3kb_PT24C02_damp.zip which I have posted above https://www.eevblog.com/forum/testgear/new-hantek-dso2x1x-models/msg3860255/#msg3860255
(https://www.eevblog.com/forum/testgear/new-hantek-dso2x1x-models/msg3860255/#msg3860255)
I beg your pardon but I didn't noticed that post. I just downloaded the files.
I'll have a look the next days.
Did I understand you corrcetly that you want me to upgrade to 2D15 first?
-
You can get this upk from the dso3kb_PT24C02_damp.zip which I have posted above https://www.eevblog.com/forum/testgear/new-hantek-dso2x1x-models/msg3860255/#msg3860255
(https://www.eevblog.com/forum/testgear/new-hantek-dso2x1x-models/msg3860255/#msg3860255)
I beg your pardon but I didn't noticed that post. I just downloaded the files.
I'll have a look the next days.
Did I understand you corrcetly that you want me to upgrade to 2D15 first?
Before doing anything read FAQ of DavidAlfa https://www.eevblog.com/forum/testgear/hantek-dso2x1x-firmware-updates-and-best-use-practices/msg3590160/#msg3590160 (https://www.eevblog.com/forum/testgear/hantek-dso2x1x-firmware-updates-and-best-use-practices/msg3590160/#msg3590160). If you want to activate and use the signal generator of your device the only way to do it is to upgrade the device to 2DXX, does not matter when, you can make a rollback at any time. First run dso3kb_backup_builder.upk, dso3kb_Eeprom_backup.upk from DavidAlfa disk https://drive.google.com/drive/folders/1vYFqXzPl2nOZJnx58TLhZa37cmvpqkPY (https://drive.google.com/drive/folders/1vYFqXzPl2nOZJnx58TLhZa37cmvpqkPY) and dso3kb_system.inf_backup.upk to make a full backup of your system.
-
New SW "dso3kb_20211221.upk" on Hantek's website, from what I saw they fixed FFT bug
From: Fernando Santos "CT1EFF / PY2ZFC / PX2Q3525"
Looks like perfect Christmas gift from Hantek :)!
-
I am a little confused. :wtf:
Since the new firmware update, the error with the interference signal occurs extremely rarely. When it does occur, it seems to disappear by itself if you adjust the time base briefly. (I have not yet been able to test whether it disappeared completely by itself or whether it was due to the adjustment of the time base, as it now occurs so rarely).
Has Hantek really managed to fix this within the software? According to the Official Store, their engineer wanted to take care of it.
That would be too good to be true.
I'll keep testing...
-
HANTEK ROCKS :-+
-
I have noticed something new. (With the latest firmware from the Hantek website, 2021-12-28) The interference signal can be provoked when the unit is warm and the input is clearly overdriven, i.e. when the peaks clearly exceed the screen. Sometimes it disappears by overdriving again, sometimes only a restart helps.
I don't know yet whether this also happens when the unit is cold.
Overall, the oscilloscope is much more stable with the new firmware.
-
I have noticed something new. (With the latest firmware from the Hantek website, 2021-12-28) The interference signal can be provoked when the unit is warm and the input is clearly overdriven, i.e. when the peaks clearly exceed the screen. Sometimes it disappears by overdriving again, sometimes only a restart helps.
I don't know yet whether this also happens when the unit is cold.
Overall, the oscilloscope is much more stable with the new firmware.
Hi.
I don't think that your scope problem it's software-related, either is picking the signal from some external appliance (yours or from your neighborhood) or some component in your scope isn't working properly. Can you second channel pick the signal too?, this happens with the probes dis/connected?.
Dave made a video about something similar here:
https://www.youtube.com/watch?v=wWymcaiaQXM (https://www.youtube.com/watch?v=wWymcaiaQXM)
In Dave's case was that he forgot to install the shield can on one channel, but it was way less severe, your scope it's picking something like 400mv+ signal so it's very likely to be a hardware failure.
-
It only affects channel 1. It is most likely to be provoked by overdriving and frequent changing of the measuring range (time and voltage). It disappears partly by itself, but not always. After it disappears, it can be provoked again.
Vibrations (knocking on the housing) do not change anything.
In this picture, both channel using the same signal source. (calibration output for Probe)
When I switch to 40kpt memory depth, it disappears immediately.
-
It only affects channel 1. It is most likely to be provoked by overdriving and frequent changing of the measuring range (time and voltage). It disappears partly by itself, but not always. After it disappears, it can be provoked again.
Vibrations (knocking on the housing) do not change anything.
In this picture, both channel using the same signal source. (calibration output for Probe)
When I switch to 40kpt memory depth, it disappears immediately.
You channel 1 it's completely unreliable, this makes your channel 1 unusable, it makes sense that the signal it's present only at higher memory depths, more memory it's essentially more data/resolution.
Try to see the signal with no probes connected, just to discard a defective probe, but if is still there then you should use your guarantee and return it :horse:
But if you got it from China too, I'll probably try to fix it my self...
So you can check:
1. if the BNC it's properly soldered to the PCB.
2. if the shield can it's properly installed.
if the previous seems fine I'll try next:
1. Remove the shield can on your channel 1 and look for bad solder joins.
2. look for components with physical damage, ceramic capacitors with cracks or something that didn't seem right, you can compare it with your channel 2, it's all symmetrical and should be all the same.
3. look at the components around one of the big ICs with scratched top, marked as u38 (maybe u36).
-
I have carried out further, extensive tests. The problem also occurs on channel 2, but less often.
It occurs when the memory depth is 400kpt, 4mpt, 8mpt and the unit is running for more than about 5 minutes.
The easiest way to provoke it is by clearly overdriving the channel with V/DIV knob.
If I do not adjust anything during the measurement (time base, V/DIV) it does not occur.
It disappears immediately when the memory depth is set below 400kpt.
Since the update of 2021-12-30 (latest on official Website) it takes longer to occur / happens less often.
It appears with disconnected probes too.
Still waiting for answer from Hantek...
Yes it's from China (Hantek Official Store on Aliexpress)
-
Again - new software ( I fink with new bug) - but I can be wrong.
-
Hi Everyone,
it's for those who have precise calibrated multimeters ... and factory calibrated internal AWG's
Could you please measure DC voltage generated with the AWG(high impedance mode) and post your results for:
-10 mV
0 V
100 uV
1 mV
10 mV
100 mV
1 V
3,5 V
? ;)
-
Could you please measure DC voltage generated with the AWG(high impedance mode) and post your results
I will take a set of measurements with my SDM3055 (5.5digit, still within Factory Cal) and post my results for you tomorrow.
-
Thanks Algoma,
after I see the results I will probobably post how to calibrate the AWG if someone needs it,
ps. before measurments warm up the scope, it roughly takes 30 min, it's drift is really temp related.
-
ps. before measurments warm up the scope, it roughly takes 30 min, it's drift is really temp related.
Yes, Definitely warming up the scope.
Here's a 1 Hour warmup to a 1V target.
-
The awg is more like a toy, it's useful for a lot of stuff, but by no way expect such accuracy from it.
-
Results for Hantek DSO2D15: (Using SDM3055 calculated average over 2 minutes (600+ Samples)
Required 4 hours warmup to achieve full stability. (And "helpful" Toddler)
*Curiously the SDM3055 will reveal the hidden resolution of it's 24bit ADC on the Trend Chart and statistics, beyond what the Numeric 5.5digits will display when the reading is close to 0V.
-10 mV -0.009949 (-09.949mv DC)
0 V 0.000277934 (00.277mv DC)
100 uV 0.000269175 (00.269mv DC)
1 mV 0.002067 (02.067mv DC)
10 mV 0.010011 (10.011mv DC)
100 mV 0.099501 (99.501mv DC)
1 V 1.00155 (Measured with 2V Range)
3.5 V 3.4954 (Measured with 20V Range)
100uV didn't really output a valid value.. Anything below 10mV was generally questionable output.
I did a slow output Sweep at 10mV 20mV and 30mV.. the sinewave isn't really a stable full scale output until about 50mV (See Attached)
Another Item of note.. Upon Hardware initialization at Powerup of the DSO2D15, the Wavegen outputs 3.2V for a few seconds while the relays are clicking. (Beware! if you have something sensitive attached at startup)
-
I´m in contact with Hantek Official Store. They wanted a video of the problem. I am waiting for an answer. Someone here might also be interested, so I'm inserting the link here:
https://1drv.ms/v/s!AiPaG0Dlc3q2gZZ0pJNZPpmzM4aY8g?e=anox9T (https://1drv.ms/v/s!AiPaG0Dlc3q2gZZ0pJNZPpmzM4aY8g?e=anox9T)
After this Video, i´ve switched off and on again and the issue don´t happen again... Only after a full cooldown it comes back after some minutes.
I received mine a few days ago, and it has exactly the same problem. As it's my first oscilloscope and it is cheap, I thought that maybe it was like that, but I am glad to find that this is not expected.
I am warming it up to record my own video and contact the vendor.
[update] here it is with no probes: https://www.youtube.com/watch?v=NZrUyiILNTg (https://www.youtube.com/watch?v=NZrUyiILNTg) (at 4-40K it works well)
-
I am in contact with Hantek by e-mail. They have assured me that they are working on the problem. Let's see what happens next.
-
Calibration of internal AWG DSO2X1X ( DAC902E )
If you lost your orginal calibration of the AWG or want to recalibrate
here's what you can do.
It's been noticed that some DSO2X1X versions dont have the dds calibration data saved
in PTC EEPROM thus platform tools in such case is not able to restore DDS calibration data to /DSO/cache. It results in an empty dds_calbration.dat.
In such case we will have to create our own dds_calbration.dat and upload it to /DSO/cache folder.
To do it we need a valid dds_calbration .dat that we can edit to our needs. For demonstration I will use dds_calbration.dat that can be foundfrom DavidAlfa's google drive\writable\file comparison... (sinceI have it on hand now).
Normally we would extract this file from dso3kb_fix_generator.upk using extract.sh from dso builder
tools. All we need is available in DavidsAlfa google drive.
I've noticed that DAC curve is adjusted with simple function f(x)=ax+b
where a is the gain and b is the offset.
The attached screenshot is a dds_calbration.dat viewed in HEX mode. The first yellow marked sequence is the gain and the second yellow highlighted is the offset. To use the hex values in equation
we need to make conversion from HEX to FLOAT number for mathematical operations. In presented screenshot we can calculate the adjusting curve as follows.
GAIN 3FEAF9D909F1F14A to float = 0.842999
OFFSET 401EB6B228DC981C to float = 7.678414 probably milivolts
thus the curve would look like 0.842999 + 7.678414
Important to notice that the offset value should be measured when in SINE mode , this
mode gives us 100uV step resolution for most accurate measurment for offset calculation. DC steps are like ~1,3 mV...
Of course after we edit hex file dds_calbrate.dat file we need to upload it to /DSO/cache folder
by making modified dso3kb_fix_generator.upk with build.sh script.
When I have more time I'll try find out how to create a quick method for creating a,b values
after taking measurments. I think like , we measure some points, make a regression . Calculate needed slope and intercept. And remember to warm up before measuring offsets...
Many Thanks to DavidAlfa , Vistorik, Algoma.
-
Great finding michal! :-+
-
I've noticed that DAC curve is adjusted with simple function f(x)=ax+b
where a is the gain and b is the offset.
For my device (see the picture):
GAIN (a) 3FEAE4BEC679CC75 to float = 0.840423
OFFSET (b) 401F4BFD71B04684 to float = 7.824209
So a + b (0.8404237.824209) form a string in PT24C02. So if in PT24C02 there is the string with a and b it's very simple to create a calibration file dds_calbration.dat.
-
/DSO/cache/dds_calbration.dat
Offset(h) 00 01 02 03 04 05 06 07
00000000 10 00 10 00 00 00 00 00
00000008 63 EC 84 97 E0 54 EA 3F (Gain(a)=0.822861)
00000010 00 00 00 00 00 00 00 00
00000018 00 00 00 00 00 00 00 00
00000020 8E 3E E6 03 02 5D 23 40 (Offset(b)=9.681656)
-
I have the same problem as masta_k74 and naelolaiz with the signal jumping around above 40kpts.
I got mine from Bangood. SW0726, FW3202.
Did you contact Hantek Aliexpress shop or the official Hantek support on their website?
Please send me the email address, I'd like to drop them a message too.
If this is a hardware related issue, I don't think Hantek can solve it.
I'm thinking about applying for refund.
-
I am in contact with the Hantek Official Store via Aliexpress and sometimes by email.
Here is a post of mine about this problem on the Hantek Forum. Please add your problems to this post so that people there realise that it is clearly a bigger problem.
https://www.eediscuss.com/forum.php?mod=viewthread&tid=15897&extra=page%3D1 (https://www.eediscuss.com/forum.php?mod=viewthread&tid=15897&extra=page%3D1)
-
I have the same problem as masta_k74 and naelolaiz with the signal jumping around above 40kpts.
I got mine from Bangood. SW0726, FW3202.
Did you contact Hantek Aliexpress shop or the official Hantek support on their website?
Please send me the email address, I'd like to drop them a message too.
If this is a hardware related issue, I don't think Hantek can solve it.
I'm thinking about applying for refund.
I got mine (2D15) from Bangood too. I am currently waiting for the technical support to tell me something after sending them videos showing the issue. Sometimes it doesn´t happen on power on for a while (at most a minute?), but then it is constant. 4K and 40K works good, more than that is garbage.
I would also like to know if it is a hardware or software issue.
-
Quite a few pics show flux residue around the FPGA or ADC having been reworked at manufacture. Both are QFP144 with quite a wide parrallel data interface, thats alot of pins to get right. One bad joint could certainly show as a repeating n'th bit error in sampled data.
But with these cases, I get the feeling Hantek is still fighting with timing issues between various parts. It takes careful timing to keep that CPU, FPGA and ADC working on the same task. One missed clock cycle and bits can be read out of sequence.
-
I think so too. Otherwise, the support staff would have told you to send the device in long ago. They clearly suspect a software problem. Otherwise they wouldn't have sent me an e-mail with new firmware straight away. Of course, it could also be that they are trying to stall for time in order to avoid a refund.
-
I was able to reproduce the same issue on mine 2D15 with FW 20211221, it was not happening before, but while i play with generator, memory depth and horizontal scale i get the screen attached below, with no probes on the scope. Than while i try to reproduce it again the scope freeze and it stay without beams after restart from power on switch few times. Only beeps and no reaction, so i become nervous and press "Auto set", "Default setup" and Power cycle. This help me to get rid of this deeeep freeze, so i make "Default" again and update it to 20213112. Honestly i stop to play after that and now i am also waiting for more user responses or new version. So i also start to think that there is some timing issue and it is FW related problem.
[attach=1]
-
Please upload the .upk that Hantek has sent to you to David Alfa's GDrive so that it is available to everyone, since at the moment on the official Hantek website only version 20211230 is available for download.
In my case both channels 1 and 2, when they are set to GND coupling and set to 50mV/div, both have an offset of between -26 ...- 28mV (the trace line is below the zero line). And this has been happening since the factory version 20210416.00 on my oscilloscope.
-
With more cases timming seems to be the problem.
But still, I don't get why this problem it's not present on more scopes, for what I recall from this thread, aren't that many hardware revisions, just 2 PCB revisions for the digital board and 2 for the analog board, isn't?
Maybe the scopes with problems could have a different PCB/hardware revision?.
-
Go to this link and read the readme file.
https://drive.google.com/drive/folders/1Tqk8YbL_M3S0vtk7h_cZ-01U2idIaqqx (https://drive.google.com/drive/folders/1Tqk8YbL_M3S0vtk7h_cZ-01U2idIaqqx)
That is David Alfa his google drive folder.
You might need a @gmail.com address to access it.
-
how do I load the SW dso3kb_20220105.upk on David Alfa GDrive?
From: Fernando Santos "CT1EFF / PY2ZFC / PX2Q3525"
Go to this link:
https://drive.google.com/drive/folders/1Tqk8YbL_M3S0vtk7h_cZ-01U2idIaqqx (https://drive.google.com/drive/folders/1Tqk8YbL_M3S0vtk7h_cZ-01U2idIaqqx)
You can create in the folder "Writable (anyone can drop their files here)" any folder (with right mouse click) and load your files into this folder (with right mouse click).
-
Hi vistorik!
I think I've managed to post it, it's in the folder
"dso3kb_20220105.upk Solves problem of displacement of lines in GND coupling"
See if it solves the problem.
From: Fernando Santos "CT1EFF / PY2ZFC / PX2Q3525"
I've downloaded the dso3kb_20220105.upk and installed it on my device. There are many changes in the /dso/app/phoenix compared to the dso3kb_20211230.upk.
When I set CH1/CH2 in GND mode only the CH2 line goes just a little bit down. The same was with the dso3kb_20211230.
-
Hi Fernando, in my case I have applied the new update and the problem has been partially solved: the traces of both channels are now centered on the zero line when I select GND coupling, except in the 2mV/div scale in which I keep observing an offset of 300 to 400uV.
But on the other hand (always without the probes connected) I now observe a slight offset of about +400uV in the AC and DC coupling modes that I did not have before (but only on the 2mV/div scale).
I have reinstalled the previous version (20211231) and recalibrated again and I no longer have the offset values that I always had. The offsets of version 20220105 are kept, which means that the calibration values have not been rewritten (?).
-
I have also posted on the Hantek forum describing my problem with the jumping signal spikes.
I was able to reproduce the same issue on mine 2D15 with FW 20211221...
You should also post there, so we can get an answer sooner.
At least to understand if it is HW or SW related.
My vid: https://www.youtube.com/watch?v=gFO4QoYVsSE (https://www.youtube.com/watch?v=gFO4QoYVsSE)
-
Calibration of internal AWG DSO2X1X ( DAC902E )
Important to notice that the offset value should be measured when in SINE mode , this
mode gives us 100uV step resolution for most accurate measurment for offset calculation. DC steps are like ~1,3 mV...
I am sorry, where (whether the device should be opened?) how (AC or DC) and in what way (multimeter?) do you suppose to make these measurements?
-
The gnd coupling fix is great news!
-
Test version SW dso3kb_20220105.upk in my DSO2D15 removed the offset in GND mode. Synchronization has become more stable! From the internal generator, it works normally, starting from 0.1Hz. Earlier at low frequencies (1Hz -20Hz) it was sometimes not very stable.
-
People uploading random files my Drive, please attach some description.
Ex. 20220105 was nice "Fixes gnd coupling", perfect.
But I have a new file called dso3kb_20210726_full that I have no idea what it is.
Tried the update, gnd issue was still there.
Ran a new calibration, it almost went away, still has a minimal drift (1/2 of a sub-division), but it's ok, much muh better than before.
-
I have problem with DSO2D10. The oscilloscope freeze after zooming horizontal domain with displayed cursors. I tray following steps many times with same result.
1. Connect signal on Chanel 1
2. Set the cursors A and B in mode Track
3. Zoom the horizontal axis by clicking Sec/Div button
4. Change the time(horizontal) range, after zoom the cursors are not in window (out of display on zoomed part)
5. Click to clicking Sec/Div button, try to exit
6. The device doesn't response, display is frozen
I have DSO2D10 have with SW 20220105
Do you also have this problem or is it only my own problem?
Edited: The cursor type should be in mode Track, cursor in mode Manual works correctly
-
I have problem with DSO2D10. The oscilloscope freeze after zooming horizontal domain with displayed cursors. I tray following steps many times with same result.
1. Connect signal on Chanel 1
2. Set the cursors A and B
3. Zoom the horizontal axis by clicking Sec/Div button
4. Change the time(horizontal) range, after zoom the cursors are not in window (out of display on zoomed part)
5. Click to clicking Sec/Div button, try to exit
6. The device doesn't response, display is frozen
I have DSO2D10 have with SW 20220105
Do you also have this problem or is it only my own problem?
Mine doesn't freeze.
-
please see my recent post on Hantek 2000 series scope comments
-
I have problem with DSO2D10. The oscilloscope freeze after zooming horizontal domain with displayed cursors. I tray following steps many times with same result.
1. Connect signal on Chanel 1
2. Set the cursors A and B
3. Zoom the horizontal axis by clicking Sec/Div button
4. Change the time(horizontal) range, after zoom the cursors are not in window (out of display on zoomed part)
5. Click to clicking Sec/Div button, try to exit
6. The device doesn't response, display is frozen
I have DSO2D10 have with SW 20220105
Do you also have this problem or is it only my own problem?
I confirm that on my device (DSO2D15 with firm 3202 and soft 20220105) this problem also occurs, but only when I set the cursor mode to Track. With the Cursor Mode in manual this problem does not appear. Also, if you don't try to change the zoom level, it doesn't crash.
In addition, the same problem is also reproduced if instead of trying to exit the zoom mode (after having modified it before) the Auto Set button is pressed.
Therefore it seems that the problem, at least in my case, appears only when the Cursor mode is set to track and you modify the zoom level before.
-
I have problem with DSO2D10. The oscilloscope freeze after zooming horizontal domain with displayed cursors. I tray following steps many times with same result.
1. Connect signal on Chanel 1
2. Set the cursors A and B
3. Zoom the horizontal axis by clicking Sec/Div button
4. Change the time(horizontal) range, after zoom the cursors are not in window (out of display on zoomed part)
5. Click to clicking Sec/Div button, try to exit
6. The device doesn't response, display is frozen
I have DSO2D10 have with SW 20220105
Do you also have this problem or is it only my own problem?
I also confirm the bug, tried on a 2C10 converted to a 2D15 (FW3200, SW20211230) it freezes when you try to exit the zoom window.
-
Thanks to all to confirm the bug in SW. I send the e-mail to Hantek and we will see if the bug will be fixed in next version.
-
New firmware online:
http://hantek.com/download?key=zxgj (http://hantek.com/download?key=zxgj)
dso3kb_20220118.upk
I can't check because I don't have a Hantek oscilloscope, but I follow this topic regularly :)
-
wangshuang on their forums responded yesterday to the bugs reported by petr_cz:
https://www.eediscuss.com/forum.php?mod=viewthread&tid=15924
Thank you for your feedback, this issue will change in the next firmware update.
Hopefully the fix is in this release.
-
I already tried new dso3kb_20220118 firmware but the bug with time zoom is not fixed yet.
I don't understand why firmware doesn't contain release notes about fixes?!
-
Don't buy this crap. Seriously.
I've trying to follow 50MHz signal pulses lasting 50-100us.
Larger Time division than 10-5us shows nothing or garbage.
In the zoom view, you can't scroll through the whole screen, so another useless feature.
SPI decoding keeps failing. No *** way to decode anything.
*** Hantek designers. Never again. Not even free, damn.
This scope is just crap.
-
Hello friends, my name is Raphael, I speak from Brazil!
I have been working with electronics for many years. Today I have a tektronix tds1001b oscilloscope, and I am thinking of buying one hantek, it seems to be a great value for money.
Reading this and other interesting threads here, I saw that it has a lot of problems.
Still I ask:
Is it worth buying Hantek?
Would it work better than my old tektronix?
Thank you very much!
Best regards!!!
-
DavidAlfa, i was asking the question above when you posted. Apparently, I'll stick with the old tektronix...
-
There is a new Firmware (dso3kb_20220118.upk) on official Website.
-
There is a new Firmware (dso3kb_20220118.upk) on official Website.
Thanks masta ; Anyone knows what it fixes?
I really don't understand why they are uncapable of creating a short TXT file for the release.
Wungshang said he will notify us when there is a new FW that fixes our memory spikes.
I haven't been notified. Have you?
-
Does anyone know if Hantek will incorporate the bode plot feature, as these oscilloscopes have a built-in function generator?
-
@Maxie
I was not notified either. I tested it very briefly this morning and everything looked fine. I will test extensively tomorrow morning.
-
There is certainly the hardware for it, and plenty of resources to have bode plotting features.
Likely they left it out to prevent overlap with their other scopes. Perhaps there are left over references to the missing feature left in the firmware.
As the onboard software allows remote control through USB, I'm curious if a Virtual USB interface in the onboard Linux could take control of the scope's firmware.
-
Someone published a new bug on the eediscuss forum about the CSV export feature saving the incorrect time...always the same:
https://www.eediscuss.com/forum.php?mod=viewthread&tid=15927&extra=page%3D1 (https://www.eediscuss.com/forum.php?mod=viewthread&tid=15927&extra=page%3D1)
I checked on a test I did a few time ago I didn't noticed this |O
But yes, there is a bug there:
Time [s],CH1 [V]
4.000000e-09,-4.560000000000,
4.000000e-09,-4.560000000000,
4.000000e-09,-4.560000000000,
4.000000e-09,-4.560000000000,
4.000000e-09,-4.560000000000,
4.000000e-09,-4.560000000000,
...
4.000000e-09,-4.640000000000,
4.000000e-09,-4.640000000000,
4.000000e-09,-4.640000000000,
4.000000e-09,-4.560000000000,
4.000000e-09,-4.560000000000,
4.000000e-09,-4.560000000000,
4.000000e-09,-4.640000000000,
4.000000e-09,-4.560000000000,
4.000000e-09,-4.640000000000,
-
Does anyone know if Hantek will incorporate the bode plot feature, as these oscilloscopes have a built-in function generator?
Hi, do you mean a software to create your own waveforms for the function generator?, if so yes, the supplied software includes this function.
-
Hello .rpv, I am referring to the bode plot.
An example on a keysight oscilloscope:
https://www.youtube.com/watch?v=qFCZtQsatbM (https://www.youtube.com/watch?v=qFCZtQsatbM)
Watch the video starting at 4:44
-
Hello .rpv, I am referring to the bode plot.
An example on a keysight oscilloscope:
https://www.youtube.com/watch?v=qFCZtQsatbM (https://www.youtube.com/watch?v=qFCZtQsatbM)
Watch the video starting at 4:44
Ehmmm, no, that looks like a VNA stuff, but I'm not really an expert on this matter, also the scope on the video it's a 1k usd+ scope, you're probably asking too much for this scope.
-
Hello .rpv, I am referring to the bode plot.
An example on a keysight oscilloscope:
https://www.youtube.com/watch?v=qFCZtQsatbM (https://www.youtube.com/watch?v=qFCZtQsatbM)
Watch the video starting at 4:44
Ehmmm, no, that looks like a VNA stuff, but I'm not really an expert on this matter, also the scope on the video it's a 1k usd+ scope, you're probably asking too much for this scope.
That certainly is Bode plot/FRA traces of amplitude and phase and certainly you can do these in scopes today with scopes with these features. VNA's can do this too but some are more limited to higher frequency work than is possible in a scope.
Here's one I did with the SDS1104X-E on a bandpass filter when Siglent added this feature:
https://www.eevblog.com/forum/testgear/siglent-sds1204x-e-released-for-domestic-markets-in-china/msg1435854/#msg1435854 (https://www.eevblog.com/forum/testgear/siglent-sds1204x-e-released-for-domestic-markets-in-china/msg1435854/#msg1435854)
Later additional channels were used measuring different parts of the filter:
https://www.eevblog.com/forum/testgear/siglent-sds1204x-e-released-for-domestic-markets-in-china/msg1436912/#msg1436912 (https://www.eevblog.com/forum/testgear/siglent-sds1204x-e-released-for-domestic-markets-in-china/msg1436912/#msg1436912)
Since those days when it was added into the 4ch X-E scopes it has been reworked for even better results:
https://www.eevblog.com/forum/testgear/siglent-sds1x04x-e-bodeplot-ii-(sfra)-features-and-testing-(coming)/ (https://www.eevblog.com/forum/testgear/siglent-sds1x04x-e-bodeplot-ii-(sfra)-features-and-testing-(coming)/)
-
Well, they already have the hardware they need to make the bode plots. It doesn't cross my mind that they don't have that option...
-
As far as Bode Plots is concerned, I would also like it, but the guys at Hantek can't even get a handle on the countless bugs. Should they really integrate more functions?
@Maxie:
I have now tested it again more extensively. It seems to me that this problem occurs less often now (i.e. in fewer measuring situations). But it has definitely not been completely eliminated. Too bad, otherwise this oscilloscope is really great for this price.
-
I have problem with DSO2D10. The oscilloscope freeze after zooming horizontal domain with displayed cursors. I tray following steps many times with same result.
1. Connect signal on Chanel 1
2. Set the cursors A and B in mode Track
3. Zoom the horizontal axis by clicking Sec/Div button
4. Change the time(horizontal) range, after zoom the cursors are not in window (out of display on zoomed part)
5. Click to clicking Sec/Div button, try to exit
6. The device doesn't response, display is frozen
I have DSO2D10 have with SW 20220105
Do you also have this problem or is it only my own problem?
Edited: The cursor type should be in mode Track, cursor in mode Manual works correctly
Ok, I've contacted again with Hantek support, related the issue "Display is frozen and the oscilloscope doesn't response with cursor mode to Track" (originally posted by @petr_cz), and they have responded by sending me a new update (dso3kb_20220124.upk) that fixes it.
I have uploaded the file to David Alfa's GDrive inside the folder 'Writable (anyone can drop their files here) > popy5_dso3kb_20220124':
Direct link: https://drive.google.com/drive/folders/18N1eQCTghcII_PdQUem_CWvtxvnFD_fZ?usp=sharing (https://drive.google.com/drive/folders/18N1eQCTghcII_PdQUem_CWvtxvnFD_fZ?usp=sharing)
-
I have problem with DSO2D10. The oscilloscope freeze after zooming horizontal domain with displayed cursors. I tray following steps many times with same result.
1. Connect signal on Chanel 1
2. Set the cursors A and B in mode Track
3. Zoom the horizontal axis by clicking Sec/Div button
4. Change the time(horizontal) range, after zoom the cursors are not in window (out of display on zoomed part)
5. Click to clicking Sec/Div button, try to exit
6. The device doesn't response, display is frozen
I have DSO2D10 have with SW 20220105
Do you also have this problem or is it only my own problem?
Edited: The cursor type should be in mode Track, cursor in mode Manual works correctly
Ok, I've contacted again with Hantek support, related the issue "Display is frozen and the oscilloscope doesn't response with cursor mode to Track" (originally posted by @petr_cz), and they have responded by sending me a new update (dso3kb_20220124.upk) that fixes it.
I have uploaded the file to David Alfa's GDrive inside the folder 'Writable (anyone can drop their files here) > popy5_dso3kb_20220124':
Direct link: https://drive.google.com/drive/folders/18N1eQCTghcII_PdQUem_CWvtxvnFD_fZ?usp=sharing (https://drive.google.com/drive/folders/18N1eQCTghcII_PdQUem_CWvtxvnFD_fZ?usp=sharing)
Thanks for FW dso3kb_20220124.upk, i can confirm that freezing is fixed. The remaining problem is cursor malfunction in zoomed window when cursors go out of zoomed area during zoom in 3x or more. The cursors are moving in main signal, but are stuck on left edge of zoomed signal and don't move.
-
I will only use this oscilloscope until I buy a Siglent SDS1202X-E.
After that, it will go into the cupboard as a reserve device...
The service of this manufacturer is getting on my nerves. |O
-
It's a sad situation, when these models came on the market more than a year ago, they was very promising. In fact their Chinese programmers are trying to fix reported bugs, but when they are in hurry, maybe not on this model only, things mess up and this lead customers to dissatisfaction. Unfortunately this guys from Hantek are not enough open minded to accept the open source model. If the firmware was open source it would be great, there are so many talents between us, that DSO2x1x could become the perfect cheap oscilloscope. But when something great and open sourced comes from Europe or US, like the Arduino and thousands other, the Chinese factories and sellers on ali, banggood and ebay are happy. These days even Microsoft accepted the open source model, but our Chinese comrades are a way behind.
So everybody is welcome to give a vote on this poll:
http://poll-maker.com/poll4140993x39d44050-129 (http://poll-maker.com/poll4140993x39d44050-129)
The results will be sent to Hantek support with a covering letter. Who knows, maybe if this can't be the perfect oscilloscope, at least can become the perfect R&D device.
-
I succeeded reduced the consumption almost with 1W by replacing the 2x SS310 diodes on the +8V line with a FERD40L60C diode and using tantalum capacitors on the opposite side of the components.
-
Cool radud5, I love modding.
Would you please explain deeper how and why, so we not only copy you but learn something as well?
-
Diode SS310 have 0,85V for 2A and FERD40L60C have 0,3V for 5A. Total power consumption decreased from 9,9W to 8,9W for 230V/50Hz input. This 1W power is it is released in the form of heat from older diode SS310. The + 8V line voltage is also used to power the -8V converter.
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?
-
I'm guessing this is relevant?
ST - FERD technology outperforms Schottky diodes [2018-07]
https://www.st.com/resource/en/flyer/flferd0718_lr.pdf (https://www.st.com/resource/en/flyer/flferd0718_lr.pdf)
-
Looks Hantek pulled the latest update 20220212 / 20220210 (why do they always have two different dates for each update??) as I'm getting a 404. Either that or they managed to bungle their release procedure... :palm:
Did anyone manage to grab it and/or know why it was pulled?
-
The link of direct download is broken
-
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 :-DD
-
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 new firmware is available for download http://hantek.com/uploadpic/hantek/files/20220214/dso3kb_20220210.rar (http://hantek.com/uploadpic/hantek/files/20220214/dso3kb_20220210.rar)
-
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 :-DD
-
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 :)
-
I have just received a new update package from Hantek.
According to the filename it has an FPGA FW update, so please do your reading and backup your system before attempting to run it.
It is supposed to fix the signal spikes problem using deep memory that quite a few people here experienced.
Links to my original post on this and Hantek's forum.
https://www.eevblog.com/forum/testgear/new-hantek-dso2x1x-models/msg3922370/#msg3922370 (https://www.eevblog.com/forum/testgear/new-hantek-dso2x1x-models/msg3922370/#msg3922370)
https://www.eediscuss.com/forum.php?mod=redirect&goto=findpost&ptid=15897&pid=22951 (https://www.eediscuss.com/forum.php?mod=redirect&goto=findpost&ptid=15897&pid=22951)
I'm uploading it to DavidAlfa's GDrive folder: https://tinyurl.com/ytteeyj7 (https://tinyurl.com/ytteeyj7)
Have not had the time to test it myself yet, maybe during this weekend.
I'm making it available for those who would also like to test.
-
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.
-
I was able to attach an external battery
https://youtu.be/X9miyLbXiQo (https://youtu.be/X9miyLbXiQo)
-
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!?!
-
I charged 22uF/400V capacitor from power source of osciloscoape to 250Vcc from 12Vcc with DC-DC converter https://www.aliexpress.com/item/32892978438.html (https://www.aliexpress.com/item/32892978438.html)
-
What is the power supply output(s) in the scope?
-
What is the power supply output(s) in the scope?
(https://i.ibb.co/cg5HLvT/2.jpg)
-
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.
-
That's just the fpga firmware. The zoom bug seems caused by the dso software.
-
Please make it simple and tidy. I've seen less dense concrete bricks than your message :D
Neither I can test anything as mine is FW 3102.
» Nobody said FW3203 is compatible with existing FW3200/3202. It might be some small design change causing the spikes...
» 2022.02.10 and 2022.02.18 have exactly the same scope software.
» 2022.02.10 doesn't modify the fpga, 2022.02.18 updates it to FW3203.
So please stop using those endless filenames. FW3202 and FW3203 is more than enough.
» Any Hantek update will make a factory reset, you always should calibrate it afterwards.
» Given this, the simplest method would be to stay in 2022.02.10, switching between FW3202 and FW3203 with FW changer, always calibrating before doing any tests.
(https://i.ibb.co/cg5HLvT/2.jpg)
Hmm...
- Step up the battery to 250V to power the mains converter (loses)
- Step down to +-8V , +5V (more loses)
The heavy load goes into the 5V line.
I have to measure it, but +-8V is for the analog frontend and probaly have low consumption, I suspect 200mA at most.
My idea is to replace the power supply with another of 9V 5A, connecting a 4P2S battery (With charging circuitry and protection) to the output, so it'll simply charge from the power supply.
Battery output goes directly to +8V, the other voltages will be sourced by adding a buck converter for +5V and a negative converter for -8V.
Removing the noise from these small 1MHz buck modules should be much easier that 20-40KHz.
I might do nothing in the end! :D
-
Please make it simple and tidy. I've seen less dense concrete bricks than your message :D
Neither I can test anything as mine is FW 3102.
» Nobody said FW3203 is compatible with existing FW3200/3202. It might be some small design change causing the spikes...
» 2022.02.10 and 2022.02.18 have exactly the same scope software.
» 2022.02.10 doesn't modify the fpga, 2022.02.18 updates it to FW3203.
So please stop using those endless filenames. FW3202 and FW3203 is more than enough.
» Any Hantek update will make a factory reset, you always should calibrate it afterwards.
» Given this, the simplest method would be to stay in 2022.02.10, switching between FW3202 and FW3203 with FW changer, always calibrating before doing any tests.
(https://i.ibb.co/cg5HLvT/2.jpg)
Hmm...
- Step up the battery to 250V to power the mains converter (loses)
- Step down to +-8V , +5V (more loses)
The heavy load goes into the 5V line.
I have to measure it, but +-8V is for the analog frontend and probaly have low consumption, I suspect 200mA at most.
My idea is to replace the power supply with another of 9V 5A, connecting a 4P2S battery (With charging circuitry and protection) to the output, so it'll simply charge from the power supply.
Battery output goes directly to +8V, the other voltages will be sourced by adding a buck converter for +5V and a negative converter for -8V.
Removing the noise from these small 1MHz buck modules should be much easier that 20-40KHz.
I might do nothing in the end! :D
Internal power source have on output +8V, -8V, +5V and TR (Line trigger). How to correctly emulate TR output pin?
First attempt is to use 9V/1,5A from any QC2.0 USB phone charger, with QC2.0 trigger https://lygte-info.dk/review/USBmeter%20QC2-QC3%20trigger%20UK.html (https://lygte-info.dk/review/USBmeter%20QC2-QC3%20trigger%20UK.html), and I would have used 2 converters at +7.5V and +5V.
I use 7,5V because I measure 7,5V to +8V line, and DC-DC PWM converter needs a minimum voltage drop.
For the -8V voltage I would have used existing onboard converter, but I got stuck at the TR pin.
Anyway, the consumption is 11W from the 12Vdc source and 9W from the 230Vac power network.
-
You don't care about TR unless you want to sync with mains, which is impossible when you're no longer connected to it, and rarely used anyways.
A 2S batery will output 7.4-8.4V, which is perfect for this application.
The power supply controller is rated for ~24W, so if there's another 10W available, using that power to charge batteries makes it even easier.
Perhabs these diodes will need to be replaced with beefier ones.
Once I wanted to check the car speaker signal, mains power dependence was a little annoying, but battery power isn't something I really need.
-
You don't care about TR unless you want to sync with mains, which is impossible when you're no longer connected to it, and rarely used anyways.
A 2S batery will output 7.4-8.4V, which is perfect for this application.
The power supply controller is rated for ~24W, so if there's another 10W available, using that power to charge batteries makes it even easier.
Perhabs these diodes will need to be replaced with beefier ones.
Once I wanted to check the car speaker signal, mains power dependence was a little annoying, but battery power isn't something I really need.
Without TR pin (I use 1,7V delayed signal) my DSO not booting every time.
-
Might it be a power-ok signal to start the system?
Or a delay to hold the system in reset while the power supply starts?
-
(https://i.ibb.co/q91XZPd/Test-bug-8-Mpt.jpg)
Someone has a fix for high memory bug?
-
Didn't FW3203 work for you?
-
Didn't FW3203 work for you?
I have FW3200
(https://i.ibb.co/YpgRHDN/Firmware.jpg)
-
You should have updated to 3202 already. So try 3203.
-
You should have updated to 3202 already. So try 3203.
I update to latest official firmware from Hantek and hack to DSO2D10 to DSO2D15.
Now have Software 1.0.2.0.0 and unchanged firmware version.
Bugs firmware problems remain, only manifesting differently
Which is the safest way to update firmware?
If I update to the 3203 firmware fix this issue?
(https://i.ibb.co/DVLW0WC/DSO2D15.jpg)
(https://i.ibb.co/3MXdMYp/Test-bug-8-Mpt-d15.jpg)
-
Don't take it bad, but it seems someone is not reading...
Everything about this issue has been said in the last page, also the FAQ was updated to mention this issue...
All you need is to run FW Changer 3203, can be reversed by installing any other FW Changer version (3200, 3202...).
I won't extend further repeating the same again and again: Read the FAQ, then ask if and doubt remains.
-
Bug Report: LowLevel Voltage Adjust
So I converted to 2D15 from 2C10, then updated to latest software 20220210 from 20210726, kept FW @3202, and Scope seems to be probing great/accurate, although when trying to adjust the voltage on the Low Level setting using the AWG the parameters only go down, regardless of which way I turn the knob, is that normal? I can record a video if needed. Everything else is working spot on so far, and no crazy rapid relay clicks anymore with auto set either lol 😅
Side Note/Question: AWG a grounded signal?
I use my AWG to send signals to class D & A/B amps on my bench that I’m troubleshooting/repairing. I use a BNC>RCA converter lug (currently looking for a single bnc to dual rca lug so I can test both channels at once on monoblock amps) and need to know if it’s a grounded signal like a typical headunit in a car environment has, I’m assuming it is being a precise grounded instrument but I wanted to ask and not just assume because it is important to my troubleshooting/repair procedures.
Update/Hack&AWG working great so far though, nice to have AWG to use a 40Hz Sine wave @ 2.5 amplitude, 1v offset (need to read what that offset really is and if I really need it above 000v while running signal through amp) on 1 device instead of hooking up 3-5 additional things to get that signal to amp. 🤓
Thx! 🖖🏼
-
I have updated the FW on my DSO to 3203 and am running SW 1.0.2.0 (20220210.00).
I think the "spikes on the signal" problem has moved from higher resolutions to the 4Kpt and 40 Kpt region now. It occurs on lower time bases (200 ns/Div. and lower). [attach=1]
Then I found another issue (less anoying):
When displaying a stored reference wave as overlay and shutting down and restarting the DSO then the reference info section on top left is still shown. The reference signal is not. [attach=2]
-
I guess you were lucky and your amp was ac-coupled, otherwise you would have blown the speakers.
Offset is the DC compound of the wave.
Normally it should be 0, otherwise the wave would be assymetrical.
In the worst case, you'll make a DC signal with AC ripple, which would push the speakers all the way out damaging the suspension, and if the amplitude is too high or the exposur time too long, burn the coil or even the amplifier.
(https://www.physicsforums.com/attachments/main-qimg-5e73fe9bc855a1f5a7abd6a703f7f27b-convert_to_webp-true-png.206113/)
I have updated the FW on my DSO to 3203 and running SW 1.0.2.0 (20220210.00).
Have you compared 3200, 3202 and 3203?
-
Have you compared 3200, 3202 and 3203?
I have reapplied 3202 and the spikes are gone.
-
I think it's pretty clear that FW3203 is (theorically) only for those having the spikes in FW3202.
Maybe they made a new hardware revision, who knows.
Otherwise, as they say, don't touch if ain't broken :D
-
After update to FW3203 spikes disappear. So far, I haven't had any problems. Thank you for help!
I think it's pretty clear that FW3203 is (theorically) only for those having the spikes in FW3202.
Maybe they made a new hardware revision, who knows.
Otherwise, as they say, don't touch if ain't broken :D
-
This is my first post, however, I have reviewed almost all of the over 900 posts on this thread. I purchased my DSO2D15 based on reviews on YouTube (before I found this forum) and thought it was a great unit for my needs (replacing a Heathkit IO-4205, 5mHz scope). However within one hour of opening my new scope (March 6, 2022), the unit bricked. Cycled the power on and off, pressed buttons, nothing. It just would go through the hardware initialization and then stop, looking at me goofily. Thanks to DavidAlfa and all the others on this thread, I determined that this unit was still worth fighting for; so I wrote to Hantek and within 10 hours, they sent me the link to 烧录 3202.zip including the platform tools. It worked like a champ and I'm back in business. I'll have to update my serial number and other system info because the unit bricked before I knew I should backup the system info with DavidAlfa's backup builder. I uploaded the full file I downloaded from Hantek to the DavidAlfa's Google Drive just in case you can use it; downloading the file was the hardest part of the fix. Thanks again! ;D ;D ;D ;D
-
Thanks PiperFlyer.
I was just going to ask if there is a Platform Tools for the 3200 FW series scopes.
All I found was older versions made for the 3000 series and I was not sure if I could use them in case of a problem.
I guess those could also be used to restore to factory state and then update the FW to 3200. Am I right?
-
Thanks for contributing PiperFlyer, will have a look at the files later :-+
Maxie, yes, you can use any platform tools, as long as you later install FW changer 320x . That's all it needs.
-
Ahhh, so thats why my 10" test sub almost jumped out of its soul ...lol. ty 😅
-
I wanted to test the plataform-tools, but I found my FEL button had failed, so I replaced it.
After that I thought ”why not?” and also clamped two long heatskinks over the ADC/FPGA with some cpu thermal paste, making a clampling thingy with a thin metal plate.
Didn't like the idea of glueing them with hardening paste, I've seen terrible things when removing the heatsink later...
-
they sent me the link to 烧录 3202.zip including the platform tools.
After using this platform-tools, if you short press the DEFAULT SETUP button you'll get the known default menu1, but if you keep this button pressed a little longer you'll get a new default menu2. If you'll choose in this menu 'Wave Gen', you'll get the next screen (default menu3).
-
This is the known menu that appears when the file ”/dso/app/Square_cusp.tmp” exists.
But at the moment it's useless, also USB won't work correctly until apply the USB fix patch.
-
This is the known menu that appears when the file ”/dso/app/Square_cusp.tmp” exists.
When the file ”/dso/app/Square_cusp.tmp” exists I knew only two-points Calibration menu (Amplitude and Offset), but not this default menu.
-
Oh, yes, it also enabled that menu by long-pressing the setup button.
It's mentioned somewhere in this 39 pages :D
-
Is this common for Scopes in general or is this a bug with this scope? I have limited scope experience (only this and a small handheld) I’ve tried calibrating but the discrepancy still exists and is many volts over when using 20v/50v/100v. Another weird thing is when I activate the 2nd channel the large offset seems to switch to the 2nd channel and the 1st drops down to mere mV like it seems it should be. Any reasons for this? Limiting BW doesn’t help, has this already been discussed and I missed it? (Tried searching through multiple threads) or am I just pulling a cliché newb mistake not doing something/assuming something? Is about 5v on the dot off per my DMM when on 50v/div. what needs to be done to fix this and/or is this just a symptom of a “budget” scope ...in parentheses cuz this isnt very budget to me atm 🥴 lol!
Pics below show the 3 highest voltage divisions being the worst and the switcharoo when 2nd channel activated
https://imgur.com/a/edxIRvz
-
Off by 7V at 100V/div? What do you expect at 100V/division?
Every pixel will be like 10 volts, and the noise will do the rest. Normally you adjust the scale to the signal voltage.
The scope has to scale the input, and ADC the precision is just 8 bit. Only high-end equipment($$$) will have better ADCs.
There're 8 vertical divisions, so:
8*100V= 800V, divide that by 256 and you get 3.1V/bit.
But it seems the scope actually fills 10 divisions, so:
10*100V= 1000V, /256 = 3.9V/bit.
1-2 bit error is something expected on this scope, lower noise belongs to the expensive market!
Use the correct tool for the job! A scope is not a DMM, its function is to display waves.
Even most DMMs will have poor accuracy in higher ranges.
-
Hi all.
I've had my DSO2D15 for about two weeks now. The scope have worked fine most of the time. Only a few freezes.
But today shit hit the fan. While just playing around I was changing the memory dept and as it scrolled past 8Mpt the unit freezed.
I thought power cycling would make it work again. It didn't.
Now when I power it on no trace appears. If I press the menu buttons the menu appears but it freezes instantly if I try to change anything.
Is there anyone that have had the same problem and what did you do to fix it?
I thought i would just ask before re-flashing with the platform tools first. but if it will be the case I'm lucky to have run the backup- and eprom builder.
-
Dosn't matter anyway. the unit is completely dead. Only the buttons light up when trying to boot in FEL mode.
-
Have you tried "Default setup" button?
Whats your sw and fw version? (Utility/system info screen)
-
Hi david. I have pretty much pressed every single button in every single order.
I've gotten the scope to work and proved the monkey theorem to be true: https://en.wikipedia.org/wiki/Infinite_monkey_theorem
It would lock up either instantly or after a few presses. "Default setup" among other buttons made it freeze instantly everytime.
Sometimes i could navigate in the different menues for longer before frezzes. Then i took a wild card, loaded firmware to an USB stick and after a few tries I was able to make it upgrade. With the same firmware version though (3202).
Then it upgrated and worked thereafter :-/O
The software is: 1.0.1.1.0(20210726.00).
Btw thanks to you David and all other for all your contributions and effort in making this scope usable. It's much appreciated :-+
-
Now you can upgrade to the latest software right away.
Are you sure you weren't in FW3200? Crashing when handling the buttons is a known issue in that version.
-
Which would be 2022.02.10 Right? I can't load hantek.com, tried several times.
Somehow I thought I had the latest software.
100% sure it was 3202. Thanks to you that I took a picture of it.
-
Yep, that's the latest.
-
There's a new user manual posted:
http://hantek.com/products/detail/17182 (http://hantek.com/products/detail/17182)
http://hantek.com/uploadpic/hantek/files/20220326/DSO2000%20Series%20Digital%20Storage%20Oscilloscope%20User%20Manual.pdf (http://hantek.com/uploadpic/hantek/files/20220326/DSO2000%20Series%20Digital%20Storage%20Oscilloscope%20User%20Manual.pdf)
pg17 added:
3. HORIZ MENU
XY mode
The XY mode is used to analyze phase differences, such as those represented by Lissajous patterns. The format plots the voltage on CH1 against the voltage on CH2, where CH1 is the horizontal axis and CH2 is the vertical axis. The oscilloscope uses the untriggered Normal acquisition mode and displays data as dots.
The oscilloscope can acquire waveform in YT mode at any sampling rate. You may view the same waveform in XY mode. To perform this operation, stop the acquisition and change the display mode to XY.
Roll mode
In Roll mode, the waveform display rolls from right to left. No trigger or horizontal offset control of waveform is available during Roll Mode, and it’s only available when set to 100ms/div or slower.
pg49 removed:
Display Mode, 2.12.2. XY Mode, 2.12.3. Roll Mode
added:
Category Real Time Acquire waveforms by real-time digital technique.
Equ-Time Rebuild waveforms by equivalent sample technique
pg 63 added:
Equivalent sampling 50GSa/s
-
Someone measured real rise time? I connected the probe(UT-H05 200Mhz 1:10 and oscilloscope in pulse mode), to 100V DC source and measured minimum rise time of 5ns, equivalent to 70Mhz bandwidth, which is too little for DSO2D15.
What is the relationship between oscilloscope bandwidth and waveform rise time? (https://www.fluke.com/en/learn/blog/oscilloscopes/what-is-the-relationship-between-oscilloscope-bandwidth-and-waveform-rise-time)
-
Someone measured real rise time? I connected the probe(UT-H05 200Mhz 1:10 and oscilloscope in pulse mode), to 100V DC source and measured minimum rise time of 5ns, equivalent to 70Mhz bandwidth, which is too little for DSO2D15.
What is the relationship between oscilloscope bandwidth and waveform rise time? (https://www.fluke.com/en/learn/blog/oscilloscopes/what-is-the-relationship-between-oscilloscope-bandwidth-and-waveform-rise-time)
I was playing with pulse generators, I build 2 and I'm getting good results (with some ringing).
I build a generator based on the 74HC14 inverter, but I can't remember from where I got it.
And the second it's an Avalanche pulse from Kerry Wong (Jim Williams)
http://www.kerrywong.com/2013/05/18/avalanche-pulse-generator-build-using-2n3904/ (http://www.kerrywong.com/2013/05/18/avalanche-pulse-generator-build-using-2n3904/)
BTW, I was under the impression that 30V was de max input voltage at 1x ::)
Use the 4K memory depth to see if there's a difference, probably will be, and using probes maybe is not a good idea, I used a ~50cm SMA-BNC cable.
-
After few hours of Power On wave generator stop to working. Now have only DC component with 3,8V, whether the generator is on or not.
Can anyone help me with what to start checking?
Can you hear the relay sound when changing trigger source from other options to external? This would indicate if the relay that switches between ext trigger and wave gen is working.
Next thing I'd check would be analog +-8V and +-5V (1st picture).
And next, voltages and signals around the wave generator's DAC and Op Amp (2nd picture). The pinouts are in the attached datasheets
-
Now I'd like to ask a question... I received my DSO2D10 a few days ago and wanted to try the "remote control" from PC, but I have a doubt about what software to install.
On Hantek's website downloads page (http://www.hantek.com/download?key=yyrj&sid=3&pid=17182&word=), there's a link (http://www.hantek.com/uploadpic/hantek/files/20210916/HantekDSO2000_Ver1.0.3.zip) to a file called HantekDSO2000_Ver1.0.3.zip, which contains IOLibSuite_17_2_20605_2.exe dated 03/07/2016 (quite old!).
On the other hand, in the user manual (http://www.hantek.com/uploadpic/hantek/files/20220326/DSO2000%20Series%20Digital%20Storage%20Oscilloscope%20User%20Manual.pdf) (chapter 4) there's a link to a Keysight's download page (which ends redirected here (https://www.keysight.com/es/en/lib/software-detail/computer-software/io-libraries-suite-downloads-2175637.html)), where you can find Keysight IO Libraries Suite 2022 and Keysight Secure Instrument Communication Expert.
Keysight IO Libraries Suite 2022 seems to be the updated version of the software on Hantek's page, so I understand this should be the better option unless the scope's internal firmware is not compatible with this update.
Can anyone advise me which one should I install?
-
HantekDSO2000_Ver1.0.3.zip only has the name 1.0.3 in reality its content is 1.0.1 (see picture)
As for the 2016 IOLibSuite_17_2_20605_2.exe, the reason is that the program itself was created in 2017 and has not changed since then. I installed it last September without trying it out. I am not currently on my machine because I am using the scope directly. :-D
-
Morgan, all it takes is installing and testing, don't be lazy, just try and check yourself and report the result :-+
The worst that could happen is having to remove it and install the older version.
-
After few hours of Power On wave generator stop to working. Now have only DC component with 3,8V, whether the generator is on or not.
Can anyone help me with what to start checking?
Can you hear the relay sound when changing trigger source from other options to external? This would indicate if the relay that switches between ext trigger and wave gen is working.
Next thing I'd check would be analog +-8V and +-5V (1st picture).
And next, voltages and signals around the wave generator's DAC and Op Amp (2nd picture). The pinouts are in the attached datasheets
Relays from channel out AWG module, switch when external trigger is selected
All power line voltages is good:
5V = 5,00V
-5V = -5,00V
1,9V = 1,92V
1,1V = 1,09V
3,3V = 3,30V
5V = 5,06V logic
2,8V = 2,77V
I have no signal on output pins 21 and 22 from U35 DAC902. I tested with other DSO.
There is a possibility that by change FW3200 to FW3202 to damage/burn the AWG module (uC or DAC)?
I tried default firmware from full backup, no positive results
-
Nobody had issues when changing FW except getting calibration issues.
Are you sure you didn't connect the generator output wrong, ex. to some external power, causing it to blow up?
-
Nobody had issues when changing FW except getting calibration issues.
Are you sure you didn't connect the generator output wrong, ex. to some external power, causing it to blow up?
It burned after I forgot device ON with the AWG module active for 4 hours, on a load of 1KOhm resistor.
I installed radiators (glued with Arctic Silver Thermal Adhesive) and a fan.
(https://i.ibb.co/SsV5WTt/00000.jpg)
-
Perhabs a poor soldering joint?
Did you install the heatsinks before or after the problem?
Could it be they're touching something in the board?
-
Perhabs a poor soldering joint?
Did you install the heatsinks before or after the problem?
Could it be they're touching something in the board?
I installed heatsinks 2 months ago.
I checked before mounting to keep the distance from the components below, and use kapton tape
What is the function of the switch on the back side of PCB?
(https://i.ibb.co/VLmWX9n/20220211-194048-Copy.jpg]https://i.ibb.co/VLmWX9n/20220211-194048-Copy.jpg)
(https://i.ibb.co/KsQBbJF/20220402-133603-Copy.jpg]https://i.ibb.co/KsQBbJF/20220402-133603-Copy.jpg)
(https://i.ibb.co/ZXHh9sn/PCB-Copy.jpg]https://i.ibb.co/ZXHh9sn/PCB-Copy.jpg)
-
What is the function of the switch on the back side of PCB?
(https://i.ibb.co/ZXHh9sn/PCB-Copy.jpg]https://i.ibb.co/ZXHh9sn/PCB-Copy.jpg)
Before using the platform-tools you need to press and hold this button down and than turn on the scope. It will boot the scope in recovery (FEL) mode.
-
This is FEL button, read more here: https://www.eevblog.com/forum/testgear/hantek-dso2x1x-firmware-updates-and-best-use-practices/ (https://www.eevblog.com/forum/testgear/hantek-dso2x1x-firmware-updates-and-best-use-practices/)
-
I need someone who can test a flash tool I'm working on, it's able to backup and restore the whole flash from FEL (Bootloader) mode.
It's important to understand it's in testing stage and you might need to recover it using an external spi programmer.
I managed to lock my flash twice by sending corrupted data, platform-tools didn't work anymore, had to remove the flash and erase it using a CH341A to make it work again.
It didn't happen again since I fixed the code, but I must give a serious, proceed-at-your-own-risk warning!
I'm doing my lasts tests, if it keeps working everytime without any issues, I'll release the tool for the brave.
It's not really required, as platform-tools + Backup Builder will do the job, but it's always nice to have a complete 1:1 backup.
Reading takes 50 minutes and writing 25.
-
I need someone who can test a flash tool I'm working on, it's able to backup and restore the whole flash from FEL (Bootloader) mode.
It's important to understand it's in testing stage and you might need to recover it using an external spi programmer.
I managed to lock my flash twice by sending corrupted data, platform-tools didn't work anymore, had to remove the flash and erase it using a CH341A to make it work again.
It didn't happen again since I fixed the code, but I must give a serious, proceed-at-your-own-risk warning!
I'm doing my lasts tests, if it keeps working everytime without any issues, I'll release the tool for the brave.
It's not really required, as platform-tools + Backup Builder will do the job, but it's always nice to have a complete 1:1 backup.
Reading takes 50 minutes and writing 25.
OK David, I could test your flash tool. I have all to do it without any problem. So, where could I get the tool?
-
Update:
Added DSO Flash Tool (https://drive.google.com/drive/folders/1xxA6giTkRFiKsF7UhHxGSISmadGx52mC) to Drive and updated the FAQ section.
-
Morgan, all it takes is installing and testing, don't be lazy, just try and check yourself and report the result :-+
The worst that could happen is having to remove it and install the older version.
OK, after asking also in Hantek's semi-official forums (https://www.eediscuss.com/forum.php?mod=viewthread&tid=15607&page=7#pid23348), I installed Keysight IO Libraries Suite 2022 (https://www.keysight.com/es/en/lib/software-detail/computer-software/io-libraries-suite-downloads-2175637.html) and I can confirm it works correctly :-+.
I preferred to ask because apart from being lazy (I recognize I am... ;D), I'm not very fond of installing and uninstalling things, as I think (maybe it's a conspiracy theory) they tend to leave garbage in my not very powerful computer during the process, so if I can go to the best option at the first try, I'd better do that.
By the way, while experimenting with SCPI, I found another way to set the internal clock of the scope (https://www.eediscuss.com/forum.php?mod=viewthread&tid=16000&page=1#pid23359) alternative to David's method (https://www.eevblog.com/forum/testgear/hacking-the-dso2x1x/msg4090234/#msg4090234). The details are at the previous link, but I'll post them also in the hacking thread.
-
I extracted the scpi commands long time ago here (https://www.eevblog.com/forum/testgear/hacking-the-dso2x1x/msg3581870/#msg3581870)
-
I extracted the scpi commands long time ago here (https://www.eevblog.com/forum/testgear/hacking-the-dso2x1x/msg3581870/#msg3581870)
Yes, I quoted your post when describing the method in the hacking thread (https://www.eevblog.com/forum/testgear/hacking-the-dso2x1x/msg4097584/#msg4097584). Very interesting list, especially the PRIvate set, though a bit scary to try them without documentation (impossible to find, I imagine).
Also curious the result of "SYSTem:RAM?" that, according to the SCPI Remote communication control manual for DSO4000BC (http://www.hantek.com/Product/DSO4000BC/DSO4000BC_SCPI_EN.pdf), reports the number of analog channels, 4 in that case (is a 4 channel scope) but also reports 4 in this one :P
-
No idea, but anyways I expect a lot of bugs on that side.
I really doubt you can break anything as long as you made your backups (builder+Eeprom).
-
I need someone who can test a flash tool I'm working on, it's able to backup and restore the whole flash from FEL (Bootloader) mode.
Hi David. I've tested your tool. Something is wrong with the memory size of the flash. Your tool defines the memory size as 138412032 bytes (132MB) (see disoflash_begin.jpg and disoflash_end.jpg), while the NeoProgrammer with CH341A defines the memory size as 132217728 bytes (128MB)(see NeoProgrammer.jpg). In the original memory dump that was read by the tool at address 06e007f0 there are 16x00 and then at address 06e00800 - 16xff, and in the backup.bin file at address 06e007f0 16xff and then at address 06e00800 16xff.
-
It's not wrong, this tool includes the ECC area, that's why the final size is 132MB, and only a backup of that size will be allowed when writing.
If the file and flash size differ, in will show an error and block the write.
I might add checksum verification in the future, but I'm way tired of this device.
You can get the same reading with the CH341 selecting "Read OOB area".
By restoring the original ECC, you would have a chance if the backup was corrupted, but without it it'll be gone.
-
It's not wrong, this tool includes the ECC area, that's why the final size is 132MB, and only a backup of that size will be allowed when writing.
Hi David. Using your tool I wrote the backup.bin file renamed as restore.bin to a flash memory, then read the contents this flash memory using the programmer CH341A, saved the read to a file and compared this file with the original file with the damp that was written to the flash memory before reading it with your tool. The files are identical. So everything works. Than you for your tool.
-
You can get the same reading with the CH341 selecting "Read OOB area".
Where (which programmer-software) did you find this option?
-
Check NeoProgrammer.
It's also uploaded in the Drive folder (Hacking/CH341...)
-
Check NeoProgrammer.
It's also uploaded in the Drive folder (Hacking/CH341...)
I've got it In the NeoProgrammer 2.2.0.10. You need to check the box against "Read/Write with spare area". Then the NeoProgrammer reads/writes 138412032 bytes. Did you mean this with selecting "Read OOB area"?
-
Yes, my bad. Spare area, OOB(Out Of Band) area, ECC area...it's the same thing.
That area is reserved for ECC when enabled, or can be used as regular storage when disabled.
Anyways, remember it's a writable filesystem, two backups will probably be different if the scope was started between them.
-
Yes, my bad. Spare area, OOB(Out Of Band) area, ECC area...it's the same thing.
That area is reserved for ECC when enabled, or can be used as regular storage when disabled.
Anyways, remember it's a writable filesystem, two backups will probably be different if the scope was started between them.
In continuation of testing of your dsoflash-tool I've got two files of 132MB from the same flash memory, one using CH341A programmer with "Read/Write with spare area" option and the second one, using your tool from my scope. The both files are identical. So it works.
In my opinion it would not be superfluous to mention in the tool-Readme.txt file about this Spare area, OOB(Out Of Band) area, ECC area, to explain why the tool reads 132MB from flash memory but not 128MB and to say about the "Read/Write with spare area" options of the NeoProgrammer.
-
hello im giorgos from greece today arrived my hantek and hacked to 2d15 works ok
just a question how i can apply overclock
download the file from gdrive but how im going to alter the multipliers
-
Isn't clear in the readme?
The system will execute the file overclock/oc_manager from the usb drive. If there's no drive, overclock won't be applied.
Now you can try rising the CPU_OC_PLL_N multiplier in that file, rebooting each time to apply the new settings.
overclock/oc_manager
# Effective frequency is (BASE_FREQ*(N+1)*(K+1))/(M+1)
# Possible values:
# PLL_N: 1-31
# PLL_K: 0-3
# PLL_M: 0-3
# ------ USER ADJUSTABLE ------
# This example: (24*(26+1)*(0+1))/(0+1) = 648MHz
CPU_OC_PLL_N=26
CPU_OC_PLL_K=0
CPU_OC_PLL_M=0
# This example: (24*(13+1)*(0+1))/(0+1) = 336MHz (168MHz DDR)
MEM_OC_PLL_N=13
MEM_OC_PLL_K=0
MEM_OC_PLL_M=0
-
done thank you oc to 668 336 mhz
-
Don't buy this crap. Seriously.
I've trying to follow 50MHz signal pulses lasting 50-100us.
Larger Time division than 10-5us shows nothing or garbage.
In the zoom view, you can't scroll through the whole screen, so another useless feature.
SPI decoding keeps failing. No *** way to decode anything.
*** Hantek designers. Never again. Not even free, damn.
This scope is just crap.
DavidAlfa, thanks for all your work on this. I recently retired and was thinking about getting 2D10 after using Hantek DSO8060 at work for many years; but now turned off due to the bug reports here and elsewhere. What's your recommendation for a reliable and accurate budget 50/100MHz scope? I mainly work on audio gear and general electronic design/repair work but have some STM32F4DISCOVERY and other micro-controller projects.
https://www.eevblog.com/forum/testgear/new-hantek-dso2x1x-models/875/ (https://www.eevblog.com/forum/testgear/new-hantek-dso2x1x-models/875/)
-
It was a quite good offer at the release price, around $200, but now people seems to get it for almost $400!
What can I recommend having a 2D15 myself? All I can say is get anything but Hantek!
I'd make a new thread asking for options given a price tag, for sure you'll get a lot of nice feedback from experienced people.
-
It was a quite good offer at the release price, around $200, but now people seems to get it for almost $400!
What can I recommend having a 2D15 myself? All I can say is get anything but Hantek!
I'd make a new thread asking for options given a price tag, for sure you'll get a lot of nice feedback from experienced people.
Thx for the reply. 2D10 still available for AUS $320 (US $240) in Australia, but I want something trustworthy. I will take up your suggestion to start a new thread.
-
I just got a very weird crash that managed to brick the scope!
Changed the memory depth to 4M, after few single shots the scope suddenly crashed with the plot area full of random green lines.
On reboot, all it showed was an empty grid, completely unresponsive to any button press.
Had to use platform-tools to recover it!
-
Edit: I zoomed until finding the smallest step. What Hantek is showing on screen is definitely BS.
Testing with 50MHz SPI signal in 1us/div
- 4Kpt shows 250MSa/s, waveform is acceptable, missing details due the lower sample rate, resolution is 4ns.
- 40Kpt shows 500MSa/s, shows garbage. Resolution is 8ns, that's 125MSA/s, bast***s!
- 4Mpt shows 125MSa/s and is 8ns, looking as expected due sampling limitations.
- Testing with 1.56MHZ SPI signal, 50us/div
- 4Kpt shows 5MSa/s, waveform lacks a lot of details but is never missing clocks, resolution is 200ns.
- 40Kpt shows 50MSa/s, but clearly isn't. Resolution is mostly 400ns. That's 2.5MSA/s.
Strangely, sometimes there're 200ns steps. What the hell is going on?
- 4Mpt shows 125MSa/s. Should I laught? Resolution is 400ns. That's 2.5MSA/s, liars! Looks almost the same as 40Kpt,
-
Don't know the Gowin FPGA, but having done some playing around with the Anlogic FPGA in the FNIRSI-1013D I think running sampling at 500MSa/s is not that simple. Also the phenomena mentioned by others that when selecting more sample memory things get messed up might be a problem with pushing the FPGA to its limits.
It might be interesting to do measurements on the ADC clock to see if it is actually sampling as fast as they say it is. Maybe whenever I feel like doing it, I will hook up my DL9705. Still only a bandwidth of 500MHz so no square wave, but it should be able to show if it is running at 500MHz clock.
-
I'm annoyed because it's lying, not because it's not capable of doing 500MSa/s everywhere.
I want to measure a 50MHz signal,so I setup everything, run a single shot, finally capture that hard-to-catch signal... but then, zooming in shows garbage, 4 pixels dancing, because clearly it wasn't sampled at the advertised speed.
I must know the real sample rate to avoid that! How am I'm going to trust anything if it says 500MSA/s and it's doing 2.5MSa/s?
Show me the real, usable sample rate! |O
Obviously Hantek wants to sell the big numbers: 1GSa/s!! 8M depth!!
(In very specific and limited conditions which aren't going to tell anyone, you'll discover after buying hehehe...)
So if I knew the only usable memory depth at 1GSa/s was 4K, maybe I would have bought a different dso.
There were other candidates that "only" had 140K, 400K, but if they did so at 1GSa/s, it would have been a completely different story!
-
Well if the assumption about the ADC hardware is correct it is capable of doing 1GSa/s. That makes it less of a lie compared to the FNIRSI-1013D and 1014D. They have 1GSa/s printed on the front, but only have 100MSa/s per ADC hardware in there. With 2 ADC's per channel still only 200MSa/s. Also on the back of the device a label that states 240Kbits of sample memory, which is also false because most of the time it only uses 1500 bytes (12000 bits) per channel.
So FNIRSI is a bigger liar then Hantek :-DD
I agree that knowing the truth about these devices would most likely drop sales and steer people to the better brands. You have to pay more for sure, but do get better equipment.
-
Haha, damn liars.
What initially seems a "good" idea to boost sales, is going destroy their already weak reputation.
If tomorrow Hantek releases a new DSOxxxx with 12" UHD screen, 24-bit 10GSA/s ADC, 100M depth, 16ch, and for just $500, will I buy it?
NO :-DD
Hah, the SPI decoder can't handle more than 16-20MHz... (0x29 is the correct one)
-
Here is why it can't use the memory when sampling at 1GSa/s, at least if the FPGA used is a GW2AR-18. It has the required number of LVDS pairs to connect the ADC.
The SDRAM in the FPGA has a max clock of 166MHz with a 32 bit wide data bus. The ADC delivers the data also 32 bits wide but with a clock of 250MHz when sampling on 1GSa/s, or with 2 channels enabled on 500MSa/s. At least if the ADC is the ADC08D500 mentioned before.
For these higher sampling rates it can use the BSRAM of which it has 828Kbits. This memory can clock up to 380MHz. But still a FPGA design running on a master clock of 250MHz takes skill.
-
I know these limitations, as I already said, I'm not blaming the hardware, but HANTEK.
Should I need to reverse-engineer the whole thing to get the real specs? Absolutely not.
As far as I remember, the ADC can pack the data, that's why it can provide 1GSA/s at 250MHz, each transfer is made of 4 8-bit samples.
The part that annoyes me most is the 40K issue. Says 500MSa's, so it should be great for zooming into small details, but it's complteley useless.
Another day in paradise ::)
-
David, is there a way to determine the frequency at which the central CPU and the memory operate? What are the default CPU and memory frequencies? Thanks in advance.
-
Check the F1C200s manual, also the OC package.
You can read the CPU/SDRAM PLL registers, which is what the script does.
Default is 408MHz CPU, 156MHz RAM.
Start with only the CPU, usually 600MHz is a safe start point, but as long as you use the "test" variant of the script, the values are read from the USB, so there's no risk.
The RAM is more picky, might not overclock at all, and will rarely reach 192MHz in the best cases.
Mine runs 792/180. I have a light overvolt 0f 80mV (1.18V).
Recently, reading the registers I found the I2C bus was running at only 46KHz.
Not sure if it's on purpose to reduce signal noise or a bug, but it worked well past 600KHz, even 800KHz, I noticed a better system response, expected since the FPGA is controlled using this bus.
Run these commands for the desired speed. If it crashes, just cycle the power, it's not permanent.
# Set I2C bus to 46KHz (Default)
devmem 0x1C27014 32 0x63
# Set I2C bus to 400KHz
devmem 0x1C27014 32 0x12
# Set I2C bus to 600KHz
devmem 0x1C27014 32 0x0A
# Set I2C bus to 800KHz
devmem 0x1C27014 32 0x11
Also tested increasing the internal bus speed from 600 to 768MHz, this caused some issues as the peripherals use this clock, could reconfigure the serial port baudrate register but still in testing stage.
I think the overall system bottleneck is the communication between the CPU and FPGA.
Needs a lot more testing before I release anything.
-
# Set I2C bus to 46KHz (Default)
devmem 0x1C27014 32 0x63
# Set I2C bus to 400KHz
devmem 0x1C27014 32 0x12
# Set I2C bus to 600KHz
devmem 0x1C27014 32 0x0A
# Set I2C bus to 800KHz
devmem 0x1C27014 32 0x11
What is the way to run the command?
-
Thanks David for what you are doing.
I have a light overvolt 0f 80mV (1.18V).
you can learn more about how to get 1.18 volts?
-
Serial port or Script Launcher (check the FAQ), also in overclock files, you could append it at the end of oc_manager and oc_manager_test.
The regulator requires modifying the resistor feedback in the board, I don't recommend that unless you know what you're doing, any mistake could fry everything with 5V.
Stock voltage will usually work up to 648-696MHz, doesn't really worth the risk.
-
Can you show the elements of the feedback controller? I understand my responsibility if it fails.
Thanks
-
Oh David, thanks for the hard work!
oc_manager_test
CPU_OC_PLL_N=28
MEM_OC_PLL_N=16
# Set I2C bus to 800KHz
devmem 0x1C27014 32 0x11
DSO has become more responsive! Work has become more convenient!
-
Check this (https://www.eevblog.com/forum/testgear/new-hantek-dso2x1x-models/msg3588847/?topicseen#msg3588847), this (https://www.eevblog.com/forum/testgear/new-hantek-dso2x1x-models/msg3597744/#msg3597744) and the attached picture.
Remember the 1.1V rail also powers the FPGA!
That RAM is a a bit too high. You'll know if it feeezes when booting from cold. Or you might be lucky!
I also tried overvolting the RAM, but any higher had a negative impact.
-
Remember the 1.1V rail also powers the FPGA!
I plan to power the processor from a separate voltage source. I cut off the tracks.
Any information on the processor model?
-
What about reading this thread, also the "Hacking" one? F1c200s everywhere. Datasheet on my Drive...
-
What about reading this thread, also the "Hacking" one? F1c200s everywhere. Datasheet on my Drive...
There are translation problems. I would be grateful if you answer the obvious questions with a link. This will be enough.
Thank you.
-
Check the f1c200s datasheet and user manual here (https://drive.google.com/drive/u/0/mobile/folders/1Tqk8YbL_M3S0vtk7h_cZ-01U2idIaqqx/1vYFqXzPl2nOZJnx58TLhZa37cmvpqkPY/1nVjMQXBddGlOT5StQ0Igod7n0qDl0spg?sort=13&direction=a)
-
I'm looking at getting one of these but have a question...
Is it worth chancing the AWG components will be on the delivered unit and getting the 2C10 or should I just go for the 2D10?
Glen.
-
I haven't had time to play around with the oscope the past 1 or 2 months, but this weekend I found some more bugs.
I see DavidAlfa discovered a lot of issues as well. Do you guys report these findings to Hantek?
What happened to the initiative of collecting all problems found in a central document? Is it still a thing?
-
I'm looking at getting one of these but have a question...
Is it worth chancing the AWG components will be on the delivered unit and getting the 2C10 or should I just go for the 2D10?
We can't answer this question. You have to decide if you need/want the AWG func.
Look at it this way. How much will you be disappointed if you chance it and don't get it.
What is the price diff? How much is the stress/peace of mind worth?
I, for one love the AWG. People say its dumb/simple. Maybe it is, but it's damn better than a 555 sq wave gen.
Probably they compare it to a 1000 bucks Keithley or something.
It's got many different waveforms, adjustable freq, amplitude, DC offset, duty cycle, several modulation types and even those have more settings.
I only wish there was 2 of them. Now I want to get another AFG, but they cost too much, and I would probably only use it for f*kin about with XY mode.
-
The 2C10 is running at AU$259 and the 2D10 is running at AU$319 on amazon.com.au at the moment, so not a huge difference.
I think I could make use of the AWG (one less thing to need to put together/buy) so my thinking is I'd go with the 2D10 and flash it up to a 2D15 from there.
Does overclocking it required the passive heatsinks and a fan installed, or can it handle it with just the heatsink? (not that it seems a hard mod)
Thanks for your reply Maxie, you basically just validated my thinking.
-
I'm looking at getting one of these but have a question...
Is it worth chancing the AWG components will be on the delivered unit and getting the 2C10 or should I just go for the 2D10?
Glen.
If it helps any, I hummed and hawed over the same question and eventually decided the awg would be nice to have but it was really a 'scope I was interested in so took a punt on the C10. I ordered from Banggood on 23rd March and I now have a fully functional D15. Worked out well for me but of course YMMV.
-
Cyril has uploaded a new 3204 fpga FW that was factory installed on his new scope.
I'd like to test it, but it's a BIN file, it should be UPK.
DavidAlfa, could you please create a FW changer for it?
-
Added.
-
I tested 3204 on my fpga, it works fine. I used to have the signal spikes issue with 3202 on deep memory settings that was fixed in version 3203. I could not find any difference playing with all kinds of waveforms and timebases on both channels for half an hour.
I wonder what they changed in this new version. Maybe while in there they found something else we don't know about, or could be they just standardized the latest fpga FW to work on all scopes. I remember some folks had problems when testing 3203.
If anyone tests please report back if you see any differences.
Me, I'm staying on 3204 for now, untill I find something that's wrong.
-
Hi all,
I'm the one who uploaded the 3204 firmware. I didn't managed to get the UART decoder to work properly up to now. I can trigger on specific data for example, this works nicely but I never managed to see the live decoding. The purple text is always showing "please, adjust the time base". Do you guys manage to get it work? Is this a regression from 3204 (I doubt but who knows).
Thanks
-
The decoder in this device is pretty tricky!
- Set same trigger as the decoder.
- Select "Normal" trigger mode instead "Auto", that way it holds the last trigger instead keeping rolling.
SPI is worse, but not impossible.
You have to adjust the level of both SCL and SDA to set the logic thresholds or it will display garbage.
Also play with the overtime setting, it seems the SPI packet must finish before the trigger start, or the decoder fails.
-
The UART trigger and decoding are worth reading here, maybe it will help. This is the latest manual.
http://www.hantek.com/uploadpic/hantek/files/20220326/DSO2000%20Series%20Digital%20Storage%20Oscilloscope%20User%20Manual.pdf (http://www.hantek.com/uploadpic/hantek/files/20220326/DSO2000%20Series%20Digital%20Storage%20Oscilloscope%20User%20Manual.pdf)
-
The UART trigger and decoding are worth reading here, maybe it will help. This is the latest manual.
http://www.hantek.com/uploadpic/hantek/files/20220326/DSO2000%20Series%20Digital%20Storage%20Oscilloscope%20User%20Manual.pdf (http://www.hantek.com/uploadpic/hantek/files/20220326/DSO2000%20Series%20Digital%20Storage%20Oscilloscope%20User%20Manual.pdf)
Thank you but I already read that manual a few times. Nothing really interesting regarding the decode feature (and why it might not work properly).
-
I didn't managed to get the UART decoder to work properly ... never managed to see the live decoding.
The purple text is always showing "please, adjust the time base".
Any update on this? I can't test, have no UART devices.
Maybe post a screenshot of what you see.
-
Any update on this? I can't test, have no UART devices.
Maybe post a screenshot of what you see.
Sorry, no success so far. I gave up for now. I try to post a few screenshot in the coming days. Thank you.
-
Hi all.
So I receive a set of "P2200" probes, the probes are OK but the interesting part it's that includes a probe-to-BNC adapter (don't know if they have a specific name), so I made a few tests regarding to the scope noise at 10X, the test proposed by @radud5 (https://www.eevblog.com/forum/testgear/new-hantek-dso2x1x-models/msg4002556/#msg4002556) and replied by @Maxie (https://www.eevblog.com/forum/testgear/new-hantek-dso2x1x-models/msg4005121/#msg4005121) where he mentions that the problem it's the test setup, and yes, I think he's correct.
The proposed test it's at 100mVPP@100KHz using a 10X probe, I made the test at 100mVPP, 50mVPP, 20mVPP and 10mVPP at 100KHz.
I just wonder how this compares with other scopes with similar BW, I think that this scope it's a bit pround to ringing issues but not entirely sure if this a setup issue too or a mix of both.
I think that the scope noise it's not the best but also isn't the worst, seeps pretty acceptable, isn't?, what do you guys think?
-
Nice, comprehensive test, you really put some time into it.
-
Sorry, no success so far. I gave up for now. I try to post a few screenshot in the coming days. Thank you.
Try loading this nude stealer virus setup. Set for 3.3V level, 115.200baud.
I think that the scope noise it's not the best but also isn't the worst, seeps pretty acceptable, isn't?, what do you guys think?
Thanks. I always had very similar results.
This test are similar, first is using the probe gnd clip, second is making direct contact to the probe gnd ring.
The difference is huge, I guess it's a probe thing? I mean, they cost $5 in pairs... I don't think they it can perform like expensive ones at all?
Anyways I didn't expect so much signal difference by a 60mm thick gnd wire... But I guess that's high frequency magic, all sort of weird things start to happen :)
It's also interesting how the average looks!
-
Try loading this nude stealer virus setup. Set for 3.3V level, 115.200baud.
Thank you DavidAlfa. I tried your setup. I didn't see any improvements (nor any nudes) :'( My serial adapter outputs 5V but I doubt this makes any difference here.
That decode feature is just not working as it should. If I use your setup without any modification, it complains about no trigger but the scope just trigger as expected :-\ If I set the scope to single sequence, it triggers but now complain that I have to adjust the time base >:( Of course, adjusting the time base does not change anything.
And to make everything even more weird, the scope triggers perfectly if I ask it to trigger on specific data :o Somehow it must be able to decode the protocol but that live decoding purple thing (nor the monitor) is able to display any data. I give up.
-
That's a weird uart signal, it's inverted! Try setting Idle level=Low
In trigger=start, the trigger starts exactly at the first falling edge, the start bit.
In trigger=data, the trigger starts after the last data bit.
You can see how the decoder is detecting everything wrong, the waves are shifted in your screenshots, caused by the wrong uart polarity, the trigger/decoder ignores the start bit and takes the next falling edge, at this point all the decoder will see is garbage.
-
That's a weird uart signal, it's inverted! Try setting Idle level=Low
You can see how the decoder is detecting everything it wrong.
The wave should start after the first falling edge, the start bit, clearly seen on my screenshot.
But as your uart level is reversed, the start bit is a rising edge, the trigger/decoder ignores it and takes the next falling edge as the start bit, at this point all the decoder will see is garbage.
Sorry, forgot to mention that I already played with Idle Level. No success. Also I just grabbed my other serial adapter which output a 3.3V signal. Exact same results as before :(
-
The wave placement is just...weird. Try recalling defaults. What FW and SW?
-
The wave placement is just...weird. Try recalling defaults. What FW and SW?
Well, the wave placement seems to be a(nother) bug caused by restoring a setup. I tried also everything, reset to default, etc. Nothing helps.
I give up for now as I don't really need this feature at the moment. I will try again when Hantek releases a new software version.
In any case, thank you for your help :-+
-
Did it came with 3204 from factory?
Perhabs that's the problem, maybe try fw 3202?
No worries, you can go back to 3204 any time.
-
Did it came with 3204 from factory?
Perhabs that's the problem, maybe try fw 3202?
No worries, you can go back to 3204 any time.
Yes, it came with 3204. I'm the one who put that firmware on your Google Drive. I don't have much time to experiment at the moment and don't need that decode feature at the moment. Maybe others who upgraded to 3204 can comment if the decode feature is working for them or not. Thanks
-
Davidalfa has started a thread at eediscuss.com (https://www.eediscuss.com/forum.php?mod=viewthread&tid=16049&extra=page%3D1) asking Hantek to release the source code, and I've answered supporting the request.
I think it would be good if all people monitoring this thread would do the same there, so Hantek could consider our request if they see there are many people interested. We should expose reasons such as increased sales or product improvement by volunteers, to try to convince them.
I don't have much faith that it will work, but it's worth a try...
-
I get a 404 from David's Post other post on EEdiscuss:
"Everything about DSO2C10 / 2C10 / 2D10 / 2D15"
https://www.eediscuss.com/forum.php?mod=viewthread&tid=16048&extra=page%3D1 (https://www.eediscuss.com/forum.php?mod=viewthread&tid=16048&extra=page%3D1)
the link https://www.eevblog.com/forum/testgear/hantek-dso2x1x-firmware-updates-and-best-use-practices (https://www.eevblog.com/forum/testgear/hantek-dso2x1x-firmware-updates-and-best-use-practices) comes up 404 without the closing / on it (Using Microsoft Edge / Chrome)
whereas https://www.eevblog.com/forum/testgear/hantek-dso2x1x-firmware-updates-and-best-use-practices/ (https://www.eevblog.com/forum/testgear/hantek-dso2x1x-firmware-updates-and-best-use-practices/) works.
-
The final slash is missing in the "best practices" link
-
Fixed the FAQ links and specified DSO2x1x on the threads qt eediscuss.
-
I already posted this in the Hacking thread, but it's pretty relevant.
Ensure to check the new USB Console (https://www.eevblog.com/forum/testgear/hacking-the-dso2x1x/msg4219495/#msg4219495) package!
-
Calibration of internal AWG DSO2X1X ( DAC902E )
When I have more time I'll try find out how to create a quick method for creating a,b values
after taking measurments.
Hi. Did you create such quick method for creating a,b values after taking measurments? How at all could a,b be calculated? Thanks.
-
Let's push Hantek to do the right thing!
We're only 3 stray cats lonely meowing there, we won't achieve anything unless everyone starts adding their little part.
Hantek sold something, then flew away shamelessly. A brand should support their products and customers!
Release Linux GPL Sources! (https://www.eediscuss.com/forum.php?mod=viewthread&tid=16049)
Fix Errors! (https://www.eediscuss.com/forum.php?mod=viewthread&tid=16074) (Report here)
-
Banggood have an offer on at the moment - if you are thinking you might want one of these scopes now is a good time - especially if you are in the EU as a DSO2D10 shipped from Czech republic $220 delivered, DSO2C10 is $196 albeit from China
-
Hi all - I'm considering jumping down the DSO2x1x rabbit hole, as I have found special deal for this week only - the choices are:
2C10 AU$220 (about US$150) or 2D15 AU$292 (about US$200)
So I consider taking the risk to buy a 2C10 then "upgrade" it to 2D15.
Q1. Has anybody bought a 2C10 very recently (esp from InfinityStore in AU), and if yes did it have AWG hardware inside?
Q2. If a 2C1x has (disabled) AWG components inside, does the scope have AWG Calibration data?
I'm confused about where the AWG Cal will come from if I update a 2C1x to 2D15. It seems very difficult to recreate Cal if lost (or never existed). :-//
Thanks for any advice you can give me, John
-
There is no AWG calibration option on the D10 I bought earlier this week, there is only a single calibration routine on my D10 (220210.00 3204) and that runs through all the voltage and timebase settings presumably setting them all to zero offsets - I didn't notice the AWG doing anything during the calibration.
-
Hantek support likely has records of the original calbration values linked to your serial number that can be restored with a custom update package. At least for the units that are supposed to have them.
There has been some previous discussion in setting calibration values for the AWG. The DAC in this scope (DAC902E) is common to other Hantek scopes. Measureing the required Gain and Offset calibration values are likely a similar procedure.
https://www.ti.com/lit/ds/symlink/dac902.pdf (https://www.ti.com/lit/ds/symlink/dac902.pdf)
-
Hantek support likely has records of the original calbration values linked to your serial number that can be restored with a custom update package. At least for the units that are supposed to have them.
There has been some previous discussion in setting calibration values for the AWG....
Thanks for the reply, Algoma. I'm not worried about AWG Calibration of a DSO2D1x, since those had "official support" of that function. If I buy a 2D1x I can just back up the Cache and EEPROM data to keep track of that.
I've read the earlier discussion about the calculation of AWG offsets, etc - however currently that seems too difficult. Since the AWG Calibration is stored in "firmware", I'm concerned whether the 2C1x models (with AWG hardware installed) will actually work OK after the hack conversion to 2D15 is performed.
It seems that a reasonable proportion of the C models have AWG hardware installed, and we know that the 100MHz models are identical to the 150MHz. So I'm wondering if Hantek is calibrating all the mainboards for AWG, and then they "de-spec" them by setting the HardwareID (model) after assembly of the C models.
Honestly I'm struggling to justify the extra AU$72 (about CA$70) for a pretty crude AWG in a genuine 2D15, so I'm really interested in hearing about how accurately the AWG works on a "converted" 2C10. ;)
-
There is no AWG calibration option on the D10 I bought earlier this week...
Yeah, my understanding is that there is no (practical) way of calibrating the AWG. I wish I could get a D10 like yours, however they won't be in stock locally until the week after the special "20% off" deal ends. So I have the choice of a 2C10 (and take a risk on AWG) or buy a 2D15 for AU$72 higher price. :-\
-
Actually there is a practical way of calibrating the AWG. Please read the attached file Calibration_upk.doc. The calculations are based on the ideas of michal_nt1.
The Calibration_upk.zip has the python's script that makes a dso3kb_calibration_restore.upk file.
To work on Windows you will need an embeddable package of Python 3. To work on Linux, you will need python3 installed and gnupg.
-
Actually there is a practical way of calibrating the AWG. Please read the attached file Calibration_upk.doc....
WOW, thanks very much for that information vistorik. I haven't seen that before, only the earlier post by michal_nt1.
The Word Doc confirms my suspicion that the 2C1x don't contain the AWG Calibration values. The process using Python etc is somewhat complicated but reasonably straight forward I guess.
So, I suppose the question remains as to whether the Hantek Scope AWG is even worthwhile worrying about. I was looking for an upgrade to my old XR-2206 based Generators.
I'd appreciate comments about how it compares to cheap stand-alone units like FY-2300, JDS6600 or even the MHS-5400.
-
I think I can make a standalone UPK that does everything, without requiring a computer, python, etc.
Something like:
- Install "dso3kb_calibrate_gen.upk". The first pass it will reset calibration and reboot the DSO.
- Make the measurements and create "values.txt" in the usb drive, ex.:
AY="632"
BY="-618"
- Run "dso3kb_calibrate_gen.upk" again. It'll know it already resetted the calibration, running the second part this time,
reading "values.txt" and calling a small program to compute the new values, generate "dds_calbration.dds" and update the eeprom.
-
Edit: Found the eeprom structure in the latest 4PDA post (https://ds-blobs-4.cdn.devapps.ru/25847341/%F4%E0%E9%EB+%EA%E0%EB%E8%E1%F0%EE%E2%EA%E8.jpg?s=000000000000000062b33da20000000063d716c244f8d35d9904bbb6b118e3be), stored at 0xE0 as plain text.
The C program seems to be almost finished.
This is my original calibration. Values are A=0.833157 B=13.485453.
For 1Vpp I get 976mV, no offset (or negligible):
(https://www.eevblog.com/forum/testgear/new-hantek-dso2x1x-models/?action=dlattach;attach=1519264)
First glance, running in the scope:
# cal
Hantek DSO2x1x Wavegen calibration tool v0.1
Usage:
cal -r - Reset calibration data
cal -s <A> <B> - Manually set calibration
cal -c <Hi> <Lo> - Generate new calibration
cal -h | --help - This help screen
A reboot is always required to reload the new calibration data!
For the calibration to work, you must first reset the calibration, reboot,
then set the WaveGen to 1KHz, 1Vpp, probe in 1x DC and measure:
Hi: Peak positive voltage in mv
Lo: Peak negative voltage in mv
Then re-run the tool with the measures, ex. "cal -c 568 -630"
Resetting the calibration does A=1.000000 B=0.000000:
# cal -r
Reseting calibration data
Out:
A:1.000000 0x3FF0000000000000
B:0.000000 0x0000000000000000
EEPROM:
1.0000000.000000
Success
# xxd /cache/dds_calbration.dat
00000000: 1000 1000 0000 0000 0000 0000 0000 f03f ...............?
00000010: 0000 0000 0000 0000 0000 0000 0000 0000 ................
00000020: 0000 0000 0000 0000 ........
# i2cdump -y 0 0x50
...
d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
e0: 31 2e 30 30 30 30 30 30 30 2e 30 30 30 30 30 30 1.0000000.000000
f0: 10 10 18 05 15 04 22 ff ff ff ff ff ff ff ff ff ??????".........
Then I rebooted and made the measurements. For 1KHz 1Vpp, I got 544mV and -608mV:
(https://www.eevblog.com/forum/testgear/new-hantek-dso2x1x-models/?action=dlattach;attach=1519231)
Ran the calibration:
# ./cal -c 544 -608
In:
AY:544.000000 BY:-608.000000
Out:
A:0.868056 0x3FEBC71C71C71C72
B:7.372800 0x401D7DBF487FCB92
EEPROM:
0.8680567.372800
Success
# xxd /cache/dds_calbration.dat
00000000: 1000 1000 0000 0000 721c c771 1cc7 eb3f ........r..q...?
00000010: 0000 0000 0000 0000 0000 0000 0000 0000 ................
00000020: 92cb 7f48 bf7d 1d40 ...H.}.@
# i2cdump -y 0 0x50
0 1 2 3 4 5 6 7 8 9 a b c d e f 0123456789abcdef
...
d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
e0: 30 2e 38 36 38 30 35 36 37 2e 33 37 32 38 30 30 0.8680567.372800
f0: 10 10 18 05 15 04 22 ff ff ff ff ff ff ff ff ff ??????".........
The amplitude is better than original... but the offset isn't, 40mV.
(https://www.eevblog.com/forum/testgear/new-hantek-dso2x1x-models/?action=dlattach;attach=1519237)
Repeated with the probe in 1x mode, the lowest offset I got was 32mV. Not terrible, but original was better.
Perhabs the algorithm isn't completely correct?
Code and precompiled binary can be found in the src folder (https://drive.google.com/drive/folders/11u1RyoRfzH6J6wp5uTzeeWnTqvixfN5m).
Depends on i2ctools, but will generate dds_calbration.dat without it, enough for testing.
Once I completely know this is working as expected, I'll make the automated UPK package :)
-
The Word Doc confirms my suspicion that the 2C1x don't contain the AWG Calibration values.
This is not entirely so. At least the last four devices 2C10 reported by the participants in 4PDA forum (e.g. here: https://4pda.to/forum/index.php?showtopic=1018961&view=findpost&p=115355039, https://4pda.to/forum/index.php?showtopic=1018961&view=findpost&p=115643634) had all AWG hardware inside, there was a real calibration file, and the calibration coefficients were also on the PT24C02. But this of course does not guarantee that you will get the same.
-
The Word Doc confirms my suspicion that the 2C1x don't contain the AWG Calibration values.
This is not entirely so. At least the last four devices 2C10 reported by the participants in 4PDA forum (e.g. here: https://4pda.to/forum/index.php?showtopic=1018961&view=findpost&p=115355039, https://4pda.to/forum/index.php?showtopic=1018961&view=findpost&p=115643634) had all AWG hardware inside, there was a real calibration file, and the calibration coefficients were also on the PT24C02. But this of course does not guarantee that you will get the same.
The real question is: Did their devices really restore the AWG calibration from the eeprom after running platform-tools?
Currently the eeprom seems more like a scratchpad, some peple have their model and SN, others have some dates, others random stuff...
30mV error out of 1V is better than nothing, right? :)
Anyways, this doesn't seem to be the correct way to get F(x)=A(B+x) Why B/10?
A1 = Vmax - Vmin
B1 = -Vmax - Vmin
A = 1000.00 / A1
B = B1 / A / 10.00
Anyways, new package, Generator calibration (https://drive.google.com/drive/folders/1KK69-WKosWJLhET32heudEsIlx7lkM_3)
Almost standalone, runs in two passes. It only requires a computer to write down the values to the usb drive.
Thanks 4PDA fellas! :)
Edit: The algorithm is definitely wrong.
After calibrating, try setting a 500mV signal. The offset is huge.
Original:
A=0.833157
B=13.485453
Vgen=500mV, Vmax=252mV, Vmin=-244mV, Offset=8mV
Scope warmed for one hour, calibrated.
Generator calibration cleared, 1Vpp gives 568mV -616mV
Following andry2pda algorithm suggestions:
A1 = AY - BY;
A = 1000 / A1;
B1 = -AY - BY;
B = B1 / A / 10.0;
A=0.844595
B=5.6832003
Vgen=500mV, Vmax=236mV, Vmin=-264mV, Offset=-28mV
A1 = AY - BY;
A = 1000 / A1;
B1 = (-AY - BY)/2;
B = B1 / A / 10.0;
A=0.844595
B=2.841600
Vgen=500mV, Vmax=232mV, Vmin=-272mV, Offset=-40mV
-
... Edit: The algorithm is definitely wrong.
After calibrating, try setting a 500mV signal. The offset is huge.
Thanks so much for the work on this, David :)
Yes, I agree that the offset algorithm is definitely not correct, however the P-P calculation is perfect. Over the next few days I will check the original DOC that they issued, and see if I can work out where they have gone wrong.
Anyway, I bought a 2C10 which just arrived - haven't even plugged it in... but I teared it apart. :-DD
It's motherboard rev DSO2D15_V1.7 2021.1.14 (like they all seem to have) and there is AWG HARDWARE inside. I will boot it up and check AWG Calibration values, etc. Perhaps if mine has a AWG Cal in Cache, we can "reverse engineer" the formula to calculate those values.
I'll be back soon with more info.
Cheers, John
-
Run Eeprom backup tool and Backup builder...
Send the files and I'll tell you if it contains calibration data :-+
(Or just run DSO2D15 converter after you made the backups, if it matches the adjusted output, it's fine then!)
@vistorik, I read you in 4PDA, I have account there, but they use russian captchas, so it's very hard for me to log in.
The result of the calibration can be seen in the file log.txt, in the usb drive. It's generated when running the calibration.
I don't really see why it would require generating the UPK package with the new calibration, when the tool does it in-place.
As it writes the values into the eeprom, you will never need to run the calibration again, the scope will read them whenever dds_calbration file is missing (After runnning platform-tools, etc).
I updated the calibration package, now instead 1Vpp, it can take any reference voltage.
Yep, adjusting the AWG using 600mVpp seem to do better:
-
Run Eeprom backup tool and Backup builder...
Send the files and I'll tell you if it contains calibration data :-+
(Or just run DSO2D15 converter after you made the backups, if it matches the adjusted output, it's fine then!)
[SNIP]
Thanks, David :-+
I've reviewed the 4PDA thread and original DOC file, and I'm not convinced that the AWG offset calculation makes sense. I will comment further once I get my AWG running.
My 2C10 came with FW 3204 SW 220210
Is there still a need to run DSOFLASH backup? That's quite a complex (more risky?) process compared to your BackupBuilder UPK.
The bloody thing has a crack in the top plastic from transit damage. I am going to try to get a partial refund, rather than returning/exchanging it with the seller.
To allow an easy users to revert to defaults (eg: for warranty return), how difficult would it be for you to make 3 new UPKs:
dso3kb_2C10_conversion.upk
dso3kb_2C15_conversion.upk
dso3kb_2D10_conversion.upk
Thanks again, John
-
To allow an easy users to revert to defaults (eg: for warranty return), how difficult would it be for you to make 3 new UPKs:
dso3kb_2C10_conversion.upk
dso3kb_2C15_conversion.upk
dso3kb_2D10_conversion.upk
Here are all these UPKs. But instead of using these rollback conversions, before changing the model number you can use the dso3kb_system.inf_backup.upk which creates a dso3kb_system.inf_restore_CNXXXXXXXXXXXXX.upk file, which restores the /cache/system.inf file.
-
No need of such, that's what Backup builder does, make your backup before doing anything, then whatever happens, restore it.
Keep it easy, I don't understand why people started flooding with lots of packages for every little thing, they're doing it worse.
-
No need of such, that's what Backup builder does, make your backup before doing anything, then whatever happens, restore it.
Hi David, sorry to cause problems here!
One of the issues here is that there is little/no information inside the packages that shows what each UPK actually changes. For example, the readme for "dso3kb_2D15_conversion.upk" doesn't state what files get changed and how to revert back afterwards. So I was unsure that BackupBuilder could restore that factory Model Number data.
Anyway, I installed the 2C15 upgrade on my 2C10 and here is info from factory AWG calibration:
Process: Upgraded 2C10 to 2C15, then Restore Defaults, then Utility > Calibrate (the DSO). Probe at 1x.
AWG: Sine 1kHz @ 600mV
100mV/Div gives AY 296, BY -296 = 592mV (offset zero)
50mV/Div gives AY 294, BY -296 = 590mV (real offset -1.0mV)
20mV/Div gives AY 289.6, BY -296 = 585.6V (real offset -3.2mV)
10mV/Div gives AY 283.2, BY -290.8 = 574mV (real offset -3.8mV)
AWG: Sine 1kHz @ 1000mV
200mV/Div gives AY 504, BY -496 = 1000mV (real offset +4.0mV)
100mV/Div gives AY 496, BY -496 = 992mV (zero offset)
50mV/Div gives AY 488, BY -494 = 982mV (real offset -3mV)
20mV/Div gives AY 480.8, BY -492.8 = 973.6V (real offset -6.0mV)
10mV/Div gives AY 472.8, BY -483.6 = 956.4mV (real offset -5.4mV)
Note 1. At low mV/div I measured AY and BY separately after scrolling V Position. In each case I cursored to the outside surface of the noise envelope.
Note 2. My "Real Offset" is the offset from Zero Volts ie: (-AY - BY)/2
WHAT CAN WE LEARN from my test?
1. The factory offset calibration must be for 100mV/DIV
2. When display mV/Div is reduced, the Measured Amplitude reduces, and offset shifts to negative. :wtf:
3. The DSO measurements cannot be trusted, so it's pointless to use it to calibrate it's own AWG :-DD
Cheers, John
-
One of the issues here is that there is little/no information inside the packages that shows what each UPK actually changes.
So apparently this is not enough...
Before doing anything, save your important data!
- Make a flash backup (Check DSO Flash Tool below)
- Run Backup Builder (In Mods section)
- Run Eeprom backup (In Mods section)
Do I also have to write a complete Wiki page about every single low-level detail? Read the Hacking thread.
Most people here is lazy as f***, not even reading the FAQ most of the time, what the heck, I already did too much :D
-
David has documented a wealth of info in the hacking thread, it really is worth reading in it's entirety.
-
I've moved the FAQ (https://www.eevblog.com/forum/testgear/new-hantek-dso2x1x-models/msg3559217/#msg3559217) here (Page 8 ), there was no sense on having it separately, getting lost, and being spammed anyways ::).
-
Well,
Last weekend I placed some few more capacitors (.47uF tantalun) to filter output from switching power suppluy (SPS) of this scope, trying to get less noise measurements. There was no improvement at all.
So, I'll replace every SPS on mother board and display backs for linear ones, using still the main SPS and, for the last moving, replacing it too.
At each replacement, I'll try some configurations to see if the terrible waveforms I'm getting with my scope, with an anoying disturbing signal, get better and clean shapes.
Any advise?
-
You can't replace some of the switchers because they generate voltages higher then what the main supply gives.
This it the case for U37 on the user interface board, which is for the LCD bias voltages. Creates both positive and negative voltages.
Most likely also the case for U34 which generates the voltage for the back light. This one uses a PWM signal to control the brightness.
See the thread on the schematics. https://www.eevblog.com/forum/testgear/hantek-dso2xxx-schematics/msg4250503/#msg4250503 (https://www.eevblog.com/forum/testgear/hantek-dso2xxx-schematics/msg4250503/#msg4250503) The ones for the user interface board are done. Working on the main board now, but have not looked at the power supply yet.
-
Thanks for replying!
I haven't seen that thread yet!
Excellent! Someone is trying to reverse schematics, as Hantek seems have forgotten :rant: their scope. I coudn't see the voltages there.
(Hey, the "someone" working on schematics is you! Congratulations and many thanks!!! :-+)
As you said, I'll try first the simple SPW (switched power suppply) first: 1,1V and 1,9V . I thought to connect the wire from linnear PS directly to probe points on pcb and remove toroids and SIC ICs from board.
If these changes do not solve the problematic noise, I'll try another trafo with needed voltage for display LCD and brightness. Let's see if it will be possible, otherwise, it is very possible sell my scope as parts unit, as it is unusable and untrustable at all :palm:.
Best wishes with your hard work!
Artur
-
I coudn't see the voltages there.
I did not do the calculations or live measurements on it yet. :(
It is quite a bit of work to go through all the components and connections with a microscope and a multi-meter, but I'm getting there eventually.
Success with your noise canceling quest :-+
-
The scope has some noise, but on the average cheap spec, completely usable, or did you expect 16-bit 10Gsps for that price?
It's just bad for very little signals, ex. 50mV and below.
People tried feeding linear power supplies without any noticeable difference.
The PCB isn't great either, most signals are on the top layer instead being "sandwiched" between gnd planes, thus generating and being exposed to interferences.
If you're having huge noise spikes, well, that's explained in the first lines of the FAQ, try fw3203 if you have 3200/3202/3204.
-
My advice: stay far away from these trash. If you need anything more than a toy with a big screen, don't spend neither 1usd on them.
-
My advice:don't buy. Even they are selling for 1usd.
-
Sure, the're great scopes out there for USD1... ;)
This scope provided great value for the money even with the bugs... my 2D10 was only $170 incl. shipping.
I hate Hantek as brand, their bugs, their non-existent support, they just fly away.
I'll never buy anything professional from them, but it was a reasonable option for the hobbist.
They cost almost double now, for that price, nope!! That's the price tag of Rigol.
-
I read all these threads before I bought and for the rf ham stuff I do, I've been really happy with it
-
Try loading this nude stealer virus setup. Set for 3.3V level, 115.200baud.
Thank you DavidAlfa. I tried your setup. I didn't see any improvements (nor any nudes) :'( My serial adapter outputs 5V but I doubt this makes any difference here.
That decode feature is just not working as it should. If I use your setup without any modification, it complains about no trigger but the scope just trigger as expected :-\ If I set the scope to single sequence, it triggers but now complain that I have to adjust the time base >:( Of course, adjusting the time base does not change anything.
And to make everything even more weird, the scope triggers perfectly if I ask it to trigger on specific data :o Somehow it must be able to decode the protocol but that live decoding purple thing (nor the monitor) is able to display any data. I give up.
Hi.
I had the same problem as you. Mine came with software 220210.00 and 3204 firmware.
I had no luck decoding uart or iic.
Fixed it downgrading to the 3202 firmware found on David alfa's Google drive.
-
Hi All,
I’m having the same issue as already discussed on this forum.
Just bought a DSO2D15 and I’m trying to decode a simple “hello World!” – message, sent via an Arduino at 115200 Baud.
Whatever I do with the trigger or the timebase, the Hantek just won’t decode the message.
Just keeps displaying the message “adjust the timebase/trigger.
The scope came with the mote recent firmware 3204/1.0.2.0.0(220210.00)
I’ using the attach setup for trigger and decode.
Also tried to decode IIC messages, this is also not working.
Does anyone have an idea on how to fix this?
Thanks,
Tom
-
Hi Tomvl, welcome to the forum.
Did you read the posts down from here? https://www.eevblog.com/forum/testgear/new-hantek-dso2x1x-models/msg4139536/#msg4139536 (https://www.eevblog.com/forum/testgear/new-hantek-dso2x1x-models/msg4139536/#msg4139536)
That is specific about the UART decoding.
The post before yours states that going back to firmware (FPGA programming) 3202 solved the problem for him.
-
Hi,
Thanks for your help!
Downgrading to 3202, did indeed solve the decoding issue.
But now I have the USB issue.
I've read on the forum, that there should be an USB_fix script on the Google drive, but I'm unable to find it.
Any idea how to proceed here?
Thanks,
Tom
-
But now I have the USB issue.
I've read on the forum, that there should be an USB_fix script on the Google drive, but I'm unable to find it.
Any idea how to proceed here?
You could find the dso3kb_usb_fix.upk here: https://drive.google.com/drive/folders/1iw9BOnvxNOd0f_2uvGwGSHmnjP4TrG4f (https://drive.google.com/drive/folders/1iw9BOnvxNOd0f_2uvGwGSHmnjP4TrG4f)
-
Thanks!
Got it all working now.
Thanks from your help!
Tom,
-
Small update from the support team of Hantek.
Their engineering department is also working on a fix, for the UART decoding issue, in their next code.
See screenshot below.
Gr,
Tom
-
The specs of the AWG on http://www.hantek.com/products/detail/17182, (http://www.hantek.com/products/detail/17182,) says:
DC offset +- 3,5V and amplitude 10mV - 7Vp-p with high impedance output.
I can set a sine wave with 0 Vdc and 7 Vpp, but i can't increase the offset with this anmplitude set. Or, I can set the offset to 3,5Vdc and 0Vpp, but I can't increase the amplitude with this setup.
The question is: Do you get the same limitation?
-
Because it in the hardware is just a 12 bit DAC followed by an opamp without an extra DC offset input, it is just +/- 3.5V full swing that can be output.
The rest is done in software.
The opamp is powered from +5V and -5V so that limits the range. See here for the schematic: https://www.eevblog.com/forum/testgear/hantek-dso2xxx-schematics/msg4270783/#msg4270783 (https://www.eevblog.com/forum/testgear/hantek-dso2xxx-schematics/msg4270783/#msg4270783)
-
My advice: stay far away from these trash. If you need anything more than a toy with a big screen, don't spend neither 1usd on them.
I'm pretty happy with mine so far. Sure, it has it's bugs, idiosyncrasies, limited performance and misleading specs. When I purchased my expectations weren't high. I got a 2C15 and upgraded to 2D15 so I think I easily got what I paid for.
Maybe post some screen shots and let us see your issue.
-
The specs of the AWG on http://www.hantek.com/products/detail/17182, (http://www.hantek.com/products/detail/17182,) says:
DC offset +- 3,5V and amplitude 10mV - 7Vp-p with high impedance output.
I can set a sine wave with 0 Vdc and 7 Vpp, but i can't increase the offset with this anmplitude set. Or, I can set the offset to 3,5Vdc and 0Vpp, but I can't increase the amplitude with this setup.
The question is: Do you get the same limitation?
Yes, I see the same.
Also:
- if I set the Amplitude to 2V
- then max the offset out at 2.5V
- I can then go back to Amplitude and bump it up to 2.5V but I see clipping/distortion of the waveform
- if I then go back to offset and try to reduce it a touch it jumps back down to 2V and the waveform looks clean again
My conclusion is that the maximum output of the awg including offset should be ±3.5V but the crappy software does not range check and limit it effectively.
Also, no surprise that this limitation to the spec is not properly conveyed in the Hantek documentation.
but it might have been useful, for example, to have been able to generate a 5Vpp square wave with 2.5V offset
I'm not too bothered about this, however, since the AWG is a freebie feature I didn't pay for on my 2C10.
-
To me, the zoom bug is really serious and limits the usability (Can't move cursor before trigger), hantek screwed that in early 2021 and never answered in their forum.
-
To me, the zoom bug is really serious and limits the usability (Can't move cursor before trigger), hantek screwed that in early 2021 and never answered in their forum.
Ah, I thought that was an odd choice as well but I've only owned the scope for 3 months, not long enough to have experienced it working properly.
I get the feeling that Hantek are not really engaged in supporting and improving their products. I guess their business model doesn't build in a budget to allow for much ongoing development on a $190 scope!
btw, thanks for putting together some awesome and concise support material and tools.
-
See here for the schematic: https://www.eevblog.com/forum/testgear/hantek-dso2xxx-schematics/msg4270783/#msg4270783 (https://www.eevblog.com/forum/testgear/hantek-dso2xxx-schematics/msg4270783/#msg4270783)
I'm sorry pcprogrammer, but I didn't fine a schematic for the power supply?
-
See here for the schematic: https://www.eevblog.com/forum/testgear/hantek-dso2xxx-schematics/msg4270783/#msg4270783 (https://www.eevblog.com/forum/testgear/hantek-dso2xxx-schematics/msg4270783/#msg4270783)
I'm sorry pcprogrammer, but I didn't fine a schematic for the power supply?
You are right, I did not make it since it is not to my interest. It is just a switching power supply. I'm interested in the actual scope hardware to understand how it functions and to be able to play with it as a hobby platform.
I'm playing with the idea to reverse engineer the FPGA. There is more open source information available about the Gowin devices than for the Anlogic devices, on which I failed to do so. The information Pepijn de Vos collected about the bitstream already showed me that it is indeed a GW2AR-18 device, and what he wrote about the interconnect routing made me revisit the Anlogic attempt for the FNIRSI-1013D FPGA. It is slow due to other reasons, but made some progress again.
It will not be an easy feat, and might fail altogether, but I'm curious of mind :)
-
Here (https://www.eevblog.com/forum/testgear/hacking-the-dso2x1x/msg4085185/#msg4085185)I posted a simplified schematic for the power supply.
I didn't include the details around the main ICs (it wouldn't be too complicated if necessary). Still, it's enough to understand how it works (my main interest was a possible battery conversion).
-
Hi forum,
I saw that people was reporting really high temperatures on the power supply, I checked the diodes (D5) and I got 70C (with 26C ambient, after ~30mins without the back part of the enclosure)* , not as much as others have reported (>95C), but still too much.
So decided to change all the diodes on the secondary:
D4 SS310 with STPS6M100SF (https://www.st.com/en/diodes-and-rectifiers/stps6m100sf.html) | slighty better diode.
D5 SS310 with FERD40H100SFP (https://www.st.com/en/diodes-and-rectifiers/ferd40h100s.html) | way better diode.
D6 SS310 with SB1045L | way better diode.
then I install some small heatsinks but they didn't made much of a difference.
(https://www.eevblog.com/forum/testgear/new-hantek-dso2x1x-models/?action=dlattach;attach=1549222;image)
so I installed bigger ones.
(https://www.eevblog.com/forum/testgear/new-hantek-dso2x1x-models/?action=dlattach;attach=1549228)
Finally got this temperatures:
D4 47C*
D5-inner 48C*
D5-outter 47C*
FERD40H100SFP-top 44C*
FERD40H100SFP-heatsink 46C
U1-heatsink 60C
U4-heatsink 62C
at 24C ambient.
*I Just put the thermocouple on top of the plastic package, *probably* not the best way to do it.
Hantek had to used either a fan o better parts.
The DC-DC converter seems hopeless, it's just not good, I mean it uses transistors for the switching... I thinking into replace it with something that uses mosfets, synchronous preferable, with this change U1 may reduce it's temperature a bit.
BTW does anyone knows what type the connector is on the output?
Also, for people that want to change D5, if you're on a 220VAC country, you *probably* should use a 100V part, 60V diode seems risky to use... I always saw that on SMPS they always use high voltage diodes on the secondary and had the doubt if was really needed or another victim of "we are using the cheapest part that'll do the job" thing, so looking for an answer I found an app note from Infineon with all the equations involved on SMPS design, on page 21 (attached) the mention the equation related to the diode voltage:
Vdiode=Vout+(DCpeak*(Ns/Np))
Ns/Np it's the transformer turn-ratio, which we don't know, but the U1 datasheet mentions the ratio 12/90 that *probably* hantek used on the PS, so for the voltages I got the diode ratings:
110/120/127 VAC using infineon turn-ratio example: 38.06V
110/120/127 VAC using DK124 turn-ratio example: 34.34V
220 VAC using infineon turn-ratio example: 60.07V
220 VAC using DK124 turn-ratio example: 53.63V
In countries were we have 110/120/127 VAC we *probably* can use a 60V part I use the 100V part mostly because was the only FERD on full plastic package when made the order.
BTW, on the U1 datasheet they recommend (for a 12V out) a 300V part :-\
-
'New' firmware is up:
dso3kb_20220517.upk
http://hantek.com/products/detail/17182 (http://hantek.com/products/detail/17182)
http://hantek.com/uploadpic/hantek/files/20220727/dso3kb_20220517.zip (http://hantek.com/uploadpic/hantek/files/20220727/dso3kb_20220517.zip)
-
Great news! Or maybe not...
I wonder how many working features will this update break ::)
-
Does anyone have a full nand w25n01g memory dump for dso2d15???
-
I applied the heat-sink mod and found that on the other big chip (left of the lemontree part) there was the same black paint typically used on fake chips. I removed it with some alcohol and took some pictures. It looks to have a National Semiconductor logo, but they scratched the part number off. Some bits of it are still readable. Perhaps it can help someone to identify the part:
-
Interesting :-+
The going believe is that the chip is a Texas Instruments adc08d500. See: https://www.eevblog.com/forum/testgear/hantek-dso2xxx-schematics/25/#top (https://www.eevblog.com/forum/testgear/hantek-dso2xxx-schematics/25/#top)
Don't know if National Semiconductor has a similar ADC.
The Lemontree chip is a Gowin GW2AR-18-144 FPGA. This has been confirmed based on the bitstream for the FPGA
-
Try deeper cleaning it with a brush, then drop some thermal paste, massage it to fully fill the porous surface and wipe gently.
Any marking leftovers will be filled now with the paste and revealed, this works great most of the times.
-
I wonder how the buttons are doing for you, guys?
My "V0" rotating enconder started to fail about a month ago, probably because any big adjustment require 45 trillions turns.
Now I can turn it max. 1 turn per second or it will do whatever it feels it's best, usually increase no matter the direction, and sometimes suddenly jump by a lot, taking another 20 seconds to adjust the value.
Chinesium software, chinesium hardware, chinesium support, everything's chinesium! :palm:
I can't find the front panel pcb pictures I took when I opened it... does anyone have any, or the encoder model/type/dimensions?
@pcprogrammer? I know you have them for sure...! ;)
-
@DavidAlfa, of course I have pictures :)
But all taken from the top, so not a good view to determine the type, and the scope is back together again :palm:
Hope the attached one helps.
-
PEC12R-4220F-S0024, Incremental encoder with switch
-
I can't find the front panel pcb pictures I took when I opened it... does anyone have any, or the encoder
I replaced the encoder V0 with a PEC12R-4220F-S0024. Ordered on arrow.de https://www.arrow.de/products/pec12r-4220f-s0024/bourns (https://www.arrow.de/products/pec12r-4220f-s0024/bourns).
-
Noted down, thanks!
Don't have enough motivation to disassemble everything again :D , I'll probably replace it in the near future.
-
Hey folks!
I've come out of the woodwork again to ask about an oscilloscope.. again. I'll try to keep it short (ha!), but basically I am *very* intent on buying one of these puppies with my soon-to-arrive little windfall.
I am just about as green as grass with electronics, and it's something I want to get in to, maybe even as a career. Anyway!
I own two USB-based scopes, and I really feel like I've been burned both times. The first scope was the infamous Hantek 6022BL, and I have opinions about this one. In fact, I asked this very forum for advice on a USB-based scope (wanted mainly for budget reasons, but I do want a full fat scope now), and was recommended the Dreamsource Lab DScope somethingorother. Initially I was wowed by it, but really, the only thing it gained me was a decent ability to trigger of something that isn't a perfect 1kHz square wave. Both scopes are identical in that measurement facilities are very poor, and decode facilities are flat out non-existent. I know there are other features any oscilloscope worth a damn that are missing on both of these. In essence, both of these scopes run on Sigrok, and I hate Sigrok (because of how basic it is and somehow simultaneously how user-friendly it is not-it's bad enough one of these problems exists, but both existing in the same application is serious talent on behalf of the developers), so it's a non-starter anyway.
In any case, I was very disappointed to discover that this is the only additional feature it seems to have. I was hoping I'd at least get some useful toys like serial decode and whatnot, but it's exactly like the 6022BL, just better made and it's a real oscilloscope that actually has a real FPGA, and doesn't need stupid driver faffing-around-with.. This drove me positively nuts with the Hantek and it's stupid unsigned driver that pushed firmware to the device on every boot because an EEPROM was too expensive crap.
This is a very long-winded way of saying that the software for both of these things is crap. I was worried, but figured "oh, DScope is still in decently active development, so it should get better eventually." Well, it seems I'm a tad cursed because the second I bought the goddamn thing is when development ceased.
I'm really tired of buying junk and I just want a *basic* scope with *basic* features. I am really hoping that third time is the charm here, but I have one or two concerns. First being is that Hantek doesn't really have a support base here in Aussieland, it seems. I really would like some recourse if I feel like I get burned again. But I think this scope is a goer for me. I played around with the Jaycar scope and I'm in love. I know it's buggy, but it seems like both first and third party development is active. At the VERY least, Hantek is at least a company more than a handful of people have heard of.
Now for the real question. I know I can get one of these for <$400 or so, but I'm wondering if I should pony up for the Jaycar model. I feel much more secure with the idea of buying an expensive instrument like this from a B&M store, even if the pricing is a tad outrageous. $549 is at the upper end of my budget, and I am happy to pay the premium for peace of mind. But TL;DR main question is: If I buy the Jaycar branded scope, will I be able to just chuck the normal 1st party Hantek updates on this? I can't imagine not being able to, but I figured I'd ask. In case nobody has done this, I guess I'd be happy enough being a guinea pig and trying it on mine when I do buy it, I just figured someone might have tried this. Lastly and frankly, I don't really want to wait for a scope to come from China anyway. I am far too impatient, have been wanting a real oscilloscope literally forever as far as my hobby is concerned, so I absolutely plan on having one of these on my desk the literal second the money hits my bank account. :P
Apologies that this is a bit of a meandering post, but I'm still new to all this, and I'm not even sure what I need to be looking for in a garden variety scope, but I know at least that serial/CAN etc. decode is essential for me, and I know that most scopes are a bit less basic than these USB toys. There's little to no complex triggering, the interface is extremely clunky, etc. Plus, having an AWG and decode alone is reason enough for me to pull the trigger on the Hantek.
Thanks all, and sorry again for the rambly nature here. Again, I'm not even sure what is considered essential for a real scope. I just know that I feel like the two USB things I have are missing a lot of features I've seen even modest old Rigols have in Dave's super vintage videos.
-
I applied the heat-sink mod and found that on the other big chip (left of the lemontree part) there was the same black paint typically used on fake chips. I removed it with some alcohol and took some pictures. It looks to have a National Semiconductor logo, but they scratched the part number off. Some bits of it are still readable. Perhaps it can help someone to identify the part:
I was curious enough to open my scope yet again and wash down that device. Mine has been ground down so enthusiastically that no one is ever going to make out any of the markings that once adorned it's package.
Isn't this is the sort of defacing that's usually associated with bootleg components?
-
Isn't this is the sort of defacing that's usually associated with bootleg components?
Removal of any identifying marks seems to be common practice in China, to slow down products from being copied and reproduced at a lower cost by their grey markets. Even with genuine and resonably well made products. Aliexpress in rife with low quality variations and clones.
-
Yeap, mainly done to make it harder to copy, just like the Lemontree FPGA you won't find anywhere :D
-
Yeap, mainly done to make it harder to copy, just like the Lemontree FPGA you won't find anywhere :D
Are you kidding?
-
Now for the real question. I know I can get one of these for <$400 or so, but I'm wondering if I should pony up for the Jaycar model. I feel much more secure with the idea of buying an expensive instrument like this from a B&M store, even if the pricing is a tad outrageous. $549 is at the upper end of my budget, and I am happy to pay the premium for peace of mind. But TL;DR main question is: If I buy the Jaycar branded scope, will I be able to just chuck the normal 1st party Hantek updates on this? I can't imagine not being able to, but I figured I'd ask. In case nobody has done this, I guess I'd be happy enough being a guinea pig and trying it on mine when I do buy it, I just figured someone might have tried this. Lastly and frankly, I don't really want to wait for a scope to come from China anyway. I am far too impatient, have been wanting a real oscilloscope literally forever as far as my hobby is concerned, so I absolutely plan on having one of these on my desk the literal second the money hits my bank account. :P
It's very unlikely there's a HW difference in which case there's no reason that it shouldn't work. The real question is do you want to just chuck the normal 1st party Hantek updates on it? I personally don't get a warm feeling that a SW update from Hantek is going to be an upgrade. They do a terrible job of verification, breaking working features while not really providing significant improvements. To make matters worse they refuse to provide the release notes so that users can make informed decisions. The way I look at it is I know the limitations of the SW I have installed and unless someone gives me a compelling reason to install something newer I'm not going to waste my time. Don't be fooled into believing they're putting any resources into their products just 'cause they have a lot of stuff out there.
Your impatience is coming at a high price considering you can go to Banggood and buy the 2C10 for $280 shipped and hack it up to a 2D15 for no additional cost. After all, this is about all this scope is worth at the end of the day. In the unlikely event that you're unlucky enough to receive a 2C10 without the AWG components you still have ~$270 to spend on a much more capable stand alone AWG if you need one. Let's face it, the inbuilt AWG is little more than a toy.
What are Jaycar giving you other than the opportunity to buy locally and quickly? Do they provide any product support or warranty support? I suspect they will just be a middle man and it's going to come back to what Hantek provide which is frankly very little. But you already know that.
Once you account for the lack of support, shitty SW, noise issues, poor triggering, memory depth limitations, measurement limitations, barely functioning protocol decoding, a whole bunch of frustration etc etc it's still a not a bad deal for <$300 but I wouldn't pay much more than that for it.
-
Yeap, mainly done to make it harder to copy, just like the Lemontree FPGA you won't find anywhere :D
Are you kidding?
No, try finding a "LemonTree 2090", it doesn't exist, you can't buy it anywhere ;)
So you can't copy a design if you can't source the parts, did I explain now?
Yeah, we do know it's a relabeled Gowin part because I ran the JTAG on it, but otherwise it still would be an unknown part.
-
Interestingly, Hantek engineers will ever guess in such oscilloscopes with a generator like dso2d15 to add a frequency response meter function?
-
Now for the real question. I know I can get one of these for <$400 or so, but I'm wondering if I should pony up for the Jaycar model. ...
...
Once you account for the lack of support, shitty SW, noise issues, poor triggering, memory depth limitations, measurement limitations, barely functioning protocol decoding, a whole bunch of frustration etc etc it's still a not a bad deal for <$300 but I wouldn't pay much more than that for it.
I just want to second @dirtmover's conclusion, he summarized it well. As my first hobby scope I like it for what it is, but I can definitely see where it cuts corners compared to a more expensive brand. I think someone else on this forum also made the point that for the price it's probably a good way to try things out. Even if you end up buying a better scope in a year, you'll only have spent $280 but you'll know what you want/need from your first 'real' scope.
-
Don't get fooled, it was marketed for the $150-$200 range, that's where it belongs, if they ask more now, well... you decide.
For $300, wouldn't consider this DSO it by any way, I'd jump into the $400 territory.
It's like getting a rusted car for $900 or decent one for $1200.
The rusted one will never be fine (or very expensive to fix), it's throwing your money away.
-
It's Australian dollar I think, $280 aud ~ $190 usd.
-
Hi, guys
I finally started to replace the main switching power supply of my scope with a linear power supply using the old simple transformer and regulators. But I have some doubts:
1 - there are two power supplys: one dual, analogic, of +8Vdc GND -8Vdc - this one is used only for being transformed in +5 and -5Vdc in main board?
So, I will just make one new +8V -8Vdc rectified and filtered by capacitors and inject its output to 7805/7905 regulators on main board, as already is.
2 - the digital power supply of +5Vdc will be used for a lot of other low voltage conversions (1v1, 1v9, 2v5, 2v8, 3v3).
Shall I use another transformer, rectifiers and filter capacitors to make a separeted power supply for it?
Also, the filter capacitors after the 7805 and 7905 on main board are of 100uF. This is 10x the recommended on datasheets for these regulators and could burn them when the equipment is turned off, I'm right?
-
2 - the digital power supply of +5Vdc will be used for a lot of other low voltage conversions (1v1, 1v9, 2v5, 2v8, 3v3). Shall I use another transformer, rectifiers and filter capacitors to make a separeted power supply for it?
I used two transformers - one for +8/-8V and one for +5V.
Please don't forget the TR line.
-
Great!
For TR line, it would be better to keep the switching power supply on? I read here, in some comments - I don't know which one any more - it's a pulse from line (60Hz) ???
If so, some clipping diodes to generate a "rectangular" positive signal could also work ??
Best regards!
-
For TR line, it would be better to keep the switching power supply on? I read here, in some comments - I don't know which one any more - it's a pulse from line (60Hz) ???
If so, some clipping diodes to generate a "rectangular" positive signal could also work ??
I've used the TR schematics of the power supply by Piton. Instead of PS817C I've used PC817, and instead of F7 of D3 - 1N4007. It works good. The TR signal from the power supply goes to the 2nd PIN of the U3 (SN74LVC1G17) on the main board. From the 4th PIN of the U3 the signal goes to the FPGA (POWER_HEAT_BEAT) - see the schematics of pcprogrammer.
-
Just a thought, when you are using a transformer, you can connect the opto coupler to the secondary side of it. Reduces the risk of shock when working on it. Just adjust the resistor values to what is needed.
-
Very clean, simple, safety and clever design! It couldn't be better!
Many thanks for so kind replies!!! This weekend I'll have work at my lab!
Best wishes and I'll post the results!
Artur
-
Any feedback yet on dso3kb_20220517.upk, please?
I've had my DSO2D10 (Amazon, 2022.02.10, 3204) since the weekend, stuffed/recovered several times already.
Thanks,
Al
'New' firmware is up:
dso3kb_20220517.upk
http://hantek.com/products/detail/17182 (http://hantek.com/products/detail/17182)
http://hantek.com/uploadpic/hantek/files/20220727/dso3kb_20220517.zip (http://hantek.com/uploadpic/hantek/files/20220727/dso3kb_20220517.zip)
-
Didn't notice any difference, also Hantek doesn't provide any changelogs. |O
Just remember we have all firmware revisions, so if some new bug appears, you can simply up/downgrade the fw as you wish.
-
I'm currently at work on my V2 version. :)[attachimg=1][attachimg=2]
-
I did the replacement of switching power supply as I said before. :-+
I also followed the recomendations of taking the TR signal from secondary of "digital" transformer (I used two transformers of 6+6 VAC). :-+
(But all of this resulted in no better performance: the spikes signal is still present at high frequencies measurement and low memory depth. :palm:) - not real - the spikes almost have gone.
I understimated the necessary current for +5V digital source, and it is more than 1A, so, the LM7805 is getting too hot and there is a terrible ripple on this line (I filtered using 4700uF capacitor). I replaced the LM7805 by LD1085 - V36 - a 3A adjustable linnear regulator.
Also, I put a filter taken from a plasma TV before power supply.
I noted in your schematic that you use 7808 and 7908. I believe they are not neccessary, as this voltage lines will just be regulated to +5 and -5Vdc for analog inputs. :o
For last, C30, C31 and C27 are too big. I have read that large capacitors can cause a reverse current blowing the regulators in the case the voltage on their output gets higger than on inputs. So, I belive 22uF is enough. This problema also repats on original capacitors in main board after +5 and -5Vdc regulators - I replaced then for smaller ones.
Also, I did not understand why the second 7808 regulator in your second circuito, as we have only one +8Vdc (I repeat, it's not neccessary to regulate this output, I believe).
-
Is there any protection on the DSO2D10's TRIGGER input?
In the Technical Specifications section of the manual, the Maximum Input Voltage for CH1 and CH2 inputs is specified as 300V.
Elsewhere in the manual it says “The external trigger signal must be a 0-3.3V [CMOS] waveform.” But that does not specify whether that is the operating range or the maximum input voltage, and whether harm would be caused by a higher voltage.
In my case I'd like to trigger the other channels on a simple +5V gate signal.
-
The complete schematics are in this post (https://www.eevblog.com/forum/testgear/hantek-dso2xxx-schematics/msg4289413/#msg4289413) (thanks to pcprogrammer (https://www.eevblog.com/forum/profile/?u=754690)). The trigger input is here (https://www.eevblog.com/forum/testgear/hantek-dso2xxx-schematics/?action=dlattach;attach=1533370).
According to the schematic, not a great protection, just diodes to +-5V, and to +-3.3V after the relay. Higher voltages than +-3.3V from a source capable of supplying more than a few mA would probably blow these diodes and more things after them...
-
See the schematic here https://github.com/pecostm32/Hantek_DSO2000/blob/main/Schematics/Mainboard/Waveform%20Generator.png (https://github.com/pecostm32/Hantek_DSO2000/blob/main/Schematics/Mainboard/Waveform%20Generator.png)
There are diodes to analog +5V and -5V, and when relay is set to external trigger there are diodes to +3V3 and ground.
After that is goes to the FPGA https://github.com/pecostm32/Hantek_DSO2000/blob/main/Schematics/Mainboard/Data_Acquisition.png (https://github.com/pecostm32/Hantek_DSO2000/blob/main/Schematics/Mainboard/Data_Acquisition.png)
Edit1: morgan_flint beat me to the punch :-DD
Edit2: Well there is the extra ~50 ohms resistor in series, so a little bit extra protection.
-
Not sure if it's related to the last update, I developed a small tachometer and used the gen to simulate the pulses.
The scope always freezed after 10-15 minutes, never did before, yet to test if its being caused by the generator or happens anytime.
-
Not sure if it's related to the last update, I developed a small tachometer and used the gen to simulate the pulses.
The scope always freezed after 10-15 minutes, never did before, yet to test if its being caused by the generator or happens anytime.
I ordered a DS2C10 because I am not at home for a few weeks and needed a super basic scope to tinker a bit. Wanted to spend as little as possible.
This type of comment tells me that I just signed for a wild ride :-DD I wonder if the engineers at Hantek are testing the scope
-
Hello,
I'm having an issue with 2 mV range. This is a 10 mV sine wave signal from external generator. When only the first channel is enabled the scope shows amplitude of 5 mV (pk-pk) but when I also enable second channel the amplitude goes to roughly 10 mV (which would be ok...) .
Any range above 2mV works ok. Does one channel affect the other in your scopes in 2 mV range too ?
-
Does one channel affect the other in your scopes in 2 mV range too ?
No, I don't see this on my device.
-
Thanks much !
-
Hi guys,
i recently bought a DSO2D10 which worked flawlessly for a week or so. I calibrated it without problem when i first tried it. I updated the software to the newest on found on Hantek site (20220517). Is far as i remember the original one was 220218? Unfortunately i didn't make a photo of that.
After one week of use, in between a measurement suddenly strange DC offsets appeared on both channels: 20V on CH1@10V/div and -16V on CH2@10V/div.
If i change the V/div these offsets change, but mostly remain seen as 2 divs and -1.5 divs on the channels. If i move the vertical position the signals will move closer/further to the offset indicator (on the left side with 1 and 2 in it).
I tried to calibrate (waited to warm up) but it gave me error 511d1.
I since tried all possible combination of firmware / software, even tried the platform tools, but the problem didn't go away.
I'd be glad if you could give me some advice what to do with it.
-
Removal of any identifying marks seems to be common practice in China, to slow down products from being copied and reproduced at a lower cost by their grey markets. Even with genuine and resonably well made products. Aliexpress in rife with low quality variations and clones.
Sharing a story... many years ago, I had a side gig which consisted of making electronics for a certain niche market.
I didn't make a fortune, but it really helped me at the time.
It was before cheap PCB assembly at low volumes was available for cheap in the western world so I was building the electronics myself.
It was also before microcontrollers, secure boot and all that stuff, so designs were particularly vulnerable to copying.
And once that happens, unless you were a company with big pockets, it was very hard if not impossible to make it stop.
The build process did include a step of scratching the markings of a certain critical component...
Fast forward a few years, I end up on a forum where people describe my design, start to reverse engineer it and were stuck on the mystery IC.
Could they have redesigned the product ? Certainly. But higher effort.
Could they have found out what the chip was ? Certainly. But higher effort.
Would they have sold a copycat product if they found what it was ? Maybe not. But maybe yes...
In China, copying is rampant, it's not a secret. And many international buyers are totally ok buying copied products... so there is a market for it... in fact, many buyers don't even know who invented the product first.
So, I totally understand why some companies do it. Actively obfuscating company IP/secrets.
I am sure many of you working in the industry also know that component selection is a critical design input parameter especially for high volume, and/or cost-critical designs.
Another variation of the situation is when companies have an invention... but choose not to patent it. Because in some situations, publishing the secrets would make it trivial to copy them, and litigation would not necessarily be trivial or cheap. In some cases, if the inner working or details of the invention are not published, it is hard to copy. So it's also a form of passive obfuscation.
I don't blame Hantek for that. I think we should focus the blame on the buggy firmware and possibly flawed design leading to a variety of weird issues (see this thread, random DC offsets, huge noise on the waveform at certain sampling parameters but not others, ...)
-
If you look at what these scopes are intended to be, it's impressive for the price they are asking. I hope they eventually get it right as this is a path in to analytic equipment on a budget we've not seen before.
I have a couple of Hantek branded products that, for their price, I am very happy with. A 70MHz 4ch USB scope and a AC/DC current probe. Together they did not cost $300. Are they as nice as the equivalent from Agilent of Rhode and Schwartz? No way, but for my purposes for these items they were affordable. Do R&S or Agilent (sorry .. Keysight) make even an AC/DC probe for under $1000, let alone a 4ch. scope with serial decoding, fft, and data logging thrown in. :scared: Yeah, maybe for 20 times what I paid this for equipment that I use at a hobbyist level just once in a while.
There is room for this, and I applaud Hantek for trying to bring it to market. I just think they may have bitten off too much on this effort.
I recently paid out about $3K on new Siglent equipment. What I got would have cost me easily $15K-$20K from Keysight/R&S/Tek. Sorry, as a retired slouch playing around in my basement I simply can't afford the "premium" big name gear.
If the big guy's wanted to get into the basement hobbyist business they could. They have no desire to address that market and willingly leave it open to the likes of Hantek.
Good all around.
-
Agreed. There is absolutely a market for this type of equipment. In fact, the reason I bought one is because I intend to leave it at some relative's home abroad that I am sometimes visiting, so I can tinker a bit and fix things while I am there, without having to pay for a full lab. Thinking about it... I never thought it was economically feasible to have a second lab. It is ! So thank you Hantek. But please, please, fix the bugs. If you don't want to fix them, open source your stuff for others to do it.
-
I know I can get one of these for <$400 or so, but I'm wondering if I should pony up for the Jaycar model. I feel much more secure with the idea of buying an expensive instrument like this from a B&M store, even if the pricing is a tad outrageous. $549 is at the upper end of my budget,
$400 WTF ??
FYI, you can buy the DSO2C10 on Ebay Australia for AUD $275 including delivery. (Equivalent to USD $185)
Currently there's 2 listings, actually the same seller:
https://www.ebay.com.au/sch/i.html?_nkw=Hantek+DSO2000&_sacat=0&LH_PrefLoc=1 (https://www.ebay.com.au/sch/i.html?_nkw=Hantek+DSO2000&_sacat=0&LH_PrefLoc=1)
They are local AU stock, delivered ex-Sydney within 2-3 days. They have European plug (just use your own IEC 3-pin kettle cord). I bought one using a recent 20% off eBay coupon from "Infinity Store", so it was even cheaper!
My 2C10 included the AWG Hardware inside, and updated cleanly to a 2D15 using David Alfa's "2D15 Conversion" UPK from his Google Drive: https://drive.google.com/drive/folders/1vYFqXzPl2nOZJnx58TLhZa37cmvpqkPY (https://drive.google.com/drive/folders/1vYFqXzPl2nOZJnx58TLhZa37cmvpqkPY)
I certainly can't see the point of paying AUD $400-500 for one of these.
-
Finally got my DS2C10, I mean DS2D15 :-DD
It had the DAC populated it from the factory. Did a full backup as per the FAQ, and changed it to a 2D15 with no issues.
I tried the AWG and it seemed that it was calibrated because if I asked it 2 volts, it gave me 2 volts... although I didn't check down to the millivolt.
I suspect it's calibrated, but didn't find a way to check easily without connecting a terminal to the scope to get a shell (if someone tells me how to unpack the eeprom dump upk, and where to look inside it, I can check)
It came with firmware 3204 from the factory.
-
I suspect it's calibrated, but didn't find a way to check easily without connecting a terminal to the scope to get a shell (if someone tells me how to unpack the eeprom dump upk, and where to look inside it, I can check)
To get the eeprom dump file you don't need to unpack the eeprom dump upk. To get this damp you can use the dso3kb_PT24C02_damp.upk. You could also use dso3kb_cache_copy.upk to get /cache/dds_calbration.dat. You can than compare the contents of the dso3kb_PT24C02_damp.bin and the dds_calbration.dat files (see the Generator calibrating check.doc) to check generator calibration.
-
I suspect it's calibrated, but didn't find a way to check easily without connecting a terminal to the scope to get a shell (if someone tells me how to unpack the eeprom dump upk, and where to look inside it, I can check)
To unpack the eeprom dump upk you can use the extract.bat (created by andry2pda from 4pda forum) from the Windows_UPK_extract_tool.zip (unpack this archive in the folder for instance c:/Test. Before unpacking this archive download Windows_UPK_extract_tool.z01.zip and Windows_UPK_extract_tool.z02.zip which are posted next and delete .zip in names of these files). You find the eeprom dump in the /CNXXXXXXXXXXXXX_eeprom/package/ee.bin file. You could also unpack one of two upk backup files dso3kb_CNxxxxxxxxxxxxx.upk or dso3kb_CNxxxxxxxxxxxxx_FULL.upk to get dds_calbration.dat file from the /CNXXXXXXXXXXXXX/package/backup.tar.gz. You can than compare the contents of the ee.bin and the dds_calbration.dat files (see the Generator calibrating check.doc in the Windows_UPK_extract_tool.zip) to check generator calibration.
-
The second part of the Windows_UPK_extract_tool.zip archive.
-
The third part of the Windows_UPK_extract_tool.zip archive.
-
Just install the USB console package and check the files, couldn't be easier!
-
Just install the USB console package and check the files, couldn't be easier!
DavidAlfa, how could I check the dds_calbration.dat file and the PT24C02 content using the USB console and Putty terminal (I've all installed) under Windows OS?
Thanks a lot in advance.
-
If it did 2V when requesting 2V, that's fine.. usually an uncalibrated gen gets noticeably off.
Don't expect mV accuracy, anyways.
Run:
hexdump /cache/dds_calbration.dat
Calibrated example:
0000000 0010 0010 0000 0000 df01 de6d a938 3fea
0000010 0000 0000 0000 0000 0000 0000 0000 0000
0000020 7d7c 4bad f88d 402a
If no calibrated, that file migh not exist at all, or maybe show:
0000000 1000 1000 0000 0000 0000 0000 0000 f03f
0000010 0000 0000 0000 0000 0000 0000 0000 0000
0000020 0000 0000 0000 0000
Or it might have random/default calibration values.
-
Run:
hexdump /cache/dds_calbration.dat
OK. Thanks. So, what I've got for the dds_calbration.dat with the PuTTY and with a HEX-Editor under Windows (it looks a bit different):
But what about the content of PT24C02? Could I see this with PuTTY?
-
So, what I've got for the dds_calbration.dat with the PuTTY and with a HEX-Editor under Windows (it looks a bit different):
Try to use
hexdump -C /cache/dds_calibration.dat
-
That's fine, calibration is different for each device.
The endianess is different in ARM and x86
-
Try to use
hexdump -C /cache/dds_calibration.dat
Yes, it helped:
phoenix login: root
unix:path=/var/run/dbus/system_bus_socket,guid=b5541119dc7a0579c1a406840000000d
# cd /cache
# ls -hl
total 12
-rw-r--r-- 1 root root 0 Jan 1 00:00 anolis.conf
-rw-r--r-- 1 root root 2.1K Jan 1 00:02 cali.dat
-rw------- 1 root root 40 Jan 1 00:00 dds_calbration.dat
-rw-r--r-- 1 root root 239 Jan 1 00:00 system.inf
# hexdump -C dds_calbration.dat
00000000 10 00 10 00 00 00 00 00 75 cc 79 c6 be e4 ea 3f |........u.y....?|
00000010 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
00000020 84 46 b0 71 fd 4b 1f 40 |.F.q.K.@|
#
Thanks. Another question. Is there an easy way to copy a file from the device's file system to a Windows computer and vice versa using the PuTTY? I cannot use the front usb port of the device because the back port is is used for connection to the computer. I'm sorry for this question, but I couldn't find any suitable and simple linux command(s).
-
You can use zmodem, I've used it many times.
Windows support is messy, better use Linux/Ubuntu.
You can also use SecureCRT software, it fully supports zmodem, it's really handy, you can download the demo.
To receive a file from the scope, you only need to run "sz <file>" in the shell, it will automatically receive it.
For sending, just drag&drop a file onto the terminal and it'll send it.
-
You can use zmodem, I've used it many times.
Windows support is messy, better use Linux/Ubuntu.
You can also use SecureCRT software, it fully supports zmodem, it's really handy, you can download the demo.
To receive a file from the scope, you only need to run "sz <file>" in the shell, it will automatically receive it.
For sending, just drag&drop a file onto the terminal and it'll send it.
Thanks. I've used SecureCRT and it works.
-
I just received my DSO2C10. When I plugged in a USB, the DSO kept beeping. I wonder is there a maximum size for the USB drive? I tried 2T and 256G both beeped unendingly...
-
Just arrived to this thread. My 2C10 is bricked. Contacted support and they sent my an update file, which obviously I can't execute because I can't get the UI working. Anyway. Attached the file so proficient users can take a look. I will go 30 pages back and start the unbrick procedure. This device is a mess and I regret not having spent 100 dollars more to get a Rigol 1202ze.
-
When I plugged in a USB, the DSO kept beeping.
Use only FAT32 formatted drives.
My 2C10 is bricked. Contacted support and they sent my an update file, which obviously I can't execute because I can't get the UI working.
Thanks for the update.
Is it still working, but unresponsive to the keypad?
Try connecting it to the computer, does it get recognized?
If so, you could send a factory reset command through scpi.
Install SCPI (Available at Hantek download page).
Connect the scope to the computer.
Open SCPI console and write "PRIVate:FACTORY:RESET"
(Keep uppercase/lowercase as that).
All settings will be resetted and should work again, avoiding the flashing step.
-
The device is connected but doesn't respond to any input using "DigitalScope" application or the "Keysight Connector Expert IO". I will need to use platform tools |O
-
Is the scpi driver installed?
No worries. Did you make any picture of system info or a backup using Backup Builder?
- Run latest platform-tools
- Apply USB Fix (Will require several presses on Update to make the USB work, this is what USB Fix will address)
- If you made a backup, restore the full package.
Otherwise:
- Install the original FW version if different, use FW Changer.
- Restore original SN, HW with Script Launcher.
-
Is the scpi driver installed?
Yes it was.
No worries. Did you make any picture of system info or a backup using Backup Builder?
I did not take any picture since I was naively using the device (with occasional reboots) until it bricked by selecting 8Ms and doing a "single seq". Then googled and arrived to this thread. I understand that I lost the serial number, calibration for signal generator, etc.
I'm quite worried. I did the recovery operation with platform tools versions:
» 2021.07.26, FW3202 (first time)
» 2021.05.17, FW3102 (second time)
all steps went good without errors but the DSO doesn't boot after. It shows the QR image and then locks at the following screen "Hantek Your testing solution provider"
Has this happened before? I think I saw the pinout for the serial port in this thread. Should I try to see the boot logs?
I don't know if it is related, but before the recovery the device locked up in graph screen, tried to setup parameters (because some buttons turned off) but I don't remember hearing the relay clicks.
-
Ok. Found the problem. The "English readme" is wrong. It says to do:
1) sunxi-fel uboot images/uboot_fastboot.bin
2) click cmds.bat
If I do (1) the first command on cmds.bat fails (which I didn't notice because it happens fast). So, I succeeded skipping (1)
@DavidAlfa in your excellent guide you may remove the string "For more info, refer to the the readme file inside platform-tools package." and put in red "Don't follow instructions in the readme_English.docx file!" . That file is a trap for fools like me. :palm:
-
Ah, FW3202 platform tools has a weird english readme, not like the others, and it's missing the PDF file.
Will correct it.
Edit: Actually most Readme files were wrong!
Made new ones, you can check it out here (https://drive.google.com/file/d/1yFDQrwlPeBpM00uE537scOjtuh0O8ofv/view?usp=sharing) (If Hantek can't properly make a simple Readme, guess their programming quality lol).
Added usb fix, serial/model/Pcb fix and FW versions, so everything required to restore the scope comes in a single package.
Created new update package for 2022.09.21 software, keeping only the the update of the software (The FW isn't updated forcefully). Apparently It just updates Russian translations.
Created new FW package, adding FW3205. Seems for 3200+ only, breaks calibration on FW3000-3102.
Updated all Platform-tools packages with the new Readme and fixes.
(Edit:2022.09.28 was the same software as 2022.09.21, it just enforced the FW3205 update. So renaming to 2022.09.21.)
BTW, CH1 had became a lot noisier than CH2, picking up high frequency spikes of about 100mV.
Fixed by just twisting/pressing hard on the BNC connector! SO just try that if you're having a similar issue.
Both have now a noise of about 1/5 division at 2/20mV/div (1/10x).
Edit: Tapping on CH1 BNC creates some rattle noise, probably the nut is loose from one of the thousand times I opened it, which would explain the RF noise.
-
(Edit:2022.09.28 was the same software as 2022.09.21, it just enforced the FW3205 update. So renaming to 2022.09.21.)
David, it seems that the dso3kb_20220921.upk from your drive.google.com/drive/ doesn't update to the FW3205. The do_update.sh doesn't have such command:
#cp /dso/app/phoenix /mnt/udisk/
#cp /lib/firmware/psram_board_test.fs.bin /mnt/udisk/
cp $WORKPATH/package/help/help.db /dso/app/
cp $WORKPATH/package/font /dso/app/ -rf
cp $WORKPATH/package/root/* -rf /
#cp /dso/app/res /mnt/udisk -a
#cp $WORKPATH/package/app /dso/app/ -rf
#cp $WORKPATH/package/vga_test /dso/app/ -rf
#cp $WORKPATH/package/vga12MHz.txt /dso/app/ -rf
The dso3kb_20220921_fpga_3205.upk updates to the FW3205.
-
Its seems you didn't read properly:
Created new update package for 2022.09.21 software, keeping only the the update of the software (The FW isn't updated forcefully).
So anyone can update to this software version without flashing the FW. Is it clear now?
There's a FW3205 update package to manually update it, but also the original package was added to the "non-safe" updates that will update the fpga, causing issues in a non-compatible system.
Created new FW package, adding FW3205.
» Quick glance «
...
» For scopes coming with FW320x, update to FW3202, FW3203(Fix for noisy spikes in 4M/8M memory depths), or FW3205 (New version, barely tested yet).
Features or compatibility of FW3204 are unknown, but it seems to break the decoder, try installing FW3202 or FW3205.
...
» System Updates «
...
These can be applied safely:
...
» 2022.09.21 (https://drive.google.com/file/d/1N1TaaPTsAV9pub5Xd2EkSz97PG9JeCET/view?usp=sharing) (Only fixes Russian translation?)
...
These will update the fpga FW version:
...
» 2022.09.21_fpga_3205 (https://drive.google.com/file/d/1aZ4cIwubGv1Iry6b0HUmG3cXNivFX9mO/view?usp=sharing) -> Sets FW3205
...
» Firmware versions «
...
» 3205_B205 (https://drive.google.com/file/d/1pWF-eQEBvp5Im6o5HmSz9devawdxyBb8/view?usp=sharing) (Supposedly it fixes the decoding problems from 3204)
-
And what does meen this?
(Edit:2022.09.28 was the same software as 2022.09.21, it just enforced the FW3205 update. So renaming to 2022.09.21.)
-
Because I also got the package dso3kb_20220928 (https://www.eevblog.com/forum/testgear/new-hantek-dso2x1x-models/?action=dlattach;attach=1613920).
When checking the differences, the software (phoenix) was exactly the same (2020.09.21, same md5 hash), the only difference was the forced fpga update:
cp /lib/firmware/psram_board_test.fs.bin /mnt/udisk/#cp /lib/firmware/psram_board_test.fs.bin /mnt/udisk/
So I just renamed the 2022.09.28 package to 2022.09.21, which only updates the software, to avoid confusion with the nosense name 2022.09.28 (As the software is still .21).
Then the "original" 2022.09.21 that updates to FW3205 was renamed to 2022.09.21_fpga_3205.
-
Then the "original" 2022.09.21 that updates to FW3205 was renamed to 2022.09.21_fpga_3205.
Thanks. Now it's clear. I just didn't notice the file 2022.09.21_fpga_3205.upk on your drive.google.com/drive.
-
Because you're faster at finding issues than me at updating things, I was on the process of updating the Drive/FAQ when you posted, the file wasn't there yet :-DD
-
Updated Backup Builder, now all possible backup combinations are generated:
Removed Eeprom_backup package, now redundant.
» Backup Builder (https://drive.google.com/drive/folders/1C-AVyzPSpOOf30XQlBBK9Pm52k3cb7TO): Backups all important system data and builds three main update packages, so you can quickly restore them:
» dso3kb_CNxxx.upk: Restores Model, Serial, HW, FW, Generator calibration, preserving the existing software.
» dso3kb_CNxxx_FULL.upk: Restores Model, Serial, HW, FW, Generator calibration and dso, overwriting the existing software.
» dso3kb_CNxxx_EE.upk: Restores system EEPROM.
Extra packages:
» dso3kb_CNxxx_FPGA.upk: Restores only the FW (fpga).
» dso3kb_CNxxx_Calibration.upk: Restores only the Generator calibration.
» dso3kb_CNxxx_Model.upk: Restores only the Model, Serial, PCB.
» dso3kb_CNxxx_Software.upk: Restores only the software.
Additionally, it will create a tar.bz2 for each package to allow easy inspection of the files.
-
My scope broke down. It was switched on, but I wasn't using it, was just soldering something. I left a waveform on the screen from the previous measurement.
Suddenly it started making a clicking noise so I looked up. The screen is now blank, the startup relay keeps clicking about 2x a second and all the colorfull button lights blink as well.
It is as if the scope is trying to power on but the protection kicks in. I was hoping it may have overheated so tried a few hours later to switch it back on, but this behavior is now permanent. Maybe there is a short circuit or something?
Now I have to open it and look inside. Haven't opened it yet, about 10 months old and probably has 20-30 hours usage.
If anyone has an idea what could have gone wrong, please reply.
-
Might well be a power supply failure, it has been reported that the main diodes are a bit underrated and get very hot. I'd open the scope and check the power supply output voltages as a first check.
Th PS schematics (https://www.eevblog.com/forum/testgear/hantek-dso2xxx-schematics/msg4350379/#msg4350379) (and all the schematics, in fact) are here (https://www.eevblog.com/forum/testgear/hantek-dso2xxx-schematics/).
The diodes marked as D5 (two SS310 in parallel) are the "main diodes" I was referring to.
-
My scope suddenly lost calibration, and i cannot re-calibrate it, i get an error 0x511d1 only and have crazy DC offsets on both channels. I previously updated the software with the official SW update from the Hantek website, but i don't know what stock SW and FW was on the scope. Now it's on FW 3203, SW 220210.00. The scope worked fine for a week with this software. Can this be a software issue or is it hardware related? If anyone have a clue, please reply.
-
Install fw3102 and try calibration again.
Read the FAQ on Page 8
-
I'd open the scope and check the power supply output voltages as a first check.
Thank you for the advice and the links to the schematics.
I have done this, there is in fact something wrong with the PS board.
It has 3 voltages, +8V -8V and +5V and all of them are not stable, jumping all around the place.
If I supply +5V to the mainboard, the scope boots up and freezes at the HW initialize phase. I guess it needs the 8V rails.
I'm now checking the components on the PS board. The diodes look fine ...
-
Haven't opened it yet, about 10 months old and probably has 20-30 hours usage.
Surely Hantek provides at least a 1 year warranty? (but maybe not, I couldn't find any warranty info from a quick googling)
-
OK, my scope is back up and running.
Unsoldered the diodes and the capacitors on the secondary side, tested them one by one.
Also tested all the resistors. Unsoldered the buck IC and the DK124.
Couldn't check the transformer waveform since I had no working scope, but everything else checked out fine.
Started to loose hope. Injected voltage and checked the feedback circuit. Everything was OK.
Then I soldered wires to the optocoupler, and manually switched the diode side. The voltage drop on the diode was good but the transistor never went low resistance. :palm: Of course its always the last part you check.
I changed it with a through-hole 817C I had in my parts bin and the PS came back to life.
It now has stable output voltages.
-
Install fw3102 and try calibration again.
Read the FAQ on Page 8
Unfortunately this didn't help. I tried every possible combination of FW/SW also low level tools but the problem persist. Interesting is, if i change the vertical position of a channel, the change is not proportional. Like if i set vertical position to 0V on channel A, nothing connected to the probe, the yellow line stays at 2V. If is set offset to 1V, the yellow line moves to 2.1V. At about 2.2 V they meet, and then at 3V the yellow line is now 2.3V or something like that. The other channel behaves the same but with different proportions.
It seem as if a channel had a fix offset voltage and the vertical position now changed another offset on top of that but with much less power.
Since both channels does the same, and this happened during use, not after an upgrade, i suspect it's a hardware issue... Maybe somewhere in the offset signal generation part, around the opamp U20.2 - that's the only common thing in both channels offset circuit...
-
Then it seems a hardware failure...
-
OK, my scope is back up and running...
I changed it with a through-hole 817C I had in my parts bin and the PS came back to life.
It now has stable output voltages.
Congrats! Good to know the optocoupler is prone to failure.
...
If I supply +5V to the mainboard, the scope boots up and freezes at the HW initialize phase. I guess it needs the 8V rails.
I'm now checking the components on the PS board. The diodes look fine ...
Somebody also reported freezes when the power supply's TR signal (for line trigger) was absent, this could also be the cause of your freezing but, on the other hand, I've tested grounding this signal and the scope booted without problems
-
Surely Hantek provides at least a 1 year warranty? (but maybe not, I couldn't find any warranty info from a quick googling)
According to the warranty card that came with mine it's 3 years on the scope and 1 year on accessories. Of course, given the abysmal level of ongoing customer support they currently provide, I expect that warranty probably isn't worth the paper it's written on.
-
Huh? Probably stolen paper, printed by kidnapped kids.
-
DSO2D15 arriving tomorrow... eeekk.. can't wait.... seriously, who could? I mean, let's be real, DOOM !!!!!!!
il do the boring stuff first, check some wave forms and whatever, dump the firmware with DavidAlphas hard work and upload it etc, but then the serious work, the whole reason we are here, DOOM!!!!
hmm given the scope does seem a bit noisy (by all accounts) then I guess it is gonna be hard to work out idle time, think DOOM Screensaver!!!!
BaDboD
-
That's a pretty expensive DOOM running device though :-DD
-
getting a good framerate , 1993, PC eerr, yah no comparison, this is way cheap. Wonder if we can get Jetpac (ZX-Spectrum) qemu Z80? nope, DOOM!!! enough. Ideas on making it a screensaver, pretty sure some answer to the fact the CPU is never idle.
can we hook the trigger event? Squinting at code apprehensively, but if there is an event for trigger, and we dont see any for a while, BOOM!! DOOM!!
-
What governor is the kernel using?
(prelim investigation while awaiting arrival of the specimen to give it a good probing)
-
All the keys are functional, there's a picture in the Doom folder showing them.
Governor? 100% speed all the time.
-
ok, it has arrived.
DSO2D15
Software: 1.0.2.0.0(220831.00)
Hardware: 003.002.001.000.000.000.000.001
Firmware: 3205
now to bone up on the FAQ and back it up before I start pounding it looking for bugs :-)
I think IIRC the soft and firm are the latest you already have? FAQ time.
-
Anyone know how to get the Hantek software working?
Keysight Connection manager does not see it, the device is shown in device manager after installing Keysight IO Suite ( Hantek supplied and the latest from Keysight ):
USB Test and Measurement Device(IVI)
Windows 11 22H2
Searches are fruitless :-(
-
Try latest IO library suite (https://www.keysight.com/us/en/lib/software-detail/computer-software/io-libraries-suite-downloads-2175637.html) from Keysight.
Working for me, also with Win11 Pro 21H2
Tested in several USB ports, 2.0 and 3.0, the device was instantly recogniced in all of them.
I remember having a lot of trouble with the Hantek-supplied version, having to re-install the suite everytime I plugged the scope.
-
So I did my best to figure out a safe and simple way of triggering a factory reset from inside.
Relying on a computer to fix it is very inconvenient, what if you don't have any nearby?
So I used a early system poweroff/reset detection.
If the system hangs after the second Hantek logo, or the user interface stops responding, power it off several times following the instructions.
I added visual feedback by toggling the backlight when the detection is triggered.
Hopefully, with Factory Reset Daemon (https://drive.google.com/drive/folders/1BF4cnQXYHPw5Sy9HccncGCQkBNM03ldj), we will rarely need to use Platform-tools again!
As always, available on the FAQ section.
Procedure in action:
https://www.youtube.com/watch?v=CCiYBvx-cuU (https://www.youtube.com/watch?v=CCiYBvx-cuU)
-
yes, thanks for confirming. That was the the first one I tried, then the Hantek supplied one (just an older version) Very weird, I got it working anyway with the latest 2022 update 2 from Keysight after removing/re-installing every driver for every device in the system, not used to having problems installing drivers for anything, was a real 'remove driver, update driver, re-install drivers many times' fest.
First problem (hardware), being detected as a device by windows.
USB2 Mainboard, will not detect in one port, fine in the port next to it, fine with unpowered hub of any USB version in both ports.
USB3 Mainboard, ^^^^^ exactly the same no difference some ports fine other nada, all good with a hub
Extension cables or A->B cables: only supplied cable worked, all cables work if hub (powered or not,USB2 or 3)
-- Works fine in either USB2 or USB3 and generally if you have any problems you NEED a hub? err , hmm, yeh
Second problem (windows) once correctly detected as shown by device manager; getting it detected by Keysight IO connection expert.
Something in the driver stack refused to allow keysight IO to talk to the device even though correctly detected by windows. Event Viewer was it's usual 'as helpful as a stab in the eye' I still don't know what the fix was. Not my initial suspicion of Core Isolation or WSL2 (desktop runs in 'virtual' if you install WSL2) nor safe boot, which it wouldn't be anyway, the IO libraries are recent and signed.
good news though, the Hantek 6022BE worked fine no matter what I did, could not get it to fail. both hardware and software are way more robust. :-)
Did you want a copy of this backup? You seem to have these or newer version already. But if there is anything to be gleamed from a current factory state backup, it is all yours if you want it. The scope has been on for 24 hours, I have been twiddling asll the knobs, no crashing or bugs as I can find.
I would need to step back through the various threads and test each scenario, but everything seems fine, offset all good, low noise (earth needs checking , low noise with USB cable plugged in or attaching an earth anywhere actually so I think it is not connected in the unit? obs quite noisy without an earth)
Regards
BaDboD
-
If your software or firmware versions are already available, I don't need anything, but thanks anyways!
-
I'm currently at work on my V2 version. :) (Attachment Link) (Attachment Link)
I modified the native power supply, the result is positive, it heats up less and the signals become cleaner.
-
I did the same long time ago, added more ferrite beads, placed lots of tantalum capacitors all over the board, no difference.
Some people have tried toroidal transformers with linear regulators, also with minimal impact.
Likely the noise is induced by the board itself by nearby digital signals from the SPI, i2c, LCD...
Perhabs adding a ferrite bead to the LCD rubbing cable would help, but I definitely don't expect easy miracles.
Also this is a 2-layer board, where a 4-layer pcb would provide much better shielding.
-
I replaced the diodes on the secondary side of the power supply with more powerful and faster ones, this helped with its overheating, and at the same time improved the quality of the power supply and the picture on the screen. It's a pity, but I did not take pictures of the screen before the rework for comparison.
-
People is obsessed with these diodes.
Not denying the temperature, but I'm still waiting for the first case of failure ::)
-
R.E the unreliable USB, the supplied USB cable is junk. Lucky my grandad had one of these antiques lying around I could test with. Ill have to see if these relics of yore can still be obtained in a high quality version but I imagine even gold plate, audiophile grade USB connectors, would have rusted from the inside by now. Ill do that after I finish demagnetizing my CD collection for less hiss, broader sound-stage and lower THD. :-)
BaDboD
-
That's a pretty expensive DOOM running device though :-DD
Convenient phone charger. :-+
-
Convenient phone charger. :-+
But not reliable. :-DD
-
DSO2D15
SN 221002902xxxx
S 1.0.2.0.0.(220921.00)
H 003.002.001.000.000.000.000.001
F 3205
What is missing?
-
Seems fine :-+
Edit: New software update available: 2022.10.28
-
Seems fine :-+
Edit: New software update available: 2022.10.28
They tried to fix a bug with connecting 50 Ω in the generator, but they made new bugs. Now the voltage when switching the load of the generator abruptly decreases by 2 times.
It is necessary and sufficient that when the load is switched to 50 Ω, the generator voltage indicator shows 2 times less, and when the generator load is switched to 1MΩ, it shows the real voltage. Everything. |O
-
Hantek way: 2+2=? ??? "Delete this code"
-
Hantek way: 2+2=? ??? "Delete this code"
A math textbook was smoked at school. :palm:
-
I bought a new DSO2D15 last week. It had firmware 3204, unreliable USB connections and couldn't decode/trigger on UART. I backed up everything, installed firmware 3205, applied USB Fix, and restored Hardware info (from the backup). EVERYTHING I tried works now, including USB and UART trigger/decode. Despite all the bad things said, I love this scope! THANKS DAVIDALFA!!!!
-
I bought a new DSO2D15 last week. It had firmware 3204, unreliable USB connections and couldn't decode/trigger on UART. I backed up everything, installed firmware 3205, applied USB Fix, and restored Hardware info (from the backup). EVERYTHING I tried works now, including USB and UART trigger/decode. Despite all the bad things said, I love this scope! THANKS DAVIDALPHA!!!!
It's a Bingo, congratulations :clap:
-
Congratulations!
You're the first user reading the FAQ/thread, following the available instructions and finally making its first message without asking the same stuff again! :clap: :clap: :clap:
Yeah, not an engineering marvel, but if you got it cheap it's pretty decent.
What did you pay for it? Looked few days ago, prices had doubled since 2021.
Definitely not buying it for $350!!
-
$260 from an Amazon seller, including the DSO2D15 scope, two probes with various probe adapters and clips and cables and connectors. When I documented my experiences with the USB and UART decoding problems, and asked for a FW update, they forwarded me a zip archive of a "platform-tools_fpga_3205" folder layout with the FW3205 images and very terse installation instructions. I relied much on your FAQ for fuller context. Their instructions only covered the FW update; the scope's front USB was almost unusable after that, and the hardware info was missing from the System Info screen. But your advice and .upk files all worked like a charm to round out the final result of everything working nicely. (THANKS THANKS THANKS)
Here's what their cmds.bat looked like:
sunxi-fel uboot images/uboot_fb.bin
fastboot flash boot images/uboot-with-spl-spinand.bin
fastboot flash logo images/logo3.bin
fastboot flash dtb images/suniv-f1c100s-licheepi-nano.dtb
fastboot flash kernel images/uImage
fastboot flash rootfssize images/rootfs.size
rem fastboot flash rootfs images/rootfs.ubifs
fastboot -S 20M flash rootfsa images/rootfs.ubifsaa
fastboot -S 20M flash rootfsb images/rootfs.ubifsab
fastboot flash cache images/cache.ubifs
fastboot flash data images/data.ubifs
fastboot reboot
If it would be helpful, I can send you a link to a copy of the folder they sent me, particularly the images sub-folder that contains all the binaries used in cmds.bat. Cheers!
-
. . . they forwarded me a zip archive of a "platform-tools_fpga_3205" folder layout with the FW3205 images and very terse installation instructions.
If it would be helpful, I can send you a link to a copy of the folder they sent me, particularly the images sub-folder that contains all the binaries used in cmds.bat.
Could you please post the link to a copy of a "platform-tools_fpga_3205".
Thanks in advance.
-
Currently uploading to the Hantek drive ;)
I ran out of space, I'm migrating everything to a new account, links in the FAQ are currently broken, wait about 20 minutes.
-
Could you please post the link to a copy of a "platform-tools_fpga_3205".
Thanks in advance.
Sent via pm.
-
So in this update Hantek is no longer flashing rootfs.ubifs.
Turns out it's unnecessary (Blank filesystem?), can be skipped and directly proceed with flashing rootfs.ubifsaa and rootfs.ubifsab.
All the .ubi files are unused, seems to be the original ubi images before they were ubinized into the .ubifs files.
And sure, I tested this in the worst-case scenario, zeroing the whole flash, then restoring with this, worked perfectly.
After cleaning all the useless stuff the size dropped dramatically!
So much that I made a Platform-tools package with all versions fitting in just 47MB.
Added a simple choice script, simplified the driver installation into running "install_driver.bat", Zadig or Phoenix_msi are no longer required.
-
DON'T BUY HANTEK!
What buy? 8)
-
Could you please post the link to a copy of a "platform-tools_fpga_3205".
Thanks in advance.
Sent via pm.
I'm sorry, but I didn't get the link via pm. What is pm? - personal message? No link in My Messages. Could you please send the link once more.
Thanks
-
Yes PM means that.
I uploaded it here (https://drive.google.com/file/d/1SGp8NwiJbe4bTRL-qpoAJIw4TvO9CXC3/view?usp=share_link). I will delete it in a few days.
-
I uploaded it here (https://drive.google.com/file/d/1SGp8NwiJbe4bTRL-qpoAJIw4TvO9CXC3/view?usp=share_link). I will delete it in a few days.
Thanks
-
gaahh, I thought I had this working under Windows 11 22H2, but in my messing about it seems I had removed the 22H2 so it works on the previous, (21H2?) but not 22H2.
tested with fresh installs and several versions inc Win 10 22H2 (works) but does not in Win 11 22H2.
Also tried the latest IVI shared components from ivifoundation.org which work fine in all versions Except Win 11 22H2
If anyone has got it working then please let me know how.
BaDboD
-
How measure wfm/s without ext trig out?
-
No idea.
Anyone knows how to view exported waves exported in native LWF format? Or huge CSV files?
I mean, no simple csv to picture converters, but interactive viewers that let you move, zoom in/out.
-
https://github.com/mattdavis90/hantek-wave-viewer
-
Yeah, I knew it. But uses Python. Which I hate for several reasons.
It's nice for some scripts, but people use it for large workloads.
Any change to the window, movement, takes 5 seconds. Only uses 15% of the cpu...
Slow as hell and almost unusable controls. But lots of potential if done right.
In the end I exported to csv and used Flow CSV Viewer (https://www.waveworks.dk/flow/).
Works great, it's extremely fast and has a very handy interface.
-
Just to show a real screen shot of DSO2D15 UART decode, at 115200 baud, here it is. It was a stream of ASCII characters "ABCD...", using the UART "Spec data" trigger of 43x (the letter "C").
[attach=1]
The UART decoder seemed to cause lockups when used with misconfigured triggers. I found it helpful to keep UART decode turned off until I had my trigger working right. The UART decoder was reasonably stable when used with the UART trigger. I was able to configure an Interval Trigger to pick up the start of my uart stream, and that worked well.
-
If you're going to work a lot with the uart decoder, consider trying the patcher to get ASCII output instead hex.
-
Friends, does anyone know the purpose of the TR line of the power supply?
There is a positive experience of powering the digital part of the device from the power bank. The analog part can be powered from an isolated converter DC - DC 5 -> 2x9 volts, 0.13A, for example REC3-0509DRW, while my analog part is powered by a transformer.
-
Friends, does anyone know the purpose of the TR line of the power supply?
Probably Trigger Reference to mains, what most brands call a Line Trigger.
-
Friends, does anyone know the purpose of the TR line of the power supply?
Probably Trigger Reference to mains, what most brands call a Line Trigger.
It's precisely that, it shouldn't be necessary if not using line trigger.
But a user has reported problems (https://www.eevblog.com/forum/testgear/new-hantek-dso2x1x-models/msg4041589/#msg4041589) in the boot procedure when this signal is absent, but I tried shorting it to GND (https://www.eevblog.com/forum/testgear/hacking-the-dso2x1x/msg4085203/#msg4085203) (no problems, there are high-value resistors upstream) and the scope booted without problems.
As you can see in the schematics (https://www.eevblog.com/forum/testgear/hantek-dso2xxx-schematics/), the TR signal is not only connected to the triggering circuitry but also to the FPGA, as you can see here (https://www.eevblog.com/forum/testgear/hantek-dso2xxx-schematics/msg4270345/#msg4270345) and here (https://www.eevblog.com/forum/testgear/hantek-dso2xxx-schematics/msg4285249/#msg4285249). That may explain cristy's problems but, as I said, I didn't see anything strange in my case.
In the worst case, that signal can be recreated by a 50-60 Hz oscillator (555 or similar) for battery operation but I see in your experiment you didn't need it to boot the scope
-
That looks good. Can you tell me which diodes you used? Do they have to be 100V - Shottky - diodes? To me, 100V reverse voltage seems very high with 7.5V output voltage. I have several shottky diodes here, but all with a lower reverse voltage.
I would have to order them first, which is not worth the shipping costs.
Temperatures of >90°C at room temperature and opened device after a few minutes seems too high to me. In summer and when the unit is closed, it is probably much higher. :bullshit:
-
I used MBR10100 diodes in the TO220 package, which I had in stock, probably others in a similar package can be used to dissipate more heat and not heat the board. I hung a small radiator on the D5, now no place is heated more than 50°C. I believe that any Schottky diodes from 30V and a current of 3A in the TO220 package will do.
-
I used MBR10100 diodes in the TO220 package, which I had in stock, probably others in a similar package can be used to dissipate more heat and not heat the board. I hung a small radiator on the D5, now no place is heated more than 50°C. I believe that any Schottky diodes from 30V and a current of 3A in the TO220 package will do.
+1 i did it too with 58 max temp.
-
I think I will equip the oscilloscope with a linear power supply for the analogue part. Whether I will then have less interference on the signals or not remains to be seen.
I'm planning a 30VA, 2x 12Vac toroidal transformer, bridge rectifier and +-8V fixed voltage regulator, so one 7808 and 7908 each.
I will generate the 5V needed for the digital part with a buck converter, which I will supply directly from the first electrolytic capacitor after the rectifier via an LC filter. The TR output that is still needed I want to build 1 to 1 according to the original circuit diagram.
My main concern is reliability, so if the noise level drops, I would of course like that.
In addition, the much heavier weight would make the unit more stable, as it constantly slips when I even touch the mains cable or press a button.
The original power supply doesn't seem to be the most reliable to me, apart from the fact that the cheap Chinese power supplies usually don't last very long anyway.
-
The alteration of the power supply does not provide noticeable advantages in terms of noise relative to the original power supply modified by me, but it will allow galvanically decoupling the device from the mains. Enough 1 transformer with separate windings ~ 2x9V and ~ 12V. To power the analog part, a diode bridge and two capacitors 2200 μF 16V are sufficient, stabilizers 7805 and 7905 are installed on the board and additional stabilization is not required. You can supply voltage rectified and smoothed by capacitors from 2x9V to 2x18V. I powered the digital part from the power bank through the USB connector. Current 1A at 5V and 0.13A at ± 9V. The transformer is better to take R-CORE, it has less capacitance between the primary and secondary windings.
Currently, I limit the power completely to batteries.
Good luck!
-
As we all know, BMP format wastes a lot of space.
Everytime I wanted to share a picture I had to convert it manually - got really tired of it!
So I cross-compiled bmp2png (http://cetus.sakura.ne.jp/softlab/b2p-home/). Required some fighting but after a while I got it running.
Then I made a new mod package: bmp2png (https://drive.google.com/drive/u/4/folders/1_rFbaj1vycflRAPRTOp5f8PQxQyEvHfG).
It automatically finds and converts any screenshots.
Original files are deleted after conversion, new ones only take 12KB, finally in a proper format ready to be uploaded anywhere.
Just wait 5 seconds after the "saving" screen goes out to ensure the file was converted.
-
Everything works great :clap:
Waiting for screen recording 8)
-
Do you mean this? :D
(https://s4.gifyu.com/images/ezgif-2-20f7e738a4.gif)
-
:-+
Is it possible to do so?
And watch movies from a flash drive :-DD
-
Not in practical ways.
-
Do you mean this? :D
(https://s4.gifyu.com/images/ezgif-2-20f7e738a4.gif)
Rigol can this? ::)
-
link is dead at the moment
-
Which link? :-//
-
Which link? :-//
Starlink ;D
-
New official release: 2022.11.14 (http://www.hantek.com/uploadpic/hantek/files/20221114/dso3kb_20221028.zip).
Bt it's actually the same as the current 2022.10.28.
-
Now that's funny :-//. I guess releasing the same load multiple times fits well with their strategy of refusing to publish any release notes. |O
-
There is a support reply on Hantek's forum that notes one item that was fixed. About a wavegen period problem. About as close to a realease note as any they've given so far.
https://www.eediscuss.com/forum.php?mod=viewthread&tid=17260&extra=page%3D1 (https://www.eediscuss.com/forum.php?mod=viewthread&tid=17260&extra=page%3D1)
-
I just bought a DSO2D15 and the USB ports don't work. I tried to do the USB Fix update but the USB stick won't stay connected long enough for it to see the update file.
I just need this for audio work. Testing stereo amplifiers etc. When I return it to Amazon, what do you guys recommend instead around the same price point?
I'd like to have the frequency, RMS and pk-pk value displayed on the screen like this one can at the bottom. A math function to calculate power in watts at 8 Ohms from the RMS voltage in realtime and a good x/y Lissajous mode would be nice too :)
Here's the versions it came with:
(http://)https://photos.smugmug.com/Hobbies/Audio/i-cDpRHmz/0/c54a99d6/X3/20221115_070357-X3.jpg (https://photos.smugmug.com/Hobbies/Audio/i-cDpRHmz/0/c54a99d6/X3/20221115_070357-X3.jpg)
And a short video of what it's doing when I insert the USB stick:
https://mmanolio.smugmug.com/Hobbies/Audio/i-JdxGgTJ/A
Thank you!
--Mark--
-
Is it in FAT32 format? It does that when formatted as ntfs/exfat etc.
-
Is it in FAT32 format? It does that when formatted as ntfs/exfat etc.
I think so but I'll double-check. The computer won't connect to the rear port either. The app and the drivers are installed.
From what I've read on here about these, I think I'm going to return it anyway.
Any suggestions for a better quality replacement for similar or not too much more money?
-
Any suggestions for a better quality replacement for similar or not too much more money?
The Siglent SDS1202X-E is going for $339. !0x the scope keeping quality and usability in mind, but it does not have the FG built in.
These little Hanteks have very little to compare to them if you look at teh specs and the price. It's just a real shame they are such little dogs. In reality the only thing they have going for them is DavidAlfa. Hantek should be paying him a handsome salary. If it weren't for his efforts they'd get all their junk back.
-
Any suggestions for a better quality replacement for similar or not too much more money?
The Siglent SDS1202X-E is going for $339. !0x the scope keeping quality and usability in mind, but it does not have the FG built in.
These little Hanteks have very little to compare to them if you look at teh specs and the price. It's just a real shame they are such little dogs. In reality the only thing they have going for them is DavidAlfa. Hantek should be paying him a handsome salary. If it weren't for his efforts they'd get all their junk back.
Thank you Bill. That Siglent is currently on sale for $287.10 on Amazon! I can do without the built-in generator although that was convenient.
Agreed!!
-
That Siglent is currently on sale for $287.10 on Amazon!
Wow, that's amazing!
-
That Siglent is currently on sale for $287.10 on Amazon!
Wow, that's amazing!
You can run DOOM on it? :D
-
I have tried another solution and am satisfied with the result. I have attached a 5V fan with reduced 3.3V operating voltage with cable ties to the shielding plate of the motherboard, which blows directly onto the low voltage side of the power supply. Now, with the FLIR camera, I no longer see any components that heat up above 55°C.
Because of interference signals I have led the +-8V - lines through 2 ferrite rings (one at the power supply and one directly in front of the plug at the main board) and provided the outputs of all 3 voltages directly at the output of the power supply with 100nF - ceramic capacitors. Except for a certain background noise, all disturbing spikes have now disappeared. (Before, I could always see clear, individual needle spikes on the noise, sometimes with 3-4 times the amplitude of the noise).
It was already clear to me that this noise could not be eliminated; I already have two other Hantek devices. A PC DSO and a DSO multimeter with the same problems. I always hoped that the next (and more expensive) one would not have these problems. :-DD
In the meantime, I know what to expect from Hantek.
-
Do you have any pic for power mod and the result in screen ?
-
Got mine last night with incredible price, $125 :-DD
I bought 2C10 and luckily the mainboard's revision is 2D15.
Now Wave Gen function works like a charm. :scared:
Thanks DavidAlfa for all his modding works.
(https://i.imgur.com/nstSbTx.jpg)
-
Unfortunately, I did not take any photos. I soldered the capacitors from +5V, +8V and -8V to GND on the underside of the PCB. Then I disconnected the plug for the 8V from the main board, put it through the ferrite rings (on the power supply side only 1x straight through the ring, the one on the plug for the main board 2x through the ring, otherwise the cable would have been too short) and reconnected it. However, as it looks in your picture, this is not necessary, as I can't see any of "my needle tips" on the signal there.
For me, there were always small needles of 2 - 4x the "noise amplitude". I got rid of them with this. The noise itself is still there and I don't know how to get rid of it. DavidAlfa has already tried a few things without success.
The spikes on my device also only appeared after some time, so I suspect that there might be a defect in the filter capacitors in the power supply unit or something similar.
A rising ESR would be a possible cause. However, the measured values of the electrolytic capacitors were normal.
For additional cooling, I use a simple 50mm fan for 5V, which I connect to about 3.3V (5V from the power supply, via 2x 1n4007 in series as a voltage dropper).
The fan runs so quietly that I can no longer hear it at a distance of 50cm.
-
You can run DOOM on it? :D
Probably with a little work. You could also mow your lawn with a Porsche using a tow behind mower. :-DD
-
For me, there were always small needles of 2 - 4x the "noise amplitude". I got rid of them with this. The noise itself is still there and I don't know how to get rid of it. DavidAlfa has already tried a few things without success.
The spikes on my device also only appeared after some time, so I suspect that there might be a defect in the filter capacitors in the power supply unit or something similar.
A rising ESR would be a possible cause. However, the measured values of the electrolytic capacitors were normal.
Needles are caused by Schottky diodes heated above 85°C, their switching noise is directly proportional to the temperature. When I replaced them with larger ones with better cooling, the noise stopped as the temperature dropped.
Probably with a little work. You could also mow your lawn with a Porsche using a tow behind mower. :-DD
Porsche is a fairly low machine, it is convenient to scatter fertilizer on the lawn from it. ;D
-
Any suggestions for a better quality replacement for similar or not too much more money?
The Siglent SDS1202X-E is going for $339. !0x the scope keeping quality and usability in mind, but it does not have the FG built in.
These little Hanteks have very little to compare to them if you look at teh specs and the price. It's just a real shame they are such little dogs. In reality the only thing they have going for them is DavidAlfa. Hantek should be paying him a handsome salary. If it weren't for his efforts they'd get all their junk back.
Thank you Bill. That Siglent is currently on sale for $287.10 on Amazon! I can do without the built-in generator although that was convenient.
Agreed!!
I returned the Hantek and received the Siglent today.
Wow!! This is a night-and-day difference. The traces on this thing almost look like an analog scope. I can easily live without the AWG for my audio work.
My USB stick was recognized immediately and I have saved my setup and a few .png's already.
thank you again!!!
-
@ Russ3000
Then it would be logical for my changes to have an effect. Due to the fan, my diodes reach about 55°C, not over 90°C as before.
The additional capacitors and ferrite rings do not interfere with the function, so I just leave them in.
The lower temperature should generally ensure a longer life for the power supply unit. Electronic components don't like higher temperatures, especially the electrolytic capacitors in switch-mode power supplies are already under enough stress, so they don't need to be stressed with high ambient temperatures.
I dare to doubt that these Chinese "quality goods" can cope well with this, especially if you take a look at the entire device in terms of design errors and software bugs.
Sometimes I wonder if they test their devices or just assemble them and sell them as quickly as possible before anyone notices. :-DD
The power supply unit design itself is strange. I would have given the transformer another winding for the 5V and put the voltage regulation on the 5V rail. The +8V and -8V are then simply rectified and smoothed, since the regulation for the analogue part is on the main board.
Why generate the +5V from the +8V with an additional step down? :-//
It looks as if someone simply forgot the 5V and had to add it later, as the transformers had already been ordered.
-
I was also surprised by the wrong power supply, I was even going to remake it by winding the winding to 5V and connecting the stabilization circuit to it. I think this is the case when the managers defeated the engineers, they changed 1 winding of the transformer in 2 turns to the stabilizer chip. The fan is certainly good, but I am a supporter of passive cooling, so there is less dust and noise. The diodes I used in the TO220 package dissipate enough heat and without a fan the temperature does not exceed 48C. At the same time, I changed the capacitors to a solid electrolyte, they have 3 times less ECP and a higher operating frequency. I also advise you to replace the R10 resistor with 4.7k to increase the voltage at the outputs + -8V, I had + 7.2V under load, which is not enough, for good operation, the 7805 requires a difference between the input and output of at least 3V, while the input current decreases stabilizer + 5V.
This is not my first device made in China, before it was an LCR meter 1832C, which was successfully turned into 1833C, a useful device in the household, also an oscilloscope 2C42, which did not even have to be redone, but inconvenient in terms of control, you need to press a lot of buttons. If you use appliances at home for a hobby, then it is quite possible to buy Chinese ones. I had to study the scheme of the device, its action, I learned a lot of new things for myself, now I'm studying lithium batteries :) A useful acquisition.
-
In mine the power supply pcb revision was dated 7.2022 which is quite different with yours @Russ3000.
Pcb was printed +-7V, and I measured +7.5 and -7.3
Test points 5V on analog section are steady 5V.
Traces quite clean even out of the box but I want to improve it more. Recaped power filter caps with Pana FC 1000uf 35V x4, Sanyo Oscon 10uf 10v parallel x2 with smd cap on 5v rails.
-
@ Russ3000
I have the Hantek 2D42 handheld, the DSO2D10 and a USB oscilloscope sold by Conrad Electronic in Germany under the Voltcraft brand. This is clearly a Hantek DSO2090. Even the software interface looks identical. I also use the devices only for hobby and leisure. Only the USB oscilloscope is no longer in use and is gathering dust in the cupboard. (The device is simply a huge disaster and surpasses the other two by far in terms of bugs and errors).
I am currently also doing a lot of projects with lithium batteries. (Both types, i.e. LiFePo4 and Li - Ion).
-
In mine the power supply pcb revision was dated 7.2022 which is quite different with yours @Russ3000.
Pcb was printed +-7V, and I measured +7.5 and -7.3
Test points 5V on analog section are steady 5V.
Traces quite clean even out of the box but I want to improve it more. Recaped power filter caps with Pana FC 1000uf 35V x4, Sanyo Oscon 10uf 10v parallel x2 with smd cap on 5v rails.
I soldered the diodes and capacitors myself, so the board looks different. For normal noise suppression, the 7805 and 7905 require a difference between the input and output voltage of at least 3V, preferably more. allow up to 30V input voltage.
-
FYI, tried feeding the device with 48v DC (something that 110/220 switching power supplies usually eat well).
The led initialization is different, not all leds turn on, only "wave gen". After the boot screen all leds turn on for a split second and then only the correct mode ones are kept on. Besides that all seems to work as usual (although not extensively tested)
-
I got myself 12 Kg lead ingot mold, filled it with numerous and varied pieces of lead, melted it over a hot charcoal fire, then poured it into the back of my Hantek DSO2D15. Shortly after that my issues were all neatly cleared up. :scared: :-DD :-+
-
Porsche is a fairly low machine, it is convenient to scatter fertilizer on the lawn from it. ;D
Yeah, sure. No issues there.
-
Sth wrong with mine in usb connection.
Osc in testing overclocking mod with 696MHz CPU and 360MHz Ram and steady.
Everything begun with "Save to usb" when the osc in FFT math, progress 35% and hung. Tried many times.
Then any update firmware upk with "remove overclock", fix usb ... 35% progress and hang.
Now it cannot recognize usb stick. When I insert usb for 1st time osc has no response but it showed repeatedly "usb connected" and beeps despite of no usb stick anymore.
-
DavidAlfa, is it possible to get a PT24C02 i2c EEPROM dump in FEL mode? If possible, could you please make such a program?
Thank you very much in advance.
-
It only supports SPI memories.
But what's the purpose? Backup Builder already does this, also provides the raw binary inside a tar file, so you can extract it very easily.
As far as I know, nothing writes the EEPROM, so unless something very strange happens, it will stay unmodified forever.
-
I got myself 12 Kg lead ingot mold, filled it with numerous and varied pieces of lead, melted it over a hot charcoal fire, then poured it into the back of my Hantek DSO2D15. Shortly after that my issues were all neatly cleared up.
There is a better idea, take 4 18650 batteries for weight, at the same time and power the device from them. I tried it, it works, DC - DC converters arrived 12V -> 5V 1A and 12V -> + -9V 0.27A, turned it on from an external power supply. With this current consumption, the battery will last for 6 hours of operation.
-
In normal operation, 5V at 1A should be sufficient. However, I would have used a 2-3A converter, because one should not forget the USB on the front panel. (According to the USB 1.1 specification, up to 0.5A) Unless you don't want to use this connection. A USB stick doesn't need 0.5A, but you don't know whether someone might connect their small, external 2.5" HDD or a USB work lamp to it.
For example, I built a small hard drive from an old notebook into an external USB housing and formatted it in FAT32. It is in a case with the oscilloscope together with other accessories. (Yes, also a small USB light with a long gooseneck).
On it I also have the latest firmware version, all of DavidAlfa´s Hacks, the PC software for the oscilloscope and other useful programmes that you might need if you are out of town with the device, e.g. with like-minded friends who don't have an oscilloscope.
Of course, not every 2.5" hard disk works. Here I was lucky that it does not require more than 0.45A. But an SSD should generally work. However, I cannot say which size the oscilloscope supports at most.
With "h2format" or "fat32format" you can also format >32GB in FAT32.
-
This Hantek only recognizes usb stick but not card reader and microSD inside.
-
That is not unusual. My car radio does not recognise card readers either, as they usually need a separate driver. Windows comes with these drivers, so you usually don't even notice the driver.
-
This Hantek only recognizes usb stick but not card reader and microSD inside.
Might be formatted incorrectly.
Your post had me check a 8GB microSD card in a USB holder that I know is FAT32 4k cluster formatted in 3 Siglent instruments and they all recognized the drive.
-
Now my Hantek cannot recognize usb stick anymore. No way...
Rear usb stills ok but front has problem.
Maybe I have to disassembly mainboard for checking usb pin port cracking solders
-
Rear usb stills ok but front has problem.
Do you unplug the rear connector when plugging in a flash drive?
@masta_k74
I checked the work with a connected flash drive, the analog part consumes the most when loading, at 5V I found an inexpensive isolated 2A converter - HLK-10D11005. They'll bring it in and change it. I have a small USB hard drive with music on Raspberry Pi 3+ Volumio program
-
I found the cause of front usb problem, came from the Sany Oscon caps which I added in 5V digital supply. Don't know why but removing them makes usb stable again.
Test 3 times with and without these caps I can confirm the cause.
Now I replaced with Nichicon FW.
-
Where did you buy the caps? I currently have a problem with two photodiodes "BPW24R" from AliExpress. Both from the same seller there. They are definitely not photodiodes, not even normal diodes, but simply empty housings. There is no measurable value, no diode path, no resistance, no voltage when irradiated with light, nothing. It seems to me that there is a growing problem with fake components. Unfortunately, I have had the photodiodes here for a long time and can no longer complain about them. Unfortunately, I was stupid enough to trust the seller and did not check them immediately. |O
-
I put the batteries in, glued everything to the front panel, it works fine, there is no noise at all.
I had to put resistors on the 2x9 output, the block did not start at a large input capacitance 7805 and 7905
An open probe at maximum sensitivity, I did not expect this.
-
Mine was bricked last night, I think no way to recovering.
The osc can boots then hangs, no response from any key and NO TRACEs ! Front input area are quite hot when I touched the shields. Don't know why.
Everything was ok before. I checked again volts at all test points on mainboard are ok for both analog and digital section.
Win11 could see the rear usb plugged in FEL mode but cannot install driver (winusb).
-
Why can't you install the driver?
Check out the Automated driver installer (https://drive.google.com/file/d/1ClBnWNCki6yvNxTzKuZpO8ujkiu8wgWK).
-
Thanks DavidAlfa, I will try and report later.
Something wrong in front input section, they quite hot on shield's surfaces. No traces on lcd.
-
I got mine from damaged genuine audio board. I think oscons are best for digital decoupling but not for usb devices related. This is the 2nd time I met this problem. Last bug was PCIe to usb 3.0 card on my music server, the computer even not recognize Amanero board.
$Where did you buy the caps? I currently have a problem with two photodiodes "BPW24R" from AliExpress. Both from the same seller there. They are definitely not photodiodes, not even normal diodes, but simply empty housings.
-
You say the input area on the front panel gets very hot? Have you checked all three voltages? If something has gone wrong with the power supply due to the changes, that could well be the case. Above all, it doesn't have to happen immediately. I would check this first, before a voltage that is possibly too high destroys everything. :-BROKE
-
Hi DavidAlfa,
I've tried many times on both win 10 vs win 11, even win 10 never ever plugged osc before, but same problem with driver installing.
Tried zadig driver it was installed successful but Device manager still showed Unknown Devices #1. Restore.bat still "waiting for any devices"
(https://i.imgur.com/U9XjypB.jpg)
Why can't you install the driver?
Check out the Automated driver installer (https://drive.google.com/file/d/1ClBnWNCki6yvNxTzKuZpO8ujkiu8wgWK).
-
Yes, until now 2 shields still hot (or warm). 7v and 5v rails are ok. I've measured on 4 test point dots on mainboard.
Quite strange but I don't know what happened. Maybe these front input shortened but cannot happened for both channels.
You say the input area on the front panel gets very hot? Have you checked all three voltages? If something has gone wrong with the power supply due to the changes, that could well be the case. Above all, it doesn't have to happen immediately. I would check this first, before a voltage that is possibly too high destroys everything. :-BROKE
-
Opened shield covers, I see U27 and U24 very hot. So problem are here but what happened before I really don't know.
Maybe these ICs were shortened circuit.
-
Strange, I've tested it in both win7 and win11.
What about manual Zadig installation?
-
Driver from Zadig was installed successful but comp still doesn't see Hantek FEL, just only Unknown device #1 below Usb host tree.
-
U24 and U27 are supplied by the 7805 on the main board, which sits at the back of the signal generator directly near the connector where the Dual 8V go to the main board.
So from the dual 8V for the analogue part of the oscilloscope. Not from the +5V for the digital part.
Check the voltages on the 7805 there. I suspect something is wrong there.
-
Yes I knew it. I looked at schematic before.
Now I have to de-soldering U24 U27 and check it again.
Volts on every test point is ok. Look like electrical shock from power board when the osc was powered on last time.
-
Look like electrical shock from power board when the osc was powered on last time.
That's exactly what I think.
According to the LMH6702MA (U24 & U27) data sheet, a maximum of ±6.75 is permissible. (Absolute maximum ratings)
With 5V, this is close to its limit for an operational amplifier. I only know of operational amplifiers with a wider voltage range.
I've learned something new again. ;D
-
Sometimes it keeps the "unknown device" name, but if it appears correctly (Without any warning sign) it'll be ok.
-
DavidAlfa,
Tell me, please, have you ever encountered such a defect and is there any way to defeat it?
I have a DSO2D15 oscilloscope right unpacked "out of the box" by pressing the "Help" button after a few seconds it hangs tightly. At least I and another user of Dezmond 2 had this defect
After carefully reading the branch and your posts on Eevblog, I, just in case, made all the necessary backups (both through DSO Flash and through Backup Builder)
In my instance DSO2D15 Software. 1.0.2.0.0.(221028.00)
FW 3205
Board version DSO2D15_V1.7 2021.1.14
-
You need to write to the developers on the forum
https://www.eediscuss.com/forum.php?mod=viewthread&tid=17227&extra=page%3D1 (https://www.eediscuss.com/forum.php?mod=viewthread&tid=17227&extra=page%3D1)
-
Thanks. Reported to the DSO2D15 discussion
https://www.eediscuss.com/forum.php?mod=viewthread&tid=17269&extra=page%3D1 (https://www.eediscuss.com/forum.php?mod=viewthread&tid=17269&extra=page%3D1)
-
DavidAlfa,
I have a DSO2D15 oscilloscope right unpacked "out of the box" by pressing the "Help" button after a few seconds it hangs tightly.
- Make a backup with Backup Builder.
- Use Platform-tools to restore a fresh filesystem.
- Restore your dso3kb_CNxxxx.upk backup (Not "FULL").
- Apply latest update.
- Calibrate.
- Done.
-
Look like this Hantek for modding and relaxing or angriness (if anyone meet hardware problem as me) not for measuring |O
-
HARD-BRICKED RECOVERY REPORT :-DD
My scope was alive last night after many effort in hardware and software related recovery
1. Replaced 2 Opamp U24+U27 by AD797 smd (temporary). Scope was booted ok but hung as before.
2. Install Adb fastboot device driver (the most important step after FEL driver)
3. Platform-tools to restore filesystem
4. Update fix and lastest fw
5. Restore backup (any backup upk) but showed red error code -3 (DavidAlfa pls help me... :-DD)
6. Calibrate ok
7. Scope was rescued. Test functions and accuracy ok.
8. Test bandwith, limited ~ 4-5MHz due to AD797's bw but for audio hobby it's still ok.
9. Replace LMH6702MA later if I find any genuine parts.
-
Err -3, probably bad UPK, corrupted after removing the drive.
Put UPK files at the root of the usb Drive.
You can also use folders, but can't have spaces or it will fail.
Always use safe USB drive extraction method.
Don't use any Backup if not yours, doesn't make sense.
If not having your own backup, follow the README instructions in Platform-tools to restore your model/serial.
If you have wave generator, calibration will be lost, run calibration tool (In FAQ).
Ensure to read the FAQ!
-
9. Replace LMH6702MA later if I find any genuine parts.
https://de.aliexpress.com/item/1005002505634382.html?spm=a2g0o.productlist.0.0.1f4ae73d6ydBWi&algo_pvid=2676966a-966b-4c80-9e0a-53de501d305d&algo_exp_id=2676966a-966b-4c80-9e0a-53de501d305d-8&pdp_ext_f=%7B%22sku_id%22%3A%2212000020917443141%22%7D&pdp_npi=2%40dis%21EUR%214.83%214.68%21%21%21%21%21%400b0a0ae216690168967435162e25e6%2112000020917443141%21sea&curPageLogUid=8EcvjRrQhB6g (https://de.aliexpress.com/item/1005002505634382.html?spm=a2g0o.productlist.0.0.1f4ae73d6ydBWi&algo_pvid=2676966a-966b-4c80-9e0a-53de501d305d&algo_exp_id=2676966a-966b-4c80-9e0a-53de501d305d-8&pdp_ext_f=%7B%22sku_id%22%3A%2212000020917443141%22%7D&pdp_npi=2%40dis%21EUR%214.83%214.68%21%21%21%21%21%400b0a0ae216690168967435162e25e6%2112000020917443141%21sea&curPageLogUid=8EcvjRrQhB6g)
-
I found many replacement on Ali or Shopee but look like fake. Even any single opamp should be worked but bandwidth limited due to opamp hardware spec.
Ad797 now works fine but limited under 5MHz.
-
Of course, buying from Aliexpress always means buying at risk.
If you want it to come from a trustworthy provider, you can use this one, for example:
https://www.mouser.de/ProductDetail/Texas-Instruments/LMH6702MA-NOPB?qs=7lkVKPoqpbZhCbCGUzyOPg%3D%3D (https://www.mouser.de/ProductDetail/Texas-Instruments/LMH6702MA-NOPB?qs=7lkVKPoqpbZhCbCGUzyOPg%3D%3D)
Now that my problems with higher memory depth and the spikes that appear later at higher sensitivity have been eliminated, I will stop soldering on the hardware, at least until new problems appear.
The last thing I did was to desolder R11 in the power supply and bridge it to raise the dual 8V "a little". (I don't have any SMD resistors at home, otherwise I would have reduced R10 a bit).
I am still puzzling over how the OpAmps could burn out although the voltage regulators are still intact. So far, I know that in case of overvoltages, the regulators go completely to short-circuit or simply absorb the overvoltage without a pulse at the output. Especially since the voltage at the input can easily be 28V. Depending on the type, even more.
The only explanation I have would be an electrolytic capacitor you used in the power supply unit that had lost a lot of capacity or whose ESR was already in the completely unusable range. In other words, an extreme ripple with the switching frequency of the power supply. The normal fixed voltage regulators cannot handle this. I have already had defective voltage regulators and subsequent electronics with a normal 50Hz transformer and bridge rectifier, with a defective filter capacitor.
-
Maybe next time I will plan linear regulator using EI transformer as usual. Simple, clean and more safety than cheap and weak switching power due to cost cutting like this.
For 5V digital LM317 /LT1084
For 8V rails dual mono LT1963 are best ideal.
Now mine is working fine but power supply quite hot, every where. 3 Schottky's diodes, transformer, pcb... Even 1000/16v x4 are warm on aluminium body.
-
Now mine is working fine but power supply quite hot, every where. 3 Schottky's diodes, transformer, pcb... Even 1000/16v x4 are warm on aluminium body.
All heating comes from the diodes through the copper tracks of the board. It is necessary to replace the diodes with large ones so that they themselves dissipate heat.
-
Err -3,
You can also use folders, but can't have spaces or it will fail.
Yes, that's rite :-+
I've restored successfully !
-
Maybe next time I will plan linear regulator using EI transformer as usual. Simple, clean and more safety than cheap and weak switching power due to cost cutting like this.
For 5V digital LM317 /LT1084
For 8V rails dual mono LT1963 are best ideal.
Now mine is working fine but power supply quite hot, every where. 3 Schottky's diodes, transformer, pcb... Even 1000/16v x4 are warm on aluminium body.
I have thought about it long enough now and will convert to a linear power supply. This switching power supply seems increasingly suspect to me. I have nothing against switching power supplies in principle, but the implementation here is very strange. Somehow it looks as if they couldn't develop their own power supply suitable for this device and made a makeshift 5V for it in the circuit diagram.
(Just put an additional step-down converter on the +8V) The main thing is to make it as cheap as possible. This leads to the conclusion that the quality of the components was reduced to a minimum.
Sure, you can do it that way, but I call that a botched job.
(However, I will take over the generation of the line trigger 1:1 from the original circuit diagram).
-
On my D2C10 traces are very clean but the screen waveform fresh rate quite slow even I overclocked @720MHz CPU.
-
A photo of a new modified power supply appeared on the Internet, everything was done correctly there, a larger diode, 3 transformer windings and + 5V stabilization.
-
A photo of a new modified power supply appeared on the Internet, everything was done correctly there, a larger diode, 3 transformer windings and + 5V stabilization.
Modified by Hantek or by a user? Can you possibly post a link?
-
Modified by Hantek or by a user? Can you possibly post a link?
Nah, it seems they've replaced it at production. Stolen from 4pda ;)
-
The primary side has also been revised. There is now a MosFet in the primary part of the power supply. It seems that there were problems with the old one. So I think my plan to convert to a linear power supply is not nonsense in general.
-
I don't think so.
There's no single case of PSU failure, just people hyping around about the heat.
I had a lot of noise when I bought it, tried a lot of stuff, nothing made a noticeable difference.
Except...wait for it... Properly grounding the scope!
My wall socket used an old weird type with 3 pins (Socket J?), earth couldn't be connected with Shucko plugs.
Had a crazy amount of ringing, completely gone after installing a proper socket and throwing that trash away (Not the scope lol).
People have added 5kg to the scope by adding crazy toroidal transformers and huge capacitors, with little to no difference.
-
I replaced the switching power supply by a linear one.
One monstrous two polo filter taken from a Plasma TV board;
So, one 3A transformer, 6+6VAC transformer (not toroidal):
And circuits:
- 5Vdc source: 1x bridge rectifier, 2x 10000uF 25V caps, 1x LD1085 - V36 and two resistors (120r and 50r), a 10uF cap
- +8 -8Vdc unregulated power supply: bridge rectfier, 2x4700uf x 25V capacitors plus the TR signal components taken from 8VAC transformer.
The scope gain weight and stabilit for use too.
Noise has gone but the wave is not stable. I think small noise makes the zero crossing sensing craizy.
-
Yeah Mine is exactly this version. Pcb is printed "batch 072022".
But it still hot. I added 5v mini fan which flows directly to power board, it's quite ok.
Traces are super clean. No spike anymore at any div.
(https://www.eevblog.com/forum/index.php?action=dlattach;topic=257914.0;attach=1646546;image)
-
Modified by Hantek or by a user? Can you possibly post a link?
Nah, it seems they've replaced it at production. Stolen from 4pda ;)
Photographed with a lighter? :D
It makes sense to redo the power if it is possible to buy a suitable transformer. For the analog part, you do not need to make a stabilizer, just 2 windings with a midpoint, a diode bridge and 2 capacitors 2200 x 16V are enough. To power the digital part, any 5V stabilizer from a separate winding of the transformer is suitable, there are still their switching stabilizers. The main thing is to untie the ground wires of analog and digital power, they should meet only at the ADC chip. It will be right.
-
I wonder about noise vs power supply board
Mine was bought near 1 month ago, directly from taobao
Mainboard revision like all of yours, 2D15 dated code 2021
So if you improve or replace new better power board with same mainboard like me maybe you have same better result like me, but no any improvement here.
Now Im just only disappointed about waveform screen refresh rate
-
If you check carefully, the noise is mostly 2 LSB with some 3 LSB peaks.
So, if the ADC range is 0-255 and we have a "127" input signal, the noise would be doing 127,128,126,127,128,129,126...
I wouldn't expect anything better from a cheap scope running 1GSps ADC in a 2-layer pcb.
Perhabs wrapping the whole board in copper foil and grouding it would help.
-
In fact whole board is shielded by frame but more pcb's layers should help to get the best grounding.
@DavidAlfa : how to get or show the number 1GSa/s ? This number is randomly even at 50us and 1 channel selected.
-
If you check carefully, the noise is mostly 2 LSB with some 3 LSB peaks.
So, if the ADC range is 0-255 and we have a "127" input signal, the noise would be doing 127,128,126,127,128,129,126...
I wouldn't expect anything better from a cheap scope running 1GSps ADC in a 2-layer pcb.
Perhabs wrapping the whole board in copper foil and grouding it would help.
Before reworking the power supply, it looked like this to me, it's a pity the picture was not preserved.
-
how to get or show the number 1GSa/s ? This number is randomly even at 50us and 1 channel selected.
It depends on the time division used.
1Gsps can be only used with 4K memory depth.
1ns/a sample * 4000 = 4us, that's the max time it can capture.
Divide that by 12 divisions and you get 333ns/div.
I xan't remember, but probably only uses 1GSps in 200ns/div and lower.
-
@Russ3000
So slowly it went in that direction with me, although it wasn't quite that bad yet. It only appeared with me after some time. All in all, after about 40 - 60 hours of operation. That's why I installed the ceramic capacitors and the ferrite rings. That also helped for the time being. My guess is that this is the beginning of the end for the filter capacitors. If I touch the power supply again, I'll put a linear one in there and this aberration will be removed.
-
@DavidAlfa
I've attached some pics. Look like these are less noise than yours.
@Russ : it's quite terrible |O
-
@Russ3000
So slowly it went in that direction with me, although it wasn't quite that bad yet. It only appeared with me after some time. All in all, after about 40 - 60 hours of operation. That's why I installed the ceramic capacitors and the ferrite rings. That also helped for the time being. My guess is that this is the beginning of the end for the filter capacitors. If I touch the power supply again, I'll put a linear one in there and this aberration will be removed.
The installation of 3 MBR10100 diodes in the TO220 package helped me, it immediately became cool and the needles in the picture were completely gone. I was very surprised.
-
That would be a possibility, of course, but I have had so many defective switch-mode power supplies on my desk that nothing convinces me to use a switch-mode power supply that has been slimmed down so much for cost reasons that its durability is guaranteed to suffer. It doesn't matter to me in the least how heavy the device is or whether I "waste" 2W or 12W during operation. Reliability and low interference are far more important to me. (Even if you will probably never get this device completely free of interference).
-
If you do not save on details, you can make a reliable power supply. I myself developed power supplies for technological equipment and passed various certifications, it turned out very reliably and quietly, I can’t imagine a stabilized power supply for 12V 100A with a transformer. Normally, the input voltage is ～90-260V, transformer units cannot do this.
-
The installation of 3 MBR10100 diodes in the TO220 package helped me, it immediately became cool and the needles in the picture were completely gone. I was very surprised.
Diodes? I don't think so.
More like the capacitors you replaced at the same time, which are by far the most important components when filtering the spikes.
-
If you do not save on details, you can make a reliable power supply. I myself developed power supplies for technological equipment and passed various certifications, it turned out very reliably and quietly, I can’t imagine a stabilized power supply for 12V 100A with a transformer. Normally, the input voltage is ～90-260V, transformer units cannot do this.
Of course, there are cases where a switching power supply is appropriate (or absolutely necessary) and there are certainly high-quality and reliable power supplies, but the one used here seems rather questionable to me. As I said, I have had many defective power supplies of the cheapest type from China on my desk and I know the problems of these devices by now.
But that doesn't apply to all Chinese power supplies. They can also do it very well.
But you can see that immediately when you open it.
In general, I have nothing against switching power supplies, so please don't misunderstand.
I occasionally use and build switching power supplies with galvanic isolation, but so far only for small input voltages, e.g. to generate higher symmetrical voltages for amplifier circuits (audio).
(My last switching power supply, a regulated push-pull converter, 24Vdc --> 2x 44Vdc works in an old HiFi - amplifier to use it in the garden arbour at the photovoltaic system. The garden has no connection to the mains).
-
So I had some ultrafast 20ns 8A rectifiers (BYC58X-600), decided to make the test.
Replaced a capacitor I didn't last time (The 5V output for the digital power).
Cutted an aluminium thin foil, wrapped the power supply with it, grounded it with the board screws.
Last, I added a small toroid near the +-8V input connector of the analog side.
Seems like it might have -very slightly- improved the noise, but can't really tell..
Previously there was a subtle hiss noise coming from the psu, now its's completetely gone.
20mV looks pretty much the same.
-
Diodes? I don't think so.
More like the capacitors you replaced at the same time, which are by far the most important components when filtering the spikes.
[/quote]
The eldest son is studying at the Technion in his last year, they study diodes in depth, I asked him about the operation of Schottky diodes at elevated temperatures, he asked his professor, he replied that short reverse current surges are possible when heated above 100C, he explained the theory of the issue to me for a long time , but I didn’t remember much, because the children are smarter than me. :)
The main source of interference is the ground loop between digital and analog power, if there is a source of electromagnetic interference inside this loop, then they will be displayed on the screen. If I have free time, I will try to wind 3 turns of wire on the transformer from above, without disassembling the transformer, I will put a diode and a capacitor, I will start the feedback of the regulator and it will turn out to be more stable 5V, I will not connect the ground, but there is no need to stabilize + -8V, there are 7805 and 7905 on the board , they perfectly stabilize the voltage.
(My last switching power supply, a regulated push-pull converter, 24Vdc --> 2x 44Vdc works in an old HiFi - amplifier to use it in the garden arbour at the photovoltaic system. The garden has no connection to the mains).
I bought a large solar battery, I am waiting for the battery charge control unit with the MPPT system to arrive, I will experiment, the most interesting idea seems to be to convert the voltage to 230V and return it to the mains so that the energy company also pays money :)
-
They do increase reverse current with temperature, but nowhere to become a problem.
As you see, even at 150°C (Quite extreme conditions) the reverse current will get around 10-20mA, not optimal for power efficiency but a small current after all.
To cause these issues you need fast and large current spikes.
Or simply crappy (High ESR) capacitors not able to filter the high frequencies.
If you have time, try restoring the original diodes while keeping the upgraded capacitors, you'll see.
-
I bought a large solar battery, I am waiting for the battery charge control unit with the MPPT system to arrive, I will experiment, the most interesting idea seems to be to convert the voltage to 230V and return it to the mains so that the energy company also pays money :)
Unfortunately, this is not possible at the arbour, as there is no electricity grid.
The reason for converting the amplifier to 24V was to reduce conversion losses. You would have had to convert from 24Vdc to 230Vac first, and then transform back down to 2x 44Vdc in the amplifier's transformer power supply. In this case, the losses in the transformer and in the voltage converter are already significant, since only a limited capacity of batteries is available.
This is the clear advantage of the switched-mode power supply.
Of course, there is also a 230V inverter in the arbour.
We also have a petrol generator. In winter, you have to recharge the batteries when the sun is rarely visible.
So, enough off-topic :-X
-
Hi all,
Can you give me idea about U24/U27 opamp's speed could be related to waveform refresh rate on screen ?
Now I'm temporary replacing LMH6702 by Ad797 and the refresh rate quite slow and very annoying.
-
As you see, even at 150°C (Quite extreme conditions) the reverse current will get around 10-20mA, not optimal for power efficiency but a small current after all.
To cause these issues you need fast and large current spikes.
I suppose the temperature of the crystal is much more than 150 degrees, the diodes have a large thermal resistance of 48 ℃ / W, users on 4PDA have measured more than 100 degrees outside.
-
I don't think so, took one of the original diodes and tortured it.
Tests were done aplying 12V in reverse polarity.
Used a large solder tip, applying a blob of solder that almost surrounded the whole the diode, except one pin to avoid making a short.
The tip was placed and left untouched, each temperature step was applied for 1 minute.
185ºC 600uA
215ºC 3.25mA
230ºC 7.5mA
245ºC 19.5mA
At 215ºC it started to make that terrible burned electronics smell (No way this is the temperature inside the PSU).
Finally crancked the temp to 280ºC, it avalanched and died (Permanent short).
You replaced the diodes and the capacitors, then blamed the diodes, that doesn't make sense.
It's like if my engine is broke, replaced 20 pieces and blamed a random part.
The only way of getting a proper result is doing a procedural method, testing one element at a time.
I'm not discussing this topic anymore! :-DD
-
I'm not discussing this topic anymore! :-DD
Ok, let's leave the diodes and move on to the capacitors. before replacing, I measured the soldered capacitors, their ESR was 3 mΩ, the ones that I soldered showed 1 mΩ, not much less, I believe this did not lead to a noticeable reduction in noise.
-
Placed ferrite over the end of the long white cable coming from PSU (at scope end), surely any cable of length leading into the faraday should have this no?
Placed heatsinks on the 2 chips, deffo at least 5 or 6C above room temperature those chips were.
Added a 5v 20mm brushless fan pointing directly at the PSU (was almost 20C above room) Silent fan so no downside. Massive diode already on the PSU for an easy 5V, right there, for the taking, candy from a baby :-) IN4007 for a small drop as I do not want to cryogenically preserve the PSU. (yeh I know 1000V, but I got a whole bunch of them)
Result is impressive,
A) Made absolutely no difference whatsoever to the scope. This is good, did not adversly affect it in anyway way that I can tell.
B) Completley worth the effort, I just feel so much better now. Though a little dissapointed I did not need to break out the microscope for it but happy that my eyes are still good enough that I did not need to break out the microscope for it, unlike reading the instructions 'leaflet' provided with just about anything these days.
To be honest, since earthing the unit properly it isn't noisy. Nothing I have done is to fix anything, normally I would expect these types of things to already be there. Anyway, might wanna overclock it when Im playing DOOM (which is, after all, why we are all here).
There is a 240uV sine @ x1, 1.02mV, 2ns, but I'm pretty sure that is just there to troll.
-
I agree, but also remember that electrolytics are usually particulary bad a high frequencies, so the measured esr cannot be applied in the same way.
A flyback transformer usually causes some ringing at the secondary, at much higher frequency than the main switcher.
See Vsec? Doesn't it look quite similar to the noise seen on some scopes?
(https://i.stack.imgur.com/LHW13.png)
My proof is that it went away after replacing only the capacitors and properly grounding the wall socket.
Maybe we should bet some real money :-DD
-
A flyback transformer usually causes some ringing at the secondary, at much higher frequency than the main switcher.
Just the EMI ringing is generated by fast diodes when turned off, I encountered this when I was designing a power supply module with PFC, I had to put silicon carbide SiC diodes instead of Schottky diodes and the ringing stopped, otherwise it was impossible to pass certification. In the oscilloscope, I replaced the diodes with higher capacitance diodes, which most likely eliminated ringing during switching. I did not expect such an effect, I changed it because it got very hot. ;D
-
You quoted the translated output :D.
Yeah, we need someone with two scopes (Not another DSO2xxx), so he can see the secondary waveforms.
-
@Russ3000
What do you think about the F12C20CT as a replacement for the two SS310s in parallel in the PSU? However, this is not a Schottky, but a Fast Recovery Diode.
-
You can try, without experience you can not immediately say.
-
Hi everyone,
I am new to the group and I was pointed to this thread because I recently purchased a Hantek DSO2D10, which is their 2 channel 100Mhz Oscilloscope, which I am returning. I have found this unit extremely buggy and while I thought it would be a great scope for what I need it for, the bugs have become way to intrusive.
For example, if you change settings too fast, then the unit will completely lock up, and will act as though it's bricked. To fix this you have to reflash the firmware. Being that I tend to move quickly I wind up hitting this bug every few minutes, have to stop what I am doing, reflash the firmware and start over.
The other bug which has me really perplexed is its inability to accurately display proper voltage when you are trying to measure under 1V or is it 1mV, honestly, I can't recall, but I learned about this from a youtube who did a comparison between this unit and the equivalent Firsi and OWON, and sadly the OWON beat it out as far as accuracy, Needless to say, I am returning it.
Interestingly, I also have a Hantek 2D72 which is a 2 channel Scope, DMM, and Signal Generator, and I have not run into any similar bugs, I would be using this as my primary shop scope, but I have found the screen to be just too small for me. Thankfully, Amazon offered me a full refund on it, and advised me not to return it, so I decided to keep it and this way I have a spare scope to use during this time where I now have no desktop scope until I purchase a new one, however, which one to replace the DSO2D10 with, is something still under discussion in another thread where everyone is being extremely helpful.
Anyway, I thought you all might find this post useful since this discussion is about the Hantek 2Dxx models. and I thought I should share my experience which honestly has not been the best. Hope this helps.
Cheers,
Systops
-
The lastest firmware + hardware (psu) from manufacturer + modding from DavidAlfa + Schematics from Pcprogrammer make these Hantek become the best scope for electrical hobbies. Mine is best performance now for $120.
Of course for x3 price Rigol or Siglent should do the job better.
-
As I said, I will provide (at least the dual 8V) from a linear power supply. The device is well usable for hobby purposes, but there are clearly better oscilloscopes for small money. I will definitely buy a Siglent SDS1202X-E when I have some money left. Then follows a conversion to Li-Ion battery operation for the Hantek, as a mobile device for outdoor use.
-
I believe that the best solution for a battery power supply circuit would be 2x3 3.7V batteries with an equalizing and charging circuit, they power the analog part of the device with a midpoint, and power the digital one from an isolated DC - DC 9-32V at + 5V 2A, for example URB2405YMD-10WR3 .
A very good device for a hobby.
There was an idea to make a differential input from 2 channels .... I found a 100 MHz bistable relay and a place on the board where to insert it. To do this, it is enough to restart the signal CHANNEL_1_IN_M and connect it to CHANNEL_2_IN_P.
-
I was thinking of a stepdown to dual 9V @600mA and another to 5V 2A. Powered from a 3S3P pack of 18650 cells. For this version I would already have a BMS, a charger with 2A, the 5V - converter and 3 cells lying around here. Only the converter for the dual 9V and 6 battery cells I would still have to buy.
Thus, it is also possible to use the device during charging without any problems. (Of course, you should then ground it properly, otherwise you may get the interference from the SMPS - charger (Y - capacitor against isolated GND in the charger) directly into the oscilloscope and the circuit to be measured, which may not be so optimal.
-
2S is enough, providing 8.4V(100%) ... 7.4V(0%)
-
For charging, I use an external power supply with a transformer and there is no need for Y capacitors between the primary and secondary side. I tried the laptop power supply, the interference is small and without grounding.
I wanted to improve the 2x9V power supply, soldered 2.2 uF ceramic capacitors, the noise on the screen increased 10 times :) I soldered it back. At such frequencies, it is impossible to immediately understand how it will be better.
-
Some pictures of the PSU.
Switching frequency is 50KHz, but each pulse creates 100MHz armonics ???
Last picture is the secondary output before rectifier.
-
Hi DavidAlfa,
How can we see the effect of overclocking ?
I overclocked @720MHz Cpu and 360MHz Ram but the scope seems to be same as before.
-
@ DavidAlfa
This is the problem with square wave signals. One builds an oscillating circuit super fast without wanting or noticing it. Capacitance of diodes, inductance of conductors, capacitors etc. can cause the strangest effects. This is the reason why I like to work with a linear regulator. Sine signals with 50Hz are much easier to control than a square wave signal with 50kHz and its countless harmonics.
Even with a linear power supply, the diodes can produce high frequency noise. But usually much less.
-
Normal pattern for flyback.
It turned out a differential input of 2 channels and even works, now you can measure everything with just two probes, like a simple Fluke 106 :)
-
Hi DavidAlfa,
How can we see the effect of overclocking ?
Did you think it would sample faster? That's not how it works.
The user interface, the decoder and FFT speed are quite faster, but the adquisition part will be the same.
-
Normal pattern for flyback.
I don't see any snubber at the primary, so the terrible ringing makes sense.
Probably it could be eliminated or mitigated with a small RC snubber.
-
Normal pattern for flyback.
I don't see any snubber at the primary, so the terrible ringing makes sense.
Probably it could be eliminated or mitigated with a small RC snubber.
You can put such a damping scheme if it is not
-
PC software: I installed the drivers, windows recognized the device as "USB Test and Measurement Device (IVI)".
But neither DigitalScope or WaveEditor were able to connect, complaining with message "The device is not connected".
Edit: After reinstalling the driver with the scope already connected, it worked.
The custom waveforms can be set up to 25MHz too.
I have dso2d10, installed all the software and drivers, but now my laptop sees it as "USB Test and Measurement Device (IVI)" but the waveform generator and keysight app cant detect it i don't know why, I tried everything (my firmware is 3205 from manufacture)
after contacting hantek official store on aliexpress he advised running the app as administrator but no luck.
what could be the problem? everything else is good with my oscilliscoop
-
PC software: I installed the drivers, windows recognized the device as "USB Test and Measurement Device (IVI)".
But neither DigitalScope or WaveEditor were able to connect, complaining with message "The device is not connected".
Edit: After reinstalling the driver with the scope already connected, it worked.
The custom waveforms can be set up to 25MHz too.
I have dso2d10, installed all the software and drivers, but now my laptop sees it as "USB Test and Measurement Device (IVI)" but the waveform generator and keysight app cant detect it i don't know why, I tried everything (my firmware is 3205 from manufacture)
after contacting hantek official store on aliexpress he advised running the app as administrator but no luck.
what could be the problem? everything else is good with my oscilliscoop
Did you install the IOLibSuite_18_2_28229?
-
PC software: I installed the drivers, windows recognized the device as "USB Test and Measurement Device (IVI)".
But neither DigitalScope or WaveEditor were able to connect, complaining with message "The device is not connected".
Edit: After reinstalling the driver with the scope already connected, it worked.
The custom waveforms can be set up to 25MHz too.
I have dso2d10, installed all the software and drivers, but now my laptop sees it as "USB Test and Measurement Device (IVI)" but the waveform generator and keysight app cant detect it i don't know why, I tried everything (my firmware is 3205 from manufacture)
after contacting hantek official store on aliexpress he advised running the app as administrator but no luck.
what could be the problem? everything else is good with my oscilliscoop
Did you installed the IOLibSuite_18_2_28229?
Yes I did , before that it was generic USB i think, when i unistall the driver it appear as DSO2D10 but with a warning sign that the driver has some problem
-
Checked the primary snubber circuit. Original capacitor is 10nF.
Replaced with 47nF capacitor, 47K resistor, FR107 diode... Sadly no difference at all.
Even tried 100nF and 10K.
-
I tried to simulate the circuit, it turned out like this
TVS P6KE150A
D1 RGP25M-E3
-
I added a large capacitor bank of 6x10uf + 6x100nF to each output (+-8V).
Finally that seems to have done something , high frequency ripple is much lower now.
-
Oops. I had 4Mpt memory depth, which limits to 250MSps, so results weren't accurate.
Measured at 1GSps, it's now about 300mVpp on both +-8V. :horse:
-
PC software: I installed the drivers, windows recognized the device as "USB Test and Measurement Device (IVI)".
But neither DigitalScope or WaveEditor were able to connect, complaining with message "The device is not connected".
Edit: After reinstalling the driver with the scope already connected, it worked.
The custom waveforms can be set up to 25MHz too.
I have dso2d10, installed all the software and drivers, but now my laptop sees it as "USB Test and Measurement Device (IVI)" but the waveform generator and keysight app cant detect it i don't know why, I tried everything (my firmware is 3205 from manufacture)
after contacting hantek official store on aliexpress he advised running the app as administrator but no luck.
what could be the problem? everything else is good with my oscilliscoop
Did you installed the IOLibSuite_18_2_28229?
Yes I did , before that it was generic USB i think, when i unistall the driver it appear as DSO2D10 but with a warning sign that the driver has some problem
Are you using Windows 11 22H2? I currently have exactly the same as you using this windows version. Works fine in Windows 10 22H2 and windows 11 prior to 22H2, so roll back, if this is your situation, and it will work.
I am using vmware player with windows 10 22H2 guest and pass through the USB device from the host (Windows 11 22H2) , whie the host refuses to work, it works fine in the VM, but also tested roll back and various hardwares and VMs (virtual box also works but video capture....) , just windows 11 22H2 on any hardware or in a VM refuses to work with the symptoms exactly as you describe.
-
I added a large capacitor bank of 6x10uf + 6x100nF to each output (+-8V).
Finally that seems to have done something , high frequency ripple is much lower now.
I use DC - DC to power the analog part, I looked at the output signal, there was a lot of interference, I installed 2.2 uF capacitors relative to the case, like yours, the interference voltage decreased noticeably, and when measured on the screen, the interference became 10 times more. Returned everything as it was. :)
-
PC software: I installed the drivers, windows recognized the device as "USB Test and Measurement Device (IVI)".
But neither DigitalScope or WaveEditor were able to connect, complaining with message "The device is not connected".
Edit: After reinstalling the driver with the scope already connected, it worked.
The custom waveforms can be set up to 25MHz too.
I have dso2d10, installed all the software and drivers, but now my laptop sees it as "USB Test and Measurement Device (IVI)" but the waveform generator and keysight app cant detect it i don't know why, I tried everything (my firmware is 3205 from manufacture)
after contacting hantek official store on aliexpress he advised running the app as administrator but no luck.
what could be the problem? everything else is good with my oscilliscoop
Did you installed the IOLibSuite_18_2_28229?
Yes I did , before that it was generic USB i think, when i unistall the driver it appear as DSO2D10 but with a warning sign that the driver has some problem
Are you using Windows 11 22H2? I currently have exactly the same as you using this windows version. Works fine in Windows 10 22H2 and windows 11 prior to 22H2, so roll back, if this is your situation, and it will work.
I am using vmware player with windows 10 22H2 guest and pass through the USB device from the host (Windows 11 22H2) , whie the host refuses to work, it works fine in the VM, but also tested roll back and various hardwares and VMs (virtual box also works but video capture....) , just windows 11 22H2 on any hardware or in a VM refuses to work with the symptoms exactly as you describe.
Well, that explains a lot of things, I suspected it was from the windows version.
i will try to use a VM, but i used the software in compatibility mode where it can work in windows 8 or 7 environments with no luck.
-
PC software: I installed the drivers, windows recognized the device as "USB Test and Measurement Device (IVI)".
But neither DigitalScope or WaveEditor were able to connect, complaining with message "The device is not connected".
Edit: After reinstalling the driver with the scope already connected, it worked.
The custom waveforms can be set up to 25MHz too.
I have dso2d10, installed all the software and drivers, but now my laptop sees it as "USB Test and Measurement Device (IVI)" but the waveform generator and keysight app cant detect it i don't know why, I tried everything (my firmware is 3205 from manufacture)
after contacting hantek official store on aliexpress he advised running the app as administrator but no luck.
what could be the problem? everything else is good with my oscilliscoop
Did you installed the IOLibSuite_18_2_28229?
Yes I did , before that it was generic USB i think, when i unistall the driver it appear as DSO2D10 but with a warning sign that the driver has some problem
Are you using Windows 11 22H2? I currently have exactly the same as you using this windows version. Works fine in Windows 10 22H2 and windows 11 prior to 22H2, so roll back, if this is your situation, and it will work.
I am using vmware player with windows 10 22H2 guest and pass through the USB device from the host (Windows 11 22H2) , whie the host refuses to work, it works fine in the VM, but also tested roll back and various hardwares and VMs (virtual box also works but video capture....) , just windows 11 22H2 on any hardware or in a VM refuses to work with the symptoms exactly as you describe.
Well, that explains a lot of things, I suspected it was from the windows version.
i will try to use a VM, but i used the software in compatibility mode where it can work in windows 8 or 7 environments with no luck.
Compatibility mode really dont do anything, just lies to programs about the version of windows they are running on.
Depending on how you got to 22H2 version you should be able to go to windows updates settings and uninstall the 22H2 update. Keysight software starts working immediately (tested in several installation scenarios) but if you feel up to running a Virtualbox or Vmware (if your using PRO Win then you also have the built in virtual machines but I don't recommend it for your daily basher.) then download and install windows 10 (from Msoft site ) in a VM and your gold.
I can't tell if it is Windows or Keysight/ivifoundation problem, so dunno who needs to update or fix what, but it looks like windows is rejecting the Keysight VISA libs,as the IVI instrumentation device always shows waiting/failed to load extension driver when you view it's properties and check event logs. 22H2 implemeted/fixed/broke? some security 'features' around drivers and signing, though signing does not seem to be the problem soooo......
That it does not affect windows 10 22H2 leads me to think this is something about Secureboot/TPM/UEFI as this is the ony real difference at this level, but this is probably completely bogus and a total red herring? Disabling / enabling related features has no effect so until windows become less opaque I am stumped, hence the workarounds.
-
As stated here (https://www.eevblog.com/forum/testgear/jaycar-selling-rebadged-hantek/?topicseen), Jaycar Australia is selling rebadged Hantek scopes.
Seems a great opportunity of getting the source code, I've sent an email to them.
-
My scope's story is so funny.
Last time mine was bricked and lost 2 traces on screen without any reasonable cause. 2 opamp LMH6702 for front end input signal are very hot.
I replaced by 2x AD797 and the scope was alive. Everything is ok now but the response (refresh rate) quite slow and BW is limited @4MHz.
I ordered set of LMH6702 from China Shopee but they are look like fake.
After receiving these I've replaced one only on 2nd channel. OMG it was same behaviour as genuine one before. Hot, very hot and lost 2nd trace on screen. 1st channel is ok with ad797.
Then I replaced the 2nd "fake" one. Same results.
So what's happened?
The ICs code is easily cleaned by using cotton swabs with alcohol hahaha :palm:
(https://i.imgur.com/MfKFYMP.jpg)
-
PC software: I installed the drivers, windows recognized the device as "USB Test and Measurement Device (IVI)".
But neither DigitalScope or WaveEditor were able to connect, complaining with message "The device is not connected".
Edit: After reinstalling the driver with the scope already connected, it worked.
The custom waveforms can be set up to 25MHz too.
I have dso2d10, installed all the software and drivers, but now my laptop sees it as "USB Test and Measurement Device (IVI)" but the waveform generator and keysight app cant detect it i don't know why, I tried everything (my firmware is 3205 from manufacture)
after contacting hantek official store on aliexpress he advised running the app as administrator but no luck.
what could be the problem? everything else is good with my oscilliscoop
Did you installed the IOLibSuite_18_2_28229?
Yes I did , before that it was generic USB i think, when i unistall the driver it appear as DSO2D10 but with a warning sign that the driver has some problem
Are you using Windows 11 22H2? I currently have exactly the same as you using this windows version. Works fine in Windows 10 22H2 and windows 11 prior to 22H2, so roll back, if this is your situation, and it will work.
I am using vmware player with windows 10 22H2 guest and pass through the USB device from the host (Windows 11 22H2) , whie the host refuses to work, it works fine in the VM, but also tested roll back and various hardwares and VMs (virtual box also works but video capture....) , just windows 11 22H2 on any hardware or in a VM refuses to work with the symptoms exactly as you describe.
Well, that explains a lot of things, I suspected it was from the windows version.
i will try to use a VM, but i used the software in compatibility mode where it can work in windows 8 or 7 environments with no luck.
Compatibility mode really dont do anything, just lies to programs about the version of windows they are running on.
Depending on how you got to 22H2 version you should be able to go to windows updates settings and uninstall the 22H2 update. Keysight software starts working immediately (tested in several installation scenarios) but if you feel up to running a Virtualbox or Vmware (if your using PRO Win then you also have the built in virtual machines but I don't recommend it for your daily basher.) then download and install windows 10 (from Msoft site ) in a VM and your gold.
I can't tell if it is Windows or Keysight/ivifoundation problem, so dunno who needs to update or fix what, but it looks like windows is rejecting the Keysight VISA libs,as the IVI instrumentation device always shows waiting/failed to load extension driver when you view it's properties and check event logs. 22H2 implemeted/fixed/broke? some security 'features' around drivers and signing, though signing does not seem to be the problem soooo......
That it does not affect windows 10 22H2 leads me to think this is something about Secureboot/TPM/UEFI as this is the ony real difference at this level, but this is probably completely bogus and a total red herring? Disabling / enabling related features has no effect so until windows become less opaque I am stumped, hence the workarounds.
Aliexpress hanteck store just sent me that they tested Win11 and its working fine, i mentioned that it is only for 22H2 and will see if they can fix it somehow
Thanks for sharing your info
-
Plz don't quote whole post just for small info |O
-
My scope's story is so funny.
Last time mine was bricked and lost 2 traces on screen without any reasonable cause. 2 opamp LMH6702 for front end input signal are very hot.
I replaced by 2x AD797 and the scope was alive. Everything is ok now but the response (refresh rate) quite slow and BW is limited @4MHz.
I ordered set of LMH6702 from China Shopee but they are look like fake.
After receiving these I've replaced one only on 2nd channel. OMG it was same behaviour as genuine one before. Hot, very hot and lost 2nd trace on screen. 1st channel is ok with ad797.
Then I replaced the 2nd "fake" one. Same results.
So what's happened?
You can solder the chip from the generator, there will be 1 fast channel while waiting for the LMH6702 ordered in Mauser
-
The long story will be continued now...
This morning I've de-soldered the "genuine" U18 same chip for WG but didn't replace immediately to U27.
Instead I soldered back the hot U27 which I took out last time, to U18 position
OMG it is cool and run ok. WG works fine. So 2 U24+U27 maybe still stay safe.
But all "genuine" and "fake" LMH6207 I replaced to U24/U27 postions were hot, and all AD797 are fine.
I can't understand!
I measured volt at pads without chip, all volts are ok.
Pin 4,7 for power, 5V
2 3 input, nearly 0V, 6 output but floating around 400mV. I think all conditions are safe for LMH but they still were hot.
-
It sounds as if a high-frequency oscillation starts with the original OP, which is above the bandwidth of the AD. Unfortunately, I can't think of anything else at the moment.
-
LMH 's specs are far better than Ad797 except volts limited why AD797 works fine ? Both channel got same behaviour.
LMHs which I thought were dead before now run ok at U18 WG.
-
Compatibility mode really dont do anything, just lies to programs about the version of windows they are running on.
Depending on how you got to 22H2 version you should be able to go to windows updates settings and uninstall the 22H2 update. Keysight software starts working immediately (tested in several installation scenarios) but if you feel up to running a Virtualbox or Vmware (if your using PRO Win then you also have the built in virtual machines but I don't recommend it for your daily basher.) then download and install windows 10 (from Msoft site ) in a VM and your gold.
I can't tell if it is Windows or Keysight/ivifoundation problem, so dunno who needs to update or fix what, but it looks like windows is rejecting the Keysight VISA libs,as the IVI instrumentation device always shows waiting/failed to load extension driver when you view it's properties and check event logs. 22H2 implemeted/fixed/broke? some security 'features' around drivers and signing, though signing does not seem to be the problem soooo......
That it does not affect windows 10 22H2 leads me to think this is something about Secureboot/TPM/UEFI as this is the ony real difference at this level, but this is probably completely bogus and a total red herring? Disabling / enabling related features has no effect so until windows become less opaque I am stumped, hence the workarounds.
i used virtualbox to install windows 10 22h2 and installed all the files and keysight program but after installing windows didnt recognize it, only show as (base system device) without drivers installed
i tried to reinstall all software with no luck, my original system (windows11) still recognize it but VM don't i tried a lot of methods.
Modify message
-
Finally, after many attempts to connect my DS02D10 to PC, i installed windows 10 22H2 in virtual box (and enabled USB connection from VirtualBox settings) then after installing the latest software keysight IOLibsuite it installed the driver for me and i was able to connect to my oscillscoop FINALLY
many thanks for (badbod) for his helpfull info
-
Hello everyone,
I just bought oscilloscope and realized that the C10 model does not have a generator :(
I have a DSO2C10 oscilloscope with the generator disabled. I updated the software from FW3200 to FW3203, should that update enable the upgrade from 2C10 to 2D15 if the elements for the generator are mounted. Or do I need to do a model modification.
-
dinorijeka
With parts for the generator installed on the board (with a high probability there is a board from 2D15 in the oscilloscope), you can install the mod from DavidAlfa. I recommend that you first make a full backup using the mod. See instructions https://www.eevblog.com/forum/testgear/new-hantek-dso2x1x-models/msg3559217/#msg3559217 (https://www.eevblog.com/forum/testgear/new-hantek-dso2x1x-models/msg3559217/#msg3559217)
If a non-2D15 printed circuit board is installed, then you can install the missing parts yourself and then calibrate the generator. This thread has relevant information.
-
Thanks Altemir,
After I change the model and PCB with SCPI commands, the generator worked :)
-
So in this update Hantek is no longer flashing rootfs.ubifs.
Turns out it's unnecessary (Blank filesystem?), can be skipped and directly proceed with flashing rootfs.ubifsaa and rootfs.ubifsab.
All the .ubi files are unused, seems to be the original ubi images before they were ubinized into the .ubifs files.
And sure, I tested this in the worst-case scenario, zeroing the whole flash, then restoring with this, worked perfectly.
After cleaning all the useless stuff the size dropped dramatically!
So much that I made a Platform-tools package with all versions fitting in just 47MB.
Added a simple choice script, simplified the driver installation into running "install_driver.bat", Zadig or Phoenix_msi are no longer required.
DavidAlfa, I'm sorry, but what does it exactly mean "zeroing the whole flash" and how did you achieve this? Does "then restoring with this" mean that you used the platform-tools with this completely zeroed flash? Sorry for these questions. I'm asking because I'm not sure I understood you correctly. Thank you very much in advance.
-
It means I filled the entire flash with zeros, then Platform-tools restored it sucessfully.
-
Hi all,
Dear DavidAlfa,
My 2C10 was restored with 2 genuine LMH6702 and works fine now, except of lagging. In fact it seem to be lagged before.
When I tough the probe to signal then ~0.5s later waveforms appear on LCD and disappear same amount of time when I remove.
Response of traces also are lagged too. All range all kind of triggers and memory depth. Quite annoying.
Im using for calibration analog audio like tape deck. Frequency range is just only 50Hz-15kHz.
Look like mine is under-clocked, don't know why.
I reflashed all 3 times even no converting to 2D15 but no improvement.
Can you tell me yours "speed" ? Are you using without any notice about waveform response refresh rate which is make you crazy ?
-
Understand how a scope works - some situations are have lag by "design".
For example, if you set the Time division to 50ms, each division is 50ms, the scope have 12 divisions, so it takes 600ms to refresh the screen.
When the trigger starts samplng, the scope will start sampling the data, it will take that time in $50 and $5000 scopes.
-
Hi there David, (and others)
Is there a summary of all this information (56 pages of it) ?
The links in your sig are helpful but seem out of date and don't have any general information (noise and other things)
Has any one tried to fit the Ethernet port? I had seen you put some kind of chip there, but another page showed it was possible on old DSO5xxx series.
https://diylazy.wordpress.com/2019/06/11/hantek_ethernet/
Thanks,
-
It means I filled the entire flash with zeros, then Platform-tools restored it sucessfully.
Below is the result of restortion of the filesystem using platform-tools when the entire flash was filled with zeros.
1. in a HEX-editor 138412032 bytes were filled with 0x00, saved in a file «00 flash 132MB dump.bin», posted here
2. copied the file «00 flash 132MB dump.bin» to dsoflash order, renamed to „restore.bin“
3. using dsoflash write.bat wrote the „restore.bin“ to the flash memory, a copy of command promt window posted here
4. using dsoflash read.bat read the flash memory to the backup.bat file, compared to «00 flash 132MB dump.bin», the files were identical
5. restored the file system using platform-tools 2022.07.07_fpga_3205: 3 errors, the device did not start, black screen
6. using dsoflash read.bat read the flash memory to the backup.bat file, renamed to „00 platform-tools-David-2022.07.07_fpga_3205_ read.bin“, posted here
7. examened the „00 platform-tools-David-2022.07.07_fpga_3205_ read.bin“ in a HEX-editor. The resalts posted here.
So, this test shows that the platform-tools was unable to restore the file system if the entire flash memory was filled with 0x00.
-
Try running "Fastboot erase NAME", where "name" is the partition (boot, rootfs, data...).
-
Try running "Fastboot erase NAME", where "name" is the partition (boot, rootfs, data...).
Should I do this before platform-tools with zeroed flash, or now after the test and then platform-tools once more?
-
Not required. It always worked until people started creating artificial conditions.
Try also "dsoflash erase". That should set the entire flash to "FF”, which is the natural erased state of flash. \$\Omega\$
-
Not required. It always worked until people started creating artificial conditions.
Try also "dsoflash erase". That should set the entire flash to "FF”, which is the natural erased starte
Thank you very much. This is exactly what I expected to hear from you.
-
Has any one tried to fit the Ethernet port? I had seen you put some kind of chip there, but another page showed it was possible on old DSO5xxx series.
https://diylazy.wordpress.com/2019/06/11/hantek_ethernet/
Thanks,
Do you play DOOM online?:D
There is no Ethernet in this device, you can connect MAX 232 and communicate with a computer via a serial port, if you have one.
-
Has any one tried to fit the Ethernet port? I had seen you put some kind of chip there, but another page showed it was possible on old DSO5xxx series.
https://diylazy.wordpress.com/2019/06/11/hantek_ethernet/
Thanks,
Do you play DOOM online?:D
There is no Ethernet in this device, you can connect MAX 232 and communicate with a computer via a serial port, if you have one.
No Doom for me, Yet, (currently my co worker is is always raving about his offline god mode)
There is a foot print of a Network port on the Main PCB, and a foot print another ic, but this is where it seems to differ from the DSO5xxx.
Are there any unpopulated spots on he bottom?
-
Here is a schematic of the unsoldered parts.
-
Good news! After emailing Jaycar few days ago, I got the source code (https://drive.google.com/file/d/1gZkmB5yC0EUMcqwdEsGccjX9LU5HAXN0)!
Includes Kernel, uboot and fpga i2c & spi kernel modules (Which seem to include some interesting info, commands...)
Definitely for this device: "linux/arch/arm/boot/dts/suniv-f1c100s-licheepi-nano_dso2dxx.dts".
Edit: Everything compiled easily with minor modifications to build.sh/Makefile, replacing the cross-compiler with arm-linux-gnueabi- and fixing the paths.
Tomorrow I'll be playing with it, trying to add networking / USB Wireless / SD support.
-
:clap:
Wireless is certainly good, will it be possible to fix program bugs in the device itself?
-
:clap:
Will it be possible to fix program bugs in the device itself?
No :-//
-
Thank you very much. This is exactly what I expected to hear from you.
I did the test.
As you said, platform-tools failed to recover if the memory was fully written with 0s, including the ECC area.
However, after restarting the scope, now the memory was flashed correctly.
So I modified the Platform-tools script to detect this.
If flashing fails, it will erase everything, reboot and try flashing again.
At leats for me, it's working perfect!
-
Here is a schematic of the unsoldered parts.
Thanks!
Can you advise what some of the bugs that need to be resolved?
Wireless or any kind of network would be great.
-
Effectively, platform-toosl fqiled to flahs a fully "zeored" flash including the ECC area.
However if you restart the scope and run flash again, it works.
I modified the Platform-tools script to erase everything before flashing, hopefully will work perfectly now, give it a try!
What does "Effectively, platform-toosl fqiled to flahs a fully "zeored" flash including the ECC area" mean?
Thank you for modification of the platform-tools. Still not updated.
-
Sorry, my thick fingers and the phone keyboard aren't good friends - Edited. ;)
Yeah, I noticed there were some conditions I wasn't handling that could cause an endless loop in the script.
Fixed, uploaded.
-
Here is a schematic of the unsoldered parts.
Thanks!
Can you advise what some of the bugs that need to be resolved?
Wireless or any kind of network would be great.
Everything is described by the link, if you find more bugs, add them, let the developers fix it.
https://www.eediscuss.com/forum.php?mod=forumdisplay&fid=44 (https://www.eediscuss.com/forum.php?mod=forumdisplay&fid=44)
-
Hi DavidAlfa,
Pls add more useful functions, such as WG setup memory (frq, volt output, offset) then save and fast recall through F0 F1 F2... F5.
:-+
-
I can't do that, I'm not a programmer, neither I have Hantek software sources, all I do is some simple tweaking.
-
Hi, I have a fairly new Hantek DSO2D10
I noticed now that I have a deviation of about 0.5V and reach 1V pk-pk (i think it is AC voltage) I tried to eliminate but don't know how
i noticed that my body has AC voltage with 60Hz and 20V RMS when touching the ground so i bought some arm-grounding strip and connect it to oscilloscope GND, RMS now about 2V but still there and as you see here it makes the signal distorted
(See attachment )
-
Actually impossible when using a proper test probe. However, if you measure with the crocodile clip cable, this is not impossible. That is why a proper test probe is included.
If this happens with the test probe, it may be defective or your socket may not be properly earthed.
-
Actually impossible when using a proper test probe. However, if you measure with the crocodile clip cable, this is not impossible. That is why a proper test probe is included.
If this happens with the test probe, it may be defective or your socket may not be properly earthed.
My oscilloscope is floating with no earth connected. i'm using the test probe. when i completly remove the probe it disappear but when i just remove the probe head it seams to reduce the distotion alot. i dont know my probe head is deffective or what but its fairly new and i have 2 all with same problem
-
Abdoh_2000
You will have to disassemble the device and measure the + 5V analog power point.
-
Hi, I have a fairly new Hantek DSO2D10
I noticed now that I have a deviation of about 0.5V and reach 1V pk-pk (i think it is AC voltage) I tried to eliminate but don't know how
i noticed that my body has AC voltage with 60Hz and 20V RMS when touching the ground so i bought some arm-grounding strip and connect it to oscilloscope GND, RMS now about 2V but still there and as you see here it makes the signal distorted
(See attachment )
Your body works as an antenna and picks up on the electric field the mains puts out. Proper grounding the scope might reduce this a bit, but when touching the probe tip with your finger you still pick up on this.
My oscilloscope is floating with no earth connected. i'm using the test probe. when i completly remove the probe it disappear but when i just remove the probe head it seams to reduce the distotion alot. i dont know my probe head is deffective or what but its fairly new and i have 2 all with same problem
The top part that you can disconnect from the probe is an extension to the tip without shielding and also acts as an antenna. All normal behavior.
-
Hi, I have a fairly new Hantek DSO2D10
I noticed now that I have a deviation of about 0.5V and reach 1V pk-pk (i think it is AC voltage) I tried to eliminate but don't know how
i noticed that my body has AC voltage with 60Hz and 20V RMS when touching the ground so i bought some arm-grounding strip and connect it to oscilloscope GND, RMS now about 2V but still there and as you see here it makes the signal distorted
(See attachment )
Your body works as an antenna and picks up on the electric field the mains puts out. Proper grounding the scope might reduce this a bit, but when touching the probe tip with your finger you still pick up on this.
My oscilloscope is floating with no earth connected. i'm using the test probe. when i completly remove the probe it disappear but when i just remove the probe head it seams to reduce the distotion alot. i dont know my probe head is deffective or what but its fairly new and i have 2 all with same problem
The top part that you can disconnect from the probe is an extension to the tip without shielding and also acts as an antenna. All normal behavior.
if i act as an antenna why it becomes very small when i remove my legs from the floor, shouldn't my body still antenna ?
i thought we have some electricity leakage at first.
also how i can eliminate this especially that my house is not grouned, and we have only two 120V lines out of phase which create the normal 220V
-
Abdoh_2000
You will have to disassemble the device and measure the + 5V analog power point.
i would rather not break the warranty and solve it without opening it (it cost me most of my hardware budget :D) i tried buying better brand but this had a good price
-
My oscilloscope is floating with no earth connected. i'm using the test probe. when i completly remove the probe it disappear but when i just remove the probe head it seams to reduce the distotion alot. i dont know my probe head is deffective or what but its fairly new and i have 2 all with same problem
That's normal, a floating probe will pick up anything from the air.
Removing earth connection will make it worse.
-
if i act as an antenna why it becomes very small when i remove my legs from the floor, shouldn't my body still antenna ?
i thought we have some electricity leakage at first.
also how i can eliminate this especially that my house is not grouned, and we have only two 120V lines out of phase which create the normal 220V
:) I have never tried that, remove my legs from the floor that is, when touching the probe tip. An electric field's behavior is not my expertise, all I know is that it is what is causing the scope to pick up a signal when the probe is not connected to any test signal, or touched with your finger. The fact that you have a multi phase mains might make it behave differently. DavidAlfa wrote in this thread that he had problems with his scope due to the lack of a proper grounding, so it might be also the cause of your problems.
-
My oscilloscope is floating with no earth connected.
Are these scopes specifically designed to work this way (I seriously doubt they are)? If not, you may want to get an earth connected for a multitude of reasons. Picking up line frequency hum is just one of the more obvious, but the most important is that if there was a failure in the power supply it could destroy a DUT or even kill you.
-
The PSU has the usual 2-4nF capacitors between live and earth.
No earth will cause everything to get slighly energized.
-
Thanks for your info, i know the downs of not having earth connected especially the (you may die if it failed) but my house wiring has no ground, it was built way back where grounding was not enforced i think.
what my options are in this case ?
i want to add that i have big G.S.M tower on top of my house for one of the local companies, i'm afraid that it may cause interference on my circuits (what a bad house to design circuits :) :))
-
What I have done, since I don't trust my house wiring, is pound two 3m long pieces of re-bar into the ground just outside the window to my electronics room. I have connected them together with a 10AWG copper wire and connected that to the earth wiring and to the neutral. This way I have a good solid earth and my neutral is properly bonded to earth.
I do not know if this is possible for you or not, but it might be a solution. Can you determine which conductor in your house wiring is neutral?
Didn't Saudi change from ~127V to 230V in teh last couple of decades?
-
what my options are in this case ?
You need to conduct an experiment, go to someone's house outside the range of the radio tower.
I am more than sure that the +5V voltage of the analog part of the device.
-
What I have done, since I don't trust my house wiring, is pound two 3m long pieces of re-bar into the ground just outside the window to my electronics room. I have connected them together with a 10AWG copper wire and connected that to the earth wiring and to the neutral. This way I have a good solid earth and my neutral is properly bonded to earth.
I do not know if this is possible for you or not, but it might be a solution. Can you determine which conductor in your house wiring is neutral?
Didn't Saudi change from ~127V to 230V in teh last couple of decades?
Im afraid i can't do that, first im in the third floor. second it maybe surprising but actually i don't have access to the earth, all roads either asphalt or ceramic floors.
the only actual ground is across the road :) :)
Yes now Saudi Arabia switched new building to 220V for each phase, but i live in old building with 120V/phase with no neutral (i thinks the neural is available in the main breaker but because no one use 120V they just ignore it i)
-
You need to conduct an experiment, go to someone's house outside the range of the radio tower.
I am more than sure that the +5V voltage of the analog part of the device.
Sorry, i didn't get you on the second line
you mean +5V is causing my problem ? and can you explain why is that
thanks
-
What I have done, since I don't trust my house wiring, is pound two 3m long pieces of re-bar into the ground just outside the window to my electronics room. I have connected them together with a 10AWG copper wire and connected that to the earth wiring and to the neutral. This way I have a good solid earth and my neutral is properly bonded to earth.
I do not know if this is possible for you or not, but it might be a solution. Can you determine which conductor in your house wiring is neutral?
Didn't Saudi change from ~127V to 230V in teh last couple of decades?
Im afraid i can't do that, first im in the third floor. second it maybe surprising but actually i don't have access to the earth, all roads either asphalt or ceramic floors.
the only actual ground is across the road :) :)
Too bad.
An isolation transformer might help with the safety aspect, but it may not help much with the noise.
-
You need to conduct an experiment, go to someone's house outside the range of the radio tower.
I am more than sure that the +5V voltage of the analog part of the device.
Sorry, i didn't get you on the second line
you mean +5V is causing my problem ? and can you explain why is that
thanks
Are you measuring the signal from the calibrator?
Here is his diagram. The transistor operates in the key mode, switches 1000 times per second, the output is a meander. When the transistor is open, the output is 0V, and when it is closed, the +5V analog supply voltage is supplied to the output through resistors R523 and R517, we see it at the top of the pulse, with a normal +5V analog supply there is a straight line.
-
Too bad.
An isolation transformer might help with the safety aspect, but it may not help much with the noise.
Maybe he has water or heating pipes in his flat. Sometimes you can also use these as earthing.
(Even if this is not optimal, it can help).
-
Too bad.
An isolation transformer might help with the safety aspect, but it may not help much with the noise.
Maybe he has water or heating pipes in his flat. Sometimes you can also use these as earthing.
(Even if this is not optimal, it can help).
;D we only have air conditioner, its hot even in winter :)
i have a question off-topic, how much power can the function generator output?
i looked in the datasheet of the device but nothing mentioned,
-
Close to nothing. it's just for signal/very low power.
There's a 50 Ohm resistor in series, any load will bring the amplitude down.
-
Close to nothing. it's just for signal/very low power.
There's a 50 Ohm resistor in series, any load will bring the amplitude down.
and for the last 2 days, i was playing with a speaker connected directly to it and was happy because it had a loud sound, where i can find all diagrams before i break something?
-
Schematics can be found here https://github.com/pecostm32/Hantek_DSO2000/tree/main/Schematics (https://github.com/pecostm32/Hantek_DSO2000/tree/main/Schematics)
-
;D we only have air conditioner, its hot even in winter :)
Do you have metal drain pipes? They do make a very good earth ground.
Once you do hook up a ground, if you can, it would be an idea to put an RCD/GFI in line with your lab power supply.
-
Hi
New member here. Sorry if I missed something, this thread is 58 pages long...
I'm getting myself my first oscilloscope. I will use it for microcontroller stuff - I2C, SPI, looking at power supply ripple, audio signals etc...I was decided on buying Hantek DSO2D15 but got scared when I heard of software issues. Apparently it was freezing at times. So in short, have these issues been solved? Is it a workable oscilloscope now?
-
It works as for anything I've needed it for. At least does what it says it should on the data sheet. Any issues likely can be improved with updates.
I would recommend pushing a bit more budget for something like a Siglent or Rigol.. but having the built in function generator has been useful.
-
The freezing issues wete mostly solved.
Check the FAQ at my signature.
-
But in your signature it says Don't buy Hantek ;D
I may be posting this in wrong thread but quickly I haven't found right one. Which oscilloscope would you recommend for my purpose, DSO2D15 or Rigol DS1102Z-E?
-
The decoder works pretty bad, a $6 logic analyzer Will do much better.
I say don't but Hantek because while the made small fixes, they added more bugs, some really affecting how you can use it
-
ah ok then.
Better not risk it with Hantek then.
-
If you need trusted tool for work, go for Siglent and Rigol but x3 price.
Hantek is only for hobbies and relaxing (if you like modding)
-
If you need trusted tool for work, go for Siglent and Rigol but x3 price.
Hantek is only for hobbies and relaxing (if you like modding)
A Siglent 3x the price would be the SDS2000XP right now. 3X the price and 15X the scope. Bargain!+++
-
Definititely.
Let's say you want to capture something on a 10us low pulse, you set the trigger and wait for it.
Once you got it, realize you can't zoom before the trigger (Worked previously from 1-2021 update) so you lose 50% of your capture and you can't see what happened before the pulse.
The decoders draw garbage most of the time, unless you zoom in so much you can only see 2-5bytes, depends on the decoder.
SPI decoder won't work at >15MHz or so, showing wrong data.
The scope is still freezing on long runs, ex. leaving it waiting for a trigger condition, come 15 minutes later and see it freezed, maybe it captured your precious wave but you can't save it!
All messages, emails, forum posts to Hantek have been ignored.
-
RTC DS3231 arrived today, installed it right away, everything worked, thanks DavidAlfa :-+
-
Yesterday evening my Siglent SDS 1104X-E finally arrived. 8)
It's already a difference between a bicycle and a Mercedes C63AMG. The range of features alone is enormous. Of course, it also costs correspondingly more. A lucky financial circumstance made it possible for me to buy the device as a Christmas present for myself.
Next month I will buy the AWG extension for the Siglent oscilloscope, then my wishes in this area will be fulfilled.
Now I can tinker with the Hantek as much as I like, because I no longer have to worry about destroying it.
I wish you all a Merry Christmas and lots of great presents! :-+
-
Cost 3x the Hantek crap, it's not so expensive for the beast it is!
Amazing:
(https://fastly.jwwb.nl/public/y/s/v/temp-vehueauhmxnzwujrdbsr/SDS1204X-E-4.png)
I might sell mine buy one of these!
-
Cost 3x the Hantek crap, it's not so expensive for the beast it is!
Amazing:
(https://fastly.jwwb.nl/public/y/s/v/temp-vehueauhmxnzwujrdbsr/SDS1204X-E-4.png)
I might sell mine buy one of these!
Careful now and brace yourself to be shocked at the package they provide. ;)
-
Careful now and brace yourself to be shocked at the package they provide. ;)
I can only agree. I am simply impressed by the device! ;D
I already have a linear dual laboratory power supply from Siglent. Now I have the same positive experience with the oscilloscope. I think I have now found the right manufacturer for my laboratory equipment. Price and performance are simply outstanding.
-
Many thanks for a tremendous resource David Alpha.
I have a question about the VID PID expected by the DSOflash utility, and I'm hoping you can help me.
I am new to this forum, and new to using a DSO2D15. I purchased it about 2 months ago, and managed to "freeze" it a couple of days ago :-(
I'm following the "rules" and doing a lot of reading and cross-checking before attempting any recovery or repair.
I suspect I'm going to need to go down the "Platform Tools system flashing" route, but before I do that I'd like to take as many safety precautions and backups as I can.
I've noticed that the DSOflash tool expects particular values for the VID and PID of my DSO2D15
ctx.hdl = libusb_open_device_with_vid_pid(NULL, 0x1f3a, 0xefe8);
But looking at device manager on my pc, the oscilloscope shows up with a different VID and PID. Do you know if that has happened to anyone else? And would it be safe to edit the src code and recompile DSOflash? (I'm not keen to do that - I would presumably have to find/install the appropriate toolchain - but if it's necessary I will work my way through it).
Any advice or suggestions you have the time to offer would be much appreciated (Equally, if you are busy elsewhere, I completely understand, there is already an enormous amount of effort gone into what you have already done).
-
First of all, ensure to read how the FEL mode works in the FAQ.
Different VID/PID suggests you didn't boot in that mode!
If stuck at Hantek screen, Platform-tools is the only way, but if you're getting to the main screen, try the much easier SCPI method.
After recovering, consider installing the factory reset daemon, migh save your day next time it happens.
-
Wow David Alpha - many thanks indeed for such a rapid response.
I'm still reading like crazy. I saw how to boot into FEL mode, but I didn't realise the VID/PID might change as a consequence, and I'm wary of "doing anything" without double checking everything first, in case I make matters worse.
I've tried the Keysight I/O Libraries suite - it fires up fine on my pc, but fails to detect the DSO2D15, and I can't tell whether that is a pc / driver issue (I've tried both the default IV Foundation driver, and the Zadig installed WinUSB one), or the DSO being unresponsive at the other end of the USB cable. Which is why I suspect I'll end up with the Platform-tools way. The DSO does complete the boot process, but then freezes with all the on screen settings as they were when the problem first appeared.
I'll try the FEL boot mode and see what happens (I'll have to tell my anti-virus to unquarantine DSOflash.exe first, but I know how to do that). I'm a bit wary because sadly I hadn't done any backups before I had this problem - didn't even realise I could or should - newbie error! :-( and there seems to be a chance I'll lose the serial number etc (which you have provided a utility to restore :-) thanks!, and some calibration setting (which may not be recoverable, at least at my current state of knowledge)
When/if I get things working again, I'll be sure to back up everything in sight, and install the factory reset daemon!
-
Yeah. Better make a backup just in case!
-
...
I'm a bit wary because sadly I hadn't done any backups before I had this problem - didn't even realise I could or should - newbie error! :-( and there seems to be a chance I'll lose the serial number etc (which you have provided a utility to restore :-) thanks!, and some calibration setting (which may not be recoverable, at least at my current state of knowledge)
...
I also locked mine before doing any backup. Don't worry, you will lose the following:
1. Model - You can restore any model number you like (that is the reason many populated PCBs can be configured as higher priced models)
2. Serial Number - I didn't have any problem leaving the default "all zero" serial number
3. Signal Generator calibration data - DavidAlfa's gdrive folder has a script to generate new calibration data (may be less accurate than factory)
As a plus: you will get the latest software with less bugs that your original and hard to deadlock again.
-
Thanks to your help I am making progress :-) ... but I am once again stuck and would appreciate any hints.
I successfully booted into FEL mode, ran Zadig to install the WinUSB driver, and then ran DSOflash.exe, which worked perfectly (took about 48 minutes to create a "backup.bin" file)
Now I am attempting to Recover my oscilloscope, using the Platform-Tools system flashing approach (the SCPI approach doesn't work for me, the IO Lib Suite still will not detect a connection).
I am having problems installing the Fastboot driver. The install_driver.bat says it has installed the Fastboot driver, but has failed to install the WinUSB driver.
I tried running restore.bat (from the Firmware\Platform tools(Low level firmware folder) anyway, but it stalls at the "<waiting for any device step>".
The Windows 11 device manager shows the FEL driver to be installed, but NOT the Android Bootloader Interface - there isn't even an Android Device appearing. I've tried removing the WinUSB driver totally, and starting again with the install_driver.bat (switching the oscilloscope off and restarting in FEL mode between steps), but I'm still stuck at the same point.
Obviously I'm doing something wrong but I can't figure out what.
PS I've googled "How to install Fastboot driver", and can find lots about how to use it for Android phones, but nothing so far that gives me any hint about where I'm going wrong here.
-
It's fine, the fastboot device comes later, it's loaded in the first platform-tool step, just go with it.
-
THANK YOU - with your help and encouragement I now once again have an oscilloscope which boots ;D
There was a final twist to getting both the FEL and the Fastboot drivers installed and working on my Windows 11 pc, which I'll record below in case it helps anyone else. After several attempts to use the automatic installer approach, which failed later because the restore.bat script either couldn't find the Fastboot driver, or couldn't find the FEL driver (depending upon exactly what else I had done before starting restore.bat), I decided to try the Manual method.
The first time I tried to install PhoenixSuite_CN the installer said everything was OK, both the FEL and the Fastboot drivers were installed successfully. BUT I I noticed a message from Windows saying (something like) "a driver can't load on this device".
It turns out that there is a Windows security setting which for some reason did not like the Fastboot driver, and was (almost silently) disabling it as soon as it was installed |O
[windows/a-driver-can-t-load-on-this-device](https://support.microsoft.com/en-us/windows/a-driver-can-t-load-on-this-device-8eea34e5-ff4b-16ec-870d-61a4a43b3dd5)
[Core isolation - Microsoft Support](https://support.microsoft.com/en-gb/windows/core-isolation-e30ed737-17d8-42f3-a2a9-87521df09b78)
I had to turn the Memory Integrity setting off - it can be found in the Core Isolation part of the Windows Security setting.
Once this was done, everything was relatively straightforward.
- I installed PhoenixSuite_CN - this said it had successfully loaded both drivers - but actually the FEL driver wasn't quite happy so
- Next I used Zadig to list available devices, select the FEL driver and replace it with the WinUSB driver
- Then I restarted the DSO2D15 in FEL mode again, and ran restore.bat. I selected FW3205 and ...
about a minute later, my oscilloscope was booting normally :)
Now it's time for me to back everything up, and install the restore daemon.
-
Now calibrate the channels, then set the gen to something like 2Vpp and check the actual output.
If matching the amplitude, your scope had calibration in the EEPROM, you only need to restore the system parameters like modelo, SN, though it's not really needed.
If you send me your flash backup I'll try to make an installable from it.
-
Hi DavidAlfa,
That's very generous of you. I've just uploaded a zipped folder to your Google Drive, you should be able to deduce which one it is by the name I gave it ;)
I'm still learning lots - is an installable the same as a upk file? (By the way, a curiosity question - is there an easy way of exploring what is inside a upk file. I don't really need to know, but the fun for me is in the learning along the way, as well as arriving at the destination with a working project).
I think I have been lucky, and the calibration is intact - at least a 600mV sine wave from the generator appears to have a peak to peak voltage of 604mV. The delay in responding to your kind offer was because I hadn't used the waveform generator yet, so I had a bit of reading and practicing to do first.
Once again, many thanks and best regards
Geoff from Oz
-
Geoff, your repaired backup is ready, download it from the same place :-+.
-
I updated dsoflash tool, making a lot of optimizations.
Now both read and write operations take ~24minutes @ 95KB/s (2x faster read), probably as fast as the FEL protocol is capable of.
Binaries and source code updated! :-+
-
Came home, powered it on.... |O
-
Geoff, your repaired backup is ready, download it from the same place :-+.
DavidAlfa, the calibration coefficients A = 0.832178 and B = 5.167167 in the binary ee.bin in the dso3kb_CNXXXXXXXXXXXXX_EE.upk and in the dso3kb_CNXXXXXXXXXXXXX_EE.tar.bz2 are wrong. They dont't match the hex values in the dds_calbration.dat in the dso3kb_CNXXXXXXXXXXXXX_Calibration.upk and in the dso3kb_CNXXXXXXXXXXXXX_Calibration.tar.bz2. The correct calibration coefficients that should be in the ee.bin are: A = 0.840267, B = 9.324291. See please the attached photos. This doesn't matter for Geoff since he probably has the correct calibration coefficients in the EEPROM.
-
Ah, yeah, that's a backup from my own EEPROM!
Since I flashed my scope with that, fixed the boot issue and made a backup afterwards, missed the fact the EEPROM was still my own.
Edit: Fixed!
-
Thanks Visitorik,
Much appreciate your extra checking (not to mention all the help DavidAlfa has given me). Glad the calibration settings problem doesn't seem to affect me :-)
-
Hi DavidAlfa,
I've downloaded the repaired package from your Google Drive, and stored it away safely, in case I ever need it. One again, thank you :-+
I'm presuming that the calibration coefficients problem spotted by Visitorik won't be a problem, since it seems that my scope has them already stored in my EEPROM.
Is there any other difference that I should look out for in the repaired backup, or can I just use the backup safely if/whenever I need to?
Cheers
Geoff from Oz
PS Now I have a working scope again, I've been trying to get the Keysight SCPI connection to work (I'm not knowledgeable enough yet to really need it, but it seems like a useful thing to know how to do). Not having much luck yet though, the IO Connection Expert doesn't detect the scope. I think it's something on my pc though; the driver for the "USB Test and Measurement Device (IVI)" isn't completely happy, it says it needs further installation (whatever that means). I will first do a bit of google research, then try removing the devices and starting again. (or possibly, just park the idea for now, I'm keen to get back to the project I was using the scope to explore when the "frozen" problem happened.)
-
I'm presuming that the calibration coefficients problem spotted by Visitorik won't be a problem, since it seems that my scope has them already stored in my EEPROM.
Hi Geoff,
you could easily check whether your EEPROM contains the factory calibration coefficients. Run the dso3kb_PT24C02_damp.upk like update from the USB drive. It creates a PT24C02_damp.bin file on this drive. Look at this file in any hex-editor. If you find at the end of this file a string 0.8402679.324291, then your EEPROM has the factory calibration coefficients that correspond to their hex values in the calibration file /cache/dds_calbration.dat.
PS Now I have a working scope again, I've been trying to get the Keysight SCPI connection to work (I'm not knowledgeable enough yet to really need it, but it seems like a useful thing to know how to do).
It is known that Keysight SCPI is not compatible with Windows 11.
-
I've downloaded the repaired package from your Google Drive, and stored it away safely, in case I ever need it. One again, thank you :-+
Please re-download it, I added your original EEPROM. That would be all. :-+
-
All looking good, MANY thanks yet again :-+
you could easily check whether your EEPROM contains the factory calibration coefficients.
Done :-) My EEPROM does have the factory calibration coefficients that correspond to their hex values in the calibration file /cache/dds_calbration.dat.
It is known that Keysight SCPI is not compatible with Windows 11.
Duh! You have saved me from much |O THANKS
Please re-download it, I added your original EEPROM. That would be all.
Done :-) Downloaded and stored away safely.
-
Hi!
I have a DSO2D15. After a couple of minutes of use it started to show the following symptoms.
https://drive.google.com/file/d/1ByR_9ueos3tpGteahgUM_qE_qPZ1a33M/view?usp=share_link
I waited the recommended 30 minutes of warmup and then tried to do calibration, but it escaped with error message (at the beginnig of the process).
I did full restore with platform tools. The problem still exists.
I have no idea whether it is a hardware or software problem.
Can anyone help me, what are the steps of the calibration process? It could take me closer to the truth :)
Thanks,
Laszlo
-
Perhabs wrong fpga firmware.
Try installing 3102, calibrate again, if getting error then try 3202 or 3205.
If still failing, it might be a hardware issue.
-
Thank you David!
Unfortunately, it seems to be a hardware error.
I tried three different FW versions you suggested. No positive result.
I'm afraid I have to continue exchanging mails with the factory...
So far they have only had ineffective suggestions...
Thank you very much again.
-
Need help!
Can't get my new 2D10 working with DSO software under Win11.
Windows Device Manager shows properly installed USB device driver but Keysight Connection Expert 2022 still doesn't recognize the scope :-//
-
Can't get my new 2D10 working with DSO software under Win11.
The DSO software is not compatible with Win11. Try Win10. See some posts above.
-
Try compatibility mode ???
-
So with regards to the noise that is picked up by the scope.
Its not too bad (with proper ground) but it is certainly noticeable when looking at small signals or compared to other devices.
Is there a remedy for this? I have see lots of ideas in this thread but it seems there is no definitive solution
I seem to have the older power supply design.
Thanks.
-
So with regards to the noise that is picked up by the scope.
Is there a remedy for this? I have see lots of ideas in this thread but it seems there is no definitive solution
I seem to have the older power supply design.
Thanks.
The noise is about 250uV with no probes attached.
You could use probe with ground spring to minimize RF-noise pickup.
Unfortunately Hantek probes come without ground spring but you can easily do it yourself.
-
Thanks, I will try some old TEK ones and see if that improves.
Any other improvements that could be made to the Power supply?
-
There is not much that can be done to improve the power supply as far as interference is concerned. I bought a decent oscilloscope (Siglent SDS 1104X-E, hacked to 1204X-E) for home use. I took my Hantek device with me to our hobby car workshop. For measurements on a car, the device is absolutely sufficient, as it is very rarely a matter of such small signals that the interferences could become a problem. Here, an expensive oscilloscope would also be much too bad, because you can certainly imagine how the device will look after some use.
-
Mine was "bricked / boot looped". Upping the points to 400K+ regularly crashed it but a few days ago it finally boot looped so bad i couldn't change any setting or hit stop before the scope would lock up.
Reboot.
Repeat.
I had to recover with FEL using the CLI tools from this post.
My OG backup is safe. When i restore it carries over the higher memory depth and same boot loop. But the calibration should be good?
The AFG is pretty much unusable now. Im still working on extracting the calibration from my backup, but i got side tracked once it stopped crashing...
FYI
I updated the fpga fw which fixed my HORRIBLE crashing issue. The scope is actually useable now. I can use 8m on both channels and the scope hasnt crashed since.
I tried the basic software update and applied the 150mhz hack a few months ago with a usb stick in the front port but it didnt do much for the crashing issue and noisy signal.
This scope really seemed like a broken design. Pretty discouraging when the Hantek update didnt fix the freezing or anything else, but DONT give up. This is a great hobbyist scope once it stops crashing. Update the fpga fw then crank up the points and enjoy.
-
@Geoff
On Win11 for the keysight connection software, i had a bug for my 34410a meter with them, i was suggested a rhode shwartz visa driver package
Worked fine, when starting R&S you have to select wich driver you want to use, and keysight will work with it in my case ...
my 2 cents
RS_VISA_Setup_Win_5_12_8.exe
https://www.rohde-schwarz.com/ca/driver-pages/remote-control/3-visa-and-tools_231388.html (https://www.rohde-schwarz.com/ca/driver-pages/remote-control/3-visa-and-tools_231388.html)
-
Is it really a bootloop or it just freezes at Hantek screen?
PM your backup, I'll try to retrieve your cal data.
Actually will burn it to my scope and get them from the serial port.
-
Is it really a bootloop or it just freezes at Hantek screen?
PM your backup, I'll try to retrieve your cal data.
Actually will burn it to my scope and get them from the serial port.
Im not sure the correct term. It boots like normal but instantly locks up after initialization. If you reboot and press default or channel off it still instantly locks up.
Soft bricked?
Ill send you the backup rn.
-
It boots like normal but instantly locks up after initialization.
Yeah, corrupted settings crashing the system on booting. Happens from time to time, Hantek didn't provide any simple safe booting method to overcome this.
PM sent with restore files.
Consider installing the Factory Reset Daemon mod (https://www.eevblog.com/forum/testgear/new-hantek-dso2x1x-models/msg4491475/#msg4491475) to avoid this in the future.
-
AFG is back to normal and im going to make a new backup with the patches. :-+ Thanks again!
-
Hi. Newbie here :)
I've seen this question asked several times, but never saw an answer.
If you update a C10 or D10 to a D15 using dso3kb_2D15_conversion.upk
has anyone confirmed that the bandwidth does actually change to 150mhz ?
Are there any revisions where that doesn't happen?
Thanks.
-
If you update a C10 or D10 to a D15 using dso3kb_2D15_conversion.upk
has anyone confirmed that the bandwidth does actually change to 150mhz ?
Damn good question.
Keen to see any replies (especially with screen shots) :popcorn:
-
If you update a C10 or D10 to a D15 using dso3kb_2D15_conversion.upk
has anyone confirmed that the bandwidth does actually change to 150mhz ?
Are there any revisions where that doesn't happen?
Thanks.
I can only see a few ways to manage the BW difference between these models:
1. Through the bill of materials - kind of stupid considering they currently only appear to produce a single PCB/BOM to cover both the C/D variants. In this case we're SOL with the SW hack.
2. Switchable hardware in the analog path - looking at the reverse engineered schematics, there's no indication this HW exists. If they've done it this way the SW hack should give you full BW.
3. Implement it using signal processing to give the impression the analog bandwidth is less than it actually is - possible but requires extra code and is probably more effort than they're prepared to put in. If they've done it this way the SW hack should give you full BW.
4. The 20x10 and 20x15 models have the exact same BW spec and they simply package a 100MHz probe with the 20x10 scopes and a 150MHz probe with the 20x15 scope - hmm, cheap, easy and quite frankly the sort of approach I'd expect Hantek to take!
My money is going on option 4. Just go buy yourself a couple of 150MHz probes to replace the 100MHz one that comes with the C10 or D10
-
good day. Who will be able to remove the KEY_SCAN_DATA, KEY_SCAN_RESET, KEY_SCAN_CLOCK lines on the lane with an oscilloscope with and without a front panel connected?
-
Why?
-
Keyboard no work
-
Check if all connector pins are ok between boards.
How did the oroblem appear? Suddenly? Sometimes it's a software lockup, It needs hard resetting or firmware flashing.
I only have this scope, so I can't capture these signals.
-
after replacement FPGA from donor..
The buttons work on the star FPGA, but there are no measurements.
I will order a new GW2AR-LV18LQ144
What's the difference between GW2A-LV18LQ144C8/I7 and
GW2AR-LV18LQ144, and which one should I order?
What is the difference between LQ144 and EQ144 cases? are they interchangeable or not?
Who changed FPGA to GOWIN?
-
Are these seriously the things you need to go through to own this scope? :scared:
-
why not?
-
why not?
Ahh, use?
My two Siglents, my Tek 465 and a Hantek BE6074 (PC scope) all just work. I thought that's how it's supposed to be. :-//
I guess if your goal is to struggle to out do bad engineers, then you are in heaven. However, I buy T&M equipment to do tests and measurements. I realize I might be in the minority in this thread. Carry on..
-
I have other oscilloscopes both analog and digital and not one. With this just an interest of repair
-
You can also check the signal levels after switching on FPGA_READY, FPGA_DONE,FPGA_RECONFIG?
-
Attach boot log
Can update via rs232?
Or how you can check the operation of the FPGA or buttons?
-
You have a sample log here:
https://www.eevblog.com/forum/testgear/hacking-the-dso2x1x/msg3580941/#msg3580941 (https://www.eevblog.com/forum/testgear/hacking-the-dso2x1x/msg3580941/#msg3580941)
Update what? The firmware? The standard way of updating is using Platform-tools.
Flash the oldest platform-tools version, the keypad kernel module (/dso/etc/fpga_i2c_kb.ko) is a lot more verbose and shows the activity of any key/knob on the terminal.
If working, you'll see a lot of messages when handling the keypad:
[ 19.680459] Get irq key
[ 19.696630] dso keyboard: key (code 0x12) pressed.,17
[ 19.830445] Get irq key
[ 19.846219] dso keyboard: key (code 0x12) released.,17
[ 21.380455] Get irq key
[ 21.396163] dso keyboard: key (code 0xe) pressed.,13
[ 21.505450] Get irq key
[ 21.520995] dso keyboard: key (code 0xe) released.,13
[ 22.180451] Get irq key
[ 22.196021] dso keyboard: key (code 0x3) pressed.,2
[ 22.280469] Get irq key
[ 22.297215] dso keyboard: key (code 0x3) released.,2
[ 22.380463] Get irq key
[ 22.396282] dso keyboard: key (code 0x3) pressed.,2
[ 22.480476] Get irq key
[ 22.496142] dso keyboard: key (code 0x3) released.,2
-
Where can I download the oldest platform-tools version?
-
Read the FAQ in my signature.
I currently made any all-in-one package with all versions.
-
https://drive.google.com/drive/mobile/folders/1-J-Dz7aB6hV3MmuJj-t_35cBSadiGHVF
-
Flash Platform-tools version 2020.12.21 fpga_3000
there is no response to the buttons.
The lines confuse me:
[ 12.653117] fpga_ctl_kbd_event:17, 3, 1, 4
[ 12.657289] fpga_ctl_kbd_event:17, 5, 1, 14
[ 12.661490] fpga_ctl_kbd_event:17, 7, 1, 54
How can I check the module /dso/etc/fpga_i2c_kb.ko) and verbose and shows the activity of any key/knob on the terminal?
Ordered gw2ar...
-
I just received my new DSO-2D15 today and it has a new version of software installed:
Version: 1.0.3.0.0
Date: 230327.00
Hardware: 003.002.001.000.000.000.000.001
Firmware: 3205
Just wondering if anyone knows what's been fixed/changed since 1.0.2.0.0
Thanks
-
Date: 230327.00
It's a newer software than available from Hantek.
Could you run Backup Builder and send me the dso3kb_CNxxx_FULL.upk / tar.bz2 file?
So I can make a new update package from it.
Any doubts read the FAQ (https://www.eevblog.com/forum/testgear/new-hantek-dso2x1x-models/msg3559217/#msg3559217) ;)
-
Thanks for sending the file, LarryR ;)
New update:
» 2023.03.27 (https://drive.google.com/file/d/16oMclbwruL-_ZH0Bx1wCLsNf47X_FqSc) Unofficial update, extracted from a device that came with it from factory.
Changelog (Like always) is completely unknown!
(Or, most likely, what are the new bugs, following Hantek's updates trend... ::))
Edit:
It seems the zoom is working again? (Able to move all the way back, instead limited to the trigger position)
-
I just viewed the ascii strings in the application code for the scope and found may references to 'anolis'
Does anyone know if Hantek used https://openanolis.cn/ (https://openanolis.cn/) to build the application(s) for the scope?
-
Its an Allwinner F1C200S running Sunxi Linux,
https://www.eevblog.com/forum/testgear/hacking-the-dso2x1x/ (https://www.eevblog.com/forum/testgear/hacking-the-dso2x1x/) has much of the details so far.
Its likely that Hantek's software used Anolis Linux OS on another SoC .. Looking through the code, it has been ported to many differnt models of their scopes and there remains alot of scrap code.
-
AFAIK, libanolis is their library for graphics, I/O, etc .
-
I'm about to order new encoders.
After thinking it twice, I'll avoid the mechanical steps in the small encoders, adjusting certain values require a lot of turning, dealing with a ton of clicking will make the experience even worse!
So the idea is keep it just like it is now, but with more steps per turn to make it less painful, and decent quality parts.
The PEC12R-4220 (7mm shaft) series are a direct replacement (As we already know, thanks to pu6k1n and vistorik :)).
If not being able to source them, the PEC12R-4225 (12mm shaft) will almost fit, the small caps have a depth of 12mm while the large ones have 11.2mm, it would only require trimming a bit off the shaft end.
- Pushbutton + stepped rotation (Sec/div knob): PEC12R-4220F-S0024 / PEC12R-4225F-S0024
- Pushbutton + smooth rotation (Small knobs): PEC12R-4020F-S0024 / PEC12R-4025F-S0024
- No pushbutton + stepped rotation (V/div knobs): PEC12R-4220F-N0024 / PEC12R-4225F-N0024
Also the PEC12R-3x series will also work, it's the same P/N, just replace the 4xxx with 3xxx.
The difference lies in including a bushing.
The shaft offset is 2mm larger in the PEC12R-4222 and PEC12R-4230, so the knob sit 2mm away from the base, though still possible with additional modifications to the shaft.
The difference can be seen here:
(https://assets.lcsc.com/images/lcsc/900x900/20180914_BOURNS-PEC12R-4230F-S0024_C143818_back.jpg) (https://assets.lcsc.com/images/lcsc/900x900/20220425_BOURNS-PEC12R-4120F-S0012_C143801_back.jpg)
-
I am replace FPGA with GW2AR-LV18EQ144PC8...
After the replacement, the buttons became work, the calibration passes but the Auto mode does not work, + incorrect data in 1GSa / s and 500,
Has GW2AR-LV18EQ144PC8 been used correctly or should GW2AR-LV18EQ144 be used without P
or such GW2AR-LV18LQ144
-
I think the SDRAM will be too slow?
But I have no idea about the exact FPGA model..
-
I am replace FPGA with GW2AR-LV18EQ144PC8...
After the replacement, the buttons became work, the calibration passes but the Auto mode does not work, + incorrect data in 1GSa / s and 500,
Has GW2AR-LV18EQ144PC8 been used correctly or should GW2AR-LV18EQ144 be used without P
or such GW2AR-LV18LQ144
alias095, the best is to ask Hantek (Han Zhangqiang, Email: zhangqiang@hantek.com) to sell you a native FPGA LEMONTREE chip of the corresponding series (numbers under the name of the chip) with an explanation of the reason. Maybe they will sell it to you. They once sold me separately a new DSO2D10 motherboard.
-
Is it worth buying DSO2D10 in 2023 or should I be looking forward for some other 2 channel model under 300 bucks? 4 channel is preferable if I could find one below 300 USD. By the way there are many oscilloscopes with 2Gpts memory depth today but I have no idea when they'll be under 400 USD.
-
Is it worth buying DSO2D10 in 2023 or should I be looking forward for some other 2 channel model under 300 bucks? 4 channel is preferable if I could find one below 300 USD. By the way there are many oscilloscopes with 2Gpts memory depth today but I have no idea when they'll be under 400 USD.
The Siglent SDS1102CML+ runs about $320. It may have slightly fewer "features", but it actually works and is properly supported by a reputable company. Probably easily "upgraded" to 150MHz too.
I wouldn't bother with Hantek bench scopes. They are just junk.
-
Is it worth buying DSO2D10 in 2023 or should I be looking forward for some other 2 channel model under 300 bucks? 4 channel is preferable if I could find one below 300 USD. By the way there are many oscilloscopes with 2Gpts memory depth today but I have no idea when they'll be under 400 USD.
I purchased and subsequently hacked a 2C10 -> 2D15 just over a year ago. It's has many shortcomings but if you don't get too hung up on it's flaws and focus on what it can do, it still offers some decent functionality for the ~$200 you'll pay for it. Now, if you expect it to meet all it's published specs you're going to be disappointed. Unless you can score something 2nd hand, I don't believe you're going to get anything better below $300.
-
So the idea is keep it just like it is now, but with more steps per turn to make it less painful, and decent quality parts.
I wonder if the software can keep up with more steps per turn or is it just going to start skipping steps?
-
I purchased and subsequently hacked a 2C10 -> 2D15 just over a year ago. It's has many shortcomings but if you don't get too hung up on it's flaws and focus on what it can do, it still offers some decent functionality for the ~$200 you'll pay for it.
Prices are low at the moment.
You can get the DSO2D15 (150MHz + AWG) for under $200 shipped.
https://www.aliexpress.us/item/3256803584138756.html (https://www.aliexpress.us/item/3256803584138756.html)
But i can still resist! ;)
-
I'm with Dirtmover. I also don't use all the features but have fixed many a radio with it now.
-
I finally ordered the new encoders. They had become completely unusable.
Look at the waveforms V0 makes when turning faster than 1/2 rotation a second!
Pure noise, missing pulses... the contacts are clearly floating.
So add +$25 to the scope during the first year.
Plus another vertical line appeared in the display so soon another $30.
-
The leg said no more, it broke a year ago and got it more or less fixed by melting it.
But the plastic had the strength of old pizza, broke in no time.
Made a 3d print, nothing fancy, the idea is to insert screws from the inside of the scope into the part.
I doubt I will be the only one with this problem so I'm attaching the STL.
Will be updating the design as needed.
-
Very cool David!
-
The leg said no more, it broke a year ago and got it more or less fixed by melting it.
But the plastic had the strength of old pizza, broke in no time.
Made a 3d print, nothing fancy, the idea is to insert screws from the inside of the scope into the part.
I doubt I will be the only one with this problem so I'm attaching the STL.
Will be updating the design as needed.
FYI, see the sticky atop the TE board ?
https://www.eevblog.com/forum/testgear/replacement-knobs-feet-and-fittings-for-test-equipment/ (https://www.eevblog.com/forum/testgear/replacement-knobs-feet-and-fittings-for-test-equipment/)
Suggest you make a post there. ;)
-
I'll do when it's fully assembled and tested working! :-+
New encoders didnt arrive yet, but just for curiosity, I tried tearing V0 apart, bending the contacts so they make more force and assemblying back.
Instant improvement! But I guess it won't last long.
On close inspection they look identical to the genuine Bourns shown online... might they be original after all?
I really hope their products aren't such crap, started failing after only a few months.
Edit: I decided to also get rid of the LCD, bought a new AT070TN94 at Ali.
-
Hi everyone.
I had the misfortune to acquire DSO2c10.
Recently, I detected an error when switching horizontal resolution from 50ms to 100ms at a memory depth of 400k or more.
The oscilloscope does not display the signal correctly.
I wrote about this in Hantek, but there is no answer.
https://www.eediscuss.com/forum.php?mod=viewthread&tid=17937&extra=page%3D1 (https://www.eediscuss.com/forum.php?mod=viewthread&tid=17937&extra=page%3D1)
Maybe this is only an error in my oscilloscope, I ask you to check this mode on your oscilloscope.
Thank you in advance.
P.S. I apologize for my English, I use a translator.
-
Indeed, there's a new firmware 2023.03.27 (http://www.hantek.com/uploadpic/hantek/files/20230728/dso3kb_20230327.zip), though they uploaded it 2 months later! (2023.07.28) :palm:
We already had it, they've been shipping new devices with the updated firmware all this time, so we extracted it from a working device.
Anyways thanks for telling!
Yeah the trigger doesn't work at very low speeds.
About the signal levels, have you calibrated the scope and later pressed "Default setup" ?
Show some pictures! If the signal is very noisy, with random spikes, try updating the FPGA to FW3205.
The statistics issue has been there since day one, it's a shame.
Check the FAQ in my signature!
-
About the signal levels, have you calibrated the scope and later pressed "Default setup" ?
Show some pictures! If the signal is very noisy, with random spikes, try updating the FPGA to FW3205.
The problem is not due to noise, the signal is clean.
The largest error when switching from 50ms to 100ms at a memory depth of 400k or more.
To check, you need to give a signal with a frequency of about 3 hz, set the trigger to normal,memory depth of 400k or more, and scan 50ms per division.
In this case, the oscilloscope shows the correct signal.
If you switch to 100ms per division, the oscilloscope will show a very stretched signal.
If you press the "single" button in this mode, the oscilloscope will show a normal signal after capturing.
Please check this on your oscilloscope.
On the Hantek website, I described everything in detail.
My oscilloscope is calibrated.
The error occurs at a horizontal resolution of 100ms or more.
Thanks.
-
Activated the generator using your program,DavidAlfa, for which thank you very much.
I continue to investigate the oscilloscope.
Found that the oscilloscope in Roll mode moves the image in jerks.
This is a consequence of poor program optimization.
Linux is not a real-time operating system.
I think that Hantek engineers devoted very little time to synchronizing processes and threads, which led to such consequences.
It is a pity that there is no source code.
This can all be fixed.
-
Yes, it'll be worse as you use it and discover more "features". We've been like this for more than 2 years.
Nothing to do, Hantek laughts at their customers.
It seems like the bottleneck is in the communication with FPGA, it uses 10MHz SPI to transfer the data to the CPU, that's a pretty small bandwidth (1.25MB/s).
Edit: Inspected it in Ghidra again, it seems it does at 50MHz.
Edit2: But it seems the Linux devicetree will limit this to 1MHz!
I made some tests here (https://www.eevblog.com/forum/testgear/hacking-the-dso2x1x/msg4988539/#msg4988539), feel free to try.
-
Hi there, I'm new on this forum and overwhelmed by the amount of information shared.
I have the Hantek DSO standing around on my desk for quite a while now. It still has the factory firmware installed. After digging through all of the information on this thread as well as on the hacking thread, I'm still a bit confused regarding the backup steps necessary before tinkering around with firmware updates.
Can anyone please explain to me the difference between Flash-, EEPROM- and Backup-Builder? What contents are saved on each backup? I assume it is not sufficient to read the ROM with a CH341A and a clip - correct?
I don't mean to bother you with my request. It is just that I'd like to better understand what and what for I'm doing each backup.
Thanks in advance!
-
Did you read the FAQ?
Backup builder does a copy of the important data like model, sn, generator calibration, current software, FPGA firmware and also the eeprom.
Backup builder files are enough recover but it's always good to make a 1:1 backup with dsoflash just in case.
-
Did you read the FAQ?
Backup builder does a copy of the important data like model, sn, generator calibration, current software, FPGA firmware and larz eeprom.
Backup builder files are enough recover but it's always good to .ake a 1:1 backup with dsoflash just in case.
Hi David,
Thanks for your fast reply. Yes, I went through your extensive FAQ section - Thank you for your work! But still it was confusing what backup does what.
So now I understood that Backup Builder already saves a lot of data:
- Generator Calibration Data
- Model and SN
- Software and FPGA-Firmware
- EEPROM
As you stated, that should be enough to recover. What more/else does dsoflash do? And do I understand it correct that no seperate EEPROM backup is necessary after running backup builder?
I think most of the confusion I'm running into is the lack of knowledge about what types of storage are present and what is stored on each storage.
-
What more/else does dsoflash do? And do I understand it correct that no seperate EEPROM backup is necessary after running backup builder?
David's dsoflash creates a complete memory dump, including the spare area of 64 bytes for every page of 2048 bytes in one binary file of 132Mb, like the programmer CH341a with an option to read the spare area does.
If you run David's backup builder you don't need to run seperate EEPROM backup.
-
The eeprom is a small memory storing some calibration values, normally nothing writes to it, it's used by the scope after a factory flash to restore the generator calibration.
But not all scopes had it, early ones like mine came blank, with the calibration only stored in the system flash.
Hantek would tell everyone to flash the scope, but that would wipe the calibration, system info...
If your version had a the calibration data in the eeprom, nice, but if not, they simply wouldn't care.
So run DSOflash and BackupBuilder. There're no other tools, it's all it needs to be safe under all circumstances.
If the scope hangs or crashes, then restore with latest Platform-tools, afterwards apply your "not-FULL" backup, will restore the important bits and it'll be ready.
DSOFlash and EE backup should never require restoring, they're there just in case.
This is properly described in teh FAQ, please read it :)
About the new encoders:
Handling cursors/levels improved by much, its's very noticeable that the new encoders have twice the pulses per rotation.
A pair of quick turns and you're already at the other side!
...
Except in trigger-> pulse mode.
The pulse width adjustment works nicely all the way from 8ns to 10ms, up and down.
But from 10ms up, it randomly goes up/down when rotating too fast, so it barely moves.
I haven't found any other settign using V0 having this behaviour, so I'm wondering if this is a firmware bug or what?
It's clearly seen here:
(https://s11.gifyu.com/images/ScuY8.gif)
-
Leg fix. Drilled the 3d print, melted a M3 insert in and used a large washer to spread the tension evenly.
(Yeah the printer needs some retraction tweaking, this is petg not pla).
Seems pretty solid!
-
Hi, I have the DSO2D15 and some button aren't working properly, for instance the single button can trigger all of these other buttons :
[attachimg=1]
I updated the firmware but it didn't help, I'm gonna contact the seller I bought it from... In case they don't want to fix or replace my scope, do you guys have any idea how to fix it ? I never opened it before but this type of issue looks like a bad ribbon somewhere ?
Thanks for your help
-
The buttons are all sampled using three wires (Scan reset, Scan data, Scan clock), it might be a bad ribbon onnection or a solder defect, luckly for you the button board is very simple, there're only 3 ics and few resistors.
I don't think it's the ribbon, otherwise you would get nothing or random input, not exactly the same buttons everytime.
Thanks to @Pcprogrammer (He fully reverse enginneered everything) we have schematics:
https://github.com/pecostm32/Hantek_DSO2000/blob/main/Schematics/User_Interface/BUTTONS.png
Looks like only one column is working? (See attached picture).
Thus, I'd start by checking U2 and its connections, specially pins A,B,C (9,10,11).
Then check U1 (Ripple counter) and ensure all its outputs are toggling on/off at several KHz.
I recall seeing a 600kHz signal in key master clock.
-
hi, there!...
i want to add a fan to my hantek oscilloscope dso2d10, so please, if any one know the size of fan that fit, please let me know...
i want to buy one whitout teardown it...;-)
many thanks and electronics greeting from spain
-
Not required and possibly another source of electrical noise for an already wonky design, I wouldn't do it, but you only need to remove the 4 screws holding the back to check the dimensions, no need to put it to pieces.
Or use the search button!
https://www.eevblog.com/forum/testgear/new-hantek-dso2x1x-models/msg3896411/?topicseen#msg3896411 (https://www.eevblog.com/forum/testgear/new-hantek-dso2x1x-models/msg3896411/?topicseen#msg3896411)
-
Thanks for your answer, so I dismantled it a bit but it doesn't look that bad, I mean traces of flux shouldn't be an issue for a button... I'll clean that and reflow Ux IC, otherwise I don't have tools to measure the 600kHz signal... could I use the scope itself, half dismantled to check it ?
Thanks again
edit : so I reflowed all the IC, it seems a bit better but I still have the issue sometime...
https://www.youtube.com/watch?v=igmsvEQ4cOA (https://www.youtube.com/watch?v=igmsvEQ4cOA)
-
i make a test with my hantek awg of the dso, and a wandel&golterman spm15, and my hantek 6,5 digit multimeter, at 1khz, 0dbm, and the results are perfect...;-)
-
thanks so much,
i find that the fan is 50*50 mm, so i can buy it without teardown my dso!...
so many thanks and electronics greetings from spain
-
Following this (https://www.eevblog.com/forum/testgear/new-hantek-dso2x1x-models/msg4985563/#msg4985563), the new display arrived, fits exactly like the original and the image quality is just as good.
Leaving the AT070TN94 link for everyone:
https://www.aliexpress.com/item/32918916584.html (https://www.aliexpress.com/item/32918916584.html)
(It's the 5mm model)
-
Leaving the AT070TN94 link for everyone:
https://www.aliexpress.com/item/32918916584.html (https://www.aliexpress.com/item/32918916584.html)
Page Not Found :(
-
Link worked for me.
- George
-
Why did you have to change the LCD?
-
You can see in the second picture on this post https://www.eevblog.com/forum/testgear/new-hantek-dso2x1x-models/msg4985563/#msg4985563 (https://www.eevblog.com/forum/testgear/new-hantek-dso2x1x-models/msg4985563/#msg4985563) that he had dead pixels on his original display.
-
Yep, the scope freezed, toggled the power off/on and one line appeared!
Few days later I got another :horse:
-
Hello, long time no see you guys ;D
I've "upgraded" my scope to Rigol Ds1102z-e and I found the analog feeling again. Much faster, more realtime feeling, more reality more sensitivity especially for audio analog calibration such as tape decks. No longer laggy.
The output waveform from these machines is not steady like function generator so DPO (Siglent) or Ultra Vision technology of Rigol is much more suitable.
I've got mine $180 for mint unit, look like brand new with all catalogue and calibration certification.
Quite happy purchasing.
:-+
-
I recently purchased DSO2D10 oscilloscope and it worked fine for a couple of days.
Today it began to lock up after boot and none of the buttons work.... Note that the button LEDs are all lit and no channel signal is displayed either.
I spent hours searching this forum but all of the "locks/freezes" I found were easily resolved by turning the scope OFF/ON which in my case does not help.
I have already contacted Hantek but given their record, I'm not expecting much.
I'd appreciate any help in debugging this.
Here are some pictures and a video of the problem: https://mega.nz/folder/peQBVASI#DWsjU1AMZSFBskD4B_fbeA (https://mega.nz/folder/peQBVASI#DWsjU1AMZSFBskD4B_fbeA)
-
I recently purchased DSO2D10 oscilloscope and it worked fine for a couple of days.
Today it began to lock up after boot and none of the buttons work....
:palm:
I hope you didn't see this thread before you made your purchase .. or see any of the negative reviews on the internet.
I honestly can't understand why anyone would buy one of these when Siglent and Rigol (and other manufacturers) with great reputations build fantastically better instruments for about the price of a Big MAc dinner and a 6-pack more.
Sorry this happened to you and I hope you discourage any you know of thinking to buy one.
All that said, you are in the right place to get help but you will need to do A LOT of work.
Good luck.
-
The trace of Ultra Vision technology is much difference from Hantek or others normal DSO.
If you need real digital scope but affordable so any Rigol (must have UltraVision) is my recommendation.
-
Today it began to lock up after boot and none of the buttons work
Check the FAQ in my signature, "Recovering" section.
First try to make a Factory reset without flashing platform-tools, so you don't lose the calibration data.
-
Thank you for the replies.
I found a windows box to try DavidAlfa's suggestion and here's how it went.
First I attempted a preliminary backup just to be safe. Put the scope in FEL mode, installed PhoenixSUite and zadig, confirmed that the USB device showed up properly in the device manager and ran "read.bat" from DSOFlash, but that failed. (1st image)
I then installed the Keysight IO Lib package and restarted the scope in normal mode. The software recognized the scope and I sent it the PRIVate:FACTORY:RESET command. The command "worked" in the sense that the scope immediately rebooted and the signal stats I had configured earlier, before the lock up, disappeared. Unfortunately the buttons are still all lit up and none of them work. And there's still no channel signal being drawn. (images 2 and 3).
I remember that when the scope was working, right after booting there would be some clicking noises (relay? for the AWG?) and then if memory serves me right the WAVE GEN and other lights would go OFF. Now there's no clicking and the lights stay ON. Maybe there's something wrong with the hardware?
edit: I should also add that before the factory reset the stats "count" would continuously increment as can be seen in the video in my post above, indicating that the phoenix process is probably running fine. this would be consistent with a the hardware error hypothesis where a relay that was supposed to switch never did, leaving all the lights ON and the phoenix process "waiting" for a signal that never arrives.
-
It's strange, should be working.
Are you properly setting the scope in FEL mode by pushing the button at the bottom? Nothing should appear in the screen.
This is the device you should install WinUSB driver to, using Zadig.
Then, you must start DSOflash only when the scope is already in FEL mode and connected to the computer.
Give it some more tries.
Maybe the flash is corrupted. The only priority now is to backup the generator calibration, everything else can be easily restored.
Might sound dumb, but had this happening several times, got some fixed by simply pressing Default Setup button, so try that!
-
I tried installing the zadig/winusb driver again and now DSO flash is reading! I think my previous error was that I installed zadig before phoenixsuite..
Anyways. in about 20 minutes I should have a backup of the flash.
Thanks DavidAlfa! Was DSOflash written by you? Is the source code available?
edit: d'oh, I see the source code up on your drive.
-
Yes, it's based in xfel (https://github.com/xboot/xfel).
So the buttons don't work at all?
-
nope, not even "default setup" :(
you can see the behavior in this 30s video: https://mega.nz/folder/peQBVASI#DWsjU1AMZSFBskD4B_fbeA/file/sb5U0TiT
-
Now you made a backup it's safe to do anything.
Download platform-tools and flash the latest version.
As always,
it's in the FAQ.
-
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:
$ md5sum platform-tools.zip
70280b90e88a60ff001bd984a0b3a0ae platform-tools.zip
-
Indeed, it was corrupted! Something went wrong when I updated it 2 weeks ago.
Should be working now.
md5 8086da8f46f5d6ae4dd18a254f4c0757
-
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.
-
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.
-
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
-
Yes, it's damn annoying!
-
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?
-
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 (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?
-
These prices do not make sense in my opinion.
The one with the best features is the cheapest?
I would be careful.
-
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
-
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.
-
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.
-
Haha next time just buy it, return later if not happy, it's amazon!
-
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
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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 (https://www.eediscuss.com) but don't expect action any time soon, if at all!
-
ty dirtmover. I notified them here https://www.eediscuss.com/forum.php?mod=viewthread&tid=17977 (https://www.eediscuss.com/forum.php?mod=viewthread&tid=17977) but nothing yet. Not holding my breath...
-
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
-
Having a backup, try platform-tools.
Or reseating the ribbon cable just in case, doesn't take much work.
-
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
-
You're right. Then there're few options left.
- Corrupted fpga FW file? I don't think so, the buttons wouldn't work either.
- Corrupted filesystem? Maybe... still, rare that only the buttons work.
(Both would be fixed with platform-tools)
- Defective chips? Still rare, maybe a bad soldering joint.
The encoders common wires are Scan_Data_4 & Scan_Data_6.
Maybe one of these are bad, or any of the diodes is shorted.
The Scan_Lines are also used for the buttons, so they would also fail if bad.
-
Just read your post, that came up while I was editing mine :'(
I had checked for continuity between diodes and U2, but I didn't check for shorts on the diodes. Will dismount it again and check.
EDIT: Done, all the diodes are OK. Also checked the connections between U2 and U1, also OK. Tried also some more cleaning and heating around U1 and U2 with hot air. No luck. Time for platform tools
EDIT2: Updated to SW 1.0.2.0.0 (221028.00) FW 3205 with Platform Tools (it was 1.0.1.1.0 (20210726.00) 3202). No luck. Must be a hardware failure (probably U2 or, maybe, U1). I will retouch all solders before trying anything else.
Any other ideas?
-
Is R109 OK? It's the only thing powering the keypad matrix.
-
Yes, I also checked R109. Although it is common with the rest of the keys, I suspected it could be also the problem because of the forward drop in the diodes (supposing there was a weaker pullup also in the FPGA). But no, it's OK.
Although I had already checked them with the multimeter, I also resoldered relevant pins of U2 (1, 2, 9, 10, 11) and U1 (3, 4, 5), but no luck.
If it's not a SW or FW problem, I can only suspect bad U2, more remotely, bad U1, or, even more strange, a failure in the FPGA section in charge of reading the keyboard.
If I had a longer ribbon cable, I could also try some "live" measurements in the user interface board, but I don't have it.
Unfortunately, without the encoders, the scope is practically useless, but maybe I can still use it with the Keysight application
-
Do you have access to the serial port? It would be interesting to see the kernel messages.
But you need flash the oldest platform-tools version, the keypad kmod (/dso/etc/fpga_i2c_kb.ko) debugging output was silenced in newer versions.
On rotation you should see a lot of messages like:
[ 22.793724] Get irq key
[ 22.818725] Get irq key
-
Yes, I have access to serial port. As I said before, I updated to the latest version SW 1.0.2.0.0 (221028.00) FW 3205 to see if that solved the problem but, seeing that it didn't, I went back to SW 1.0.1.1.0 (20210726.00) FW 3202, and the problem persists.
With the old SW&FW, I can't see any "irq" messages in the console. I'm attaching the console's output after a reboot and after pressing several keys and rotating knobs. Also checked that /dso/etc/fpga_i2c_kb.ko exists, but I don't know if I have to do something else to get the "irq" messages
EDIT:
I opened a ticket in Banggood; I don't expect anything as I bought it on 2022-03-20, more than a year ago, but you never know if you don't try.. I'm suggesting them to send me a replacement for the interface board, that should be cheap for them, and replace it by myself. Let's see what happens...
Also checked at https://www.eediscuss.com/forum.php (https://www.eediscuss.com/forum.php) that problems with knobs and keyboard are frequent
-
Nah, try the oldest build, I know it's FW3000, it won't damage anything.
The kernel module in FW3202 version is already silent.
Alternatively you can manually replace the module with the attached ones and rebooting afterwards to take effect:
cp /mnt/udisk/fpga_i2c_kb_verbose.ko /dso/etc/
# Or
cp /mnt/udisk/fpga_i2c_kb_silent.ko /dso/etc/
reboot
Any key/encoder activity is shown:
[ 123.838713] Get irq key <---------- Encoder rotation
[ 124.113703] Get irq key
[ 124.138710] Get irq key
[ 124.163720] Get irq key
[ 124.188729] Get irq key
[ 124.213696] Get irq key
[ 124.238704] Get irq key <---------- Button press
[ 125.617587] dso keyboard: key (code 0x1) pressed.,0
[ 125.738713] Get irq key <---------- Button Release
[ 125.742694] dso keyboard: key (code 0x1) released.,0
Code 0x1 is F0 button.
-
Nah, try the oldest build, I know it's FW3000, it won't damage anything
Done!
[ 136.417041] Get irq key
[ 136.433047] dso keyboard: key (code 0xe) released.,13
[ 149.642025] Get irq key
[ 149.658439] dso keyboard: key (code 0x7) pressed.,6
[ 149.842016] Get irq key
[ 149.858236] dso keyboard: key (code 0x7) released.,6
[ 156.892013] Get irq key
[ 156.908293] dso keyboard: key (code 0x3) pressed.,2
util_thread_pause:thread 0xa8fc70 is paused
[ 157.004948] fpga_ctl_kbd_event:17, 3, 0, 50
[ 157.009204] cnt =1,80,124
[ 157.022758] cnt =0,80,124
[ 157.026935] fpga_ctl_kbd_event:17, 5, 0, 40
[ 157.033041] fpga_ctl_kbd_event:17, 7, 0, 0
[ 157.042905] Get irq key
[fpga_dds__set_dds_light] 0
[ 157.058569] dso keyboard: key (code 0x3) released.,2
[ 157.082690] cnt =1,64,124
[ 157.102674] cnt =1,0,124
[ 157.122654] cnt =0,0,124
ia_self_test_on_key_up:65471
[ 159.617033] Get irq key
[ 159.632270] dso keyboard: key (code 0x12) pressed.,17
[ 159.767034] Get irq key
[ 159.782249] dso keyboard: key (code 0x12) released.,17
ia_self_test_on_key_up:75
[ 160.567032] Get irq key
[ 160.582264] dso keyboard: key (code 0xa) pressed.,9
[ 160.692035] Get irq key
[ 160.707332] dso keyboard: key (code 0xa) released.,9
[ 160.712348] dso keyboard: key (code 0xa) pressed.,9
[ 160.717354] dso keyboard: key (code 0xa) released.,9
ia_self_test_on_key_up:67
[ 162.567031] Get irq key
..............................................................................
[ 239.767014] Get irq key
[ 239.782266] dso keyboard: key (code 0x20) pressed.,31
[ 239.892018] Get irq key
[ 239.907317] dso keyboard: key (code 0x20) released.,31
ia_self_test_on_key_up:88
[ 249.142022] Get irq key
[ 249.167045] Get irq key
[ 249.192009] Get irq key
[ 249.217037] Get irq key
Apparently, the same results as you: it responds to encoder rotation, but they don't work doing what they're supposed to do!
I understand this discards any hardware failure, at least at the user interface PCB
Completely clueless now!
EDIT: sometimes I stop getting "Get irq key" on rotating the knobs. But no response on the screen even when the "Get irq key" appears
-
Rotate V0 knob while not in any menu, so the dso app doesn't show its stuff.
You should get plenty of irq messages in a single rotation.
Do you have any signal analyzer? Would be interesting to see what's going on at the encoder pins.
I'd replace the 4051s and the 4066, they're cheap so you won't lose anything trying.
-
Rotate V0 knob while not in any menu, so the dso app doesn't show its stuff.
You should get plenty of irq messages in a single rotation.
That's what I get, not only with V0, but with all the knobs, although sometimes there are some interruptions and lags.
Do you have any signal analyzer? Would be interesting to see what's going on at the encoder pins.
No, unfortunately, I don't (although planning to get one of those cheap USB login analyzers one of these days...). I should also need a longer ribbon cable to be able to access the user interface PCB with the rest of the scope connected.
I'd replace the 4051s and the 4066, they're cheap so you won't lose anything trying.
Yes, I think I'll try that, but considering the HW detects the knobs' movement, as stated by the IRQ messages, I don't have much confidence that it'd solve the problem, but it's worth a try.
Just a last crazy elucubration: when the rear USB is connected to the PC and Keysight's application is running, the front panel keys are locked... ¿Could it be something is blocking the response to the knobs, although nothing is connected? Would be very strange, as buttons should also lock, but almost all the sensible possibilities have come to an end
-
I forgot something: You get the IRQ on *any* change, even if the knob didn't made a full quadrature cycle.
It seems everything is processed in software, the fpga just sends raw data when something changes.
So imagine the encoder contacts "A" and "B"... Only "A" might be toggling, and "B" stuck high/low, nothing would happen but you will get the IRQ messages as well.
This is while rotating the Time/Div control.
At first I'm making full steps, but then I'm making half steps, backwards and forwards, so it never settles into the next step.
Still, you get plenty of IRQs.
[ 94.585066] Get irq key
[ 94.610065] Get irq key
dso_acq_control:1:store_depth 4000, extra_len 64,acq_all_nm_for_read 4064,acq_dot_nm_of_timerange 80,sample_rate = 1000000000.000000
[ 95.285081] Get irq key
[ 95.310090] Get irq key
dso_acq_control:1:store_depth 4000, extra_len 64,acq_all_nm_for_read 4064,acq_dot_nm_of_timerange 160,sample_rate = 1000000000.000000
[ 96.110066] Get irq key
[ 96.135080] Get irq key
dso_acq_control:1:store_depth 4000, extra_len 64,acq_all_nm_for_read 4064,acq_dot_nm_of_timerange 320,sample_rate = 1000000000.000000
[ 96.985074] Get irq key
[ 97.010073] Get irq key
dso_acq_control:1:store_depth 4000, extra_len 64,acq_all_nm_for_read 4064,acq_dot_nm_of_timerange 800,sample_rate = 1000000000.000000
[ 101.035063] Get irq key
[ 101.310079] Get irq key
[ 101.935058] Get irq key
[ 101.985166] Get irq key
[ 102.060081] Get irq key
[ 102.110083] Get irq key
[ 102.410074] Get irq key
[ 102.560081] Get irq key
[ 102.660067] Get irq key
[ 102.735065] Get irq key
[ 102.860078] Get irq key
[ 102.935082] Get irq key
[ 103.160093] Get irq key
[ 103.310069] Get irq key
[ 103.335062] Get irq key
[ 103.410078] Get irq key
[ 103.485066] Get irq key
[ 103.510078] Get irq key
[ 103.635070] Get irq key
[ 103.760065] Get irq key
[ 103.835067] Get irq key
[ 103.860062] Get irq key
Take any of the stepping encoders, and slighly turn them to right or left, about 1/4 of the step, much less than it would need to make the "click".
Do you notice one side behaving differently? I one side needs more than the other, then it's likely to be a bad common signal.
Try soldering two wires to any encoder pins, then randomly touch ground with one at a time. Or just shorting them with tweezers or whatever.
I guess one of them won't make the IRQs!
-
It's a good guess, although not all the encoders are going to get one contact stuck at the same time. But the symptoms would also be the same if one of the signals Scan_Data_4 or Scan_Data_6 (not both at the same time) had gone nuts!
Time to look for an HC4051!! Thanks!!
-
I don't mean the encoder is stuck, but one of 4051s!
-
Ah, OK, I didn't understand it well. Sorry!
Most probably, U2, as it is the one that has two signals exclusively for the encoders, so it's the first one to be changed, but I'll buy more than one, just in case.
-
Take any of the stepping encoders, and slighly turn them to right or left, about 1/4 of the step, much less than it would need to make the "click".
Do you notice one side behaving differently? I one side needs more than the other, then it's likely to be a bad common signal.
Try soldering two wires to any encoder pins, then randomly touch ground with one at a time. Or just shorting them with tweezers or whatever.
I guess one of them won't make the IRQs!
I tried this and, as you guessed, one of them (the one that corresponds to Scan_Data_6) doesn't make IRQs.
It seems clear that channel 6 of the analog multiplexer U2 is not working.
I also checked that pulling down the Key_Scan_Data generates lots of IRQs, with lots of random key detections ;D
I also made another desperate attempt: shorting out pins 2 and 4 of U2, in the hope that channel 7 (unused, as Scan_Data_7 doesn't exist) would work and the software would "understand". But no luck. Replacing U2 is now the only hope...
-
You got it! Should be it. What else if not?
Damaged FPGA? Strange, but go figure.
Maybe they called them "LemonTrees" because they didn't pass QA and GoWin didn't want to its name there.
-
...sorry for my bad english...
Maybe, your problem is the same like mine DSO2D10 after a few month: suddenly shortcut in one of rotary encoder case (GND) to the inner encoder PCB.
It's blocking the data lines.
Mine repair was simple: teardown the encoder case, a little tape to isolate.
Search this video in YouTube: "Hantek DSO5202P: Knobs/Encoders Not Working Repair"
Maybe helping you...
-
Hello experts!
I got a DSO2D15 and I started making backups. First I used Backup_Builder so now I have all the files it produced. Then I made a safety backup with Dsoflash and it produced the 135168kB file. Then at the first power cycle the problems started. Serial and Hardware in system information show "undefined", so i tried to update them using the file "dso3kb_CN2318029043950_Model.upk", but I got an error:
Updated failed! Error code is -2
I tried also the USB fix update, the latest update from Hantek site, the full update I have got from Backup_Builder, even do_other_update without any script (just to test if it runs), all throw immediately the same error:
Updated failed! Error code is -2
I also tried the "Default setup" key, nothing changed.
Also tried in the Keysight Connection Expert console
PRIVate:SET:PCB "003.002.001.000.000.000.000.001"
error:
! VI_ERROR_TMO: A timeout occurred
Visa ErrorCode: 0xBFFF0015 (-1073807339)
and
PRIVate:SET:SERIal CN2318029043950
! VI_ERROR_TMO: A timeout occurred
Visa ErrorCode: 0xBFFF0015 (-1073807339)
however, the command:
PRIVate:FACTORY:RESET
reboots the scope, but returns error
-> PRIVate:FACTORY:RESET
! VI_ERROR_IO: I/O error
Visa ErrorCode: 0xBFFF003E (-1073807298)
What is weird is that after every power cycle the scope seems to forget some of the settings (if I disable the sound, it comes back at next power on); or if I save the settings in the internal memory it says it was done ok, but when I recall them it say "Recall failed".
Before making backups the system info showed (it looks to me that there are the latest versions of software and firmware):
Model: DSO2D15
Serial CN2318029043950
Software 1.0.3.0.0(230327.00)
Hardware 003.002.001.000.000.000.000.001
Firmware 3205
So my question is: is it any way to get back the update functionality? and as a bonus to set the serial and hardware fields?
Best regards,
Ionut
-
That's really weird. Try platform-tools then restoring your backupbuilder backup.
Or restoring the entire dsoflash backup.
-
It doesn't work. Platform-tools ends in error:
FLASH FAILED!
ERASE PARTITIONS...
Erasing 'boot' OKAY [ 0.045s]
Finished. Total time: 0.053s
Erasing 'cache' OKAY [ 0.077s]
Finished. Total time: 0.091s
Erasing 'dtb' OKAY [ 0.034s]
Finished. Total time: 0.048s
Erasing 'kernel' OKAY [ 0.073s]
Finished. Total time: 0.082s
Erasing 'rootfs' FAILED (remote: 'failed erasing from device')
fastboot: error: Command failed
Failed to erase the memory!
-
No damn idea! Post the complete log.
-
Not easy because of the cls in the batch:
FLASH PARTITIONS...
Selected: 2022.10.28_fpga_3205
< waiting for any device >
Sending 'boot' (202 KB) OKAY [ 0.022s]
Writing 'boot' OKAY [ 0.137s]
Finished. Total time: 0.177s
Sending 'logo' (750 KB) OKAY [ 0.063s]
Writing 'logo' OKAY [ 0.606s]
Finished. Total time: 1.892s
Sending 'dtb' (11 KB) OKAY [ 0.008s]
Writing 'dtb' OKAY [ 0.039s]
Finished. Total time: 0.086s
Sending 'cache' (1612 KB) OKAY [ 0.109s]
Writing 'cache' OKAY [ 0.710s]
Finished. Total time: 0.846s
Sending 'kernel' (2999 KB) OKAY [ 0.197s]
Writing 'kernel' OKAY [ 1.468s]
Finished. Total time: 1.682s
Sending 'rootfssize' (0 KB) OKAY [ 0.007s]
Writing 'rootfssize' FAILED (remote: 'ubi erase failed')
fastboot: error: Command failed
FLASH FAILED!
ERASE PARTITIONS...
Erasing 'boot' OKAY [ 0.045s]
Finished. Total time: 0.051s
Erasing 'cache' OKAY [ 0.077s]
Finished. Total time: 0.085s
Erasing 'dtb' OKAY [ 0.034s]
Finished. Total time: 0.050s
Erasing 'kernel' OKAY [ 0.075s]
Finished. Total time: 0.082s
Erasing 'rootfs' FAILED (remote: 'failed erasing from device')
fastboot: error: Command failed
Failed to erase the memory!
Press any key to continue . . .
-
And I have to add that a normal boot leads to a blank screen, now it's totally bricked...
-
For whatever reason the nand can't be written to!
Of course, if new data can't be written, it won't boot.
What does "dsoflash erase" do?
Also try erasing the entire flash with xfel (https://github.com/xboot/xfel/releases/tag/v1.3.2).
Only boot in fel mode, then:
xfel spinand
if detected
xfel spinand erase 0x0 0x8000000
But it's basically the same.
-
xfel spinand
Found spi nand flash 'W25N01GV' with 134217728 bytes
xfel spinand erase 0x0 0x8000000
100% [================================================] 128.000 MB, 13.645 MB/s 00
dsoflash erase did erase it ok also.
But platform-tools still fails with the same errors as before.
-
This issue never hapened before, maybe a defective flash? I don't know.
I suggest contact Hantek with this issue, they will likely send some platform-tools version!
-
I made some changes to dsoflash. Please download the latest version.
If running, power off the scope to reset everything.
Power the scope in FEL mode and run "dsoflash status", post the output.
Run "dsoflash erase", and "dsoflash status" again, is the output the same?.
This is my output:
Status 1: 0x7C
SRP0 BP3 BP2 BP1 BP0 TB WP-E SRP1
0 1 1 1 1 1 0 0
Status 2: 0x08
OTP-L OTP-E SR1-L ECC-E BUF RES RES RES
0 0 0 0 1 0 0 0
Status 3: 0x00
RES LUT-F ECC-1 ECC-0 P-FAIL E-FAIL WEL BUSY
0 0 0 0 0 0 0 0
-
The output is the same and exactly as yours, both before and after the flash erase.
-
Nothing seem wrong with the flash. Did you try restoring with dsoflash already?
Another thing you can try is to download a 132MB from here:
https://pinetools.com/random-file-generator
Flash it, then read it back, then open both files in HxD and run Analysis / Compare data to see what's wrong.
Ensure to store your original backup in a safe place, NO in the same folder, you might accidentally overwrite it.
-
Yes, the restore with dsoflash gets me to the point where I started this conversation: the scope boots, but updates fail with the "error code is -2", some settings do not survive reboot, cannot save/ recall settings.
-
Whoops, the dumped flash is entirely different of the read one, every byte seems to be different; example:
written
FD 39 77 ED 30 F7 83 91 24 ED 3B 8A F5 DC C0 49 53 20 CE BE 4D 99 FE 61 C0 B8 1A 02 DB 15 EC A4 FC 1C 62 39 0E F7 02 F0 BC 48 96 45 39 A4 83....
read
14 00 00 E8 20 47 03 00 24 40 10 00 A1 9C 80 49 00 00 00 00 41 10 4C 00 00 00 00 00 00 00 00 00 2C 00 00 00 00 00 00 00 00 00 00 00 31 24 02....
But the differences are too dramatic to explain why a restore of the original dump still works. Very strange!
-
And the weirdest thing of all: I flashed back the original file I dumped from the scope when I got it, then read back the flash content, and they are identical ! Hard for me to understand what's happening...
-
Few more test: make a dump after erasing, should be all FFs...
I would start a claim with the seller right now.
-
There is a https://4pda.to/forum/dl/post/29004439/Hantek2D15_V17_3205.rar new version of platform-tools (https://4pda.to/forum/dl/post/29004439/Hantek2D15_V17_3205.rar new version of platform-tools) on the 4pda forum.
After this platform-tools:
SW 1.0.2.0.0(221028)
FW 3205
-
It's not a new version? We already had 2022.10.28_fpga_3205.
Edit: Yeah, it's the same filesystem. Same MD5 checksums.
-
It's not a new version?
Look at the "Programm DSO2000 series Guide.pdf", no more PhoenixSuit_CN.msi installation. The Guide is new.
-
Just using the bare driver, extracted from the Phoenix Suite. That's what I do in the unified pack.
Else than that, nothing new.
-
After my trusty old Atten/Siglent decided to brick itself, I just got my new DSO2D10 via Amazon AU - a bit cheaper than Aliexpress or Bangood, free shipping from AU to NZ and delivered in a week. Out of the box, it's a pretty good scope for the money, but my motto is "If it's broke, fix it; if it ain't broke, hack it till it's even better".
So first, many thanks to the contributors to this forum for their excellent hints and advice, and to DavidAlfa in particular for his expertise and the various hacks and tweaks on google drive.
My DSO2D10 came with the latest firmware installed, but I reinstalled it anyway, along with the DSO2000 and Keysight PC apps and driver, then ran a full platform-tools backup and Backup_Builder for safety's sake.
First I upgraded it to DSO2D15, all OK except that PRIVate:READ:EEPROM still showed DSO2D10. Not sure if this causes any issues, but PRIVate:SET:MODEl1 and PRIVate:SET:MODEl2 to DSO2D15 fixed that issue.
Then I installed and tested Factory_Reset_Daemon (just in case of lockups), and installed the Small_English_Font which made the interface look a lot nicer. I also installed bmp2png_Daemon for when I want to save screenshots, and then used patcher to change the trace color for channel 1 to orange (CH1_COL="\xFF\xA5\x00") instead of yellow, to match the button color.
It would be nice if patcher also changed the ID, Trigger and channel block (at the bottom of the screen) but I can live with that.
Finally, I tested and overclocked to CPU_OC_PLL_N=28, CPU_OC_PLL_K=2, CPU_OC_PLL_M=2 and MEM_OC_PLL_N=16, which appears to be rock solid stable so far.
The only thing I haven't succeeded at so far is installing the USB Console "dso3kb_usb_console_install.upk" - it gives a message "Update Failed! Error code is -3". Not sure why this is, any help appreciated.
Anyway, it's a significant improvement on my old Atten/Siglent and I'm loving it so far - no lockups or odd behaviour (yet!)
-
You also have to modify some pictures to match the new plot colours, see here:
https://www.eevblog.com/forum/testgear/hacking-the-dso2x1x/msg3606590/#msg3606590 (https://www.eevblog.com/forum/testgear/hacking-the-dso2x1x/msg3606590/#msg3606590)
Check out the existing theme, for "visually impaired" as some people have trouble perceiving the difference between green and yellow.
You can extract it using the provided upk tools, all the files are inside, modify the colours, build the upk and done!
-
Thanks. Worked out how to do it from the document in your link.
-
Because you probably didn't read anything? :-DD
They're not in some usual picture format, that's why I linked that message but you missed the "SEE HERE" part.
Download the pdf and read the section 6.2.
-
Correct. My bad :-[ All sorted now and loving the new color scheme, orange for CH1 and blue for Wave generator & Burst, to match the button LED colors :-)
is the USB console upk installable on this model? Gives me an error code -3
-
Nice! Would you mind to share the theme package?
For sure someone else will like it.
USB console should work for all.
Error -3 ? Perhabs a corrupted package? Try downloading it again.
You're right about the patcher, I will look at the picture format, shouldn't be too hard to also patch the pictures on the fly.
-
Here's my theme attached. The font colors for Ch1 in the Measure menu are still yellow rather than orange - couldn't find a way to change that.
After installing stock firmware, I install my button_match theme and then Small_English_Font. There's probably a way of incorporating Small_English_Font into my theme but I'm only just starting to learn this stuff!
Yes, downlaoding USB console again worked thanks.
-
There were more suspicious data nearby the plot color table,.might be for other unimplemented functions...or for the measurements.
It takes an inmense amount of work to reverse-engineer the binary in Ghidra, patching it, copy to the scope, test, nope, keep trying other locations... very slow and tedious.
I did 99% of all this during the pandemic as I were 24/7 alone at home!
But cannot spend a week with coffee, nachos and loud metal anymore (Work, sleep, eat, blah blah), also I lost a lot of interest as Hantek is not fixing anything.
-
Quite understand and really appreciate all of the hard work you put into this. Still a pretty good scope for the money and for what I need it for :-)
-
Still a pretty good scope for the money and for what I need it for :-)
I still don't know what to make of this device.
To some it's the biggest piece of crap ever assembled, to others it's "a pretty good scope for the money".
It's perfectly clear that it doesn't come close to Rigol and Siglent etc, but it costs less than half as much here.
So in principle it can still be good value for money if you don't have too high expectations.
Somehow this thing appeals to me. I love cheap stuff.
The basic functions should work though.
I know... :palm:
-
It's a lot better than my old Atten/Siglent SDS1152CML which is now just an expensive and unaesthetic paperweight! At least this thing is just about impossible to brick!
-
It's a lot better than my old Atten/Siglent SDS1152CML which is now just an expensive and unaesthetic paperweight! At least this thing is just about impossible to brick!
Thanks!
Would you say that a DSO2C10 is worth CHF 140.- (~$156)?
Because that's how much it should cost tomorrow at the promotion, if I interpreted that correctly.
I was actually going to buy a Rigol DHO802, but I'm a little disappointed with my first impressions of this unit.
There are a few things that bother me, and "cute" and "12 bit" alone is not enough for me to pay significantly more than double the price of the Hantek.
I know a lot of people talk bad about these cheap Hanteks, but they also talk bad about the Zeeweii DSO2512G, which I haven't regretted buying for a second.
The difference is perhaps that the Zeeweii never crashes. ;)
-
I'd say that's a pretty good price if you don't need the wave generator. It's certainly not the best scope in the world but it's not the worst either. really depends what you need it for - most of my work is on audio (analog and digital) so adequate for that, although an old CRT analogue scope also comes in handy for CD eye patterns and the like.
-
Hello, greetings, with the latest updates, has the trigger problem been solved?, which did not stop the image, it was said that the trigger worked by software, not by hardware. Does it work with the latest updates correctly? It is something that stops me from purchasing
-
...sorry for my bad english...
Maybe, your problem is the same like mine DSO2D10 after a few month: suddenly shortcut in one of rotary encoder case (GND) to the inner encoder PCB.
It's blocking the data lines.
Mine repair was simple: teardown the encoder case, a little tape to isolate.
Search this video in YouTube: "Hantek DSO5202P: Knobs/Encoders Not Working Repair"
Maybe helping you...
Hello and thank you! Sorry for the late response! I didn't get or maybe I didn't see the email announcing your post. I'll see the viden and try if it's the same problem.
In the meantime, I've ordered the HC4051 to replace U2, waiting for it to arrive. With a bit of luck, the problem will be solved by the time it arrives!
-
In the manual, P51 Auto Scale, it says "Trigger Coupling is adjusted to DC, Noise Reject or HF Reject". Implies it has this capability - is there a way of setting Trigger Coupling manually (e.g. to Noise Reject)? I can't find it under the Trigger menu or Auto Set menu!
-
...sorry for my bad english...
Maybe, your problem is the same like mine DSO2D10 after a few month: suddenly shortcut in one of rotary encoder case (GND) to the inner encoder PCB.
It's blocking the data lines.
Mine repair was simple: teardown the encoder case, a little tape to isolate.
Search this video in YouTube: "Hantek DSO5202P: Knobs/Encoders Not Working Repair"
Maybe helping you...
Hello and thank you! Sorry for the late response! I didn't get or maybe I didn't see the email announcing your post. I'll see the video and try if it's the same problem.
In the meantime, I've ordered the HC4051 to replace U2, waiting for it to arrive. With a bit of luck, the problem will be solved by the time it arrives!
EDIT: Indeed, that was the problem!!!!
One of the encoders had one of the sides derived to the case, which in turn is connected to the ground. As the video that @Joemega suggested to view (https://youtu.be/X6q4JcOLKOI) explains, this is equivalent to having Scan_Data_4 or Scan_Data_6 (the latter in my case) connected to ground via the corresponding diode, so no change for any of the encoders is detected when Scan_Line_X selects them (see first attachment).
So I did the same as @Joemega: opened the offending encoder by straightening the 4 tabs that hold the plastic part to the case and insulating the plastic part from the metallic part with some tape.
As you can see in the 2nd and 3rd photos, the failure was caused by a bad encoder's design (I don't think it can be fully blamed on Hantek, but mostly on their supplier...). The plastic part has conductive circular tracks embedded and these tracks have four little spikes (two at each side) protruding from the plastic matrix exactly where the aforementioned tabs lay when the encoder is closed. Depending on how the tabs are pressed during manufacturing, maybe there will be contact or not, but the distance would be very short, so just with normal use or with a light blow on the buttons this contact may happen, as was in my case.
Now the scope is back to normal and the panel self test goes OK. From what I've seen in the eediscuss forum, this failure is not that uncommon (not only for DSO2000 series, as the video is for another model), so maybe this can help if your oscilloscope develops this failure over time.
Many thanks to @Joemega for spotting the solution and to @DavidAlfa for his help analyzing the failure.
-
After applying all the mods I wanted and overclocking to CPU 720MHz, memory 408MHz, to my DSO2D10, I'm very happy with the performance and stability of my upgraded DSO2D15. No freezes or glitches after several hours of use. Thanks to DavidAlfa and others for the tips and tricks.
https://www.youtube.com/watch?v=bMFlXeKC0Zw (https://www.youtube.com/watch?v=bMFlXeKC0Zw)
-
Hello everybody,
After my first adventures with DSO2D15 (hardware issue still unresolved, I will need to replace the memory chip which is on the way together with a programmer and converter board), I ended with my laptop loaded with all the software necessary to connect to and program the oscilloscope.
Then I started to have strange behavior on my laptop, and errors related to USB connected devices (smartphone, DVD-writer) which are caused by the before mentioned software. So I have put together some instructions on how to "clean" your PC and restore back the USB to working condition, and I am now sharing this with you:
USB is derailed from normal functioning:
- connecting phone does no longer work
- writing more than one DVD on a writer connected to USB fails randomly (some of the written files do not verify)
- possible other errors on USB-connected devices
Steps to recover:
- uninstall Phoenix Suite, do not press the button with chinese characters (it says "Cancel" !), be patient it will uninstall in a minute or two
- no need to touch zadig
- under Device Manager/ Show hidden devices in View menu, then list USB devices with VID_1f3a_PID_ef08, there are possibly multiple devices and in multiple places; then normal uninstall all BUT leave only one of them, the last uninstall do it with checking "Delete the driver software for this device"; look for devices under:
Universal Serial Bus controllers
Universal Serial Bus devices
- uninstall Windows software listed in Settings/ Apps (here is what I had installed on my laptop):
DSO2000
IVI Shared Components 3.0.0
IVI.NET Shared Components 1.1.2 for .NET 2.0
IVI.NET Shared Components 2.0.0 for .NET 2.0
Keysight Communication Fabric 2.2
Keysight Discovery Service
Keysight Distributed Infrastructure
Keysight IO Libraries Suite 2023 Update 1 -> it will complain about not finding an uninstaller, there is no problem, just go on
Keysight VISA Cross-Platform Components - windows -> will be uninstalled by "Keysight IO Libraries Suite 2023 Update 1"
Keysight VISA Cross-Platform Components - windows x64 -> will be uninstalled by "Keysight IO Libraries Suite 2023 Update 1"
VISA Shared Components 7.2.0 (64-bit)
VISA.NET Shared Components 5.6.0 (64-bit)
VISA.NET Shared Components 7.2.0 (64-bit)
- reboot PC
Note: this will repair the MTP driver for Android smartphone, if not: under Device Manager, right click on the MTP driver with yellow exclamation mark/ Update, choose to browse computer/ pick from a list of available drivers/ click on the MTP driver, then reboot again
-
...
I honestly can't understand why anyone would buy one of these when Siglent and Rigol (and other manufacturers) with great reputations build fantastically better instruments for about the price of a Big MAc dinner and a 6-pack more.
...
smh. I just ordered a DSO2D10, but I can still cancel it. Does anyone have a model recommendation that has similar specs? (100MHz, 1GSa/S, function gen) for just a bit more?
The only one I can find that has a wave generator is the Rigol DS1104Z-S Plus, but this one is over 5x the price. 😩
-
smh. I just ordered a DSO2D10, but I can still cancel it. Does anyone have a model recommendation that has similar specs? (100MHz, 1GSa/S, function gen) for just a bit more?
The only one I can find that has a wave generator is the Rigol DS1104Z-S Plus, but this one is over 5x the price. 😩
As far as I know, there is nothing from Rigol or Siglent in this price range.
The cheapest are Rigol DS1102Z-E or Siglent SDS1202X-E (or SDS1102CML+), as far as I know. Prices differ by country.
A signal generator could be bought separately. E.g. a FY3224S for the beginning does not cost much.
-
smh. I just ordered a DSO2D10, but I can still cancel it. Does anyone have a model recommendation that has similar specs? (100MHz, 1GSa/S, function gen) for just a bit more?
The only one I can find that has a wave generator is the Rigol DS1104Z-S Plus, but this one is over 5x the price. 😩
As far as I know, there is nothing from Rigol or Siglent in this price range.
The cheapest are Rigol DS1102Z-E or Siglent SDS1202X-E (or SDS1102CML+), as far as I know. Prices differ by country.
A signal generator could be bought separately. E.g. a FY3224S for the beginning does not cost much.
Thanks for the suggestion. Looks like those are 2x+ the price unfortunately, at least in Japan. Oh well, I guess I'll stick with the Hantek and see how it goes.
Edit: Gosh darn it, looks like the DS1102Z-E went on sale, and just as soon as I get the shipping notification for the Hantek -_-
-
Also the new Rigol DHO800 series look very nice.
12 bit ADC and 1024x600 touchscreen, $350 2ch/70MHz version, $400 4ch/70MHz, blows Hantek out of the water.
I think the 802/804 can be hacked to the faster 100MHz 812/814, but I didn't search for it.
https://www.batronix.com/shop/rigol/DHO800.html (https://www.batronix.com/shop/rigol/DHO800.html)
-
Also the new Rigol DHO800 series look very nice.
12 bit ADC and 1024x600 touchscreen, $350 2ch/70MHz version, $400 4ch/70MHz, blows Hantek out of the water.
I think the 802/804 can be hacked to the faster 100MHz 812/814, but I didn't search for it.
Early tests show hacks are possible but they aren't perfected yet though I am sure there won't be a problem once there are enough oscilloscopes in peoples' hands.
Also thank you David for voicing your opinions of the DSO2x1x oscilloscopes. I nearly bought one but held off to see if the firmware improved. Now I have a Rigol DHO804 on the way. You might consider adding a new first section to your DSO2x1x FAQ titled "Should I buy one?" with links to you and others saying "don't."
-
Anyway, in one respect the Hantek is unbeaten: it costs one third of a Rigol with AWG.
As problematic as it may be, no one has ever doubted the bandwidth or sampling rate as far as I know.
Unfortunately, the Hantek has no competition in terms of price and is therefore difficult to compare.
-
Dear friends, I need your help again.
I received a faulty (memory chip error) DSO2D15 and Hantek support instructed me to replace the W25N01GVZEIG. I bought some chips from AliExpress and now the plan is to: (1) desolder the old chip from the board, (2) sit/ solder a W25N01GVZEIG on a SOP8 board with pins, (3) prepare some sort of socket for this convertor I manufactured and (4) solder the socket with some wires to the motherboard to replace the original W25N01GVZEIG (David has done something like this using old MMC card and a MMC socket).
But now my problem is that I desoldered the memory chip from the board using hot air, but I managed to rip two of the pads which were used to connect the W25N01GVZEIG (attached), the corresponding pins are 7 and 8, on the left-down part of the empty place where the chip was.
Do you know any alternative locations on the motherboard where I can solder wires, i.e. where those 7&8 chip pins were going onto the board?
Many thanks for any ideas you would provide!
-
Always poke the IC with the tweezers before trying to remove it, if not moving freely then more heating is required!
I disencourage doing the socket thing, I did in a time where almost nothing was knew about the scope.
I removed all that short after learning there's nothing important inside and no special procedures are needed for recovery.
Check the schematics (https://github.com/pecostm32/Hantek_DSO2000/blob/main/Schematics/Mainboard/Processor.png), also this picture (https://www.eevblog.com/forum/testgear/hantek-dso2xxx-schematics/msg4262782/#msg4262782).
[attachimg=1]
-
Dear friends, I need your help again.
I bought some chips from AliExpress and now the plan is to: (1) desolder the old chip from the board, (2) sit/ solder a W25N01GVZEIG on a SOP8 board with pins, (3) prepare some sort of socket for this convertor I manufactured and (4) solder the socket with some wires to the motherboard to replace the original W25N01GVZEIG (David has done something like this using old MMC card and a MMC socket).
I did something similar to what you want to do in order to be able to quickly change memory chips during various tests or in cases of checking problematic dumps from members of the Russian forum. As it turned out, this socket thing does not work without any problems with any wires. You can solder everything correctly, but the scope will not boot, or after updating or using platform-tools, the scope stops working. Maybe I was just unlucky. The wires I use now without any problems are a set of breadboard jumper wires from Aliexpress. So I would not advise you to build such socket things.
-
Thank you both for your advice, I appreciate your experience. Unfortunately for me it's not a choice, I need to revive the scope I just bought, and soldering back the memory with hot air seems to be impossible now (with the two pads exfoliated, and my soldering skills seem to be poor...).
So if I do not try with wires and some kind of socket, the scope is as good as a paperweight.
I will let you know what happens.
Best regards to all.
-
soldering back the memory with hot air seems to be impossible now (with the two pads exfoliated, and my soldering skills seem to be poor...).
Such damaged pads are easily repaired using two thin wires as shown in David's photo. At least you could try this. This is better than the story with socket thing.
-
@vistorik: there is one more impediment I did not mention: the couple of W25N01GVZEIG I received from AliExpress are used ones (despite the seller said they are new!!), and the back was polished to hide the fact they were desoldered from some board. As a result, they do not adhere well to solder, I spent a few days trying to make them stick on a converter board using hot air gun and solder paste. So putting such a chip on the DSO motherboard would inevitably lead to over-heating (due to my lack of experience with hot air soldering) and more pads exfoliating, eventually desoldering other components and destroying the motherboard beyond repair.
So despite your solution being very elegant, I went on with the converter-socket-wires approach. The picture shows the hardware part of the result.[attach=1].
First I put a memory flashed with the image I saved with dsoflash when the scope arrived. The scope started, but the functionality was poor: buttons were sluggish, de-calibration of the input, could not save into internal memory (kind of errors I have seen previously when I started asking help in this forum).
Then I put another memory (huh, this is one advantage of having a socket - could change the memory very easy!) and flashed the scope using platform tools in FEL mode. Scope started and was working much better, then I upgraded to the latest firmware from Hantek website, calibrated, and all works well now. I tried to set the serial number and board ID using the upks created when I ran Backup builder when I received the scope, but I got error -3 (and this error appeared on any upgrade with a package from that Backup builder created set. Finally I managed to change those two using commands in Keysight IO Monitor (PRIVate:SET:SERIal and PRIVate:SET:PCB).
So I would say that it is still a success. I can use this scope for visual inspection of waveforms and will not trust this scope for exact measurements, but at least I did not loose all the money, which is something! And all this is due to you all who worked to decipher the intricacies of this scope and share this information with us.
Thank you all !
-
Error -3?
Make sure you're placing the upk files at the root of the USB drive, better avoid folders, absolutely avoid spaces in folders or filenames, always use safe drive extraction.
Also, place a small decoupling cap in the socket pins to compensate the long wires, the usual 100nF should do it.
The only thing you can really lose is the generator amplitude calibration, the scope channels will work fine after running a calibration procedure, so relax, you can trust it.
Still, I don't think the upk backups are broken, I can check them if you send them to me.
-
It turns out that the generator calibration is fine, I checked it at 1kHz and 100kHz, for 1.5 and 6V amplitude and for all the waveforms it can provide - it seems that the amplitude and frequencies are ok (at least gross values, not talking about mVolts).
As for upks all conditions were met. I unpacked the dso3kb_CNxxxxxxxxx.upk and all the files are ok, they are even exact content with the other backup by backup builder I took with the new memory chip and after setting everything up - all files within the upk are identical.
-
And I have uploaded on Gdrive the files (in the writable folder).
Thanks again.
-
Then I put another memory (huh, this is one advantage of having a socket - could change the memory very easy!) and flashed the scope using platform tools in FEL mode.
After you flashed the scope using platform-tools, the calibration generator file dds_calbration.dat could be restored by the system using calibration coefficients from EEPROM PT24C02. You could check this using dso3kb_CNxxx_Calibratio.tar.bz2 and dso3kb_CNxxx_EE.tar.bz2 archives from your backup. From the dso3kb_CNxxx_EE.tar.bz2 you could get ee.bin - this is the dump of PT24C02, and from the dso3kb_CNxxx_Calibratio.tar.bz2 you could get dds_calbration.dat. Using any HEX-editor you could see calibration coefficients in these files in Hex and Double float format. To convert these formats you can use a Floating Point to Hex Converter (https://gregstoll.com/~gregstoll/floattohex/). /). Calibration coefficients in HEX format (HEX value) must be entered byte by byte in reverse order, and then you click "Convert to double" - these should be calibration coefficients in ee.bin (see the pictures as example). The calibration coefficients in the dds_calbration.dat and the ee.bin are in red frames.
-
I've been reading this thread for 3 days now, and I can't thank everyone enough for sharing their knowledge and experiences. Very much appreciated.
I just got a Hantek DSO2D15 off Amazon for $215USD, and so far, it's been great except for one thing: I work with MIDI, so I need to decode UART at custom baud rate of 31250. So far I haven't been able to get there because:
- The initial value is ~115200, and the multifunction knob only increments/decrements by 1. You can imagine how long that takes to get to 31250. Still, I tried.
- Once I got down around 49000, the number would randomly increment by ~10000, ~1000, or ~100, with no discernible logic to which one. If Hantek tried to implement ballistics on the multifunction encoder for custom baud rate, it needs work. Or I'm doing it wrong.
- The error always increments the value, never decrements.
- At this point, I can never get below 55000, because once I get down around there, no matter how slowly I roll the multifunction encoder, the value will always jump up by one of the aforementioned amounts.
Has anyone else seen this?
I would assume a workaround is to set it manually via PC connection, but it seems odd that Hantek didn't implement the custom baud rate by allowing you to choose a starting point and rolling from there. But like I said, I may be doing it wrong. The manual is fairly sparse on this subject.
I'm also on a Mac, so I haven't tried to set up the SCPI tools yet. The eediscuss forum shows SCPI commands available for the Trigger/UART namespace, so maybe I can set it there?
Software is 1.0.3.0.0(230831.00)
Hardware rev is 003.002.000.000.000.000.001
Firmware is 3205.
-
Rotate slower, then it'll let you adjust it. If you go too fast then yeah, it'll go in 1000, 10000 steps. (Or maybe it's a new software bug introduced in the newer version you have!)
Unpack this setup file, copy the .pho file to the root of a usb drive and load it from the Save/Recall menu (Choose external)
23.08.31 is a newer software version, not released yet!
Please run Backup Builder and send me the FULL package so I can make a new update, everything is in the FAQ (Check my signature).
Edit:
For whatever reason, I mean, because it's *** Hantek, it saved a crooked setup, the scope went extremely slow after loading it.
Saved a new setup, this worked as it should.
-
DavidAlfa, Full backup uploaded to your drive per the FAQ and the Hacking thread. Your .pho file gave me the 31250 baud rate I needed, cheers!
-
DavidAlfa, Full backup uploaded to your drive per the FAQ and the Hacking thread. Your .pho file gave me the 31250 baud rate I needed, cheers!
Except EE package, all others are corrupted somehow.
Please run backup builder again, or try reuploading them.
BTW, I forgot I had added the extra packages, so I only need extra/dso3kb_CNxxxx_Software.upk file.
First I put a memory flashed with the image I saved with dsoflash when the scope arrived. The scope started, but the functionality was poor: buttons were sluggish, de-calibration of the input, could not save into internal memory (kind of errors I have seen previously when I started asking help in this forum).
You should have avoided this in first place, you knew your old memory was bad, so would your image. So no need to replace it, just take the platform-tools route directly.
I tried to set the serial number and board ID using the upks created when I ran Backup builder when I received the scope, but I got error -3 (and this error appeared on any upgrade with a package from that Backup builder created set.
I ran dso3kb_CN2318029043950_Calibration.upk and worked just fine, so again check that your usb isn't bad somehow, remember, fat32, no files or folders with spaces or strange chars, always use safe drive extraction.
All your UPKs extracted fine.
The generator calibration is the only real important thing unless it's already stored in the eeprom, otherwise it won't matter.
-
Hello David,
I would like to thank you very much for your extensive work on the Hantek DSO2X1X software. And also to the others who contributed to the improvement. This work led to me buying a DSO 2C10 for just under 180EUR from a Czech warehouse on aliexpress, contrary to the suggestion in your signature. It comes with all the necessary components for the generator and has already been extensively supplied with your mods (including backup). It didn't have any software that was new to you. Your work is great. Despite all the criticism of C'n'C (cheap 'n china), we should not forget that these products can at least reduce the price level for competitors to a somewhat more reasonable level. And the thing is usable, thanks to your work. Let's see how I can suppress the interference from the power supply and the problem that you can destroy the generator with a strong trigger source still connected. Clamping diodes connected directly to the output OP of the generator could put too much capacitive load on it and lead to wild oscillations. But perhaps specifically add it to the first filter capacitor in the generator's output network.
By the way, I'm the one who uploaded 5 themes for you today. I understand Theme006 as a simple addon, and that's why I delete some not necessary from your do_update.sh. You might want to take a closer look at this and see if you agree.
-
I can't check your files right now, so I don't know what are you calling "not necessary", check the existing existing "Visually impaired " theme as the guideline.
Also search "theme" in the dso2x1x hacking thread, there you'll find more details.
Themes might modify the icons, and/or the dso binary (Phoenix), never hardcode Phoenix itself, use pattern search & replace, like the existing theme does using bgrep, that way it will be more likely to work between different versions.
-
Hallo David,
don't worry, theme 002, 003, 004 and 005 are based on theme 001, exchanges a lot of icons, use your full do_update.sh and change only the color define in this file on some of the four theme.
Theme 006 changes only the two wave generator icons. I see it as an addon (update) to any theme. So I removed the color defines and the BGRP define. And I also remove begining with the "use a clean phoenix copy" section everything which manipulate the colors within the phoenix app. (Backups will be done.) So for me it's a example for a theme (update) which exchanges only icons with no connetion to a color which will be drawn by the phoenix app. This is for your brief information.
All the five theme include a readme and 2 images of the changed dso screen. They are all already installed on my 2C10 (2D15) and ok for me.
I had already read the full ...DSO 02X1X thread and the "hacking thread" before I ordered my DSO 2C10.
Thank you.
-
DavidAlfa, Full backup uploaded to your drive per the FAQ and the Hacking thread.
Hey, just in case you missed this:
Except EE package, all others are corrupted somehow.
Please run backup builder again, or try reuploading them.
It would be interesting to try out that new version, cheers!
I had already read the full ...DSO 02X1X thread and the "hacking thread" before I ordered my DSO 2C10.
Thank you.
Thank you for contributing! I just checked the files... you mention using a Hex editor to modify the icons?
That's why I said to read the hacking thread, there it's explained how to open the icons in Gimp!
This great guide explains how to open them (section 6.2):
https://www.eevblog.com/forum/testgear/upgrading-the-hantek-dso4072c-osciloscope-bandwidth-from-70mhz-to-200mhz/?action=dlattach;attach=848068 (https://www.eevblog.com/forum/testgear/upgrading-the-hantek-dso4072c-osciloscope-bandwidth-from-70mhz-to-200mhz/?action=dlattach;attach=848068)
-
I resisted it for a long time, but when the price reached $130 (https://www.aliexpress.com/item/3256804499579931.html) it finally happened.
I ordered a DSO2C10 to minimize the risk and because I already have an AWG.
That's about the price category of a Fnirsi DPOX. :palm:
I know that a Rigol or Siglent would be better, but seriously, you can't compare them price-wise.
I've read that they hardly ever crash now.
I'll read up on the subject when it's on its way.
Thanks in advance to DavidAlfa for all the information. :-+
-
$130 is a very good price!
You'll find small bugs here and there, occasional lockups, but they crash way less often since FPGA FW was updated to 3102/3202 in 2021 or so.
-
$130 is a very good price!
You'll find small bugs here and there, occasional lockups, but they crash way less often since FPGA FW was updated to 3102/3202 in 2021 or so.
Thank you!
I have a question that I have never found an answer to: Is there really a difference, between the 100MHz and the 150MHz version?
You probably know the video of Kerry Wong (https://youtu.be/Mmx7eo9STXE?t=1567) where he measures 200MHz and more with the 100MHz Hantek.
Of course it falls below the -3dB limit, but is the DSO2C15 or a hacked DSO2C10 really better?
In other words, is it worth hacking it?
-
The only true fact I know of is they ship a 100MHz or 150MHz proble with each version!
They seem to not have any real difference in HW.
-
The only true fact I know of is they ship a 100MHz or 150MHz proble with each version!
They seem to not have any real difference in HW.
Thanks!
I can well imagine that this is the only difference. ;)
Since I have a 250MHz probe and other BNC and SMA connectors as well as an AWG, the DSO2C10 is probably the device with the best price/performance ratio for my case.
Hacking is probably not worth it.
Hopefully it will arrive soon.
-
The only true fact I know of is they ship a 100MHz or 150MHz proble with each version!
They seem to not have any real difference in HW.
I also found no sign of a difference between the 100MHz and 150MHz versions of the DSO (at least after the 2D15_conversion upgrade, because I wasn't looking for a difference before). My 100MHz version came with a PP-150 sample. But it has a bandwidth of 100MHz on the nameplate. If you look for the PP-150 on aliexpress, if something is specified, it is always specified as 100MHz.
With the money I saved I bought two 250MHz specified probes (the black ones with the red 1x/10x switch). They were just under 1EUR more expensive than the PP-200 (200MHz specified).
Today I compared both probes (CH1 the 250MHz, CH2 the 100MHz PP-150). I removed the ground pigtails from both probes (avoid interference) and adjusted them cleanly at the calibration output. The rise times of the calibration signal are not sufficient to detect differences between the two probes. Then I inserted a sufficiently thick needle into the signal output of the BNC socket of the wave generator to connect both probes at the same time with their hook (again without pigtails). I set the generator to 1Vpp, 10MHz square:
(http://)
We know that we cannot accurately predict the signal shape at the output due to the output filter and the capacitive load from the two probes. Both probes are connected to this signal at the same time. The 250MHz probe shows shorter rise times...
I also noticed that the 250MHz probe shows higher amplitudes of the 100MHz interference signal (during probe calibation), which probably comes from the power supply.
Neither are exact measurement results, but rather indicators of the differences to be expected between the two probes. On both probes, the 1x/10x switches are sufficiently stiff to not move on their own, as was written in a review of the 250MHz probe.
-
$150 and I am the happy owner of this device)) I immediately reflashed it to D15 (many thanks to DavidAlfa) and also had to declare war on HF noise, replaced the capacitors with others with an operating frequency of 200 kHz, replaced the input capacitor with Nichicon 47mkf, added ceramic capacitors 0.1 uF and 1 MCF for power buses and ferrite rings for wires. Now it is a little closer in image quality to analog))
-
Power consumption is pleasing)
-
Test AWG square 50mv frequency 500kHz.
What problems ))
-
1MHz
-
Test AWG square 50mv frequency 500kHz.
What problems ))
Hi!
I am still waiting for my DSO2C10. With a little luck I'll have it in two weeks.
Could you describe what exactly you changed (schematic or photo?) and what exact components you used as replacements?
Since your changes were obviously successful, that would be interesting. I'm a newbie at this sort of things.
Thank you.
-
Of course it falls below the -3dB limit, but is the DSO2C15 or a hacked DSO2C10 really better?
In other words, is it worth hacking it?
the main purpose of this hacking is unlock AWG which was hidden on cheaper C10 version.
-
Now it is a little closer in image quality to analog))
.
No .... these kind of scope should never give you analog image quality.
I think with DSO you should choose the one with Digital Phosphor technology (like SPO/Siglent or Ultra Vision/Rigol) for better result and faster waveform capture/display rate.
I hate the laggy on Hantek especially when opening Measuring (only 1-2 parameters like RMS or Freq) on the display.
-
Got a 2C15 a few months ago (Now a 2D15 after sending the SCPI commands to turn on WAVE GEN)
One thing I have noticed about the LCD screen on my Hantek DSO is
the change in contrast when changing vertical viewing angle.
See attached picture.
Upper screenshot was taken when viewing LCD pretty much straight on at right angle.
Lower screenshot is viewing from somewhat above the screen.
(This is my normal viewing angle when scope is on my desk).
The non zoomed portion of the waveform is almost invisible.
I have noticed this problem only with DISPLAY PERSISTENCE and the Horizontal Zoom features,
not sure if this highlighting/non-highlighting is done other places in the menus.
SW is 1.0.3.0.0(20230327)
FW is 3202
For now I'll probably prop the front feet up on something to fix the viewing angle.
Is there a contrast adjustment on the internal LCD panel?
(The DISPLAY menu shows just Intensity and Brightness)
-
No contrast adjustment. Use the bottom legs to adjust the viewing angle.
This screen is actually pretty decent!I hate the laggy on Hantek especially when opening Measuring (only 1-2 parameters like RMS or Freq) on the display.
Have you tried overclocking? Not a miracle but helps.
Most will get around 684-720MHz just fine.
-
Yes I did and used Hantek for 9 months before gave it for my friend.
I tried the optimum and steady clock for Cpu and Ram but basically Hantek uses cpu for calculating and drawing waveform so it must be lagged.
If you use Hantek for "static" waveform it is ok but "dynamic" like analog audio monitoring or calibrating (tape deck azimuth and phase, recording bias...) its not real-time display, delay about 0.5s. The more measuring display on screen the more laggy scope does. Quite annoying.
Then I switched to Rigol Ds1102z-e and now Siglent Sds1202x-e. $100 extra but definitely better. Waveform displayed look like analog scope, both trace and speed.
-
Then I switched to Rigol Ds1102z-e and now Siglent Sds1202x-e. $100 extra but definitely better.
It depends very much on where you live.
Here the RIGOL DS1102Z-E costs about 320 CHF, the Siglent SDS1202X-E (imported by post, there is no distributor here) about 385 CHF.
That's quite a difference compared to the 124 CHF for the Hantek DSO2C10.
I see it as the next step. I'm sure I can learn and experiment a lot with the Hantek.
When I'm "done with it", I might buy a Rigol, but then a better one, with 4 channels etc. We'll see.
-
Then I switched to Rigol Ds1102z-e and now Siglent Sds1202x-e. $100 extra but definitely better.
So the SDS1102C > SDS1102X-E > SDS1202X-E product ID and BW hacks all worked ?
-
So the SDS1102C > SDS1102X-E > SDS1202X-E product ID and BW hacks all worked ?
;D Im in the middle now ... SDS1102X-E. I will test "SCOPE_ID?" soon as your hint.
Anyway I like "E" than "C" despite of its just a sufix.
Of course I know C is never becomes E, it lack of ERES menu and half of capture rate but I see Siglent 1102X-E is more responsive than Rigol DS1102Z-E. It is much faster in UI, capture rate, better noise front end, layout in front plate...
-
It depends very much on where you live.
When I'm "done with it", I might buy a Rigol, but then a better one, with 4 channels etc. We'll see.
I completely agree ...
Especially now you are living in Switzerland now, the heaven on the Earth, so I wonder why you don't take a look at Siglent or Rigol even Rohde & Schwarz or so on instead of Hantek. I'm just joke ;D
Hantek is good, maybe best p/p but it suite for student or amatuer user.
I see that the measuring result from Hantek is not reliable.
When it gives results I am always skeptical... is this (waveform) right?
I use scope for calibration analog audio equipment, especially bias mixed with signal. Hantek showed me laggy and ugly waveform, noise, bad trigger (for complex signal)
I just want to share my experience, I'm not talking bad about Hantek here.
It depends on your needs and how you use the device.
Anyway thanks David Alfa for your support and all usefull modding/hacking tips/tools.
-
Hantek is good, maybe best p/p but it suite for student or amatuer user.
...
It depends on your needs and how you use the device.
Exactly!
I wouldn't even call myself a serious amateur.
I got my first small oscilloscope (Zeeweii) in January this year and have had a lot of fun with it so far.
I also bought a TinySA and a NanoVNA and that opens up a new world as well.
But for me these are toys and they are fascinating in themselves.
I don't need them for a specific purpose or to earn money, just to play and learn.
I think that the Hantek with its relatively many features will also keep me busy for a while. Maybe I will even try to "improve" it. :palm:
I might not dare to do that with a "good" Siglent or Rigol device. So that's fine with me!
As you can see, there are different perspectives and needs and although I could afford a better device, it wouldn't be right for me at the moment.
-
hello of the whole thread I read, but nowhere did I come across whether anyone tried to increase the AWG frequency set ?, generator, thank you for the answer
edit, does a man get a reply here? Or is the forum dead?
im sory im translate gooogle
-
23.08.31 is a newer software version, not released yet!
David, you can get this new software version from 4pda.to/forum: https://4pda.to/forum/dl/post/29467623/dso3kb_20230906.upk.zip
-
David, you can get this new software version from 4pda.to/forum: https://4pda.to/forum/dl/post/29467623/dso3kb_20230906.upk.zip
My Russian is not very good, but 404 probably means "not found" there too. ;)
-
David, you can get this new software version from 4pda.to/forum: https://4pda.to/forum/dl/post/29467623/dso3kb_20230906.upk.zip
My Russian is not very good, but 404 probably means "not found" there too. ;)
You do not have access to download files from this forum without registering. David has it.
-
David, you can get this new software version from 4pda.to/forum: https://4pda.to/forum/dl/post/29467623/dso3kb_20230906.upk.zip
My Russian is not very good, but 404 probably means "not found" there too. ;)
You do not have access to download files from this forum without registering. David has it.
OK, but the message should then read "401 Unauthorized".
-
Yeah you need to be logged on to download!
Edit: Attached. It's actually 23.08.31 version.
Will update the faq/Drive tomorrow.
-
My English is not good, so I used Google Translate:
I successfully modified 2c15 into 2d15. However, other problems arose during the modification process. I disassembled the device to determine if any relevant original parts were missing. However, after installing it back, I found that the CH1 reference voltage drifted greatly after the machine was cold-started. I tried to calibrate the device but the system reported error code 510d1. Just wait until the machine warms up and restart it a few times.
vbase is constantly changing, the highest is 90v, the lowest is -400mv.
CH2 is normal.
Did I break something while disassembling the device?
-
Did you change FW version?
-
No, I just upgraded the software to the latest one. fw is always 3202.
-
Yeah you need to be logged on to download!
Edit: Attached. It's actually 23.08.31 version.
Will update the faq/Drive tomorrow.
Hi, do you see any improvement on this version ? ;D
-
hello of the whole thread I read, but nowhere did I come across whether anyone tried to increase the AWG frequency set ?, generator, thank you for the answer
edit, does a man get a reply here? Or is the forum dead?
im sory im translate gooogle
I've been here for a long time and, as far as I remember, there's no way to increase it
-
Hi.
Partially corrected the signal display error at a memory depth of 400k or more.
Previously, when switching from 50ms/division to 100ms/division, the signal was not displayed correctly.
With the new software, this problem has been fixed, BUT if after switching to 100ms/division, press the Start/Stop button and again the Start/Stop button, the signal is not displayed correctly again.
-
You could increase the frequency by making a custom waveform in the pc software...
-
So now I am also one of the Hantek victims... :palm:
I think whether the device is worth the money depends on the money.
I paid CHF 123.14 (~$130). Everything included (postage, paypal fees,...).
That's the price range of an Owon hds272s for example.
I did a test with the TinySA to see how far the 100MHz version (without modifications) goes and if there is a difference to the 150MHz version (except for the probes).
Strangely enough, the Vpp tends to increase up to 150MHz.
This could also be due to the TinySA or the cable, or simply because I've only had it for half an hour.
It can trigger and measure up to 250MHz, although the end can be felt here.
I can't imagine that the 150Mhz version works better.
So not bad for the price.
And it is absolutely silent and starts up quickly! A dream! :-DD
P.S. The shop (https://de.aliexpress.com/item/1005004685894683.html) is worth recommending. Very pleasant and communicative.
-
Hello. I purchased a new oscilloscope DSO2C10, firmware 3205 - after purchase I backed it up (with DSO Flash) and installed the mod 2D15. He worked for 20 days. Yesterday, when analyzing I2C (3.3V) signals, it stopped responding to buttons. The buttons continue to beep when pressed. I read earlier about the device freezing due to overheating, so I turned off the oscilloscope... But after cooling for 12 hours, everything is the same - it turns on, initializes, test blinks and that's it... Sometimes (at the moment of switching on) I manage to press a button - then I can go to the menu and perform actions within the menu for a long time, after exiting the menu there is no reaction. The buttons continue to beep when pressed. When connecting via USB with the standard program, there is no connection, but there is a USB icon on the oscilloscope... Tell me, please, which way to look? Thank you.
-
I know I may be a bit overcautious, but this is the first time I've to deal with an *.upk file.
I want to run the backup builder.
In all the descriptions I read "Run system update".
But I don't have anything that says that.
I have a menu item "Update Firmware".
Is that it?
Sorry, I know it sounds ridiculous, but I don't want to make a mistake before I have backed up everything.
-
Yes! :-+
-
Yes! :-+
Thank you very much!
That worked perfectly!
The AWG is now also working. :-+
Edit: So, now I think I'm done with the setup and backups for the time being.
Overclocking, factory reset daemon, fonts.... all done.
You can tell it's not a professional tool, but I find it quite exciting for the price.
The built-in AWG makes a very stable and nice 10MHz square wave. I like it.
-
I did a few tests with my new Hantek. Of course the model is no longer brand new, but perhaps there have been improvements compared to previous versions?
There were complaints about the noise level.
I can't find anything special about mine.
At 5mV/div I see almost no noise and at 2mv/div I can see that it is alive. ;)
For me it is not a "show-stopper". (See attached image noise5mV.png, noise2mV.png)
The cheap device doesn't fail even at frequencies that are much higher than the bandwidth.
It jitters and fluctuates and the amplitude drops, but it doesn't show any "fantasy frequencies".
See 200Mhz, 250Mhz from TinySA. (attached image 200Mhz.png, 250Mhz.png)
That's impressive!
I also found most of the measurements OK for an oscilloscope.
I have the following results with the tools at my disposal.
1kHz Square Wave:
5V -> 4.96Vpp
2V -> 2.08Vpp
1V -> 1.04Vpp
500mV -> 504mVpp
100mV -> 104mVpp
50mV -> 52mVpp
40mV -> 39mVpp
10mV -> 10mVpp
5mV -> 4.96mVpp (See attached Image 5mV.png, that's with 50Ohm Load Resistor, so half of it)
Signal from Si5351A with descending frequencies. Because the amplitude is not adjustable, I used a 20dB attenuator.
162MHz -> 610mVpp
100MHz -> 620mVpp
80MHz 560mVpp
50MHz -> 570mVpp
30MHz -> 540mVpp
10MHz -> 538mVpp
1MHz -> 516mVpp
The signal of course goes from square wave to sine wave above 50Mhz, but the measurements don't seem shockingly deviating to me.
What I really don't understand is the amplitude measurement with heavy ripple/overshoot.
Actually the Si5351A should output 3.3 volts amplitude.
The measurement with the Hantek shows a heavy overshoot (See attached image VAmp.png)
I don't think that's a problem per-se, but the amplitude (Vamp) should be much lower than the Vpp?
Visually it's correct too, but the specified measurement value (Vamp) isn't correct?
If you subtract 1.2 volts, it would be better, right?
Strangely enough, my even cheaper Zeeweii seems closer to reality. The attached Image shows exactly the same input signal.
(See zeeweii.png)
Is it a (another) bug?
-
hello, me how much to frekvenci the entrance to the osciloscopes, i.e. max the entry rate thank you
what I skated so my oscloscoploscoped to 300Mhz you know no more
im sory google translate
-
hello, me how much to frekvenci the entrance to the osciloscopes, i.e. max the entry rate thank you
what I skated so my oscloscoploscoped to 300Mhz you know no more
Is this question addressed to me?
Unfortunately, I don't understand a word. Could you rephrase the question?
-
Some more measurements.
This time DC
10V -> 10.3V
8V -> 7.98V
5V -> 5.04V
2V -> 2.03V
1V -> 1.02V
0.5V -> 0.506V
0.1V -> 0.999V
0.0543V -> 0.0543V
0.0242V -> 0.0244V
-1V -> -.995V
-5V -> -5V
I think this is acceptable for an oscilloscope.
Make sure you choose a suitable V/Div range.
So far no lockups except when testing overclocking.
Runs stable with 696/384 (28/15)
-
A scope is not a DMM and shouldn't be treated as such.
This tests make no sense.
-
A scope is not a DMM and shouldn't be treated as such.
This tests make no sense.
You're right, but since it has a "DVM" window, it kind of pretends to have that feature.
At least I'm not making a video (https://youtu.be/esE1JL8IScU?t=252) about it. ;)
-
It does work close enough, but within certain limits.
Typical accuracy is 0.2-0.4 divisions.
-
It does work close enough, but within certain limits.
Typical accuracy is 0.2-0.4 divisions.
Yes. I didn't expect better accuracy, I just wanted to make sure it wasn't "light years" off.
But what I still don't understand is the interpretation of amplitude vs peak-to-peak.
As a newbie, I thought that Amplitude = Vpp without overshoot.
But I don't see that in the measurements.
Am I wrong or is it the Hantek?
-
Hi, I'm still trying to understand the Hantek.
is there any difference between acquire type equivalent-time and real- time?
I have not been able to find any difference.
Thanks!
-
is there any difference between acquire type equivalent-time and real- time?
According to the information I've found, this is somewhere between "obsolete" and "not implemented".
I don't really understand why this option is there, but I think it's best to forget about this "feature".
-
The only true fact I know of is they ship a 100MHz or 150MHz proble with each version!
They seem to not have any real difference in HW.
I have checked this with a rise-time measurement and think that there is actually no difference to the 150MHz version.
So far I'm very happy with the purchase.
Of course, not everything is perfect, but you get a lot for your money with the DSO2C10.
Thanks again! :-+
-
I have purchased a DSO02C10 from Banggood some weeks ago. It arrived with the latest software apparently. I was able to upgrade it to 2D15 with the "do_other_update" method. The dso3kb_FW3205_B205.upk did not work for me: it successfully ran, but nothing was changed. The older FW .upk-s did not work either: ran sucessfully and after restart nothing has been changed.
Thank you for the great job of DavidAlfa and all the others made it possible.
God bless you all.
-
FW has nothing to do with the model.
Did you read the FAQ?
Reuploaded broken 2023.08.31 update (It downloaded a 0 byte file).
-
This year, Santa Claus was generous and gave me a DSO2C10 oscilloscope. I have already made a backup and upgrade to 2D15. I was lucky and the generator was present on the pcb. Here are the software versions it came with: Software 1.0.3.0.0(230831.00)
Hardware 003.002.001.000.000.000.000.000 Firmware 3205
On the PCB, the marking DSO2D15_V1.7 2021.1.14
The first thing I noticed is that my power supply is different than I saw on the Internet, it has a different SMPS controller. And in my case it is +7V/-7V and not +8V/-8V as before.
This is my first post on the Forum, but generally speaking, I have been working in electronics for over 30 years. Greetings to everyone.
-
Yes, there's a revised PSU in latter models.
-
The first thing I noticed is that my power supply is different than I saw on the Internet, it has a different SMPS controller. And in my case it is +7V/-7V and not +8V/-8V as before.
I also have one of these PSUs and don't see any worrying noise even at 2mV/div.
A little in normal acquire mode and almost nothing in HR mode. (Nothing connected).
-
I saw somewhere on cxem.net a conversion to a linear power supply. There wasn't much difference. Maybe Hantek improved the quality of the built-in power supply.
Maybe it will heat up less at +/-7V. Anyway, I added heatsinks on the ADC, FPGA and F1C200.
-
Maybe Hantek improved the quality of the built-in power supply.
I think so too, because noise is not an issue with my version.
If it was less noisy at 2mV/div, I would think it had crashed. ;)
In any case, I wouldn't think of trying to improve anything in this area.
-
I have just looked at the DSO2000 specs again.
Overvoltage Category: 300V CAT II
Maximum Input Voltage:300VRMS (10X)
What does this mean: "300VRMS (10X)"?
30VRMS @1X?
That would be less than what the Zeeweii can handle.
Really?
-
Does nobody really know how many volts the Hantek can withstand on the BNC?
I'm not at all concerned about my safety as I don't work with mains, I just want to know whether I'll damage my scope if I have 40 volts on the alligator clip or the 1x probe, for example.
Should I ask in the beginners' forum?
I've read some stuff but I'm not quite sure if I understand it right and I want to be sure.
Somehow there are different aspects and I don't know exactly what the values refer to.
- CAT rating seems to be more for the protection of people.
- The maximum the scope can display (10Vpp x 8 in my case).
- What can the probes withstand? (600Vpk x10 and 200Vpk x1 in my case).
- What interests me: At what voltage on the BNC will my scope be damaged?
While the description of my scope only says this:
Overvoltage Category: 300V CAT II
Maximum Input Voltage:300VRMS (10X)
the manual of another Hantek scope says something similar, but with an addition:
CAT I and CAT II 300VRMS (10×), Installation Category
CAT III 150VRMS (1×)
So the answer could be 150Vrms?
Thank you!
-
Received my new new DSO2C10. Added some components from brocken premium psu:
x and y capacitors right on power socket, ferrites - the ring near switch button and clip-on ferrite on +-7v flat cable. Also added copper shield to the transformer.
2mv high frequency noise level was redused in about 2 times.
-
Added the metal shield to psu
CH1 nothing connected
CH2 PP-150 probe X1
Obviously no needs for lps
-
Looks great!
But do you also have screenshots of "before"? Was there much more noise before?
My unit shows comparable results without any changes.
(attached HR/BW).
-
On your screen CH1 connected ?
I didn't save initial images, just remember visually - the noise of connected CH2 was about two times or more bigger comparing with non connected CH1
-
On your screen CH1 connected ?
I didn't save initial images, just remember visually - the noise of connected CH2 was about two times or more bigger comparing with non connected CH1
The Hantek PP-150 probe is connected to Ch2, but it's not short-circuited like in your case.
When I connect the crocodile clip with the probe tip, I see a few spikes, but not necessarily a larger base noise level.
I'm not experienced enough to judge that.
-
By the way, the Hantek has a statistics mode.
This is perhaps a little more informative, as a screenshot only ever shows a specific moment (-> Avg)
-
Received my new new DSO2C10. Added some components from brocken premium psu:
x and y capacitors right on power socket, ferrites - the ring near switch button and clip-on ferrite on +-7v flat cable. Also added copper shield to the transformer.
2mv high frequency noise level was redused in about 2 times.
How high is the current consumption in +5/+7/-7V lines in the new version of the power supply?
-
Hi all,
i've a question for the forum ..
I running on my pc linux ubuntu 20.04 lts
Exist software linux for Hantek DS02xx oscilloscope?
I've found OpenHantek, but seem not corrtect for this series.
Thanks
Roberto iw2evk
-
Have you tried it?
It says "Supported devices: DSO2xxx Series".
https://github.com/OpenHantek/openhantek (https://github.com/OpenHantek/openhantek)
There is Keysight IO Libraries Suite for Linux, which seems to be the basis for the Hantek applications.
Not sure how useful.
https://www.keysight.com/zz/en/lib/software-detail/computer-software/io-libraries-suite-downloads-2175637.html (https://www.keysight.com/zz/en/lib/software-detail/computer-software/io-libraries-suite-downloads-2175637.html)
-
Mhh..
i try it in the christmas holidays..
Thanks
Roberto
-
Just tried this on my RPi4: https://github.com/phmarek/hantek-dso2000
I was able to control the DSO2000 on the shell and read out values.
It's a start. In any case, you don't have to install the Keysight monster this way.
-
Hi,
seem intersting..
it's a executable pyton file ?
I suppose : connect dso2... to pc (for me linux ubuntu 20.04)
goes to shell
With Super user start file .PY with command required
then recover on pc the file and use in conjunction with spreadsheth (e.g. opencalc) tor use data collected.
Right ?
Roberto
P.s. if you speack italian or french contact me on PM
Thanks
-
With PyVISA I was able to address the Hantek DSO2000 immediately.
First I tried Ni-Visa, but it did not see my Hantek using the "VISA Interactive Control". However, I didn't try it for long.
With the "phmarek / hantek-dso2000" script (which is using PyVISA) you can download the waveform data in different formats. Apparently also for viewing in "gnuplot".
But I am more interested in controlling the scope, e.g. that I don't get a cramp when I want to adjust the signal generator from 10Hz to 10MHz by turning the "Multifunctional Knob".
You can control the device with PyVISA using any of the SCPI commands.
I have converted the SCPI command list from the "DSO2000 SCPI Programmers Manual" PDF into a machine-readable form (JSON), so that you can use it as a basis for an interface.
(-> Attachment. First version, may contain errors).
Btw. you don't need to be "super user", it should be enough to add "99-hantek-dso.rules" to "/etc/udev
/rules.d/".
https://github.com/phmarek/hantek-dso2000/tree/main/etc/udev/rules.d
-
i've installed on linux lubuntu 20.04 via flatpack.
But in 99-hantek-dso.rules seem not appaers my version
-
i've installed on linux lubuntu 20.04 via flatpack.
But in 99-hantek-dso.rules seem not appaers my version
I have absolutely no idea what you're talking about.
-
Hi everyone, I'm new to the forum and I'm waiting for the Hantek DSO2C10 oscilloscope to be delivered to me.
In the meantime I would like to familiarize myself with the tools made available by DavidAlfa (Thanks David).
In particular I would like to start with the "DSO_Builder" utility to extract the scripts to see how they are made.
I would like to point out that I have read the "readme.txt" file but unfortunately it is intended for those who already know cygwin...
Since I use Windows 10 I therefore installed cygwin(64bit) and added the path to cygwin/bin in "environment variables"
to be able to use the Windows dos-prompt.
I tried copying the "dso3kb_backup_builder.upk" file into a folder and launching Run ./extract.sh "dso3kb_MyPackage.upk"
but nothing happens and I get no error messages, but I also can't find the extracted package.
At this point it is not clear to me how to proceed to decrypt and extract the "dso3kb_backup_builder.upk" file.
Could you help me from this point?
Thank you.
-
Since I use Windows 10 I therefore installed cygwin(64bit) and added the path to cygwin/bin in "environment variables" to be able to use the Windows dos-prompt.
I tried copying the "dso3kb_backup_builder.upk" file into a folder and launching Run ./extract.sh "dso3kb_MyPackage.upk"
but nothing happens and I get no error messages
Could you help me from this point?
1. When installing cygwin, you must also install gpg for encryption/decryption, for this enter gnupg in the search line and select all packages with gpg. You could do it also after cygwin installing.
2. After cygwin installed you should have "Cygwin Terminal" icon on your desktop - see the picture.
3. You should run this "Cygwin Terminal" and with "CD" commands go to the directory with the script extract.sh and the upk-file, which shoul be in the same directory.
3. Now in the "Cygwin Terminal" window you should enter
./extract.sh "dso3kb_MyPackage.upk"
and press Enter.
-
I would like to point out that I have read the "readme.txt" file but unfortunately it is intended for those who already know cygwin...
Absolutely not, anyone can do this, cygwin setup will ask which packages to install.
The readme is pretty straightforward:
cygwin: Select Packages -> Not installed -> Search: gnupg -> Change gnupg from "skip" to latest version.
-
@vistorik
Thankyou for the reply,
1) Yes already selected and installed gnupg
2) Yes the icon is present
3) ... I'm not able to change dir !!! |O
@DavidAlfa
Thankyou for all your effort on this scope, Yes I read this readme (I read almost all your drive...).
Now, about change dir in the terminal window see the picture please.
[attach=1]
-
..... this happen with dos prompt of windows
-
Now, about change dir in the terminal window see the picture please.
(Attachment Link)
Use no spaces in the directory name.
I use this slash "/" to change a directory: cd c:/...
But seems it doesn't matter...
xxxxx@sonyvgnfz ~
$ cd c:/DB_BACKUP
xxxxx@sonyvgnfz /cygdrive/c/DB_BACKUP
$ cd c:\DEVELOPER
xxxxx@sonyvgnfz /cygdrive/c/DEVELOPER
$
-
Thanks vistorik,
Now is OK :-+
Was matter of "/" instead of "\" and No-Spaces in folders name.
All worked well in cygwin terminal as you suggested, but no way to go in Windows dos prompt.
Ciao and tankyou again.
-
All worked well in cygwin terminal as you suggested, but no way to go in Windows dos prompt.
Because extract.sh is a sh/bash shell script that is not understood by the Windows shell. It is not a batch (BAT) or command (CMD) script. It has to run in a bash shell, which is provided in this case by Cygwin.
-
@veteran68
Thanks, Ok now I understand.
Bye
-
Now is OK :-+
@carlonb, perhaps this information will be useful for you when working with David's extract.sh/build.sh scripts:
Executing the extract.sh script (from David's Readme.txt file):
./extract.sh "dso3kb_package_name.upk"
The extract.sh script decrypts everything and unpacks it into a created "package_name" folder, which will contain a "package" folder and sometimes an "upend" file.
The "package" folder usually contains 2 files - do_update.sh and Manifest.xml, but may contain additional files and folders with files, for example, for copying files or folders to specific folders in the device file system. The do_update.sh file is an execution script that is executed after the update program copies the "package" folder to the /dso/var/run folder of the device.
The Manifest.xml file contains:
<?xml version="1.0" encoding="utf-8"?>
<manifest factory="yes">
<Vendor name="hantek"/>
<Product name="DSO"/>
<Model name="DSO4000b"/>
<SoftwaveVersion version="1.0"/>
<date value="161203"/>
<cmd>chmod 777 /dso/var/run/package/do_update.sh</cmd>
<cmd>/dso/var/run/package/do_update.sh</cmd>
</manifest>
The "upend" file contains a list of files and folders in the "package" folder.
Executing the build.sh script (from David's Readme.txt file):
./build.sh "package_name"
where [b]"package_name"[/b] is a folder containing a "package" folder and sometimes an "upend" file.
The build.sh script archives, encrypts and creates the file "dso3kb_package_name.upk"
After selecting the upk-file in Utility->Update->Update Firmware of the device, the folder /dso/var/run is created, if it did not exist. If this folder exists, then all its contents are deleted. After this, the selected upk-file is unpacked into this folder and the do_update.sh script from "package" folder is executed.
To create and edit the do_update.sh file under Windows, use the Notepad++ text editor with the Edit->EOL Conversion->Unix (LF) option.
David, I apologize in advance for any possible inaccuracies and delitantism. I'm not a Linux expert.
-
Hi all,
i return on thread abou linux software for controlling DSO2d scopes.
I've tried openhantek, but don't support this models (i've also asked confirm to developpers )
So remain Oscope ..
Someone have a valid linux software ?
I've also ased to Hantek without any resuts..
Many thanks in advance
regards
Roberto
-
Better copy dso_builder to c:\cygwin64\home\your_user.
Then just open the cygwin terminal and do cd dso_builder.
Yeah this will never work under Windows, that's why cygwin is used in first place! Why the mess if we could simply run it in windows? :).
It's a tool that let us run linux stuff without installing a Linux VM or second OS.
Will add this to the readme, but let me say that if you're struggling with this, what you're going to play with won't be any easier!
-
Better copy dso_builder to c:\cygwin64\home\your_user.
Then just open the cygwin terminal and do cd dso_builder.
Yeah this will never work under Windows, that's why cygwin is used in first place! Why the mess if we could simply run it in windows? :).
It's a tool that let us run linux stuff without installing a Linux VM or second OS.
Will add this to the readme, but let me say that if you're struggling with this, what you're going to play with won't be any easier!
Tanks for the hint.
Regarding the readme, it is not necessary to explain why cygwin is used and why it doesn't work with Windows, it would be enough
just indicate that (Windows Environment):
1) Install cygwin with the gnupg package (Select Packages -> Not installed -> Search: gnupg -> Change gnupg from "skip" to latest version).
2) The dso_builder "extract.sh" file must be copied in the directory where the "dso3kb_MyPackage.upk" file to be extracted resides.
3) Open the cygwin terminal and from the $ prompt with CD move to the folder where the "dso3kb_MyPackage.upk" file to extract resides (point 2).
NOTE: The path must not contain spaces and use "\" separators instead of the standard windows "/".
5) From the $ prompt type ./extract.sh "dso3kb_MyPackage.upk" to execute the extraction.
I definitely have no intention of playing with these scripts, this is just curiosity.
I will limit myself to using what you have already prepared only when everything is clear to me. I don't usually operate on things I don't know about.
Thank you for your work and as soon as I receive my DSO I will definitely have more questions (after re-reading everything on the FAQ page again).
-
The readme in every package and the giant FAQ aren't clear enough? :-//
-
@DavidAlfa,
Ohhh, don't worry, you have done a huge job to improve this scope.
It's probably just my problem since (Improving the Hantek) is a new topic for me.
Ciao
-
Today arrived my dso2c10, the strange thing is that it arrived via a courier appointed by Amazon???
I kept an eye on the tracking of the Spanish Aliexpress supplier but it was always in transit between Spain and France.
I was convinced of a serious delay due to the Christmas holidays but unexpectedly it was delivered today
with just one day delay compared to the forecast, total of 15 days from the order. :))
Freshly turned on out of the box:
SW version: 1.0.3.0.0(230327.00)
FW version: 3205
PCB No.: 003.002.001.000.000.000.000.000
I soon made the backup with dso3kb_backup_builder.upk: All OK.
DSOflash:
After connecting the USB cable to the back, turning on the DSO with the FEL button pressed, Windows 10 automatically installed its own driver (without asking me) but the name was "undefined device #1".
In any case I started Zadig and saw that USB ID:1f3a and PID:efe8 were correct, so I installed the driver.
Then I launched read.bat and after about 26 minutes it completed the backup.
Now I have a doubt, do you think that this backup is correct?
I attach the screenshot about it.
If you confirm it I will proceed to find out if the conversion to 2D15 gives me the AWG.
Bye and thanks.
-
Yeah! Don't worry, DsoFlash backup is not really important, just a sort of last resort thing (Because you never know).
My advice is to zip/rar/7zip that file and upload it to your Google drive or something.
2D15 mod won't change anything critical either.
Some boards are missing the generator parts, so if not working just restore dso3kb_CNxxx_Model.upk generated by Backup Builder.
-
AWG components already on board and enabled! ;D
I'm one of (many) lucky people so I've gained 48Euros (Payed 162Euros).
A lot of thanks to DavidAlfa, now it's time to do other mods....
I will keep all of you updated.
Bye
-
Added the following mods to my scope:
Small English font
bmp_to_png
Overclock with DavidAlfa default values CPU=648MHz RAM=336MHz.
All worked very well.
The next mod will be RTC hacking ASAP I will receive the rtc module.
Bye
-
Happy new Year to all people in the forum :)
@DavidAlfa
Hi David, I need an help about the "patcher", so if I only want enable uart ascii decoding without change plot colors
do I set the flag PATCH_COLOR=0 in file patch_values ?
I prefer mantain original colors as they reflect the color ring around the BNC connectors.
Thankyou
Bye
-
Exactly! The first 3 options are true/false switches.
# Restore only, skip patching
RESTORE_ONLY=0
# Enable ASCII decoding
PATCH_UART=1
# Change plot colours
PATCH_COLOR=1
# These are the default colours
# Hex: R G B
CH1_COL="\xFF\xFF\x00"
CH2_COL="\x00\xFF\x00"
FFT_COL="\xFF\x00\xFF"
-
Enabled uart ascii decoding without change plot colors option.
Thankyou davidAlfa
-
@carlonb: Where did you buy it from? I see banggood has good offer on the models right now
-
@carlonb: Where did you buy it from? I see banggood has good offer on the models right now
Hi keenox, I've buy here the 2c10
https://it.aliexpress.com/item/1005006321759112.html?spm=a2g0o.order_list.order_list_main.10.69593696HES1X3&gatewayAdapt=glo2ita (https://it.aliexpress.com/item/1005006321759112.html?spm=a2g0o.order_list.order_list_main.10.69593696HES1X3&gatewayAdapt=glo2ita)
I saw Banggood but you need to add the shipping cost.
-
If you compare prices and have a little patience, you can get it really cheap.
I bought mine in november in a promotion for ~$130 including delivery here (https://www.aliexpress.com/item/1005004685894683.html).
It's definitely worth that much. ;)
-
Hi all,
I'm experimenting with some tools and tested the "dso_builder" by DavidAlfa used to extract or build the UPK files. This tool needs the installation of CYGWIN on windows to work, then I was able to use it.
Now I know that exist also a packet for Windows "Windows UPK build-extract tools.rar" done by andry2pda but I can't find it, is there some one that can address me where i can download it?
Thanks in advance.
-
Now I know that exist also a packet for Windows "Windows UPK build-extract tools.rar" done by andry2pda but I can't find it, is there some one that can address me where i can download it?
Thanks in advance.
I attached a "Windows UPK build-extract tools.zip". andry2pda made bat-files, I testet. They work. But be very careful when using these bat-files, especially when building your own upk-files - you may end up with a non-functioning device. I advice using David's "dso_builder" tools, at least for building upk-files. I've added the english ReadMe file.
-
@ vistorik,
Thankyou for the file.
All this is only for couriosity and only see how these tools in general works, so I will be very careful using it.
Best regards
-
Hi all,
I've update my Hantek Wavefile Viewer. Originally it was Python only and used matplotlib which was admittedly very slow for large files but served to prove the point. I recently found some time to do a rewrite in C++ and instead of building a viewer it outputs the file as a VCD for GTKWave or Sigrok to use. I've successfully used it on 8M captures to analyse a WS2812B LED and also for I2C. Hopefully others will find it useful :)
https://github.com/mattdavis90/hantek-wave-viewer (https://github.com/mattdavis90/hantek-wave-viewer)
-
I've uploaded a wave form with a 2Hz square wave to the AWG of the Hantek.
To my absolute astonishment, a stable square wave is generated at 50Mhz (2x25), which it can also display reasonably well.
I mean it's 50MHz!
Can I trust my eyes? :-/O
(50Ohm Terminator, so should be 1.75Vpp -> 1.48 measured. Not too bad).
-
Who has the mathematical division function for two channels? Probably everyone has this mistake. Hantek has not yet released a fix. The math division function does not work.
-
Who has the mathematical division function for two channels? Probably everyone has this mistake. Hantek has not yet released a fix. The math division function does not work.
Yes, that's one of the things that doesn't work, or I don't know how.
Strangely, it doesn't work with the PC software either, although it seems to calculate/display the math stuff independently of the scope.
Well, not such a serious bug for me.
-
@DavidAlfa: Is there an updated bug list for the latest software/firmware?
You once created one here (https://www.eevblog.com/forum/testgear/new-hantek-dso2x1x-models/msg4031653/?topicseen#msg4031653):
The zoom window problem has been solved right?
» Serious artifacts caused by undersampling, ex. a 10MHz signal shows garbage below 20us/div, you might not notice there's a signal there.
The problem still exists. But I found out that it does show something under certain conditions.
- Acquire mode: PEAK
- Memory depth: 4k
- 2nd channel off
See attachment. No idea if this is helpful.
-
No. I barely use it...
-
The "Multifunctional Knob" really annoys me.
Is it worth the effort to replace it with a
PEC12R-4220F-S0024 Bourns, or does that not change much?
That would be this one (https://www.distrelec.ch/de/inkrementale-drehgeber-24-ppr-5v-100min-sup-sup-horizontale-befestigung-ip40-printstifte-pec12r-series-bourns-pec12r-4220f-s0024/p/30037239?itemList=cart), wouldn't it?
Can anyone who has done this share their experience?
Thank you!
-
Yes, it will improve a lot.
https://www.eevblog.com/forum/testgear/new-hantek-dso2x1x-models/msg4878152/#msg4878152 (https://www.eevblog.com/forum/testgear/new-hantek-dso2x1x-models/msg4878152/#msg4878152)
https://www.eevblog.com/forum/testgear/new-hantek-dso2x1x-models/msg4984594/#msg4984594 (https://www.eevblog.com/forum/testgear/new-hantek-dso2x1x-models/msg4984594/#msg4984594)
https://www.eevblog.com/forum/testgear/new-hantek-dso2x1x-models/msg4985563/#msg4985563 (https://www.eevblog.com/forum/testgear/new-hantek-dso2x1x-models/msg4985563/#msg4985563)
https://www.eevblog.com/forum/testgear/new-hantek-dso2x1x-models/msg4993288/#msg4993288 (https://www.eevblog.com/forum/testgear/new-hantek-dso2x1x-models/msg4993288/#msg4993288)
-
Yes, it will improve a lot.
Thank you!
Do I understand you correctly that you have replaced all the encoders?
The big ones work fine for me and most of the smaller ones are acceptable.
Only V0 is really troublesome. It sometimes just changes direction depending on the rotation speed.
Unfortunately, I need it very often and for many turns, for the frequency of the AWG, FFT center, etc.
Sometimes I start the laptop just to make a setting via SCPI command. :palm:
-
The encoders are cheap, it's the shipping what bulks the costs.
V0 was unusable, trigger level did some woes.... I didn't want to open it again 2 months later, so yeah I replaced them all.
-
Yes, the shipping costs...
The store here with halfway reasonable shipping costs only has PEC12R-4220F-S0024 in stock, i.e. the one with the 24 detents.
You said:
After thinking it twice, I'll avoid the mechanical steps in the small encoders, adjusting certain values require a lot of turning, dealing with a ton of clicking will make the experience even worse!
Since the original big knobs have 12 mechanical steps and are pretty tough to turn, I would like to ask you if the Bourns PEC12R with 24 detents (Which you have installed for the big knobs?) would be acceptable for the V0 too? Or are they too hard to turn?
Thank you!
-
They work well. I put 24 steps everywhere, but didn't put detents on v0 and trigger, would be annoying.
-
They work well. I put 24 steps everywhere, but didn't put detents on v0 and trigger, would be annoying.
So you wouldn't recommend these for the V0.
Well, then I'll wait for a good opportunity for one with "Detent Option 0 = No Detents (https://media.distrelec.com/Web/Downloads/_t/ds/PEC12R_eng_tds.pdf)"
The other stores here charge a flat rate of more than € 20 for shipping alone.
That's too much for a $130 scope.
Maybe I'll need something else soon so that it's worth ordering there.
The price on Aliexpress is also absurd. (https://www.aliexpress.com/item/1005006194450509.html)
Thank you!
-
Just think: Will you enjoy a lot of brrrrrrrr when moving V0 to adjust anything? I don't think so?
Check RS-Online, here in Spain it has the best shipping rates.
-
Just think: Will you enjoy a lot of brrrrrrrr when moving V0 to adjust anything? I don't think so?
Check RS-Online, here in Spain it has the best shipping rates.
Thanks for the tip! I haven't looked at this store yet.
But as far as I can see, they don't have the desired encoder either:
https://ch.rs-online.com/web/c/?searchTerm=PEC12R-4020F-S0024
-
Did you read everything? I had the same problem, the solution is very simple! Just buy the 4225 and cut ~2mm off the shaft.
If not being able to source them, the PEC12R-4225 (12mm shaft) will almost fit, the small caps have a depth of 12mm while the large ones have 11.2mm, it would only require trimming a bit off the shaft end.
-
Did you read everything? I had the same problem, the solution is very simple! Just buy the 4225 and cut ~2mm off the shaft.
Yes, thank you. I had seen it.
I'll probably do it that way, I was just hoping to get the exact model at a reasonable shipping price.
It does exist here at Mouser (https://www.mouser.ch/ProductDetail/Bourns/PEC12R-4020F-S0024?qs=Zq5ylnUbLm43qafljSxq%252Bw%3D%3D) or Digikey (https://www.digikey.ch/de/products/detail/bourns-inc/PEC12R-4020F-S0024/4699271), but the delivery costs are too high.
-
It's just cutting 2mm of the shaft plastic... Why the overthinking?
-
It's just cutting 2mm of the shaft plastic... Why the overthinking?
I'm not in a hurry.
The part is not broken, it works "as designed" by Hantek. ;)
If I can find the exact part for the same shipping costs, then I'd rather take that than cutting and filing a PEC12R-4225.
But it's good to know that this option exists.
I'll look around a bit and then probably order the PEC12R-4025F-S0024.
Btw. is there anything to consider when removing the front cover?
There is only one ribbon cable, right?
Thank you.
-
Hey, everybody.
At some point in the firmware update, my oscilloscope calibration function broke. I have read that this happens due to incorrect FPGA firmware. I have a full dump of the oscilloscope from the time of purchase, I rebuilt it - it shows firmware 220210.00 and Firmware 3204, but when I try to calibrate I get error 511d6. Tried different FPGA versions - some have error 511d1, some have error 511d6.
Help me to understand, please.
-
Try latest 320x or 3102, must be one of them
-
@DavidAlfa I found out that the latest version of dsoflash at the moment from your google disk does not allow to restore correctly my backup, taken by dsoflash a year and a half ago. I have recorded and read with the old version of dsoflash - the results are identical and recorded and read with the google disk version several times and the files are different. I uploaded the files to a temporary folder on google drive so you can analyze them.
-
With no booting between writing and reading? Otherwise that will change the filesystem.
Except small areas in the UBI partitions, all the flash is identical.
(Edit: Because it wasn't erasing the flash due a bug in the code!).
-
Yes, without booting between writing and reading.
-
The UBI partitions CRC is different, this can only be done by the scope itself, DSOFlash can't do this.
If data was bad, like wrogn CRC written, the scope wouldn't boot or work properly!
-
That's the thing, if I write the dump with the old version of dsoflash, the oscilloscope loads, but if I write the dump with the your google disk, the oscilloscope does not load - hangs on the second splash screen. I've checked several times.
-
Looks like my nand memory chip is dead. Because now it is not detected by dsoflash.
-
Strange, but will check it later. Writing to the flash can't kill it in such way!
-
I soldered out the flash drive, it reads in the programmer. The problem is not the flash drive, but a badly soldered contact near the flash drive. Thanks for the advice!
But the problem with dsoflash from your google disk remains. The images filled with it do not help to boot the oscilloscope.
-
That's the thing, if I write the dump with the old version of dsoflash, the oscilloscope loads, but if I write the dump with the your google disk, the oscilloscope does not load - hangs on the second splash screen. I've checked several times.
Sill very rare than the first ~15MB are perfect and then only few bytes of the UBI header change. Will check it, but it's extremely slow and time consuming so I can't tell when it'll be ready.
Actually you'll never really need DSOflash to restore anything, just run lastest platform-tools, then restore fw version, model/serial and AWG calibration from Backup Builder.
Edit:
Read my flash, wrote back, read again, exactly the same md5sum.
-
@DavidAlfa I found out that the latest version of dsoflash at the moment from your google disk does not allow to restore correctly my backup
Well, indeed, your restore.bin didn't match the original when reading back.
Will make more tests...
-
I was able to initialize the SDRAM (Not easy, zero documentation available for FEL |O), it's much larger than the SRAM scratchpad (64MB vs ~4KB), so it will allow much longer queues, removing a lot of overhead.
It made a dramatic speedup to 300KB/s, it only takes 7 minutes now!
-
Yes, dsoflash is now correctly restoring the image on my oscilloscope. Thank you very much.
-
Great! Thanks for reporting.
I added the final touches, including md5 generation and verification, updated the files in Google Drive.
-
Semenich56 from the 4pda forum https://4pda.to/forum/index.php?showtopic=1018961&view=findpost&p=128147933 (https://4pda.to/forum/index.php?showtopic=1018961&view=findpost&p=128147933 forum) received a DSO2C10 with GD5F1GQ4UAYIG flash memory instead of W25N01GVZEIG.
-
No problem, check the supported spi nand memories (https://github.com/xboot/xfel/blob/master/spinand.c#L44-L161), the GD5F1GQ4UAYIG (https://github.com/xboot/xfel/blob/master/spinand.c#L54) is included, everything should work.
-
No problem, check the supported spi nand memories (https://github.com/xboot/xfel/blob/master/spinand.c#L44-L161), the GD5F1GQ4UAYIG (https://github.com/xboot/xfel/blob/master/spinand.c#L54) is included, everything should work.
DavidAlfa, do you think the dsoflash could read this flash?
-
Semenich56 from the 4pda forum could not get a memory (GD5F1GQ4UAYIG) dump https://4pda.to/forum/index.php?showtopic=1018961&view=findpost&p=128198761 (https://4pda.to/forum/index.php?showtopic=1018961&view=findpost&p=128198761) using dsoflash.
-
If the memory wasn't detected properly It would complain showing unsupported memory error.
The scope rebooting is a completely new behavior that I've never seen before!
Are you using latest version? Or did you copy dsoflash to the 4pda thread? Because it's been updated recently to correct a bug not restoring the firmware properly, also got much faster.
I noticed a unnecessary step in the .bat files, since now dsoflash sets the usb to high-speed mode by itself, sunxi-fel is no longer required.
Updated the files. But this would not cause any rebooting, just set the usb mode twice.
-
Hi!
I reactivated my 2D15 after a few months of non-use, and noticed that there was no waveform display - which I thought was due to wrong trigger settings.
Then I noticed that only a few keypresses work (Trig Menu, or CH1 Menu, a few others), but then the UI freezes.
As the USB and SSH console still worked, I could reboot without my local modifications -- same problem. Even dropping the CPU overclocking doesn't help.
Remove the USB cable doesn't help.
dmesg or the serial console have no (error) output when pressing the keys; the UI freezes, but the console keeps working, and the phoenix binary looks like it's running normally, using 98% CPU like always.
As (some) keys work once or twice after reboot, I don't think it's hardware-related - can anyone offer ideas what is wrong?
Thanks!
-
Press load defaults. 98% CPU is normal in this device.
-
As (some) keys work once or twice after reboot, I don't think it's hardware-related - can anyone offer ideas what is wrong?
I don't know if this is helpful, but my unit (overclocked) only crashes in the first few minutes after startup, if at all.
It depends a bit on what is turned on from the last session.
Then when I turn it back on, it runs for hours without interruption.
It looks like it might be "too cold" when it first starts up.
Sounds strange, but I can't explain it any other way.
Maybe it has something to do with the new PSU?
It's best not to do anything to it for 2 minutes after starting, at least with my device. Then it runs reliably.
But that probably has nothing to do with your case.
-
It's probably the RAM, happened to me too. I just leave it stock, OC only the CPU.
You'll get nothing out of that extra 5% OC else that lockups.
-
It's probably the RAM, happened to me too. I just leave it stock, OC only the CPU.
You'll get nothing out of that extra 5% OC else that lockups.
Thank you.
I had MEM_OC_PLL_N=15, now trying with 13
-
I wrote a little script to measure frequency response with the Hantek.
It's my first Python script longer than 3 lines, so..., but maybe someone will find it useful. ;)
Requires pyvisa and gnuplot. I only tested it on Linux. It may also run on other systems with small adjustments.
You can choose between three (cheap) signal generators or add your own:
Hantek internal sg.
Feeltech fy3200: Two channels, phase measurement
Tinysa: Higher bandwidth.
The code is attached and there is a small README.md in the zip.
If anyone would like to try it and has any questions, please ask!
Attention, it is quite slow!
So don't choose too many points for initial tests.
But you can just let it run and don't have to worry about it.
EDIT: BUG FIXED
A new zip is attached.
I mixed up FFR (the time between the first falling edge of source 1 and the first rising edge of source 2) and FRR (the time between the first rising edge of source 1 and the first rising edge of source 2).
The bug was not immediately obvious. :palm:
Pictures:
10db_att_internal.png
10dB Attenuator, internal SG
30M_30P_tinysa.png
30MHz LPF from RF Demo Kit with tinysa
6.5_internal.png
6.5MHz BSF from RF Demo Kit with tinysa
6.5m_40_feeltech4.png
6.5MHz BSF from RF Demo Kit with fy3200, second channel with phase. 40 points.
-
It's probably the RAM, happened to me too. I just leave it stock, OC only the CPU.
You'll get nothing out of that extra 5% OC else that lockups.
Yes, avoiding to overclock the RAM prevents occasional lockups after startup. :-+
-
Hmmm, thanks, but doesn't help -- resp. the key default setup doesn't seem to work at all.
I removed the files from /data/setup (looked promising as last.pho was 0 bytes!) but that didn't help either.
Ah, thanks! /dso/etc/aslf/ is the directory with settings - moving that away and rebooting fixed the DSO!
Merci!
-
Ah, thanks! /dso/etc/aslf/ is the directory with settings - moving that away and rebooting fixed the DSO!
Interesting.
Can you explain what was going on?
What can go so wrong with "settings" that the keys no longer work, as you wrote?
-
I have no idea -- DavidAlfa suggested it!
And it's not that no key worked -- a few of them did, once or twice.
My hunch would have been to look at the FPGA firmware, as that one's responsible for translating key presses to input events.
-
When I tested the script (above), I found that the frequency response with the tinysa from 1M to 150M was not very flat or linear. (-> picture, direct connection, dummy load, no DUT).
10dB gain over the frequency range.
Now I'm wondering if it's the Hantek, the tinysa, the cable or the script.
Unfortunately, I think the Hantek is the culprit, but I would prefer it to be for other reasons.
Does anyone know anything about it?
Can someone check this with a decent signal generator?
It doesn't have to be with the script, a few measurements would be enough (e.g. 1, 10, 50, 100, 150 MHz).
Perhaps someone has already tested this?
Thank you.
-
If I connect the oscilloscope to the PC via USB (SCPI), does it make sense to use an Adum3160 USB Isolator ?
Do the SCPI commands work with it?
E.g. https://www.eevblog.com/forum/reviews/chinese-usb-isolator-test/ (https://www.eevblog.com/forum/reviews/chinese-usb-isolator-test/)
Thank you!
-
New firmware released
https://4pda.to/forum/index.php?showtopic=1018961&view=findpost&p=128715169 (https://4pda.to/forum/index.php?showtopic=1018961&view=findpost&p=128715169)
-
New firmware released
https://4pda.to/forum/index.php?showtopic=1018961&view=findpost&p=128715169 (https://4pda.to/forum/index.php?showtopic=1018961&view=findpost&p=128715169)
Thanks!
But the link there does not work for me:
Ой! Ошибка 404.
Запрашиваемая информация не существует, перемещена или удалена.
Do you have to be a member and logged in?
-
Warning: This update forces the fpga fw update to a new version: FW3208.
I modded it to only apply the software update, preserving the existing fpga FW, so it doesn't cause issues on scopes with FW3000/3102.
Also made a new FW update package.
» 3208_B208 (https://drive.google.com/file/d/18kIhrKJ1aVUrSgCb2NDZCk81qRvw_hlL)
» 2024.02.02 (https://drive.google.com/file/d/1i5pKBkqZWpgScXEeQ69Sm-QarDbt61s5)
» 2024.02.02_fpga_3208 (https://drive.google.com/file/d/19Q1V52XrAPduTIcd-FpF79prOrcXdW32) -> Sets FW3208
-
Thank you for your efforts. :-+
Are there any obvious show-stopper bugs, like the 4k-only bug mentioned in the other thread (https://www.eevblog.com/forum/testgear/hantek-dso2x1x-firmware-updates-and-best-use-practices/msg5324705/#msg5324705)?
Are there any obvious improvements?
Is it a slower debug version, as someone on 4dpa noted (https://4pda.to/forum/index.php?showtopic=1018961&view=findpost&p=128727304)?
Would you recommend updating now or should we wait for the official release from Hantek (https://hantek.com/download?key=fjzl&sid=0&pid=17182&word)?
-
Any idea what the changes are?
-
Any idea what the changes are?
Fixed the mathematical division function, it didn't work before.
-
Meh, that's no sense, the binary size is almost identical to older versions, definitely not a debug build.
In fact it would be the best thing happening, if they ever make that error we could see the original function and variable names (Debug symbols), allowing much easier reverse engineering.
-
I have done the (full) update.
All I can say so far is that it is still running and has not crashed.
EDIT: Math Div seems to work now.
-
I have attached two measurements with the above script that might be (somewhat) interesting in general.
The measurements are made with the internal signal generator from 1MHz to 25MHz sine (50cm coax with 50Ω dummy load).
The first frequency response is without bandwidth limitation.
You can see in the footer that it is approx. -0.75dB at approx. 25MHz (x,y).
The second frequency response is with the internal 20Mhz bandwidth limitation.
You can see in the footer that the -3dB point is reached at approx. 22.5Mhz (x,y).
Please note: y2 and Phase are not relevant here.
-
Hola DavidAlfa! Used the dsoflash v0.34, made a backup, renamed the backup files as "restore.bin" and "restore.md5", then run write.bat and got an error.
-
"File doesn't match t*he Flash size" ???
What the heck?
Try running it several times to see if It always fails in the same way?
Is your system 100% working, not overclocked or anything?
Never seen this!
-
"File doesn't match t*he Flash size" ???
What the heck?
Try running it several times to see if It always fails in the same way?
Is your system 100% working, not overclocked or anything?
Never seen this!
3 times ran, the same result. "What the heck?" This is the text from dsoflash v0.34 main.c:
else{
printf("File doesn't match t*he flash size\r\n");
printf(" Flash: %uBytes, File: %uBytes\r\n", read_bytes, capacity);
terminal_error();
"Is your system 100% working, not overclocked or anything?" nothing of these, windows 10, scope withour overclocking. Reading is OK. Without restore.md5 dsoflash writes the same restore.bin without problem.
-
Is your system 32 or 64bit?
-
Is your system 32 or 64bit?
32 bit
-
Spotted the bug. Try the lastest v0.35 (https://drive.google.com/drive/u/1/folders/13hwsIJd3eGrnHWCLPcQrPQiAb7rRx3W0).
-
Spotted the bug. Try the lastest v0.35 (https://drive.google.com/drive/u/1/folders/13hwsIJd3eGrnHWCLPcQrPQiAb7rRx3W0).
Now it works.
-
Great! :-+
The "F*lash" thing was a plain, giant typo, but wasn't the bug.
When I added md5 check, I loaded the files in the wrong order.
Md5 file is 33 bytes, so the last loaded file size was that.
Of course it didn't match the flash size!
Now I wonder how I missed this. After trying 300 times, maybe I missed the last one!
-
If I connect the oscilloscope to the PC via USB (SCPI), does it make sense to use an Adum3160 USB Isolator ?
Do the SCPI commands work with it?
I'll answer my own question ;-)
I bought one of each of these (https://www.aliexpress.com/item/1005001369085297.html). One for the Hantek and one for the AWG.
Works perfectly on both devices. :)
I can't subjectively notice any speed penalty with SCPI (Attached image shows downloaded wave data).
A little bit of isolation is always a good thing. :-+
-
Great! :-+
The "F*lash" thing was a plain, giant typo, but wasn't the bug.
When I added md5 check, I loaded the files in the wrong order.
Md5 file is 33 bytes, so the last loaded file size was that.
Of course it didn't match the flash size!
Now I wonder how I missed this. After trying 300 times, maybe I missed the last one!
David. This is not an End! Now there is an error without *.md5 file.
-
Opps true. Should be fixed in v0.36, try it out.
I really don't have time to read/flash the scope every time, in fact it's been taking dust for weeks!
-
Opps true. Should be fixed in v0.36, try it out.
I really don't have time to read/flash the scope every time, in fact it's been taking dust for weeks!
Now it writes without problems both without and with *.md5. End?
-
Should be.
-
I can't subjectively notice any speed penalty with SCPI (Attached image shows downloaded wave data).
Well, did you ever try getting a 2 channel 4Msamples dump?
As SCPI runs in ~4kB blocks it's about 2000 round trips - you might see a measurable difference then.
(And that download speed is why I started my patch, see https://github.com/phmarek/hantek-dso2000-quick-fetch (https://github.com/phmarek/hantek-dso2000-quick-fetch).)
-
Well, did you ever try getting a 2 channel 4Msamples dump?
As SCPI runs in ~4kB blocks it's about 2000 round trips - you might see a measurable difference then.
Yes, thank you, you're certainly right.
Like the official Hantek Windows software, I only download 4kpt data to get a somewhat up-to-date image.
Everything else is too slow anyway, with or without the USB-Isolator.
I'm interested in remote control of the device because I prefer to enter values with the keyboard and mouse rather than turning dubious rotary encoders.
I need the image to set triggers, positions and cursors.
It doesn't have to be particularly detailed (deep memory).
Btw. since the update 2024.02.02_fpga_3208 I haven't had a single crash and I use it several times a day.
It's really stable now.
-
I am answering my own question (https://www.eevblog.com/forum/testgear/new-hantek-dso2x1x-models/msg5341133/#msg5341133) (again ;) ).
Apparently there is a big difference with the RF frequency response depending on "which side" of the relay you are on (200mV/div vs. 500mV/div)
I made the measurement above with 200mV/div, this new one below with 500mV/div.
At 500mV/div the frequency response is within 3dB up to 150Mhz.
I didn't find the phenomenon mentioned here, but it is discussed on 4pda (https://4pda-to.translate.goog/forum/index.php?showtopic=1018961&st=3500&_x_tr_sl=auto&_x_tr_tl=en&_x_tr_hl=en&_x_tr_pto=wapp#entry122505010).
So with 200mV/div the amplitudes are usable up to about 60/70MHz afaics.
Of course, this is not a reliable measurement, I don't have the tools for that. But as an impression it will probably be correct.
-
The bandwidth is normally specificied for a -3dB amplitude range.
-
The bandwidth is normally specificied for a -3dB amplitude range.
Yes, maybe the topic is a bit fragmented now.
I originally measured an amplitude increase of +10dB from 1MHz to 150MHz at 200mV/div. That had puzzled me. It is not very good and there are comments on this problem on 4pda.
(https://www.eevblog.com/forum/testgear/new-hantek-dso2x1x-models/?action=dlattach;attach=2022308;image)
At 500mV/div and above the frequency response looks good up to 150MHz (see new measurement one message above yours), i.e. within (-)3dB (Externally amplified signal).
-
Hello,
Today I've opened package with my new DSO2C10 from Aliexpress. The oscilloscope looked undamaged. I turned it on without problems, went through physical button check and successfully made calibration procedure. Then turn off the oscilloscope. After turning it on again the display and all keys are frozen and there are no waveforms. It went completely frozen before I had chance for any backup. The Firmware version was 3205.
I tried recovering with Platform tools, but sadly I get following error:
"
Erasing 'boot' FAILED (remote: 'invalid NAND device')
fastboot: error: Command failed
Failed to erase the memory!
"
Please help!
-
If still booting, try hitting Default Setup several times.
You can also try performing factory reset through a SCPI command.
But this seems a memory failure, claim to the seller.
If you have the knowledge, you can resolder or replace the w25n01gv spi nand.
-
hitting Default Setup doesn't help.
factory reset through a SCPI doesn't help.
I made a claim to the seller, let's see how it goes.
I was able to use successfully use DSOFLASH tool (problem remains). Does it mean that nand itself is ok?
Maybe I should test previous version of platform tools with "cmds.bat"? Is there is any difference vs unified version with restore.bat?
-
I looked through a vent hole and apparently i have a some Gigadevice spi nand chip, not Winbond! what now?
-
That's not a problem!
But you might need a specific platform tools. Send a mail to Hantek?
-
The NAND is GD5F1GQ5UEYIG. Email sent. TY!
-
The NAND is GD5F1GQ5UEYIG. Email sent. TY!
artmau, I could try to solve your problem if you'll send me the backup.bin file that you've got with the dsoflash.
-
Here is the link to the file: https://filetransfer.io/data-package/to1hUCnm#link
I've tried comparing my dump file with the "default(original).bin" from dso2c10 (dated May 25 2021?) on my own but there are a lot of large and small differences... I cannot tell specific reason for the lockup. I do not want to copy/paste fragments randomly. Maybe restoring whole original dump with dsoflash is an idea?
-
Here is the link to the file: https://filetransfer.io/data-package/to1hUCnm#link
I've tried comparing my dump file with the "default(original).bin" from dso2c10 (dated May 25 2021?) on my own but there are a lot of large and small differences... I cannot tell specific reason for the lockup. I do not want to copy/paste fragments randomly. Maybe restoring whole original dump with dsoflash is an idea?
The dump obtained on a W25N01GVZEIG chip will not work on a GD5F1GQ5UEYIG chip. So you need a new platform-tools that works with the GD5F1GQ5UEYIG. After using platform-tools you need to restore the system.inf and the dds_calbration.dat files. These files could be obtained from your dump. I've downloaded the backup.bin file and suppose to test this file with my device with a GD5F1GQ5UEYIG chip connected to the device.
-
Here is the link to the file: https://filetransfer.io/data-package/to1hUCnm#link
artmau, I flashed your dump to my GD5F1GQ5UEYIG chip using dsoflash v.36. The device started normally, nothing freezes, everything works. But your device information is not in the dump. Your dump looks like after using a platform-tools. The system.inf file is not difficult to make if you know the serial number of your device. I extracted the information for the calibration file from your dump and can make a upk-file to restore the system.inf file (need the serial number of your device) and calibration file - this is not a problem. Have you tried turning on the device after using platform-tools?
-
Yes, the scope is still locked up (boots up, but at the end of sequence there the relays do not switch, no waveforms, the keybord is unresponsive, and the all keys are lit). But I used only unified version the Platform Tools (are there some tools missing?) for restoring and failed. I emailed Hantec for version working with GD5F1GQ5UEYIG, still waiting. Btw. are the previous versions of PT still somewhere available?
It may not be apparent, but the serial number is on the bar code sticker on the back of the scope.
It seems, that the command "DDS:CAL:RESUlt" from SCPI codes list extracted by David gives back calibration data, in my case: 0.833235, 5.294509 (offset, amplitude). Is this correct?
Tomorrow morning I'll try to restore with dsoflash v.36 once more.
edit: the command should be "DDS:CAL:RESUlt?"
-
Yes, the scope is still locked up (boots up, but at the end of sequence there the relays do not switch, no waveforms, the keybord is unresponsive, and the all keys are lit). But I used only unified version the Platform Tools (are there some tools missing?) for restoring and failed. I emailed Hantec for version working with GD5F1GQ5UEYIG, still waiting. Btw. are the previous versions of PT still somewhere available?
It may not be apparent, but the serial number is on the bar code sticker on the back of the scope.
It seems, that the command "DDS:CAL:RESUlt" from SCPI codes list extracted by David gives back calibration data, in my case: 0.833235, 5.294509 (offset, amplitude). Is this correct?
Tomorrow morning I'll try to restore with dsoflash v.36 once more.
If your scope is locked up with the same memory contents as mine while my scope is working normally, this can only mean a problem with the hardware, provided that you sent me the dump exactly corresponding to the contents of your scope's memory at the current moment when your scop is locked up.
Calibration data are correct.
You could aloso try to flash the dump from another scope with the GD5F1GQ5UEYIG memory chip (link: https://filetransfer.io/data-package/vemVQ7dA#link (https://filetransfer.io/data-package/vemVQ7dA#link)) using dsoflash v0.36. If your scope is still locked up with this dump then it looks like a hardware problem.
-
Ok, after using the dsoflash v.36 second time with my own dump the oscilloscope is alive! The only change that I can think of is that the first time I reflashed the dump was in state before using "PRIVate:FACTORY:RESET" command.
Using the "PRIVate:FACTORY:RESET" itself did not unlock the scope for me.
edit: At first all looked good, but after the third power cycle the scope got locked again. This time noumerous flashing with dsoflash v.36 with any available dump does not unlock the scope. Some hardware issue after all...
edit2: looks like the unlocking was just a fluke. There is no apparent hardware cause and for now i do not have any more ideas.
to go deeper i would need to know the end of startup sequence. I'll disconnect power for 12 hours like yesterday and try tomorrow morning. Should I update firmware to 3208 if the scope somehow unlocks?
edit3: still no luck. clearly a hardware problem :(
-
Hello all,
first post here so be gentle. I just got the DSO2D15 and i have read the topic from the start.
The following question / idea came to my mind about the slagish UI.
I have seen development boards for the GW2AR-18-144 (that manages all LVDS connectivity) and the F1C200S and what hit me was that the GW2AR-18-144 boards used 50Mhz crystals while F1C200S all used 24Mhz.
Likewise in the datasheets the only option for the F1C200S is 24/25Mhz crystals, which i consider a limitation to the GW2AR-18-144 that seems to be able to work with at least double the reference frequency.
So my idea is, if it is possible to utilize a frequency doubler(phase-locked loop if im correct) to feed the GW2AR-18-144 with 48Mhz from the same 24Mhz crystal (to keep phase between ICs) that feeds them both on the factory hantek implementation? Fun part is that R820 is perfect to interfere with the GW2AR-18-144 Clock path.
Do you think this will solve the slagish UI?
-
Hi,
I was in the market for a hobby level scope and came across this thread. After a lot of reading (especially this thread) I decided on the DSO2C10 and ordered it off Amazon. Two days later and I received the scope today. I'm very pleased, it was fully populated and because of everyone's hard work and documentation I was able to navigate through the upgrade process without any issues. A special thanks to DavidAlfa, you have spent a lot of time and shown more patience than most with this effort and it certainly shows.
Thanks, and have a happy Easter!
BitMaP