Electronic Engineer Discuss

View: 9115|Reply: 7
Print Prev. thread Next thread

Hantek DSO5202BM: Two bugs, when setting the scan time 80 sec/div

[Copy link]

24

Threads

119

Posts

119

Credits

注册会员

Rank: 2

Credits
119
Jump to specified page
1#
Post time 2017-8-14 11:55:21 | Show the author posts only Reply Awards |Descending |Read mode
Two bugs are revealed, which are manifested when setting the scan time 80 sec / div:
1) On the screen, the oscillogram runs too fast and passes one division in 13 seconds instead of 80 seconds;
2) Неверная информация в окне "Sys Status":



In this window it is said that all 4000 samples stored in memory are displayed on the screen. However, this can not be due to the fact that a period of about 26.6 minutes (20 divisions of 80 seconds each) is placed on the screen, and 33.3 minutes (4K * 0.5 (2 samples per second)) in the memory.

P.S: Sorry my bad english.


Reply

Use magic Report

24

Threads

119

Posts

119

Credits

注册会员

Rank: 2

Credits
119
2#
 Author| Post time 2017-8-14 12:06:01 | Show the author posts only
Edited by Oleg10011001 at 2017-8-14 12:22

Now it turned out that the oscilloscope does not use all available memory under the oscillogram. In 4K memory at a sample rate of 2 samples per second, an oscillogram with a duration of 2000 seconds should fit, but the oscilloscope stores only what is placed on the screen - 1600 seconds. Why is this happening? It makes sense to do a scan of 100 sec / div instead of a scan of 80 sec / div, so that the entire contents of the memory are placed on the screen and the memory is fully used.


24

Threads

119

Posts

119

Credits

注册会员

Rank: 2

Credits
119
3#
 Author| Post time 2017-11-12 18:39:35 | Show the author posts only
The bug described here has not been fixed yet, although it's been almost three months ...

167

Threads

2070

Posts

2232

Credits

版主

Rank: 7Rank: 7Rank: 7

Credits
2232
4#
Post time 2017-11-13 11:06:31 | Show the author posts only
Oleg10011001 replied at 2017-11-12 18:39
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.

167

Threads

2070

Posts

2232

Credits

版主

Rank: 7Rank: 7Rank: 7

Credits
2232
5#
Post time 2017-11-15 08:04:43 | Show the author posts only
Oleg10011001 replied at 2017-11-12 18:39
The bug described here has not been fixed yet, although it's been almost three months ...

Sir, our engineer will modify these bugs.
Because our engineer is busy with other projects. He's going to finish it in a week.
Please wait for a while.

24

Threads

119

Posts

119

Credits

注册会员

Rank: 2

Credits
119
6#
 Author| Post time 2017-11-26 11:57:41 | Show the author posts only
Edited by Oleg10011001 at 2017-11-26 12:00
amy replied at 2017-11-15 08:04
Sir, our engineer will modify these bugs.
Because our engineer is busy with other projects. He's  ...

It's been more than one week and I hope that your engineer is already working on fixing the bugs I've indicated


167

Threads

2070

Posts

2232

Credits

版主

Rank: 7Rank: 7Rank: 7

Credits
2232
7#
Post time 2017-11-27 16:44:35 | Show the author posts only
Oleg10011001 replied at 2017-11-26 11:57
It's been more than one week and I hope that your engineer is already working on fixing the bugs I' ...

Sir, I'm sorry.
Our engineer is very busy, and some bugs are complicated to modify.
Only a small problem has been fixed at the moment. Please give me your email to receive the firmware.
We plan to take some time every week fix one bug.

24

Threads

119

Posts

119

Credits

注册会员

Rank: 2

Credits
119
8#
 Author| Post time 2017-11-27 17:49:54 | Show the author posts only
I sent you a message in PM.
You have to log in before you can reply Login | Register

Points Rules

Dark room|Mobile|Archiver|Electronic Engineer Discuss

2024-4-19 21:10 GMT+8 , Processed in 0.155817 second(s), 20 queries .

Powered by Discuz! X3.2

© 2001-2013 Comsenz Inc.

Quick Reply To Top Return to the list