This modulation (USP) isn’t supported natively by SatNOGS.
Looking at your journal log, this is a bug after the initial satnogs client startup and “normal” maybe you can also share a real observation and the output from sudo satnogs-setup → Advanced → Support.
By this observation I just wanted to show, that the waterfall shows signals, unlike the other one. Currently, it’s still about receptions, not about decodations.
Dec 19 17:10:47 madrid satnogs-client[52517]: gr-satellites: Observation: 10792388, Norad: 60237, Name: 0_OBJECT_C, Script: satnogs_fsk.py
Dec 19 17:10:47 madrid satnogs-client[52517]: gr-satellites: Starting observation 10792388
Dec 19 17:10:47 madrid satnogs-client[52517]: gr-satellites: running at 57600 sps
Dec 19 17:10:47 madrid satnogs-client[4737]: rig_init: rig does not have rx_range!!
Dec 19 17:10:47 madrid satnogs-client[4737]: network_open: hoststr=127.0.0.1, portstr=4532
Dec 19 17:10:49 madrid satnogs-client[52556]: Found Rafael Micro R820T/2 tuner
Dec 19 17:10:49 madrid satnogs-client[52556]: Found Rafael Micro R820T/2 tuner
Dec 19 17:10:49 madrid satnogs-client[52556]: [INFO] Opening Generic RTL2832U OEM :: 00001220...
Dec 19 17:10:49 madrid satnogs-client[52556]: Found Rafael Micro R820T/2 tuner
Dec 19 17:10:50 madrid satnogs-client[52556]: [INFO] Using format CF32.
Dec 19 17:10:50 madrid satnogs-client[52556]: Allocating 15 zero-copy buffers
Dec 19 17:17:19 madrid satnogs-client[4737]: netrigctl_close: done status=Command completed successfully
Dec 19 17:17:21 madrid satnogs-client[52671]: gr-satellites: Observation: 10792388, Norad: 60237, Name: 0_OBJECT_C, Script: satnogs_fsk.py
Dec 19 17:17:21 madrid satnogs-client[52671]: gr-satellites: Stopping observation 10792388
Dec 19 17:17:21 madrid satnogs-client[52671]: gr-satellites: processing KISS data to network
Dec 19 17:17:29 madrid satnogs-client[52709]: adding: iq_57600_10792388.raw (deflated 23%)
Dec 19 17:17:31 madrid satnogs-client[52709]: test of /import/group/raw/iq_57600_10792388.raw.zip OK
Dec 19 17:39:00 madrid satnogs-client[52859]: gr-satellites: Observation: 10792564, Norad: 41789, Name: 0_ALSAT_1N, Script: satnogs_fsk.py
Dec 19 17:39:00 madrid satnogs-client[52859]: gr-satellites: Satellite not supported
Dec 19 17:39:00 madrid satnogs-client[4737]: rig_init: rig does not have rx_range!!
Dec 19 17:39:00 madrid satnogs-client[4737]: network_open: hoststr=127.0.0.1, portstr=4532
Dec 19 17:39:01 madrid satnogs-client[52876]: Found Rafael Micro R820T/2 tuner
Dec 19 17:39:02 madrid satnogs-client[52876]: Found Rafael Micro R820T/2 tuner
Dec 19 17:39:02 madrid satnogs-client[52876]: [INFO] Opening Generic RTL2832U OEM :: 00001220...
Dec 19 17:39:02 madrid satnogs-client[52876]: Found Rafael Micro R820T/2 tuner
Dec 19 17:39:02 madrid satnogs-client[52876]: [INFO] Using format CF32.
Dec 19 17:39:03 madrid satnogs-client[52876]: Allocating 15 zero-copy buffers
Dec 19 17:46:35 madrid satnogs-client[4737]: netrigctl_close: done status=Command completed successfully
Dec 19 17:46:37 madrid satnogs-client[52971]: gr-satellites: Observation: 10792564, Norad: 41789, Name: 0_ALSAT_1N, Script: satnogs_fsk.py
Dec 19 17:46:46 madrid satnogs-client[53007]: adding: iq_57600_10792564.raw (deflated 23%)
Dec 19 17:46:48 madrid satnogs-client[53007]: test of /import/group/raw/iq_57600_10792564.raw.zip OK
One last option, save IQ files from observations, replay them and see if there was information send during the observation, if there isn’t, maybe a RF chain hardware problem.
Hi Daniel,
first one looks like a prebuilt python package is no longer available, just a guess.
the second one, with experimental, probably leads to a mixed setup as the master branch is aimed at the dockerized client.
if you want to you can try the new stack, it will uninstall the host based client and install the dockerized one instead. do note that it does work, but it lacks a few details like the pre-/post script for now. curl -sLf https://satno.gs/install | sudo sh -s -- -C master
well, it has a waterfall at least (: note that you need to specify the master branch when running satnogs-setup again (before it is released as stable): sudo satnogs-setup -C master
to see the client logs: sudo docker logs -f -n 100 -t satnogs_satnogs-client