Automatic Decoding Question

[nb3t]

Should I be seeing automatic decoding with my stations? I was under the impression that it was working with at least APT. I’ve recorded several great passes and been able to decode from audio outside of SatNOGS. My stations haven’t decoded anything nor registered any errors during such passes.

The config on both is similar and pasted below, but I do have ENABLE_DECODED_DATA=“True”

SATNOGS_API_TOKEN=“xxxxxxxxxxx”
SATNOGS_NETWORK_API_URL=“https://network.satnogs.org/api/”
SATNOGS_RX_DEVICE=“rtlsdr”
SATNOGS_STATION_ELEV=“634”
SATNOGS_STATION_ID=“27”
SATNOGS_STATION_LAT=“37.194”
SATNOGS_STATION_LON="-80.489"
SATNOGS_VERIFY_SSL=“True”
SATNOGS_IF_GAIN=“0”
SATNOGS_RF_GAIN=“44.5”
SATNOGS_BB_GAIN=“0”
ENABLE_DECODED_DATA=“True”

Is there anything I can do to troubleshoot or verify it is actually enabled?

[surligas]

Hi @nb3t,

which flowgraph do you use? For now satnogs_fsk9600_g3ruh_ax25 and satnogs_noaa_apt_decoder support automatic decoding.

[nb3t]

Thanks for the response @surligas.

These are both on the pi image. In my settings.py I see the apt decoder:

GNURADIO_APT_SCRIPT_FILENAME = ‘satnogs_noaa_apt_decoder.py’

However, there’s no reference to the fsk deoder that I see:

SATNOGS_NETWORK_API_URL = environ.get(‘SATNOGS_NETWORK_API_URL’, ‘SatNOGS Network API’)
SATNOGS_NETWORK_API_QUERY_INTERVAL = 1 # In minutes
SATNOGS_NETWORK_API_POST_INTERVAL = 2 # In minutes
GNURADIO_UDP_PORT = 16886
GNURADIO_IP = ‘127.0.0.1’
GNURADIO_SCRIPT_PATH = [‘/usr/bin’, ‘/usr/local/bin’]
GNURADIO_SCRIPT_FILENAME = ‘satnogs_fm_demod.py’
GNURADIO_FM_SCRIPT_FILENAME = ‘satnogs_fm_demod.py’
GNURADIO_CW_SCRIPT_FILENAME = ‘satnogs_cw_demod.py’
GNURADIO_APT_SCRIPT_FILENAME = ‘satnogs_noaa_apt_decoder.py’
GNURADIO_BPSK_SCRIPT_FILENAME = ‘satnogs_bpsk_demod.py’
SATNOGS_RX_DEVICE = environ.get(‘SATNOGS_RX_DEVICE’, ‘rtlsdr’)
CURRENT_PASS_TCP_PORT = 5005

This is interesting since the settings.py in gitlab does include the FSK line (https://github.com/satnogs/satnogs-client/blob/master/satnogsclient/settings.py).

I’ve manually edited the settings.py file to include this, but won’t the playbook overwrite when satnogs-setup is run later?

[surligas]

@nb3t

I’ve manually edited the settings.py file to include this, but won’t the playbook overwrite when satnogs-setup is run later?

Perhaps, I do not know. Can anyone of the satnogs-client guys help us?

As far the NOAA decoder concerns, you can use the --sync=0 option to disable the synchronization. This eventually will generate a non-aligned or even an only noise image, regardless the presence or absence of signal. Please post the resulting image and audio to be able to help you.

[cshields]

hmm it should be included in the latest client (though in other threads we are debugging an issue with said script)…

@nb3t can you run ‘/var/lib/satnogs/bin/pip show satnogsclient’ and give us the version number?

[nb3t]

@surligas

As far the NOAA decoder concerns, you can use the --sync=0 option to disable the synchronization. This eventually will generate a non-aligned or even an only noise image, regardless the presence or absence of signal. Please post the resulting image and audio to be able to help you.

That’s a nice troubleshooting step, thanks @surligas!

[nb3t]

@cshields

/var/lib/satnogs/bin/pip show satnogsclient

Production 27 (VHF):

Name: satnogsclient
Version: 0.4.1
Summary: SatNOGS Client
Home-page: GitHub - satnogs/satnogs-client: Ground Station Client software
Author: SatNOGS project
Author-email: dev@satnogs.org
License: AGPLv3
Location: /var/lib/satnogs/lib/python2.7/site-packages
Requires: SQLAlchemy, pyserial, requests, flask, validators, APScheduler, pytz, pyopenssl, redis, flask-socketio, ephem, python-dateutil

dpkg -l gr-satnogs:

Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
++±==============-============-============-=================================
ii gr-satnogs 20171016.13f armhf SatNOGS GNU Radio Out-Of-Tree Mod

Production 28 (UHF):

Name: satnogsclient
Version: 0.5
Summary: SatNOGS Client
Home-page: GitHub - satnogs/satnogs-client: Ground Station Client software
Author: SatNOGS project
Author-email: dev@satnogs.org
License: AGPLv3
Location: /var/lib/satnogs/lib/python2.7/site-packages
Requires: SQLAlchemy, pyserial, requests, flask, validators, APScheduler, pytz, pyopenssl, redis, flask-socketio, ephem, python-dateutil

dpkg -l gr-satnogs :

Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
++±==============-============-============-=================================
ii gr-satnogs 20171015.13f armhf SatNOGS GNU Radio Out-Of-Tree Mod

@cshields I guess I’m mistaken, but I had thought that executing the playbook through satnogs-setup was grabbing the latest. However, it looks like I’ve got one at .4 and one at .5. If it’s the playbook acting up, just let me know if I can grab anything to help debug.

[cshields]

@nb3t

but I had thought that executing the playbook through satnogs-setup was grabbing the latest.

yeah, that’s the intent… if it is not working that way then hmmm… Try re-running it on both of your systems now, there were some fixes put in that should fix the FSK scripts.

[cshields]

when you run it the menu will change, go to “Apply configuration” to finish the update.

[nb3t]

@cshields Corey, I may have been a little quick to run the update. I was initially getting some errors but they went away after running a few times.

I’ll let this run with passes for a bit and see if/how the decoding is working here.

If you need anything from my boxes, just let me know.

[cshields]

gitlab went belly up today, hence your errors… At least I hope those are the only reasons for the errors. Let’s hope gitlab holds up now and the latest run works for you.

[nb3t]

@cshields Ah, okay… that makes sense… made for an interesting user experience!

In the middle of the playbook I started getting messages such as unable to locate file. When I got it to load later, git decided there were some uncommitted local changes. So, after a hard reset it worked fine. I had just assumed you were still messing with the repo and I didn’t realize it went down.

[cshields]

I misspoke on the FSK fix: run the ‘sudo satnogs-setup’ command and hit the “Update” command before “Apply”. This will ensure you update to the latest first…

I’ve verified the fix in 2 other Ground Stations…

[nb3t]

Yep, I got it.

The new interface is very nice and appreciated.

[Zathras]

Seeing a lot of files (800+) left in /tmp during/after a FSK9k6 observation.
Yet there is good data in the Data tab

These files do not get deleted.

[cshields]

that’s good - means the script is working. (the good data at least).

I’ll file an issue for the leftover files, that will cause an issue if left undeleted and start to pile up:

don't keep failed CRC files (#111) · Issues · librespacefoundation / SatNOGS...