Hantek DSO5202BM: A question on the use of a memory oscilloscope.

Oleg10011001 · Post time 2017-1-8 10:55:21

Edited by Oleg10011001 at 2017-1-8 14:28

I noticed that when using a single channel and installation scan time in the range of 2 ns ... 800us oscilloscope memorizes only 1.6M dots although the available memory is enough for 2M dots. Why is this happening? Why not use 20% of the memory?

P.S: Sorry my bad english.

Oleg10011001 · Post time 2017-1-8 13:35:46

Edited by Oleg10011001 at 2017-1-8 15:23

And another point on which I would like to draw your attention more specifically requested. When the oscilloscope operates as a single-window mode, press on the "SEC / DIV" has no function. Please do so by clicking on the "SEC / DIV" sets the minimum sweep time (2ns). Also I would like to see by clicking on "Vertical position" of both channels and the "Horizontal position" could move the corresponding markers not only in the center of the screen, but also on the two edges of the screen (on the extreme line). That is, when you click on these controls appropriate markers on the line to move to the specified position. Similar changes would like to see in the management of the cursor by moving the cursor in the measurement mode. This would make the work more comfortable with an oscilloscope.

Oleg10011001 · Post time 2017-1-8 21:46:50

Why is this happening? Why not use 20% of the memory?

Maybe it's just a bug. The fact that I have noticed that the length of the signal recorded in the memory can vary depending on what type of scan time to deliver at its dimension. Here for example is the same signal for different values of the sweep time:

amy · Post time 2017-1-17 14:37:23

Oleg10011001 replied at 2017-1-8 13:35
And another point on which I would like to draw your attention more specifically requested. When the ...

Sir, the "Horizontal position" button only can move the corresponding markers to the center of the screen, can't move the markers to other position.
You can turn the button to move the markers to any position.

amy · Post time 2017-1-17 15:16:24

Oleg10011001 replied at 2017-1-8 21:46
Maybe it's just a bug. The fact that I have noticed that the length of the signal recorded in the m ...

Did you stop at different basetime or at the same basetime?

Oleg10011001 · Post time 2017-1-17 21:07:06

Edited by Oleg10011001 at 2017-1-17 21:09

Did you stop at different basetime or at the same basetime?

Capturing waveform was stopped when it was set sweep time 2ns and used memory depth of 2M. The screenshots shown above shows the same waveform stored in the memory.

amy · Post time 2017-1-18 14:50:50

Ok, we will modify this bug, please wait for a while.