Hantek DSO5202BM: The problem with using cursors Track mode.

Oleg10011001

Attention! He discovered that the bug with the use cursors measure voltage mode cursor measurements are not fully fixed. For example, here are some screenshots follow the cursor on the rising edge of the pulse:

amy

Dir sir,
Please inform how to create.
We will test this problem.

Oleg10011001

You can not reproduce the error using the information from the screenshots? Weird ... On my oscilloscope, the error occurs on a regular basis. Here are the steps:
1) Turn on the oscilloscope. The probe is only connected to the first channel;
2) Install the probe at the desired point the test circuit and press "AUTO" button. In this case, I connect the probe to the sixth contact CH340G chip on the Arduino Uno board, that is, look, that is transmitted via USB between your PC and this board;
3) After the completion of the function "AUTO" I see periodically transmitted pulse packets 1Khz frequency. Scan time is automatically set to 400us (although sometimes for some reason placed on 2ms):



4) I need to see momentum in detail in this I change the scan time to 200ns, have positioned the burst on the screen so that it fills most of the screen and stop the capture by clicking "SINGLE SEQ" button. Next I will work with the stored (4K) waveform:



5) After clicking the "HORIZ MENU" button and set the active window to set "Window Ctrl" turn to work with two windows mode;
6) Make active top window, select it in the desired position on the waveform, and then making an active lower window start it right to increase the portion of the waveform reaching eventually to sweep time 2ns. By the way, today noted that since the sweep time 20ns for the bottom window displays the waveform there is becoming less available working area of the screen width and going up to 2ns have scan on the screen as follows:



7) Next, by clicking "CURSOR" turns on cursor measurement type "TRACK".
8) Press the V0 knob positions the cursor "S" in the center of the bottom of the window that is active. The result is the following:



9) A little V0 rotate the knob back and forth and get the following:





10) Move the cursor to "E" in the bottom window on what does not affect:



That's all. As I said, this problem occurs continually. Reset the oscilloscope settings to default problem not solved.

amy

Dir sir,
We are modifying the BUG. Please wait for a while.

amy

Dear sir,
Please check your email.

Oleg10011001

One can see that there was an attempt to correct the error in the measured voltage cursors in "Track" mode. Unfortunately, this error is still not fixed, although it has become less:







Moreover, a new error has been added in the latest version of the firmware; in previous versions of the firmware, this error was absent. When using the oscilloscope in a mode with two windows in the upper window (when it is active) began to work badly cursors to measure the voltage in "Track" mode. Once the cursor "S" and / or "E" leave that part of the waveform, which is projected in the lower window, so immediately stops working associated cursor measuring voltage:



Other alleged errors are still relevant.

amy

Please change the display type to dots toview.

When the basetime of the minor window is verysmall, the quantity of the display dots is very few.

There is a distance without data between twopoints.

When the cursor is between two points, thereis no real point to track, so the cursor cannot track accurately.

  

amy

About the new bug, we are modifying.
Later we will send the firmware to your mailbox.

Oleg10011001

Now I understand. Thanks for the explanation! I want to note that really is that cursors measure the time located between DOTS and constantly and I do not understand why it made possible? Would not it be more correct to move the cursors only by dots? In addition, if the waveform is drawn in Vectors mode, why not move the cursors to measure voltage on the point vectors that are known? I would also add that I have previously raised the issue that need the ability to adjust the accuracy / speed of moving cursors measure time. At that time I did not have coarse displacement mode because the cursor moves very slowly. This time, I note that I do not have pixel-precise cursor movement. Still, when 2ns scan on the waveform signal digitized at a frequency 1Gs / sec cursor step 5 ns - it's too rough, you need to be able to take a step 1ns move the cursor, just you can move the cursor to any dots on the screen.. I certainly can move the waveform so that was one of the cursors to the desired place, but for the second cursor, this method is not suitable ...

P.S: I would also like to know whether it is possible here to ask not only fix bugs or modify something, but also add new capabilities previously missing? For example, I would like to have trigger catch pulses which differ from the specified values are not only the width (duration), and height (voltage)...

amy

Dear sir,
Please check your email for the new firmware.

If you want to magnify to 2ns to view the waveform, please use single window mode.
In single window mode, the min. cursor step and basetime step are 50ps also, now you can view use the cursor to test every point.
In double window mode, the min base time of the major window is 200ns(constant), the cursor traces the points in the major window.
Now, the min. cursor step and basetime step are 5ns also. In minor window, the view just be an enlargement of the major window view.