Hantek DSO2000 Master Thread (DSO2C10 DSO2C15 DSO2D10 DSO2D15)

[Aldo22]

Did you overclock already? Because that's a common issue.
Better to leave RAM unmodified, and don't set the CPU over 648MHz.

Yes, I have slightly higher values (see below), but it rarely hangs and I have it under control.
Before switching off, for example, turn the memory depth down to 4k and make sure that not too much is going on (FFT, cursors, zoom etc..), then hardly anything goes wrong at the next start. Otherwise it restarts in 12 seconds. No problem for me.

Thank you.

Code: [Select]

# ------ USER ADJUSTABLE ------
# This example: (24*(28+1)*(0+1))/(0+1) = 696MHz
CPU_OC_PLL_N=28
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

[pcprogrammer]

The board is version 1.7 with date 2021.1.14 and works with formware version 3209.
Yes, the FPGA is marked with Lemontree 2090.

That is the same version and date as on my board. I have never updated my scope and firmware is 3200, so should also work with 3209.

So the question is for those who use the firmware versions 31xx and below, what the FPGA marking is on those boards.

[DavidAlfa]

[pcprogrammer]

So the only difference lies in the date code and the marking below that. Mine says 2105C and N43X03.00

With your flash foot print and the foil it looks a bit like a surgical procedure. 

[Aldo22]

So the only difference lies in the date code and the marking below that. Mine says 2105C and N43X03.00

Mine says: 2208C and N4PX12.00

[pcprogrammer]

So the only difference lies in the date code and the marking below that. Mine says 2105C and N43X03.00

Mine says: 2208C and N4PX12.00

And which firmware version are you using?

[Aldo22]

So the only difference lies in the date code and the marking below that. Mine says 2105C and N43X03.00

Mine says: 2208C and N4PX12.00

And which firmware version are you using?

3209

[cfgnunes]

Better to leave RAM unmodified, and don't set the CPU over 648MHz.

I've just updated the script to set teh RAM to the default 156MHz, RAM is quite sensitive so better leave it alone.

Hi, DavidAlfa! In that case, what do you think about refactoring the script to remove all parts that modify the PLL values of RAM and leaves only CPU? What do you think?

[DavidAlfa]

what do you think about refactoring the script to remove all parts that modify the PLL values of RAM and leaves only CPU?

No, why? Just leave it for anyone to try.
I added more info in the readme file anyway.
The script computes the new frequency and compares it to the default values, skipping when unchanged.
If you OC only the cpu it won't touch the RAM in any way.

Before switching off, for example, turn the memory depth down to 4k and make sure that not too much is going on (FFT, cursors, zoom etc..), then hardly anything goes wrong at the next start. Otherwise it restarts in 12 seconds.

So much mess for +24MHz RAM and +48MHz CPU which makes no real difference in real life.

[cfgnunes]

Hi, guys.
I've created a simple CPU benchmark script. It's good for numerical testing the CPU performance and the overclocking results.
After the script completes, it automatically saves the results in a file named "cpu_benchmark_results.txt", which is stored on the USB flash drive."

My results were:

Without overclocking:

Code: [Select]

CPU Benchmark Results
=====================
 -> Max Number: 2000
 -> Primes Found: 303
 -> Elapsed Time: 51 seconds.

With overclocking (CPU: 672MHz,  MEM: 312MHz):

Code: [Select]

CPU Benchmark Results
=====================
 -> Max Number: 2000
 -> Primes Found: 303
 -> Elapsed Time: 41 seconds.

With overclocking (CPU: 672MHz, MEM: 360MHz):

Code: [Select]

CPU Benchmark Results
=====================
 -> Max Number: 2000
 -> Primes Found: 303
 -> Elapsed Time: 39 seconds.

To run the script:
1. Copy the script to the root of the USB drive and rename it to "do_other_update".
2. Copy dso3kb_do_other_update.upk (from the "Script Launcher" made by DavidAlfa) to the USB drive.
3. Plug the USB drive, go to Utility->Update and run dso3kb_do_other_update.upk

[DavidAlfa]

You have a pi benchmark here, really shows how performance increases linearly with speed, benchmarks here and here.

[MOliver]

I bought a Hantek dso2d15 oscilloscope.
The factory installed system:
Software:1.0.3.0.0(230831.00)
Hardware:003.002.001.000.000.000.000.001
Firmware:3205
What updates should I install that fix known bugs?
Should I use flash backup or Backup Builder to create a backup?

Thanks

[snow06]

Hi DavidAlfa,
I have a DSO2C15, v0 knob, vertical, horizontal button not working, can't update firmware because when I turn the v0 button there is no action. This failur could be happen becaus of softwrare or firmware? Or there is knob pcb failure? any clue?
I made front panel test, attached the result as pic.
Software: 1.0.3.0.0 (230327.00)
Firmware: 3204

[DavidAlfa]

Probably a hardware fault, some users have reported the metal casing of the encoder causing a short, check this:
https://www.eevblog.com/forum/testgear/new-hantek-dso2x1x-models/msg5068099/#msg5068099

The solution is to slighly pry the tabs off with a small screwdriver, can be done without desoldering, pull only so slighly (0.5mm or less) so the tab stops shorting.
Before doing anything, verify if the 1st / 3rd pin is actually shorted to the case.

[snow06]

Repair method for buttons not working

[serafis]

Sorry, bit late to the party as I only just saw this, but if anyone's still interested this is how my scope was set up for the video.



I used an external 2-channel signal generator (Juntek JDS-2900), with CH1 outputting a Sine waveform at 1000Hz and CH2 a 'Sinc' waveform at 1000.1Hz

From the SEC/DIV menu, X-Y mode will plot CH1 (X-axis) against CH2 (Y-Axis), which gives the moving composite waveform in the main window - the shape difference between the two waveforms dictates the composite shape, and the tiny difference between the frequencies dictates the speed of movement. I adjusted the V/Div and position of each channel to size and center the moving composite waveform. I adjusted SEC/DIV to the best vector (rather than dots) resolution - sometimes using Long Memory can improve this further.

Then I pressed the SEC/DIV (ZOOM) knob, which causes the CH1 and CH2 X-T waveforms to be displayed in the upper window, and the moving X-Y composite waveform in the small lower window.

No tricks or pranks, just using the features of the scope.

P.S. If you use X-Y mode on two waveforms of the same frequency and phase, you'll just see a line or some dots. If you change the phase of one of the waveforms to, say, 90 degrees, you'll see a shape. If you cause the phase to change with time (e.g. by a tiny frequency adjustment on one channel) you'll see a moving shape. X-Y mode is most useful for eye patterns (e.g adjusting CD players) or Lissajous curves, but analog scopes are much better than digital scopes for these modes.

[yanivf]

I'm newbie and just got hantek dso2d15 oscilloscope. Aside of basic issues I found like it hanging during saving csv file. I am not sure if the auto-set behaving as expected. I connected both channels to the build-in signal (5vpp @ 1khz) and both are showing fine. When I click on auto-set, I expected it to align the two signals one below the other but instead it changed the scale and caused the signals to overlap. I also noticed that after hitting the auto-set, I need to go back to the horizontal menu and change the type back to rolling as it changes it to yt.

Below is a link to a clip showing what happens when I click auto-set.
https://1drv.ms/v/s!AoIrlVDr4zCPpoh-s4WDcQKd9zdJvw?e=VzJmh2

[Aldo22]

CSV: It's probably not hanging, this can take several minutes.

Auto Set: Yes, strange decision. But actually you only have to adjust the V/div afaics.
Is your firmware up to date?
You can always select “Cancel” to undo the auto set.

YT/Roll: As documented. See manual 2.15.1.

[yanivf]

Thank you Aldo22 for the quick response. My DSO came with 3209.

The video is not really doing justice because I already had the two signals set properly. What I was trying to show is that auto-set doesn't seem to do the work properly if the settings were wrong to start with.

I left the save to CSV for an hour. There is no cancel so had to turn off/on the DSO to get out of it.

The other thing I noticed is that if I set the AWG frequency below 300hz the measurement option shows *** for frequency

[Aldo22]

The video is not really doing justice because I already had the two signals set properly. What I was trying to show is that auto-set doesn't seem to do the work properly if the settings were wrong to start with.

I don't know, it's not like that for me.
Maybe it's confused by noise? Try switching the probes to 1x.

I left the save to CSV for an hour. There is no cancel so had to turn off/on the DSO to get out of it.

With 4k memory depth, it should actually be quick.
Try another USB stick, e.g. with only 2 or 4GB memory. It may also be sufficient to reduce the size of the partition.

The other thing I noticed is that if I set the AWG frequency below 300hz the measurement option shows *** for frequency

It always takes a whole cycle to determine the frequency, except in DVM mode.
In the attached screenshot it is not a full cycle, so it does not show the frequency at the bottom, only in the DVM window.

[dirtmover]

Probably a hardware fault, some users have reported the metal casing of the encoder causing a short, check this:
https://www.eevblog.com/forum/testgear/new-hantek-dso2x1x-models/msg5068099/#msg5068099

The solution is to slighly pry the tabs off with a small screwdriver, can be done without desoldering, pull only so slighly (0.5mm or less) so the tab stops shorting.
Before doing anything, verify if the 1st / 3rd pin is actually shorted to the case.

(Attachment Link)

(Attachment Link)

Turned my scope on today and none of the knobs were working.

Turns out I have a knob problem with ch2 volts/div. I found if I apply a small amount of pressure to the right hand side of the knob and release everything starts to work fine. If I then apply a small amount of pressure to the left hand side of the knob then release, all the knobs stop working! Must be a short on that knob.