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

You are absolutely right counterpart. Software is great, but I want some finishing and supplements.

Also not working properly vertical scanning ranges of volts / div.

I think you have the wrong sys file loaded to get that bug. Check OP and use the linked sys25116

Hello,

I want to ask some of the authors of the software to show me where exactly are configured ranges Horizontal scanning: 1S …0,1uS.

The idea is to add a range of 0.05uS.

Thanks in advance!



P.S: Time for v1.30!

First off, thanks to pmos and all the devs that have turned the Quad into something much more than when I first got it a year and a half ago.



I was wondering if it would be possible get multiple binaries for this community edition, packaged for alternate slots? With several great firmwares available, it would be nice to be able organize them into different slots without having to reflash to run a different firmware.



I built a hex 1.29 locally compiled for slot two, but it crashes (freezes at loadup screen and beeps constantly). The binary I downloaded for 1.29 run’s fine(in slot one). I used the 2013q1 arm-eabi-none toolchain from Launchpad, but I manually “installed”(unzipped) it to a temp folder and hacked up the built script and environment to avoid interfering with some other gcc toolchains I have installed. So it’s entirely possible I goofed it up somewhere. From reading some of the other forums, I’m a little worried I’m going to hose my bootloader with a bad build.



Thanks again,



Jon

Can anyone publish a “C” code SYS25116, because I find only HEX file.



Thanks in advance!

Here’s the source code for Marco Sinati’s SYS25116.

Be aware that it wasn’t made for compiling with GCC.

pmos69

On line 137 of Menu.c an error instead:

{(char *) CH_D_STR, (u16 *) Y_INV +3, 14-1, CIRC, 188, 228, 1, UPDAT}, / / ​​Track sourtse

should be:

{(char *) CH_D_STR, (u16 *) Y_INV +3, 15-1, CIRC, 188, 228 1, UPDAT}, / / ​​Track sourtse

to exit a menu: SPEC_B.

If you have the time and opportunity point me where to look for ranges of horizontal scanning 1S … 0.1 uS. The idea is to add a range of 0.05uS and automatic switching between the range of the horizontal sweep.

I would like to get involved in improving the software.

Thanks in advance!

I can not add files in the forum!!!

Publish one of my version of the software, without claim to any copyrights, because I have not changed anything substantial changes:

1. Removed bug for displaying SPEC_B.
   
2. Changed the colors of the FFT, I do not know whether the most appropriate, but I personally do not red fuzzy.
   
3. In Trig menu is added FulAU which currently doubles AUTO menu, but the idea is to osushtestvi automatically switching range of the horizontal sweep.
   
   If you like, use it!
   
   
   
   P.S: Use with: SYS25116
   
   [size=150]I want to emphasize that this is v1, 29, Pedro Simoes whit small cosmetic changes![/size]

I have two questions to [size=150]pmos69[/size]:

1. SYS1.6, who publish the same as it is SYS25116.
   
2. With what compiler to work after changes in the SYS file.
   
   
   
   I apologize in advance that you are wasting time and Thanks!

1. Sorry, didn’t understand the question.
   
2. IAR

SYS1.6 and SYS25116 are the same.

This versione derive from the original SYS1.50 modified, the version 1.6 is the the sixth release, the correct name was SYS15116 but when i have renamed it, i’m wrong!!



I’m sorry!

SYS1.6 gives me a lot of errors when compiling with IAR. Missing libraries, errors in the code and can not generate HEX file.

I have not ever worked with this compiler.

pmos69 or some other, can I send changed files, and you can compile a new SYS25116.

Thank you.

Anybody compiled this SIS file and publish it.

There’s a long time no one posts in this forum. SYS 1.61 site (pmos69 . net) has lost its domain, how can I get it now?

Yes, those links don’t seem to work now. They were working fairly recently.



I think you can also get the files from here



<LINK_TEXT text=“https://github.com/gabonator/DS203/tree … ns/pmos129”>https://github.com/gabonator/DS203/tree/master/Resources/Applications/pmos129</LINK_TEXT>

Is it just me or does the display not refresh properly when using 200uS/div. or 500uS/div. horizontal sweep? The very left-most column of pixels in the waveform display jumps all over the place with the input signal, but the rest of the waveform does not update as well. If I set “TrOFF” and give up triggering it seems to update fine. Is this a problem with the way triggering is performed? No combination of trigger settings alleviate the issue other than disabling it in those timescales.



Has anyone else experienced this issue? Is there a work-around?

I don’t have a problem with refresh / trigger on those timebases (or any others).



So if you just do a loopback from the internal sig-gen to channel A on Auto trig 1/2 level then you don’t get a refreshing display which changes with sig-gen frequency and waveform?



What versions firmware are you running?

I am on HW 2.7 with SYS 1.50 v1.6 and GCC APP v1.29. I have not flashed my FPGA as it came stock with 2.61 (All the HW 2.7s do).



You are absolutely right in your description of the problem. Though that is not the only time I get refresh issues, it is certainly the most pronounced. 200uS time-base is completely unusable for me. This is not the case with the stock SYS/APP or with the stock SYS and Gabonator’s APP.