Hi,
- I saw your tweet is the Pi combining tinyGS and the satnogs-client. Maybe there are conflicting software versions?
This is impossible because TinyGS is running on a dedicated LoRa module (heltec) and is connected over the WiFi AP that is configured on the RPI. Also, the setup worked before I moved it a couple of moths ago.
- Was the system previously running debian buster? Here a detailed post on the upgrade to bullseye
It was running “Linux satnogs 5.15.84-v7l+ #1613 SMP Thu Jan 5 12:01:26 GMT 2023 armv7l” from the beginning as I download the image.
-
sudo satnogs-setupoption Advanced option Support and share the output.
As requested:
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-06-06T09:35:22.553403+00:00",
"distribution": {
"DESCRIPTION": "Raspbian GNU/Linux 11 (bullseye)",
"RELEASE": "11",
"CODENAME": "bullseye",
"ID": "Raspbian"
},
"pending-updates": false,
"platform": {
"system": "Linux",
"node": "satnogs",
"release": "5.15.84-v7l+",
"version": "#1613 SMP Thu Jan 5 12:01:26 GMT 2023",
"machine": "armv7l"
},
"memory": {
"total": 4025397248,
"available": 3706580992,
"percent": 7.9,
"used": 157184000,
"free": 2559819776,
"active": 543281152,
"inactive": 768983040,
"buffers": 120283136,
"cached": 1188110336,
"shared": 954368,
"slab": 97710080
},
"disk": {
"total": 15336914944,
"used": 5792321536,
"free": 8866578432,
"percent": 39.5
}
},
"configuration": {
"satnogs_antenna": "RX",
"satnogs_api_token": "[redacted]",
"satnogs_rx_samp_rate": "2.048e6",
"satnogs_soapy_rx_device": "driver=rtlsdr",
"satnogs_station_elev": "25",
"satnogs_station_id": "2849",
"satnogs_station_lat": "51.98773",
"satnogs_station_lon": "5.95154"
}
}
------------[ copy end ]-------------