@begreen pointed out the LE issue we also have on FOX-satellites, so it might turn out to be as complicated in satnogs-decoders. We need to find a solution for that…
@surligas “demodulated” the iq recordings provided on @begreen’s website.
They are only containing a “dummy periodic message”, but this shows the whole decoding process works.
The only thing to do is now: clear the LE issue for data values!
By the way - do you know why only one observation (here) contains decoded data? Others look also promising but lack of incomplete/not decoded data sets?
I didn’t check all, but: there are a lot of obs with very faint signals. The one that decodes curiously decoded with an old (and very simple compared to the new one) version of the BPSK decoder (basically the one I developed for PICSAT some time ago).
Maybe we should try to capture some IQs to get @surligas into this
There is perhaps an issue for small baudrates, due to a fixed non-parametric transition width at the low pass filter. An IQ recording will help to fix that!
We’ve decided to stay on BPSK 9k6 for most of the time. We’ve finished commissioning of the satellite and now entering experiments phase, so we’ll demand more energy and higher baud rate is one of the energy-saving method.
Hi!
I think that we should remove 1k2, 2k4, 4k8 bps modes from the list - we’re using and will be using in the future 9k6 only.
Another topic that I’d like to discuss is data demodulation - 99,99% observations are useless for now, because the only output is a waterfall. There are no demod data, moreover it’s impossible to demod 9k6 data from ogg file (because of this problem: Ogg artifacts frequency offset).
In our software/webapp dedicated to mission there are right now 377006 frames received and uploaded, so I’m wondering what’s the problem with SatNOGS. So I’d like to solve it and get similar demoded amount of data in the future from satnogs
Hey,
There is no flowgraph to demodulate in gr-satnogs yet. Maybe you could contribute one?
I do also have a katai struct decoder laying around I need to do some checks, maybe a refactor with it.
db.satnogs.org is holding something around 30k frames for PW-Sat2…
Yes, that’s true adn great! But I believe that could be much more - most of the observations lack demod data. I think I can try to adapt our (PW-Sat2) GRC flow graphs that we use to demodulate BPSK and decode AX.25. But it demands some cleaning Maybe you’ve already taken a look at this flowgraph and can comment if you think it’s worth to use it?
Concerning your katai struct decoder - I remember that there was an issue with bit endianness (because of lack of kaitai support). Is that resolved now? Another thing is that we’ve updated on-board software introducing a new power saving mode, so there is additional ‘short’ telemetry frame format However it’s much easier than ‘full telemetry’ frame.
But the first thing I’d like to take up is to figure out and fix (if possible, maybe it’s SNR issue) observations without data.
BTW. Is there any API or sth like this to access data in SatNOGS db in real-time? I know that there is an option to download data in csv but having it in real time would be great!
Maybe you’ve already taken a look at this 
However it’s much easier than ‘full telemetry’ frame.