Please share extra information, going over the post I have no idea what the issue is?
As a remark, after launch and during the TLE “lottery” it can be difficult to get decoding and frame uploads working.
Do note that the temporary norad id is messing with it, as the TLE used for tracking is the only source of id on the pre-/post-obs scripts.
For example Bluebird 01 is now
Temporary NORAD ID
98804
Followed NORAD ID
61046
Which means that any obs scheduled now will use 61046, for example at the bottom of the obs page 10256104
During the first weeks this will change and the TLE lottery will soon settle.
So, if you want to demodulate these you need to have satyaml’s with the “Followed NORAD ID”,
which is not the case for the current satyaml.
And to make things more complicated, with BLUEBIRD we need an extra options that is configured in ${HOME}/.gr_satellites/sat.cfg and also has an ID dependency
The below example is using the Followed NORAD ID
61046 --disable_dc_block
61049 --disable_dc_block
61045 --disable_dc_block
61048 --disable_dc_block
61047 --disable_dc_block
Many thank SA2KNG,
Thank you so much for your hard work on this project…
ve2dsk
1 Like
Should I be regularly updating gr-satellites somehow? I haven’t been.
If you build from master then you can look at the commits and see if there’s something worth rebuilding, for satyaml updates it is usually sufficient to just update those without reinstalling. The script linked may need adjusting depending on your host, certainly need to have the path writable by your user.
I try to update the gr-satellites package build for the satnogs repos, but those are only built on releases and not the intermediate commits.