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

Moderators: lily.li, violet, jeremy882, crail.lyu969

alienrelics
Pre-kindergarten
Pre-kindergarten
Posts: 13
Joined: Wed Feb 05, 2014 12:05 am

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

Post by alienrelics » Sat Feb 07, 2015 11:15 am

Will this work with hardware version 2.52?

Thank you for making this a truly useful device.

Wildcat
Elementary-1
Elementary-1
Posts: 166
Joined: Fri Jun 22, 2012 1:29 pm
Are you a staff member of seeedstudio?: no
Which products/projects are your favorite?: DSO Quad

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

Post by Wildcat » Sat Feb 07, 2015 2:45 pm

Will this work with hardware version 2.52?
To my knowledge, hardware versions went from 2.2 to 2.6. Perhaps you mean
a device that came with app version 2.52? Such a device would have hardware
V2.6, SYS V1.51 and FPGA V2.61. These programs should work fine on that
version or anything later. Keep in mind that the Alterbios plug-in should be installed
on any device with a 2MB drive (prior to hardware V2.72)
See http://www.seeedstudio.com/wiki/DSO_Qua ... g_Firmware for more info
on hardware/system versions.

alienrelics
Pre-kindergarten
Pre-kindergarten
Posts: 13
Joined: Wed Feb 05, 2014 12:05 am

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

Post by alienrelics » Sun Feb 08, 2015 5:04 am

Oops, I meant HW 2.72.

fflan
Pre-kindergarten
Pre-kindergarten
Posts: 10
Joined: Tue Dec 03, 2013 12:21 am

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

Post by fflan » Wed Feb 11, 2015 4:28 pm

Hi Wildcat,
Do I need to save something to avoid a recalibration ?
Sorry, I don't remember if after an upgrade we have to recalibrate.
Thank you

Wildcat
Elementary-1
Elementary-1
Posts: 166
Joined: Fri Jun 22, 2012 1:29 pm
Are you a staff member of seeedstudio?: no
Which products/projects are your favorite?: DSO Quad

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

Post by Wildcat » Thu Feb 12, 2015 8:48 am

Do I need to save something to avoid a recalibration ?
Sorry, I don't remember if after an upgrade we have to recalibrate.
Thank you
Calibration routine is the same for these 2 new versions as it was for the previous one (V3.3) so it
will not be affected. V3.4 is the same as V3.3 as far as the entire config file is concerned. V4 adds
some new functions to the menus, these will simply be added to the previous version's config file when
saved.

If you plan to go back to V3 after loading and saving a config file with V4, the added menu
items could cause menu corruption from arrays being accessed out of bounds if saved in a position
that V3 does not support, so it may be advisable to save a copy of the WPT file in this case before
upgrading.

It's not a bad idea to save a copy of the config file(s) before upgrading, no matter what versions are
involved, but calibration should not be affected with these latest versions. Also keep in mind if you
have saved any in the additional positions (CONF001.CFG to CONF009.CFG), that although calibration
is not read when loading these files, calibration info is saved in each one, so these could be used as
backups and copied back and renamed to the boot config file (the regular config file "XXXX.WPT")
if necessary.

gce02307
Pre-kindergarten
Pre-kindergarten
Posts: 2
Joined: Tue Feb 24, 2015 9:30 am

Wave Calibration

Post by gce02307 » Tue Feb 24, 2015 9:53 am

Hello everyone,

I bought this little lovely device a few days before. I found it's really powerful when used with Wildcat4!

I have one question. What is the Wave Calibration of Wildcat4 is doing and how?
I could not find any difference between it is on and off.
My device is HW 2.81 and running with FPGA 281 and SYS B162

Thanks in advance for any help.

Wildcat
Elementary-1
Elementary-1
Posts: 166
Joined: Fri Jun 22, 2012 1:29 pm
Are you a staff member of seeedstudio?: no
Which products/projects are your favorite?: DSO Quad

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

Post by Wildcat » Tue Feb 24, 2015 5:35 pm

I have one question. What is the Wave Calibration of Wildcat4 is doing and how?
I could not find any difference between it is on and off.
Wave calibration (long press left toggle center button with meters off) toggles any amplitude compensation applied
to the waveform so it's height accurately displays on screen in relation to the grid. Compensation is accomplished by introducing extra "steps" in the waveform. While small and generally not noticeable, under some conditions they can be,
and will detract from what the actual waveform should look like, so they can be turned off if desired. Each V/div range
and channel is calibrated separately, also keep in mind that this won't do anything unless the entire calibration routine
has been done (Access this by holding down button 2 for more than 3 seconds while the menu is on chA or chB).
This involves using an adjustable voltage source and DMM to calibrate each range. The included user guide explains
how to do this.

Once calibrated, toggling this will simply just adjust the height of the waveform a bit, varying somewhat for each vert
range. With calibration on, a "C" will be displayed in the menu area, off will show "U" (for uncalibrated).

gce02307
Pre-kindergarten
Pre-kindergarten
Posts: 2
Joined: Tue Feb 24, 2015 9:30 am

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

Post by gce02307 » Tue Feb 24, 2015 7:34 pm

Hi Wildcat,
Thank you for quick reply. Now I can see the difference.

Initially I tried CHANNEL A in 1V/DIV range. Maybe the difference introduced by the calibration is small for that setting. Now I try CHANNEL B in 0.5V/DIV range, and the difference is obvious.

I understand that the stock application always runs in "Wave Calibration ON" setting, and you implemented the ability to turn off that setting into your application.

Thanks again for your kind help, and your continued support for this little lovely device!

borland
Kindergarten
Kindergarten
Posts: 50
Joined: Sun Mar 15, 2015 2:47 am

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

Post by borland » Sun Mar 15, 2015 2:58 am

Just installed Wildcat’s version 4.0. Nice work Wildcat. Just a couple bugs to report….

- When saving a configuration file (SaveFile 000.CFG), program prompts user with “OK” but immediately increments CH(A) mode setting (DC/AC/DT/TL/RS/) (e.g., DC -> AC, AC -> DT, etc). The saved configuration file must be reloaded, to restore the Channel A mode setting.

- Analog Calibration can be confusing.
* After calibrating DC-offsets and gains, user is incorrectly prompted (at header) to press button 2 to “confirm the re-calibration of Ch_A “. This is confusing, as user might think program needs confirmation of user inputed calibration data. At footer, user is also prompted to use right toggle to “select the next operation”. Header prompt should instead say “restart re-calibration of Ch_A”. If user incorrectly confirms re-calibration, all previously entered data is lost and must be re-entered. User must right toggle twice (<-) to find “Press button 2” or “3” to save calibration data.

* Wildcat User Guide does not cover or explain if Ch_A / Ch_B calibrations should be performed separately or together. Preference is to do Ch_A and Ch_B independently, as the battery level may run low while trying to do both channels at once. Note: Calibration mode is accessed with long-press of button 2, only when Ch_A or Ch_B are selected. If Ch_B is selected, calibration is entered already set for Ch_B, likewise for Ch_A. It is however possible to switch from Ch_A to Ch_B within Calibration mode in order to populate both calibration tables before saving to WPT file.

* Left toggle button beeps can be annoying and should be muted during gain calibration steps. This is especially annoying if no previous calibration data exists.

Device:
Revision(W4.0) by Wilcat
Alterbios 0.4: OK
Hardware Ver V2.70
SYS Ver 1.52
GCCv1.7W4.0 APP(2.51+SmTech1.8+PMOS69 fixes)
Reload parameter from disk
DFU 3.11C.

What's with the bootup "Reload parameter from disk". Anyone know what that means?

Wildcat
Elementary-1
Elementary-1
Posts: 166
Joined: Fri Jun 22, 2012 1:29 pm
Are you a staff member of seeedstudio?: no
Which products/projects are your favorite?: DSO Quad

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

Post by Wildcat » Sun Mar 15, 2015 1:14 pm

When saving a configuration file (SaveFile 000.CFG), program prompts user with “OK” but immediately increments CH(A) mode setting (DC/AC/DT/TL/RS/) (e.g., DC -> AC, AC -> DT, etc). The saved configuration file must be reloaded, to restore the Channel A mode setting.
Yes it does! Never noticed this, if you use the center press left toggle button to save a config file it advances the setting
if any of the menus are set to the 2nd position. I tend to press the same button again (#3) to save config files, and it does not do it that way, so I never noticed it... You don't need to reload a config file to change it back though, just flip the toggle left. Will be checking into it.
Analog Calibration can be confusing.
* After calibrating DC-offsets and gains, user is incorrectly prompted (at header) to press button 2 to “confirm the re-calibration of Ch_A “. This is confusing, as user might think program needs confirmation of user inputed calibration data. At footer, user is also prompted to use right toggle to “select the next operation”. Header prompt should instead say “restart re-calibration of Ch_A”. If user incorrectly confirms re-calibration, all previously entered data is lost and must be re-entered. User must right toggle twice (<-) to find “Press button 2” or “3” to save calibration data.
This is a carry-over from the original programming, I never changed it. The original English was a bit strange. I can change the wording around.
Wildcat User Guide does not cover or explain if Ch_A / Ch_B calibrations should be performed separately or together. Preference is to do Ch_A and Ch_B independently, as the battery level may run low while trying to do both channels at once. Note: Calibration mode is accessed with long-press of button 2, only when Ch_A or Ch_B are selected. If Ch_B is selected, calibration is entered already set for Ch_B, likewise for Ch_A. It is however possible to switch from Ch_A to Ch_B within Calibration mode in order to populate both calibration tables before saving to WPT file.
I'm not sure if your concern with the battery running low is because it could run out and turn the device off, or if it will affect calibration. As far as calibration is concerned, if I remember right, when saving one channel, the battery level affecting the other channel if it was also calibrated is taken into consideration as far as the battery may now, after time spent calibrating the second channel, be a bit lower. The battery level does not have to be very close to the exhaustion point to set the low level, say maybe 1/4 charge or a bit more should be ok. Battery levels are recorded at calibration
saving point and used as a reference. If the high battery level calibration is done while charging, the VB+ line will be high enough for good interpolation/extrapolation with a low bat level even at 1/2 charge.
Left toggle button beeps can be annoying and should be muted during gain calibration steps. This is especially annoying if no previous calibration data exists
OK, I suppose they could be muted as they don't serve any function. This is again a carry over from the original version, not done on purpose.
What's with the bootup "Reload parameter from disk". Anyone know what that means?
This is also a carry-over from the original, it simply means that the start-up config file was found and used to set configuration. If no config file is found it reads "Parameter record not found". I DID correct the original spelling that stated "Reload parameter form disk"

I appreciate the feedback! Will be posting an update shortly, which will contain a few other fixes as well (in particular a triggering issue while serial decoding in large buffer mode on the 500uS timebase), as well as added SPI and I2C decoding. Will keep all this in mind.

Post Reply