SatNOGS Wiki - User contributions [en]

Antennas

2021-01-31T16:14:14Z

Fjkraan: Added an antenna design with 3Dprinted parts, link to thingiverse.

__NOTOC__
The type of antenna largely depends on the type of ground station. A no rotator ground station will benefit from a different type of antenna (omnidirectional) than a rotator based ground station (directional). The two different approaches are explored below. In addition to the choice of antenna the choice of location for the ground station will have an effect on the quality of observations.

==Non-Rotator Ground Station (Omnidirectional)==
This type of ground station will require an antenna that will give a broad coverage from its fixed position. It is therefore not just the antenna that needs to be considered but also the proximity of buildings, geography or metallic structures that might be in the path of a line of sight between the ground station and satellite.Typical ground stations have had success with simple wire antennas that can be commercially bought or made at home. Colinear or ‘white stick’ antennas are vertically polarised omnidirectional antennas. These have anecdotally been used for successful satellite work but should be avoided. The following are considered suitable choices:'''It is highly recommended that you use a mast-mounted Low-Noise Amplifier (LNA) with these antennas.'''
{| class="wikitable" style="width: 100%;"
! style="width: 49%" |
===Commercial Antennas===
!
! style="width: 49%" |
===Homebrew Antennas===
|-
|[[File:WiMo TA-1.gif|left|frameless|160x160px]]

====WiMo TA-1====
VHF Turnstile

Estimated cost: 90€

Some SatNOGS stations using this antenna:

[https://network.satnogs.org/stations/141/ 141 - balcony-only-east-passes]

[https://network.satnogs.org/stations/33/ 33 - G7KSE]

[https://network.satnogs.org/stations/129/ 129 - Chabot Space And Science Center]

[https://network.satnogs.org/stations/896/ 896 - KJ6DZB]

*[https://www.wimo.com/scanner-antennas_e.html#004 Product link]
*[http://oz9aec.net/antennas/air-tests-wimo-ta-1-turnstile-antenna OZ9AEC Review]
|
|[[File:VHF Turnstile.jpg|left|frameless|100x100px]]

====Turnstile====
Estimated cost: TBD

Some SatNOGS stations using this antenna:

[https://network.satnogs.org/stations/13/ 13 - OZ9AEC-VHF1]

[https://network.satnogs.org/stations/7/ 7 - Stony]

[https://network.satnogs.org/stations/16/ 16 - VK5QI-70CM]

*SatNOGS Turnstile Antenna (TBD)
*[https://vk4adc.com/web/index.php/vhfuhf-projects/26-multiband-ants/156-turnstile-vhf-uhf-fds VK4ADC instructions for VHF and UHF Turnstile antennas]
*[https://www.aeronetworks.ca/2017/12/amateur-satcom-rx-antenna-for-2-meter.html Six-element tape-measure VHF Turnstile with modeled patterns (could be used as directional) by Herman Oosthuysen]
*[https://iz7boj.wordpress.com/2018/12/02/double-turnstile-construction-for-satellites-receiving-in-435mhz-band/ Double turnstile construction for 435MHz]
|-
|[[File:M2 Eggbeaters.png|left|frameless|100x100px]]

====M2 Eggbeater====
VHF / UHF Eggbeater Antennas

Estimated cost: $304 (VHF), $280 (UHF), $573 (combo)

Some SatNOGS stations using this antenna:

[https://network.satnogs.org/stations/50/ 50 - N5CNB-UHF]

[https://network.satnogs.org/stations/77/ 77 - N5CNB-VHF]

*[https://www.m2inc.com/FGEB144RK2M Product link for VHF]
*[https://www.m2inc.com/FGEB432RK70CM Product link for UHF]
*[https://www.m2inc.com/FGSATPACK1 Product link for combination package]
|
|[[File:VHF EZ-Lindenblad.png|left|frameless|112x112px]]

====Lindenblad====
Estimated cost: TBD

Some SatNOGS stations using this antenna:

[https://network.satnogs.org/stations/12/ 12 - W2BFJ]

[https://network.satnogs.org/stations/98/ 98 - Grove-UHF-01]

[https://network.satnogs.org/stations/442/ 442 - DL1UNX-FFB VHF]

*[https://www.amsat.org/wordpress/wp-content/uploads/2015/08/An-EZ-Lindenblad-Antenna-for-2-Meters2.pdf AA2TX EZ-Lindenblad design can be found at this AMSAT PDF]
*[https://www.qsl.net/py4zbz/DCA.pdf KD6JDJ instructions can be found at this QST PDF]
*[https://www.amsat.org/articles/w6shp/lindy.html W6SHP instructions for VHF and UHF Lindenblad]
|-
|[[File:Winkler Turnstile.jpg|left|frameless|100x100px]]

====Winkler Turnstile====
VHF/UHF Turnstile Antennas

Estimated cost: 40€ (VHF), 30€ (UHF)

Some SatNOGS stations using this antenna:

[https://network.satnogs.org/stations/47/ 47 - DB0RV]

*[http://www.winklerantennenbau.de/sonst.htm Pricing page]
*[http://www.winklerantennenbau.de/kreuz137.htm Product link for VHF]
*[http://www.winklerantennenbau.de/kreuz446.htm Product link for UHF]
|
|[[File:UHF Paralindy.jpg|left|frameless|100x100px]]

====UHF Parasitic Lindenblad====
Estimated cost: $15 (with access to a 3D printer)

Some SatNOGS stations using this antenna:

[https://network.satnogs.org/stations/300/ 300 - KB9JHU-Experimental]

[https://network.satnogs.org/stations/32/ 32 - SV1QZZ - UHF #2]

[https://network.satnogs.org/stations/187/ 187 - K3LRD UHF Lindenblad]

*[https://www.amsat.org/wordpress/wp-content/uploads/2014/01/70ParaLindy.pdf Instructions can be found at this AMSAT PDF by AA2TX]
|-
|
|
|[[File:Quadrifilar Antennas.png|left|frameless|100x100px]]

====Quadrifilar Helix Antenna (QFH)====
Estimated cost: TBD

Some SatNOGS stations using this antenna:

[https://network.satnogs.org/stations/272/ 272 - K3LRD VHF QFH]

[https://network.satnogs.org/stations/255/ 255 - EA5BZ - Elche]

[https://network.satnogs.org/stations/183/ 183 - SPUTNIX-R2ANF-VHF/UHF-stationary]

[https://network.satnogs.org/stations/890/ 890 - Valpo WIRED Lab 3]

*[http://www.g4ilo.com/qfh.html G4ILO QFH Instructions]
*[https://www.aeronetworks.ca/2017/12/parasitic-quadrifilar-helical-antenna.html VHF Model/patterns for QFH by Herman Oosthuysen]
*[http://jcoppens.com/ant/qfh/calc.en.php QFH Calculator by ON6JC/LW3HAZ]
*[https://community.libre.space/t/an-easy-3d-printed-quadrifilar-helix-antenna/1487 3D Printed UHF QFH Antenna by surligas]
*[https://www.thingiverse.com/thing:4737259 3D Printed VHF QFH Antenna based on G4ILO's dimensions]
|-
|
|
|[[File:Vhf moxon turnstile.png|left|frameless|100x100px]]

===="Turnstiled" Moxon====
Estimated cost: TBD

Some SatNOGS stations using this antenna:

[https://network.satnogs.org/stations/305/ 305 - VK5KJP-VHF]

[https://network.satnogs.org/stations/331/ 331 - VK5KJP-UHF]

*[https://sat.fg8oj.com/images/VHFUHFSatelite.pdf Instructions can be found at this QST article by W4RNL]
|}


==Rotator Ground Station==
A rotator based ground station is able to make use of directional antennas. These will have a directional gain, meaning that you will need to point them in the direction of the satellite but the signal you receive will be stronger and for longer. They will allow much lower to the horizon passes to be received and more successful observations. These are not complex antennas but the choice will depend on the type of satellite and there are variations on the main types: yagi, helical and quad.

{| class="wikitable" style="width: 100%;"
! style="width: 49%" |
===Commercial Antennas===
!
! style="width: 49%" |
===Homebrew Antennas===
|-
|[[File:M2 Leopack.png|left|frameless|100x100px]]

====M2 Circularly Polarized Yagis====
VHF/UHF Cross-element Yagi

Estimated cost: $296 (UHF), $296 (VHF), $638 (Combo kit)

Some SatNOGS stations using this antenna:

[https://network.satnogs.org/stations/2/ 2 - KB9JHU]

[https://network.satnogs.org/stations/109/ 109 - EA6WQ - Tomas Orzaez]

[https://network.satnogs.org/stations/25/ 25 - N7IPY]

[https://network.satnogs.org/stations/834/ 834 - Valpo WIRED Lab 1] - ([https://www.m2inc.com/FG2MCP14 2MCP14] and [https://www.m2inc.com/FG436CP30 436CP30] ~3.3m booms)

*[https://www.m2inc.com/FG2MCP8A Product link - VHF]
*[https://www.m2inc.com/FG436CP16 Product link - UHF]
*[https://www.m2inc.com/FGLEOPACK Product link - Combo kit]
|
|[[File:Cross element UHF yagi.jpg|left|frameless|133x133px]]

====Yagi Antennas, Cross-element yagi antennas====
VHF/UHF directional antenna

Estimated cost: TBD

A common type of antenna that is either horizontally or vertically polarised. Simple to construct and suitable for a large number of satellites.

Some SatNOGS stations using this antenna:

TBD

*TBD: Assembly instructions
*[https://gitlab.com/librespacefoundation/satnogs/satnogs-antennas/tree/master/Yagi Source code for SatNOGS yagi antenna designs are here].
|-
|[[File:Wimo xquad vhf.jpg|left|frameless|100x100px]]

====WiMo X Quad====
VHF/UHF Cross-element Quad

Estimated cost: 149€ (VHF), 149€ (UHF)

Some SatNOGS stations using this antenna:

[https://network.satnogs.org/stations/6/ 6 - Apomahon]

[https://network.satnogs.org/stations/49/ 49 - OZ7SAT]

[https://network.satnogs.org/stations/232/ 232 - VK5QI-AZ/EL]

*[https://www.wimo.com/xquad-antennas_e.html Product link]
|
|[[File:Satnogs helical v1.jpg|left|frameless|100x100px]]

====Helical Antennas====
UHF circularly polarized directional antenna

Estimated cost: TBD

A less common type that are circularly polarized. The antenna looks a bit like a corkscrew and can be either LHCP (Left hand circular polarisation) or RHCP (right hand circular polarisation).

Some SatNOGS stations using this antenna:

[https://network.satnogs.org/stations/6/ 6 - Apomahon]

*v4 [https://satnogs.dozuki.com/Guide/Helical+Antenna+v4/11 Assembly instructions]
*[https://ohai.satnogs.org/project/helical-antenna-v5/ v5 Assembly instructions]
*[https://gitlab.com/librespacefoundation/satnogs/satnogs-antennas/tree/master/Helical Source code for SatNOGS helical antenna designs are here.]
|-
|[[File:Arrow Portable Yagi.jpg|left|frameless|100x100px]]

====Arrow Dual-band portable yagi====
VHF/UHF portable yagi

Estimated cost: $83-$149

Some SatNOGS stations using this antenna:

TBD

*[http://www.arrowantennas.com/arrowii/146-437.html Product price/ordering link]
*[http://www.arrowantennas.com/sub/arrowiiyagi.html Product details link]
|
|
|-
|[[File:Elk Log Periodic.jpg|left|frameless|112x112px]]

====Elk Log Periodic====
VHF/UHF portable yagi

Estimated cost: $130-$163

Some SatNOGS stations using this antenna:

TBD

*[https://elkantennas.com/product/dual-band-2m440l5-log-periodic-antenna/ Product link]
|
|
|}


A radome design is available from SatNOGS. This will protect the ground station from the elements in all but extra ordinary conditions. The design can be found [https://gitlab.com/librespacefoundation/satnogs/satnogs-radome/blob/master/satnogs-radome-v1-bom.ods here] and construction guide [https://ohai.satnogs.org/project/satnogs-radome-v1/hardware/ here]. 
[[Category:Antenna]]
[[Category:Hardware]]
__NOEDITSECTION__
[[Category:Omnidirectional Antennas]]
[[Category:Directional Antennas]]

Troubleshooting Legacy

2020-09-01T17:44:01Z

Fjkraan: Forgot a satnogs_fsk1200-ax25.py instance to update, see previous edit

==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.

==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

2020-09-01T17:42:20Z

Fjkraan: /* Updated the local test command */

==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.

==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_fsk_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

2020-09-01T17:40:07Z

Fjkraan: /* Raise or Set the debug level, warning not to let is at debug level. */

==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.

==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_fsk_ax25.py to make sure that works:

<pre>
$ cd /tmp
$ satnogs_fsk_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]]