SatNOGS Wiki - User contributions [en]

SatNOGS Setup Legacy

2021-04-12T18:56:55Z

Jacquin01: /* Initial Setup */

==Introduction==
<code>satnogs-setup</code> provides a set of scripts for configuring a '''SatNOGS Client''' system. <code>satnogs-setup</code> main function is to bring up a menu-driven console configuration utility and provision the system using [[SatNOGS Client Ansible|Ansible]].

==Initial Setup==
Before starting <code>satnogs-setup</code>, ensure the Raspberry Pi is up to date. This can be done with <code>sudo apt update</code> and then <code>sudo apt upgrade</code>.

(See: [[Troubleshooting#apt-get update: connection failed]] ).

After the first boot of the system, packages and the configuration tool itself '''must be updated'''. Follow the [[SatNOGS Client Setup#Updating SatNOGS Client Software|Updating]] instruction found below.

To configure a '''SatNOGS Client''' system:

#SSH into the system and run <code>sudo satnogs-setup</code>; this will bring up the configuration menu
#Set '''all''' options in '''Basic Configuration''' (see below)
#Select <code>Apply</code> and the Raspberry Pi will configure itself; this may take some time
#Select <code>Back</code> to exit
{{Message|You can always reconfigure the software by running <code>sudo satnogs-setup</code> again.}}
===Basic Configuration===
{| class="wikitable"
!Setting
!Description
|-
|<code>SATNOGS_API_TOKEN</code>
|The API token assigned to your ground station on the SatNOGS Network website, please don’t share your api key as this can give access to anyone to upload and change things in network related to your station and its observations.

To find your API token, log in to [https://network.satnogs.org network.satnogs.org], click on the user icon at the top right corner and then click on the "Dashboard" option. On the top of the dashboard page right under the user icon click the button "API key" to show your API token.
|-
|<code>SATNOGS_SOAPY_RX_DEVICE</code>
|If you are using an RTL-SDR, this is <code>driver=rtlsdr</code>. For other devices tested configurations can be found at [[Software_Defined_Radio]].

See [https://github.com/pothosware/SoapyRTLSDR/wiki#modules pothosware/SoapyRTLSDR/wiki#modules] for other SDR modules (linked in the navigation bar at the right side of the page). If multiple devices are attached to your station you should also specify the serial of the desired device here, e.g. <code>driver=uhd,serial=3164495</code>.
|-
|<code>SATNOGS_ANTENNA</code>
|If you are using an RTL-SDR, this is <code>RX</code>. For other devices tested configurations can be found at [[Software_Defined_Radio]].

If your device is not listed there yet, use <code><nowiki>SoapySDRUtil --probe 2>&1| grep Antennas</nowiki></code> to get available antennas.
|-
|<code>SATNOGS_RX_SAMP_RATE</code>
|Specify the receiver sampling rate. Recommended value for RTL-SDR: <code>2.048e6</code> (for 2Msps), other devices will need different sample rates described at [[Software_Defined_Radio]] .

The command <code><nowiki>SoapySDRUtil --probe 2>&1 | grep Sample</nowiki></code> can be used to find all valid sample rates.
|-
|<code>SATNOGS_RF_GAIN</code>
|RF Gain value for your SDR hardware.

Run <code>SoapySDRUtil --probe</code> to see all possible gain values for your hardware.
Example: For RTL-SDR without pre-amp, 32.8 is a good starting value. Follow [[Omnidirectional Station How To#Setting the gain|Setting the gain]] to find a good gain value.
|-
|<code>SATNOGS_STATION_ELEV</code>
|The height of your ground station above sea level in metres.
|-
|<code>SATNOGS_STATION_ID</code>
|The '''numeric ID''' assigned to your station in the SatNOGS Network site when the groundstation was created.
|-
|<code>SATNOGS_STATION_LAT</code>
|The latitude of your station. North is positive, south is negative.
|-
|<code>SATNOGS_STATION_LON</code>
|The longitude of your station. East is positive, west is negative.
|}

==Advanced Setup==
{{Warning|Changes to the following settings may be required to optimise station performance, or enable support for additional features (e.g. rotator control)}}A more detailed description on setting up a development environment using the SatNOGS reference setup is given in [[SatNOGS_Client_Development]].

NOTE: To get your station online, you need to set SATNOGS_NETWORK_API_URL to https://network.satnogs.org/api/
{| class="wikitable"
!Setting
!Description
|-
|<code>SATNOGS_PPM_ERROR</code>
|The local oscillator frequency deviation in ppm.
|-
|<code>SATNOGS_RX_BANDWIDTH</code>
|Soapy baseband filter bandwidth [https://github.com/pothosware/SoapySDR/blob/a489f3dca9d3ccd9b276b95a608ac3ef0299f635/include/SoapySDR/Device.hpp#L904-L910] of RX Channel 0 in Hz (only available on specific devices). TODO: Testing.
|-
|<code>SATNOGS_DEV_ARGS</code>
|Soapy device arguments (currently only accepting the <code>serial</code> key successfully) and stream arguments.
NOTE: This parameter / its meaning might change in the near future, see issue [https://gitlab.com/librespacefoundation/satnogs/satnogs-client/-/issues/373 satnogs-client#373].
|-
|<code>SATNOGS_GAIN_MODE</code>
|Choose the gain mode:

*<code>"Overall"</code> (default): Set the gain with the single value from <code>SATNOGS_RF_GAIN</code>
*<code>"Settings Field"</code>: Ignore <code>SATNOGS_RF_GAIN</code>, use the settings from <code>SATNOGS_OTHER_SETTINGS</code> instead
|-
|<code>SATNOGS_STREAM_ARGS</code>
|
|-
|<code>SATNOGS_TUNE_ARGS</code>
|
|-
|<code>SATNOGS_OTHER_SETTINGS</code>
|Only available if <code>SATNOGS_GAIN_MODE</code>is<code>"Settings Field"</code>.
Available gain settings can be retrieved using <code>SoapySDRUtil --probe="driver=xxxx`</code>

Example for Airspy: Use<code>"LNA=12,MIX=8,VGA=11"</code>See also: [[SDR#Airspy|Airspy support]]
|-
|<code>SATNOGS_DC_REMOVAL</code>
|
|-
|<code>SATNOGS_BB_FREQ</code>
|
|-
|<code>SATNOGS_LO_OFFSET</code>
|Don't use this parameter to correct for the local oscillator frequency deviation, use <code>SATNOGS_PPM_ERROR</code> instead!
To avoid the SDR carrier at the DC the LO is shifted from the actual frequency a little. Default: <code>100e3</code> (100 kHz)
|-
|
|
|-
|<code>SATNOGS_ROT_MODEL</code>
|Hamlib rotator model. If you don't have a rotator (like the [[No rotator|No rotator setup]]), leave it empty.
Use the macro name for your rotator model from this [https://gist.github.com/kerel-fs/2354ff9c082cd3c1594afc38c67bc32a#hamlib-release-33 list of rotator models in Hamlib]. If you are connecting to a separate rotctld instance, use <code>ROT_MODEL_NETROTCTL</code>
|-
|<code>SATNOGS_ROT_BAUD</code>
|Baud rate for Hamlib rotator serial port, if using a serial-connected rotator.
|-
|<code>SATNOGS_ROT_PORT</code>
|Serial port for Hamlib rotator, OR the network address of a rotctld instance (e.g. <code>localhost:4533</code> )
|-
|<code>SATNOGS_ROT_THRESHOLD</code>
|Rotator movement threshold, in degrees. If set, the rotator will only be commanded when the target has moved more than <threshold> degrees away from the current azimuth/elevation position. Default: 4 degrees
|-
|
|
|-
|<code>HAMLIB_UTILS_ROT_ENABLED</code>
|Whether or not to enable the Hamlibs rotator daemon. Rotctld is a software daemon that provides a network server to control a rotator on a serial port.
|-
|<code>HAMLIB_UTILS_ROT_OPTS</code>
|Options for rotcld:
For a yaesu rotator, use <code>-m 601 -r /dev/ttyACM0 -s 9600 -T 0.0.0.0</code>

For a SatNOGS rotator <code>-m 204 -s 19200 -r /dev/ttyACM0 -C timeout=200</code> or <code>-m 204 -s 19200 -r /dev/ttyUSB0 -C timeout=200</code>
|-
|
|
|-
|<code>SATNOGS_PRE_OBSERVATION_SCRIPT</code><code>SATNOGS_POST_OBSERVATION_SCRIPT</code>
|Allows execution of a shell script either pre or post-observation. The following can be entered into the script path to enable passing of information to the script:
<code><nowiki>{{FREQ}}</nowiki></code> - Observation Centre Frequency

<code><nowiki>{{TLE}}</nowiki></code> - Target object TLE data, as a JSON-formatted object.

<code><nowiki>{{TIMESTAMP}}</nowiki></code> - Start time of the observation, in the format: %Y-%m-%dT%H-%M-%S%z

<code><nowiki>{{ID}}</nowiki></code> - Observation ID number.

<code><nowiki>{{BAUD}}</nowiki></code> - Baud rate of the modulation used, if applicable.

<code><nowiki>{{SCRIPT_NAME}}</nowiki></code> - The name of the demodulation flow-graph script in use.
|-
|
|
|-
|<code>EXPERIMENTAL</code>
|Install latest (experimental) versions of all software
|-
|<code>APT_REPOSITORY</code>
|This options allows you to change the SatNOGS packages repository. For example, to install unstable package builds use:
<code>deb <nowiki>http://download.opensuse.org/repositories/home:/librespace:/satnogs-unstable/Raspbian_10</nowiki> ./</code>
|-
|<code>APT_KEY_URL</code>
|This options allows you to change the SatNOGS packages repository key URL. For example, to install unstable package builds use:
<code><nowiki>http://download.opensuse.org/repositories/home:/librespace:/satnogs-unstable/Raspbian_10/Release.key</nowiki></code>
|-
|<code>APT_KEY_ID</code>
|This options allows you to specify an alternative SatNOGS packages repository key ID.
|-
|<code>SATNOGS_CLIENT_URL</code>
|If you to try a development version of satnogs-client, you can change the URL here. The URL needs to be in [https://pip.pypa.io/en/stable/reference/pip_install PIP format]. Here are some examples:

*<code>git+<nowiki>https://gitlab.com/librespacefoundation/satnogs/satnogs-client.git@master</nowiki></code> -- the 'master' branch (the current development version) of satnogs-client
*<code><nowiki>git+https://gitlab.com/jdoe/satnogs-client.git@new-feature</nowiki></code> -- the 'new-feature' branch of jdoe's fork of satnogs-client
|-
|<code>SATNOGS_RADIO_FLOWGRAPHS_VERSION</code>
|This options allows you to change the version of satnogs-flowgraphs package to be installed. For example:
<code>0.1-1</code>
|-
|
|
|-
|<code>LOG_LEVEL</code>
|Define SatNOGS client log level, available values: <code>ERROR</code>, <code>WARNING</code>, <code>INFO</code> and <code>DEBUG</code>
|}

==Obsolete Setup Variables==
The following options were available in previous versions of the SatNOGS client system and have no effect on the latest stable version.
{| class="wikitable"
!Setting
!Description
|-
|<code>SATNOGS_RX_DEVICE</code>
|If you are using an RTL-SDR, this is <code>rtlsdr</code>. Other devices supported by gr-satnogs include <code>usrpb200</code>, <code>usrp2</code>, <code>airspy/airspymini</code>, <code>lime</code>, or <code>hackrf</code>.
|-
|<code>SATNOGS_PPM_ERROR</code> (available again)
|gr-satnogs: The PPM correction [https://gitlab.com/librespacefoundation/satnogs/gr-satnogs/-/blob/v1.5.1/apps/flowgraphs/README.md#execution-arguements-interface]
|-
|<code>SATNOGS_DEV_ARGS</code> (available again)
|gr-satnogs: SDR device specific arguments [https://gitlab.com/librespacefoundation/satnogs/gr-satnogs/-/blob/v1.5.1/apps/flowgraphs/README.md#execution-arguements-interface]
Note: This variable was re-purposed to set soapy device and stream arguments, so it's not obsolete anymore.
|-
|<code>SATNOGS_IF_GAIN</code>
|gr-satnogs: Intermediate frequency gain [https://gitlab.com/librespacefoundation/satnogs/gr-satnogs/-/blob/v1.5.1/apps/flowgraphs/README.md#execution-arguements-interface]
|-
|<code>SATNOGS_BB_GAIN</code>
|gr-satnogs: Baseband gain [https://gitlab.com/librespacefoundation/satnogs/gr-satnogs/-/blob/v1.5.1/apps/flowgraphs/README.md#execution-arguements-interface]
|-
|<code>SATNOGS_RADIO_GR_SATNOGS_VERSION</code>
|This options allows you to change the version of gr-satnogs package to be installed. For example: <code>1.5.1-1</code>
|}

==Updating SatNOGS Client Software==
{{Warning| An update can potentially interrupt a running observation!}}
To update SatNOGS software, including the configuration tool itself:

#SSH into the system and (re-)run <code>sudo satnogs-setup</code>; this will bring up the configuration menu
#Select <code>Update</code> to update the configuration tool and all distribution packages to the latest
#If you are prompted for a reboot during the upgrade, once the upgrade is finished, select <code>Reboot</code>, SSH back into the system and re-run <code>satnogs-setup</code> to continue to the next step
#Select <code>Apply</code> and the Raspberry Pi will update itself; this may take some time
#Before exit, check at the top that you have the latest satnogs-client and gr-satnogs versions
#Select <code>Back</code> to exit

{{Message|You can check your current version of client (and other client software) at the top of window after running <code>sudo satnogs-setup</code>; alternatively you can generate the support report by going at <code>Advanced -> Support</code>.}}
{{Message|Client version on SatNOGS Network is updated after the first observation with the new client.}}
===Upgrading from Debian 'stretch' to 'buster'===
Debian <code>stretch</code> is no longer supported. If you have already installed an older version of Debian or Raspbian SatNOGS image based on <code>stretch</code> (releases <= [https://gitlab.com/librespacefoundation/satnogs/satnogs-pi-gen/-/tags/2018080300 2018080300]), you must upgrade to <code>buster</code> otherwise it will be impossible to receive updates or upgrades in the future.
====Method 1: Reflashing and reinstalling (recommended)====
The recommended method to upgrade to <code>buster</code> is reflashing the latest Raspbian SatNOGS image (or reinstalling latest Debian). Follow [[Raspberry Pi|Raspberry Pi]] installation instructions and reinstall from scratch.
====Method 2: Release upgrade using satnogs-upgrade (advanced)====
{{Warning|Make sure you have a stable connection to the internet and your SatNOGS client during this process. Release upgrades can consume a lot of time, data and storage.}}To upgrade from stretch to buster using the configuration tool:

#SSH into the system
#Make sure you have enough free space on your SD card (>2GiB) by running <code>df -h /</code> on the console
#Run <code>sudo satnogs-setup</code> and select <code>Update</code> to update the tool itself and then select <code>Apply</code>. This may inform you that the current distribution is not supported and exit. If not, select <code>Exit</code> to exit the tool.
#Run <code>sudo satnogs-upgrade</code> to update all distribution packages to the latest; this will also prompt you for a distribution upgrade, if it detects that one is needed
#Keep an eye on the upgrade progress; <code>dpkg</code> may prompt for changes
#Once the upgrade is completed run <code>sudo sync; sudo reboot</code>
#After the reboot, SSH back into the system and make sure you are on the correct release by running <code>lsb_release -a</code>
#Run <code>sudo rm -f /root/.satnogs/.bootstrapped; sudo satnogs-setup</code> and select <code>Update</code> and then <code>Apply</code>; this may take some time
#Before exit, check at the top that you have the latest satnogs-client and gr-satnogs versions
#Select <code>Back</code> to exit

==Verification of correct installation==
To see if satnogs-client has started successfully, check the logs with <code>systemctl</code>:<pre>
$ systemctl status satnogs-client
</pre>You should see an output that looks like this:<pre>
● satnogs-client.service - SatNOGS client
Loaded: loaded (/etc/systemd/system/satnogs-client.service; enabled; vendor preset: enabled)
Active: active (running) since Wed 2020-03-04 19:30:56 GMT; 6min ago
Main PID: 6309 (satnogs-client)
Tasks: 11 (limit: 2200)
Memory: 37.9M
CGroup: /system.slice/satnogs-client.service
└─6309 /var/lib/satnogs/bin/python3 /var/lib/satnogs/bin/satnogs-client

Mar 04 19:30:56 raspberrypi systemd[1]: Started SatNOGS client.
</pre>If you see that, great -- you're ready to [[Operation|schedule your first observation]]! If not, check out the [[Troubleshooting]] page.

==Backup & Restore the configuration==
The configuration of your SatNOGS station is stored at <code>/etc/ansible/host_vars/localhost</code>. If your station software is broken (e.g. due to a corrupt SD card) or if you want to downgrade from the experimental software back to the stable releases, you can perform the following steps:

#Backup the configuration file at <code>/etc/ansible/host_vars/localhost</code>
#Re-flash the SD card with a fresh image
#Restore the configuration file
#Run <code>sudo satnogs-setup</code> and select <code>Update</code> to update the tool itself and then select <code>Apply</code>

==See also==

*[[SatNOGS Client Ansible]]

[[Category:Build]]
[[Category:Software]]

Troubleshooting Legacy

2021-04-12T18:53:40Z

Jacquin01: /* apt-get update: connection failed */

==Client troubleshooting==

===Raise or Set the debug level===

*Run <code>sudo satnogs-setup</code>;
*Go to '''Advanced Configuration''' and set the '''Debug level''' (see below)
*'''Apply''' the change

{| class="wikitable"
!'''Setting'''
!Value
|-
|'''DEBUG'''
|
{| class="wikitable"
|<code>CRITICAL</code>
|50
|-
|<code>ERROR</code>
|40
|-
|<code>WARNING</code>
|30
|-
|<code>INFO</code>
|20
|-
|<code>DEBUG</code>
|10
|-
|<code>NOTSET</code>
|0 
|}
|}

When done debugging, don't forget to reset the log level, or the files will fill up your disk space.

===Client not showing up on the network?===

*Check that you have ticked the "Is it operational?" checkbox on the groundstation page.
*Check your settings and ensure that the API token and station ID are correct. You can get these from your profile page on the SatNOGS network site. If you have accounts in both dev and prod, make sure you're using the token and station ID from the right environment.
*Check your SATNOGS_NETWORK_API_URL. It should point to https://network.satnogs.org/api/ (prod) or https://network-dev.satnogs.org/api/ (dev).
*Check your network connectivity. Can you ping network.satnogs.org or network-dev.satnogs.org? Try running <code>curl https://network.satnogs.org</code> or <code>curl https://network-dev.satnogs.org</code>.
*Check the logs for an error (<code>journalctl -f -u satnogs-client.service</code> or <code>less /var/log/supervisor/satnogs-error.log</code>) and post to our forums at https://community.libre.space

===RuntimeError: RTL-SDR device not found.===
Seems that the device is not there. Try rebooting and check if Soapy can identify it using <code>SoapySDRUtil --find</code>.

==="satnogsclient - ERROR - Cannot connect to socket 127.0.0.1:4533"===

The client is trying to connect to rotctld but is unable to.

*If you have a no-rotator setup, ensure that satnogs-client is configured as such; see the [[Raspberry Pi]] page for info on how to do this.
**These errors may continue to be reported until [https://gitlab.com/librespacefoundation/satnogs/satnogs-client/issues/340 issue #340] is resolved.

*If you do have a rotator, ensure that rotctld is running.

 

===Some uploads missing & Doppler-correction not working properly===
The station/client might have a clock offset. This causes a Doppler shift on the waterfall and some observations don't start because of a conflict between the time on the PC of the station and the time of the SatNOGS Network.

===Uploads (waterfall or audio) are missing for a past observation===
When using <code>satnogs-setup</code> for editing/updating the configuration of the station, the satnogs-client gets restarted. When this happens during an observation the observation will be aborted and no waterfall/audio/data files will be uploaded. Such observations should be voted as ''failed''.

The partial data from such observations is stored in <code>/tmp/.satnogs/data/</code>, look for files like <code>receiving_{satnogs|waterfall}_123456_2019-01-01T12-23-42.{out|dat}</code>. They can be manually removed.

===Invalid Signature for download.opensuse.org===
Example error during satnogs-setup update or apt-get update:
<code>The following signatures were invalid: EXPKEYSIG 8BD3901736A40B6C home:librespace OBS Project <home:[[Mailto:librespace@build.opensuse.org|librespace@build.opensuse.org]]></code>
Fix:

<code>wget -qO - <nowiki>http://download.opensuse.org/repositories/home:/librespace:/satnogs-unstable/Raspbian_10/Release.key</nowiki> | sudo apt-key --keyring /etc/apt/trusted.gpg add -</code>

More info available at https://community.libre.space/t/sudo-apt-update-signature-invalid/7643/7

===apt-get update: connection failed===
When using the sudo apt-get update command, we get the following connection error:
[[File:UpdateFailed.png]]

However, a ping to the Ip address works.

If you use a firewall (Ex: stormshield SN210), it can include a default rule that blocks connection urls containing a dot-slash ("./"). (This rule can be named as follows: "path with self-reference")

This rule must be modified to allow the raspberry to access the repository

==Signal troubleshooting==

===Blank or solid purple waterfall?===
{{Warning|Some information in this section seems outdated or wrong. Please take it with care.
Once reviewed this banner can be removed.}}
At the first sign of trouble, put your station into testing mode.

*Make sure the RTLSDR gain is set correctly. Follow the guide at [[Omnidirectional_Station_How_To#Setting_the_gain]] to find a proper gain setting. Check your gain value is valid. Wrong values can result in blank waterfalls. For example '7.7.' will result in errors (and a blank waterfall - there is an extra '.' at the end). <code>journalctl -u satnogs-client.service</code> It might be a big file, but work through it and look for errors. <code>df -h</code> Ensure there is sufficient hard drive space. If temp files can not be created, the waterfall might be blank. Run <code>rtl_test</code> for about 30 seconds and make sure you can connect with the dongle and that there are no errors.

===Not receiving anything?===

*Make sure the satellite you are testing observations against is active and recently received by others on [https://network.satnogs.org our production network site]. If you click on a satellite name, a popup will appear and give you the option to click on "Past Observations". If everything in the past shows red, then the problem is likely with that satellite.

*SO-50 is a good satellite to use for testing as it is a strong FM voice signal assuming you have UHF capabilities. Schedule using "PE0SAT - Mode V/U FM Voice - 436.794 MHz". Here is an example to compare against: https://network.satnogs.org/observations/3334/

*ISS is a good test for VHF as the APRS digipeater is alive again (as of this writing; check [https://www.issfanclub.com/ issfanclub.com] for up-to-date information). When you schedule it, be sure to select the APRS downlink.

*If you're using an rtlsdr, check that it can be seen and is operating correctly by running rtl_test. Let it run for 30 seconds or so, then hit Ctrl-c to kill it:

<pre>
pi@raspberrypi:~ $ rtl_test
Found 1 device(s):
0: Realtek, RTL2838UHIDIR, SN: 00000001

Using device 0: Generic RTL2832U OEM
Found Rafael Micro R820T tuner
Supported gain values (29): 0.0 0.9 1.4 2.7 3.7 7.7 8.7 12.5 14.4 15.7 16.6 19.7 20.7 22.9 25.4 28.0 29.7 32.8 33.8 36.4 37.2 38.6 40.2 42.1 43.4 43.9 44.5 48.0 49.6
[R82XX] PLL not locked!
Sampling at 2048000 S/s.

Info: This tool will continuously read from the device, and report if
samples get lost. If you observe no further output, everything is fine.

Reading samples in async mode...
^CSignal caught, exiting!

User cancel, exiting...
Samples per million lost (minimum): 0
</pre>

*You can also try a manual run of satnogs_afsk1200_ax25.py to make sure that works:

<pre>
$ cd /tmp
$ satnogs_afsk1200_ax25.py --soapy-rx-device="driver=rtlsdr" --antenna=RX --samp-rate-rx=2.048e6 --rx-freq=444000000 --file-path=./audio-out.ogg --waterfall-file-path=./waterfall.dat
</pre>

Let it run for a minute or so. If everything is working, this should create an .ogg file and a .dat file of non-zero size (probably a few MB each).

===Observations seem off-frequency?===
[[File:Waterfall_3519_2017-04-24T04-48-48_resized.png|frame|Check your location!]]

*'''PPM drift''' While newer SDR devices are very good and stable, there still may be some PPM drift to compensate for if you notice that signals are consistently off center. The SATNOGS_PPM_ERROR setting in /etc/supervisord.d/satnogs.ini can be used to correct for this.
*'''Clock sync''' Make sure your clock is synced. Ensure ntp is configured and running (especially with the Raspberry Pi which lacks a real time clock)
*'''Wrong location''' If your signal seems to be on but drifts at the apex like in this image, check to make sure your Latitude, Longitude, and Elevation coordinates are set properly and in the right format.

===USB===
You can reset USB without having to reboot the system by running these commands:

echo “usb1” > /sys/bus/usb/drivers/usb/unbind
echo “usb1” > /sys/bus/usb/drivers/usb/bind

This can be placed in the satnogs_post_observation_script for automation.

===RF Noise===
If you notice a noise in the waterfall every time motors are spinning, you will need to:

*Twist each pair or the motor wire
*Add proper grounding
*Add capacitor to the DC input of drivers
*Wrap the motors wire with adhesive aluminum and then connect it to GND on driver side
*Add ferrites to motors wires

[[File:Rf noise.png|alt=RF Noise|left|thumb|400x400px|Too much RF Noise]]

[[Category:Operate]]
[[Category:Hardware]]
[[Category:Software]]

Troubleshooting Legacy

2021-04-12T18:53:12Z

Jacquin01: Explain how firewall can block apt-get update with ./ in the url

==Client troubleshooting==

===Raise or Set the debug level===

*Run <code>sudo satnogs-setup</code>;
*Go to '''Advanced Configuration''' and set the '''Debug level''' (see below)
*'''Apply''' the change

{| class="wikitable"
!'''Setting'''
!Value
|-
|'''DEBUG'''
|
{| class="wikitable"
|<code>CRITICAL</code>
|50
|-
|<code>ERROR</code>
|40
|-
|<code>WARNING</code>
|30
|-
|<code>INFO</code>
|20
|-
|<code>DEBUG</code>
|10
|-
|<code>NOTSET</code>
|0 
|}
|}

When done debugging, don't forget to reset the log level, or the files will fill up your disk space.

===Client not showing up on the network?===

*Check that you have ticked the "Is it operational?" checkbox on the groundstation page.
*Check your settings and ensure that the API token and station ID are correct. You can get these from your profile page on the SatNOGS network site. If you have accounts in both dev and prod, make sure you're using the token and station ID from the right environment.
*Check your SATNOGS_NETWORK_API_URL. It should point to https://network.satnogs.org/api/ (prod) or https://network-dev.satnogs.org/api/ (dev).
*Check your network connectivity. Can you ping network.satnogs.org or network-dev.satnogs.org? Try running <code>curl https://network.satnogs.org</code> or <code>curl https://network-dev.satnogs.org</code>.
*Check the logs for an error (<code>journalctl -f -u satnogs-client.service</code> or <code>less /var/log/supervisor/satnogs-error.log</code>) and post to our forums at https://community.libre.space

===RuntimeError: RTL-SDR device not found.===
Seems that the device is not there. Try rebooting and check if Soapy can identify it using <code>SoapySDRUtil --find</code>.

==="satnogsclient - ERROR - Cannot connect to socket 127.0.0.1:4533"===

The client is trying to connect to rotctld but is unable to.

*If you have a no-rotator setup, ensure that satnogs-client is configured as such; see the [[Raspberry Pi]] page for info on how to do this.
**These errors may continue to be reported until [https://gitlab.com/librespacefoundation/satnogs/satnogs-client/issues/340 issue #340] is resolved.

*If you do have a rotator, ensure that rotctld is running.

 

===Some uploads missing & Doppler-correction not working properly===
The station/client might have a clock offset. This causes a Doppler shift on the waterfall and some observations don't start because of a conflict between the time on the PC of the station and the time of the SatNOGS Network.

===Uploads (waterfall or audio) are missing for a past observation===
When using <code>satnogs-setup</code> for editing/updating the configuration of the station, the satnogs-client gets restarted. When this happens during an observation the observation will be aborted and no waterfall/audio/data files will be uploaded. Such observations should be voted as ''failed''.

The partial data from such observations is stored in <code>/tmp/.satnogs/data/</code>, look for files like <code>receiving_{satnogs|waterfall}_123456_2019-01-01T12-23-42.{out|dat}</code>. They can be manually removed.

===Invalid Signature for download.opensuse.org===
Example error during satnogs-setup update or apt-get update:
<code>The following signatures were invalid: EXPKEYSIG 8BD3901736A40B6C home:librespace OBS Project <home:[[Mailto:librespace@build.opensuse.org|librespace@build.opensuse.org]]></code>
Fix:

<code>wget -qO - <nowiki>http://download.opensuse.org/repositories/home:/librespace:/satnogs-unstable/Raspbian_10/Release.key</nowiki> | sudo apt-key --keyring /etc/apt/trusted.gpg add -</code>

More info available at https://community.libre.space/t/sudo-apt-update-signature-invalid/7643/7

=== apt-get update: connection failed ===
When using the sudo apt-get update command, we get the following connection error:
[[File:UpdateFailed.png]]
However, a ping to the Ip address works.

If you use a firewall (Ex: stormshield SN210), it can include a default rule that blocks connection urls containing a dot-slash ("./"). (This rule can be named as follows: "path with self-reference")

This rule must be modified to allow the raspberry to access the repository

==Signal troubleshooting==

===Blank or solid purple waterfall?===
{{Warning|Some information in this section seems outdated or wrong. Please take it with care.
Once reviewed this banner can be removed.}}
At the first sign of trouble, put your station into testing mode.

*Make sure the RTLSDR gain is set correctly. Follow the guide at [[Omnidirectional_Station_How_To#Setting_the_gain]] to find a proper gain setting. Check your gain value is valid. Wrong values can result in blank waterfalls. For example '7.7.' will result in errors (and a blank waterfall - there is an extra '.' at the end). <code>journalctl -u satnogs-client.service</code> It might be a big file, but work through it and look for errors. <code>df -h</code> Ensure there is sufficient hard drive space. If temp files can not be created, the waterfall might be blank. Run <code>rtl_test</code> for about 30 seconds and make sure you can connect with the dongle and that there are no errors.

===Not receiving anything?===

*Make sure the satellite you are testing observations against is active and recently received by others on [https://network.satnogs.org our production network site]. If you click on a satellite name, a popup will appear and give you the option to click on "Past Observations". If everything in the past shows red, then the problem is likely with that satellite.

*SO-50 is a good satellite to use for testing as it is a strong FM voice signal assuming you have UHF capabilities. Schedule using "PE0SAT - Mode V/U FM Voice - 436.794 MHz". Here is an example to compare against: https://network.satnogs.org/observations/3334/

*ISS is a good test for VHF as the APRS digipeater is alive again (as of this writing; check [https://www.issfanclub.com/ issfanclub.com] for up-to-date information). When you schedule it, be sure to select the APRS downlink.

*If you're using an rtlsdr, check that it can be seen and is operating correctly by running rtl_test. Let it run for 30 seconds or so, then hit Ctrl-c to kill it:

<pre>
pi@raspberrypi:~ $ rtl_test
Found 1 device(s):
0: Realtek, RTL2838UHIDIR, SN: 00000001

Using device 0: Generic RTL2832U OEM
Found Rafael Micro R820T tuner
Supported gain values (29): 0.0 0.9 1.4 2.7 3.7 7.7 8.7 12.5 14.4 15.7 16.6 19.7 20.7 22.9 25.4 28.0 29.7 32.8 33.8 36.4 37.2 38.6 40.2 42.1 43.4 43.9 44.5 48.0 49.6
[R82XX] PLL not locked!
Sampling at 2048000 S/s.

Info: This tool will continuously read from the device, and report if
samples get lost. If you observe no further output, everything is fine.

Reading samples in async mode...
^CSignal caught, exiting!

User cancel, exiting...
Samples per million lost (minimum): 0
</pre>

*You can also try a manual run of satnogs_afsk1200_ax25.py to make sure that works:

<pre>
$ cd /tmp
$ satnogs_afsk1200_ax25.py --soapy-rx-device="driver=rtlsdr" --antenna=RX --samp-rate-rx=2.048e6 --rx-freq=444000000 --file-path=./audio-out.ogg --waterfall-file-path=./waterfall.dat
</pre>

Let it run for a minute or so. If everything is working, this should create an .ogg file and a .dat file of non-zero size (probably a few MB each).

===Observations seem off-frequency?===
[[File:Waterfall_3519_2017-04-24T04-48-48_resized.png|frame|Check your location!]]

*'''PPM drift''' While newer SDR devices are very good and stable, there still may be some PPM drift to compensate for if you notice that signals are consistently off center. The SATNOGS_PPM_ERROR setting in /etc/supervisord.d/satnogs.ini can be used to correct for this.
*'''Clock sync''' Make sure your clock is synced. Ensure ntp is configured and running (especially with the Raspberry Pi which lacks a real time clock)
*'''Wrong location''' If your signal seems to be on but drifts at the apex like in this image, check to make sure your Latitude, Longitude, and Elevation coordinates are set properly and in the right format.

===USB===
You can reset USB without having to reboot the system by running these commands:

echo “usb1” > /sys/bus/usb/drivers/usb/unbind
echo “usb1” > /sys/bus/usb/drivers/usb/bind

This can be placed in the satnogs_post_observation_script for automation.

===RF Noise===
If you notice a noise in the waterfall every time motors are spinning, you will need to:

*Twist each pair or the motor wire
*Add proper grounding
*Add capacitor to the DC input of drivers
*Wrap the motors wire with adhesive aluminum and then connect it to GND on driver side
*Add ferrites to motors wires

[[File:Rf noise.png|alt=RF Noise|left|thumb|400x400px|Too much RF Noise]]

[[Category:Operate]]
[[Category:Hardware]]
[[Category:Software]]

File:UpdateFailed.png

2021-04-12T18:36:48Z

Jacquin01:

Connection failed for download.opensuse.org