It just preloads the starting point at 1/2 least significant bit. I actually didn’t give it a whole lot of thought, this is common practice when working with ADC’s. Has to do with integer math, where most compilers will not round out a value. For example, if you start out at 0, then add 0.999, you will still get 0, however, subtract 0.001 and you will get -1. This creates a 1/2 LSB offset biased towards the negative. If you preload it at +0.5 then it takes an equal level to bring it positive as it does negative, effectively “centering” the zero level. This is also the reason the original author added “512” to the calibration calculations, these subsequently get divided by 1024, biasing the value to +1/2 LSB.
The original code initialized these @ 2048 (out of 4096 samples). I just changed it so it would work correctly when using the smaller buffer.
As I mentioned, I did not give this huge amount of thought at the time, it may be that the 1/2LSB offset is taken care in subsequent calculations, so you may be right…
I found HEX binaries in root directory of archive, but if I tried to install any of them (i suppose there are three version to three different slots), no one is possible to install. Each try seems to be succesfull (fast unmount/mount and rename HEX to RDY extension) but nothing on DSO is overwritten. There is still previous one version of DSO active in slot1 and previously installed LOGIC analyzer in slot 3.
May be I missed something, or included HEX is wronlgy compiled a recompilation necessary. I want to start building of development environment for future improvement participation, but now I need to use DSO with best actual FW…
Thank you very much Wildcat. You fixed the triggering so now I can see occasional bursts of data on a serial line. This scope hase been practically useless to me until now.
You moved DSO Quad form almost unusable toy to quite nice DSO. I hope that we get soon merged FW of yours and Pmos’s version with good buttons layout - each FW i tried used different mapping and for me it was necessary to print help card with buttons mapping. (I see Wildcat buttons mapping to be most effective - especially moving some fucntion from jogdials to big buttons is nice.
May be let discuss some definitive buttons functions layout and keep it across future versions…
I was very disappointed by severity and amount of bugs in official firmware as very poor and incomplete doc.
So it is necessary strongly recommend to newcomers IMMEDIATELY switch to PMOS or WILDCAT version!!!
However per the last picture posted here, it’s really a sub set of green CH4. This buggered me for a while. Long press of play/pause doesn’t seem to do anything.
I’ve been using the Wildcat version as my main app which functions very nicely as a scope.
I can’t seem to make sense of the signal generator part though. It sets the waveform and the amplitude OK but all the frequencies seem to be off by a factor of 4. E.g. when I set 1KHz I get a 250 microsecond period waveform on the display rather than the 1msec I was expecting. The timebase looks OK against normal external signals.
There is something like a bug and is a kind of mirror behavior in realtime scan with short buffer
Other Small thing is that the Square that tells the size of the buffer (bottom middle) only fills complete if the full screnn is off, when full screen is activated the scan looses almost 4 squares of measurement. Thank you
Triggered by a comment in another post, I figured out that Wildcat needs the standard SYS rather than the modified SYS25116 I had been using on the community edition. I put Sys1.52 on and now the signal generator frequencies match the display.