Hello,
I am using the satnogs artifacts imager in my project. Recently, I tried RTLSDR with my 137Mhz V-dipole antenna to receive APT signal from weather satellite NOAA-15, but it fails. I think I am missing configuration in satnogs-setup for SoapySDR or in other some decoding tools.
Please, help me to configure setting to receive the signal from RTLSDR. I have tried the satnogs SDR setup.
Hi @modular_gs_KHEC and welcome!
Can you copy paste here the logs and the support report of your station? This will help us to find what is the error.
For getting both of them check in Troubleshooting - SatNOGS Wiki the two yellow boxes at the top.
that is your personal api token, you should renew it so noone else can abuse it.
okey sir! thanks
try removing the .service from the journalctl and see if it shows something
If you indeed has entered these, you need to do Apply in setup for this to be written in the -client config
I did…
for the first time when APPLY was done it takes a while and changes are made…
does the ‘*’ stays remain after apply is executed?
As it is described here:
https://wiki.satnogs.org/SatNOGS_Client_Setup#Basic_Configuration
SATNOGS_SOAPY_RX_DEVICE should be driver=rtlsdr
Probably this is the issue. If after applying this change it still doesn’t work, please copy paste the support report by choosing the menu item Advanced -> Support from sudo satnogs-setup.
thank you!
I change this configuration but still the same…
my support report is below:
Generating support report. Please wait…
------------[ copy here ]------------
{
“versions”: {
“satnogs-client”: “1.8.1”,
“satnogs-client-ansible”: “202209101521”,
“satnogs-flowgraphs”: “1.4-1”,
“gr-satnogs”: “2.3.4.0-1”,
“gr-soapy”: “2.1.3.1-1”,
“gnuradio”: “3.8.2.0-14”,
“satnogs-config”: “0.13.2”
},
“state”: {
“is-applied”: true,
“pending-tags”: null
},
“system”: {
“date”: “2023-08-05T18:11:07.063136+00:00”,
“distribution”: {
“DESCRIPTION”: “Raspbian GNU/Linux 11 (bullseye)”,
“RELEASE”: “11”,
“CODENAME”: “bullseye”,
“ID”: “Raspbian”
},
“pending-updates”: true,
“platform”: {
“system”: “Linux”,
“node”: “raspberrypi”,
“release”: “6.1.21-v8+”,
“version”: “#1642 SMP PREEMPT Mon Apr 3 17:24:16 BST 2023”,
“machine”: “aarch64”
},
“memory”: {
“total”: 3978645504,
“available”: 3762421760,
“percent”: 5.4,
“used”: 136294400,
“free”: 3256373248,
“active”: 239591424,
“inactive”: 376094720,
“buffers”: 32780288,
“cached”: 553197568,
“shared”: 856064,
“slab”: 66899968
},
“disk”: {
“total”: 30443524096,
“used”: 4829343744,
“free”: 24322195456,
“percent”: 16.6
}
},
“configuration”: {
“hamlib_utils_rot_opts”: “-m 601 -r /dev/ttyACM0 -s 9600 -T 0.0.0.0”,
“satnogs_antenna”: “RX”,
“satnogs_api_token”: “[redacted]”,
“satnogs_rf_gain”: “44.5”,
“satnogs_rx_samp_rate”: “2.048e6”,
“satnogs_soapy_rx_device”: “driver=rtlsdr”,
“satnogs_station_elev”: “1401”,
“satnogs_station_id”: “3186”,
“satnogs_station_lat”: “27.671114”,
“satnogs_station_lon”: “85.439625”
}
}
------------[ copy end ]-------------
Press Enter to continue…
hmm, do note the date of the logs.
not sure if anything has changed, but if you don’t get the current date in the logs, the actual name for the log needs to be adjusted. this is what I used in the past journalctl -f -n 50 -u satnogs-client
it looks like it was online recently Last seen 13 hours, 51 minutes ago
I’m guessing the issue was the driver= part missing ?
Hi! @SA2KNG …
I reinstall the artifacts image and start configuring from the beginning…
Here I got two different logs… I have intentionally not provide the SATNOGS_SOAPY_RX_DEVICE and SATNOGS_RX_SAMP_RATE…
This is what I get
$ journalctl -f -n 50 -u satnogs-client.service OR
$ journalctl -f -u satnogs-client.service
– Journal begins at Sat 2022-09-10 17:10:32 UTC. –
Aug 06 14:38:06 raspberrypi satnogs-client[8199]: satnogsclient - ERROR - SATNOGS_SOAPY_RX_DEVICE not configured but required
Aug 06 14:38:06 raspberrypi satnogs-client[8199]: satnogsclient - ERROR - SATNOGS_RX_SAMP_RATE not configured but required
Aug 06 14:38:06 raspberrypi satnogs-client[8199]: satnogsclient - ERROR - Settings are invalid, exiting…
Aug 06 14:38:06 raspberrypi systemd[1]: satnogs-client.service: Main process exited, code=exited, status=255/EXCEPTION
Aug 06 14:38:06 raspberrypi systemd[1]: satnogs-client.service: Failed with result ‘exit-code’.
Aug 06 14:38:06 raspberrypi systemd[1]: satnogs-client.service: Consumed 3.716s CPU time.
Aug 06 14:38:06 raspberrypi systemd[1]: satnogs-client.service: Scheduled restart job, restart counter is at 30.
Aug 06 14:38:06 raspberrypi systemd[1]: Stopped SatNOGS client.
Aug 06 14:38:06 raspberrypi systemd[1]: satnogs-client.service: Consumed 3.716s CPU time.
Aug 06 14:38:06 raspberrypi systemd[1]: Started SatNOGS client.
Aug 06 14:38:10 raspberrypi satnogs-client[8200]: satnogsclient - ERROR - SATNOGS_SOAPY_RX_DEVICE not configured but required
Aug 06 14:38:10 raspberrypi satnogs-client[8200]: satnogsclient - ERROR - SATNOGS_RX_SAMP_RATE not configured but required
Aug 06 14:38:10 raspberrypi satnogs-client[8200]: satnogsclient - ERROR - Settings are invalid, exiting…
Aug 06 14:38:10 raspberrypi systemd[1]: satnogs-client.service: Main process exited, code=exited, status=255/EXCEPTION
Aug 06 14:38:10 raspberrypi systemd[1]: satnogs-client.service: Failed with result ‘exit-code’.
Aug 06 14:38:10 raspberrypi systemd[1]: satnogs-client.service: Consumed 3.749s CPU time.
Aug 06 14:38:10 raspberrypi systemd[1]: satnogs-client.service: Scheduled restart job, restart counter is at 31.
Aug 06 14:38:10 raspberrypi systemd[1]: Stopped SatNOGS client.
Aug 06 14:38:10 raspberrypi systemd[1]: satnogs-client.service: Consumed 3.749s CPU time.
Aug 06 14:38:10 raspberrypi systemd[1]: Started SatNOGS client.
and when I run
$ journalctl -u satnogs-client.service
– Journal begins at Sat 2022-09-10 17:10:32 UTC, ends at Sun 2023-08-06 14:36:46 UTC. –
Aug 06 13:53:04 raspberrypi systemd[1]: Started SatNOGS client.
Aug 06 13:53:14 raspberrypi satnogs-client[4867]: satnogsclient - ERROR - SATNOGS_API_TOKEN not configured but required
Aug 06 13:53:14 raspberrypi satnogs-client[4867]: satnogsclient - ERROR - SATNOGS_STATION_ID not configured but required
Aug 06 13:53:14 raspberrypi satnogs-client[4867]: satnogsclient - ERROR - SATNOGS_STATION_LAT not configured but required
Aug 06 13:53:14 raspberrypi satnogs-client[4867]: satnogsclient - ERROR - SATNOGS_STATION_LON not configured but required
Aug 06 13:53:14 raspberrypi satnogs-client[4867]: satnogsclient - ERROR - SATNOGS_STATION_ELEV not configured but required
Aug 06 13:53:14 raspberrypi satnogs-client[4867]: satnogsclient - ERROR - SATNOGS_SOAPY_RX_DEVICE not configured but required
Aug 06 13:53:14 raspberrypi satnogs-client[4867]: satnogsclient - ERROR - SATNOGS_RX_SAMP_RATE not configured but required
Aug 06 13:53:14 raspberrypi satnogs-client[4867]: satnogsclient - ERROR - SATNOGS_ANTENNA not configured but required
Aug 06 13:53:14 raspberrypi satnogs-client[4867]: satnogsclient - ERROR - SATNOGS_STATION_LAT not configured
Aug 06 13:53:14 raspberrypi satnogs-client[4867]: satnogsclient - ERROR - SATNOGS_STATION_LON not configured
Aug 06 13:53:14 raspberrypi satnogs-client[4867]: satnogsclient - ERROR - SATNOGS_STATION_ELEV not configured
Aug 06 13:53:14 raspberrypi satnogs-client[4867]: satnogsclient - ERROR - Settings are invalid, exiting…
Aug 06 13:53:14 raspberrypi systemd[1]: satnogs-client.service: Main process exited, code=exited, status=255/EXCEPTION
Aug 06 13:53:14 raspberrypi systemd[1]: satnogs-client.service: Failed with result ‘exit-code’.
Aug 06 13:53:14 raspberrypi systemd[1]: satnogs-client.service: Consumed 5.534s CPU time.
Aug 06 13:53:14 raspberrypi systemd[1]: satnogs-client.service: Scheduled restart job, restart counter is at 1.
Aug 06 13:53:14 raspberrypi systemd[1]: Stopped SatNOGS client.
Aug 06 13:53:14 raspberrypi systemd[1]: satnogs-client.service: Consumed 5.534s CPU time.
Aug 06 13:53:14 raspberrypi systemd[1]: Started SatNOGS client.
Aug 06 13:53:18 raspberrypi satnogs-client[5057]: satnogsclient - ERROR - SATNOGS_API_TOKEN not configured but required
