I usually have slow downloads of satnogs observations, but the last couple of days have been very fast. Just another data point.
Yeah, something’s changed in the last few hours/days.
I was getting awfully slow loading waterfalls and audio on a reasonably fast ‘fibre’ (to the cabinet not the home) connection here in the UK - waterfalls visibly slow; audio progress bar running for 10s of seconds. Just assumed that was normal, although it felt like it was something going wrong in my local browser as it affected the whole Chrome UI - other tabs hanging too. But it’s now blisteringly fast.
Apologies for the late response; I ran update and copied thee support page again, doesn’t seem to have fixed it. The support info follows:
{
“versions”: {
“satnogs-client”: “1.3.1”,
“satnogs-client-ansible”: “202004031132”,
“satnogs-flowgraphs”: “1.1.1-1”,
“gr-satnogs”: “2.1.2-1”,
“gr-soapy”: “2.1.2-1”,
“gnuradio”: “3.8.1.0~rc1-2”,
“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”: false,
“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”: 971059200,
“available”: 711073792,
“percent”: 26.8,
“used”: 182505472,
“free”: 98930688,
“active”: 488968192,
“inactive”: 266522624,
“buffers”: 64270336,
“cached”: 625352704,
“shared”: 10534912,
“slab”: 92971008
},
“disk”: {
“total”: 31090814976,
“used”: 3765264384,
“free”: 26015092736,
“percent”: 12.6
}
},
“configuration”: {
“satnogs_antenna”: “RX”,
“satnogs_api_token”: “[redacted]”,
“satnogs_ppm_error”: “0”,
“satnogs_rf_gain”: “14.4”,
“satnogs_rx_samp_rate”: “2.048e6”,
“satnogs_soapy_rx_device”: “driver=rtlsdr”,
“satnogs_station_elev”: “170”,
“satnogs_station_id”: “1051”,
“satnogs_station_lat”: “34.60225”,
“satnogs_station_lon”: “-88.547191”
}
}
Hmm… It seems to have returned an observation somewhat successfully, I’ll schedule more and post more details later.
It seems that running updates as @vk5qi recommended has fixed the problem, imagine that…I will continue to watch it for a day or two, but it seems to be working now. Thank you!
1 Like