[RESOLVED] 1.8.1 client requires root access to /usr/local/bin?

I just updated to 1.8.1 and everything is working.

I would like to add my pre & post script files I had with my previous 1.6 client to /usr/local/bin but it says I don’t have permission.

I’m still a newb at linux so I use WinSCP as a file manager and I get this error when I try to copy my scripts over.

How do I fix this?

Thanks in advance,
tz

yes, those are owned by root, as are most files in /usr/local

from ssh/terminal:
sudo chown satnogs:satnogs /usr/local/bin/
change satnogs:satnogs to the user:group you use.

other solution is to scp them to the home dir and copy with sudo.

That worked, thanks @SA2KNG

now to get gr-satellites installed…

1 Like

If you’re using satnogs repos, I have added the latest build there, so installing is easy.
sudo apt install gr-satellites
and it should install this one:
ii gr-satellites 3.15.1-1 arm64 Collection of satellite telemetry signal decoders

@SA2KNG Thanks! It looks like that worked!

pi@raspberrypi:~ $ gr_satellites --version
gr_satellites v3.15.1
Copyright (C) 2020 Daniel Estevez
License GPLv3+: GNU GPL version 3 or later <https://gnu.org/licenses/gpl.html>.
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
pi@raspberrypi:~ $

Where on here do I need to continue with the setup?

Another question I have, and I searched the wikis, is I’d like to run the decoders on as many satellites as possible but I don’t want to send duplicate data to the satnogs db. So how do I find out which satellites satnogs decodes so I can enter in the rest in grsat-wrapper.sh? If memory serves, commenting out the line “SELECTED=…” will try and decode all of the observations.

Thanks again!
K3TZ

Next steps would be the from download and forward. Do all this via ssh, not ftp/scp.
Please do monitor the logs from satnogs-client and see that it is all working. There will be some extra log messages from this script.

Afaict there has been no big complaints on duplicate frames, sometimes the two demodulates different weak frames so complementing eachother. Perhaps support for blacklisting would also be a good idea but there has been no demand for it.

@SA2KNG Ok, that’s what I thought but wanted to make sure. I setup a few observations and I think I broke something.

This is what I get in the log:

Dec 16 20:50:46 raspberrypi satnogs-client[413]: satnogsclient.scheduler.tasks - INFO - Spawning observer worker.
Dec 16 20:51:43 raspberrypi satnogs-client[413]: satnogsclient.scheduler.tasks - INFO - Trying to GET observation jobs from the network
Dec 16 20:52:43 raspberrypi satnogs-client[413]: satnogsclient.scheduler.tasks - INFO - Trying to GET observation jobs from the network
Dec 16 20:53:43 raspberrypi satnogs-client[413]: satnogsclient.scheduler.tasks - INFO - Trying to GET observation jobs from the network
Dec 16 20:53:43 raspberrypi satnogs-client[413]: satnogsclient.scheduler.tasks - INFO - Post data started
Dec 16 20:54:43 raspberrypi satnogs-client[413]: satnogsclient.scheduler.tasks - INFO - Trying to GET observation jobs from the network
Dec 16 20:55:43 raspberrypi satnogs-client[413]: satnogsclient.scheduler.tasks - INFO - Trying to GET observation jobs from the network
Dec 16 20:56:43 raspberrypi satnogs-client[413]: satnogsclient.scheduler.tasks - INFO - Trying to GET observation jobs from the network
Dec 16 20:56:43 raspberrypi satnogs-client[413]: satnogsclient.scheduler.tasks - INFO - Post data started
Dec 16 20:57:28 raspberrypi satnogs-client[413]: satnogsclient.scheduler.tasks - ERROR - Observer job lock acquiring timed out.
Dec 16 20:57:43 raspberrypi satnogs-client[413]: satnogsclient.scheduler.tasks - INFO - Trying to GET observation jobs from the network
D

Any ideas?

Thanks!

This is indicating a failed obs, where lockfile didn’t get removed or the previous flowgraph is still running. I think it is mostly related to flowgraph exiting due to bad parameters or sdr problems. Most other problems doesn’t affect future observations.
Increase log level with SATNOGS_LOG_LEVEL="INFO" and restart the client, then you should see more details around the problem.

@SA2KNG Ok, I think I have it working now. I forgot a few steps that I had done before. I started from scratch and had a successful observation 6904247

Dec 20 20:11:35 raspberrypi satnogs-client[1561]: satnogsclient.scheduler.tasks - INFO - Spawning observer worker.
Dec 20 20:11:35 raspberrypi satnogs-client[1561]: satnogsclient.observer.observer - INFO - Executing pre-observation script.
Dec 20 20:11:35 raspberrypi satnogs-client[1722]: Found 1 device(s):
Dec 20 20:11:35 raspberrypi satnogs-client[1722]:   0:  Realtek, RTL2838UHIDIR, SN: 00000001
Dec 20 20:11:35 raspberrypi satnogs-client[1722]: Using device 0: Generic RTL2832U OEM
Dec 20 20:11:35 raspberrypi satnogs-client[1722]: Found Rafael Micro R820T tuner
Dec 20 20:11:35 raspberrypi satnogs-client[1728]: gr-satellites: Observation: 6904247, Norad: 39444, Name: 0_FUNCUBE_1, Script: satnogs_bpsk.py
Dec 20 20:11:35 raspberrypi satnogs-client[1728]: gr-satellites: Starting observation 6904247
Dec 20 20:11:36 raspberrypi satnogs-client[1728]: gr-satellites: running at 48000 sps
Dec 20 20:11:36 raspberrypi satnogs-client[1561]: satnogsclient.observer.observer - INFO - Start rotctrl thread.
Dec 20 20:11:36 raspberrypi satnogs-client[1561]: satnogsclient.observer.worker - INFO - Tracking initiated
Dec 20 20:11:36 raspberrypi satnogs-client[1561]: rot_init called
Dec 20 20:11:36 raspberrypi satnogs-client[1561]: initrots4_dummy: _init called
Dec 20 20:11:36 raspberrypi satnogs-client[1561]: rot_register (1)
Dec 20 20:11:36 raspberrypi satnogs-client[1561]: rot_register (2)
Dec 20 20:11:36 raspberrypi satnogs-client[1561]: dummy_rot_init called
Dec 20 20:11:36 raspberrypi satnogs-client[1561]: rot_open called
Dec 20 20:11:36 raspberrypi satnogs-client[1561]: dummy_rot_open called
Dec 20 20:11:36 raspberrypi satnogs-client[1561]: rot_get_position called
Dec 20 20:11:36 raspberrypi satnogs-client[1561]: dummy_rot_get_position called
Dec 20 20:11:36 raspberrypi satnogs-client[1561]: rot_get_position: got az=0.00, el=0.00
Dec 20 20:11:36 raspberrypi satnogs-client[1561]: rot_set_position called az=153.97 el=10.13
Dec 20 20:11:36 raspberrypi satnogs-client[1561]: rot_set_position: south_zero=0
Dec 20 20:11:36 raspberrypi satnogs-client[1561]: dummy_rot_set_position called: 153.97 10.13
Dec 20 20:11:36 raspberrypi satnogs-client[1561]: satnogsclient.observer.observer - INFO - Start rigctrl thread.
Dec 20 20:11:36 raspberrypi satnogs-client[1561]: satnogsclient.observer.worker - INFO - Tracking initiated
Dec 20 20:11:36 raspberrypi satnogs-client[1561]: rig_init: rig does not have rx_range!!
Dec 20 20:11:36 raspberrypi satnogs-client[1561]: network_open: hoststr=127.0.0.1, portstr=4532
Dec 20 20:11:37 raspberrypi satnogs-client[1561]: satnogsclient.observer.observer - INFO - Start gnuradio thread.
Dec 20 20:11:39 raspberrypi satnogs-client[1767]: Found Rafael Micro R820T tuner
Dec 20 20:11:39 raspberrypi satnogs-client[1767]: [INFO] Opening Generic RTL2832U OEM :: 00000001...
Dec 20 20:11:39 raspberrypi satnogs-client[1767]: Found Rafael Micro R820T tuner
Dec 20 20:11:39 raspberrypi satnogs-client[1767]: [R82XX] PLL not locked!
Dec 20 20:11:39 raspberrypi satnogs-client[1767]: [INFO] Using format CF32.
Dec 20 20:11:40 raspberrypi satnogs-client[1767]: Allocating 15 zero-copy buffers
Dec 20 20:12:25 raspberrypi satnogs-client[1561]: satnogsclient.scheduler.tasks - INFO - Trying to GET observation jobs from the network
Dec 20 20:13:25 raspberrypi satnogs-client[1561]: satnogsclient.scheduler.tasks - INFO - Trying to GET observation jobs from the network
Dec 20 20:13:25 raspberrypi satnogs-client[1561]: satnogsclient.scheduler.tasks - INFO - Post data started
Dec 20 20:14:25 raspberrypi satnogs-client[1561]: satnogsclient.scheduler.tasks - INFO - Trying to GET observation jobs from the network
Dec 20 20:15:25 raspberrypi satnogs-client[1561]: satnogsclient.scheduler.tasks - INFO - Trying to GET observation jobs from the network
Dec 20 20:16:25 raspberrypi satnogs-client[1561]: satnogsclient.scheduler.tasks - INFO - Trying to GET observation jobs from the network
Dec 20 20:16:25 raspberrypi satnogs-client[1561]: satnogsclient.scheduler.tasks - INFO - Post data started
Dec 20 20:17:25 raspberrypi satnogs-client[1561]: satnogsclient.scheduler.tasks - INFO - Trying to GET observation jobs from the network
Dec 20 20:18:25 raspberrypi satnogs-client[1561]: satnogsclient.scheduler.tasks - INFO - Trying to GET observation jobs from the network
Dec 20 20:19:25 raspberrypi satnogs-client[1561]: satnogsclient.scheduler.tasks - INFO - Trying to GET observation jobs from the network
Dec 20 20:19:25 raspberrypi satnogs-client[1561]: satnogsclient.scheduler.tasks - INFO - Post data started
Dec 20 20:20:11 raspberrypi satnogs-client[1561]: satnogsclient.observer.observer - INFO - Tracking stopped.
Dec 20 20:20:11 raspberrypi satnogs-client[1561]: netrigctl_close: done status=Command completed successfully
Dec 20 20:20:11 raspberrypi satnogs-client[1561]: satnogsclient.observer.worker - INFO - Tracking stopped.
Dec 20 20:20:11 raspberrypi satnogs-client[1561]: satnogsclient.observer.worker - INFO - Tracking stopped.
Dec 20 20:20:11 raspberrypi satnogs-client[1561]: satnogsclient.observer.observer - INFO - Observation Finished
Dec 20 20:20:11 raspberrypi satnogs-client[1561]: satnogsclient.observer.observer - INFO - Executing post-observation script.
Dec 20 20:20:12 raspberrypi satnogs-client[1908]: gr-satellites: Observation: 6904247, Norad: 39444, Name: 0_FUNCUBE_1, Script: satnogs_bpsk.py
Dec 20 20:20:12 raspberrypi satnogs-client[1908]: gr-satellites: Stopping observation 6904247
Dec 20 20:20:12 raspberrypi satnogs-client[1924]: Found 1 device(s):
Dec 20 20:20:12 raspberrypi satnogs-client[1924]:   0:  Realtek, RTL2838UHIDIR, SN: 00000001
Dec 20 20:20:12 raspberrypi satnogs-client[1924]: Using device 0: Generic RTL2832U OEM
Dec 20 20:20:12 raspberrypi satnogs-client[1924]: Found Rafael Micro R820T tuner
Dec 20 20:20:12 raspberrypi satnogs-client[1561]: satnogsclient.observer.observer - INFO - Rename encoded file for uploading finished
Dec 20 20:20:12 raspberrypi satnogs-client[1561]: satnogsclient.observer.observer - INFO - Creating waterfall plot.
Dec 20 20:20:12 raspberrypi satnogs-client[1561]: satnogsclient.waterfall - INFO - Reading waterfall file
Dec 20 20:20:25 raspberrypi satnogs-client[1561]: satnogsclient.scheduler.tasks - INFO - Trying to GET observation jobs from the network
Dec 20 20:21:25 raspberrypi satnogs-client[1561]: satnogsclient.scheduler.tasks - INFO - Trying to GET observation jobs from the network
Dec 20 20:22:25 raspberrypi satnogs-client[1561]: satnogsclient.scheduler.tasks - INFO - Trying to GET observation jobs from the network
Dec 20 20:22:25 raspberrypi satnogs-client[1561]: satnogsclient.scheduler.tasks - INFO - Post data started
Dec 20 20:22:25 raspberrypi satnogs-client[1561]: satnogsclient.scheduler.tasks - INFO - Trying to PUT observation data for id: 6904247
Dec 20 20:22:28 raspberrypi satnogs-client[1561]: satnogsclient.scheduler.tasks - INFO - Upload successful.
Dec 20 20:22:28 raspberrypi satnogs-client[1561]: satnogsclient.scheduler.tasks - INFO - Trying to PUT observation data for id: 6904247
Dec 20 20:22:43 raspberrypi satnogs-client[1561]: satnogsclient.scheduler.tasks - INFO - Upload successful.

The antenna I have is just a small whip I am using for testing the station, so I didn’t expect to receive anything.

One thing that is still puzzling me is the rig control error: rig_init: rig does not have rx_range!!, I’m not sure why that is happening.

Thanks for your help, time to get the outside antenna back up!

73,
-K3TZ

There’s a bunch of odd errors/warnings in the new client, many of them benign. I’d ignore them until something is not working.
Good to see it’s working (: There’s always improvements that can be made and it’s a fun hobby!

1 Like