DSO203 GCC APP - Community Edition (2.51+SmTech1.8+Fixes)

End-Of-Life Products & Services DSO
#91

Hello Pedro



The sys was a problem. Updating from Marcos binary corrected the problem.



Now, my setup has

HW 2.60

SYS 1.50 SmTech 1.6



Thanks very much



Regards

Jerson

#92

Here the modified files.

In the sources i have deleted the “interlace mode” because it’s never used in the software. In this mode we have more free memory.



Thanks

Marco

#93

Here are the code modifications necessary to fix the trigger (they’re all on Process.c):

At the start of the file, declare:
</s>u8 HoldOnNext=0;<e>

In Synchro() change
[code] if((_Status == RUN)&&(__Get(FIFO_FULL)!=0))
{ // FIFO is full
__Set(FIFO_CLR, W_PTR); // FIFO write pointer reset
Wait_Cnt = Wait[_T_base];
JumpCnt =0;

if(_Mode == SGL)

{
_Status = HOLD; // one finished, enter the pause
_State.Flag |= UPDAT;
}
}[/code]
to
[code] if(HoldOnNext==1) {
_State.Value = HOLD; // one finished, enter the pause
_State.Flag |= UPDAT;
HoldOnNext=0;
return;
}

if((_Status == RUN)&&(__Get(FIFO_FULL)!=0)){ // FIFO is full
if((_Mode != SGL)) {
__Set(FIFO_CLR, W_PTR); // FIFO write pointer reset
}
Wait_Cnt = Wait[_T_base];
JumpCnt =0;
if(_Mode == SGL){
HoldOnNext=1;
}
}
[/code]
That should be all :smiley:

#94

Thanks!

#95

This is great.

A lot of contributions already from a lot of people.

It’s just a pitty I’m away and buried in work, but I’ll merge everything as soon as physically possible.



Thanks everybody.

#96

Hi Pedro & Jack



I have used pmos69_app_v119 and merged the changes.



Following files have been modified and you can find the mods by searching for ‘Jerson’ in the code



E:\Download\DSO203\pmos69_app\App\src\Menu.c

179: {(char*)NumStr, (u16*)V_COLOR, 10-1, NUM2, 342, 152, 5, UPDAT}, // Class (Jerson was 11-1 now 10-1)

536: if(Title[i][j].Value >= Title[i][j].Limit){ // Jerson (was ==10, made >=Limit)

E:\Download\DSO203\pmos69_app\App\src\Function.c

390: /* removed by Jerson. Was causing selections to jump around (bounce) */



Attached file has the changes.



Thanks for helping me get into this Marco, Pedro, Gabriel and of course the original author Bure



Regards

#97

[code]v1.20

  • Improvements in the FFT (Marco Sinatti):
    • The FFT function and FFT source can be selected from the track4 menù, it’s possible to select the ch A or ch B.
      They are displayed as track4 math results.
    • Changed some colors
    • Changed the FFT meter positions, the max meter moves along the peak position
  • Trigger fixes (JackTheVendicator)
  • Fixed volume control + selection bounce (Jerson)[/code]

Thanks everybody



Latest download: https://github.com/pmos69/dso203_gcc/zipball/master

#98

As usual, I borked something up in the fix :oops: (I haven’t worked on it for months).

To correct it, remove line 579 (u8 HoldOnNext=0;) and place at the head of the file instead (before line 14 is fine). Then, go to line 353 and change from
</s>if((_T_base > 15)&&(_Status == RUN)) DataBuf[i] = __Read_FIFO(); // read into the 32-bit FIFO data reading pointer +1<e>
to
</s>if(((_T_base > 15)||(_Mode == SGL))&&(_Status == RUN)) DataBuf[i] = __Read_FIFO(); // read into the 32-bit FIFO data reading pointer +1<e>
(this adds a check that updates the screen in SGL mode just after the scope goes in HOLD status).



–EDIT–

FFT seems to work correctly even in single shot mode.

#99

done:

[code]v1.21

  • SGL Trigger fix (JackTheVendicator)[/code]
#100

First, thanks for your great work. Now DSO X is really usable. :slight_smile:

But there is a little problem in my dso.

I replaced the switcher regulator to a LDO, now most of the noise is reduced,but the display of RMS is not correct.



Maybe is a bug. can you check it? I’m good at hardware but not arm :wink:

Thanks

#101

@pmos69

I’ve added your firmware in the wiki <LINK_TEXT text=“http://www.seeedstudio.com/wiki/DSO_Qua … plications”>http://www.seeedstudio.com/wiki/DSO_Quad#User_applications</LINK_TEXT>

#102

v1.21 ∆T on 500ms and 1s bug







#103

∆V bug







































#104

I couldn’t reproduce the issue.





Are you using the correct sys and fpga?

#105

Yes, I’m using sys1.6 from macrosin and fpga 2.61.

In fact, this problem maybe is something about the hardware, because I find not like the schma, the v- is -2.8v but not -3v.

Now I have a v+ of 3v, maybe is the difference between V+ and v- caused this problem.



But after the calibration, other values are corrected. Is the RMS has a different way of calculation?

#106

RMS is always positive, by definition.

#107

Thanks for this firmware, feels better than the stock firmware. I just installed v1.21, after playing around with some 1Mhz spi signal (<LINK_TEXT text=“http://neophob.com/2012/03/lpd6803-spi- … -distance/”>http://neophob.com/2012/03/lpd6803-spi-and-long-distance/</LINK_TEXT>) I discovered some issues:
[list]

  • [*]I measured for about 5minutes on CHA and CHB. then I disconnected cables, the wave form on the display just freeze (the menus were working fine). I had to restart the quad. Edit: had this error again, btw mode is RUN and not HOLD
  • [*]I confirm the delta voltage bug
  • [*]on the stock firmware a 1mhz spi signal looks like this: http://neophob.com/wp-content/uploads/2012/03/spi-1mhz-lpd6803-arduino-clockonly.png. now if I look at the same signal with your firmware it looks like the stock firmware at the 5uS time value. however if i'm using a time value of 10mS the signal starts oscillating, see the attached screenshot. this was NOT visible on the stock firmware, I *guess* thats a bug?
  • [*]the firmware suffer (like the stock firmware) of a non existing blue color channel if a screenshot is saved.
    • [/list] [*]signal generator, there is no difference for the rect/sin/saw generator between 20khz and 50khz
    thanks again for you time and effort!

    cheers
    michu


    ---
    https://www.facebook.com/PixelInvaders
    #108

    Thanks for the report, but please check your SYS and FPGA versions.

    I say this because, as you can see from the screenshots I posted, the app actually has no problems with the blue color channel.

    #109

    thanks pmos69, just to be sure I should update to the SYS version from marco (<LINK_TEXT text=“https://sites.google.com/site/marcosina … ronica/dso”>https://sites.google.com/site/marcosinatti/elettronica/dso</LINK_TEXT>), currently v1.8? that would be SYS25116.hex, correct (my quad use the hardware model v2.6)? there is also an fpga222 file inside, but my quad has FPGA261 preinstalled, so I do nou update fgpa files?



    thanks



    Edit: now I’m confused… the official SYS151 was released on the 2011-11-15 by seeed, however the SYS25116.hex file has a timestamp of 2011-11-12, so 3 days older… and to make thing even more complicated I found this ftp site <LINK_TEXT text=“ftp://shodtech.net/DSO_Quad/marcosin_ch … nary_V1.7/”>ftp://shodtech.net/DSO_Quad/marcosin_changes/binary_V1.7/</LINK_TEXT>, there is the same SYSFile (compared by content) but with another timestamp…



    just an idea, i would make things alot easier for newbies (like me) you add the needed sys/fgpa files or reference to them in the text file.



    Edit: I just reread the readme file, you write:

    Tested with:

    • SYS 1.50 1.6 from Marco Sinatti
    • FPGA 2.61
    • HW 2.6



      I reinstalled my fpga v2.61 file(from seeed), the sysfile from marco sinatti (SYS25116.hex) and DSO203 GCC v1.21. see attached screenshot to see my start screen. my screenshot still misses the blue color… any hints whats wrong?
    #110

    I just want to let know that v1.21 fixes triggering. Nice release. Thanks!