Initial RTL-SDR setup issues

SatNOGS Software
1

Hi, So I got the latest build to install correctly, but I get no data from the rtl-sdr.
using satnogs-setup it is set as driver=rtlsdr
Running rtl_test gives:
ound 1 device(s):
0: Generic, RTL2832U, SN: 77771111153705700

Using device 0: Generic RTL2832U
Found Rafael Micro R820T tuner
Supported gain values (29): 0.0 0.9 1.4 2.7 3.7 7.7 8.7 12.5 14.4 15.7 16.6 19.7 20.7 22.9 25.4 28.0 29.7 32.8 33.8 36.4 37.2 38.6 40.2 42.1 43.4 43.9 44.5 48.0 49.6
[R82XX] PLL not locked!
Sampling at 2048000 S/s.

Info: This tool will continuously read from the device, and report if
samples get lost. If you observe no further output, everything is fine.

Reading samples in async mode…
Allocating 15 zero-copy buffers
^CSignal caught, exiting!

User cancel, exiting…
Samples per million lost (minimum): 0

So it seems the drivers are there, but I am not sure that the station is running.
I only get a one liner from
journalctl -u satnogs-client.service
– Logs begin at Fri 2020-04-03 09:53:41 BST, end at Fri 2020-04-03 10:11:15 BST
Apr 03 09:53:45 SomersetWest systemd[1]: Started SatNOGS client.

This was all done with the latest build from Satnogs Git.
Should there be udev rules for the rtl-sdr?

Rikus

2

Please copy paste here the results of Advanced ---> Support in sudo satnogs-setup.

3

HI, here is the support output

Generating support report. Please wait…
------------[ copy here ]------------
{
“versions”: {
“satnogs-client”: “1.3.1”,
“satnogs-client-ansible”: “202004012056”,
“satnogs-flowgraphs”: “1.1.1-1”,
“gr-satnogs”: “2.1-1”,
“gr-soapy”: “2.1.2-1”,
“gnuradio”: “3.8.1.0~rc1-2”,
“satnogs-config”: “0.10”
},
“state”: {
“is-applied”: false,
“pending-tags”: null
},
“system”: {
“distribution”: {
“DESCRIPTION”: “Raspbian GNU/Linux 10 (buster)”,
“RELEASE”: “10”,
“CODENAME”: “buster”,
“ID”: “Raspbian”
},
“pending-updates”: false,
“platform”: {
“system”: “Linux”,
“node”: “SomersetWest”,
“release”: “4.19.97-v7+”,
“version”: “#1294 SMP Thu Jan 30 13:15:58 GMT 2020”,
“machine”: “armv7l”,
“processor”: “”
},
“memory”: {
“total”: 971059200,
“available”: 790200320,
“percent”: 18.6,
“used”: 109363200,
“free”: 382910464,
“active”: 340971520,
“inactive”: 163676160,
“buffers”: 37847040,
“cached”: 440938496,
“shared”: 6475776,
“slab”: 62697472
},
“disk”: {
“total”: 7474692096,
“used”: 3798900736,
“free”: 3324571648,
“percent”: 53.3
}
},
“configuration”: {
“satnogs_antenna”: “RX”,
“satnogs_api_token”: “[redacted]”,
“satnogs_rf_gain”: “Overall”,
“satnogs_rx_samp_rate”: “2.048e6”,
“satnogs_soapy_rx_device”: “driver=rtlsdr”,
“satnogs_station_elev”: “145”,
“satnogs_station_id”: “1453”,
“satnogs_station_lat”: “-34.063831”,
“satnogs_station_lon”: “18.837979”
}
}
------------[ copy end ]-------------

4

I note that satnogs_rf_gain is set to “Overall”. This should be the gain value.
It’s satnogs_gain_mode that defaults to “Overall”.

5

Hi,
Ok, I have fixed that, updated and rebooted but the situation is the same. It does not seem if the ground station connects to the SDR at all.
SoapySDRUtil --probe=“driver=rtlsdr” produces the correct info and data.
rtl_test -p gives a ppm 89 which seems about ok for the device.
So it is there and alive Satnogs just does not seem to connect.

R

6

What’s the output of ‘journalctl -f -u satnogs-client.service’ during an observations?

Hopefully it should show up something…

You could also try running a flowgraph manually and see what happens. To do this, run:

$ sudo su satnogs -s /bin/bash
$ python3 /usr/bin/satnogs_cw_decoder.py --soapy-rx-device="driver=rtlsdr" --antenna=RX --samp-rate-rx=2.048e6

This gives me the following output on my station:

satnogs@satnogs2mv2:~ $ python3 /usr/bin/satnogs_cw_decoder.py --soapy-rx-device=“driver=rtlsdr” --antenna=RX --samp-rate-rx=2.048e6
Found Rafael Micro R820T tuner
Found Rafael Micro R820T tuner
[R82XX] PLL not locked!
[INFO] Using format CF32.
4
Allocating 15 zero-copy buffers

1 Like
7

Hi,
The thing is it does not seem to start any observations.
journalctl -f -u satnogs-client.service, just shows the one line when the client started.–

Logs begin at Thu 2019-02-14 10:11:59 GMT. –
Apr 03 12:54:45 SomersetWest systemd[1]: Started SatNOGS client.

Also the script you provided gave the following:
satnogs@SomersetWest:/home/pi $ python3 /usr/bin/satnogs_cw_decoder.py --soapy-rx-device=“driver=rtlsdr” --antenna=RX --samp-rate-rx=2.048e6

Found Rafael Micro R820T tuner
Found Rafael Micro R820T tuner
[R82XX] PLL not locked!
[INFO] Using format CF32.
Segmentation fault

Rikus

8

Hi,

Ok after reboot I got the following:

Found Rafael Micro R820T tuner
Found Rafael Micro R820T tuner
[R82XX] PLL not locked!
[INFO] Using format CF32.
4
/home/pi/.gnuradio/prefs/vmcircbuf_default_factory: No such file or directory
vmcircbuf_createfilemapping: createfilemapping is not available
gr::vmcircbuf_sysv_shm: shmat (2): Invalid argument
gr::vmcircbuf_sysv_shm: shmat (2): Invalid argument
gr::vmcircbuf_sysv_shm: shmat (2): Invalid argument
Allocating 15 zero-copy buffers

Seems there is something screwy.
The /home/pi/.gnuradio/prefs does contain the file???

R

9

Oh i’ve seen the segfault issue before (just a few hours ago in fact)

Sorry, you need to cd to the satnogs home directory (e.g. just run ‘cd’ once you are running as the satnogs users) before you can run the flowgraph. Probably a permissions issue with running the flowgraph in the ‘pi’ users home directory.

That output looks right actually. Remember the flowgraphs are normally run as the satnogs users, so those files will end up in the satnogs users home directory.

10

Hi Mark,
Ok, I now get the same output. It also generated a test.wav file.
So, how do I get it to rum from the Satnogs network??
Maybe I’m really daft,but I cant get it to run:
I got to my Satnogs Dashboard,
Schedule a new observation and then nothing. Just stating “waiting for waterfall”
Also the journal file still only has the following entry

Apr 03 14:03:00 SomersetWest systemd[1]: Started SatNOGS client.

Thanks

Rikus

11

At this point it should work… can you re-post your support output?

12

Hi,

Generating support report. Please wait…
------------[ copy here ]------------
{
“versions”: {
“satnogs-client”: “1.3.1”,
“satnogs-client-ansible”: “202004012056”,
“satnogs-flowgraphs”: “1.1.1-1”,
“gr-satnogs”: “2.1-1”,
“gr-soapy”: “2.1.2-1”,
“gnuradio”: “3.8.1.0~rc1-2”,
“satnogs-config”: “0.10”
},
“state”: {
“is-applied”: true,
“pending-tags”: null
},
“system”: {
“distribution”: {
“DESCRIPTION”: “Raspbian GNU/Linux 10 (buster)”,
“RELEASE”: “10”,
“CODENAME”: “buster”,
“ID”: “Raspbian”
},
“pending-updates”: false,
“platform”: {
“system”: “Linux”,
“node”: “SomersetWest”,
“release”: “4.19.97-v7+”,
“version”: “#1294 SMP Thu Jan 30 13:15:58 GMT 2020”,
“machine”: “armv7l”,
“processor”: “”
},
“memory”: {
“total”: 971059200,
“available”: 802942976,
“percent”: 17.3,
“used”: 107450368,
“free”: 617664512,
“active”: 228589568,
“inactive”: 64536576,
“buffers”: 24301568,
“cached”: 221642752,
“shared”: 6475776,
“slab”: 39247872
},
“disk”: {
“total”: 7474692096,
“used”: 3805274112,
“free”: 3318198272,
“percent”: 53.4
}
},
“configuration”: {
“satnogs_antenna”: “RX”,
“satnogs_api_token”: “[redacted]”,
“satnogs_rf_gain”: “38.2”,
“satnogs_rx_samp_rate”: “2.048e6”,
“satnogs_soapy_rx_device”: “driver=rtlsdr”,
“satnogs_station_elev”: “145”,
“satnogs_station_id”: “1453”,
“satnogs_station_lat”: “-34.063831”,
“satnogs_station_lon”: “18.837979”
}
}
------------[ copy end ]-------------

13

Is there something I am missing from the Satnogs API side?

14

Nothing looks obviously wrong there. You should be OK.

You will only see output from journalctl when an observation actually occurs. So I’d suggest queueing up as many as you can so you have as many opportunities as possible. This is a bit more difficult for a 2m-only station, as there are lets sats to look at.

15

Ok,
But even of there is no overpass, should the unit not be running providing a waterfall with just noise?
R

16

Nope. The SDR is only started and recording when there is an observation occurring.

17

Following this link… i’m having the same issues …following the same steps and getting the same results …

Max

18

Same issue here.
Updated earlier today and Station looks ok, but no results from scheduled observations.
Will run journal on next ob…

19

Ok, so journal reports the following…

Apr 05 18:07:23 raspberrypi satnogs-client[7014]: [INFO] [UHD] linux; GNU C++ version 8.3.0; Boost 106700; UHD_3.15.0.0-2
Apr 05 18:07:23 raspberrypi satnogs-client[7014]: Found Rafael Micro R820T tuner
Apr 05 18:07:23 raspberrypi satnogs-client[7014]: Traceback (most recent call last):
Apr 05 18:07:23 raspberrypi satnogs-client[7014]: File “/usr/bin/satnogs_cw_decoder.py”, line 45 9, in
Apr 05 18:07:23 raspberrypi satnogs-client[7014]: main()
Apr 05 18:07:23 raspberrypi satnogs-client[7014]: File “/usr/bin/satnogs_cw_decoder.py”, line 44 4, in main
Apr 05 18:07:23 raspberrypi satnogs-client[7014]: tb = top_block_cls(antenna bb_freq=options.bb_freq, bfo_freq=options.bfo_freq, bw=options.bw, dc_removal=op decoded_data_file_path=options.decoded_data_file_path, dev_args=options.dev_args on_per_sec=options.doppler_correction_per_sec, enable_iq_dump=options.enable_iq tions.file_path, gain=options.gain, gain_mode=options.gain_mode, iq_file_path=op , lo_offset=options.lo_offset, other_settings=options.other_settings, ppm=option =options.rigctl_port, rx_freq=options.rx_freq, samp_rate_rx=options.samp_rate_rx options.soapy_rx_device, stream_args=options.stream_args, tune_args=options.tune ons.udp_IP, udp_port=options.udp_port, waterfall_file_path=options.waterfall_fil s.wpm)
Apr 05 18:07:23 raspberrypi satnogs-client[7014]: File "/usr/bin/satnogs_cw_de , in init
Apr 05 18:07:23 raspberrypi satnogs-client[7014]: tune_args, settings, samp_
Apr 05 18:07:23 raspberrypi satnogs-client[7014]: File “/usr/lib/python3/dist- py_swig.py”, line 166, in make
Apr 05 18:07:23 raspberrypi satnogs-client[7014]: return soapy_swig.source , dev_args, stream_args, tune_args, other_settings, sampling_rate, type)
Apr 05 18:07:23 raspberrypi satnogs-client[7014]: RuntimeError: soapy::source: U rate. Rate must be in the range [8000.000000, 8000.000000] [16000.000000, 16000 0000, 22050.000000] [32000.000000, 32000.000000] [44100.000000, 44100.000000] [4 .000000] [96000.000000, 96000.000000]
Apr 05 18:07:27 raspberrypi satnogs-client[7014]: satnogsclient.observer.observe erfall data file found

I followed the setup guide in the Wiki but it looks like the sample rate is unsupported. 2.048e6 looks like the issue.

From support in the setup tool I get…

Generating support report. Please wait…
------------[ copy here ]------------
{
“versions”: {
“satnogs-client”: “1.3.1”,
“satnogs-client-ansible”: “202004031132”,
“satnogs-flowgraphs”: “1.1.1-1”,
“gr-satnogs”: “2.1-1”,
“gr-soapy”: “2.1.2-1”,
“gnuradio”: “3.8.0.0-6”,
“satnogs-config”: “0.10.1”
},
“state”: {
“is-applied”: true,
“pending-tags”: null
},
“system”: {
“distribution”: {
“DESCRIPTION”: “Raspbian GNU/Linux 10 (buster)”,
“RELEASE”: “10”,
“CODENAME”: “buster”,
“ID”: “Raspbian”
},
“pending-updates”: true,
“platform”: {
“system”: “Linux”,
“node”: “raspberrypi”,
“release”: “4.19.97-v7+”,
“version”: “#1294 SMP Thu Jan 30 13:15:58 GMT 2020”,
“machine”: “armv7l”,
“processor”: “”
},
“memory”: {
“total”: 971055104,
“available”: 774840320,
“percent”: 20.2,
“used”: 122839040,
“free”: 101371904,
“active”: 435003392,
“inactive”: 332238848,
“buffers”: 47333376,
“cached”: 699510784,
“shared”: 6520832,
“slab”: 80441344
},
“disk”: {
“total”: 31090814976,
“used”: 3322875904,
“free”: 26457481216,
“percent”: 11.2
}
},
“configuration”: {
“satnogs_antenna”: “RX”,
“satnogs_api_token”: “[redacted]”,
“satnogs_rf_gain”: “32.8”,
“satnogs_rx_samp_rate”: “2.048e6”,
“satnogs_soapy_rx_device”: “config=rtlsdr”,
“satnogs_station_elev”: “29”,
“satnogs_station_id”: “715”,
“satnogs_station_lat”: “53.380”,
“satnogs_station_lon”: “-2.758”
}
}
------------[ copy end ]-------------

Any ideas?

20

If you are using an RTL-SDR, please set SATNOGS_SOAPY_RX_DEVICE to driver=rtlsdr as recommended in the wiki.

Maybe this fixes the issue.