pmos69 / dso203_gcc Goto Github PK

Is it possible to put bigger display on the DSO?

Reported by Jerson:

Hi Pedro

Wonder if you can look at this. I tried looking at the code, but can't figure out where it is going wrong.

See this video that shows the GCC version in SCAN mode. Here you will see the waveform is printed in 3 distinct segments that repeat themselves.
http://youtu.be/2zUi5dcPvrQ

This is another video with the AP1_100 version in SCAN mode with buffer set to 360(smallest setting). This problem does not happen here. Sad we don't have the sources for AP1_100
http://youtu.be/VU-VZ2kq62M

Please let me know if I there is a way I can help. Right now, I cannot figure out the whole code, so, not sure where to look. But, I am guessing SYNCHRO and PROCESS are the right places to look.

Regards
Jerson

Reported by g-coder

Strange vertical floating line......bug with SCAN mode...

Hi Pedro,

I have uploaded the 'cleaned up' version 1.18 of the source. I have not been able to work out how to issue a pull request to you.

Peter

Pending check...

Reported by g-coder

Reported by g-coder

http://www.youtube.com/watch?v=CFL4SC5hU0M

Patch for Process.c to correct problem with (A-B) calculation.

The code confuses + and - signs, so the calculation offsets the display incorrectly. The following diff to the Process.c file corrects this.

. # diff Process.c Process_corrected.c
.
. 37c37
. < s16 Posi_412, Posi_41, Posi_42, Posi_4_2, Posi_4F1, Posi_4F2, Posi_4F3, Posi_4F4;
. ---
. > s16 Posi_412, Posi_41_2, Posi_41, Posi_42, Posi_4_2, Posi_4F1, Posi_4F2, Posi_4F3, Posi_4F4;
. 326a327
. > Posi_41_2 = _4_posi - _1_posi + _2_posi;
. 539c540
. < Tmp = Posi_412 + Va - Vb;
. ---
. > Tmp = Posi_41_2 + Va - Vb;

The signal generator is off. Max frequency is 10khz on square wave. PWM can go to higher frequency but the selections are screwed up.

Reported by pbootsma:

When I'm single shot triggering with a smaller time devision than 100uS I have an screen refresh problem.
It gets the trigger and switches to hold, but does not draw the data (90 percent of the times I try).
Sometimes when I just change random things in hold mode like some settings, it shows the data after all.
So it seems like a screen refresh problem.

I also have a dso nano and tested it in parallel. The dso nano had no problem displaying the triggered data.
So no problems with the data itself.

JackTheVendicator said:

Because there's a small fix to apply to the code to correctly refresh on SINGL at that rates. I can give the code to pmos69 if he's interested.

Hi Pedro,

In between you submitting V1.18 and V1.19 I have revised the code base to make it more readable and to use scope (i.e. use of static, const etc).
I am happy to upload it, but I can't work out how to submit the code revision, and I fear that if I am successful in uploading it could create confusion for others as to which version of code that they should use.
Is there some way I can send you the code base privately on this web site?

Cheers,
Peter Phillipa

Reported by jpd

There appears to be a major problem with the way signal scaling is handled. Try measuring a constant DC signal, alter the Y position of the trace, and see the reported amplitude of the signal change.

This currently does not work with the 2.72 / 8M hardware. Some fixes can be found here: http://www.seeedstudio.com/forum/viewtopic.php?f=26&t=5128 due to the change in sector size.

Note that this has been changed to not depend on a modified SYS, but this is controlled by an #ifdef. There are still issues with the FFT functions, not sure why. Perhaps Memory?

In the original firmware, it is not possible to set Y origin lower than visible window.
This is annoying, especially for these use cases:

• voltage always greater than a fixed positive value, for example 4V
• variations of this voltage very inferior to this value
  -> we want to see the waveform of these tiny variations around 4V

Problem: when we zoom the Y axis, the zoom is made near Y=0, so that it is not possible to set the Y origin sufficiently low, as this setting is graphical and the Y-origin cursor cannot go lower than the bottom of the visible window.

Possible solution: when the cursor goes beyond the window's limits, it could go on and the user could trigger its position looking at the displayed Y value (even if the Y cursor is not directly visible).

APP only starts correctly about 1/3 of the times.
The other 2/3, only a black screen appears.