Thanks also. Despite the overhead pass over FN41, the SNR seemed much less than observed before. No frames detected. Might not have helped that another bird was up band at the same time. Nevertheless, given the high pass left wondering if somehow the down-link power was reduced as well? Very curious to see how others make out this round.
… but that’s not the end of the story. Even though we only had ONE capture file to work with (I got zero decodes), I ran Bob’s capture frames through ssdv-merge.py and apparently that scans the ENTIRE file for valid frames (better than SSDV does by itself, apparently). I say that because sending the output from ssdv-merge.py to the SSDV utility produced a more complete image!
… moral of the story is that when I DO get future captures w/ some number of valid decodes, you can bet I’m going to let the ssdv-merge.py script search the file before I send anything to SSDV!
KO95. Moscow region. 18:27-18:31 UTC. Yagi 7el.+RTL SDR V4 This timе I tried to sync the signal’s polarity change - every 5-6 packets signal went weaker than restores, got 174 packets (vs 147 on friday) but more missing places. Next time I will try a helical antenna.
Very nifty script setup. Thank you very much for sharing this with us. I streamed the audio directly from the browser into direwolf by not using pavucontrol, but by connecting them with qpwgraph directly.
Unfortunately I got known of this event only, by your scheduled observation at BEEGND-4. Now I will follow this thread more closely. To everyone: Feel free to schedule BEEGND-4, if there is to happen anything cool related to ssdv again.
Good news - we successfully tweeted from the satellite tonight. Bad news, we ran out of time on the pass before sending the next set of SSDV commands. It may be mid-week before we get more scheduled.