Electronic Engineer Discuss

Title: Hantek DSO5202BM: A bug that appears when you scroll the waveform horizontally [Print this page]

Author: Oleg10011001    Time: 2017-8-6 03:05
Title: Hantek DSO5202BM: A bug that appears when you scroll the waveform horizontally
When the oscillogram is scrolled horizontally (no matter in which direction), the oscillogram is erroneously shifted relative to the triggering point of the trigger. The bug appears only when the "Time / Div" setting is set to "Fine" in the "HORIZ MENU" and then the time sweep is changed (in my case, I reduced the time from 8 ns to 5.04 ns). For example, here is a screenshot of the screen made before I started scrolling horizontally with "HORIZONTAL POSITION":




After scrolling the oscillogram horizontally, the oscillogram shifts relative to the triggering point, which can be seen on the following two screenshots:








Author: Oleg10011001    Time: 2017-11-12 18:40
The bug described here has not been fixed yet, although it's been almost three months ...

Author: amy    Time: 2017-11-13 11:05
Oleg10011001 replied at 2017-11-12 18:40
The bug described here has not been fixed yet, although it's been almost three months ...

Sir, sorry, I missed your question.
I will reply you tomorrow.

Author: Oleg10011001    Time: 2019-8-14 02:42
Edited by Oleg10011001 at 2019-8-14 03:01
amy replied at 2017-11-13 11:05
Sir, sorry, I missed your question.
I will reply you tomorrow.

amy, a lot of time has already passed, and you still have not fixed the problem indicated in this thread. More than two years have passed... Do I have to wait long?


Author: amy    Time: 2019-8-14 09:31
The problem was solved long ago.
Download the firmware on this link to update:
http://hantek.com/en/ProductDetail_3_55.html

Author: Oleg10011001    Time: 2019-8-14 17:53
Edited by Oleg10011001 at 2019-8-14 18:17

amy, no, this bug has not yet been fixed. I checked it out. In addition, during the check, I found another bug. When changing the time scan in the direction of 20ns -> 8ns -> 4ns -> 2ns, there are no errors. But if you start to change the time scan in the other direction, you get the following: 2ns -> 8ns -> ... That is, there is no 4ns value.


Author: amy    Time: 2019-8-15 09:09
I reproduce this problem. But I couldn't reproduce the last problem. Please describe the procedure.

Author: Oleg10011001    Time: 2019-8-15 15:28
Just turn on the oscilloscope. Then set the time scan to 2ns. After that, try increasing this value to 4ns. I have at this step stably instead of 4 ns the value is set to 8 ns...

Author: amy    Time: 2019-8-16 08:51
Oleg10011001 replied at 2019-8-15 15:28
Just turn on the oscilloscope. Then set the time scan to 2ns. After that, try increasing this value  ...

Yes, I have reproduced this problem.
You said the last bug has not beed fixed. But I couldn't reproduce. Please describe the procedure.


Author: JIN64    Time: 2019-8-16 13:19
Oleg10011001 replied at 2019-8-15 15:28
Just turn on the oscilloscope. Then set the time scan to 2ns. After that, try increasing this value  ...

Наверное лучше им отправить видео.

Author: Oleg10011001    Time: 2019-8-16 17:54
Edited by Oleg10011001 at 2019-8-16 21:32

amy, I don’t understand why you can’t reproduce this bug ... I get it stably if I follow the instructions that I gave in my first message in this thread. Here is a short video demonstrating this bug: https://youtu.be/7etwLMoFtYY


Author: amy    Time: 2019-8-17 16:54
Ok, I have reproduced.
The engineer will update the firmware next week.

Author: Oleg10011001    Time: 2019-8-23 22:16
The work week is over...

Author: amy    Time: 2019-8-31 08:39
Please use this to update.
[attach]3133[/attach]


Author: Oleg10011001    Time: 2019-9-1 04:02
OK, it seems the bug is fixed Thank you for your help!





Welcome to Electronic Engineer Discuss (https://www.eediscuss.com/) Powered by Discuz! X3.2