Wait, run
sudo satnogs-setup
and clear the value
“satnogs_dev_args”: “serial”,
clear serial
should we sudo journalctl -f -u satnogs-client.service every do some observation on ground station?
I’ve let it go all this time when do observation
No, you have to run only when something goes wrong.
So, at 08:46:47 you have a message,… no waterfall data find…
Most probably its a wrong path somewhere, I am not an expert…
Lets wait to check and most probably somebody will find the mistake.
The log looks odd, I don’t run this type of system so have nothing to compare and test (all mine run under docker).
The unfortunate thing is that the SDR messages are missing, and also very unfortunate is that your private API token is visible in the log.
This is what a observation start looks like for me:
satnogsclient.scheduler.tasks - INFO - Spawning observer worker.
satnogsclient.observer.observer - INFO - Start rotctrl thread.
satnogsclient.observer.worker - INFO - Tracking initiated
satnogsclient.observer.observer - INFO - Start rigctrl thread.
satnogsclient.observer.worker - INFO - Tracking initiated
rig_init: rig does not have rx_range!!
network_open: hoststr=rigctld, portstr=4532
satnogsclient.observer.observer - INFO - Start gnuradio thread.
Found Rafael Micro R820T tuner
Found Rafael Micro R820T tuner
[INFO] Opening Generic RTL2832U OEM :: 1864...
Found Rafael Micro R820T tuner
[R82XX] PLL not locked!
[INFO] Using format CF32.
Allocating 15 zero-copy buffers
And stopping:
satnogsclient.observer.observer - INFO - Tracking stopped.
netrigctl_close: done status=Command completed successfully
satnogsclient.observer.worker - INFO - Tracking stopped.
satnogsclient.observer.worker - INFO - Tracking stopped.
satnogsclient.observer.observer - INFO - Observation Finished
I’m not sure the journalctl command is correct, or there is something else that causes the log to not contain this.
what should i do sir
I don’t have the answer to why the logs don’t contain the flowgraph/sdr messages, maybe @PE0SAT knows.
Regarding the settings, this is still in there, and I recommend removing it.
Also, lower the satnogs_log_level to INFO instead of DEBUG, that is what I always use as it is a good balance of messages.
Yes, indeed, for same command, my log contains info about RTL V4 Blog… here I can not find… but no remarks about not finding RTL or other errors.
Perhaps show all logs and keep an eye out for the satnogs stuff when the observation starts:
sudo journalctl -n 50 -f
When looking at this community entry, I am lost, there are some default settings changed that shouldn’t have changed.
We need to get back to a default config and then only change the values that are part of the setup @nhanifah13 is using.
What computer are you using, what exact SDR are you using, explaining the RF chain.
How is the setup connected to the Internet, are there firewalls of maybe proxies in place.
When you login to the system via ssh is dns working.
So back to basics and share as much information as possible.
The most basic configuration that uses a RTL-SDR looks like this:
(Removed my personal data, that will need to be entered by the ground station owner)
SATNOGS_API_TOKEN="xxxx"
SATNOGS_STATION_ID="xxxx"
SATNOGS_STATION_LAT="xxxx"
SATNOGS_STATION_LON="xxxx"
SATNOGS_STATION_ELEV="x"
SATNOGS_SOAPY_RX_DEVICE="driver=rtlsdr"
SATNOGS_RX_SAMP_RATE="2.048e6"
SATNOGS_ANTENNA="RX"
This information is taken from /etc/ansible/host_vars/localhost and is used when running sudo satnogs-setup
Here is the file that generated the above active satnogs-client config that is located in /etc/default
satnogs_antenna: RX
satnogs_api_token: xxxx
satnogs_rx_samp_rate: 2.048e6
satnogs_soapy_rx_device: driver=rtlsdr
satnogs_station_elev: 'x'
satnogs_station_id: 'xxxx'
satnogs_station_lat: 'xxxx'
satnogs_station_lon: 'xxxx'
This can help you to back to an initial working config and go from there.
i’m using HP 840G2 and RTL-SDR V3. For internet settings, I just followed the steps for configuring the Raspberry Pi on the Satnogs client. Previously I had also tried DNS testing on my network and the results were good
$ journalctl -f -u satnogs-client.service
– Journal begins at Tue 2023-11-14 21:44:27 GMT. –
Jul 04 18:29:54 raspberrypi satnogs-client[393]: apscheduler.executors.default - WARNING - Run time of job “post_data (trigger: interval[0:03:00], next run at: 2024-07-04 17:32:16 UTC)” was missed by 0:00:38.136521
Jul 04 18:30:16 raspberrypi satnogs-client[393]: satnogsclient.scheduler.tasks - DEBUG - Get jobs started
Jul 04 18:30:16 raspberrypi satnogs-client[393]: satnogsclient.scheduler.tasks - DEBUG - URL: https://network.satnogs.org/api/jobs/
Jul 04 18:30:16 raspberrypi satnogs-client[393]: satnogsclient.scheduler.tasks - DEBUG - Params: {‘ground_station’: 3587, ‘lat’: -6.975504, ‘lon’: 107.6293934, ‘alt’: 665}
Jul 04 18:30:16 raspberrypi satnogs-client[393]: satnogsclient.scheduler.tasks - DEBUG - Headers: {‘Authorization’: 'Token xxx
Jul 04 18:30:16 raspberrypi satnogs-client[393]: satnogsclient.scheduler.tasks - INFO - Trying to GET observation jobs from the network
Jul 04 18:30:16 raspberrypi satnogs-client[393]: urllib3.connectionpool - DEBUG - Starting new HTTPS connection (1): network.satnogs.org:443
Jul 04 18:30:17 raspberrypi satnogs-client[393]: urllib3.connectionpool - DEBUG - https://network.satnogs.org:443 “GET /api/jobs/?ground_station=3587&lat=-6.975 504&lon=107.6293934&alt=665 HTTP/1.1” 200 361
Jul 04 18:30:17 raspberrypi satnogs-client[393]: satnogsclient.scheduler.tasks - DEBUG - Adding new job: 9789267
Jul 04 18:30:17 raspberrypi satnogs-client[393]: satnogsclient.scheduler.tasks - DEBUG - Observation obj: {‘id’: 9789267, ‘start’: ‘2024-07-05T02:56:28Z’, ‘end’ : ‘2024-07-05T03:00:56Z’, ‘ground_station’: 3587, ‘tle0’: ‘0 NSL-2’, ‘tle1’: ‘1 55067U 23001BL 24186.46585654 .01063379 55412-3 22941-2 0 9992’, ‘tle2’: ‘2 55067 97.4045 258.0317 0009467 257.3010 102.7210 15.98476334 84043’, ‘frequenc y’: 401199531, ‘mode’: ‘PSK31’, ‘transmitter’: ‘3uR3VaFGvM4cKbxY6JzXoC’, ‘baud’: None}
Jul 04 18:31:16 raspberrypi satnogs-client[393]: satnogsclient.scheduler.tasks - DEBUG - Get jobs started
Jul 04 18:31:16 raspberrypi satnogs-client[393]: satnogsclient.scheduler.tasks - DEBUG - URL: https://network.satnogs.org/api/jobs/
Jul 04 18:31:16 raspberrypi satnogs-client[393]: satnogsclient.scheduler.tasks - DEBUG - Params: {‘ground_station’: 3587, ‘lat’: -6.975504, ‘lon’: 107.6293934, ‘alt’: 665}
That is good to hear and I don’t see any show stoppers, try to go back to a basic configuration.
Please also share your full RF chain, this will also help when optimize the RF gain settings after you have a working basic install/configuration.
what is the difference in using debug and info? I just followed step by step and adjusted the example results from the satnogs website
in the code we use a logger, and it has different levels of messages, where it gets more and more verbose for each level. selecting a certain level makes it possible to select a balance of very spammy to very quiet logs visible to the user.