Hi I joined this forum after reading this great thread. I have also bought the Hantek 6022be for all the reasons already mentioned. The software RichardK is busy with just made it more promising. I still need to understand how to use this DSO properly, as this is all new to me.
I will try to post the noise shown on both my channels when connected to the internal square wave. It interesting to see that channel 2 is nearly clean compared to channel 1.
Both probes were set to X10.
Any comments please?
I just did a similar measurement, the results were the same on the latest binary and stock software... It started out with less noise on CH1, but then a few minutes later the noise evened out between channels (both my version and stock software).
Considering my scope was near a window and it's 2F outside, I think it's safe to say it's thermally related and once the scope warmed up, both channels had pretty much the same noise.
Edit: The keen-eyed observer might notice something in the next build that Rick Law was asking for a few pages back
...
The interesting part with my 6022be running on the Hantek program with both probes grounded; only channel 1 is noisy, channel 2 is shows no significant noise at all, just a blip every 3 to 4 seconds.
...
Any inputs here will be appreciated.
Hello, anyone know bandwidth and div/v relationship for DSO6022BE?
//Time Division
enum THantekTimeDivision
{
//1016 samples
HTTimeDiv48MS_1NS=0, //960, 1, 1
HTTimeDiv48MS_2NS=1, //960, 1, 1
HTTimeDiv48MS_5NS=2, //960, 1, 1
HTTimeDiv48MS_10NS=3, //960, 1, 1
HTTimeDiv48MS_20NS=4, //960, 1, 1
HTTimeDiv48MS_50NS=5, //960, 1, 1
HTTimeDiv48MS_100NS=6, //960, 1, 1
HTTimeDiv48MS_200NS=7, //960, 1, 1
HTTimeDiv48MS_500NS=8, //960, 1, 1
HTTimeDiv48MS_1US=9, //960, 1, 1
HTTimeDiv48MS_2US=10, //960, 1, 1
//130048 samples
HTTimeDiv16MS_5US=11, //800, 1, 1
HTTimeDiv8MS_10US=12, //800, 1, 1
HTTimeDiv4MS_20US=13, //800. 1, 1
HTTimeDiv1MS_50US=14, //500, 1, 1
HTTimeDiv1MS_100US=15, //1000, 1, 1
HTTimeDiv1MS_200US=16, //2000, 1, 1
HTTimeDiv1MS_500US=17, //5000, 1, 1
HTTimeDiv1MS_1MS=18, //10000, 1, 1
HTTimeDiv1MS_2MS=19, //20000, 1, 1
//523264 samples
HTTimeDiv1MS_5MS=20, //50000, 1, 1
HTTimeDiv1MS_10MS=21, //100000, 1, 1
HTTimeDiv1MS_20MS=22, //200000, 1, 1
//1047552 samples
HTTimeDiv1MS_50MS=23, //500000, 1, 1
HTTimeDiv1MS_100MS=24, //1000000, 1, 1
HTTimeDiv500K_200MS=25,//1000000, 1, 1
HTTimeDiv200K_500MS=26,//1000000, 1, 1
HTTimeDiv100K_1S=27, //1000000, 1, 1
HTTimeDiv100K_2S=28, //2000000, 1, 1
HTTimeDiv100K_5S=29, //5000000, 1, 1
HTTimeDiv100K_10S=30, //10000000,1,1
HTTimeDiv100K_20S=31, //20000000,1,1
HTTimeDiv100K_50S=32, //50000000,1,1
HTTimeDiv100K_100S=33, //100000000,1,1
HTTimeDiv100K_200S=34, //200000000,1,1
HTTimeDiv100K_500S=35, //500000000,1,1
HTTimeDiv100K_1000S=36,//1000000000,1,1
HTTimeDiv100K_2000S=37,//2000000000,1,1
HTTimeDiv100K_5000S=38,//-1,1,1
};
Hello, anyone know bandwidth and div/v relationship for DSO6022BE?
HI for everybody,
could you perhaps help me?
I have this equipment, used it with my desktop pc.It was fine.
Then I connected it to my other desktop, I checked the reference signal and it was not 1 kHz, but about 1,9 kHz ( T= 540 microsec).
Where is the problem?
thanks, I ask them, they tell me below data, this is correct?
1. V/div and bandwidth relationship for you reference as below:
Volt/div Bandwidth
20mV, 50mV, 100mV 10MHz
200mV 12MHz
500mV, 1V, 2V, 5V 20MHz
2. No attenuation, cut off voltage -+5V, attenuation 10X, -+50V.
Looks question1, it is not correct, how about with question2?
Let me add some clues to this puzzle. I have similar problem except it swaps Ch occasionally. Often, my Ch1 has much less noise to Ch2. Not quite down to occasional blip, just Ch1 about 1/3 to 2/3 the constant noise of Ch2. Then, occasionally, without probe swapping, without disconnection, I turned it back on to continue prior work (ie:it is connecting back to the same circuit at the same point.), the "noise channel" reverse and Ch2 is 1/3 cleaner than Ch1.
My guess is, it is software artifact but not real. I think packets were dropped. Something unknown affects which channel has lower priority (got processed second? got less package?) and the trace was smoothed out rather than it being less noise.
Rick
The keen-eyed observer might notice something in the next build that Rick Law was asking for a few pages back
Hantek released an update of the software (1.0.4), but i haven't noticed any changes to the GUI. They must have corrected some bugs.
Hantek released an update of the software (1.0.4), but i haven't noticed any changes to the GUI. They must have corrected some bugs.
The HTDisplayDll.dll has been updated, HTMarch.dll has not changed... I'm comparing the two Display dll's disassembled right now to see what has changed and will test the new DLL with the latest binary.
Issue 1:
At certain settings, Ch2 will use Ch1's position. Look at the attached video, you will see the Ch2 trace is on top of Ch1 for a brief time, then disappear, then come back. But looking carefully: Ch2 trace actually returned to where it should be at the bottom part of the screen. It will stay there for a flash then go back to where Ch1 is. The hopping around is non-stop once you get it started.
https://www.youtube.com/watch?v=9l1oj9mdqfQ&feature=youtu.be#
Settings to get that issue going:
Ch1: 110KHz, triangle, +2.76v to -2.76v
Ch2: 110KHz, square, +2.00 to -2.00v
TimeScale 5uS/division
Trigger: Edge, Auto, Ch1, Rising
To Start:
The hopping around does not happen all the time. To get it going, set it to 5uS then switch between FULL Screen and windowed partial screen, resize the screen, full screen again. After a few tries, the hopping around will start.
To Stop:
Switch to 10uS and then back to 5uS a few times, the hopping will stop. (Sometimes it will stop at first switching)
Also:
At 10uS, I can get the hopping going also. At much slower speed, I can't get it to hop around.
Issue 2:
Using the scope's built-in 1KHz reference wave and with the AC coupling turned on, you see the AC-filtered wave jittering up and down a bit too much. I think the noise is affecting the evaluated DC offset. With the offset changing, the trace is moving up and down too much.
If I can suggest, perhaps the evaluated DC offset should be dampen a bit. Perhaps keeping DC offset unchange unless/until the evaluated new DC offset is at least abs(X%) greater than current DC offset and minimum delta of at least 10mV. That should make it rock solid if in fact the noise is the cause of the problem.
Issue 3:
I notice that once paused, changing the time-scale doesn't redraw the trace at the new time-scale. Actually, I found and using time-scale changing to zoom in is easier for me. If you think so as well, perhaps don't waste time on zooming.
Issue 4:
I miss the regular measurement window. I can get the current peak/max/min regardless of where in the trace it would occur. The interactive cursor measurement is very nice, I like it, but it can't do that job.
If I don't have the peak on the visible trace, I can't put the cursor there and I can't measure it. Same for the unknown-position max and min. If I can't put the cursor there (unknown-position), I can't measure it.
The standard measurement window does that. Where ever it may be on the trace, I get the peak/min/max for that duration.
I hope we can keep the interactive cursor along with the old measurement window.