I would like to get help with the next 2 question. I am a newbie to this software and don’t now much about it. Tried to decode some cw data 2 days ago but it faild. If I look at my screen from Raspberry I see this failure message. First wich command do I need to use to get back to the command-line? And second I instal the Image from scratch but now it came with this failure message and I don’t see any waterfall or anythins else. Anyone know a solution?
John.
ctrl+c should get you back to the command line
K3RLD, thanks for the fast answer. 
Johan.
If you can provide us with the ‘support’ output from satnogs-setup, that will help check you have all your settings correct.
You can find this by running: sudo satnogs-setup
Then navigating to Advanced -> Support
Hello VK5QI, thanks for the answer. If I am back home this evening will do this.
Johan.
May be you need to update + apply from satnogs-setup another time
I tried to update and apply it but that is not working. Got a failure on that. So maybe that is the problem. If I look at the suport file I see also at “pending-updates” that there is false behind it. So maybe thats the problem. But no idea how to change it so it will work.
Johan.
OK I think the issue is that sample rate is not valid for an Airspy.
If you run: SoapySDRUtil --probe | grep Sample
It should give you a list of valid sample rates for your SDR.
For an Airspy Mini i think the valid sample rates are 3 MHz and 6 MHz, (3e6, 6e6), and for the Airspy R2… can’t remember!
It’s also worth noting that pretty much all Raspberry Pi’s (even the RPi 4) seem to have trouble dealing with the high sample rates from the Airspy units.
Thank you very much for this answer Mark. First I am going to try to change the sample rate today to see if we will get something working. Otherwise I am going to order a rtl sdr dongle also, can get it easily in my neighbourhood.
If you start a new project like this and it is not working right away it is always difficult where the failer could be. Yesterday evening read a lot message on this forum about this subject but also other issues. Always nice to see that people are willing to help others.
If there are updates then I will post it at this tread.
Johan.
Good morning,
just installed my Satnogs station, but no luck:
{
“versions”: {
“satnogs-client”: “1.3.2”,
“satnogs-client-ansible”: “202006062329”,
“satnogs-flowgraphs”: “1.2.1-1”,
“gr-satnogs”: “2.1.2.1-1”,
“gr-soapy”: “2.1.3-1”,
“gnuradio”: “3.8.0.0-6”,
“satnogs-config”: “0.10.2”
},
“state”: {
“is-applied”: true,
“pending-tags”: null
},
“system”: {
“date”: “2020-06-14T07:01:50.833578+00:00”,
“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-v7l+”,
“version”: “#1294 SMP Thu Jan 30 13:21:14 GMT 2020”,
“machine”: “armv7l”,
“processor”: “”
},
“memory”: {
“total”: 4095750144,
“available”: 3780734976,
“percent”: 7.7,
“used”: 170213376,
“free”: 3497779200,
“active”: 392212480,
“inactive”: 74014720,
“buffers”: 32002048,
“cached”: 395755520,
“shared”: 8798208,
“slab”: 71892992
},
“disk”: {
“total”: 62707105792,
“used”: 3228598272,
“free”: 56883810304,
“percent”: 5.4
}
},
“configuration”: {
“satnogs_antenna”: “RX”,
“satnogs_api_token”: “[redacted]”,
“satnogs_rf_gain”: “28”,
“satnogs_rx_samp_rate”: “2.048e6”,
“satnogs_soapy_rx_device”: “driver=rtlsdr”,
“satnogs_station_elev”: “380”,
“satnogs_station_id”: “1027”,
“satnogs_station_lat”: “45.350”,
“satnogs_station_lon”: “7.690”
}
}
Any observation fails with something like:
Jun 13 07:00:38 raspberrypi satnogs-client[22391]: rot_init called
Jun 13 07:00:38 raspberrypi satnogs-client[22391]: dummy: _init called
Jun 13 07:00:38 raspberrypi satnogs-client[22391]: rot_register (1)
Jun 13 07:00:38 raspberrypi satnogs-client[22391]: rot_register (2)
Jun 13 07:00:38 raspberrypi satnogs-client[22391]: dummy_rot_init called
Jun 13 07:00:38 raspberrypi satnogs-client[22391]: rot_open called
Jun 13 07:00:38 raspberrypi satnogs-client[22391]: dummy_rot_open called
Jun 13 07:00:38 raspberrypi satnogs-client[22391]: rot_get_position called
Jun 13 07:00:38 raspberrypi satnogs-client[22391]: dummy_rot_get_position called
Jun 13 07:00:38 raspberrypi satnogs-client[22391]: rot_set_position called
Jun 13 07:00:38 raspberrypi satnogs-client[22391]: dummy_rot_set_position called: 0.41 4.96
Jun 13 07:00:40 raspberrypi satnogs-client[22391]: Found Rafael Micro R820T tuner
Jun 13 07:00:40 raspberrypi satnogs-client[22391]: Found Rafael Micro R820T tuner
Jun 13 07:00:41 raspberrypi satnogs-client[22391]: [R82XX] PLL not locked!
Jun 13 07:00:41 raspberrypi satnogs-client[22391]: [INFO] Using format CF32.
Jun 13 07:00:41 raspberrypi satnogs-client[22391]: Could not find port: freq in:
Jun 13 07:00:41 raspberrypi satnogs-client[22391]: system
Jun 13 07:00:41 raspberrypi satnogs-client[22391]: freq
Jun 13 07:00:41 raspberrypi satnogs-client[22391]: 3
Jun 13 07:00:41 raspberrypi satnogs-client[22391]: Traceback (most recent call last):
Jun 13 07:00:41 raspberrypi satnogs-client[22391]: File “/usr/bin/satnogs_noaa_apt_decoder.py”, line 454, in
Jun 13 07:00:41 raspberrypi satnogs-client[22391]: main()
Jun 13 07:00:41 raspberrypi satnogs-client[22391]: File “/usr/bin/satnogs_noaa_apt_decoder.py”, line 439, in main
Jun 13 07:00:41 raspberrypi satnogs-client[22391]: tb = top_block_cls(antenna=options.antenna, bb_freq=options.bb_freq, bw=options.bw, dc_removal=options.dc_removal,
Jun 13 07:00:41 raspberrypi satnogs-client[22391]: File “/usr/bin/satnogs_noaa_apt_decoder.py”, line 124, in init
Jun 13 07:00:41 raspberrypi satnogs-client[22391]: self.satnogs_doppler_compensation_0 = satnogs.doppler_compensation(samp_rate_rx, rx_freq, lo_offset, 441604, 1,
Jun 13 07:00:41 raspberrypi satnogs-client[22391]: File “/usr/lib/python3/dist-packages/satnogs/doppler_compensation.py”, line 147, in init
Jun 13 07:00:41 raspberrypi satnogs-client[22391]: self.doppler, “freq”)
Thanks for support.
Piero IZ1ERR
Solved updating gnu-radio to version 3.8.1
Hello Mark and others, just switch from my Airspy dongle to a blue RTLSDR dongle. After I changed my configuration, put some new observations on my ground station and then run journal ctl -f -u satnogs-client.service. As what I did in my first picture from this message, Till my surprise there are NO failures anymore to see. It looks like satnogs start and stop every copple of minutes, Lets hope that he now will decode and create a waterfall after the first observations.
Fingers crossed.
Johan.
Hello Guys, my first Observation with the new dongle nr. #2391819 from NOAA-19 at around 18:00 utc was a succes! Both the waterfall and the audio is recorded and send to my ground station PE9DX. So I am very happy that it is working now.
Now I can start working at the hardware. This first observation from NOAA was with a 144 MHz antenne and no LNA.
Like to thank all the guys who gave a helping hand at my questions.
Greetings,
Johan.
