Scott, the owner of this station (2134) , is running gr-satellite for DIY-1 for report to the dashboard, but apparently it is it does not work . I was able to decode the frames using the WAV file generated by the station. What can be wrong @EA4GPZ , @DL4PD ?
Hmm, hard to know. Maybe something about the way he’s running gr-satellites in-line with the decoder (more specifically, the way samples are being sent to gr-satellites), since decoding in post-processing with the WAV does work.
Perhaps the --dump_path option of gr-satellites is useful to debug this.
Thank for posting this Daniel, I was meaning to start a thread after investigating without any clear answer as to how to fix this.
The satnogs-gr_satellites process starts without error for DIY-1, it creates a log file but without any decoding. Satnogs-gr_satellites seems to be working for other satellites so I’m not why it seems particular (so far) to DIY-1.
Log for satnogs_gr_satellites log for that observation 5055359 (grsat_5055359.log):
(env) goes@goes:/data/satnogs$ more grsat_5055359.log
gr::log :DEBUG: correlate_access_code_tag_bb0 - Access code: 2dd4
gr::log :DEBUG: correlate_access_code_tag_bb0 - Mask: ffff
gr::log :DEBUG: correlate_access_code_tag_bb0 - writing tag at sample 78952
gr::log :DEBUG: correlate_access_code_tag_bb0 - writing tag at sample 132313
gr::log :DEBUG: correlate_access_code_tag_bb0 - writing tag at sample 202198
gr::log :DEBUG: correlate_access_code_tag_bb0 - writing tag at sample 219343
I’ll add the flag --dump_path as @ea4gpz suggests going forward. The pre/post scripts are set via satnogs-setup as per the satnogs-gr_satellites installation instructions.
hxxps://github.com/kng/satnogs_gr-satellites/blob/main/INSTALL.md (URL defanged because I don’t like the way it was displaying in this post)