Today I noticed that the update disabled auto-ranging on the waterfall from my station. It for some reason changed it from the default True to False. Just want this issue to me know.
This shouldn’t have changed. Can you check that it is not enabled in your config?
It did not change for me, too (as expected)!
My support report just after upgrading:
{
"versions": {
"satnogs-client": "1.2+1.gcfbefd4",
"satnogs-client-ansible": "202003221112",
"satnogs-flowgraphs": "1.0.1-1",
"gr-satnogs": "2.0.1+9+gdb67e42f-1",
"gr-soapy": "2.1.1-1",
"gnuradio": "3.8.1.0~rc1-2",
"satnogs-config": "0.9"
},
"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": "satnogs37-prod",
"release": "4.19.97-v7l+",
"version": "#1294 SMP Thu Jan 30 13:21:14 GMT 2020",
"machine": "armv7l",
"processor": ""
},
"memory": {
"total": 4095750144,
"available": 3541565440,
"percent": 13.5,
"used": 415543296,
"free": 3273236480,
"active": 500523008,
"inactive": 204382208,
"buffers": 39141376,
"cached": 367828992,
"shared": 8839168,
"slab": 55111680
},
"disk": {
"total": 15256010752,
"used": 3514273792,
"free": 11075616768,
"percent": 24.1
}
},
"configuration": {
"experimental": true,
"hamlib_utils_rot_enabled": false,
"satnogs_antenna": "RX",
"satnogs_api_token": "[redacted]",
"satnogs_log_level": "INFO",
"satnogs_network_api_url": "https://network.satnogs.org/api/",
"satnogs_rf_gain": 48,
"satnogs_rot_flip": true,
"satnogs_rot_flip_angle": "180",
"satnogs_rot_ip": "192.168.10.5",
"satnogs_rot_model": "ROT_MODEL_NETROTCTL",
"satnogs_rot_port": "192.168.10.5",
"satnogs_rx_device": "rtlsdr",
"satnogs_rx_samp_rate": "2.048e6",
"satnogs_setup_ansible_branch": "master",
"satnogs_soapy_rx_device": "driver=rtlsdr",
"satnogs_station_elev": 275,
"satnogs_station_id": 37,
"satnogs_station_lat": 50.749791,
"satnogs_station_lon": 6.216148
}
}
This broke some things for me. I had the dev args:
rtl,buffers=32,buflen=16384,bias=1
That gave an out of range error for rtl - I fixed that by simply removing it.
Now running with:
buffers=32,buflen=16384,bias=1
No errors now but my biasT doesn’t seem to activate but I do get message about the buffers 
What changed?
SoapySDR RTL module does not expose the biasT setting. There is a featur request on the project repository but it has not been implemented yet.
I guess all I can hope for is that I can use a pre-observation script now - before the update that way of doing it didn’t work so well.
Wish me luck - if not my hardware setup is broken.
Users have reported that it works.
Success! Manually installing rtl_biast and:
/home/pi/install/rtl-sdr-blog/build/src/rtl_biast -b 1
as pre-observation script seems to work.
5 Likes
Will this update require any autoscheduling updates/fixes?
I had it originally left as default then updated. And weirdly after the update it was changed to false with out my interaction with ansible. Causing a few of my observations to have weird looking water falls till I set it back to being the correct value of true.
Updated station with microsd card update as was on stretch, now on buster as the base ( as per option 2 of update directions)
re re run satnogs , everything looks ok , new menu shows
put in api key , etc as per guidelines , rebooted , power down etc …
station appears on network , in test mode but all observations blank
flushed usb … , all observations still blank ??
all sats tested are good performers usual at my location, a couple of purple results, mostly blank so reduced the gain to 11 as per instructions
rtrl test shows its good and working, same dongle as per always ( 7000+ observations) , usb unplugged etc all no improvement
all results still blank
station monitor 0.3.1 shows sats as they pass, no waterfall though ? not sure if this is a station or monitor issue ?
cant figure out how to post logs and screen shots, (advanced — support) , doesn’t produce any information, just sits there
Anyone any ideas have tried all the ideas in the other threads ?
else may have to start again from scratch with a fresh buster image ?
cheers
I moved your post to this topic as it fits here.
For the station monitor check this post SatNOGS station monitor v0.3.x - #26 by wose.
You can upload screenshots here or use an external site and paste here links, for example imgur. “Advanced → Support” sometimes take a little time before show the results.
Hi Fredy
thanks for the move …
had seen the station monitor post re working with new build ( thank you ) , it shows the pass, just no data hence more inclined its the rtl and data capture not the monitor.
Will try advanced support again tonight
Hi,
I’m posting here because I see another issue with Flowgraphs, but I don’t know enough to say if there’s a bigger/different issue. So apologies if this would be better in a new thread.
Following on from the problems resolved last week, I’ve run a normal upgrade and on clicking ‘Apply’ everything runs fine until:
Install SatNOGS Flowgraphs…
Retrying… (1 of 4)
Retrying… (2 of 4)
Retrying… (3 of 4)
localhost failed | msg: ‘/usr/bin/apt-get -y -o “Dpkg::Options::=–force-confdef” -o “Dpkg::Options::=–force-confold” install ‘satnogs-flowgraphs=1.0.1-1’’ failed: E: Unable to correct problems, you have held broken packages.
| stdout: Reading package lists…
Building dependency tree…
Reading state information…
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:The following packages have unmet dependencies:
satnogs-flowgraphs : Depends: gr-satnogs (< 2.1) but 2.1-1 is to be installed
| stderr: E: Unable to correct problems, you have held broken packages.
I’ve rebooted and run sudo satnogs-setup a few times, but the same things appear and passes no longer show a waterfall.
I also see:
Apr 01 19:13:57 piSatNOGS satnogs-client[347]: apscheduler.executors.default - ERROR - Job “spawn_observer (trigger: date[2020-04-01 19:13:56 UTC], next run at: 2020-04-01 19:13:56 UTC)” rai
Apr 01 19:13:57 piSatNOGS satnogs-client[347]: Traceback (most recent call last):
Apr 01 19:13:57 piSatNOGS satnogs-client[347]: File “/usr/lib/python3/dist-packages/apscheduler/executors/base.py”, line 125, in run_job
Apr 01 19:13:57 piSatNOGS satnogs-client[347]: retval = job.func(*job.args, **job.kwargs)
Apr 01 19:13:57 piSatNOGS satnogs-client[347]: File “/var/lib/satnogs/lib/python3.7/site-packages/satnogsclient/scheduler/tasks.py”, line 80, in spawn_observer
Apr 01 19:13:57 piSatNOGS satnogs-client[347]: observer.observe()
Apr 01 19:13:57 piSatNOGS satnogs-client[347]: File “/var/lib/satnogs/lib/python3.7/site-packages/satnogsclient/observer/observer.py”, line 152, in observe
Apr 01 19:13:57 piSatNOGS satnogs-client[347]: self.observation_decoded_data)
Apr 01 19:13:57 piSatNOGS satnogs-client[347]: File “/var/lib/satnogs/lib/python3.7/site-packages/satnogsclient/upsat/gnuradio_handler.py”, line 108, in exec_gnuradio
Apr 01 19:13:57 piSatNOGS satnogs-client[347]: proc = subprocess.Popen(args)
Apr 01 19:13:57 piSatNOGS satnogs-client[347]: File “/usr/lib/python3.7/subprocess.py”, line 775, in init
Apr 01 19:13:57 piSatNOGS satnogs-client[347]: restore_signals, start_new_session)
Apr 01 19:13:57 piSatNOGS satnogs-client[347]: File “/usr/lib/python3.7/subprocess.py”, line 1522, in _execute_child
Apr 01 19:13:57 piSatNOGS satnogs-client[347]: raise child_exception_type(errno_num, err_msg, err_filename)
Apr 01 19:13:57 piSatNOGS satnogs-client[347]: FileNotFoundError: [Errno 2] No such file or directory: ‘satnogs_fsk_ax25.py’: ‘satnogs_fsk_ax25.py’
Apr 01 19:19:23 piSatNOGS satnogs-client[347]: apscheduler.executors.default - ERROR - Job “spawn_observer (trigger: date[2020-04-01 19:19:22 UTC], next run at: 2020-04-01 19:19:22 UTC)” rai
Apr 01 19:19:23 piSatNOGS satnogs-client[347]: Traceback (most recent call last):
Apr 01 19:19:23 piSatNOGS satnogs-client[347]: File “/usr/lib/python3/dist-packages/apscheduler/executors/base.py”, line 125, in run_job
Apr 01 19:19:23 piSatNOGS satnogs-client[347]: retval = job.func(*job.args, **job.kwargs)
Apr 01 19:19:23 piSatNOGS satnogs-client[347]: File “/var/lib/satnogs/lib/python3.7/site-packages/satnogsclient/scheduler/tasks.py”, line 80, in spawn_observer
Apr 01 19:19:23 piSatNOGS satnogs-client[347]: observer.observe()
Apr 01 19:19:23 piSatNOGS satnogs-client[347]: File “/var/lib/satnogs/lib/python3.7/site-packages/satnogsclient/observer/observer.py”, line 152, in observe
Apr 01 19:19:23 piSatNOGS satnogs-client[347]: self.observation_decoded_data)
Apr 01 19:19:23 piSatNOGS satnogs-client[347]: File “/var/lib/satnogs/lib/python3.7/site-packages/satnogsclient/upsat/gnuradio_handler.py”, line 108, in exec_gnuradio
Apr 01 19:19:23 piSatNOGS satnogs-client[347]: proc = subprocess.Popen(args)
Apr 01 19:19:23 piSatNOGS satnogs-client[347]: File “/usr/lib/python3.7/subprocess.py”, line 775, in init
Apr 01 19:19:23 piSatNOGS satnogs-client[347]: restore_signals, start_new_session)
Apr 01 19:19:23 piSatNOGS satnogs-client[347]: File “/usr/lib/python3.7/subprocess.py”, line 1522, in _execute_child
Apr 01 19:19:23 piSatNOGS satnogs-client[347]: raise child_exception_type(errno_num, err_msg, err_filename)
Apr 01 19:19:23 piSatNOGS satnogs-client[347]: FileNotFoundError: [Errno 2] No such file or directory: ‘satnogs_cw_decoder.py’: ‘satnogs_cw_decoder.py’
Apr 01 19:26:53 piSatNOGS satnogs-client[347]: apscheduler.executors.default - ERROR - Job “spawn_observer (trigger: date[2020-04-01 19:26:52 UTC], next run at: 2020-04-01 19:26:52 UTC)” rai
Apr 01 19:26:53 piSatNOGS satnogs-client[347]: Traceback (most recent call last):
Apr 01 19:26:53 piSatNOGS satnogs-client[347]: File “/usr/lib/python3/dist-packages/apscheduler/executors/base.py”, line 125, in run_job
Apr 01 19:26:53 piSatNOGS satnogs-client[347]: retval = job.func(*job.args, **job.kwargs)
Apr 01 19:26:53 piSatNOGS satnogs-client[347]: File “/var/lib/satnogs/lib/python3.7/site-packages/satnogsclient/scheduler/tasks.py”, line 80, in spawn_observer
Apr 01 19:26:53 piSatNOGS satnogs-client[347]: observer.observe()
Apr 01 19:26:53 piSatNOGS satnogs-client[347]: File “/var/lib/satnogs/lib/python3.7/site-packages/satnogsclient/observer/observer.py”, line 152, in observe
Apr 01 19:26:53 piSatNOGS satnogs-client[347]: self.observation_decoded_data)
Apr 01 19:26:53 piSatNOGS satnogs-client[347]: File “/var/lib/satnogs/lib/python3.7/site-packages/satnogsclient/upsat/gnuradio_handler.py”, line 108, in exec_gnuradio
Apr 01 19:26:53 piSatNOGS satnogs-client[347]: proc = subprocess.Popen(args)
Apr 01 19:26:53 piSatNOGS satnogs-client[347]: File “/usr/lib/python3.7/subprocess.py”, line 775, in init
Apr 01 19:26:53 piSatNOGS satnogs-client[347]: restore_signals, start_new_session)
Apr 01 19:26:53 piSatNOGS satnogs-client[347]: File “/usr/lib/python3.7/subprocess.py”, line 1522, in _execute_child
Apr 01 19:26:53 piSatNOGS satnogs-client[347]: raise child_exception_type(errno_num, err_msg, err_filename)
Apr 01 19:26:53 piSatNOGS satnogs-client[347]: FileNotFoundError: [Errno 2] No such file or directory: ‘satnogs_noaa_apt_decoder.py’: ‘satnogs_noaa_apt_decoder.py’
Any ideas how I handle this please?
Thanks
We track the issue at https://gitlab.com/librespacefoundation/satnogs/satnogs-client-ansible/-/issues/75
Thanks. I’m not sure how to recover the situation. I’ve run the upgrade from the setup again and the problem is still there. Is there a way to resolve it? Or do I need to reinstall from scratch?
Did you change from stable to testing or vice versa?
No. I just ran satnogs-setup and upgrade followed by apply. I’ve not changed from the default.
New packages have just been released. Selecting Update should resolve your issue by bumping all software to the latest.
Thanks - that worked and I’m back up and running again. 