SatNOGS Wiki - User contributions [en]

Troubleshooting

2025-11-20T02:21:48Z

Kerel+satnogs: Update log level table: add description column and reduce rows to sensible defaults

==Client troubleshooting==

If the hints for common issues below don't help solve your issue, you are welcome to post in the [https://community.libre.space/c/satnogs/6 SatNOGS section] of the [https://community.libre.space/ Community forum]. When doing so, please include any error from the logs and the output of the support report to give the necessary context:

{{Message|
Check the whole error log with <code>sudo docker logs satnogs_satnogs-client</code>
Check live the error log with <code>sudo docker logs -f satnogs_satnogs-client</code>}}

{{Message|Generate support report by the menu item <code>Advanced -> Support</code> in <code>sudo satnogs-setup</code>}}
===Raise or Set the debug level===

*Run <code>sudo satnogs-setup</code>
*Go to '''Advanced Configuration''' and set the '''Debug level''' to one of the Values below
*'''Apply''' the change

{| class="wikitable"
!Level
!Description
|-
|WARNING
|'''Default.''' Show only indications that something unexpected happened, or that a problem might occur in the near future (e.g. ‘disk space low’).
|-
|INFO
| Show confirmations that things are working as expected.
|-
|DEBUG
| Show very detailed information, typically only of interest to a developer trying to diagnose a problem.
|}

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

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

<code>sudo docker exec -ti satnogs_satnogs-client SoapySDRUtil --find="driver=rtlsdr"</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.

===ERROR - Observer job lock acquiring timed out.===

<pre>
Mar 03 20:05:53 satnogs satnogs-client[257]: satnogsclient.scheduler.tasks - ERROR - Observer job lock acquiring timed out.
</pre>

This message is shown when a previous Observation failed (due to a hardware issue or some bug) and didn't properly terminate. To fix this issue, first check the logs for the observation that failed to understand the root cause. Then, restart satnogs-client.

==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>sudo docker logs satnogs_satnogs-client</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>sudo docker exec -ti satnogs_satnogs-client 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:~ $ sudo docker exec -ti satnogs_satnogs-client 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>
$ sudo docker exec -ti satnogs_satnogs-client timeout -s INT 20s satnogs_afsk1200_ax25.py --soapy-rx-device="driver=rtlsdr" --antenna=RX --samp-rate-rx=2.048e6 --rx-freq=444000000 --rigctl-host=rigctld --file-path=/tmp/audio-out.ogg --waterfall-file-path=/tmp/waterfall.dat
$ sudo docker exec -ti satnogs_satnogs-client ls -lah /tmp/audio-out.ogg /tmp/waterfall.dat
$ sudo docker exec -ti satnogs_satnogs-client rm /tmp/audio-out.ogg /tmp/waterfall.dat
</pre>

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:

<pre>
$ usbreset
Usage:
usbreset PPPP:VVVV - reset by product and vendor id
usbreset BBB/DDD - reset by bus and device number
usbreset "Product" - reset by product name

Devices:
Number 001/003 ID 0424:ec00
Number 001/002 ID 0424:9514
Number 001/004 ID 0bda:2838 RTL2838UHIDIR
$ usbreset 001/004
Resetting RTL2838UHIDIR ... ok
</pre>

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

SatNOGS Operations Manual

2025-11-19T16:04:40Z

Kerel+satnogs:

===Requirements===
This manual assumes you have SatNOGS moderator access on Network and DB. If you don't please reach out to our channels for gaining access and helping with SatNOGS Operations!

===Adding a new Satellite===
{{Warning|This manual is intended for SatNOGS Moderators. For a guide on how to add your mission to SatNOGS see [[Satellite Operator Guide]]}}

====0. Should we add it?====
In principle SatNOGS DB aims to capture all information about satellites regardless of their origin, ownership or purpose. So the simple answer is "Yes you should add it". That said we do prioritize the satellites that can be (and will be) tracked by the SatNOGS Network and especially the ones that have been pro-active in reaching out and sharing as much information as possible.

====1. Find new satellites====
Besides the missions that will actively reach out to us by filling issues in [https://gitlab.com/librespacefoundation/satnogs-ops satnogs-ops repo], we need to track launch activity to ensure we are adding new satellites in our DB. Some resources for tracking launches:

*https://space.skyrocket.de/doc_chr/lau2020.htm
*https://spaceflightnow.com/launch-schedule/
*https://www.space.com/32286-space-calendar.html

Tip: As of 2020 we are not adding any swarm satellite entries (e.g. Starlink, OneWeb etc)
 

====2. File the issues in satnogs-ops====
Once you have the information it is needed then navigate to [https://gitlab.com/librespacefoundation/satnogs-ops satnogs-ops repo] and open new issues containing all the information needed.

[https://gitlab.com/librespacefoundation/satnogs-ops/-/issues/new New issue on satnogs-ops]

Some websites and online resources for digging up information (if not already provided by the mission teams):

*http://nanosats.eu/
*http://www.amsatuk.me.uk/iaru/index.php
*https://fcc.report/
*https://apps.fcc.gov/oetcf/els/index.cfm
*Search Google and Twitter for mission posted information!

====3. Add satellite in DB====
 

====4. Add and approve transmitters in DB====

==== 5. Sync SatNOGS Network ====
Go to [https://network.satnogs.org/settings_site/ Network Site Settings] and click on "Sync"
 
====6. Update provisional TLEs (~12 hours before launch)====
{{Warning|This manual is intended for SatNOGS Moderators. If you are not a SatNOGS Moderator, please share TLEs in the '''Launch Thread''', so that one of the moderators can add it. Follow [[Satellite Operator Guide#3._Operations]] for more information. }}

* Acquire provisional TLEs (either constructed from the community or shared by the launch provider)
** You can verify the integrity of the TLE [https://www.vcalc.com/wiki/MichaelBartmess/TLE+Checksum here] and [https://oraas.orekit.space/oraas-tools-tletranslator.html here]
* Go to "[https://network.satnogs.org/admin/base/tle/add/ Add new TLE]" on network.satnogs.org
** Fill out the TLE (don't forget the TLE 0 line too)
** Enter "manual" as source
** Save the TLE
* Go to "[https://network.satnogs.org/admin/base/satellite/ Satellites]" in Admin of network.satnogs.org
** Find and Edit your satellite
** Check "Manual TLE" field
** Save the Satellite

 
====7. Schedule LEOP====
 

====8. Review results====

SatNOGS Operations Manual

2025-11-19T16:04:19Z

Kerel+satnogs:

===Requirements===
This manual assumes you have SatNOGS moderator access on Network and DB. If you don't please reach out to our channels for gaining access and helping with SatNOGS Operations!

===Adding a new Satellite===
{{Warning|This manual is intended for SatNOGS Moderators. For a guide on how to add your mission to SatNOGS see [[Satellite Operator Guide]]}}

====0. Should we add it?====
In principle SatNOGS DB aims to capture all information about satellites regardless of their origin, ownership or purpose. So the simple answer is "Yes you should add it". That said we do prioritize the satellites that can be (and will be) tracked by the SatNOGS Network and especially the ones that have been pro-active in reaching out and sharing as much information as possible.

====1. Find new satellites====
Besides the missions that will actively reach out to us by filling issues in [https://gitlab.com/librespacefoundation/satnogs-ops satnogs-ops repo], we need to track launch activity to ensure we are adding new satellites in our DB. Some resources for tracking launches:

*https://space.skyrocket.de/doc_chr/lau2020.htm
*https://spaceflightnow.com/launch-schedule/
*https://www.space.com/32286-space-calendar.html

Tip: As of 2020 we are not adding any swarm satellite entries (e.g. Starlink, OneWeb etc)
 

====2. File the issues in satnogs-ops====
Once you have the information it is needed then navigate to [https://gitlab.com/librespacefoundation/satnogs-ops satnogs-ops repo] and open new issues containing all the information needed.

[https://gitlab.com/librespacefoundation/satnogs-ops/-/issues/new New issue on satnogs-ops]

Some websites and online resources for digging up information (if not already provided by the mission teams):

*http://nanosats.eu/
*http://www.amsatuk.me.uk/iaru/index.php
*https://fcc.report/
*https://apps.fcc.gov/oetcf/els/index.cfm
*Search Google and Twitter for mission posted information!

====3. Add satellite in DB====
 

====4. Add and approve transmitters in DB====

==== 5. Sync SatNOGS Network ====
Go to [https://network.satnogs.org/settings_site/ Network Site Settings] and click on "Sync"
 
====6. Update provisional TLEs (~12 hours before launch)====
{{Warning|This manual is intended for SatNOGS Moderators. If you are not a SatNOGS Moderator, please share TLEs in the '''Launch Thread''', so that one of the moderators can add it. Follow the [[Satellite Operator Guide#3._Operations]] for more information. }}

* Acquire provisional TLEs (either constructed from the community or shared by the launch provider)
** You can verify the integrity of the TLE [https://www.vcalc.com/wiki/MichaelBartmess/TLE+Checksum here] and [https://oraas.orekit.space/oraas-tools-tletranslator.html here]
* Go to "[https://network.satnogs.org/admin/base/tle/add/ Add new TLE]" on network.satnogs.org
** Fill out the TLE (don't forget the TLE 0 line too)
** Enter "manual" as source
** Save the TLE
* Go to "[https://network.satnogs.org/admin/base/satellite/ Satellites]" in Admin of network.satnogs.org
** Find and Edit your satellite
** Check "Manual TLE" field
** Save the Satellite

 
====7. Schedule LEOP====
 

====8. Review results====

SatNOGS Operations Manual

2025-11-19T16:02:40Z

Kerel+satnogs: Add note for Satellite Operators to share TLE via launch thread

===Requirements===
This manual assumes you have SatNOGS moderator access on Network and DB. If you don't please reach out to our channels for gaining access and helping with SatNOGS Operations!

===Adding a new Satellite===
{{Warning|This manual is intended for SatNOGS Moderators. For a guide on how to add your mission to SatNOGS see [[Satellite Operator Guide]]}}

====0. Should we add it?====
In principle SatNOGS DB aims to capture all information about satellites regardless of their origin, ownership or purpose. So the simple answer is "Yes you should add it". That said we do prioritize the satellites that can be (and will be) tracked by the SatNOGS Network and especially the ones that have been pro-active in reaching out and sharing as much information as possible.

====1. Find new satellites====
Besides the missions that will actively reach out to us by filling issues in [https://gitlab.com/librespacefoundation/satnogs-ops satnogs-ops repo], we need to track launch activity to ensure we are adding new satellites in our DB. Some resources for tracking launches:

*https://space.skyrocket.de/doc_chr/lau2020.htm
*https://spaceflightnow.com/launch-schedule/
*https://www.space.com/32286-space-calendar.html

Tip: As of 2020 we are not adding any swarm satellite entries (e.g. Starlink, OneWeb etc)
 

====2. File the issues in satnogs-ops====
Once you have the information it is needed then navigate to [https://gitlab.com/librespacefoundation/satnogs-ops satnogs-ops repo] and open new issues containing all the information needed.

[https://gitlab.com/librespacefoundation/satnogs-ops/-/issues/new New issue on satnogs-ops]

Some websites and online resources for digging up information (if not already provided by the mission teams):

*http://nanosats.eu/
*http://www.amsatuk.me.uk/iaru/index.php
*https://fcc.report/
*https://apps.fcc.gov/oetcf/els/index.cfm
*Search Google and Twitter for mission posted information!

====3. Add satellite in DB====
 

====4. Add and approve transmitters in DB====

==== 5. Sync SatNOGS Network ====
Go to [https://network.satnogs.org/settings_site/ Network Site Settings] and click on "Sync"
 
====6. Update provisional TLEs (~12 hours before launch)====
{{Warning|This manual is intended for SatNOGS Moderators. If you are not a SatNOGS Moderator, please share TLEs in the '''Launch Thread''', so that one of the moderators can add it. Follow the [[Satellite Operator Guide]] for more information. }}

* Acquire provisional TLEs (either constructed from the community or shared by the launch provider)
** You can verify the integrity of the TLE [https://www.vcalc.com/wiki/MichaelBartmess/TLE+Checksum here] and [https://oraas.orekit.space/oraas-tools-tletranslator.html here]
* Go to "[https://network.satnogs.org/admin/base/tle/add/ Add new TLE]" on network.satnogs.org
** Fill out the TLE (don't forget the TLE 0 line too)
** Enter "manual" as source
** Save the TLE
* Go to "[https://network.satnogs.org/admin/base/satellite/ Satellites]" in Admin of network.satnogs.org
** Find and Edit your satellite
** Check "Manual TLE" field
** Save the Satellite

 
====7. Schedule LEOP====
 

====8. Review results====

Linux Desktop

2025-05-13T09:02:45Z

Kerel+satnogs: Remove old guide from 2018, add link to new guide

PE1CKK Az-El rotator

2025-02-04T11:48:16Z

Kerel+satnogs: specification table: fix style

{{Template:Rotator
|Rotator-Name=PE1CKK Az-El rotator
|image=
|type= Az/El
|cost=
|status=
|latest-release=
|latest-release-name=
|source-repo=
|documentation=[http://www.hybridpretender.nl/az-el.html Az-El rotator]
}}

===Introduction===
A fully 3D printed Az-El system, designed by PE1CKK.

* Link: http://www.hybridpretender.nl/az-el.html
* [https://community.libre.space/t/az-el-printed-rotor-from-pa3axa-and-pe1ckk/12827/5 Forum thread]

===Specification===
{| class="wikitable"
| colspan="2" align="center" |'''PE1CKK Az-El rotator'''
|-
|Plastic Parts||20
|-
|Non Printed Parts||
|-
|Cost||
|-
|Controller Electronics||
|-
|Type||AZ/EL
|-
|Motors||2x DC Motors
|-
|Speed (deg/sec)||
|-
|Torque (Nm)||
|-
|Brake Torque (Nm)||
|-
|Dimensions (mm)||
|-
|Weight (kg)||
|}

===Sourcing & parts===
[https://pad.tchncs.de/sheet/#/2/sheet/view/AfIfw2d1qwsnxny3PwVpOHarpkMlnl2fUeAyfzKnC3A/ Bill-of-materials (collaborative sheet)]

====3D-printed Parts====
{| class="wikitable"
|'''Part'''
|'''Model Filename'''
|'''Quantity'''
|-
|Bottom baseplate
|baseplate_2
|1
|-
|Vertical base
|vertical base
|1
|-
|Big gear half
|tandwiel_groot
|4
|-
|Motor gear
|tandwiel_motor
|2
|-
|Resistor gear
|tandwiel_potmeter
|2
|-
|Gear clamp
|lagerklem
|2
|-
|Standoff ring
|bus
|8
|}
 

====Other Parts====
{| class="wikitable"
|'''Part'''
|'''Quantity'''
|'''Distributor'''
|'''Price (each)'''
|'''Remarks'''
|-
|Ball bearing: 35x44x5mm 6707-2R
|4
|aliexpress
|3.00 €
| - Fixed typo in bearing trade number
|-
|Motor: Bringsmart JGY-370 12V 10rpm
|2
|aliexpress
|5.00 €
|
|-
|L298N bridge motor controller
|1
|aliexpress
|4.00 €
|
|}

PE1CKK Az-El rotator

2025-02-04T11:46:50Z

Kerel+satnogs:

{{Template:Rotator
|Rotator-Name=PE1CKK Az-El rotator
|image=
|type= Az/El
|cost=
|status=
|latest-release=
|latest-release-name=
|source-repo=
|documentation=[http://www.hybridpretender.nl/az-el.html Az-El rotator]
}}

===Introduction===
A fully 3D printed Az-El system, designed by PE1CKK.

* Link: http://www.hybridpretender.nl/az-el.html
* [https://community.libre.space/t/az-el-printed-rotor-from-pa3axa-and-pe1ckk/12827/5 Forum thread]

===Specification===
{| {{table}}
| colspan="2" align="center" |'''PE1CKK Az-El rotator'''
|-
|Plastic Parts||20
|-
|Non Printed Parts||
|-
|Cost||
|-
|Controller Electronics||
|-
|Type||AZ/EL
|-
|Motors||2x DC Motors
|-
|Speed (deg/sec)||
|-
|Torque (Nm)||
|-
|Brake Torque (Nm)||
|-
|Dimensions (mm)||
|-
|Weight (kg)||
|}

===Sourcing & parts===
[https://pad.tchncs.de/sheet/#/2/sheet/view/AfIfw2d1qwsnxny3PwVpOHarpkMlnl2fUeAyfzKnC3A/ Bill-of-materials (collaborative sheet)]

====3D-printed Parts====
{| class="wikitable"
|'''Part'''
|'''Model Filename'''
|'''Quantity'''
|-
|Bottom baseplate
|baseplate_2
|1
|-
|Vertical base
|vertical base
|1
|-
|Big gear half
|tandwiel_groot
|4
|-
|Motor gear
|tandwiel_motor
|2
|-
|Resistor gear
|tandwiel_potmeter
|2
|-
|Gear clamp
|lagerklem
|2
|-
|Standoff ring
|bus
|8
|}
 

====Other Parts====
{| class="wikitable"
|'''Part'''
|'''Quantity'''
|'''Distributor'''
|'''Price (each)'''
|'''Remarks'''
|-
|Ball bearing: 35x44x5mm 6707-2R
|4
|aliexpress
|3.00 €
| - Fixed typo in bearing trade number
|-
|Motor: Bringsmart JGY-370 12V 10rpm
|2
|aliexpress
|5.00 €
|
|-
|L298N bridge motor controller
|1
|aliexpress
|4.00 €
|
|}

PE1CKK Az-El rotator

2025-02-04T11:45:35Z

Kerel+satnogs: Add link to original documentation

{{Template:Rotator
|Rotator-Name=PE1CKK Az-El rotator
|image=
|type= Az/El
|cost=
|status=
|latest-release=
|latest-release-name=
|source-repo=
|documentation=[http://www.hybridpretender.nl/az-el.html Az-El rotator]
}}

===Introduction===
A fully 3D printed Az-El system, designed by PE1CKK.

Link: http://www.hybridpretender.nl/az-el.html

===Specification===
{| {{table}}
| colspan="2" align="center" |'''PE1CKK Az-El rotator'''
|-
|Plastic Parts||20
|-
|Non Printed Parts||
|-
|Cost||
|-
|Controller Electronics||
|-
|Type||AZ/EL
|-
|Motors||2x DC Motors
|-
|Speed (deg/sec)||
|-
|Torque (Nm)||
|-
|Brake Torque (Nm)||
|-
|Dimensions (mm)||
|-
|Weight (kg)||
|}

===Sourcing & parts===
[https://pad.tchncs.de/sheet/#/2/sheet/view/AfIfw2d1qwsnxny3PwVpOHarpkMlnl2fUeAyfzKnC3A/ Bill-of-materials (collaborative sheet)]

====3D-printed Parts====
{| class="wikitable"
|'''Part'''
|'''Model Filename'''
|'''Quantity'''
|-
|Bottom baseplate
|baseplate_2
|1
|-
|Vertical base
|vertical base
|1
|-
|Big gear half
|tandwiel_groot
|4
|-
|Motor gear
|tandwiel_motor
|2
|-
|Resistor gear
|tandwiel_potmeter
|2
|-
|Gear clamp
|lagerklem
|2
|-
|Standoff ring
|bus
|8
|}
 

====Other Parts====
{| class="wikitable"
|'''Part'''
|'''Quantity'''
|'''Distributor'''
|'''Price (each)'''
|'''Remarks'''
|-
|Ball bearing: 35x44x5mm 6707-2R
|4
|aliexpress
|3.00 €
| - Fixed typo in bearing trade number
|-
|Motor: Bringsmart JGY-370 12V 10rpm
|2
|aliexpress
|5.00 €
|
|-
|L298N bridge motor controller
|1
|aliexpress
|4.00 €
|
|}

PE1CKK Az-El rotator

2025-02-04T11:44:02Z

Kerel+satnogs: /* Sourcing & parts */ add table "3D-printed parts"

{{Template:Rotator
|Rotator-Name=PE1CKK Az-El rotator
|image=
|type= Az/El
|cost=
|status=
|latest-release=
|latest-release-name=
|source-repo=
|documentation=[http://www.hybridpretender.nl/az-el.html Az-El rotator]
}}

===Introduction===
A fully 3D printed Az-El system, designed by PE1CKK.

===Specification===
{| {{table}}
| colspan="2" align="center" |'''PE1CKK Az-El rotator'''
|-
|Plastic Parts||20
|-
|Non Printed Parts||
|-
|Cost||
|-
|Controller Electronics||
|-
|Type||AZ/EL
|-
|Motors||2x DC Motors
|-
|Speed (deg/sec)||
|-
|Torque (Nm)||
|-
|Brake Torque (Nm)||
|-
|Dimensions (mm)||
|-
|Weight (kg)||
|}

===Sourcing & parts===
[https://pad.tchncs.de/sheet/#/2/sheet/view/AfIfw2d1qwsnxny3PwVpOHarpkMlnl2fUeAyfzKnC3A/ Bill-of-materials (collaborative sheet)]

==== 3D-printed Parts ====
{| class="wikitable"
|'''Part'''
|'''Model Filename'''
|'''Quantity'''
|-
|Bottom baseplate
|baseplate_2
|1
|-
|Vertical base
|vertical base
|1
|-
|Big gear half
|tandwiel_groot
|4
|-
|Motor gear
|tandwiel_motor
|2
|-
|Resistor gear
|tandwiel_potmeter
|2
|-
|Gear clamp
|lagerklem
|2
|-
|Standoff ring
|bus
|8
|}
 

==== Other Parts ====
{| class="wikitable"
|'''Part'''
|'''Quantity'''
|'''Distributor'''
|'''Price (each)'''
|'''Remarks'''
|-
|Ball bearing: 35x44x5mm 6707-2R
|4
|aliexpress
|3.00 €
| - Fixed typo in bearing trade number
|-
|Motor: Bringsmart JGY-370 12V 10rpm
|2
|aliexpress
|5.00 €
|
|-
|L298N bridge motor controller
|1
|aliexpress
|4.00 €
|
|}

PE1CKK Az-El rotator

2025-02-04T11:38:26Z

Kerel+satnogs: added BOM

PE1CKK Az-El rotator

2025-02-04T11:36:36Z

Kerel+satnogs: Add section "sourcing & parts"

Template:Rotator

2025-02-04T10:59:49Z

Kerel+satnogs: Reverted edits by Kerel+satnogs (talk) to last revision by Ppapadeas

{| cellpadding="3" style="float:right; border-spacing:0px; background-color:#e27afff; font-size:95%; margin:0 0 0.5em 1em; width:28em; border-left: 0px; border-right: 0px; border-bottom: 0px; border-top: 0px;"
! colspan="2" style="color: black; background-color: #f6f6f6; font-weight: bold; text-align:center; font-size: larger; -moz-border-radius-topright: 8px; -moz-border-radius-topleft: 8px; border-left: 0px; border-right: 0px; border-bottom: 0px; border-top: 0px;" | {{{Rotator-Name}}}
|- class{{{image}}}="hiddenStructure"
| colspan="2" align="center" bgcolor="#ffffff" style="border-left: 0px; border-right: 0px; border-bottom: 0px; border-top: 0px;" | [[Image:{{{image}}}|thumb|center|{{{Rotator-Name}}}]]
|-
! colspan="2" style="color: black; background-color: #f6f6f6; font-weight: bold; text-align:center; border-left: 0px; border-right: 0px; border-bottom: 0px; border-top: 0px;" | Rotator Information
|- class{{{type|}}}="hiddenStructure" bgcolor="#ffffff" valign="top" border-left="0px" border-right="0px" border-bottom="0px" border-top="0px"
| style="border-left: 0px; border-right: 0px; border-bottom: 0px; border-top: 0px;" | '''Type:''' || style="border-left: 0px; border-right: 0px; border-bottom: 0px; border-top: 0px;" | {{{type}}}
|- class{{{type|}}}="hiddenStructure" bgcolor="#ffffff" valign="top" border-left="0px" border-right="0px" border-bottom="0px" border-top="0px"
| style="border-left: 0px; border-right: 0px; border-bottom: 0px; border-top: 0px;" | '''Cost:''' || style="border-left: 0px; border-right: 0px; border-bottom: 0px; border-top: 0px;" | {{{cost}}}
|-
! colspan="2" style="color: black; background-color: #f6f6f6; font-weight: bold; text-align:center; border-left: 0px; border-right: 0px; border-bottom: 0px; border-top: 0px; " | Release Information
|- background-color="#fbfbff" valign="top" border-left="0px" border-right="0px" border-bottom="0px" border-top="0px"
| style="border-left: 0px; border-right: 0px; border-bottom: 0px; border-top: 0px;" | '''Status:''' || style="border-left: 0px; border-right: 0px; border-bottom: 0px; border-top: 0px;" | {{{status}}}
|- background-color="#fbfbff" valign="top" border-left="0px" border-right="0px" border-bottom="0px" border-top="0px"
| style="border-left: 0px; border-right: 0px; border-bottom: 0px; border-top: 0px;" | '''Latest Release:''' || style="border-left: 0px; border-right: 0px; border-bottom: 0px; border-top: 0px;" | [{{{latest-release}}} {{{latest-release-name}}}]
|- background-color="#fbfbff" valign="top" border-left="0px" border-right="0px" border-bottom="0px" border-top="0px"
| style="border-left: 0px; border-right: 0px; border-bottom: 0px; border-top: 0px;" | '''Repository:''' || style="border-left: 0px; border-right: 0px; border-bottom: 0px; border-top: 0px;" | [{{{source-repo}}}]
|- background-color="#fbfbff" valign="top" border-left="0px" border-right="0px" border-bottom="0px" border-top="0px"
| style="border-left: 0px; border-right: 0px; border-bottom: 0px; border-top: 0px;" | '''Documentation:''' || style="border-left: 0px; border-right: 0px; border-bottom: 0px; border-top: 0px;" | [{{{documentation}}}]
|- background-color="#fbfbff" valign="top" border-left="0px" border-right="0px" border-bottom="0px" border-top="0px"
|-
! colspan="2" style="color: #3074c2; background-color: #f6f6f6; font-weight: bold; text-align:center; -moz-border-radius-bottomright: 8px; -moz-border-radius-bottomleft: 8px; border-left: 0px; border-right: 0px; border-bottom: 0px; border-top: 0px;" |  
|}
<noinclude>
== [[Syntax]] ==
Copy this into your article and leave those sections blank, that you don't need! 
<pre>
{{Template:Rotator
|Rotator-Name=
|image=
|type=
|status=
|latest-release=
|latest-release-name=
|source-repo=
|documentation=
}}
</pre>
</noinclude>

Template:Rotator

2025-02-04T10:58:20Z

Kerel+satnogs:

{| cellpadding="3" style="float:right; border-spacing:0px; background-color:#e27afff; font-size:95%; margin:0 0 0.5em 1em; width:28em; border-left: 0px; border-right: 0px; border-bottom: 0px; border-top: 0px;"
! colspan="2" style="color: black; background-color: #f6f6f6; font-weight: bold; text-align:center; font-size: larger; -moz-border-radius-topright: 8px; -moz-border-radius-topleft: 8px; border-left: 0px; border-right: 0px; border-bottom: 0px; border-top: 0px;" | {{{Rotator-Name}}}
|-
{{#if:{{{image|}}}|IMAGE| NO IMAGE}}
|-
! colspan="2" style="color: black; background-color: #f6f6f6; font-weight: bold; text-align:center; border-left: 0px; border-right: 0px; border-bottom: 0px; border-top: 0px;" | Rotator Information
|- class{{{type|}}}="hiddenStructure" bgcolor="#ffffff" valign="top" border-left="0px" border-right="0px" border-bottom="0px" border-top="0px"
| style="border-left: 0px; border-right: 0px; border-bottom: 0px; border-top: 0px;" | '''Type:''' || style="border-left: 0px; border-right: 0px; border-bottom: 0px; border-top: 0px;" | {{{type}}}
|- class{{{type|}}}="hiddenStructure" bgcolor="#ffffff" valign="top" border-left="0px" border-right="0px" border-bottom="0px" border-top="0px"
| style="border-left: 0px; border-right: 0px; border-bottom: 0px; border-top: 0px;" | '''Cost:''' || style="border-left: 0px; border-right: 0px; border-bottom: 0px; border-top: 0px;" | {{{cost}}}
|-
! colspan="2" style="color: black; background-color: #f6f6f6; font-weight: bold; text-align:center; border-left: 0px; border-right: 0px; border-bottom: 0px; border-top: 0px; " | Release Information
|- background-color="#fbfbff" valign="top" border-left="0px" border-right="0px" border-bottom="0px" border-top="0px"
| style="border-left: 0px; border-right: 0px; border-bottom: 0px; border-top: 0px;" | '''Status:''' || style="border-left: 0px; border-right: 0px; border-bottom: 0px; border-top: 0px;" | {{{status}}}
|- background-color="#fbfbff" valign="top" border-left="0px" border-right="0px" border-bottom="0px" border-top="0px"
| style="border-left: 0px; border-right: 0px; border-bottom: 0px; border-top: 0px;" | '''Latest Release:''' || style="border-left: 0px; border-right: 0px; border-bottom: 0px; border-top: 0px;" | [{{{latest-release}}} {{{latest-release-name}}}]
|- background-color="#fbfbff" valign="top" border-left="0px" border-right="0px" border-bottom="0px" border-top="0px"
| style="border-left: 0px; border-right: 0px; border-bottom: 0px; border-top: 0px;" | '''Repository:''' || style="border-left: 0px; border-right: 0px; border-bottom: 0px; border-top: 0px;" | [{{{source-repo}}}]
|- background-color="#fbfbff" valign="top" border-left="0px" border-right="0px" border-bottom="0px" border-top="0px"
| style="border-left: 0px; border-right: 0px; border-bottom: 0px; border-top: 0px;" | '''Documentation:''' || style="border-left: 0px; border-right: 0px; border-bottom: 0px; border-top: 0px;" | [{{{documentation}}}]
|- background-color="#fbfbff" valign="top" border-left="0px" border-right="0px" border-bottom="0px" border-top="0px"
|-
! colspan="2" style="color: #3074c2; background-color: #f6f6f6; font-weight: bold; text-align:center; -moz-border-radius-bottomright: 8px; -moz-border-radius-bottomleft: 8px; border-left: 0px; border-right: 0px; border-bottom: 0px; border-top: 0px;" |  
|}
<noinclude>
== [[Syntax]] ==
Copy this into your article and leave those sections blank, that you don't need! 
<pre>
{{Template:Rotator
|Rotator-Name=
|image=
|type=
|status=
|latest-release=
|latest-release-name=
|source-repo=
|documentation=
}}
</pre>
</noinclude>

Template:Rotator

2025-02-04T10:52:02Z

Kerel+satnogs: fix previous change

{| cellpadding="3" style="float:right; border-spacing:0px; background-color:#e27afff; font-size:95%; margin:0 0 0.5em 1em; width:28em; border-left: 0px; border-right: 0px; border-bottom: 0px; border-top: 0px;"
! colspan="2" style="color: black; background-color: #f6f6f6; font-weight: bold; text-align:center; font-size: larger; -moz-border-radius-topright: 8px; -moz-border-radius-topleft: 8px; border-left: 0px; border-right: 0px; border-bottom: 0px; border-top: 0px;" | {{{Rotator-Name}}}
{{#if:{{{image|}}}|
|-
| colspan="2" align="center" bgcolor="#ffffff" style="border-left: 0px; border-right: 0px; border-bottom: 0px; border-top: 0px;" | [[Image:{{{image}}}|thumb|center|{{{Rotator-Name}}}]]
}}
|-
! colspan="2" style="color: black; background-color: #f6f6f6; font-weight: bold; text-align:center; border-left: 0px; border-right: 0px; border-bottom: 0px; border-top: 0px;" | Rotator Information
|- class{{{type|}}}="hiddenStructure" bgcolor="#ffffff" valign="top" border-left="0px" border-right="0px" border-bottom="0px" border-top="0px"
| style="border-left: 0px; border-right: 0px; border-bottom: 0px; border-top: 0px;" | '''Type:''' || style="border-left: 0px; border-right: 0px; border-bottom: 0px; border-top: 0px;" | {{{type}}}
|- class{{{type|}}}="hiddenStructure" bgcolor="#ffffff" valign="top" border-left="0px" border-right="0px" border-bottom="0px" border-top="0px"
| style="border-left: 0px; border-right: 0px; border-bottom: 0px; border-top: 0px;" | '''Cost:''' || style="border-left: 0px; border-right: 0px; border-bottom: 0px; border-top: 0px;" | {{{cost}}}
|-
! colspan="2" style="color: black; background-color: #f6f6f6; font-weight: bold; text-align:center; border-left: 0px; border-right: 0px; border-bottom: 0px; border-top: 0px; " | Release Information
|- background-color="#fbfbff" valign="top" border-left="0px" border-right="0px" border-bottom="0px" border-top="0px"
| style="border-left: 0px; border-right: 0px; border-bottom: 0px; border-top: 0px;" | '''Status:''' || style="border-left: 0px; border-right: 0px; border-bottom: 0px; border-top: 0px;" | {{{status}}}
|- background-color="#fbfbff" valign="top" border-left="0px" border-right="0px" border-bottom="0px" border-top="0px"
| style="border-left: 0px; border-right: 0px; border-bottom: 0px; border-top: 0px;" | '''Latest Release:''' || style="border-left: 0px; border-right: 0px; border-bottom: 0px; border-top: 0px;" | [{{{latest-release}}} {{{latest-release-name}}}]
|- background-color="#fbfbff" valign="top" border-left="0px" border-right="0px" border-bottom="0px" border-top="0px"
| style="border-left: 0px; border-right: 0px; border-bottom: 0px; border-top: 0px;" | '''Repository:''' || style="border-left: 0px; border-right: 0px; border-bottom: 0px; border-top: 0px;" | [{{{source-repo}}}]
|- background-color="#fbfbff" valign="top" border-left="0px" border-right="0px" border-bottom="0px" border-top="0px"
| style="border-left: 0px; border-right: 0px; border-bottom: 0px; border-top: 0px;" | '''Documentation:''' || style="border-left: 0px; border-right: 0px; border-bottom: 0px; border-top: 0px;" | [{{{documentation}}}]
|- background-color="#fbfbff" valign="top" border-left="0px" border-right="0px" border-bottom="0px" border-top="0px"
|-
! colspan="2" style="color: #3074c2; background-color: #f6f6f6; font-weight: bold; text-align:center; -moz-border-radius-bottomright: 8px; -moz-border-radius-bottomleft: 8px; border-left: 0px; border-right: 0px; border-bottom: 0px; border-top: 0px;" |  
|}
<noinclude>
== [[Syntax]] ==
Copy this into your article and leave those sections blank, that you don't need! 
<pre>
{{Template:Rotator
|Rotator-Name=
|image=
|type=
|status=
|latest-release=
|latest-release-name=
|source-repo=
|documentation=
}}
</pre>
</noinclude>

Template:Rotator

2025-02-04T10:49:58Z

Kerel+satnogs: Hide image row if template field "image" is empty, using if-syntax instead of missing CSS class "hiddenStructure"

{| cellpadding="3" style="float:right; border-spacing:0px; background-color:#e27afff; font-size:95%; margin:0 0 0.5em 1em; width:28em; border-left: 0px; border-right: 0px; border-bottom: 0px; border-top: 0px;"
! colspan="2" style="color: black; background-color: #f6f6f6; font-weight: bold; text-align:center; font-size: larger; -moz-border-radius-topright: 8px; -moz-border-radius-topleft: 8px; border-left: 0px; border-right: 0px; border-bottom: 0px; border-top: 0px;" | {{{Rotator-Name}}}
{{#if:{{{image|}}}|
| colspan="2" align="center" bgcolor="#ffffff" style="border-left: 0px; border-right: 0px; border-bottom: 0px; border-top: 0px;" | [[Image:{{{image}}}|thumb|center|{{{Rotator-Name}}}]]
}}
|-
! colspan="2" style="color: black; background-color: #f6f6f6; font-weight: bold; text-align:center; border-left: 0px; border-right: 0px; border-bottom: 0px; border-top: 0px;" | Rotator Information
|- class{{{type|}}}="hiddenStructure" bgcolor="#ffffff" valign="top" border-left="0px" border-right="0px" border-bottom="0px" border-top="0px"
| style="border-left: 0px; border-right: 0px; border-bottom: 0px; border-top: 0px;" | '''Type:''' || style="border-left: 0px; border-right: 0px; border-bottom: 0px; border-top: 0px;" | {{{type}}}
|- class{{{type|}}}="hiddenStructure" bgcolor="#ffffff" valign="top" border-left="0px" border-right="0px" border-bottom="0px" border-top="0px"
| style="border-left: 0px; border-right: 0px; border-bottom: 0px; border-top: 0px;" | '''Cost:''' || style="border-left: 0px; border-right: 0px; border-bottom: 0px; border-top: 0px;" | {{{cost}}}
|-
! colspan="2" style="color: black; background-color: #f6f6f6; font-weight: bold; text-align:center; border-left: 0px; border-right: 0px; border-bottom: 0px; border-top: 0px; " | Release Information
|- background-color="#fbfbff" valign="top" border-left="0px" border-right="0px" border-bottom="0px" border-top="0px"
| style="border-left: 0px; border-right: 0px; border-bottom: 0px; border-top: 0px;" | '''Status:''' || style="border-left: 0px; border-right: 0px; border-bottom: 0px; border-top: 0px;" | {{{status}}}
|- background-color="#fbfbff" valign="top" border-left="0px" border-right="0px" border-bottom="0px" border-top="0px"
| style="border-left: 0px; border-right: 0px; border-bottom: 0px; border-top: 0px;" | '''Latest Release:''' || style="border-left: 0px; border-right: 0px; border-bottom: 0px; border-top: 0px;" | [{{{latest-release}}} {{{latest-release-name}}}]
|- background-color="#fbfbff" valign="top" border-left="0px" border-right="0px" border-bottom="0px" border-top="0px"
| style="border-left: 0px; border-right: 0px; border-bottom: 0px; border-top: 0px;" | '''Repository:''' || style="border-left: 0px; border-right: 0px; border-bottom: 0px; border-top: 0px;" | [{{{source-repo}}}]
|- background-color="#fbfbff" valign="top" border-left="0px" border-right="0px" border-bottom="0px" border-top="0px"
| style="border-left: 0px; border-right: 0px; border-bottom: 0px; border-top: 0px;" | '''Documentation:''' || style="border-left: 0px; border-right: 0px; border-bottom: 0px; border-top: 0px;" | [{{{documentation}}}]
|- background-color="#fbfbff" valign="top" border-left="0px" border-right="0px" border-bottom="0px" border-top="0px"
|-
! colspan="2" style="color: #3074c2; background-color: #f6f6f6; font-weight: bold; text-align:center; -moz-border-radius-bottomright: 8px; -moz-border-radius-bottomleft: 8px; border-left: 0px; border-right: 0px; border-bottom: 0px; border-top: 0px;" |  
|}
<noinclude>
== [[Syntax]] ==
Copy this into your article and leave those sections blank, that you don't need! 
<pre>
{{Template:Rotator
|Rotator-Name=
|image=
|type=
|status=
|latest-release=
|latest-release-name=
|source-repo=
|documentation=
}}
</pre>
</noinclude>

PE1CKK Az-El rotator

2025-02-04T10:46:09Z

Kerel+satnogs: Add initial "PE1CKK Az-El rotator" page using rotator template

Template:Rotator

2025-02-04T10:44:43Z

Kerel+satnogs: Hide image row if image is empty

{| cellpadding="3" style="float:right; border-spacing:0px; background-color:#e27afff; font-size:95%; margin:0 0 0.5em 1em; width:28em; border-left: 0px; border-right: 0px; border-bottom: 0px; border-top: 0px;"
! colspan="2" style="color: black; background-color: #f6f6f6; font-weight: bold; text-align:center; font-size: larger; -moz-border-radius-topright: 8px; -moz-border-radius-topleft: 8px; border-left: 0px; border-right: 0px; border-bottom: 0px; border-top: 0px;" | {{{Rotator-Name}}}
|- class{{{image|}}}="hiddenStructure"
| colspan="2" align="center" bgcolor="#ffffff" style="border-left: 0px; border-right: 0px; border-bottom: 0px; border-top: 0px;" | [[Image:{{{image}}}|thumb|center|{{{Rotator-Name}}}]]
|-
! colspan="2" style="color: black; background-color: #f6f6f6; font-weight: bold; text-align:center; border-left: 0px; border-right: 0px; border-bottom: 0px; border-top: 0px;" | Rotator Information
|- class{{{type|}}}="hiddenStructure" bgcolor="#ffffff" valign="top" border-left="0px" border-right="0px" border-bottom="0px" border-top="0px"
| style="border-left: 0px; border-right: 0px; border-bottom: 0px; border-top: 0px;" | '''Type:''' || style="border-left: 0px; border-right: 0px; border-bottom: 0px; border-top: 0px;" | {{{type}}}
|- class{{{type|}}}="hiddenStructure" bgcolor="#ffffff" valign="top" border-left="0px" border-right="0px" border-bottom="0px" border-top="0px"
| style="border-left: 0px; border-right: 0px; border-bottom: 0px; border-top: 0px;" | '''Cost:''' || style="border-left: 0px; border-right: 0px; border-bottom: 0px; border-top: 0px;" | {{{cost}}}
|-
! colspan="2" style="color: black; background-color: #f6f6f6; font-weight: bold; text-align:center; border-left: 0px; border-right: 0px; border-bottom: 0px; border-top: 0px; " | Release Information
|- background-color="#fbfbff" valign="top" border-left="0px" border-right="0px" border-bottom="0px" border-top="0px"
| style="border-left: 0px; border-right: 0px; border-bottom: 0px; border-top: 0px;" | '''Status:''' || style="border-left: 0px; border-right: 0px; border-bottom: 0px; border-top: 0px;" | {{{status}}}
|- background-color="#fbfbff" valign="top" border-left="0px" border-right="0px" border-bottom="0px" border-top="0px"
| style="border-left: 0px; border-right: 0px; border-bottom: 0px; border-top: 0px;" | '''Latest Release:''' || style="border-left: 0px; border-right: 0px; border-bottom: 0px; border-top: 0px;" | [{{{latest-release}}} {{{latest-release-name}}}]
|- background-color="#fbfbff" valign="top" border-left="0px" border-right="0px" border-bottom="0px" border-top="0px"
| style="border-left: 0px; border-right: 0px; border-bottom: 0px; border-top: 0px;" | '''Repository:''' || style="border-left: 0px; border-right: 0px; border-bottom: 0px; border-top: 0px;" | [{{{source-repo}}}]
|- background-color="#fbfbff" valign="top" border-left="0px" border-right="0px" border-bottom="0px" border-top="0px"
| style="border-left: 0px; border-right: 0px; border-bottom: 0px; border-top: 0px;" | '''Documentation:''' || style="border-left: 0px; border-right: 0px; border-bottom: 0px; border-top: 0px;" | [{{{documentation}}}]
|- background-color="#fbfbff" valign="top" border-left="0px" border-right="0px" border-bottom="0px" border-top="0px"
|-
! colspan="2" style="color: #3074c2; background-color: #f6f6f6; font-weight: bold; text-align:center; -moz-border-radius-bottomright: 8px; -moz-border-radius-bottomleft: 8px; border-left: 0px; border-right: 0px; border-bottom: 0px; border-top: 0px;" |  
|}
<noinclude>
== [[Syntax]] ==
Copy this into your article and leave those sections blank, that you don't need! 
<pre>
{{Template:Rotator
|Rotator-Name=
|image=
|type=
|status=
|latest-release=
|latest-release-name=
|source-repo=
|documentation=
}}
</pre>
</noinclude>

Template:Rotator

2025-02-04T10:36:00Z

Kerel+satnogs: Reverted edits by Kerel+satnogs (talk) to last revision by Ppapadeas

Template:Rotator

2025-02-04T10:33:36Z

Kerel+satnogs: Show image only iff the image field is non-empty

{| cellpadding="3" style="float:right; border-spacing:0px; background-color:#e27afff; font-size:95%; margin:0 0 0.5em 1em; width:28em; border-left: 0px; border-right: 0px; border-bottom: 0px; border-top: 0px;"
! colspan="2" style="color: black; background-color: #f6f6f6; font-weight: bold; text-align:center; font-size: larger; -moz-border-radius-topright: 8px; -moz-border-radius-topleft: 8px; border-left: 0px; border-right: 0px; border-bottom: 0px; border-top: 0px;" | {{{Rotator-Name}}}
{{#if: {{{image|}}} |
|- class{{{image}}}="hiddenStructure"
| colspan="2" align="center" bgcolor="#ffffff" style="border-left: 0px; border-right: 0px; border-bottom: 0px; border-top: 0px;" | [[Image:{{{image}}}|thumb|center|{{{Rotator-Name}}}]]
|-
}}
! colspan="2" style="color: black; background-color: #f6f6f6; font-weight: bold; text-align:center; border-left: 0px; border-right: 0px; border-bottom: 0px; border-top: 0px;" | Rotator Information
|- class{{{type|}}}="hiddenStructure" bgcolor="#ffffff" valign="top" border-left="0px" border-right="0px" border-bottom="0px" border-top="0px"
| style="border-left: 0px; border-right: 0px; border-bottom: 0px; border-top: 0px;" | '''Type:''' || style="border-left: 0px; border-right: 0px; border-bottom: 0px; border-top: 0px;" | {{{type}}}
|- class{{{type|}}}="hiddenStructure" bgcolor="#ffffff" valign="top" border-left="0px" border-right="0px" border-bottom="0px" border-top="0px"
| style="border-left: 0px; border-right: 0px; border-bottom: 0px; border-top: 0px;" | '''Cost:''' || style="border-left: 0px; border-right: 0px; border-bottom: 0px; border-top: 0px;" | {{{cost}}}
|-
! colspan="2" style="color: black; background-color: #f6f6f6; font-weight: bold; text-align:center; border-left: 0px; border-right: 0px; border-bottom: 0px; border-top: 0px; " | Release Information
|- background-color="#fbfbff" valign="top" border-left="0px" border-right="0px" border-bottom="0px" border-top="0px"
| style="border-left: 0px; border-right: 0px; border-bottom: 0px; border-top: 0px;" | '''Status:''' || style="border-left: 0px; border-right: 0px; border-bottom: 0px; border-top: 0px;" | {{{status}}}
|- background-color="#fbfbff" valign="top" border-left="0px" border-right="0px" border-bottom="0px" border-top="0px"
| style="border-left: 0px; border-right: 0px; border-bottom: 0px; border-top: 0px;" | '''Latest Release:''' || style="border-left: 0px; border-right: 0px; border-bottom: 0px; border-top: 0px;" | [{{{latest-release}}} {{{latest-release-name}}}]
|- background-color="#fbfbff" valign="top" border-left="0px" border-right="0px" border-bottom="0px" border-top="0px"
| style="border-left: 0px; border-right: 0px; border-bottom: 0px; border-top: 0px;" | '''Repository:''' || style="border-left: 0px; border-right: 0px; border-bottom: 0px; border-top: 0px;" | [{{{source-repo}}}]
|- background-color="#fbfbff" valign="top" border-left="0px" border-right="0px" border-bottom="0px" border-top="0px"
| style="border-left: 0px; border-right: 0px; border-bottom: 0px; border-top: 0px;" | '''Documentation:''' || style="border-left: 0px; border-right: 0px; border-bottom: 0px; border-top: 0px;" | [{{{documentation}}}]
|- background-color="#fbfbff" valign="top" border-left="0px" border-right="0px" border-bottom="0px" border-top="0px"
|-
! colspan="2" style="color: #3074c2; background-color: #f6f6f6; font-weight: bold; text-align:center; -moz-border-radius-bottomright: 8px; -moz-border-radius-bottomleft: 8px; border-left: 0px; border-right: 0px; border-bottom: 0px; border-top: 0px;" |  
|}
<noinclude>
== [[Syntax]] ==
Copy this into your article and leave those sections blank, that you don't need! 
<pre>
{{Template:Rotator
|Rotator-Name=
|image=
|type=
|status=
|latest-release=
|latest-release-name=
|source-repo=
|documentation=
}}
</pre>
</noinclude>

SatNOGS DB

2025-01-08T23:17:12Z

Kerel+satnogs:

==Introduction==
[[File:SatNOGS DB front page.png|alt=|400x400px|thumb|SatNOGS DB front page]][https://db.satnogs.org/ SatNOGS DB] is an effort to create a holistic, unified, global transmitter database for all satellite information. You can export the data or even connect your application using our API. It's part of the SatNOGS project.
==Data==
The DB is open to everyone. Anyone is able to submit suggestions or use the existing Transmitters. All data are public and freely under the [https://creativecommons.org/licenses/by-sa/4.0/ Creative Commons Attribution-ShareAlike 4.0 license] (CC-BY-SA-4.0).

__TOC__

==Contribute==

===Suggesting new Satellites===
Feel free to suggest satellites for upcoming or previous launches.

#Login to SatNOGS DB
#Go to "All Satellites" section in the left menu
#At the top right click on "Edit" button and choose "Suggest New Satellite"
#Leave blank NORAD ID if it isn’t known or satellite isn’t identified

=== Suggesting edits for existing satellites ===

# Login to SatNOGS DB
# Go to the page of the satellite you want to edit
# At the top right, click "Edit" and choose "Edit {satellite name}"
# Always make sure to include a citation that provides the primary source for your edit

===Suggesting transmitters===
[[File:Create new transmitter.png|thumb|Menu item to add new transmitter suggestion (for logged in users)]]
[[File:Transmitter suggestion.png|alt=|thumb|New transmitter suggestion (any logged in user can do it!)]]
We rely on crowd-sourced information to keep our transmitter details up to date. Anyone with a SatNOGS login can submit transmitter details. Moderators are notified and approve submissions frequently.

#Login in SatNOGS DB
#Navigate to the satellite page of the satellite you want to edit (if the satellite was recently added, you can access the last 5 from the home page, otherwise use the search)
#At the top right click on "Edit" button and choose "Submit New Transmitter"
#If modulation isn’t know please choose the FM one.

Further Notes:

*Description: This is the name that will appear for this transmitter across DB, Network, and API users. Please use the following notations
**Band, for instance VHF, or for a transceiver, MODE U/V
**Baud (if applicable), in the format 9k6 for 9600
**Mode, for instance FSK
**Rough type description, ie TLM for "telemetry", or "FM Transponder" for repeater
**Examples
***UHF 9k6 FSK TLM
***MODE U/V FM Transceiver
***VHF CW TLM
*Type
**Transmitter: one-way downlink (telemetry)
**Transceiver: repeats an uplinked signal intact
**Transponder: interacts with an uplinked signal or downlinks after signal modification
*Status
**Active: alive and well
**Inactive: not functional or powered down
**Invalid: this is a legacy or erroneous transmitter information that should be hidden from UI
*Downlink Freq: Published frequency, in Hz
*Downlink Drifted: Observed frequency, or what frequency should be used to properly tune (with doppler correction). In most cases this should be the same as the Downlink frequency. This field '''must be entered''' even if there is no drift.
*Downlink Mode: The modulation mode for this transmitter
*Baud rate: the baud rate, if applicable. If this is a CW beacon, use WPM
*Citation URL: a URL to link to in providing the details for your suggestion. Include observations from SatNOGS Network and/or frequency coordination documentation.
*Service: The ITU service that the transmitter can be categorized.

===Approving transmitters===
[[File:Review transmitter suggestion.png|thumb|Review transmitter suggestion (for moderators only)]]
If you are a moderator you can approved suggestions for transmitters. For that follow the instructions:

#Log in to db.satnogs.org
#Navigate to the satellite page that has pending suggestions for transmitters
#Review the suggestion
#Decide to accept or reject it by clicking on the transmitter menu top right.

Note: this process may change in the future; see [https://gitlab.com/librespacefoundation/satnogs/satnogs-db/issues?milestone_title=Improved+User+Experience the Gitlab issues list] for details.

===Adding Satellites manually (deprecated)===
If you are a moderator you can add new satellite on the DB directly. For that follow the instructions:

#Login in SatNOGS DB
#Navigate to https://db.satnogs.org/admin (if you are seeing a login screen, you are either not logged in or don't have moderator permissions)
#Click on Base::Satellite [https://db.satnogs.org/admin/base/satellite/add/ Add button]
#Complete the information to the best of your knowledge. NORAD ID and Name are mandatory. Add multiple names on the "Names" field.
#Click Save and you are done!
#You can now move on to the next steps: suggesting and approving transmitters for this satellite.

Note: this process may change in the future; see [https://gitlab.com/librespacefoundation/satnogs/satnogs-db/issues?milestone_title=Improved+User+Experience the Gitlab issues list] for details.

===Coding===
Fluent in Python and/or JS? We need you to help with the satnogs-db web application! Take a look at our [https://gitlab.com/librespacefoundation/satnogs/satnogs-db source code], or visit our [https://gitlab.com/librespacefoundation/satnogs/satnogs-db/issues? issues tracker] to start filling bugs, feature requests or code fixes for existing ones.

==API==

More info can be found in [[SatNOGS DB/API|API wiki page]].

==Documentation & Installation==

You can find documentation and installation instructions about the project in our [https://docs.satnogs.org/projects/satnogs-db/en/stable/ Read the Docs instance].

==See also==

*[[SatNOGS Network]]
*[https://libre.space/2020/03/02/space-situational-awareness/ Space Situational Awareness – The story so far and an open way forward]

[[Category:Infrastructure]]
[[Category:Operate]]
[[Category:Satellite]]
[[Category:RF Modes]]

SatNOGS DB

2025-01-08T23:16:34Z

Kerel+satnogs:

__TOC__

==Introduction==
[[File:SatNOGS DB front page.png|alt=|400x400px|thumb|SatNOGS DB front page]][https://db.satnogs.org/ SatNOGS DB] is an effort to create a holistic, unified, global transmitter database for all satellite information. You can export the data or even connect your application using our API. It's part of the SatNOGS project.
==Data==
The DB is open to everyone. Anyone is able to submit suggestions or use the existing Transmitters. All data are public and freely under the [https://creativecommons.org/licenses/by-sa/4.0/ Creative Commons Attribution-ShareAlike 4.0 license] (CC-BY-SA-4.0).

==Contribute==

===Suggesting new Satellites===
Feel free to suggest satellites for upcoming or previous launches.

#Login to SatNOGS DB
#Go to "All Satellites" section in the left menu
#At the top right click on "Edit" button and choose "Suggest New Satellite"
#Leave blank NORAD ID if it isn’t known or satellite isn’t identified

=== Suggesting edits for existing satellites ===

# Login to SatNOGS DB
# Go to the page of the satellite you want to edit
# At the top right, click "Edit" and choose "Edit {satellite name}"
# Always make sure to include a citation that provides the primary source for your edit

===Suggesting transmitters===
[[File:Create new transmitter.png|thumb|Menu item to add new transmitter suggestion (for logged in users)]]
[[File:Transmitter suggestion.png|alt=|thumb|New transmitter suggestion (any logged in user can do it!)]]
We rely on crowd-sourced information to keep our transmitter details up to date. Anyone with a SatNOGS login can submit transmitter details. Moderators are notified and approve submissions frequently.

#Login in SatNOGS DB
#Navigate to the satellite page of the satellite you want to edit (if the satellite was recently added, you can access the last 5 from the home page, otherwise use the search)
#At the top right click on "Edit" button and choose "Submit New Transmitter"
#If modulation isn’t know please choose the FM one.

Further Notes:

*Description: This is the name that will appear for this transmitter across DB, Network, and API users. Please use the following notations
**Band, for instance VHF, or for a transceiver, MODE U/V
**Baud (if applicable), in the format 9k6 for 9600
**Mode, for instance FSK
**Rough type description, ie TLM for "telemetry", or "FM Transponder" for repeater
**Examples
***UHF 9k6 FSK TLM
***MODE U/V FM Transceiver
***VHF CW TLM
*Type
**Transmitter: one-way downlink (telemetry)
**Transceiver: repeats an uplinked signal intact
**Transponder: interacts with an uplinked signal or downlinks after signal modification
*Status
**Active: alive and well
**Inactive: not functional or powered down
**Invalid: this is a legacy or erroneous transmitter information that should be hidden from UI
*Downlink Freq: Published frequency, in Hz
*Downlink Drifted: Observed frequency, or what frequency should be used to properly tune (with doppler correction). In most cases this should be the same as the Downlink frequency. This field '''must be entered''' even if there is no drift.
*Downlink Mode: The modulation mode for this transmitter
*Baud rate: the baud rate, if applicable. If this is a CW beacon, use WPM
*Citation URL: a URL to link to in providing the details for your suggestion. Include observations from SatNOGS Network and/or frequency coordination documentation.
*Service: The ITU service that the transmitter can be categorized.

===Approving transmitters===
[[File:Review transmitter suggestion.png|thumb|Review transmitter suggestion (for moderators only)]]
If you are a moderator you can approved suggestions for transmitters. For that follow the instructions:

#Log in to db.satnogs.org
#Navigate to the satellite page that has pending suggestions for transmitters
#Review the suggestion
#Decide to accept or reject it by clicking on the transmitter menu top right.

Note: this process may change in the future; see [https://gitlab.com/librespacefoundation/satnogs/satnogs-db/issues?milestone_title=Improved+User+Experience the Gitlab issues list] for details.

===Adding Satellites manually (deprecated)===
If you are a moderator you can add new satellite on the DB directly. For that follow the instructions:

#Login in SatNOGS DB
#Navigate to https://db.satnogs.org/admin (if you are seeing a login screen, you are either not logged in or don't have moderator permissions)
#Click on Base::Satellite [https://db.satnogs.org/admin/base/satellite/add/ Add button]
#Complete the information to the best of your knowledge. NORAD ID and Name are mandatory. Add multiple names on the "Names" field.
#Click Save and you are done!
#You can now move on to the next steps: suggesting and approving transmitters for this satellite.

Note: this process may change in the future; see [https://gitlab.com/librespacefoundation/satnogs/satnogs-db/issues?milestone_title=Improved+User+Experience the Gitlab issues list] for details.

===Coding===
Fluent in Python and/or JS? We need you to help with the satnogs-db web application! Take a look at our [https://gitlab.com/librespacefoundation/satnogs/satnogs-db source code], or visit our [https://gitlab.com/librespacefoundation/satnogs/satnogs-db/issues? issues tracker] to start filling bugs, feature requests or code fixes for existing ones.

==API==

More info can be found in [[SatNOGS DB/API|API wiki page]].

==Documentation & Installation==

You can find documentation and installation instructions about the project in our [https://docs.satnogs.org/projects/satnogs-db/en/stable/ Read the Docs instance].

==See also==

*[[SatNOGS Network]]
*[https://libre.space/2020/03/02/space-situational-awareness/ Space Situational Awareness – The story so far and an open way forward]

[[Category:Infrastructure]]
[[Category:Operate]]
[[Category:Satellite]]
[[Category:RF Modes]]

SatNOGS DB

2025-01-08T23:13:42Z

Kerel+satnogs:

__NOTOC__

==Introduction==
[[File:SatNOGS DB front page.png|alt=|400x400px|thumb|SatNOGS DB front page]][https://db.satnogs.org/ SatNOGS DB] is an effort to create a holistic, unified, global transmitter database for all satellite information. You can export the data or even connect your application using our API. It's part of the SatNOGS project.
==Data==
The DB is open to everyone. Anyone is able to submit suggestions or use the existing Transmitters. All data are public and freely under the [https://creativecommons.org/licenses/by-sa/4.0/ Creative Commons Attribution-ShareAlike 4.0 license] (CC-BY-SA-4.0).

==Contribute==

===Suggesting new Satellites===
Feel free to suggest satellites for upcoming or previous launches.

#Login to SatNOGS DB
#Go to "All Satellites" section in the left menu
#At the top right click on "Edit" button and choose "Suggest New Satellite"
#Leave blank NORAD ID if it isn’t known or satellite isn’t identified

=== Suggesting edits for existing satellites ===

# Login to SatNOGS DB
# Go to the page of the satellite you want to edit
# At the top right, click "Edit" and choose "Edit {satellite name}"
# Always make sure to include a citation that provides the primary source for your edit

===Suggesting transmitters===
[[File:Create new transmitter.png|thumb|Menu item to add new transmitter suggestion (for logged in users)]]
[[File:Transmitter suggestion.png|alt=|thumb|New transmitter suggestion (any logged in user can do it!)]]
We rely on crowd-sourced information to keep our transmitter details up to date. Anyone with a SatNOGS login can submit transmitter details. Moderators are notified and approve submissions frequently.

#Login in SatNOGS DB
#Navigate to the satellite page of the satellite you want to edit (if the satellite was recently added, you can access the last 5 from the home page, otherwise use the search)
#At the top right click on "Edit" button and choose "Submit New Transmitter"
#If modulation isn’t know please choose the FM one.

Further Notes:

*Description: This is the name that will appear for this transmitter across DB, Network, and API users. Please use the following notations
**Band, for instance VHF, or for a transceiver, MODE U/V
**Baud (if applicable), in the format 9k6 for 9600
**Mode, for instance FSK
**Rough type description, ie TLM for "telemetry", or "FM Transponder" for repeater
**Examples
***UHF 9k6 FSK TLM
***MODE U/V FM Transceiver
***VHF CW TLM
*Type
**Transmitter: one-way downlink (telemetry)
**Transceiver: repeats an uplinked signal intact
**Transponder: interacts with an uplinked signal or downlinks after signal modification
*Status
**Active: alive and well
**Inactive: not functional or powered down
**Invalid: this is a legacy or erroneous transmitter information that should be hidden from UI
*Downlink Freq: Published frequency, in Hz
*Downlink Drifted: Observed frequency, or what frequency should be used to properly tune (with doppler correction). In most cases this should be the same as the Downlink frequency. This field '''must be entered''' even if there is no drift.
*Downlink Mode: The modulation mode for this transmitter
*Baud rate: the baud rate, if applicable. If this is a CW beacon, use WPM
*Citation URL: a URL to link to in providing the details for your suggestion. Include observations from SatNOGS Network and/or frequency coordination documentation.
*Service: The ITU service that the transmitter can be categorized.

===Approving transmitters===
[[File:Review transmitter suggestion.png|thumb|Review transmitter suggestion (for moderators only)]]
If you are a moderator you can approved suggestions for transmitters. For that follow the instructions:

#Log in to db.satnogs.org
#Navigate to the satellite page that has pending suggestions for transmitters
#Review the suggestion
#Decide to accept or reject it by clicking on the transmitter menu top right.

Note: this process may change in the future; see [https://gitlab.com/librespacefoundation/satnogs/satnogs-db/issues?milestone_title=Improved+User+Experience the Gitlab issues list] for details.

===Adding Satellites manually (deprecated)===
If you are a moderator you can add new satellite on the DB directly. For that follow the instructions:

#Login in SatNOGS DB
#Navigate to https://db.satnogs.org/admin (if you are seeing a login screen, you are either not logged in or don't have moderator permissions)
#Click on Base::Satellite [https://db.satnogs.org/admin/base/satellite/add/ Add button]
#Complete the information to the best of your knowledge. NORAD ID and Name are mandatory. Add multiple names on the "Names" field.
#Click Save and you are done!
#You can now move on to the next steps: suggesting and approving transmitters for this satellite.

Note: this process may change in the future; see [https://gitlab.com/librespacefoundation/satnogs/satnogs-db/issues?milestone_title=Improved+User+Experience the Gitlab issues list] for details.

===Coding===
Fluent in Python and/or JS? We need you to help with the satnogs-db web application! Take a look at our [https://gitlab.com/librespacefoundation/satnogs/satnogs-db source code], or visit our [https://gitlab.com/librespacefoundation/satnogs/satnogs-db/issues? issues tracker] to start filling bugs, feature requests or code fixes for existing ones.

==API==

More info can be found in [[SatNOGS DB/API|API wiki page]].

==Documentation & Installation==

You can find documentation and installation instructions about the project in our [https://docs.satnogs.org/projects/satnogs-db/en/stable/ Read the Docs instance].

==See also==

*[[SatNOGS Network]]
*[https://libre.space/2020/03/02/space-situational-awareness/ Space Situational Awareness – The story so far and an open way forward]

[[Category:Infrastructure]]
[[Category:Operate]]
[[Category:Satellite]]
[[Category:RF Modes]]

SatNOGS DB

2025-01-08T23:10:14Z

Kerel+satnogs: Add "suggesting satellites" and other updates

__NOTOC__

==Introduction==
[[File:SatNOGS DB front page.png|alt=|400x400px|thumb|SatNOGS DB front page]][https://db.satnogs.org/ SatNOGS DB] is an effort to create a holistic, unified, global transmitter database for all satellite information. You can export the data or even connect your application using our API. It's part of the SatNOGS project.
==Data==
The DB is open to everyone. Anyone is able to submit suggestions or use the existing Transmitters. All data are public and freely under the [https://creativecommons.org/licenses/by-sa/4.0/ Creative Commons Attribution-ShareAlike 4.0 license] (CC-BY-SA-4.0).

==Contribute==

=== Suggesting Satellites ===
Feel free to suggest satellites for upcoming or previous launches.

# Login in SatNOGS DB
# Go to "All Satellites" section in the left menu
# At the top right click on Edit button and choose Suggest New Satellite
# Leave blank NORAD ID if it isn’t known or satellite isn’t identified

===Suggesting transmitters===
[[File:Create new transmitter.png|thumb|Menu item to add new transmitter suggestion (for logged in users)]]
[[File:Transmitter suggestion.png|alt=|thumb|New transmitter suggestion (any logged in user can do it!)]]
We rely on crowd-sourced information to keep our transmitter details up to date. Anyone with a SatNOGS login can submit transmitter details. Moderators are notified and approve submissions frequently.

# Login in SatNOGS DB
# Navigate to the satellite page of the satellite you want to edit (if the satellite was recently added, you can access the last 5 from the home page, otherwise use the search)
# At the top right click on "Edit" button and choose "Submit New Transmitter"
# If modulation isn’t know please choose the FM one.

Further Notes:

*Description: This is the name that will appear for this transmitter across DB, Network, and API users. Please use the following notations
**Band, for instance VHF, or for a transceiver, MODE U/V
**Baud (if applicable), in the format 9k6 for 9600
**Mode, for instance FSK
**Rough type description, ie TLM for "telemetry", or "FM Transponder" for repeater
**Examples
***UHF 9k6 FSK TLM
***MODE U/V FM Transceiver
***VHF CW TLM
*Type
**Transmitter: one-way downlink (telemetry)
**Transceiver: repeats an uplinked signal intact
**Transponder: interacts with an uplinked signal or downlinks after signal modification
*Status
**Active: alive and well
**Inactive: not functional or powered down
**Invalid: this is a legacy or erroneous transmitter information that should be hidden from UI
*Downlink Freq: Published frequency, in Hz
*Downlink Drifted: Observed frequency, or what frequency should be used to properly tune (with doppler correction). In most cases this should be the same as the Downlink frequency. This field '''must be entered''' even if there is no drift.
*Downlink Mode: The modulation mode for this transmitter
*Baud rate: the baud rate, if applicable. If this is a CW beacon, use WPM
*Citation URL: a URL to link to in providing the details for your suggestion. Include observations from SatNOGS Network and/or frequency coordination documentation.
*Service: The ITU service that the transmitter can be categorized.

=== Approving transmitters ===
[[File:Review transmitter suggestion.png|thumb|Review transmitter suggestion (for moderators only)]]
If you are a moderator you can approved suggestions for transmitters. For that follow the instructions:

#Log in to db.satnogs.org
#Navigate to the satellite page that has pending suggestions for transmitters
#Review the suggestion
#Decide to accept or reject it by clicking on the transmitter menu top right.

Note: this process may change in the future; see [https://gitlab.com/librespacefoundation/satnogs/satnogs-db/issues?milestone_title=Improved+User+Experience the Gitlab issues list] for details.

=== Adding Satellites manually (deprecated) ===
If you are a moderator you can add new satellite on the DB directly. For that follow the instructions:

#Login in SatNOGS DB
#Navigate to https://db.satnogs.org/admin (if you are seeing a login screen, you are either not logged in or don't have moderator permissions)
#Click on Base::Satellite [https://db.satnogs.org/admin/base/satellite/add/ Add button]
#Complete the information to the best of your knowledge. NORAD ID and Name are mandatory. Add multiple names on the "Names" field.
#Click Save and you are done!
#You can now move on to the next steps: suggesting and approving transmitters for this satellite.

Note: this process may change in the future; see [https://gitlab.com/librespacefoundation/satnogs/satnogs-db/issues?milestone_title=Improved+User+Experience the Gitlab issues list] for details.

===Coding===
Fluent in Python and/or JS? We need you to help with the satnogs-db web application! Take a look at our [https://gitlab.com/librespacefoundation/satnogs/satnogs-db source code], or visit our [https://gitlab.com/librespacefoundation/satnogs/satnogs-db/issues? issues tracker] to start filling bugs, feature requests or code fixes for existing ones.

==API==

More info can be found in [[SatNOGS DB/API|API wiki page]].

==Documentation & Installation==

You can find documentation and installation instructions about the project in our [https://docs.satnogs.org/projects/satnogs-db/en/stable/ Read the Docs instance].

==See also==

*[[SatNOGS Network]]
*[https://libre.space/2020/03/02/space-situational-awareness/ Space Situational Awareness – The story so far and an open way forward]

[[Category:Infrastructure]]
[[Category:Operate]]
[[Category:Satellite]]
[[Category:RF Modes]]

Troubleshooting Legacy

2024-03-04T09:51:43Z

Kerel+satnogs: Add "Observer job lock acquiring timed out" section

==Client troubleshooting==

{{Message| Before starting check the logs for an error:

* Check the whole error log with <code>journalctl -u satnogs-client.service</code>
* Check live the error log <code>journalctl -f -u satnogs-client.service</code>}}

{{Message|If the hints for common issues below don't help solve your issue, you are welcome to post in the forum. When doing so, please include any error from the logs and the output of the support report generated by the menu item <code>Advanced -> Support</code> from <code>sudo satnogs-setup</code>. This helps give context to the logging messages.}}
===Raise or Set the debug level===

*Run <code>sudo satnogs-setup</code>
*Go to '''Advanced Configuration''' and set the '''Debug level''' to one of the Values below
*'''Apply''' the change

{| class="wikitable"
!'''Setting'''
!Values
|-
|'''DEBUG'''
|
{| class="wikitable"
|<code>CRITICAL</code>
|-
|<code>ERROR</code>
|-
|<code>WARNING</code>
|-
|<code>INFO</code>
|-
|<code>DEBUG</code>
|-
|<code>NOTSET</code>
|}
|}

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

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

<pre>
The following signatures were invalid: EXPKEYSIG 8BD3901736A40B6C home:librespace OBS Project <home:librespace@build.opensuse.org>
</pre>

Fix:

<pre>
wget -qO - http://download.opensuse.org/repositories/home:/librespace:/satnogs-unstable/Raspbian_10/Release.key > k
gpg --no-default-keyring --keyring ./temp-keyring.gpg --import k
gpg --no-default-keyring --keyring ./temp-keyring.gpg --export --output k.gpg
mkdir /etc/apt/keyrings
mv k.gpg /etc/apt/keyrings/satnogs2.gpg
vi /etc/apt/sources.list.d/satnogs.list
</pre>
Insert a signed-by statement, as:
<pre>
deb [signed-by=/etc/apt/keyrings/satnogs2.gpg] /repositories/home:/librespace:/satnogs/Raspbian_11 - openSUSE Download ./
</pre>

More info available at https://community.libre.space/t/sudo-apt-update-signature-invalid/7643/7 and https://community.libre.space/t/update-to-the-invalid-signature-problem-in-the-troubleshooting-document/11386

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

=== ERROR - Observer job lock acquiring timed out. ===

<pre>
Mar 03 20:05:53 satnogs satnogs-client[257]: satnogsclient.scheduler.tasks - ERROR - Observer job lock acquiring timed out.
</pre>

This message is shown when a previous Observation failed (due to a hardware issue or some bug) and didn't properly terminate. To fix this issue, first check the logs for the observation that failed to understand the root cause. Then, restart satnogs-client.

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

Raspberry Pi

2024-02-20T21:41:23Z

Kerel+satnogs: /* Download */ Update to SatNOGS image release 2023111400

[[File:B3342fcc865731d69e0c9d7a8b1abb887185bc13 1 531x500.jpg|alt=Libre Space Foundation Raspberry Pi Case|thumb|Libre Space Foundation Raspberry Pi Case, [https://www.thingiverse.com/thing:3233687 on thingiverse]]]

==Introduction==

The Raspberry Pi (version 3 and 4) is the reference platform for SatNOGS (see our [[SatNOGS Client Ansible|Ansible guide]] to install SatNOGS on other Linux machines). You can try using various distributions for this (eg. Debian/Armbian, Arch, Fedora), but the one we suggest is our custom image based on latest Raspbian.

{{Message|This page assumes you have an account and a ground station registered on either network.satnogs.org or network-dev.satnogs.org. Make note of your station ID and API Key.}}

==Download==
'''<big>Raspbian SatNOGS Image:</big> <big>[https://gitlab.com/librespacefoundation/satnogs/satnogs-pi-gen/-/jobs/artifacts/2023111400/download?job=release artifacts.zip]</big> ''' (Release: 2023111400)

Download the latest Raspbian SatNOGS Image from above (or via the "Download" icon on the right side of the [https://gitlab.com/librespacefoundation/satnogs/satnogs-pi-gen/tags latest tag page on GitLab]). This image has the SatNOGS setup script installed, the SSH server enabled and all required packages preinstalled. You will get an <code>artifacts.zip</code> file with the following content:

*A Zipped image file
*An Image info file
*A SHA256 checksum file

===Data integrity verification===

You should verify the data integrity of the artifacts by comparing the SHA256 checksums. On Linux, run <code>sha256sum -c sha256sums</code> in the directory where the artifacts are downloaded and unzipped.

Example:
<pre>
$ sha256sum -c sha256sums
2023-11-14-Raspbian-SatNOGS-master-lite.info: OK
image_2023-11-14-Raspbian-SatNOGS-master-lite.zip: OK
</pre> 

==Flashing==
[https://www.raspberrypi.org/documentation/installation/installing-images/README.md Follow the usual Raspbian flashing instructions], and boot your Raspberry Pi.

You will need to set the login password for your Pi, as well as Wifi settings and Locale settings by clicking the "Advanced" options before writing the image.
[[File:Image.png|alt=Gear Icon for Rpi imager|left|thumb|73x73px]]

 
==Getting console access==
You can log in the Raspberry Pi by connecting it to a keyboard and monitor or through network via an SSH connection.

===Keyboard and monitor===
Once your Raspberry Pi is booted, log in with userID and password that you set during the imaging process.

===Ethernet===
If you are using wired Ethernet you should get connectivity right away. You just need to find the IP address of Raspberry Pi (e.g. in your router management interface). Log in with SSH using username you set during the image writing process. "'''pi'''" password "'''raspberry'''", in this example:
$ ssh pi@192.168.1.2
If your network supports [[wikipedia:Zero-configuration_networking|<code>zeroconf</code>]], then you can use the hostname of your Pi:
$ ssh pi@raspberrypi.local

===Pre-boot wireless configuration===
If neither keyboard/monitor, nor a wired Ethernet are available, you can set up a WiFi connection before boot by mounting the boot partition of the flashed SD card and editing files directly. Note your OS may mount boot partition in a different location. [https://raspberrypi.stackexchange.com/questions/10251/prepare-sd-card-for-wifi-on-headless-pi#comment98121_57023 Windows users have line ending problems]. Suggested actions:

$ $EDITOR /media/Raspbian_SatNOGS-boot/wpa_supplicant.conf

contents: (note key_mgmt options include NONE, WPA-PSK, WPA-EAP)

ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev
update_config=1
country=US

network={
ssid="NETWORK_NAME"
psk="password"
key_mgmt=WPA-PSK
}

===Pre-boot user creation===
The latest version of Raspberry Pi OS, of which the SatNOGS image is based on, '''does not''' have the "'''pi'''" user already upon first boot.

If you wish to login using ssh upon the first boot with the prior default username / password of "pi" / "raspberry", then:

*Create the file <code>userconf.txt</code> in the root of the <code>boot</code> partition of the uSD card.
*Its contents should be the single line:
**<code>pi:$6$/XOZsG1X0IAbhXB0$wYZHRkvib0SUKQA3KVAxofPR.JsFAbI2NCue2znGvhRsQobVdllFXyQZ7fMSvAoyEj8MfHtkMeSZT7IRIixg01</code>
**(the format is username:encrypted-password)

For more information about this file, see: [https://www.raspberrypi.com/documentation/computers/configuration.html#configuring-a-user Raspberry Pi Documentation - Configuration - Setting up a Headless Raspberry Pi - Configuring a User]
 
==Configuration==

===Raspberry Pi Setup===
If you used the advance settings during imaging, this step can be skipped.

Once your Raspberry Pi is booted, log in with the username you set up during the imaging process and run:
<pre>
$ sudo raspi-config
</pre>

You will want to be sure to do the following:

*Set a strong, unique password
*Change localization settings:
**by default the rpi locale is configured for EN-GB, change as appropriate (ie: to EN_US.UTF-8)
**set timezone (we recommend UTC so your logs match the times in Network; UTC is under the 'none of the above' submenu)
**set keyboard layout, again this is defaulting to a UK layout
**set wifi country
**expand filesystem (under the Advanced menu)
*Configure network or WiFi (see [https://www.raspberrypi.org/documentation/configuration/wireless/wireless-cli.md this doc for network configuration instructions])
*Finish and reboot

===SatNOGS Setup===
SSH to the Raspberry Pi with userID you set during imaging password.

Follow [[SatNOGS Client Setup]] instructions to configure the system.

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

Satellite Operator Guide

2023-01-10T08:42:55Z

Kerel+satnogs: /* 3. Operations */ Add Satellite Identification section

{{warning|This guide is intended for Satellite Operators. For SatNOGS Operations moderators please see [[SatNOGS Operations Manual]]}}
==Introduction==
You are building a satellite? Congratulations! The information below will be helpful for the Communications and Operations part of your mission. Plan early and invest time in COMMS and Ground Segment. As a community, SatNOGS is here to help you in the process!

Although the information is tailored for missions that will be using Amateur Radio bands of the spectrum, some information is still relevant for other parts of the band too.

==Process==
===0. Early Stage===
It's strongly advised to get in touch with the AMSAT of you country at the beginning of your project. It enables that the radio amateur requirements are taken in account at the early stage on your project. It avoids false expectations and miscommunications along the way. In order to use an Amateur Radio band, your mission needs to be Amateur Radio related. Broadly speaking this includes and Amateur Radio service (like a transponder) or Amateur Radio experiment (new modulations, propagation experiments etc).
===1. Frequency Coordination===
First you need to determine whether you'll require an amateur frequency, a non-amateur frequency, or both.

Historically educational but non-Amateur Radio satellite operators (e.g. university research projects) were often improperly permitted to use amateur spectrum on a not-commercial basis. As this practice has led to serious congestion of the Amateur Radio Service, the IARU will no longer coordinate amateur frequency allocation for this purpose. Therefore:

*If your satellite will be purely for Amateur Radio use (i.e. all of its major functions will be available for use by all licensed Amateur Radio operators), then you're usually able to request Amateur Radio Space Service frequency coordination from IARU. You remain free to perform limited control functions on Amateur Radio spectrum. If there is an AMSAT organization in your country, start there. If not, approach your national Amateur Radio body. They will usually help you to get a radio amateur frequency coordination from IARU your allocation. It will take time: usually between six months and a year. If you don't ask for an IARU coordination, the launcher of your satellite may not allow you to launch the satellite.
*If your satellite will have substantial non-Radio Amateur use (sensor data, imagery, space-qualification of components, ...) then you will usually require a (non-amateur) Space Service license and frequency allocation. Approach your local radio communication regulator directly to start this process, which will have to finalized through ITU.
*If your satellite will do both, then you'll require licenses and frequency allocation/coordination for both services. A recent example is [https://www.amsat.org/falconsat-3/ FalconSAT-3].

====1.1 Publicly and openly document your Communications====
If you are planning to use a Radio Amateur band you are required to publicly and openly document ever singe detail of your transmission. That includes your modulation, encoding, framing and various functions. Your uplink and TC operations might not be publicly documented if you choose so.

Regardless of your band usage, we would strongly advise you to openly document your Communications since Open Data is a core pillar of sustainable and efficient Space operations. See the [https://manifesto.libre.space/ Libre Space Manifesto] for more info.

===2. Integration with SatNOGS===
====2.1 Reasons to Join====
You have recently discovered SatNOGS and you are involved in a mission. Here are the top 10 reasons why your mission should join SatNOGS:

#SatNOGS can help streamline your mission operations (Dashboards, Monitoring, Telemetry acquisition)
#SatNOGS is open source technology. Every piece of technology we develop is licensed as an open source project (software and hardware), which you can learn from, re-mix, re-use and contribute!
#SatNOGS is a global community of satellite enthusiasts, radio amateurs and satellite operators! [[Get In Touch|Join our community and be part of it.]]
#SatNOGS is best suited for educational, research, non-profit, experimental and amateur missions. Libre Space Foundation[https://libre.space/] that runs SatNOGS is committed on supporting those missions.
#SatNOGS is the largest global ground station network. 400 stations online with a spread around the world. No other network can beat that :)
#SatNOGS is non-profit. Our sustainability is funded through development funds, custom development if needed and a viral model of adding ground stations to the network. Using the network is as simple as adding another station to it!
#SatNOGS is full of educational opportunities. Great learning material, documentation and a vibrant community can help you get up to speed for mission COMMS and Operations.
#SatNOGS modular technology stack allows you to integrate with your existing space and ground station hardware easily. We support many COTS hardware or can easily add support for more.
#SatNOGS provides also a vertical approach if you choose to opt-in for tested integration through Libre Space Foundation space qualified hardware COMMS options (SatNOGS COMMS[https://gitlab.com/librespacefoundation/satnogs-comms/] and PQ9ISH COMMS[https://gitlab.com/librespacefoundation/pq9ish/pq9ish-comms-vu-hw/]).
#SatNOGS is a project abiding to the Libre Space Manifesto [https://manifesto.libre.space/].

 

====2.2 Add a new Mission====
Do you want to integrate your mission with SatNOGS? Cool! Here is a short guide how to do this. Please also reach out to us via [[Get In Touch|chat or community]] so that we can support you. Checklist:

#SatNOGS DB
#*Suggest to add your satellite to satnogs-db by creating an issue in [https://gitlab.com/librespacefoundation/satnogs-ops/issues satnogs-ops] providing the following information:
#**Name
#**NORAD catalog number (if already assigned)
#**Amateur Radio call sign (if Amateur service)
#**Description
#**Project Website
#**Image of the satellite
#*Once the new satellite was added to satnogs-db by one of the satnogs-ops team members, find your satellite in [https://db.satnogs.org/ db.satnogs.org] and add a transmitter suggestion for each transmitter of your satellite
#SatNOGS GNURadio
#*Choose one of the existing flowgraphs in [https://gitlab.com/librespacefoundation/satnogs/gr-satnogs gr-satnogs] or provide a new one
#SatNOGS Client
#*If you added a new flowgraph under the previous point, make sure to add support for it in [https://gitlab.com/librespacefoundation/satnogs/satnogs-client satnogs-client]
#*Wait for the next release of [https://gitlab.com/librespacefoundation/satnogs/satnogs-client-ansible/ satnogs-client-ansible], then let the station owners know that your satellite is supported now and ask them to update their stations.
#SatNOGS Decoders
#*Add a decoder written in [https://kaitai.io/ Kaitai] to [https://gitlab.com/librespacefoundation/satnogs/satnogs-decoders satnogs-decoders]
#SatNOGS Dashboard
#*To obtain editor permissions to build a SatNOGS Dashboard for your mission you need an account in the LSF SSO system. To get this, go to https://dashboard.satnogs.org/login and press "Sign-in with Auth0". On the following page select sign-up to register.
#*Sign-in to https://dashboard.satnogs.org once (you will have read permissions for now).
#*Please create an issue in https://gitlab.com/librespacefoundation/satnogs-ops/-/issues with the following details:
#**The Satellite
#**Your Satellite Team
#**Your email address used for the login
#*Once you got editor permissions, you can create a new dashboard in [https://dashboard.satnogs.org dashboard.satnogs.org] for your satellite.
{{warning|In order to have scheduling rights in SatNOGS Network, you need to own an operational Online Station in the Network. Consider building one, or donating one in the Network.}}
==3. Operations==

=== 3.1 Launch Operations / Satellite Identification ===
A few weeks / days before the launch, a contributor will create the '''Launch Thread''' for every planned launch in the [https://community.libre.space/c/satellites-observations/launches/26 Launches] category of our community. This thread is supposed to collect information about the satellites that will be launched and about when and where this will happen.

After the launch all communication about identifications / deployments / determined orbits / operational status are shared in this launch thread. Keeping the information for all satellites of a single launch in one thread is tremendously helpful for coordinating between missions! For example identifying two of three satellites in a train will allow the identification by exclusion principle of the third one. Note however that for launches with many satellites this thread is quite busy. So if you e.g. intent to describe your mission in detail you can open a separate thread for your mission in the [https://community.libre.space/c/satellites-observations/16 Satellites & Observations] category.

You are highly welcomed to participate in this thread, for example by stating the affiliation with your mission, sharing the expected orbit, frequencies and modulations or sharing the identification of your satellite. If you share identifications please always shortly explain how you got to a certain TLE (e.g. from on-board GPS, via doppler measurements or using the exclusion principle).

'''<big>We wish you a successful mission. Claim Space, the Libre Way!</big>'''
 
==See Also==

*[[DB|SatNOGS DB]]
*[[Network|SatNOGS Network]]
*[[Forum|Community Forum]]
*[[Get In Touch]]

[[Category:Satellite]]
[[Category:RF Modes]]

Wiki/Replay observations from audio

2022-10-26T11:04:05Z

Kerel+satnogs: Create page

{{Message|This page is under construction.}}

using the ogg audio from bpsk obs to replay and tune around the recorded band

Build

2022-08-17T09:49:27Z

Kerel+satnogs: Remove link to platform "Fedora" (broke & not supported anymore for quite some years)

__NOTOC__
==Introduction==

Building a ground station need not be complicated. There are a few things to consider when working out what it is you are going to do. Choices such as the desire to have a fixed or steerable ground station will play a big part in the amount of equipment needed and the time taken as well as the complexity of any build. If you are new to this and a little unsure then a fixed (no rotator) option is a good choice. If you fancy a challenge and want to pick out the weakest signals then the steerable ground station might be what you are after. There is more detail in the [[Ground Stations]] page

The illustration below sets out the various major components to give an idea as to what is commonly used.

==Options for Ground Stations==

A satellite ground station is made up from different parts. The following diagram can help you select your setup based on your needs and/or your existing setup.

[[File:Satnogs_imagemap.png|center]]

Here are some links explaining the different options:

{| class="wikitable" style="margin: 0 auto;"
!Platform
!Controller
![[Rotators|Rotator]]
!Radio
![[Antennas|Antenna]]
|-
|[[Raspberry_Pi|Raspberry Pi]]
|[[SatNOGS Rotator Controller|SatNOGS Controller]]
|[[SatNOGS_Rotator_v3|SatNOGS Rotator]]
|[[Radio#SDR|SDR]]
|[[Antennas|Yagi]]
|-
|[[SatNOGS_Client_Ansible|Debian system]]
|[http://spid.net.pl/en/rot2prog-2/ Rot2Prog]
|[[SPID Big RAS]]
|
|[[Antennas|Helical]]
|-
|[[Linux Desktop]]
|[[G-5500|lsf-g5500]]
|[[G-5500|Yaesu G5500]]
|
|[[Antennas|Vertical]]
|-
|
|[https://wiki.satnogs.org/SatNOGS_Arduino_Uno/CNC_Shield_Based_Rotator_Controller Arduino UNO CNC Shield based controller]
|[[No rotator]]
|
|[[Antennas|Cross-Yagi]]
|-
|
|[https://community.libre.space/t/ramps-1-4-board-for-satnogs-rotator/3386 RAMPS 1.4 Board for SatNOGS Rotator]
|[[SuperAntennaz|SuperAntennaz]]
|
|-
|}

{{Message|Use the above table to select your setup. E.g. RPi3 > Yaesu G550 > SDR > UHF helical & VHF Cross Yagi}}

==How do I pick?==

'''Client''': The Raspberry Pi is the reference platform for SatNOGS, and is currently the option that has the best support from the community. Certain SDRs may benefit from a more powerful CPU, like what you'd find in a desktop machine; however, currently you'll need to set that up on your own.

'''Rotator''': A rotator, like the [[SatNOGS_Rotator_v3|SatNOGS Rotator v3]], will allow your antenna to follow satellites as they move across the sky, and thus pick up fainter signals. But if you want to get started quickly, or don't have the hardware skills to build your own, you can still pick up stronger signals (the ISS, NOAA and Meteor weather satellites) with a [[No_rotator|no-rotator]] setup. If you already have [https://github.com/Hamlib/Hamlib/wiki/Supported-Rotators a rotator supported by rotctl], you can use that.

'''Signal Reception''': The reference radio for SatNOGS is the [https://www.rtl-sdr.com RTL-SDR v3], but other latest-generation SDRs like the [http://www.nooelec.com/store/nesdr-smart-sdr.html NooElec NESDR SMart] should work as well. Higher-end SDRs should work as well, but can get a bit expensive. Alternately, [https://sourceforge.net/p/hamlib/wiki/Supported%20Radios/ any radio supported by rigctl] should work.

Amplification is generally done by a low noise amplifier, or LNA. There are multiple options:

*A wide-band LNA next to your SDR (see [http://lna4all.blogspot.com/ LNA4ALL], [https://iz7boj.wordpress.com/2019/04/11/spf5189z-lna-measurements-on-vna/ SPF5189] and similar)
*A band specific (or two) pre-amplifiers next to your antennas ([http://www.wimo.com/mast-preamplifier_e.html example])
*No amplification at all...just pump the gain of your SDR. (This is not recommended for the rtl-sdr.)

'''Antenna''': Stationary antennas (eg: [https://en.wikipedia.org/wiki/Turnstile_antenna Turnstile], [https://community.libre.space/t/parasitic-lindenblad-on-uhf/1128/2 Lindenblad]) will be easy to build and mount, as they won't require rotator hardware. They will let you receive stronger broadcasts, like NOAA weather satellites and ISS broadcasts, but may not work for receiving fainter cubesat broadcasts. Directional antennas (eg: Yagis, Helicals) can be more complicated to build, but will also require a rotator to track satellites across the sky. The advantage is that they will let you pick up fainter broadcasts from cubesats or ham radio satellites. Sometimes it's useful the ability of [[Antenna switching|switch]] different antennas among observations.

==Next steps==

Once you have a ground station ready, you should go ahead and operate it! More info can be found on the [[Operation]] wiki page.

[[Category:Build]]
[[Category:Hardware]]

SatNOGS Client Development

2022-08-12T21:55:58Z

Kerel+satnogs: /* Setting up a gr-satnogs development environment */

==Intro==
This page describes the setup of a development environment for the
SatNOGS ground station reference setup based on [https://gitlab.com/librespacefoundation/satnogs/satnogs-client-ansible satnogs-client-ansible].
It is assumed you have already setup your ground station as explained in [[SatNOGS_Client_Setup]].

==satnogs-flowgraphs==
For each Satellite Transmitter Mode there is a specific flowgraph in this package. There are generic (e.g. CW) and satellite-specific flowgraphs. The Satellite-Transmitter-Mode-to-flowgraph mapping is defined in satnogs-client. This package is using gr-soapy for SDR hardware support and gr-satnogs for required GNURadio blocks.
 
==gr-satnogs==

The gnuradio Out-Of-Tree module [https://gitlab.com/librespacefoundation/satnogs/gr-satnogs gr-satnogs] provides blocks required by satnogs-flowgraphs. The gitlab-CI automatically builds the package in docker containers, configured by the [https://gitlab.com/librespacefoundation/satnogs/gr-satnogs/blob/master/.gitlab-ci.yml .gitlab-ci.yml]. The built packages for releases are pushed to the librespace:satnogs package repository, the built package for the latest development version on master is pushed to the librespace:satnogs-unstable package repository.

To use a modified gr-satnogs module on a SatNOGS ground station, it’s recommended to clone your fork on your station, build the patched gr-satnogs packages and install it.

To install the latest development version of gr-satnogs on your station, set <code>experimental=True</code> or configure in <code>satnogs-setup</code>.

 

===Setting up a gr-satnogs development environment===

OUTDATED since [https://gitlab.com/librespacefoundation/satnogs/satnogs-client-ansible/-/commit/336a3206fbeec8e1a5257ce375578f31a92988e4 satnogs-client-ansible@336a320]!

*Fork gr-satnogs
*Fork gr-satnogs-package
*Adjust the repository url of gr-satnogs in [https://gitlab.com/librespacefoundation/satnogs/gr-satnogs-package/blob/master/debian/debian/rules#L22 gr-satnogs-package/debian/debian/rules#L22]
*Adjust the repository url in the version detection in [https://gitlab.com/librespacefoundation/satnogs/gr-satnogs-package/blob/master/.gitlab-ci.yml#L13 gr-satnogs-package/.gitlab-ci.yml#L13] ,[https://gitlab.com/librespacefoundation/satnogs/gr-satnogs-package/blob/master/.gitlab-ci.yml#L30 #L30] ,[https://gitlab.com/librespacefoundation/satnogs/gr-satnogs-package/blob/master/.gitlab-ci.yml#L47 #L47]
*Wait for the gitlab-CI to build your first version of gr-satnogs-package (~45 min)
*Install your freshly built gr-satnogs-package by pointing the <code>SATNOGS_RADIO_GR_SATNOGS_PACKAGE</code> in satnogs-setup to the built artifact/debian package of your architecture (e.g. <code>armhf</code>, <code>amd64</code>). The build artifacts are available in your gr-satnogs-package fork by clicking CI/CD, selecting there the latest pipeline, the latest build-job and then in the right column <code>Browse</code>, path <code>build/debian/output/$your_arch/gr-satnogs_$your_arch.deb</code>

==satnogs-client==
The [https://gitlab.com/librespacefoundation/satnogs/satnogs-client satnogs-client] is a python package, and gets installed by satnogs-setup in a python virtual environment using [https://pip.pypa.io/ pip]. The development is done in the <code>master</code> branch.

Please note that satnogs-client and satnogs-flowgraphs must be installed in compatible versions, due to (frequent) changes in the arguments available in the demodulation scripts, see [[Compatibility]].
===Setting up a satnogs-client development environment===

#Fork [https://gitlab.com/librespacefoundation/satnogs/satnogs-client satnogs-client]
#Clone the repository on your development machine
#Create a new branch (e.g. station123) with your changes & push it
#Run satnogs-setup and change the value of <code>SATNOGS_CLIENT_URL</code> to point to your repository and branch as described in [[SatNOGS_Client_Setup#Advanced_Setup]]
#Hit "Apply" in satnogs-setup to finally install your satnogs-client version
#Profit.

=== Miscellaneous development notes ===

* [[How to bodge an immediate observation in for testing purposes]]

[[Category:Develop]]
[[Category:Software]]

SatNOGS Client Development

2022-08-12T21:54:27Z

Kerel+satnogs: /* Setting up a gr-satnogs development environment */

==Intro==
This page describes the setup of a development environment for the
SatNOGS ground station reference setup based on [https://gitlab.com/librespacefoundation/satnogs/satnogs-client-ansible satnogs-client-ansible].
It is assumed you have already setup your ground station as explained in [[SatNOGS_Client_Setup]].

==satnogs-flowgraphs==
For each Satellite Transmitter Mode there is a specific flowgraph in this package. There are generic (e.g. CW) and satellite-specific flowgraphs. The Satellite-Transmitter-Mode-to-flowgraph mapping is defined in satnogs-client. This package is using gr-soapy for SDR hardware support and gr-satnogs for required GNURadio blocks.
 
==gr-satnogs==

The gnuradio Out-Of-Tree module [https://gitlab.com/librespacefoundation/satnogs/gr-satnogs gr-satnogs] provides blocks required by satnogs-flowgraphs. The gitlab-CI automatically builds the package in docker containers, configured by the [https://gitlab.com/librespacefoundation/satnogs/gr-satnogs/blob/master/.gitlab-ci.yml .gitlab-ci.yml]. The built packages for releases are pushed to the librespace:satnogs package repository, the built package for the latest development version on master is pushed to the librespace:satnogs-unstable package repository.

To use a modified gr-satnogs module on a SatNOGS ground station, it’s recommended to clone your fork on your station, build the patched gr-satnogs packages and install it.

To install the latest development version of gr-satnogs on your station, set <code>experimental=True</code> or configure in <code>satnogs-setup</code>.

 

===Setting up a gr-satnogs development environment===

OUTDATED since [https://gitlab.com/librespacefoundation/satnogs/satnogs-client-ansible/-/commit/90e4fc476f5b2a7a103068afb2e9d18d70dcf00e satnogs-client-ansible@90e4fc4]!

*Fork gr-satnogs
*Fork gr-satnogs-package
*Adjust the repository url of gr-satnogs in [https://gitlab.com/librespacefoundation/satnogs/gr-satnogs-package/blob/master/debian/debian/rules#L22 gr-satnogs-package/debian/debian/rules#L22]
*Adjust the repository url in the version detection in [https://gitlab.com/librespacefoundation/satnogs/gr-satnogs-package/blob/master/.gitlab-ci.yml#L13 gr-satnogs-package/.gitlab-ci.yml#L13] ,[https://gitlab.com/librespacefoundation/satnogs/gr-satnogs-package/blob/master/.gitlab-ci.yml#L30 #L30] ,[https://gitlab.com/librespacefoundation/satnogs/gr-satnogs-package/blob/master/.gitlab-ci.yml#L47 #L47]
*Wait for the gitlab-CI to build your first version of gr-satnogs-package (~45 min)
*Install your freshly built gr-satnogs-package by pointing the <code>SATNOGS_RADIO_GR_SATNOGS_PACKAGE</code> in satnogs-setup to the built artifact/debian package of your architecture (e.g. <code>armhf</code>, <code>amd64</code>). The build artifacts are available in your gr-satnogs-package fork by clicking CI/CD, selecting there the latest pipeline, the latest build-job and then in the right column <code>Browse</code>, path <code>build/debian/output/$your_arch/gr-satnogs_$your_arch.deb</code>

==satnogs-client==
The [https://gitlab.com/librespacefoundation/satnogs/satnogs-client satnogs-client] is a python package, and gets installed by satnogs-setup in a python virtual environment using [https://pip.pypa.io/ pip]. The development is done in the <code>master</code> branch.

Please note that satnogs-client and satnogs-flowgraphs must be installed in compatible versions, due to (frequent) changes in the arguments available in the demodulation scripts, see [[Compatibility]].
===Setting up a satnogs-client development environment===

#Fork [https://gitlab.com/librespacefoundation/satnogs/satnogs-client satnogs-client]
#Clone the repository on your development machine
#Create a new branch (e.g. station123) with your changes & push it
#Run satnogs-setup and change the value of <code>SATNOGS_CLIENT_URL</code> to point to your repository and branch as described in [[SatNOGS_Client_Setup#Advanced_Setup]]
#Hit "Apply" in satnogs-setup to finally install your satnogs-client version
#Profit.

=== Miscellaneous development notes ===

* [[How to bodge an immediate observation in for testing purposes]]

[[Category:Develop]]
[[Category:Software]]

Software Defined Radio

2022-08-09T08:52:47Z

Kerel+satnogs: Airspy section: Add example station 1559 (DB2OS-VHF Omni)

==Introduction==

Built upon [https://gnuradio.org/ GNU Radio] and [https://github.com/pothosware/SoapySDR/wiki SoapySDR] by using the [https://gitlab.com/librespacefoundation/gr-soapy gr-soapy] module SatNOGS supports a large variety of Software-Defined Radios (SDRs). The gr-soapy module was developed in the [https://sdrmaker.space/ SDR Makerspace] and is maintained by Libre Space Foundation to bring the vendor-neutral SDR support by SoapySDR to the flexible gnuradio ecosystem.

The most cost-effective solution is to use an RTL-SDR with a Raspberry Pi. More advanced SDRs are also used, but they require more processing power and thus might require a more powerful computing platform than the Raspberry Pi.

==Supported Devices==

SoapySDR supports SDR devices through runtime-loadable modules [https://github.com/pothosware/SoapySDR/wiki#plugin-architecture]. You can find all available modules in the [https://github.com/pothosware/SoapySDR/wiki#modules SoapySDR wiki] (see right column). Most SDR modules are installed by default when setting up a SatNOGS station.

The following SDRs are supported by SatNOGS. SatNOGS uses the RTL-SDR as the recommended beginner signal receiver and tuner.
The more advanced SDRs may require more processing power than a Raspberry Pi 3b or 4 can offer.

*[[Software Defined Radio#RTL-SDR Support|RTL-SDR]]
**[https://www.nooelec.com/store/sdr/sdr-receivers.html NooElec NESDR SMArt]
**[https://www.rtl-sdr.com/buy-rtl-sdr-dvb-t-dongles/ RTL-SDR Blog R820T2 RTL2832U]
**Full band UV HF RTL-SDR USB Tuner Receiver

*[[Software Defined Radio#USRP support|USRP devices]]
**[https://www.ettus.com/product/category/USRP-Bus-Series USRP B200]

*[[Software Defined Radio#Airspy support|Airspy]]
*[[Software Defined Radio#LimeSDR support|LimeSuite devices]]
**[https://limemicro.com/products/boards/limesdr-mini/ LimeSDR mini]
*[[Software Defined Radio#PlutoSDR support|PlutoSDR]]
**[https://www.analog.com/en/design-center/evaluation-hardware-and-software/evaluation-boards-kits/adalm-pluto.html#eb-overview ADALM-PLUTO] (untested)

{{Message|There are probably a lot more devices supported since the transition from gr-osmosdr to gr-soapy. Please update this list when you were able to successfully run a SatNOGS station with a new radio family or model. You can also link your station as an example to give others the ability to compare performance.}}

==Supported Devices with closed-source drivers==
Unfortunately some vendors require closed-source drivers in their SoapySDR modules and thus those modules or dependencies can't be redistributed by others. Thus they must be manually installed by the user. The following devices require closed-source drivers:

*[[Software Defined Radio#SDRPlay support|SDRPlay]]

==Unsupported Devices==
{{Warning|This section might be outdated due to the transition to gr-soapy. Please update when possible.}}
 

*[https://greatscottgadgets.com/hackrf/ HackRF One] (not compatible with the SatNOGS client on Raspberry Pi, ''Update: works fine now on a Pi4, only tested with the 8GB version of the Pi4. Will probably work with a 2/4GB version too. Not tested on a Pi3, might not be powerful enough to handle 8MS/s'')

==RTL-SDR Support==
The RTL-SDR is based on two chips -- the versatile [http://www.realtek.com.tw/products/productsView.aspx?Langid=1&PFid=35&Level=4&Conn=3&ProdID=257 RTL2832U chip] and the [https://rtl-sdr.com/wp-content/uploads/2013/04/R820T_datasheet-Non_R-20111130_unlocked.pdf R820T tuner]. The RTL-SDR is currently the cheapest, most common, and most performing solution available in terms of general sensitivity having a frequency range of 24 – 1766 MHz. A metal enclosure with SMA connector is preferred, along with a stable TCXO (low ppm). HF coverage is optional.

 

===Using RTL-SDR.com V3 Dongle's Bias-T Power Supply===
The RTL-SDR.com V3 dongle has a built in software activated Bias-T voltage supply intended to be used for applications such as powering inline LNAs (Low Noise Amplifiers). There are several ways to turn on the voltage, but through initial testing (as of this writing, 17 Aug 2019) it seems that the following procedure works best.

The below relates to Raspberry Pi installs only. No testing has been performed on other systems as of yet.

{{Warning|Turning on the Bias-T with no LNA installed and a "shorted" style antenna (such as loops, egg-beaters, etc.) can damage the RTL-SDR.com V3 dongle. Never activate the bias-t with no LNA installed between the antenna and the SDR dongle.}}

'''Requirements:'''

#Raspberry Pi running Raspbian Buster or newer (latest release of SatNogs image, [https://gitlab.com/librespacefoundation/satnogs/satnogs-pi-gen/-/tags 2019091100], is demonstrated to work)
#[https://www.rtl-sdr.com/buy-rtl-sdr-dvb-t-dongles/ RTL-SDR.com V3 SDR dongle]
#[https://www.rtl-sdr.com/rtl-sdr-blog-v-3-dongles-user-guide/ RTL-SDR.com Bias-T Software Switch] for linux systems
#LNA capable of being powered via feedline coax (note that some LNAs need modifications to be powered by the coax, and some cannot be powered by the coax at all. Check the specifications for your LNA prior to attempting to turn on the Bias-T power supply)

 

====Instructions for installing RTL-SDR.com Bias-T Software Switch====

#Log into your SatNogs station either directly or via SSH
#If your station does not have cmake installed (SatNogs Image 2019091100 does not), install cmake with <code>sudo apt install cmake</code>
#Clone the source for the Bias-T software switch with <code>git clone <nowiki>https://github.com/rtlsdrblog/rtl_biast</nowiki></code>
#<code>cd rtl_biast</code>
#<code>mkdir build</code>
#<code>cd build</code>
#<code>cmake ..</code> (if you get a <code>LibUSB 1.0 required to compile rtl-sdr</code> error here, then do <code>sudo apt install libusb-1.0-0-dev</code> prior to attempting <code>cmake ..</code> again)
#<code>make</code>

The software switch should now be installed in the "src" directory. If you <code>cd src</code>, you can turn on the bias-t with the command <code>./rtl_biast -b 1</code> and turn it off with <code>./rtl_biast -b 0</code>. Note that the developers of this switch have warned against attempting to <code>sudo make install</code> so that this command can be executed from ouside the src directory. Testing has shown this warning to be accurate, so don't plan on running these commands from anywhere but the src directory, or else be sure to use the full path.

Switching the Bias-T on should yield between 4.5V and 5.0V across the center conductor and shield of the coax. The voltage should rise almost instantly. When switched off, the voltage seems to decrease gradually, over 5 to 10 seconds.

====Instructions to activate the bias-t for SatNogs Observations automatically:====

#Log into your SatNogs station either directly or via SSH
#<code>sudo satnogs-setup</code>
#select <code>Advanced</code>
#for <code>Radio</code> -><code>SATNOGS_RF_GAIN</code>, enter a low gain value supported by your RTL-SDR.com V3 dongle (entering <code>rtl_test</code> at the command line prior to starting <code>satnogs-setup</code> will give you all allowable values of RF gain) and select <code>Ok</code>
#for <code>Scripts</code> -><code>SATNOGS_PRE_OBSERVATION_SCRIPT,</code> enter <code>/home/pi/rtl_biast/build/src/rtl_biast -b 1</code> and select <code>Ok</code>
#for <code>Scripts</code> -><code>SATNOGS_POST_OBSERVATION_SCRIPT,</code> enter <code>/home/pi/rtl_biast/build/src/rtl_biast -b 0</code> and select <code>Ok</code>
#Select <code>Back</code>
#Select <code>Apply</code> (allow system to update and hit enter when prompted)
#Select <code>Back</code>

Your station is now set up to turn the Bias-T on for each scheduled observation (using the <code>SATNOGS_PRE_OBSERVATION_SCRIPT</code> string) and then turn it off at the conclusion of each observation (using the <code>SATNOGS_POST_OBSERVATION_SCRIPT</code>).

You should now schedule several observations to fine tune the <code>SATNOGS_RF_GAIN</code> value to get the best S/N performance for your station. Some have reported needing zero RF gain, others have reported low RF gain required (between 5 and 10 db), and others have said they see little benefit even with very high gain. Each station will be different.

====E4000 Tuner Gain Settings====
The RTLSDR Driver exposes six (!) IF gain settings (IF1 through IF6) for the E4000 tuner, along with a TUNER gain setting, which is actually a combined LNA and Mixer gain control. Details on the gain stages are available in page 28 of the E4000 data-sheet here: https://www.nooelec.com/files/e4000datasheet.pdf

When you follow the '[[Omnidirectional Station How To#Setting the gain|Setting the Gain]]' guide, all gain sliders (IF1 through IF6, and TUNER) should be presented in SoapySDR, allowing the user to adjust them to optimise for best performance. Once the correct values have been determined, you will need to define these specifically in satnogs-setup as follows:

*<code>SATNOGS_GAIN_MODE</code>=<code>"Settings Field"</code>
*<code>SATNOGS_OTHER_SETTINGS</code>=<code>"IF1=6,IF2=3,IF2=2,IF3=0,IF4=0,IF5=2,IF6=3,TUNER=30"</code>

(Replacing the values in the line above with the ones you determined)

====R820T Gain Settings====
Unfortunately librtlsdr only exposes a single gain control for the R820T/T2 tuners, even though multiple gain adjustments are available. Use the standard SATNOGS_RF_GAIN option, with a gain between 0 and 42 (dB), as optimised for your station via the '[[Omnidirectional Station How To#Setting the gain|Setting the Gain]]' guide.

==Airspy support==
Vendor: [https://airspy.com/ Airspy]

required SoapySDR module: [https://github.com/pothosware/SoapyAirspy/wiki SoapyAirspy]

Example stations:

*[https://network.satnogs.org/stations/1559/ 1559 - DB2OS-VHF-Omni] / [https://network.satnogs.org/observations/6307151/ Observation #6307151]

'''Note than none of the settings below should be entered with the " " around the value. This is only for better readability in the Wiki !'''

===Gain settings===
There are two possible gain modes:

*<code>SATNOGS_GAIN_MODE</code>=<code>"Overall"</code>: (default) Use a single gain value. Set the overall gain with <code>SATNOGS_RF_GAIN</code>,e.g. <code>SATNOGS_RF_GAIN</code>=<code>43</code>.
*<code>SATNOGS_GAIN_MODE</code>=<code>"Settings Field"</code>: Use granular gain values. Set the different gain stages separately:
**without pre-amp: <code>SATNOGS_OTHER_SETTINGS</code>=<code>"LNA=12,MIX=8,VGA=11"</code>
**with pre-amp: <code>SATNOGS_OTHER_SETTINGS</code>=<code>"LNA=9,MIX=6,VGA=11"</code> (used in [https://network.satnogs.org/stations/49/ 49 - OZ7SAT])

For reference see also the Airspy driver library linearity gain settings in [https://github.com/airspy/airspyone_host/blob/bceca18f9e3a5f89cff78c4d949c71771d92dfd3/libairspy/src/airspy.c#L117-L122 libairspy/src/airspy.c#L117-L122].

The airspy driver offers "Linearity" and "Sensitivity" gain settings, using a look-up table to configure all three gain stages from a single value (optimized for linearity and gain respectively). Those modes are unfortunately not available through the SoapyAirspy module (see [https://github.com/pothosware/SoapyAirspy/pull/14 SoapyAirspy#14]).

The "Overall" gain mode is a soapy-specific driver-independent mode to configure all gain stages based on the single gain value from <code>SATNOGS_RF_GAIN</code>. It tries to evenly distribute the gain, potentially resulting in non-optimal configuration. Thus for achieving optimal results the "Settings Field" mode is recommended, where all three gain stages can be configured separately.

===Sample rates===

*Airspy R2: <code>SATNOGS_RX_SAMPLE_RATE</code>=<code>2.5e6 or 10e6</code>
*Airspy Mini: <code>SATNOGS_RX_SAMPLE_RATE</code>=<code>3e6 or 6e6</code>
*Airspy HF+: <code>SATNOGS_RX_SAMPLE_RATE</code>=<code>768e3</code>

source: [https://twitter.com/DutchSpace/status/1241305651168661504]

If you want to activate the integrated bias tee, set <code>SATNOGS_DEV_ARGS</code>=<code>"biastee=true"</code>.
Bit packing ("Enable packing 4 12-bit samples into 3 16-bit words for 25% less USB trafic.") could be enabled with <code>SATNOGS_DEV_ARGS</code>=<code>"bitpacking=true"</code> (untested). Device arguments can be concatenated with comma as delimiter.

==SDRPlay support==
Vendor: [http://www.sdrplay.com/ SDRPlay]

required SoapySDR module: [https://github.com/pothosware/SoapySDRPlay SoapySDRPlay]

The following settings [https://network.satnogs.org/observations/?norad=&observer=&station=1354&results=d1&start=2020-02-20+00%3A00&end=2020-02-24+23%3A59 worked well] for an [https://www.sdrplay.com/rspduo/ SDRplay RSPduo] when using cross-yagis and good [https://www.ssb.de/en/amplifiers/preamplifier/vox/100w SSB low-noise amplifiers]:

*<code>SATNOGS_SOAPY_RX_DEVICE="driver=sdrplay"</code>
*<code>SATNOGS_RX_SAMP_RATE=2e6</code>
*<code>SATNOGS_RX_BANDWIDTH=600e3</code>
*<code>SATNOGS_RF_GAIN=34</code>
*<code>SATNOGS_ANTENNA="Tuner 1 50 ohm"</code>

Note that 14-bits ADC resolution is only available when using sample rates below 6.048 MSPS, above which the resolution is reduced gradually to 12, 10, and 8 bits.

==USRP support==
Vendor: [https://ettus.com Ettus Research]

required SoapySDR module: [https://github.com/pothosware/SoapyUHD/wiki SoapyUHD]

Recent USRPs that use the Analog Devices [https://www.analog.com/en/products/ad9361.html AD9361 RFIC] can use almost arbitrary sample rates and analog bandwidth settings. It can be an advantage to set the sample rate as high as the host computer can handle and the analog bandwidth to as narrow as meaningful. The following settings [https://network.satnogs.org/observations/?norad=&observer=&station=1353&results=d1&start=2020-02-20+00%3A00&end=2020-02-24+23%3A59 worked well] for a [https://www.ettus.com/all-products/ub210-kit/ USRP B210] when using cross-yagis and good [https://www.ssb.de/en/amplifiers/preamplifier/vox/100w SSB low-noise amplifiers]:

*<code>SATNOGS_SOAPY_RX_DEVICE="driver=uhd"</code>
*<code>SATNOGS_RX_SAMP_RATE=2e6</code>
*<code>SATNOGS_RX_BANDWIDTH=600e3</code>
*<code>SATNOGS_RF_GAIN=50</code>
*<code>SATNOGS_ANTENNA="RX2"</code>
**on the B200 your Antenna options are <code>TX/RX</code> and <code>RX2</code>, be sure you select the right option for your configuration!

==LimeSDR support==
Vendor: [https://limemicro.com Lime microsystems]

required SoapySDR module: [https://github.com/myriadrf/LimeSuite/tree/master/SoapyLMS7 SoapyLMS7 wrapper]

*<code>SATNOGS_SOAPY_RX_DEVICE</code>=<code>"driver=lime"</code>
*<code>SATNOGS_RX_SAMP_RATE</code>=<code>"2.048e6"</code>
*<code>SATNOGS_ANTENNA</code>=<code>"LNAW"</code>
*<code>SATNOGS_GAIN_MODE</code>=<code>"Settings Field"</code>
*<code>SATNOGS_RF_GAIN</code>=<code>20</code>
*<code>SATNOGS_OTHER_SETTINGS</code>=<code>"TIA=12,PGA=0,LNA=12"</code>

(untested, copied from station 1378)

Example stations:

*[https://network.satnogs.org/stations/1378/ 1378 - Wolbach library]

==PlutoSDR support==
Vendor: [https://www.analog.com Analog Devices]

required SoapySDR module: [https://github.com/pothosware/SoapyPlutoSDR/wiki SoapyPlutoSDR]

*<code>SATNOGS_SOAPY_RX_DEVICE</code>=<code>"driver=plutosdr"</code>
*<code>SATNOGS_RX_SAMP_RATE</code>=<code>"2e6"</code>
*<code>SATNOGS_ANTENNA</code>=<code>"A_BALANCED"</code>
*<code>SATNOGS_RF_GAIN</code>=<code>50</code>

==HackRF support==
Vendor: [https://greatscottgadgets.com/hackrf/ Great Scott Gadgets]

required SoapySDR module: [https://github.com/pothosware/SoapyHackRF SoapyHackRF]

*<code>SATNOGS_SOAPY_RX_DEVICE</code>=<code>"driver=hackrf"</code>
*<code>SATNOGS_ANTENNA</code>=<code>"TX/RX"</code>
*<code>SATNOGS_RX_SAMP_RATE="8e6"</code>
**HackRF supports 8 to 20MS/s. Higher than 8MS/s has not been tested with SatNOGS on a RaspberryPi
**HackRF can run lower than 8MS/s, but it is not recommended as the ADC's filter is not designed for samplerates lower than 8MS/s

There are two possible gain modes:

"Overal", specifying just one global gain:

*<code>SATNOGS_GAIN_MODE</code>=<code>"Overall"</code>
*<code>SATNOGS_RF_GAIN</code>=<code>"64"</code> (Supported gain range: 0-116dB)

"Settings Field", specifying the individual gains.

*<code>SATNOGS_GAIN_MODE</code>=<code>"Settings Field"</code>
*<code>SATNOGS_OTHER_SETTINGS</code>=<code>"AMP=14,LNA=40,VGA=48"</code>
**AMP: supports 0 (amp disabled) and 14 (amp enabled)
**LNA: supports 0-40dBin 8dB steps
**VGA: supports 0-62dB in 2dB steps

To activate bias-T power on the antenna port:

*<code>SATNOGS_DEV_ARGS</code>=<code>bias_tx=true</code>

Example stations:

*[https://network.satnogs.org/stations/1868/ 1868 - HB9FXX S-Band]

==Remote==
Using the SoapySDRServer running on the same machine or over the network.

Required SoapySDRServer module: [https://github.com/pothosware/SoapyRemote/wiki SoapyRemote].
Optional SoapySDRUtil to probe for SDR and settings.
Make sure to match the antenna and gain setting from the actual device connected to the remote. Also possible to select remote drivers and other parameters; <code>driver=remote,remote:driver=rtlsdr</code>

*<code>SATNOGS_SOAPY_RX_DEVICE</code>=<code>"driver=remote"</code>
*<code>SATNOGS_RX_SAMP_RATE</code>=<code>"2e6"</code>
*<code>SATNOGS_ANTENNA</code>=<code>"RX"</code>
*<code>SATNOGS_RF_GAIN</code>=<code>20.7</code>

Not stable.

==References==

*[https://www.rtl-sdr.com/rtlsdr4everyone-review-of-5-rtl-sdr-dongles/ Review of 5 RTL-SDR Dongles]
*[https://hackaday.com/2017/09/05/19-rtl-sdr-dongles-reviewed/ 19 RTL-SDR Dongles Reviewed]
*[https://www.rtl-sdr.com/review-airspy-vs-sdrplay-rsp-vs-hackrf/ Review: Airspy VS. SDRplay RSP VS. HackRF]

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

__NOEDITSECTION__

SatNOGS Setup Legacy

2022-04-02T14:39:54Z

Kerel+satnogs: /* Advanced Setup */ List supported modules in SATNOGS_PPM_ERROR

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

{{Message| In case of getting a similar error to this:
<code>W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://download.opensuse.org/repositories/home:/librespace:/satnogs/Raspbian_10 ./ InRelease: The following signatures were invalid: EXPKEYSIG 8BD3901736A40B6C home:librespace OBS Project <home:librespace@build.opensuse.org>
</code>
Check at https://wiki.satnogs.org/Troubleshooting#Invalid_Signature_for_download.opensuse.org on how to solve it}}In case of getting a similar error to "Newer kernel available" annoying message after running sudo apt update:

Package configuration

┌──────────┤ Pending kernel upgrade ├─────────────────────┐

│ │

│ Newer kernel available │

│ │

│ The currently running kernel version is 4.19.97-v7l+ which is not the │

│ expected kernel version 4.19.93-v8+. │

│ │

│ Restarting the system to load the new kernel will not be handled │

│ automatically, so you should consider rebooting. │

│ │

│ <Ok> │

│ │

└─────────────────────────────────────────────────|

Do a "sudo apt purge need restart" after doing a reboot after doing a "sudo apt update"{{Message| In case of getting a similar error to this:
<code>
E: Repository 'http://archive.raspberrypi.org/debian buster InRelease' changed its 'Suite' value from 'testing' to 'oldstable'

N: This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details.

E: Repository 'http://raspbian.raspberrypi.org/raspbian buster InRelease' changed its 'Suite' value from 'stable' to 'oldstable'

N: This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details.
</code>
Run <code>sudo apt-get update --allow-releaseinfo-change</code> instead of just <code>sudo apt-get update</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 (value will be rounded to integer).
Available with the following modules:

* SoapyRTLSDR
* SoapySDRPlay

Not available with the following modules:

* SoapyUHD
* SoapyPluto
|-
|<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>
|-
|
|-
|<code>SATNOGS_ARTIFACTS_ENABLED</code>
|Enable generation and uploading of HDF5 artifacts files to SatNOGS DB. (added in satnogs-client 1.7)
|-
|<code>SATNOGS_ARTIFACTS_API_TOKEN</code>
|SatNOGS DB API token associated with an account in SatNOGS DB. This token is secret. It is used to upload artifacts to SatNOGS DB. It can be found in SatNOGS DB user page. (added in satnogs-client 1.7)
|}

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

SatNOGS Setup Legacy

2022-04-02T11:50:05Z

Kerel+satnogs:

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

{{Message| In case of getting a similar error to this:
<code>W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://download.opensuse.org/repositories/home:/librespace:/satnogs/Raspbian_10 ./ InRelease: The following signatures were invalid: EXPKEYSIG 8BD3901736A40B6C home:librespace OBS Project <home:librespace@build.opensuse.org>
</code>
Check at https://wiki.satnogs.org/Troubleshooting#Invalid_Signature_for_download.opensuse.org on how to solve it}}In case of getting a similar error to "Newer kernel available" annoying message after running sudo apt update:

Package configuration

┌──────────┤ Pending kernel upgrade ├─────────────────────┐

│ │

│ Newer kernel available │

│ │

│ The currently running kernel version is 4.19.97-v7l+ which is not the │

│ expected kernel version 4.19.93-v8+. │

│ │

│ Restarting the system to load the new kernel will not be handled │

│ automatically, so you should consider rebooting. │

│ │

│ <Ok> │

│ │

└─────────────────────────────────────────────────|

Do a "sudo apt purge need restart" after doing a reboot after doing a "sudo apt update"{{Message| In case of getting a similar error to this:
<code>
E: Repository 'http://archive.raspberrypi.org/debian buster InRelease' changed its 'Suite' value from 'testing' to 'oldstable'

N: This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details.

E: Repository 'http://raspbian.raspberrypi.org/raspbian buster InRelease' changed its 'Suite' value from 'stable' to 'oldstable'

N: This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details.
</code>
Run <code>sudo apt-get update --allow-releaseinfo-change</code> instead of just <code>sudo apt-get update</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 (value will be rounded to integer).
|-
|<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>
|-
|
|-
|<code>SATNOGS_ARTIFACTS_ENABLED</code>
|Enable generation and uploading of HDF5 artifacts files to SatNOGS DB. (added in satnogs-client 1.7)
|-
|<code>SATNOGS_ARTIFACTS_API_TOKEN</code>
|SatNOGS DB API token associated with an account in SatNOGS DB. This token is secret. It is used to upload artifacts to SatNOGS DB. It can be found in SatNOGS DB user page. (added in satnogs-client 1.7)
|}

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

Software Defined Radio

2022-02-06T17:55:22Z

Kerel+satnogs: airspy: Add comment on linearity and sensitivity

==Introduction==

Built upon [https://gnuradio.org/ GNU Radio] and [https://github.com/pothosware/SoapySDR/wiki SoapySDR] by using the [https://gitlab.com/librespacefoundation/gr-soapy gr-soapy] module SatNOGS supports a large variety of Software-Defined Radios (SDRs). The gr-soapy module was developed in the [https://sdrmaker.space/ SDR Makerspace] and is maintained by Libre Space Foundation to bring the vendor-neutral SDR support by SoapySDR to the flexible gnuradio ecosystem.

The most cost-effective solution is to use an RTL-SDR with a Raspberry Pi. More advanced SDRs are also used, but they require more processing power and thus might require a more powerful computing platform than the Raspberry Pi.

==Supported Devices==

SoapySDR supports SDR devices through runtime-loadable modules [https://github.com/pothosware/SoapySDR/wiki#plugin-architecture]. You can find all available modules in the [https://github.com/pothosware/SoapySDR/wiki#modules SoapySDR wiki] (see right column). Most SDR modules are installed by default when setting up a SatNOGS station.

The following SDRs are supported by SatNOGS. SatNOGS uses the RTL-SDR as the recommended beginner signal receiver and tuner.
The more advanced SDRs may require more processing power than a Raspberry Pi 3b or 4 can offer.

*[[Software Defined Radio#RTL-SDR Support|RTL-SDR]]
**[https://www.nooelec.com/store/sdr/sdr-receivers.html NooElec NESDR SMArt]
**[https://www.rtl-sdr.com/buy-rtl-sdr-dvb-t-dongles/ RTL-SDR Blog R820T2 RTL2832U]
**Full band UV HF RTL-SDR USB Tuner Receiver

*[[Software Defined Radio#USRP support|USRP devices]]
**[https://www.ettus.com/product/category/USRP-Bus-Series USRP B200]

*[[Software Defined Radio#Airspy support|Airspy]]
*[[Software Defined Radio#LimeSDR support|LimeSuite devices]]
**[https://limemicro.com/products/boards/limesdr-mini/ LimeSDR mini]
*[[Software Defined Radio#PlutoSDR support|PlutoSDR]]
**[https://www.analog.com/en/design-center/evaluation-hardware-and-software/evaluation-boards-kits/adalm-pluto.html#eb-overview ADALM-PLUTO] (untested)

{{Message|There are probably a lot more devices supported since the transition from gr-osmosdr to gr-soapy. Please update this list when you were able to successfully run a SatNOGS station with a new radio family or model. You can also link your station as an example to give others the ability to compare performance.}}

==Supported Devices with closed-source drivers==
Unfortunately some vendors require closed-source drivers in their SoapySDR modules and thus those modules or dependencies can't be redistributed by others. Thus they must be manually installed by the user. The following devices require closed-source drivers:

*[[Software Defined Radio#SDRPlay support|SDRPlay]]

==Unsupported Devices==
{{Warning|This section might be outdated due to the transition to gr-soapy. Please update when possible.}}
 

*[https://greatscottgadgets.com/hackrf/ HackRF One] (not compatible with the SatNOGS client on Raspberry Pi, ''Update: works fine now on a Pi4, only tested with the 8GB version of the Pi4. Will probably work with a 2/4GB version too. Not tested on a Pi3, might not be powerful enough to handle 8MS/s'')

==RTL-SDR Support==
The RTL-SDR is based on two chips -- the versatile [http://www.realtek.com.tw/products/productsView.aspx?Langid=1&PFid=35&Level=4&Conn=3&ProdID=257 RTL2832U chip] and the [https://rtl-sdr.com/wp-content/uploads/2013/04/R820T_datasheet-Non_R-20111130_unlocked.pdf R820T tuner]. The RTL-SDR is currently the cheapest, most common, and most performing solution available in terms of general sensitivity having a frequency range of 24 – 1766 MHz. A metal enclosure with SMA connector is preferred, along with a stable TCXO (low ppm). HF coverage is optional.

 

===Using RTL-SDR.com V3 Dongle's Bias-T Power Supply===
The RTL-SDR.com V3 dongle has a built in software activated Bias-T voltage supply intended to be used for applications such as powering inline LNAs (Low Noise Amplifiers). There are several ways to turn on the voltage, but through initial testing (as of this writing, 17 Aug 2019) it seems that the following procedure works best.

The below relates to Raspberry Pi installs only. No testing has been performed on other systems as of yet.

{{Warning|Turning on the Bias-T with no LNA installed and a "shorted" style antenna (such as loops, egg-beaters, etc.) can damage the RTL-SDR.com V3 dongle. Never activate the bias-t with no LNA installed between the antenna and the SDR dongle.}}

'''Requirements:'''

#Raspberry Pi running Raspbian Buster or newer (latest release of SatNogs image, [https://gitlab.com/librespacefoundation/satnogs/satnogs-pi-gen/-/tags 2019091100], is demonstrated to work)
#[https://www.rtl-sdr.com/buy-rtl-sdr-dvb-t-dongles/ RTL-SDR.com V3 SDR dongle]
#[https://www.rtl-sdr.com/rtl-sdr-blog-v-3-dongles-user-guide/ RTL-SDR.com Bias-T Software Switch] for linux systems
#LNA capable of being powered via feedline coax (note that some LNAs need modifications to be powered by the coax, and some cannot be powered by the coax at all. Check the specifications for your LNA prior to attempting to turn on the Bias-T power supply)

 

====Instructions for installing RTL-SDR.com Bias-T Software Switch====

#Log into your SatNogs station either directly or via SSH
#If your station does not have cmake installed (SatNogs Image 2019091100 does not), install cmake with <code>sudo apt install cmake</code>
#Clone the source for the Bias-T software switch with <code>git clone <nowiki>https://github.com/rtlsdrblog/rtl_biast</nowiki></code>
#<code>cd rtl_biast</code>
#<code>mkdir build</code>
#<code>cd build</code>
#<code>cmake ..</code> (if you get a <code>LibUSB 1.0 required to compile rtl-sdr</code> error here, then do <code>sudo apt install libusb-1.0-0-dev</code> prior to attempting <code>cmake ..</code> again)
#<code>make</code>

The software switch should now be installed in the "src" directory. If you <code>cd src</code>, you can turn on the bias-t with the command <code>./rtl_biast -b 1</code> and turn it off with <code>./rtl_biast -b 0</code>. Note that the developers of this switch have warned against attempting to <code>sudo make install</code> so that this command can be executed from ouside the src directory. Testing has shown this warning to be accurate, so don't plan on running these commands from anywhere but the src directory, or else be sure to use the full path.

Switching the Bias-T on should yield between 4.5V and 5.0V across the center conductor and shield of the coax. The voltage should rise almost instantly. When switched off, the voltage seems to decrease gradually, over 5 to 10 seconds.

====Instructions to activate the bias-t for SatNogs Observations automatically:====

#Log into your SatNogs station either directly or via SSH
#<code>sudo satnogs-setup</code>
#select <code>Advanced</code>
#for <code>Radio</code> -><code>SATNOGS_RF_GAIN</code>, enter a low gain value supported by your RTL-SDR.com V3 dongle (entering <code>rtl_test</code> at the command line prior to starting <code>satnogs-setup</code> will give you all allowable values of RF gain) and select <code>Ok</code>
#for <code>Scripts</code> -><code>SATNOGS_PRE_OBSERVATION_SCRIPT,</code> enter <code>/home/pi/rtl_biast/build/src/rtl_biast -b 1</code> and select <code>Ok</code>
#for <code>Scripts</code> -><code>SATNOGS_POST_OBSERVATION_SCRIPT,</code> enter <code>/home/pi/rtl_biast/build/src/rtl_biast -b 0</code> and select <code>Ok</code>
#Select <code>Back</code>
#Select <code>Apply</code> (allow system to update and hit enter when prompted)
#Select <code>Back</code>

Your station is now set up to turn the Bias-T on for each scheduled observation (using the <code>SATNOGS_PRE_OBSERVATION_SCRIPT</code> string) and then turn it off at the conclusion of each observation (using the <code>SATNOGS_POST_OBSERVATION_SCRIPT</code>).

You should now schedule several observations to fine tune the <code>SATNOGS_RF_GAIN</code> value to get the best S/N performance for your station. Some have reported needing zero RF gain, others have reported low RF gain required (between 5 and 10 db), and others have said they see little benefit even with very high gain. Each station will be different.

====E4000 Tuner Gain Settings====
The RTLSDR Driver exposes six (!) IF gain settings (IF1 through IF6) for the E4000 tuner, along with a TUNER gain setting, which is actually a combined LNA and Mixer gain control. Details on the gain stages are available in page 28 of the E4000 data-sheet here: https://www.nooelec.com/files/e4000datasheet.pdf

When you follow the '[[Omnidirectional Station How To#Setting the gain|Setting the Gain]]' guide, all gain sliders (IF1 through IF6, and TUNER) should be presented in SoapySDR, allowing the user to adjust them to optimise for best performance. Once the correct values have been determined, you will need to define these specifically in satnogs-setup as follows:

*<code>SATNOGS_GAIN_MODE</code>=<code>"Settings Field"</code>
*<code>SATNOGS_OTHER_SETTINGS</code>=<code>"IF1=6,IF2=3,IF2=2,IF3=0,IF4=0,IF5=2,IF6=3,TUNER=30"</code>

(Replacing the values in the line above with the ones you determined)

====R820T Gain Settings====
Unfortunately librtlsdr only exposes a single gain control for the R820T/T2 tuners, even though multiple gain adjustments are available. Use the standard SATNOGS_RF_GAIN option, with a gain between 0 and 42 (dB), as optimised for your station via the '[[Omnidirectional Station How To#Setting the gain|Setting the Gain]]' guide.

==Airspy support==
Vendor: [https://airspy.com/ Airspy]

required SoapySDR module: [https://github.com/pothosware/SoapyAirspy/wiki SoapyAirspy]

'''Note than none of the settings below should be entered with the " " around the value. This is only for better readability in the Wiki !'''

===Gain settings===
There are two possible gain modes:

*<code>SATNOGS_GAIN_MODE</code>=<code>"Overall"</code>: (default) Use a single gain value. Set the overall gain with <code>SATNOGS_RF_GAIN</code>,e.g. <code>SATNOGS_RF_GAIN</code>=<code>43</code>.
*<code>SATNOGS_GAIN_MODE</code>=<code>"Settings Field"</code>: Use granular gain values. Set the different gain stages separately:
**without pre-amp: <code>SATNOGS_OTHER_SETTINGS</code>=<code>"LNA=12,MIX=8,VGA=11"</code>
**with pre-amp: <code>SATNOGS_OTHER_SETTINGS</code>=<code>"LNA=9,MIX=6,VGA=11"</code> (used in [https://network.satnogs.org/stations/49/ 49 - OZ7SAT])

For reference see also the Airspy driver library linearity gain settings in [https://github.com/airspy/airspyone_host/blob/bceca18f9e3a5f89cff78c4d949c71771d92dfd3/libairspy/src/airspy.c#L117-L122 libairspy/src/airspy.c#L117-L122].

The airspy driver offers "Linearity" and "Sensitivity" gain settings, using a look-up table to configure all three gain stages from a single value (optimized for linearity and gain respectively). Those modes are unfortunately not available through the SoapyAirspy module (see [https://github.com/pothosware/SoapyAirspy/pull/14 SoapyAirspy#14]).

The "Overall" gain mode is a soapy-specific driver-independent mode to configure all gain stages based on the single gain value from <code>SATNOGS_RF_GAIN</code>. It tries to evenly distribute the gain, potentially resulting in non-optimal configuration. Thus for achieving optimal results the "Settings Field" mode is recommended, where all three gain stages can be configured separately.

===Sample rates===

*Airspy R2: <code>SATNOGS_RX_SAMPLE_RATE</code>=<code>2.5e6 or 10e6</code>
*Airspy Mini: <code>SATNOGS_RX_SAMPLE_RATE</code>=<code>3e6 or 6e6</code>
*Airspy HF+: <code>SATNOGS_RX_SAMPLE_RATE</code>=<code>768e3</code>

source: [https://twitter.com/DutchSpace/status/1241305651168661504]

If you want to activate the integrated bias tee, set <code>SATNOGS_DEV_ARGS</code>=<code>"biastee=true"</code>.
Bit packing ("Enable packing 4 12-bit samples into 3 16-bit words for 25% less USB trafic.") could be enabled with <code>SATNOGS_DEV_ARGS</code>=<code>"bitpacking=true"</code> (untested). Device arguments can be concatenated with comma as delimiter.

==SDRPlay support==
Vendor: [http://www.sdrplay.com/ SDRPlay]

required SoapySDR module: [https://github.com/pothosware/SoapySDRPlay SoapySDRPlay]

The following settings [https://network.satnogs.org/observations/?norad=&observer=&station=1354&results=d1&start=2020-02-20+00%3A00&end=2020-02-24+23%3A59 worked well] for an [https://www.sdrplay.com/rspduo/ SDRplay RSPduo] when using cross-yagis and good [https://www.ssb.de/en/amplifiers/preamplifier/vox/100w SSB low-noise amplifiers]:

*<code>SATNOGS_SOAPY_RX_DEVICE="driver=sdrplay"</code>
*<code>SATNOGS_RX_SAMP_RATE=2e6</code>
*<code>SATNOGS_RX_BANDWIDTH=600e3</code>
*<code>SATNOGS_RF_GAIN=34</code>
*<code>SATNOGS_ANTENNA="Tuner 1 50 ohm"</code>

Note that 14-bits ADC resolution is only available when using sample rates below 6.048 MSPS, above which the resolution is reduced gradually to 12, 10, and 8 bits.

==USRP support==
Vendor: [https://ettus.com Ettus Research]

required SoapySDR module: [https://github.com/pothosware/SoapyUHD/wiki SoapyUHD]

Recent USRPs that use the Analog Devices [https://www.analog.com/en/products/ad9361.html AD9361 RFIC] can use almost arbitrary sample rates and analog bandwidth settings. It can be an advantage to set the sample rate as high as the host computer can handle and the analog bandwidth to as narrow as meaningful. The following settings [https://network.satnogs.org/observations/?norad=&observer=&station=1353&results=d1&start=2020-02-20+00%3A00&end=2020-02-24+23%3A59 worked well] for a [https://www.ettus.com/all-products/ub210-kit/ USRP B210] when using cross-yagis and good [https://www.ssb.de/en/amplifiers/preamplifier/vox/100w SSB low-noise amplifiers]:

*<code>SATNOGS_SOAPY_RX_DEVICE="driver=uhd"</code>
*<code>SATNOGS_RX_SAMP_RATE=2e6</code>
*<code>SATNOGS_RX_BANDWIDTH=600e3</code>
*<code>SATNOGS_RF_GAIN=50</code>
*<code>SATNOGS_ANTENNA="RX2"</code>
**on the B200 your Antenna options are <code>TX/RX</code> and <code>RX2</code>, be sure you select the right option for your configuration!

==LimeSDR support==
Vendor: [https://limemicro.com Lime microsystems]

required SoapySDR module: [https://github.com/myriadrf/LimeSuite/tree/master/SoapyLMS7 SoapyLMS7 wrapper]

*<code>SATNOGS_SOAPY_RX_DEVICE</code>=<code>"driver=lime"</code>
*<code>SATNOGS_RX_SAMP_RATE</code>=<code>"2.048e6"</code>
*<code>SATNOGS_ANTENNA</code>=<code>"LNAW"</code>
*<code>SATNOGS_GAIN_MODE</code>=<code>"Settings Field"</code>
*<code>SATNOGS_RF_GAIN</code>=<code>20</code>
*<code>SATNOGS_OTHER_SETTINGS</code>=<code>"TIA=12,PGA=0,LNA=12"</code>

(untested, copied from station 1378)

Example stations:

*[https://network.satnogs.org/stations/1378/ 1378 - Wolbach library]

==PlutoSDR support==
Vendor: [https://www.analog.com Analog Devices]

required SoapySDR module: [https://github.com/pothosware/SoapyPlutoSDR/wiki SoapyPlutoSDR]

*<code>SATNOGS_SOAPY_RX_DEVICE</code>=<code>"driver=plutosdr"</code>
*<code>SATNOGS_RX_SAMP_RATE</code>=<code>"2e6"</code>
*<code>SATNOGS_ANTENNA</code>=<code>"A_BALANCED"</code>
*<code>SATNOGS_RF_GAIN</code>=<code>50</code>

==HackRF support==
Vendor: [https://greatscottgadgets.com/hackrf/ Great Scott Gadgets]

required SoapySDR module: [https://github.com/pothosware/SoapyHackRF SoapyHackRF]

*<code>SATNOGS_SOAPY_RX_DEVICE</code>=<code>"driver=hackrf"</code>
*<code>SATNOGS_ANTENNA</code>=<code>"TX/RX"</code>
*<code>SATNOGS_RX_SAMP_RATE="8e6"</code>
**HackRF supports 8 to 20MS/s. Higher than 8MS/s has not been tested with SatNOGS on a RaspberryPi
**HackRF can run lower than 8MS/s, but it is not recommended as the ADC's filter is not designed for samplerates lower than 8MS/s

There are two possible gain modes:

"Overal", specifying just one global gain:

*<code>SATNOGS_GAIN_MODE</code>=<code>"Overall"</code>
*<code>SATNOGS_RF_GAIN</code>=<code>"64"</code> (Supported gain range: 0-116dB)

"Settings Field", specifying the individual gains.

*<code>SATNOGS_GAIN_MODE</code>=<code>"Settings Field"</code>
*<code>SATNOGS_OTHER_SETTINGS</code>=<code>"AMP=14,LNA=40,VGA=48"</code>
**AMP: supports 0 (amp disabled) and 14 (amp enabled)
**LNA: supports 0-40dBin 8dB steps
**VGA: supports 0-62dB in 2dB steps

To activate bias-T power on the antenna port:

*<code>SATNOGS_DEV_ARGS</code>=<code>bias_tx=true</code>

Example stations:

*[https://network.satnogs.org/stations/1868/ 1868 - HB9FXX S-Band]

==Remote==
Using the SoapySDRServer running on the same machine or over the network.

Required SoapySDRServer module: [https://github.com/pothosware/SoapyRemote/wiki SoapyRemote].
Optional SoapySDRUtil to probe for SDR and settings.
Make sure to match the antenna and gain setting from the actual device connected to the remote. Also possible to select remote drivers and other parameters; <code>driver=remote,remote:driver=rtlsdr</code>

*<code>SATNOGS_SOAPY_RX_DEVICE</code>=<code>"driver=remote"</code>
*<code>SATNOGS_RX_SAMP_RATE</code>=<code>"2e6"</code>
*<code>SATNOGS_ANTENNA</code>=<code>"RX"</code>
*<code>SATNOGS_RF_GAIN</code>=<code>20.7</code>

Not stable.

==References==

*[https://www.rtl-sdr.com/rtlsdr4everyone-review-of-5-rtl-sdr-dongles/ Review of 5 RTL-SDR Dongles]
*[https://hackaday.com/2017/09/05/19-rtl-sdr-dongles-reviewed/ 19 RTL-SDR Dongles Reviewed]
*[https://www.rtl-sdr.com/review-airspy-vs-sdrplay-rsp-vs-hackrf/ Review: Airspy VS. SDRplay RSP VS. HackRF]

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

__NOEDITSECTION__

SatNOGS Setup Legacy

2022-01-27T09:39:32Z

Kerel+satnogs: Add the variables required for artifacts upload

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

{{Message| In case of getting a similar error to this:
<code>W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://download.opensuse.org/repositories/home:/librespace:/satnogs/Raspbian_10 ./ InRelease: The following signatures were invalid: EXPKEYSIG 8BD3901736A40B6C home:librespace OBS Project <home:librespace@build.opensuse.org>
</code>
Check at https://wiki.satnogs.org/Troubleshooting#Invalid_Signature_for_download.opensuse.org on how to solve it}}
{{Message| In case of getting a similar error to this:
<code>
E: Repository 'http://archive.raspberrypi.org/debian buster InRelease' changed its 'Suite' value from 'testing' to 'oldstable'

N: This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details.

E: Repository 'http://raspbian.raspberrypi.org/raspbian buster InRelease' changed its 'Suite' value from 'stable' to 'oldstable'

N: This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details.
</code>
Run <code>sudo apt-get update --allow-releaseinfo-change</code> instead of just <code>sudo apt-get update</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>
|-
|
|-
|<code>SATNOGS_ARTIFACTS_ENABLED</code>
|Enable generation and uploading of HDF5 artifacts files to SatNOGS DB. (added in satnogs-client 1.7)
|-
|<code>SATNOGS_ARTIFACTS_API_TOKEN</code>
|SatNOGS DB API token associated with an account in SatNOGS DB. This token is secret. It is used to upload artifacts to SatNOGS DB. It can be found in SatNOGS DB user page. (added in satnogs-client 1.7)
|}

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

Linux Desktop

2021-11-23T11:56:50Z

Kerel+satnogs: /* Packages needed */

{{Warning|Manual installation of the SatNOGS Station Software is a tedious & brittle process, not recommended for SatNOGS Stations. Please consider running your SatNOGS Station on Debian or Raspbian and follow the [[SatNOGS Client Ansible]] guide for installing the SatNOGS Client }}

== Introduction ==

Here you will find instructions on installing SatNOGS manually on a generic Linux distribution. It is highly recommended to run SatNOGS stations on a Debian or Raspbian host system so that [[SatNOGS_Client_Ansible]] can be used for setup. All other Linux distributions require the manual installation of all needed programs.

== Packages needed ==

Please check the README of each of those projects for their dependencies and installation procedure.

* [https://gitlab.com/librespacefoundation/satnogs/satnogs-client satnogs-client]
** libhamlib
* [https://gitlab.com/librespacefoundation/satnogs/satnogs-flowgraphs satnogs-flowgraphs]
** [https://gitlab.com/librespacefoundation/satnogs/gr-satnogs gr-satnogs]
** gnuradio
** [https://gitlab.com/librespacefoundation/gr-soapy gr-soapy]
** soapysdr
* [https://gitlab.com/librespacefoundation/satnogs/satnogs-config satnogs-config]

=Installation on Ubuntu 16.04 in 2018=
{{Warning|The rest of this page provides deprecated and unsupported information - 2018-06-22}}

== Prep Work ==

Install dependencies

<pre>
sudo apt-get update
sudo apt-get install -y python-pip python-dev supervisor cmake libusb-1.0-0-dev libhamlib-utils vorbis-tools software-properties-common unzip
</pre>

Install gnuradio libs from myriadrf since we need a newer version than Ubuntu provides for 16.04

<pre>
sudo apt-get purge --auto-remove libgnuradio*
sudo add-apt-repository -y ppa:myriadrf/drivers
sudo add-apt-repository -y ppa:myriadrf/gnuradio
sudo apt-get update
sudo apt-get install -y gnuradio-dev libboost-dev libnova-dev libpng-dev
</pre>

== Install gr-satnogs ==

Grab the latest gr-satnogs debian package, unpack it, and install the appropriate deb file:
<pre>
wget -O archive.zip https://gitlab.com/librespacefoundation/satnogs/gr-satnogs-package/-/jobs/35403119/artifacts/download (broken link here)
unzip archive.zip -d gr-satnogs
</pre>

== Install satnogs client ==
<pre>
pip install satnogsclient
</pre>

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

Linux Desktop

2021-11-23T09:30:38Z

Kerel+satnogs: Split outdated content in new section; Add currently needed packages

{{Warning|Manual installation of the SatNOGS Station Software is a tedious & brittle process, not recommended for SatNOGS Stations. Please consider running your SatNOGS Station on Debian or Raspbian and follow the [[SatNOGS Client Ansible]] guide for installing the SatNOGS Client }}

== Introduction ==

Here you will find instructions on installing SatNOGS manually on a generic Linux distribution. It is highly recommended to run SatNOGS stations on a Debian or Raspbian host system so that [[SatNOGS_Client_Ansible]] can be used for setup. All other Linux distributions require the manual installation of all needed programs.

== Packages needed ==

Please check the README of each of those projects for their dependencies and installation procedure.

* [https://gitlab.com/librespacefoundation/satnogs/satnogs-client satnogs-client]
** libhamlib
* [https://gitlab.com/librespacefoundation/satnogs/satnogs-flowgraphs satnogs-flowgraphs]
** [https://gitlab.com/librespacefoundation/satnogs/gr-satnogs gr-satnogs]
** gnuradio
** [https://gitlab.com/librespacefoundation/satnogs/gr-soapy gr-soapy]
** soapysdr
* [https://gitlab.com/librespacefoundation/satnogs/satnogs-config satnogs-config]

=Installation on Ubuntu 16.04 in 2018=
{{Warning|The rest of this page provides deprecated and unsupported information - 2018-06-22}}

== Prep Work ==

Install dependencies

<pre>
sudo apt-get update
sudo apt-get install -y python-pip python-dev supervisor cmake libusb-1.0-0-dev libhamlib-utils vorbis-tools software-properties-common unzip
</pre>

Install gnuradio libs from myriadrf since we need a newer version than Ubuntu provides for 16.04

<pre>
sudo apt-get purge --auto-remove libgnuradio*
sudo add-apt-repository -y ppa:myriadrf/drivers
sudo add-apt-repository -y ppa:myriadrf/gnuradio
sudo apt-get update
sudo apt-get install -y gnuradio-dev libboost-dev libnova-dev libpng-dev
</pre>

== Install gr-satnogs ==

Grab the latest gr-satnogs debian package, unpack it, and install the appropriate deb file:
<pre>
wget -O archive.zip https://gitlab.com/librespacefoundation/satnogs/gr-satnogs-package/-/jobs/35403119/artifacts/download (broken link here)
unzip archive.zip -d gr-satnogs
</pre>

== Install satnogs client ==
<pre>
pip install satnogsclient
</pre>

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

SatNOGS Ansible

2021-11-23T08:24:40Z

Kerel+satnogs:

==Introduction==

{{Warning|Follow these instructions only if you are provisioning SatNOGS to Debian from another host or are installing on the same host. }}

'''SatNOGS Client Ansible''' makes the actual provisioning of the '''SatNOGS Client''' system. It is called, under the hood, when applying the configuration using [[SatNOGS Client Setup|SatNOGS Client Setup utility]]. It currently supports Raspbian and Debian (stretch and buster).

==Raspbian==

For Raspberry Pi, which is the reference platform for SatNOGS, a custom Raspbian image with '''SatNOGS Client Ansible''' pre-installed is available. Installation instructions are given in the [[Raspberry_Pi| Raspberry Pi Setup Guide]].

==Debian==

These sections contain generic instructions for installing SatNOGS Client on a Debian system.

==Other distributions==

Other distributions are not supported by '''SatNOGS Client Ansible''', as the pre-built packages won't be compatible. Thus, while derived from Debian, '''SatNOGS Client Ansible''' is known to break for Ubuntu and Linux Mint. If you are an experienced user, a manual installation of all components could be possible.

==Installation Guide==
===Prerequisites===

*A target Debian system. To install Debian please follow the [https://www.debian.org/releases/stretch/installmanual Debian Installation Guide] and chose the net installer if you want to run a headless server. The target system can be the host itself.
*A user (referenced later as ''youruser'') which is member of 'sudo' group exists on the target system.
*An SSH server running on the target system.
*A host system with Git and latest version of Ansible installed. To install Ansible on Debian, follow the [https://docs.ansible.com/ansible/latest/installation_guide/intro_installation.html#installing-ansible-on-debian Ansible Installation Guide].

===Installation===

On the host system run the following commands:
$ git clone <nowiki>https://gitlab.com/librespacefoundation/satnogs/satnogs-client-ansible.git</nowiki> # Clone SatNOGS Client Ansible repository
$ cd satnogs-client-ansible # Change to cloned repository directory
$ git checkout stable # Optionally, check out stable (Debian Buster 10) branch
$ cp -r production.dist production # Copy dist configuration
$ vi production/inventory/hosts # Update file with your own target host e.g. 127.0.0.1, user and SSH password
$ ssh youruser@yourtargetsystem true # Test SSH connection to target system
$ ansible-playbook -i production/inventory/hosts -K site.yml # Run Ansible playbook
$ ssh -t youruser@yourtargetsystem sudo satnogs-setup # Setup SatNOGS client (see below)

 

===Next Steps===

Follow [[SatNOGS_Client_Setup|SatNOGS Client Setup]] to configure your system and SatNOGS station.

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

SatNOGS Ansible

2021-11-23T08:18:24Z

Kerel+satnogs: Add link to Raspberry Pi Setup Guide

==Introduction==

'''SatNOGS Client Ansible''' makes the actual provisioning of the '''SatNOGS Client''' system. It is called, under the hood, when applying the configuration using [[SatNOGS Client Setup|SatNOGS Client Setup utility]]. It currently supports Raspbian and Debian (stretch and buster).

==Raspbian==

For Raspberry Pi, which is the reference platform for SatNOGS, a custom Raspbian image with '''SatNOGS Client Ansible''' pre-installed is available. Installation instructions are given in the [[Raspberry_Pi| Raspberry Pi Setup Guide]].

==Debian==

{{Warning|Follow these instructions only if you are provisioning SatNOGS to Debian from another host or are installing on the same host. If you are using [[Raspberry_Pi|SatNOGS Raspbian]] image, follow [[SatNOGS_Client_Setup|SatNOGS Client Setup]] to set up your system. }}These sections contain generic instructions for installing SatNOGS Client on a Debian system.

==Other distributions==

Other distributions are not supported by '''SatNOGS Client Ansible''', as the pre-built packages won't be compatible. While derived from Debian, this includes Ubuntu und Linux Mint.

===Prerequisites===

*A target Debian system. To install Debian please follow the [https://www.debian.org/releases/stretch/installmanual Debian Installation Guide] and chose the net installer if you want to run a headless server. The target system can be the host itself.
*A user (referenced later as ''youruser'') which is member of 'sudo' group exists on the target system.
*An SSH server running on the target system.
*A host system with Git and latest version of Ansible installed. To install Ansible on Debian, follow the [https://docs.ansible.com/ansible/latest/installation_guide/intro_installation.html#installing-ansible-on-debian Ansible Installation Guide].

===Installation===

On the host system run the following commands:
$ git clone <nowiki>https://gitlab.com/librespacefoundation/satnogs/satnogs-client-ansible.git</nowiki> # Clone SatNOGS Client Ansible repository
$ cd satnogs-client-ansible # Change to cloned repository directory
$ git checkout stable # Optionally, check out stable (Debian Buster 10) branch
$ cp -r production.dist production # Copy dist configuration
$ vi production/inventory/hosts # Update file with your own target host e.g. 127.0.0.1, user and SSH password
$ ssh youruser@yourtargetsystem true # Test SSH connection to target system
$ ansible-playbook -i production/inventory/hosts -K site.yml # Run Ansible playbook
$ ssh -t youruser@yourtargetsystem sudo satnogs-setup # Setup SatNOGS client (see below)

 

==See also==

*[[SatNOGS Client Setup]]

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

SatNOGS Ansible

2021-11-23T08:15:51Z

Kerel+satnogs: /* Other distributions */ Fix title level

==Introduction==

'''SatNOGS Client Ansible''' makes the actual provisioning of the '''SatNOGS Client''' system. It is called, under the hood, when applying the configuration using [[SatNOGS Client Setup|SatNOGS Client Setup utility]]. It currently supports Raspbian and Debian (stretch and buster).

==Raspbian==

For Raspberry Pi, which is the reference platform for SatNOGS, a [[Raspberry Pi|Raspbian image]] with '''SatNOGS Client Ansible''' pre-installed is available.

==Debian==

{{Warning|Follow these instructions only if you are provisioning SatNOGS to Debian from another host or are installing on the same host. If you are using [[Raspberry_Pi|SatNOGS Raspbian]] image, follow [[SatNOGS_Client_Setup|SatNOGS Client Setup]] to set up your system. }}These sections contain generic instructions for installing SatNOGS Client on a Debian system.

==Other distributions==

Other distributions are not supported by '''SatNOGS Client Ansible''', as the pre-built packages won't be compatible. While derived from Debian, this includes Ubuntu und Linux Mint.

===Prerequisites===

*A target Debian system. To install Debian please follow the [https://www.debian.org/releases/stretch/installmanual Debian Installation Guide] and chose the net installer if you want to run a headless server. The target system can be the host itself.
*A user (referenced later as ''youruser'') which is member of 'sudo' group exists on the target system.
*An SSH server running on the target system.
*A host system with Git and latest version of Ansible installed. To install Ansible on Debian, follow the [https://docs.ansible.com/ansible/latest/installation_guide/intro_installation.html#installing-ansible-on-debian Ansible Installation Guide].

===Installation===

On the host system run the following commands:
$ git clone <nowiki>https://gitlab.com/librespacefoundation/satnogs/satnogs-client-ansible.git</nowiki> # Clone SatNOGS Client Ansible repository
$ cd satnogs-client-ansible # Change to cloned repository directory
$ git checkout stable # Optionally, check out stable (Debian Buster 10) branch
$ cp -r production.dist production # Copy dist configuration
$ vi production/inventory/hosts # Update file with your own target host e.g. 127.0.0.1, user and SSH password
$ ssh youruser@yourtargetsystem true # Test SSH connection to target system
$ ansible-playbook -i production/inventory/hosts -K site.yml # Run Ansible playbook
$ ssh -t youruser@yourtargetsystem sudo satnogs-setup # Setup SatNOGS client (see below)

 

==See also==

*[[SatNOGS Client Setup]]

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

SatNOGS Ansible

2021-11-23T08:15:29Z

Kerel+satnogs: /* Other distributions= */ Fix syntax

==Introduction==

'''SatNOGS Client Ansible''' makes the actual provisioning of the '''SatNOGS Client''' system. It is called, under the hood, when applying the configuration using [[SatNOGS Client Setup|SatNOGS Client Setup utility]]. It currently supports Raspbian and Debian (stretch and buster).

==Raspbian==

For Raspberry Pi, which is the reference platform for SatNOGS, a [[Raspberry Pi|Raspbian image]] with '''SatNOGS Client Ansible''' pre-installed is available.

==Debian==

{{Warning|Follow these instructions only if you are provisioning SatNOGS to Debian from another host or are installing on the same host. If you are using [[Raspberry_Pi|SatNOGS Raspbian]] image, follow [[SatNOGS_Client_Setup|SatNOGS Client Setup]] to set up your system. }}These sections contain generic instructions for installing SatNOGS Client on a Debian system.

===Other distributions===

Other distributions are not supported by '''SatNOGS Client Ansible''', as the pre-built packages won't be compatible. While derived from Debian, this includes Ubuntu und Linux Mint.

===Prerequisites===

*A target Debian system. To install Debian please follow the [https://www.debian.org/releases/stretch/installmanual Debian Installation Guide] and chose the net installer if you want to run a headless server. The target system can be the host itself.
*A user (referenced later as ''youruser'') which is member of 'sudo' group exists on the target system.
*An SSH server running on the target system.
*A host system with Git and latest version of Ansible installed. To install Ansible on Debian, follow the [https://docs.ansible.com/ansible/latest/installation_guide/intro_installation.html#installing-ansible-on-debian Ansible Installation Guide].

===Installation===

On the host system run the following commands:
$ git clone <nowiki>https://gitlab.com/librespacefoundation/satnogs/satnogs-client-ansible.git</nowiki> # Clone SatNOGS Client Ansible repository
$ cd satnogs-client-ansible # Change to cloned repository directory
$ git checkout stable # Optionally, check out stable (Debian Buster 10) branch
$ cp -r production.dist production # Copy dist configuration
$ vi production/inventory/hosts # Update file with your own target host e.g. 127.0.0.1, user and SSH password
$ ssh youruser@yourtargetsystem true # Test SSH connection to target system
$ ansible-playbook -i production/inventory/hosts -K site.yml # Run Ansible playbook
$ ssh -t youruser@yourtargetsystem sudo satnogs-setup # Setup SatNOGS client (see below)

 

==See also==

*[[SatNOGS Client Setup]]

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

SatNOGS Ansible

2021-11-23T08:15:04Z

Kerel+satnogs: Add note on pre-built packages / supported distributions

==Introduction==

'''SatNOGS Client Ansible''' makes the actual provisioning of the '''SatNOGS Client''' system. It is called, under the hood, when applying the configuration using [[SatNOGS Client Setup|SatNOGS Client Setup utility]]. It currently supports Raspbian and Debian (stretch and buster).

==Raspbian==

For Raspberry Pi, which is the reference platform for SatNOGS, a [[Raspberry Pi|Raspbian image]] with '''SatNOGS Client Ansible''' pre-installed is available.

==Debian==

{{Warning|Follow these instructions only if you are provisioning SatNOGS to Debian from another host or are installing on the same host. If you are using [[Raspberry_Pi|SatNOGS Raspbian]] image, follow [[SatNOGS_Client_Setup|SatNOGS Client Setup]] to set up your system. }}These sections contain generic instructions for installing SatNOGS Client on a Debian system.

==Other distributions===

Other distributions are not supported by '''SatNOGS Client Ansible''', as the pre-built packages won't be compatible. While derived from Debian, this includes Ubuntu und Linux Mint.

===Prerequisites===

*A target Debian system. To install Debian please follow the [https://www.debian.org/releases/stretch/installmanual Debian Installation Guide] and chose the net installer if you want to run a headless server. The target system can be the host itself.
*A user (referenced later as ''youruser'') which is member of 'sudo' group exists on the target system.
*An SSH server running on the target system.
*A host system with Git and latest version of Ansible installed. To install Ansible on Debian, follow the [https://docs.ansible.com/ansible/latest/installation_guide/intro_installation.html#installing-ansible-on-debian Ansible Installation Guide].

===Installation===

On the host system run the following commands:
$ git clone <nowiki>https://gitlab.com/librespacefoundation/satnogs/satnogs-client-ansible.git</nowiki> # Clone SatNOGS Client Ansible repository
$ cd satnogs-client-ansible # Change to cloned repository directory
$ git checkout stable # Optionally, check out stable (Debian Buster 10) branch
$ cp -r production.dist production # Copy dist configuration
$ vi production/inventory/hosts # Update file with your own target host e.g. 127.0.0.1, user and SSH password
$ ssh youruser@yourtargetsystem true # Test SSH connection to target system
$ ansible-playbook -i production/inventory/hosts -K site.yml # Run Ansible playbook
$ ssh -t youruser@yourtargetsystem sudo satnogs-setup # Setup SatNOGS client (see below)

 

==See also==

*[[SatNOGS Client Setup]]

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

MediaWiki:Sidebar

2021-11-11T09:14:05Z

Kerel+satnogs:

* Build
** Build|[Station] Build a Ground Station
** Raspberry_Pi|[Station] Install a Raspberry Pi
** SatNOGS_Client_Setup|[Station] Configure/Update your Station
** Omnidirectional_Station_How_To|[Station] Omnidirectional Howto
** Radio|SDR Support
** Troubleshooting|Client Troubleshooting
* Operate
** Satellite_Operator_Guide|Add your Mission
** Operation|Managing Observations
** Decode_Telemetry_and_Packets|Decode Telemetry and Packets
** Telemetry_Dashboards|Telemetry Dashboards
** :Category:RF Modes|RF Modes
* Contribute
** Get_Started|Get Started
** SatNOGS_DB|Crowd-Sourced Satellite Info
** Software_contribution|Software Contribution
** Server_Development_Environment|Server Development Environment
** Hacking_the_GNURadio_Module_'gr-satnogs'|SatNOGS GNURadio Module
** SatNOGS_Client_Development|SatNOGS Client Development
** Adding_a_new_data_decoder|Adding a new data decoder
** Academic_Papers|Academic Papers citing SatNOGS
** Provide_documentation|Provide Documentation
** SatNOGS_Operations_Manual|SatNOGS Operations Manual
* Learn
** Rotators|Rotators
** Antennas|Antennas
** Understanding_satnogs-flowgraphs| Understanding SatNOGS Flowgraphs
** SDR_Setup| SatNOGS SDR setup
** Spectrum_Management | Spectrum Management and Frequency Coordination
** Glossary|Glossary
* Contact
** Get_In_Touch|Get In Touch
** https://community.libre.space|Forums
** Press|Press
* Links
** https://db.satnogs.org|SatNOGS DB
** https://network.satnogs.org|SatNOGS Network
** https://dashboard.satnogs.org|SatNOGS Dashboard
** https://community.libre.space|SatNOGS Forums
** https://libre.space|Libre Space Foundation
** https://status.libre.space|System Status
* SEARCH

Glossary

2021-11-04T14:46:27Z

Kerel+satnogs: Glouton

This is a list of common terms and abbreviations used in the satellite community. __NOTOC__

Altitude - Sometimes referred to as elevation, is the angle between the object and the observer's local horizon. For visible objects it is an angle between 0 degrees to 90 degrees
Attitude - Spacecraft orientation in space, see [https://en.wikipedia.org/wiki/Attitude_control#Spacecraft_attitude_control Spacecraft Attitude Control] 
Azimuth - The azimuth is the angle between the north vector and the perpendicular projection of the satellite (or star) down onto the horizon. Azimuth is usually measured in degrees (°). The concept is used in navigation, astronomy, engineering, mapping, mining and artillery. 
Dashboard -
Decoder -
Demodulator -
Elevation - The elevation is the angle above the horizon. Elevation is normally measured in degrees (°).The concept is used in navigation, astronomy, engineering, mapping, mining and artillery.
Fixed Ground Station - A ground station that uses fixed antennas that wait for the satllite to pass overhead. There are no moving parts in this system.
Glouton - https://github.com/deckbsd/glouton-satnogs-data-downloader
Ground Station - A hardware and software combination that comprises primarily of a receiver, SatNOGS client and antenna. There are two main types. Fixed and Steerable.
Helical Antenna -
Horizontal Co-ordinate System - Sometimes also called the az/el system, the Alt/Az system or the altazimuth system (from the name of the altazimuth mount for telescopes, whose two axes follow altitude and azimuth) is a celestial coordinate system that uses the observer's local horizon as the fundamental plane. It is expressed in terms of altitude (or elevation) angle and azimuth.
Observation - The scheduling and vetting of a particular satellite through a specific ground station. Observations are scheduled using the SatNOGS Network
RTL-SDR - A cheal USB 'dongle' based on a commonly available chipset that can be used as a broadband VHF and UHF receiver. There are a huge variety of dongles with a price ranging from $3 to $30+
Rotator - The Rotator is the mechanism that points the antenna at a satellite, and follows it as it passes overhead. There are multiple versions of the SatNOGS Rotator: * [[SatNOGS Rotator v1|Version 1]] * [[SatNOGS Rotator v2|Version 2]] * [[SatNOGS Rotator v3|Version 3]]
SatNOGS Client - Software used to handle scheduling and controlling observations at the ground station
SatNOGS DB - A database of all of the satellites that can be observed through the SatNOGS system. The database contains a brief explanation fo the satelitte, its transmitters and TLE's required to conduct an observation.
SatNOGS Network - The infrastructure based around a client and server that handles observations and the results of the obervations.
Satellite - In the context of spaceflight, a satellite is an artificial object which has been intentionally placed into orbit. Such objects are sometimes called artificial satellites to distinguish them from natural satellites such as Earth's Moon. Satellites are used for a large number of purposes. Common types include military and civilian Earth observation satellites, communications satellites, navigation satellites, weather satellites, and research satellites. Space stations and human spacecraft in orbit are also satellites. Satellite orbits vary greatly, depending on the purpose of the satellite, and are classified in a number of ways. 
Steerable Ground Station - A ground station that makes use of a rotator to point antennas at a satellite as it passes overhead. This set up will require a rotator.
TLE -
Turnstile Antenna -
Yagi Antenna -

[[Category:Hardware]]
[[Category:Software]]
[[Category:Build]]
[[Category:Operate]]
[[Category:Develop]]

SatNOGS Rotator v3

2021-11-01T12:13:09Z

Kerel+satnogs: Fix latest release name (added -pre-release suffix)

{{Template:Rotator
|Rotator-Name=SatNOGS Rotator v3
|image=V3.jpg
|type= Az/El
|cost=~220 USD
|status= Beta
|latest-release= https://gitlab.com/librespacefoundation/satnogs/satnogs-rotator/tags/v3.1-pre-release
|latest-release-name= v3.1-pre-release
|source-repo= https://gitlab.com/librespacefoundation/satnogs/satnogs-rotator/
|documentation= [https://ohai.libre.space/project/satnogs-rotator-v3-mechanical-assembly/satnogs/ v3.0.1] [https://wiki.satnogs.org/SatNOGS_Rotator_v3#Build_Sequence v3.1]
}}

==Introduction==

v3 marks a major re-haul of the SatNOGS Rotator design, with learnings from [[SatNOGS Rotator v2|v2]] applied. You can see a lot of the thinking and background research that was conducted prior to v3 development in this [https://community.satnogs.org/t/satnogs-rotator-version-3/226 thread]. Also in this wiki page you can also find a "How to build the rotator", mechanical analysis and all documentation about the [https://gitlab.com/librespacefoundation/satnogs/satnogs-rotator SatNOGS rotator].

Also in this [https://ethercalc.net/v3specs list] is presented different rotators, either commercial or DIY builds.

==Specifications==

{| {{table}}
| style="background:#f0f0f0;" align="center" |
| style="background:#f0f0f0;" align="center" |'''SatNOGS v3 Rotator'''
|-
|Plastic Parts||15
|-
|Non Printed Parts||38
|-
|Cost||~ $220
|-
|Controller Electronics||[[SatNOGS Rotator Controller]]
|-
|Type||AZ/EL (possible X/Y)
|-
|Motors||2x NEMA 17 Stepper or 2x DC Motors
|-
|Frame Material||Aluminum T-slot 20x20
|-
|Speed (deg/sec)||7
|-
|Torque (Nm)||?, ~30
|-
|Brake Torque (Nm)||?
|-
|Dimensions (mm)||280x140x140 (AZ/EL)
|-
|Weight (kg)||~5
|
|}

====Design Goals====
Considering the specifications as detailed in the [https://wiki.satnogs.org/SatNOGS_Rotator_v3#Mechanical_Analysis_.5BWIP.5D Mechanical Analysis], we would also like for the 3rd version of SatNOGS rotator to be:

*inexpensive (less than €300, if possible)
*lightweight and portable (~6Kg, size:~300x~150x~150mm)
*rigid and durable
*easy to build and fix (try to use easily available materials)
*weatherproof
*electromagnetically shielded, so that noise in reception is reduced
*accurate (<1deg, backlash reduction and use of encoders at the axis)

==Sourcing==

'''3d Printing at a Fab Lab or your local hackerspace:''' If you don't have your own 3d printer, then a local Fab Lab or hackerspace may be able to do it for you. Fab Labs and hackerspaces are places that have invested in the machinery and you can take the designs to them. Generally they need .stl files to import into the software that runs the machines, but this should be discussed with the Fab Lab or hackerspace. You then pay for the material, time or a combination of the two for each of the parts or any other agreement in place.

*[http://www.fabfoundation.org/fab-labs FabLabs]
*[https://wiki.hackerspaces.org/List_of_Hacker_Spaces List of hacker spaces]

Most people building the rotator have had success builds with simple ABS material for the 3D printing parts.

'''T Slot''' - If you don't want to cut the pieces yourself, then you may be able to find a supplier that will do this for you. ([http://www.kjnltd.co.uk/ Here's one in the United Kingdom].)

Hidden corner connectors - AliExpress gave the cheapest supplier

A good US source is [http://us.misumi-ec.com/ MISUMI-USA]; they will also cut to length. MISUMI has several other global locations [https://www.misumi-ec.com].

Beware, the 20-series T-slot from [https://8020.net/ 80/20 Inc.] in the US has slots that are only 5.2mm wide. The hidden corner connectors from e.g. AliExpress '''will not fit'''.

'''Stepper Motors''' - eBay

'''Belts''' - eBay

'''Fixings / Pipe''' - eBay

====Vendors Table====

Like the [https://reprap.org/wiki/RepRap_Buyers%27_Guide RepRap Buyers' Guide wiki], feel free to populate the table.

{| class="wikitable"
|-
!Vendor
!Location
!Parts
!Notes
|-
|[https://www.pololu.com/ pololu]
|USA, Worldwide
|Motors, electronics
| -
|-
|[http://mouser.com/ mouser]
|Worldwide
|Motors, electronics
| -
|-
|[https://www.ebay.com/ ebay]
|Worldwide
|Motors, electronics, Fasteners, T-Slots, pulleys, Tubes
| -
|-
|[https://www.aliexpress.com/ aliexpress]
|Worldwide
|Motors, electronics, Fasteners, T-Slots, pulleys, Tubes
| -
|-
|[https://grobotronics.com/ grobotronics]
|GR, EU
|Motors, electronics, Fasteners, T-Slots, pulleys
| -
|-
|[https://www.motedis.com/shop/index.php motedis]
|DE, EU
|T-Slots, Tubes
| -
|-
|[https://uk.misumi-ec.com/ Misumi]
|Worldwide
|T-Slots, Tubes, Fasteners, Pulleys
| -
|-
|[https://www.omc-stepperonline.com/ omc-stepperonline]
|Worldwide
|Stepper motors
| -
|-
|[https://www.fastenal.ca/ fastenal]
|USA
|Fasteners
| -
|-
|[https://www.mcmaster.com/ mcmaster]
|USA
|Fasteners
| -
|-
|[http://www.rs-online.com/ rs]
|Worldwide
|Electronics, fasteners, motors
| -
|-
|[https://8020.net/ 80/20]
|USA
|T-Slots
| -
|-
|[https://www.pcbway.com/ pcbway]
|CN
|PCB fabrication
| -
|-
|[https://www.servocity.com/ servocity]
|USA
|Motors, T-slots, fasteners
|Most of parts are not metric
|-

|}

==Build Sequence==

====Tools & Consumables====
Here are presented tools and consumables about part fabrication, port-processing and assembly process.
Most of the tools are available in every hackerspace, makerspaces, FabLabs etc.

{| class="wikitable"
|-
!Tool/Consumable
!Description
|-
|Drill bits
|2mm for aluminum, 3mm, 4mm and 5mm for plastic
|-
|Drill driver
|For aluminum tube drill hole, 3D printed part
|-
|Sandpaper
|80(dry), 120(dry), 240(dry) and 1000(wet) grit
|-
|Acetone
|For acetone vapor bath
|-
|Hacksaw
|For aluminum Tube
|-
|Square File
|For worm axis, for use on steel
|-
|Precision Knife
|For general use, especially in 3d-Printed parts
|-
|Caliper
|Measuring Range 0-150mm
|-
|Combination Wrenches
|5.5mm, 7mm and 8mm
|-
|Thread-locker
|Like Loctite 271
|-
|Cyano acrylic glue
|Like Loctite 401
|-
|Screw driver
|Number 1 Phillips
|-
|Heat Gun
|For Heat-shrinkables or use a lighter
|-
|Ball-End L-Keys
|Hex 1.5mm, 2mm, 2.5mm, and 3mm
|-
|Soldering iron and consumables
|For cables
|-
|Wire Cutter
|For cables
|-
|Long-Nose Plier
|General purpose
|-
|}

====Parts====
Make sure you have all parts, according to [https://gitlab.com/librespacefoundation/satnogs/satnogs-rotator/blob/master/rotator-bom.ods BOM].

Most of the parts could be fabricated by a FDM 3D-printer. Some parts have only 2D geometry so could be
fabricated by a laser cutter. Other parts have modifications of common(hardware) parts like threaded rods or
aluminum pipes. Also you could find a lot of guides for [https://www.3dhubs.com/knowledge-base/post-processing-fdm-printed-parts post processing for FDM printed parts].

<gallery widths="200" heights="200" perrow="4">
File:C1001.png|C1001, Aluminum Tube 6063 OD40mm TH1.5mm L240mm, 2 variants -1 and -3
File:C1010-3.png|C1010-3, FDM-3Dprinted, Material: ABS, Layer height: 0.4 mm, Perimeters: 2, Top/bottom solid layers: 3, Fill density: 20%, Fill pattern: Honeycomb, Fan speed: [35, 100], No support material
File:C1011-3.png|C1011-3, laser cut in 3mm Acrylic Sheet or in FDM-3Dprinter with same fabrication parameters as C1010-3
File:C1020-1.png|C1020-1, FDM-3Dprinted, Material: ABS, Layer height: 0.4 mm, Perimeters: 2, Top/bottom solid layers: 3, Fill density: 20%, Fill pattern: Honeycomb, Fan speed: [35, 100], No support material, [http://sinkhacks.com/building-acetone-vapor-bath-smoothing-3d-printed-parts/ Smoothing the part with acetone vapor bath]
File:C1021-1.png|C1021-1, FDM-3Dprinted, Material: ABS, Layer height: 0.4 mm, Perimeters: 2, Top/bottom solid layers: 3, Fill density: 20%, Fill pattern: Honeycomb, Fan speed: [35, 100], No support material, [http://sinkhacks.com/building-acetone-vapor-bath-smoothing-3d-printed-parts/ Smoothing the part with acetone vapor bath], [https://community.libre.space/t/version-3-1-stepper-varient-with-v2-controller/1430/5 Imperial variant], [https://community.libre.space/t/help-to-buy-metric-tubing-for-v3-rotator/784/6 tool that helps to build imperial part]
File:C1022-3.png|C1022-3, laser cut in 3mm Acrylic Sheet or in FDM-3Dprinter with same fabrication parameters as C1010-3
File:C1030-1.png|C1030-1, FDM-3Dprinted, Material: ABS, Layer height: 0.4 mm, Perimeters: 2, Top/bottom solid layers: 3, Fill density: 20%, Fill pattern: Honeycomb, Fan speed: [35, 100], No support material
File:C1040-1.png|C1040-1, FDM-3Dprinted, Material: ABS, Layer height: 0.4 mm, Perimeters: 2, Top/bottom solid layers: 3, Fill density: 20%, Fill pattern: Honeycomb, Fan speed: [35, 100], No support material, [https://community.libre.space/t/version-3-1-stepper-varient-with-v2-controller/1430/5 Imperial variant], [https://community.libre.space/t/help-to-buy-metric-tubing-for-v3-rotator/784/6 tool that helps to build imperial part]
File:C1041-1.png|C1041-1, FDM-3Dprinted, Material: ABS, Layer height: 0.4 mm, Perimeters: 2, Top/bottom solid layers: 3, Fill density: 20%, Fill pattern: Honeycomb, Fan speed: [35, 100], No support material, [https://community.libre.space/t/version-3-1-stepper-varient-with-v2-controller/1430/5 Imperial variant], [https://community.libre.space/t/help-to-buy-metric-tubing-for-v3-rotator/784/6 tool that helps to build imperial part]
File:C1042-1.png|C1042-1, laser cut in 3mm Acrylic Sheet or in FDM-3Dprinter with same fabrication parameters as C1010-3
File:C1043-1.png|C1043-1, FDM-3Dprinted, Material: ABS, Layer height: 0.4 mm, Perimeters: 2, Top/bottom solid layers: 3, Fill density: 20%, Fill pattern: Honeycomb, Fan speed: [35, 100], Support material, Brim Width: 2 mm
File:C1050.png|C1050, Aluminum Profile 20x20 B-type slot 6, 2 variants -1 and -5
File:C1060-1.png|C1060-1, M5 Threaded rod A2 stainless steel(304)
File:C1061.png|C1061, 2 variants -5 and -6, FDM-3Dprinted, Material: ABS, Layer height: 0.4 mm, Perimeters: 2, Top/bottom solid layers: 3, Fill density: 20%, Fill pattern: Honeycomb, Fan speed: [35, 100], No support material
File:C1062-1.png|C1062-1, It is recommended to build in laser sintering like Shapeways with White Versatile Plastic (cost ~10€) or like C1030-1 and [http://sinkhacks.com/building-acetone-vapor-bath-smoothing-3d-printed-parts/ Smoothing the part with acetone vapor bath]
File:C1070-1.png|C1070-1, FDM-3Dprinted, Material: ABS, Layer height: 0.4 mm, Perimeters: 2, Top/bottom solid layers: 3, Fill density: 20%, Fill pattern: Honeycomb, Fan speed: [35, 100], No support material
File:C1071-1.png|C1071-1, FDM-3Dprinted, Material: ABS, Layer height: 0.4 mm, Perimeters: 2, Top/bottom solid layers: 3, Fill density: 20%, Fill pattern: Honeycomb, Fan speed: [35, 100], No support material
File:C1072-1.png|C1072-1, FDM-3Dprinted, Material: ABS, Layer height: 0.4 mm, Perimeters: 2, Top/bottom solid layers: 3, Fill density: 20%, Fill pattern: Honeycomb, Fan speed: [35, 100], No support material
File:C1083-1.png|C1083-1, FDM-3Dprinted, Material: ABS, Layer height: 0.4 mm, Perimeters: 2, Top/bottom solid layers: 3, Fill density: 20%, Fill pattern: Honeycomb, Fan speed: [35, 100], No support material
File:C1080-3 2.png|C1080-3, Cover Box bottom part, galvanized steel sheet, thickness 0.5mm
File:C1081-3 2.png|C1081-3, Cover Box top part, galvanized steel sheet, thickness 0.5mm
File:C1082-5.png|C1082-5, Cover Box side part, galvanized steel sheet, thickness 0.5mm
File:C1084-1.png|C1084-1, FDM-3Dprinted, Material: ABS, Layer height: 0.4 mm, Perimeters: 2, Top/bottom solid layers: 3, Fill density: 20%, Fill pattern: Honeycomb, Fan speed: [35, 100], No support material
</gallery>

====Assembly====
Follow the [https://ohai.satnogs.org/project/satnogs-rotator-v3-mechanical-assembly/hardware/ instructions for mechanical assembly] and also you can [https://www.youtube.com/watch?v=D6P9HK23Gmo watch timelapse]
Also, exploded views and instructions are present here.

{{Message|
Prior to Step 8, the rotary encoders must be ready and prior to Step 11 the motor must be mounted in A1070-1. For the rotary encoder assembly look at the next section [https://wiki.satnogs.org/SatNOGS_Rotator_v3#Rotator_Controller Rotator_Controller].}}

Some notes for assembly:

*Resolve collision between of end-stop arm and C1042-1 end-stop mount, [https://community.libre.space/t/rotator-3-1-end-stop-switch-mounting/3463 community post]
*[https://community.libre.space/t/rotator-3-1-worm-gear-issues/1858/7 Running the worm gear] and [https://community.libre.space/t/rotator-3-1-worm-gear-issues/1858/9 lapping the worm gear] to get gear box running smooth
*[https://community.libre.space/t/stepper-motor-bolts-v3-1/3388 Collision between bolts and motor], this issue can be created by using wrong M4 screws(H1100-5) and washers(H1110-1)

<gallery widths="180" heights="180" perrow="4">
File:A1010-1.png|Step 1, Prepare the assembly of worm gear
File:A1011.png|Step 2, Prepare the assembly of worm gear mount, 2 variants -1 and -2 (mirror)
File:A1020-1.png|Step 3, Prepare the assembly of shaft collar for worm wheel
File:A1033-1.png|Step 4, Prepare the encoder gear
File:A1070-1.png|Step 5, Prepare the Motor mount
File:A1060-1.png|Step 6, In case of DC motor configuration
File:A1031-1.png|Step 7, Bearing side without encoder and end-stop mounts
File:A1032-1.png|Step 8, Bearing side with encoder and end-stop mounts
File:A1030.png|Step 9, Prepare symmetric and asymmetric axis, 2 variants -1 and -3
File:A1001-3.png|Step 10, Frame with worm gear mount and A1001-1 assembly
File:A1040.png|Step 11, Rotator module 2 Variants -1 and -3, symmetric and asymetric [[:File:Tip for Step 11 (A1040) -- Note 10 - use of M5 Nuts to attach Drill.jpg|(Assembly Tip - Note 10:Jam two M5 nuts together at end of shaft to easily run gearbox manually)]]
File:A1050-1.png|Step 12, Final step of Antenna Rotator
</gallery>

====Rotator Controller====
The default way of controlling the rotator is to use the [[SatNOGS Rotator Controller]].This works for both stepper motor and DC motor set ups (Note: If you are uing the [https://wiki.satnogs.org/SatNOGS_Rotator_Controller#Encoders the rotary encoders] these will need to be set up). An alternative is to use the [[SatNOGS_Arduino_Uno/CNC_Shield_Based_Rotator_Controller]], whih has been used as a stand alone set up for use with GPredict.

It's also possible to use a standard 3d printing RAMPs 1.4 board as an alternative, though note that these are designed for steppers which may cause extra RF noise. A RAMPs 1.4 [https://github.com/TheSkorm/satnogs-rotator-ramps14 firmware] has been developed.

====Cover Box - Cabling====
Prepare the cover box and install it to antenna rotator with rotator controller and cables.

<gallery widths="200" heights="200" perrow="4">
File:Cover_box_1.JPG| Put the C1080-3 with screws M4 L10 DIN912, C1084-1 and washers M4 DIN125 to the azimuth module. The screw with the Phillips Rounded Head Screws For Sheet Metal, M3,5 X 6,5, DIN 7981,INOX A2, C1082-5 to the C1080-3 and put the C1083-1. Note screw only the middle screw.
File:Power_cable_1.JPG| The power - data cable must be passed inside the azimuth axis. This solution is tested [https://network.satnogs.org/stations/200/ in station 200] without problem.
File:Power_cable_2.JPG| In the other side of power cable must be installed a connector with 4 terminals and waterproof like [https://grobotronics.com/connector-sp-4-pin-male.html Weipu - SP1310/P4I]. Also it is needed to have the female connector for cable that connected to the client. For cheaper solution use a bigger cable to connect the rotator with client and power source.
File:Other_cables_2.JPG|The 3 CAT5e UTP cables are 2x sensors (encoders - end stops) 1x power and data (RS-485). For color code use [https://en.wikipedia.org/wiki/Power_over_Ethernet#Pinouts 802.3af Standards A and B] from the power sourcing equipment perspective.
File:Other_cables_3.JPG|The other cables are for DC motor or stepper motors. In each side of the CAT5e UTP cables must be put a Heat-shrinkable asreferred in [https://gitlab.com/librespacefoundation/satnogs/satnogs-rotator/blob/master/rotator-bom.ods BOM]. Also a Heat-shrinkable must be putin the cable gland in rotator controller for motor cables.
File:Other_cables_1.JPG|Pass all the cables though the hole in the bottom of C1080-3
File:Motor_ferrite_bead.JPG|Add ferrite beads for motor cables, dimensions L25mm and OD 13mm
File:Velcro_for_controller_1.JPG|Add velcro to mount the rotator controller outside the box. Velcro tape specifications: Heavy duty, stick on, max 7Kg, 50mm x 100mm. The tape might be used to mount [https://wiki.satnogs.org/No_rotator client box] in the rotator.
File:Rotator_controller_1.JPG| Cabling management inside the rotator controller. The controller is mounted to the rotator by using a tape as mentioned previously.
File:Rotator controller 2.JPG| Cabling management outside the rotator controller
File:Testing_1.JPG| The rotator is ready for testing, before the final step do not put the C1081-3, in order to most of components must be accessible
File:Testing 2.JPG| The final step. If everything is working properly, must be put the C1081-3 by using sheet metal screws as mentioned previously. In this step if the holes of C1081-3 are not aligned with the holes of the other two parts, C1082-5 and C1080-3, drill new holes and screw them, take a look in [https://gitlab.com/librespacefoundation/satnogs/satnogs-rotator/issues/73 issue 73]. Put stickers!!!!!!

</gallery>

====Testing====
You are ready! Proceed with [https://wiki.satnogs.org/SatNOGS_Rotator_Controller#Troubleshooting_hints testing].

====Heading Calibration====
The heading calibration is a manual process:

*Power the rotator, it starts moving in order to find the home position, to find the end-stops
*Remove the power from the rotator, the rotator is in home position
*Install the rotator to vertical axis by using U-Bolt clamps
*The azimuth axis it must be heading to the North, this is achieved by using a compass (e.g. from smart phone)
*Secure the rotator in the vertical axis
*Install the elevation axis with the same process, now the zero elevation is achieved by using a pocket level
*Secure the elevation axis
*In the case of wrong rotation:
**For stepper motors swap a pair of two stepper motor cables ([https://gitlab.com/librespacefoundation/satnogs/satnogs-rotator-firmware/issues/15 it exists an open issue to be done by a command])
**For DC motors, [https://gitlab.com/librespacefoundation/satnogs/satnogs-rotator-firmware/commit/961fb696536e35642f2b7064cc3c64676ebebb17 change the sign of encoder reading], it is a hacky method but it would be resolved by [https://gitlab.com/librespacefoundation/satnogs/satnogs-rotator-firmware/issues/15 this issue]

====Counterweight for Antenna====
It is necessary to balance the antenna in elevation and azimuth axis in order to not wear the gear box of rotator. In elevation axis would be done either by using back mounted antennas or by mounting the center of antenna mass in the mast. For a back mounted antenna, it is necessary to use counter-balance weights. An idea is to use weights that is used for training (it's cheap). The parts that used to mount weights to [https://www.wimo.com/en/x-quad X-quad antenna] are this [https://gitlab.com/librespacefoundation/satnogs/satnogs-hardware-misc/-/tree/master/mount-counterweight 3D printing part], a square aluminum profile 15x15 mm, weights with inner hole D28mm and M5 hex nuts DIN934 with M5 screws DIN912 L12 stainless steel to lock the weights in specific distance. Another way to [https://community.libre.space/t/quartapounds-satnogs-rotator-v3-1/3453/57 balance the antenna].

[[File:Counter-weight.jpg|thumb|center|800x420px|alt=|Counterweights]]

==Mechanical Analysis [WIP]==

====Brake Torque====
The greatest force the tracker needs to withstand is the force created by strong wind. The worst case is when one antenna is elevated at 90 degs, facing the direction of the wind. We based our calculations on an [http://k7nv.com/notebook/topics/windload.html article] found online after comparing it to others. We “translated” the second table in metric (because we don’t understand imperial and because we needed same units system in our calculations)

{| class="wikitable"
|-
!Method
!Wind Zone(km/h)
!Height (m)
!Pressure(N/m^2)
|-
|EIA-222-C
|160
|N/A
|1280

|-
|EIA-222-F
|128
|14
|1260

|-
|EIA-222-F
|128
|21
|1390

|-
|EIA-222-F
|128
|30
|1500

|-
|UBC'97
|128
|14
|1290

|-
|UBC'97
|128
|21
|1160

|-
|UBC'97
|128
|21
|1390

|-
|UBC'97
|128
|30
|1260

|-
|UBC'97
|128
|42
|990

|-
|UBC'97
|128
|42
|1360

|-
|Generic Formula
|150
|N/A
|1270

|}

and we applied the worst case model (EIA-222-F) in 3 different antennas: in the biggest one of our designs, and in two others, for which we obtained data from [http://download.qrz.ru/pub/hamradio/antenna/rotators/G-800SA_1000SA.pdf yaesu G800 rotator manual at page 3]. We assumed that antennas are mounted in 1m away from the azimuth axis. For our antenna with 2m length (actual, not wavelength), made by 2cm square tube, the generated torque was ≈600Kg*cm. For the 144MHz 10-elements Yagi from the article is ≈6000Kg*cm and for the third 430MHz, 12-elements Yagi is ≈1800Kg*cm

====Moment of inertia====
Now for the moment of inertia: (for all installation methods we assumed that antennas are counterbalanced in the elevation axis) the worst case scenario here is to use two 3kg (our designs are less than 1kg) back mounted yagis with 3kg counterbalances both mounted in 0.75m away from azimuth axis. The torque you need in order to accelerate this system from ω=0deg/s angular velocity to ω=5deg/s (the math about angular velocity is below) in one second is about 60kg*cm.

Note: we suppose that the mass of antennas is near to the altitude axis, so the torque of this axis that is needed to accelerate is approximately 0.

*M1: torque of Azimuth axis
*L: length of center of mass of antennas from azimuth axis (0.75m)
*m: mass of antennas and of counterweight (3kg + 3kg = 6kg)
*I: moment inertia
*a: angular acceleration of azimuth axis 5deg/s^2
*I = I1 + I2 = m*L^2 + m*L^2 = 2*m*L^2 = 6.75 kg*m^2
*M1 = I*a = 6.75kgm^2 * 0.087rad/s^2 = 0.58 Nm = 5.8 kgm = 58 kgcm

====Angular velocity====
(How well do you remember trigonometry?)For the angular velocity max needed in altitude axis the things are straightforward. The closer is the satellite the larger the velocity. According to the wikipedia article about LEO, the lowest height limit is 160 km and the speed unit to orbit earth in this altitude is 7,8 km/s. As a result, maximum velocity in ALT axis is 2,8 deg/s. In ALT AZ rotator design there is a well known limitation: the closer something passes near zenith the biggest gets the velocity of the AZ axis. Therefore, we have analyzed this problem to figure out the optimal velocity and how high we are allowed to track a target in relation to AZ velocity. The picture below illustrates a ground station B which tracks a satellite Γ in X degrees altitude. The satellite velocity at this point is vertical to the screen (page) plane.

[[File:Anglular_velocity.png|thumb|center|800x420px|alt=|Angular Velocity]]

The equations that lead to maximum altitude at which we can track in relation to AZ angular velocity are

*ω : angular velocity of AZ DOF in rad/s
*H = ΑΕ + ΕΓ : Minimum Height of LEO, 160 km
*R = ΑΕ : Radius of Earth, 6500 km
*u : linear velocity of satellite that rotates in 160km height is 7.8 km/s
*ΒΔ = u / ω : ΒΔ in km
*α = atan(ΒΔ / R)
*δ = π - α
*γ = asin( sqrt(R^2+ΒΔ^2) * sin(δ) / (H+R) )
*ά = π - δ - γ
*ΓΔ = (H+R) * sin(ά) / sin(δ)
*χ = atan(ΓΔ / ΒΔ)

Below you can see the plot of the equations mentioned above, where horizontal axis represents angular velocity (ω) in deg/s and vertical axis shows the max track altitude (χ) for lower bound of LEO.

[[File:Anglular_velocity_plot.png|thumb|center|800x420px|alt=|Angular Velocity Plot]]

After studying this diagram, we came up to the conclusion that an angular velocity of 5 deg/s is adequate. For this decision, we took into consideration the main lobe of antenna (Δ3db) which in most situations is about 20 deg.

====Pulleys/Belts/Gearing====
Horizontal distance between pulleys (P1, P2) is 58mm.
Vertical distance between pulleys (P1, P2) is w = 9.5mm.

Pulleys and Belt are GT2, 2mm pitch.
Belt width, 6mm.
Belt thickness, 1.38mm (0.76 tooth).

Wrap angle in both pulleys is larger than 60deg.
At least 6 teeth in contact with the pulley at any given time.
In practice that means you want a minimum of a 12 tooth pulley, and usually try to get at least 18 teeth.

Outer Diameter of pulleys:

P(T) | OD(mm) 
16 | 10.2 
20 | 12.7 
36 | 22.9 
40 | 25.5 

Belt calculation (according to calculator):

Ratio | P1(T) | P2(T) | Belt(T) | L(mm) 
2.25|16|36|85/86|58.65/59.66 
1.8|20|36|86/87/88|57.78/58.78/59.78 
2.5|16|40|87/88|58.5/59.5 
2|20|40|89/90|58.65/59.66 

Motor Maximun no-load speed, 200RPM = 1200deg/s
Motor Maximum stall-torue, 1.2Nm

[[File:Motor_perfomance_graph.png|thumb|center|800x420px|alt=|Angular Velocity]]

Position of idler do not care, or min 1.3*P1, max 1.5*P1 (for 20T, ~16mm/~20mm).

Belt gear selection:

*20/36 with 1.8 ratio and 86T/172mm belt without idler
*20/40 with 2 ratio and 90T/190mm belt with idler

To calculate Deflection force, (page T-31, sdp - design-guidelines)

*Y = 2.05, Tst = 1.3kg
*span length, t = 57.64mm
*Belt pitch length, L = 180mm
*Fd,min =
*Fd,max =
*2.8kg Working Tension [shapeoko - Belts and Pulleys](https://www.shapeoko.com/wiki/index.php/Belts_and_Pulleys#Tensile_Cord_Materials)

P3 
/ \ 
P1 P2 
| 
P4-P5 

*Determination of design load

According to perfomance graph of DC motor, the optimal output power is Tm = 0.6Nm with efficiency of 0.2 and 100RPM = 600deg/s.
Select a service factor of 1.5 (service factors between 1.5 and 2.0 are generally recommended when
designing small pitch synchronous drives).
Tpeak = SF*Tm = 1.5*0.6 = 0.9Nm

*Choice of belt pitch

Due to backslash and accuracy in both directions of movements and volume constrains, we choose GT2, pitch 2mm.

*Check belt pitch selection based on individual graphs

Due to Tpeak = 0.9Nm No-load speed,(Speed of fastest shaft) = 100RPM = 600deg/s
GT2 pitch 2mm belt is the better solution for our application.

*Determine speed ratio

Speed ratio 1.8-2.25 according to specification of output rotation speed of 5deg/s.

*Check belt speed

V(m/s) = 0.0000524 x pulley PD (mm) x pulley rpm = 0.066548m/s
Belt speeds up to 6,500 fpm (33.02 m/s) do not require special pulleys.

*Determine belt length

Table 'Belt calculation (according to calculator)'
Teeth in mesh: 9

*Determine the belt width

From Table 43
torque = 0.17Nm
Length Correction Factor = 0.9
width multiplier = 1.00
torque*Length Correction Factor*width multiplier = 0.17*0.9*1.00 = 0.153Nm
Teeth in mesh: 9
Tpeak = 0.9Nm, so belt width is nice for our application

*Check the number of teeth in mesh

Teeth in mesh: 9 according to calculator

*Determine proper belt installation tension

SECTION 10, on page T50, look at 'To calculate Deflection force, (page T-31, sdp - design-guidelines)'

*Y = 2.05, Tst = 0.812*DQ/d + mS^2 = 12.8lb + 0 = 5.8kg
*DQ = Tpeak = 0.9Nm = 7.9lb-in
*d = 12.7mm = 0.5in
*S = (0.5*100/3.82)/1000 = 0.0131ft/min
*m = 0.039
*span length, t = sqrt(CD^2 - (PD-pd/2)^2) = 57.64mm
*Belt pitch length, L = 180mm
*t/L = 0.32
*Fd,min = 0.8lb = 0.36kg
*Fd,max = 0.9lb = 0.41kg

*Safety factor 1.5

*P2 timing pulley torque - Maximum radial load of timing belt ball bearing 625zz

Tpeak = 0.9Nm
TorqueP2 = 2*0.9Nm = 1.8Nm, PDp2 = 25.5mm
Radial static load of 625ZZ is 0.38kN
T-39

*Maximum thrust load of timing belt ball bearing 625zz

*Maximum radial and thrust load of output ball bearings 6008zz

Calculate or evaluate correct loads for deep groove ball bearings
radial static load = 11.6kN
thrust static load = 0.7*11.6kN = 8.12kN
This type of construction permits the bearings to support relatively high thrust load in either direction.
In fact the thrust load capacity is about 70% of the radial load capacity. A ball bearing primarily designed
to support radial load can also support high thrust load; because only few balls carry the radial load,
whereas all the balls can withstand the thrust load.

*Maximum self-locking or back-drivable torque of gear box (according to more weak component)

It necessary to achieve [specs](https://community.libre.space/t/satnogs-rotator-version-3/226), 60Nm (6Kg in 1 meter)

*Nominal torque of drivable torque of gear box (according to more weak component) and maximum rotational speed of gear box

Notes:

*[https://sdp-si.com/eStore/CenterDistanceDesigner sdp distance calculator]
*[http://www.ebay.com/itm/2GT-Timing-Belt-L-172-232-240-244-640-810-GT2-Belts-closed-loop-5pcs-lot-/221977955532?var=&hash=item33aeeacccc:m:me5GvSt_amrm6RWT03Ut4JA belt GT2-6mm wide, 172mm]
*[https://www.ebay.com/itm/2GT-GT2-synchronous-Timing-belt-Perimeter-98-194mm-width-6-9mm-Cogged-close-loop/222574382655?ssPageName=STRK%3AMEBIDX%3AIT&var=521434616407&_trksid=p2060353.m2749.l2649 belt GT2-6mm wide, 180mm]
*[http://www.ebay.com/itm/5pcs-Timing-Pulley-GT2-Idler-16-20T-gear-Bearing-Reprap-6mm-Belt-3-5mm-Bore-3D-/132195520937?var=&hash=item1ec77791a9:m:mljSYBViBlKOgXr3Gy-u0Tg idler pulley, no-teeth-ID3mm-OD18mm]
*[http://www.brecoflex.com/products/pulleys/design-guidelines/ brecoflex - design-guidelines]
*[http://www.shreegeeimpex.com/TECH_DATA_PAG/idlers_ten.htm shreegeeimpex - design-guidelines]
*[http://www.sdp-si.com/PDFS/Technical-Section-Timing.pdf sdp - design-guidelines]

====Motor Specification====

General Specification about motors. The voltage and current consumption also it depends from the motor controller which is (maybe) different
from [https://wiki.satnogs.org/SatNOGS_Rotator_Controller SatNOGS Rotator Controller].

{| class="wikitable"
|-
!Specification
!Value
|-
|Min-Max Stall Torque (Nm)
|0.4 - 1.5
|-
|Min-Max Speed (RPM)
|100 - 200
|-
|Size (mm) (LxWxH)
|47x42x64
|-
|}

<gallery widths="200" heights="200" perrow="4">
File:Motor mount dimensions.png|Motor mount dimensions
File:Max motor height.png|Maximum Motor Height
</gallery>

====Worm Gear Box Calculations====

*Gear ratio: i12 = 30
*Angle between axis of gears: δ = 90 deg
*Number of threads in worm: If i12 >= 30 then z1 = 1
*Number of teeth in worm wheel: z2 = i12*z1 = 30
*Center distance: initial case a = 45.5 mm
*Worm reference diameter: AGMA d01>= 11.5*(a/25.4)^0.875 = 19.15 mm, so d01 = 19.5mm
*Worm wheel reference: d02 = 2*a - d01 = 71.5 mm
*Axial module: ms = d02/z2 = 2.38 , so ms = 2.5

Recalculate d02, a with new axial module

*d02 = z2*ms = 75mm, a = (d02+d01)/2 = 47.25mm
*Axial pitch: ts = π*ms = 7.854mm
*Reference lead angle: γ0 = atan(d02/(i12*d01)) = 7.3 deg
*Worm tip diameter: dk1 = d01 + 2*hk = 24.5mm
**Worm teeth reference addendum in axial section: hk = hk* *ms = 2.5mm
**Worm tooth reference addendum coefficient: hk* = 1
*Worm root diameter: df1 = d01 - 2*hf = 13.5mm
**Worm tooth reference dedendum: hf = hf* _ms = 1.2_ms = 3mm
**Dedendum coefficient: hf* = 1.2
*Worm length: L = 2.5_ms_sqrt(z2+2) = 35.36mm
*Worm tooth thickness: smx1 = smx1* * ts = 3.927mm
**Tooth thickness coefficient: smx1* = 0.5
*Normal pressure angle: aon = 20 deg
*Worm wheel throat diameter: dk2 = d02+2*hk = 80mm
*Worm wheel root diameter: df2 = d02 - 2*hf = 69mm
*Worm wheel outside diameter: de2 = dk2 + 2*mx = 83.5mm
**Worm wheel tooth external addendum: mx = n*ms, 0.4<=n<=1.5
*Effective worm wheel face width: b2H,max = sqrt((2_a - df2)^2 - (2_a - de2)^2) = 23mm

[[Category:Build]]
[[Category:Hardware]]
[[Category:Rotator]]

SatNOGS Rotator v3

2021-10-26T13:54:55Z

Kerel+satnogs: Fix broken URL to v3.0.1 documentation (OHAI)

{{Template:Rotator
|Rotator-Name=SatNOGS Rotator v3
|image=V3.jpg
|type= Az/El
|cost=~220 USD
|status= Beta
|latest-release= https://gitlab.com/librespacefoundation/satnogs/satnogs-rotator/tags/v3.1-pre-release
|latest-release-name= v3.1
|source-repo= https://gitlab.com/librespacefoundation/satnogs/satnogs-rotator/
|documentation= [https://ohai.libre.space/project/satnogs-rotator-v3-mechanical-assembly/satnogs/ v3.0.1] [https://wiki.satnogs.org/SatNOGS_Rotator_v3#Build_Sequence v3.1]
}}

==Introduction==

v3 marks a major re-haul of the SatNOGS Rotator design, with learnings from [[SatNOGS Rotator v2|v2]] applied. You can see a lot of the thinking and background research that was conducted prior to v3 development in this [https://community.satnogs.org/t/satnogs-rotator-version-3/226 thread]. Also in this wiki page you can also find a "How to build the rotator", mechanical analysis and all documentation about the [https://gitlab.com/librespacefoundation/satnogs/satnogs-rotator SatNOGS rotator].

Also in this [https://ethercalc.net/v3specs list] is presented different rotators, either commercial or DIY builds.

==Specifications==

{| {{table}}
| style="background:#f0f0f0;" align="center" |
| style="background:#f0f0f0;" align="center" |'''SatNOGS v3 Rotator'''
|-
|Plastic Parts||15
|-
|Non Printed Parts||38
|-
|Cost||~ $220
|-
|Controller Electronics||[[SatNOGS Rotator Controller]]
|-
|Type||AZ/EL (possible X/Y)
|-
|Motors||2x NEMA 17 Stepper or 2x DC Motors
|-
|Frame Material||Aluminum T-slot 20x20
|-
|Speed (deg/sec)||7
|-
|Torque (Nm)||?, ~30
|-
|Brake Torque (Nm)||?
|-
|Dimensions (mm)||280x140x140 (AZ/EL)
|-
|Weight (kg)||~5
|
|}

====Design Goals====
Considering the specifications as detailed in the [https://wiki.satnogs.org/SatNOGS_Rotator_v3#Mechanical_Analysis_.5BWIP.5D Mechanical Analysis], we would also like for the 3rd version of SatNOGS rotator to be:

*inexpensive (less than €300, if possible)
*lightweight and portable (~6Kg, size:~300x~150x~150mm)
*rigid and durable
*easy to build and fix (try to use easily available materials)
*weatherproof
*electromagnetically shielded, so that noise in reception is reduced
*accurate (<1deg, backlash reduction and use of encoders at the axis)

==Sourcing==

'''3d Printing at a Fab Lab or your local hackerspace:''' If you don't have your own 3d printer, then a local Fab Lab or hackerspace may be able to do it for you. Fab Labs and hackerspaces are places that have invested in the machinery and you can take the designs to them. Generally they need .stl files to import into the software that runs the machines, but this should be discussed with the Fab Lab or hackerspace. You then pay for the material, time or a combination of the two for each of the parts or any other agreement in place.

*[http://www.fabfoundation.org/fab-labs FabLabs]
*[https://wiki.hackerspaces.org/List_of_Hacker_Spaces List of hacker spaces]

Most people building the rotator have had success builds with simple ABS material for the 3D printing parts.

'''T Slot''' - If you don't want to cut the pieces yourself, then you may be able to find a supplier that will do this for you. ([http://www.kjnltd.co.uk/ Here's one in the United Kingdom].)

Hidden corner connectors - AliExpress gave the cheapest supplier

A good US source is [http://us.misumi-ec.com/ MISUMI-USA]; they will also cut to length. MISUMI has several other global locations [https://www.misumi-ec.com].

Beware, the 20-series T-slot from [https://8020.net/ 80/20 Inc.] in the US has slots that are only 5.2mm wide. The hidden corner connectors from e.g. AliExpress '''will not fit'''.

'''Stepper Motors''' - eBay

'''Belts''' - eBay

'''Fixings / Pipe''' - eBay

====Vendors Table====

Like the [https://reprap.org/wiki/RepRap_Buyers%27_Guide RepRap Buyers' Guide wiki], feel free to populate the table.

{| class="wikitable"
|-
!Vendor
!Location
!Parts
!Notes
|-
|[https://www.pololu.com/ pololu]
|USA, Worldwide
|Motors, electronics
| -
|-
|[http://mouser.com/ mouser]
|Worldwide
|Motors, electronics
| -
|-
|[https://www.ebay.com/ ebay]
|Worldwide
|Motors, electronics, Fasteners, T-Slots, pulleys, Tubes
| -
|-
|[https://www.aliexpress.com/ aliexpress]
|Worldwide
|Motors, electronics, Fasteners, T-Slots, pulleys, Tubes
| -
|-
|[https://grobotronics.com/ grobotronics]
|GR, EU
|Motors, electronics, Fasteners, T-Slots, pulleys
| -
|-
|[https://www.motedis.com/shop/index.php motedis]
|DE, EU
|T-Slots, Tubes
| -
|-
|[https://uk.misumi-ec.com/ Misumi]
|Worldwide
|T-Slots, Tubes, Fasteners, Pulleys
| -
|-
|[https://www.omc-stepperonline.com/ omc-stepperonline]
|Worldwide
|Stepper motors
| -
|-
|[https://www.fastenal.ca/ fastenal]
|USA
|Fasteners
| -
|-
|[https://www.mcmaster.com/ mcmaster]
|USA
|Fasteners
| -
|-
|[http://www.rs-online.com/ rs]
|Worldwide
|Electronics, fasteners, motors
| -
|-
|[https://8020.net/ 80/20]
|USA
|T-Slots
| -
|-
|[https://www.pcbway.com/ pcbway]
|CN
|PCB fabrication
| -
|-
|[https://www.servocity.com/ servocity]
|USA
|Motors, T-slots, fasteners
|Most of parts are not metric
|-

|}

==Build Sequence==

====Tools & Consumables====
Here are presented tools and consumables about part fabrication, port-processing and assembly process.
Most of the tools are available in every hackerspace, makerspaces, FabLabs etc.

{| class="wikitable"
|-
!Tool/Consumable
!Description
|-
|Drill bits
|2mm for aluminum, 3mm, 4mm and 5mm for plastic
|-
|Drill driver
|For aluminum tube drill hole, 3D printed part
|-
|Sandpaper
|80(dry), 120(dry), 240(dry) and 1000(wet) grit
|-
|Acetone
|For acetone vapor bath
|-
|Hacksaw
|For aluminum Tube
|-
|Square File
|For worm axis, for use on steel
|-
|Precision Knife
|For general use, especially in 3d-Printed parts
|-
|Caliper
|Measuring Range 0-150mm
|-
|Combination Wrenches
|5.5mm, 7mm and 8mm
|-
|Thread-locker
|Like Loctite 271
|-
|Cyano acrylic glue
|Like Loctite 401
|-
|Screw driver
|Number 1 Phillips
|-
|Heat Gun
|For Heat-shrinkables or use a lighter
|-
|Ball-End L-Keys
|Hex 1.5mm, 2mm, 2.5mm, and 3mm
|-
|Soldering iron and consumables
|For cables
|-
|Wire Cutter
|For cables
|-
|Long-Nose Plier
|General purpose
|-
|}

====Parts====
Make sure you have all parts, according to [https://gitlab.com/librespacefoundation/satnogs/satnogs-rotator/blob/master/rotator-bom.ods BOM].

Most of the parts could be fabricated by a FDM 3D-printer. Some parts have only 2D geometry so could be
fabricated by a laser cutter. Other parts have modifications of common(hardware) parts like threaded rods or
aluminum pipes. Also you could find a lot of guides for [https://www.3dhubs.com/knowledge-base/post-processing-fdm-printed-parts post processing for FDM printed parts].

<gallery widths="200" heights="200" perrow="4">
File:C1001.png|C1001, Aluminum Tube 6063 OD40mm TH1.5mm L240mm, 2 variants -1 and -3
File:C1010-3.png|C1010-3, FDM-3Dprinted, Material: ABS, Layer height: 0.4 mm, Perimeters: 2, Top/bottom solid layers: 3, Fill density: 20%, Fill pattern: Honeycomb, Fan speed: [35, 100], No support material
File:C1011-3.png|C1011-3, laser cut in 3mm Acrylic Sheet or in FDM-3Dprinter with same fabrication parameters as C1010-3
File:C1020-1.png|C1020-1, FDM-3Dprinted, Material: ABS, Layer height: 0.4 mm, Perimeters: 2, Top/bottom solid layers: 3, Fill density: 20%, Fill pattern: Honeycomb, Fan speed: [35, 100], No support material, [http://sinkhacks.com/building-acetone-vapor-bath-smoothing-3d-printed-parts/ Smoothing the part with acetone vapor bath]
File:C1021-1.png|C1021-1, FDM-3Dprinted, Material: ABS, Layer height: 0.4 mm, Perimeters: 2, Top/bottom solid layers: 3, Fill density: 20%, Fill pattern: Honeycomb, Fan speed: [35, 100], No support material, [http://sinkhacks.com/building-acetone-vapor-bath-smoothing-3d-printed-parts/ Smoothing the part with acetone vapor bath], [https://community.libre.space/t/version-3-1-stepper-varient-with-v2-controller/1430/5 Imperial variant], [https://community.libre.space/t/help-to-buy-metric-tubing-for-v3-rotator/784/6 tool that helps to build imperial part]
File:C1022-3.png|C1022-3, laser cut in 3mm Acrylic Sheet or in FDM-3Dprinter with same fabrication parameters as C1010-3
File:C1030-1.png|C1030-1, FDM-3Dprinted, Material: ABS, Layer height: 0.4 mm, Perimeters: 2, Top/bottom solid layers: 3, Fill density: 20%, Fill pattern: Honeycomb, Fan speed: [35, 100], No support material
File:C1040-1.png|C1040-1, FDM-3Dprinted, Material: ABS, Layer height: 0.4 mm, Perimeters: 2, Top/bottom solid layers: 3, Fill density: 20%, Fill pattern: Honeycomb, Fan speed: [35, 100], No support material, [https://community.libre.space/t/version-3-1-stepper-varient-with-v2-controller/1430/5 Imperial variant], [https://community.libre.space/t/help-to-buy-metric-tubing-for-v3-rotator/784/6 tool that helps to build imperial part]
File:C1041-1.png|C1041-1, FDM-3Dprinted, Material: ABS, Layer height: 0.4 mm, Perimeters: 2, Top/bottom solid layers: 3, Fill density: 20%, Fill pattern: Honeycomb, Fan speed: [35, 100], No support material, [https://community.libre.space/t/version-3-1-stepper-varient-with-v2-controller/1430/5 Imperial variant], [https://community.libre.space/t/help-to-buy-metric-tubing-for-v3-rotator/784/6 tool that helps to build imperial part]
File:C1042-1.png|C1042-1, laser cut in 3mm Acrylic Sheet or in FDM-3Dprinter with same fabrication parameters as C1010-3
File:C1043-1.png|C1043-1, FDM-3Dprinted, Material: ABS, Layer height: 0.4 mm, Perimeters: 2, Top/bottom solid layers: 3, Fill density: 20%, Fill pattern: Honeycomb, Fan speed: [35, 100], Support material, Brim Width: 2 mm
File:C1050.png|C1050, Aluminum Profile 20x20 B-type slot 6, 2 variants -1 and -5
File:C1060-1.png|C1060-1, M5 Threaded rod A2 stainless steel(304)
File:C1061.png|C1061, 2 variants -5 and -6, FDM-3Dprinted, Material: ABS, Layer height: 0.4 mm, Perimeters: 2, Top/bottom solid layers: 3, Fill density: 20%, Fill pattern: Honeycomb, Fan speed: [35, 100], No support material
File:C1062-1.png|C1062-1, It is recommended to build in laser sintering like Shapeways with White Versatile Plastic (cost ~10€) or like C1030-1 and [http://sinkhacks.com/building-acetone-vapor-bath-smoothing-3d-printed-parts/ Smoothing the part with acetone vapor bath]
File:C1070-1.png|C1070-1, FDM-3Dprinted, Material: ABS, Layer height: 0.4 mm, Perimeters: 2, Top/bottom solid layers: 3, Fill density: 20%, Fill pattern: Honeycomb, Fan speed: [35, 100], No support material
File:C1071-1.png|C1071-1, FDM-3Dprinted, Material: ABS, Layer height: 0.4 mm, Perimeters: 2, Top/bottom solid layers: 3, Fill density: 20%, Fill pattern: Honeycomb, Fan speed: [35, 100], No support material
File:C1072-1.png|C1072-1, FDM-3Dprinted, Material: ABS, Layer height: 0.4 mm, Perimeters: 2, Top/bottom solid layers: 3, Fill density: 20%, Fill pattern: Honeycomb, Fan speed: [35, 100], No support material
File:C1083-1.png|C1083-1, FDM-3Dprinted, Material: ABS, Layer height: 0.4 mm, Perimeters: 2, Top/bottom solid layers: 3, Fill density: 20%, Fill pattern: Honeycomb, Fan speed: [35, 100], No support material
File:C1080-3 2.png|C1080-3, Cover Box bottom part, galvanized steel sheet, thickness 0.5mm
File:C1081-3 2.png|C1081-3, Cover Box top part, galvanized steel sheet, thickness 0.5mm
File:C1082-5.png|C1082-5, Cover Box side part, galvanized steel sheet, thickness 0.5mm
File:C1084-1.png|C1084-1, FDM-3Dprinted, Material: ABS, Layer height: 0.4 mm, Perimeters: 2, Top/bottom solid layers: 3, Fill density: 20%, Fill pattern: Honeycomb, Fan speed: [35, 100], No support material
</gallery>

====Assembly====
Follow the [https://ohai.satnogs.org/project/satnogs-rotator-v3-mechanical-assembly/hardware/ instructions for mechanical assembly] and also you can [https://www.youtube.com/watch?v=D6P9HK23Gmo watch timelapse]
Also, exploded views and instructions are present here.

{{Message|
Prior to Step 8, the rotary encoders must be ready and prior to Step 11 the motor must be mounted in A1070-1. For the rotary encoder assembly look at the next section [https://wiki.satnogs.org/SatNOGS_Rotator_v3#Rotator_Controller Rotator_Controller].}}

Some notes for assembly:

*Resolve collision between of end-stop arm and C1042-1 end-stop mount, [https://community.libre.space/t/rotator-3-1-end-stop-switch-mounting/3463 community post]
*[https://community.libre.space/t/rotator-3-1-worm-gear-issues/1858/7 Running the worm gear] and [https://community.libre.space/t/rotator-3-1-worm-gear-issues/1858/9 lapping the worm gear] to get gear box running smooth
*[https://community.libre.space/t/stepper-motor-bolts-v3-1/3388 Collision between bolts and motor], this issue can be created by using wrong M4 screws(H1100-5) and washers(H1110-1)

<gallery widths="180" heights="180" perrow="4">
File:A1010-1.png|Step 1, Prepare the assembly of worm gear
File:A1011.png|Step 2, Prepare the assembly of worm gear mount, 2 variants -1 and -2 (mirror)
File:A1020-1.png|Step 3, Prepare the assembly of shaft collar for worm wheel
File:A1033-1.png|Step 4, Prepare the encoder gear
File:A1070-1.png|Step 5, Prepare the Motor mount
File:A1060-1.png|Step 6, In case of DC motor configuration
File:A1031-1.png|Step 7, Bearing side without encoder and end-stop mounts
File:A1032-1.png|Step 8, Bearing side with encoder and end-stop mounts
File:A1030.png|Step 9, Prepare symmetric and asymmetric axis, 2 variants -1 and -3
File:A1001-3.png|Step 10, Frame with worm gear mount and A1001-1 assembly
File:A1040.png|Step 11, Rotator module 2 Variants -1 and -3, symmetric and asymetric [[:File:Tip for Step 11 (A1040) -- Note 10 - use of M5 Nuts to attach Drill.jpg|(Assembly Tip - Note 10:Jam two M5 nuts together at end of shaft to easily run gearbox manually)]]
File:A1050-1.png|Step 12, Final step of Antenna Rotator
</gallery>

====Rotator Controller====
The default way of controlling the rotator is to use the [[SatNOGS Rotator Controller]].This works for both stepper motor and DC motor set ups (Note: If you are uing the [https://wiki.satnogs.org/SatNOGS_Rotator_Controller#Encoders the rotary encoders] these will need to be set up). An alternative is to use the [[SatNOGS_Arduino_Uno/CNC_Shield_Based_Rotator_Controller]], whih has been used as a stand alone set up for use with GPredict.

It's also possible to use a standard 3d printing RAMPs 1.4 board as an alternative, though note that these are designed for steppers which may cause extra RF noise. A RAMPs 1.4 [https://github.com/TheSkorm/satnogs-rotator-ramps14 firmware] has been developed.

====Cover Box - Cabling====
Prepare the cover box and install it to antenna rotator with rotator controller and cables.

<gallery widths="200" heights="200" perrow="4">
File:Cover_box_1.JPG| Put the C1080-3 with screws M4 L10 DIN912, C1084-1 and washers M4 DIN125 to the azimuth module. The screw with the Phillips Rounded Head Screws For Sheet Metal, M3,5 X 6,5, DIN 7981,INOX A2, C1082-5 to the C1080-3 and put the C1083-1. Note screw only the middle screw.
File:Power_cable_1.JPG| The power - data cable must be passed inside the azimuth axis. This solution is tested [https://network.satnogs.org/stations/200/ in station 200] without problem.
File:Power_cable_2.JPG| In the other side of power cable must be installed a connector with 4 terminals and waterproof like [https://grobotronics.com/connector-sp-4-pin-male.html Weipu - SP1310/P4I]. Also it is needed to have the female connector for cable that connected to the client. For cheaper solution use a bigger cable to connect the rotator with client and power source.
File:Other_cables_2.JPG|The 3 CAT5e UTP cables are 2x sensors (encoders - end stops) 1x power and data (RS-485). For color code use [https://en.wikipedia.org/wiki/Power_over_Ethernet#Pinouts 802.3af Standards A and B] from the power sourcing equipment perspective.
File:Other_cables_3.JPG|The other cables are for DC motor or stepper motors. In each side of the CAT5e UTP cables must be put a Heat-shrinkable asreferred in [https://gitlab.com/librespacefoundation/satnogs/satnogs-rotator/blob/master/rotator-bom.ods BOM]. Also a Heat-shrinkable must be putin the cable gland in rotator controller for motor cables.
File:Other_cables_1.JPG|Pass all the cables though the hole in the bottom of C1080-3
File:Motor_ferrite_bead.JPG|Add ferrite beads for motor cables, dimensions L25mm and OD 13mm
File:Velcro_for_controller_1.JPG|Add velcro to mount the rotator controller outside the box. Velcro tape specifications: Heavy duty, stick on, max 7Kg, 50mm x 100mm. The tape might be used to mount [https://wiki.satnogs.org/No_rotator client box] in the rotator.
File:Rotator_controller_1.JPG| Cabling management inside the rotator controller. The controller is mounted to the rotator by using a tape as mentioned previously.
File:Rotator controller 2.JPG| Cabling management outside the rotator controller
File:Testing_1.JPG| The rotator is ready for testing, before the final step do not put the C1081-3, in order to most of components must be accessible
File:Testing 2.JPG| The final step. If everything is working properly, must be put the C1081-3 by using sheet metal screws as mentioned previously. In this step if the holes of C1081-3 are not aligned with the holes of the other two parts, C1082-5 and C1080-3, drill new holes and screw them, take a look in [https://gitlab.com/librespacefoundation/satnogs/satnogs-rotator/issues/73 issue 73]. Put stickers!!!!!!

</gallery>

====Testing====
You are ready! Proceed with [https://wiki.satnogs.org/SatNOGS_Rotator_Controller#Troubleshooting_hints testing].

====Heading Calibration====
The heading calibration is a manual process:

*Power the rotator, it starts moving in order to find the home position, to find the end-stops
*Remove the power from the rotator, the rotator is in home position
*Install the rotator to vertical axis by using U-Bolt clamps
*The azimuth axis it must be heading to the North, this is achieved by using a compass (e.g. from smart phone)
*Secure the rotator in the vertical axis
*Install the elevation axis with the same process, now the zero elevation is achieved by using a pocket level
*Secure the elevation axis
*In the case of wrong rotation:
**For stepper motors swap a pair of two stepper motor cables ([https://gitlab.com/librespacefoundation/satnogs/satnogs-rotator-firmware/issues/15 it exists an open issue to be done by a command])
**For DC motors, [https://gitlab.com/librespacefoundation/satnogs/satnogs-rotator-firmware/commit/961fb696536e35642f2b7064cc3c64676ebebb17 change the sign of encoder reading], it is a hacky method but it would be resolved by [https://gitlab.com/librespacefoundation/satnogs/satnogs-rotator-firmware/issues/15 this issue]

====Counterweight for Antenna====
It is necessary to balance the antenna in elevation and azimuth axis in order to not wear the gear box of rotator. In elevation axis would be done either by using back mounted antennas or by mounting the center of antenna mass in the mast. For a back mounted antenna, it is necessary to use counter-balance weights. An idea is to use weights that is used for training (it's cheap). The parts that used to mount weights to [https://www.wimo.com/en/x-quad X-quad antenna] are this [https://gitlab.com/librespacefoundation/satnogs/satnogs-hardware-misc/-/tree/master/mount-counterweight 3D printing part], a square aluminum profile 15x15 mm, weights with inner hole D28mm and M5 hex nuts DIN934 with M5 screws DIN912 L12 stainless steel to lock the weights in specific distance. Another way to [https://community.libre.space/t/quartapounds-satnogs-rotator-v3-1/3453/57 balance the antenna].

[[File:Counter-weight.jpg|thumb|center|800x420px|alt=|Counterweights]]

==Mechanical Analysis [WIP]==

====Brake Torque====
The greatest force the tracker needs to withstand is the force created by strong wind. The worst case is when one antenna is elevated at 90 degs, facing the direction of the wind. We based our calculations on an [http://k7nv.com/notebook/topics/windload.html article] found online after comparing it to others. We “translated” the second table in metric (because we don’t understand imperial and because we needed same units system in our calculations)

{| class="wikitable"
|-
!Method
!Wind Zone(km/h)
!Height (m)
!Pressure(N/m^2)
|-
|EIA-222-C
|160
|N/A
|1280

|-
|EIA-222-F
|128
|14
|1260

|-
|EIA-222-F
|128
|21
|1390

|-
|EIA-222-F
|128
|30
|1500

|-
|UBC'97
|128
|14
|1290

|-
|UBC'97
|128
|21
|1160

|-
|UBC'97
|128
|21
|1390

|-
|UBC'97
|128
|30
|1260

|-
|UBC'97
|128
|42
|990

|-
|UBC'97
|128
|42
|1360

|-
|Generic Formula
|150
|N/A
|1270

|}

and we applied the worst case model (EIA-222-F) in 3 different antennas: in the biggest one of our designs, and in two others, for which we obtained data from [http://download.qrz.ru/pub/hamradio/antenna/rotators/G-800SA_1000SA.pdf yaesu G800 rotator manual at page 3]. We assumed that antennas are mounted in 1m away from the azimuth axis. For our antenna with 2m length (actual, not wavelength), made by 2cm square tube, the generated torque was ≈600Kg*cm. For the 144MHz 10-elements Yagi from the article is ≈6000Kg*cm and for the third 430MHz, 12-elements Yagi is ≈1800Kg*cm

====Moment of inertia====
Now for the moment of inertia: (for all installation methods we assumed that antennas are counterbalanced in the elevation axis) the worst case scenario here is to use two 3kg (our designs are less than 1kg) back mounted yagis with 3kg counterbalances both mounted in 0.75m away from azimuth axis. The torque you need in order to accelerate this system from ω=0deg/s angular velocity to ω=5deg/s (the math about angular velocity is below) in one second is about 60kg*cm.

Note: we suppose that the mass of antennas is near to the altitude axis, so the torque of this axis that is needed to accelerate is approximately 0.

*M1: torque of Azimuth axis
*L: length of center of mass of antennas from azimuth axis (0.75m)
*m: mass of antennas and of counterweight (3kg + 3kg = 6kg)
*I: moment inertia
*a: angular acceleration of azimuth axis 5deg/s^2
*I = I1 + I2 = m*L^2 + m*L^2 = 2*m*L^2 = 6.75 kg*m^2
*M1 = I*a = 6.75kgm^2 * 0.087rad/s^2 = 0.58 Nm = 5.8 kgm = 58 kgcm

====Angular velocity====
(How well do you remember trigonometry?)For the angular velocity max needed in altitude axis the things are straightforward. The closer is the satellite the larger the velocity. According to the wikipedia article about LEO, the lowest height limit is 160 km and the speed unit to orbit earth in this altitude is 7,8 km/s. As a result, maximum velocity in ALT axis is 2,8 deg/s. In ALT AZ rotator design there is a well known limitation: the closer something passes near zenith the biggest gets the velocity of the AZ axis. Therefore, we have analyzed this problem to figure out the optimal velocity and how high we are allowed to track a target in relation to AZ velocity. The picture below illustrates a ground station B which tracks a satellite Γ in X degrees altitude. The satellite velocity at this point is vertical to the screen (page) plane.

[[File:Anglular_velocity.png|thumb|center|800x420px|alt=|Angular Velocity]]

The equations that lead to maximum altitude at which we can track in relation to AZ angular velocity are

*ω : angular velocity of AZ DOF in rad/s
*H = ΑΕ + ΕΓ : Minimum Height of LEO, 160 km
*R = ΑΕ : Radius of Earth, 6500 km
*u : linear velocity of satellite that rotates in 160km height is 7.8 km/s
*ΒΔ = u / ω : ΒΔ in km
*α = atan(ΒΔ / R)
*δ = π - α
*γ = asin( sqrt(R^2+ΒΔ^2) * sin(δ) / (H+R) )
*ά = π - δ - γ
*ΓΔ = (H+R) * sin(ά) / sin(δ)
*χ = atan(ΓΔ / ΒΔ)

Below you can see the plot of the equations mentioned above, where horizontal axis represents angular velocity (ω) in deg/s and vertical axis shows the max track altitude (χ) for lower bound of LEO.

[[File:Anglular_velocity_plot.png|thumb|center|800x420px|alt=|Angular Velocity Plot]]

After studying this diagram, we came up to the conclusion that an angular velocity of 5 deg/s is adequate. For this decision, we took into consideration the main lobe of antenna (Δ3db) which in most situations is about 20 deg.

====Pulleys/Belts/Gearing====
Horizontal distance between pulleys (P1, P2) is 58mm.
Vertical distance between pulleys (P1, P2) is w = 9.5mm.

Pulleys and Belt are GT2, 2mm pitch.
Belt width, 6mm.
Belt thickness, 1.38mm (0.76 tooth).

Wrap angle in both pulleys is larger than 60deg.
At least 6 teeth in contact with the pulley at any given time.
In practice that means you want a minimum of a 12 tooth pulley, and usually try to get at least 18 teeth.

Outer Diameter of pulleys:

P(T) | OD(mm) 
16 | 10.2 
20 | 12.7 
36 | 22.9 
40 | 25.5 

Belt calculation (according to calculator):

Ratio | P1(T) | P2(T) | Belt(T) | L(mm) 
2.25|16|36|85/86|58.65/59.66 
1.8|20|36|86/87/88|57.78/58.78/59.78 
2.5|16|40|87/88|58.5/59.5 
2|20|40|89/90|58.65/59.66 

Motor Maximun no-load speed, 200RPM = 1200deg/s
Motor Maximum stall-torue, 1.2Nm

[[File:Motor_perfomance_graph.png|thumb|center|800x420px|alt=|Angular Velocity]]

Position of idler do not care, or min 1.3*P1, max 1.5*P1 (for 20T, ~16mm/~20mm).

Belt gear selection:

*20/36 with 1.8 ratio and 86T/172mm belt without idler
*20/40 with 2 ratio and 90T/190mm belt with idler

To calculate Deflection force, (page T-31, sdp - design-guidelines)

*Y = 2.05, Tst = 1.3kg
*span length, t = 57.64mm
*Belt pitch length, L = 180mm
*Fd,min =
*Fd,max =
*2.8kg Working Tension [shapeoko - Belts and Pulleys](https://www.shapeoko.com/wiki/index.php/Belts_and_Pulleys#Tensile_Cord_Materials)

P3 
/ \ 
P1 P2 
| 
P4-P5 

*Determination of design load

According to perfomance graph of DC motor, the optimal output power is Tm = 0.6Nm with efficiency of 0.2 and 100RPM = 600deg/s.
Select a service factor of 1.5 (service factors between 1.5 and 2.0 are generally recommended when
designing small pitch synchronous drives).
Tpeak = SF*Tm = 1.5*0.6 = 0.9Nm

*Choice of belt pitch

Due to backslash and accuracy in both directions of movements and volume constrains, we choose GT2, pitch 2mm.

*Check belt pitch selection based on individual graphs

Due to Tpeak = 0.9Nm No-load speed,(Speed of fastest shaft) = 100RPM = 600deg/s
GT2 pitch 2mm belt is the better solution for our application.

*Determine speed ratio

Speed ratio 1.8-2.25 according to specification of output rotation speed of 5deg/s.

*Check belt speed

V(m/s) = 0.0000524 x pulley PD (mm) x pulley rpm = 0.066548m/s
Belt speeds up to 6,500 fpm (33.02 m/s) do not require special pulleys.

*Determine belt length

Table 'Belt calculation (according to calculator)'
Teeth in mesh: 9

*Determine the belt width

From Table 43
torque = 0.17Nm
Length Correction Factor = 0.9
width multiplier = 1.00
torque*Length Correction Factor*width multiplier = 0.17*0.9*1.00 = 0.153Nm
Teeth in mesh: 9
Tpeak = 0.9Nm, so belt width is nice for our application

*Check the number of teeth in mesh

Teeth in mesh: 9 according to calculator

*Determine proper belt installation tension

SECTION 10, on page T50, look at 'To calculate Deflection force, (page T-31, sdp - design-guidelines)'

*Y = 2.05, Tst = 0.812*DQ/d + mS^2 = 12.8lb + 0 = 5.8kg
*DQ = Tpeak = 0.9Nm = 7.9lb-in
*d = 12.7mm = 0.5in
*S = (0.5*100/3.82)/1000 = 0.0131ft/min
*m = 0.039
*span length, t = sqrt(CD^2 - (PD-pd/2)^2) = 57.64mm
*Belt pitch length, L = 180mm
*t/L = 0.32
*Fd,min = 0.8lb = 0.36kg
*Fd,max = 0.9lb = 0.41kg

*Safety factor 1.5

*P2 timing pulley torque - Maximum radial load of timing belt ball bearing 625zz

Tpeak = 0.9Nm
TorqueP2 = 2*0.9Nm = 1.8Nm, PDp2 = 25.5mm
Radial static load of 625ZZ is 0.38kN
T-39

*Maximum thrust load of timing belt ball bearing 625zz

*Maximum radial and thrust load of output ball bearings 6008zz

Calculate or evaluate correct loads for deep groove ball bearings
radial static load = 11.6kN
thrust static load = 0.7*11.6kN = 8.12kN
This type of construction permits the bearings to support relatively high thrust load in either direction.
In fact the thrust load capacity is about 70% of the radial load capacity. A ball bearing primarily designed
to support radial load can also support high thrust load; because only few balls carry the radial load,
whereas all the balls can withstand the thrust load.

*Maximum self-locking or back-drivable torque of gear box (according to more weak component)

It necessary to achieve [specs](https://community.libre.space/t/satnogs-rotator-version-3/226), 60Nm (6Kg in 1 meter)

*Nominal torque of drivable torque of gear box (according to more weak component) and maximum rotational speed of gear box

Notes:

*[https://sdp-si.com/eStore/CenterDistanceDesigner sdp distance calculator]
*[http://www.ebay.com/itm/2GT-Timing-Belt-L-172-232-240-244-640-810-GT2-Belts-closed-loop-5pcs-lot-/221977955532?var=&hash=item33aeeacccc:m:me5GvSt_amrm6RWT03Ut4JA belt GT2-6mm wide, 172mm]
*[https://www.ebay.com/itm/2GT-GT2-synchronous-Timing-belt-Perimeter-98-194mm-width-6-9mm-Cogged-close-loop/222574382655?ssPageName=STRK%3AMEBIDX%3AIT&var=521434616407&_trksid=p2060353.m2749.l2649 belt GT2-6mm wide, 180mm]
*[http://www.ebay.com/itm/5pcs-Timing-Pulley-GT2-Idler-16-20T-gear-Bearing-Reprap-6mm-Belt-3-5mm-Bore-3D-/132195520937?var=&hash=item1ec77791a9:m:mljSYBViBlKOgXr3Gy-u0Tg idler pulley, no-teeth-ID3mm-OD18mm]
*[http://www.brecoflex.com/products/pulleys/design-guidelines/ brecoflex - design-guidelines]
*[http://www.shreegeeimpex.com/TECH_DATA_PAG/idlers_ten.htm shreegeeimpex - design-guidelines]
*[http://www.sdp-si.com/PDFS/Technical-Section-Timing.pdf sdp - design-guidelines]

====Motor Specification====

General Specification about motors. The voltage and current consumption also it depends from the motor controller which is (maybe) different
from [https://wiki.satnogs.org/SatNOGS_Rotator_Controller SatNOGS Rotator Controller].

{| class="wikitable"
|-
!Specification
!Value
|-
|Min-Max Stall Torque (Nm)
|0.4 - 1.5
|-
|Min-Max Speed (RPM)
|100 - 200
|-
|Size (mm) (LxWxH)
|47x42x64
|-
|}

<gallery widths="200" heights="200" perrow="4">
File:Motor mount dimensions.png|Motor mount dimensions
File:Max motor height.png|Maximum Motor Height
</gallery>

====Worm Gear Box Calculations====

*Gear ratio: i12 = 30
*Angle between axis of gears: δ = 90 deg
*Number of threads in worm: If i12 >= 30 then z1 = 1
*Number of teeth in worm wheel: z2 = i12*z1 = 30
*Center distance: initial case a = 45.5 mm
*Worm reference diameter: AGMA d01>= 11.5*(a/25.4)^0.875 = 19.15 mm, so d01 = 19.5mm
*Worm wheel reference: d02 = 2*a - d01 = 71.5 mm
*Axial module: ms = d02/z2 = 2.38 , so ms = 2.5

Recalculate d02, a with new axial module

*d02 = z2*ms = 75mm, a = (d02+d01)/2 = 47.25mm
*Axial pitch: ts = π*ms = 7.854mm
*Reference lead angle: γ0 = atan(d02/(i12*d01)) = 7.3 deg
*Worm tip diameter: dk1 = d01 + 2*hk = 24.5mm
**Worm teeth reference addendum in axial section: hk = hk* *ms = 2.5mm
**Worm tooth reference addendum coefficient: hk* = 1
*Worm root diameter: df1 = d01 - 2*hf = 13.5mm
**Worm tooth reference dedendum: hf = hf* _ms = 1.2_ms = 3mm
**Dedendum coefficient: hf* = 1.2
*Worm length: L = 2.5_ms_sqrt(z2+2) = 35.36mm
*Worm tooth thickness: smx1 = smx1* * ts = 3.927mm
**Tooth thickness coefficient: smx1* = 0.5
*Normal pressure angle: aon = 20 deg
*Worm wheel throat diameter: dk2 = d02+2*hk = 80mm
*Worm wheel root diameter: df2 = d02 - 2*hf = 69mm
*Worm wheel outside diameter: de2 = dk2 + 2*mx = 83.5mm
**Worm wheel tooth external addendum: mx = n*ms, 0.4<=n<=1.5
*Effective worm wheel face width: b2H,max = sqrt((2_a - df2)^2 - (2_a - de2)^2) = 23mm

[[Category:Build]]
[[Category:Hardware]]
[[Category:Rotator]]

Omnidirectional Station How To

2021-10-26T11:10:13Z

Kerel+satnogs: /* Installing Image on Linux/Windows/MacOS (using Rasperry Pi Imager) */ Fix Raspberry Pi Imager link

[[File:Omnidirectional VHF Turnstile Antenna.jpg|alt=VHF Turnstile Antenna|thumb|VHF Turnstile antenna, [https://network.satnogs.org/stations/23/ SatNOGS Station 23]]]
This How-To is written to get you quickly receiving satellite data with an Omnidirectional antenna (an antenna that does not move).

==Prerequisites/Background==
I'm assuming that you are a bit familiar with amateur radio, or linux in general, or you already have a Raspberry Pi.

===Expectation Management===
First off, I'd like to set some expectations around a SatNOGS station with an omnidirectional antenna. Yes, you will be able to hear satellites, Morse code beacons, maybe even some voice contacts on a FM transponder. But for CubeSats with 1 watt transmitters at 9600 baud, it's going to be really difficult to actually decode any data with an omni antenna. You'll definitely see squiggly lines on the waterfall plot, but demodulating the signal and extracting satellite telemetry is going to be pretty difficult.

The only way to get more signal is a better antenna. And a better antenna with more gain is going to be more directional, which means you will need a way to point that antenna at the satellite, and this How-To just got a lot more complicated. So we're not going there.

A better preamp helps a bit, see the LNA section below.

===Hardware Required===
This is a list of the hardware for indoor/testing purposes:

*Raspberry Pi
**Power supply + cable (see note below)
**Up to 16 GB Micro SD card
**Ethernet cable
*RTL SDR Blog v3 dongle
*Various short lengths of coax
*Preamp/LNA - Or not if your coax is short, see LNA section below
*Omnidirectional antenna - just a dual mag-mount on a cookie sheet will work OK for stronger satellites

==Setting up the Raspberry Pi==
I chose the [https://www.raspberrypi.org/products/raspberry-pi-3-model-b/ Raspberry Pi 3 Model B] for my station. SatNOGS is known to work on the RPi 3B, 3B+ and 4 models.

===Downloading/Writing the SD image===
The SatNOGS team has done a great job creating a Raspbian image with all the required software.
The latest download is given in the [[Raspberry_Pi#Download|Download section]].

====Installing Image on Linux====
* Unzip the downloaded file:
<pre>unzip artifacts.zip</pre>
* Figure out which device is the SD card. SD cards are usually start with mmcblk.
<pre>sudo lsblk</pre>
* Write the image. This will take a while. Make sure you don't overwrite your host OS:
<pre>sudo dd if=<latest_image_date>-Raspbian-SatNOGS-lite.img of=/dev/mmcblk0</pre>

====Installing Image on Linux/Windows/MacOS (using Rasperry Pi Imager)====
{{Warning|WARNING: This section was recently added. Please test and if it works, remove this banner.}}

This section describes the installation of installing the previously downloaded image to an SD card using the cross-platform Raspberry Pi Imager. [https://www.raspberrypi.com/documentation/computers/getting-started.html#using-raspberry-pi-imager|This guides] explains the process using this tool in more detail.

* Download the latest version of [https://www.raspberrypi.com/software/ Raspberry Pi Imager]
* Connect an SD card reader with the SD card inside
* Open Raspberry Pi Imager and choose the previously downloaded image from "Choose OS > Use custom > artifacts.zip"
* Review your selections and click '''Write''' button to begin writing data to the SD card.

===Power notes===
Thinking I could save a few bucks, I used a no-name generic 2.4 amp "tablet" USB power supply I got as a freebie, and a micro-USB cable I use for charging my phone. What a mistake! The Micro-USB cable wire gauge was too small, so there was too much voltage drop on the cable, so the Raspberry Pi reported power problems every time it was doing anything.

Power problems are indicated by either a lightning bolt in the upper right of the monitor, or the red power LED flashes on the board itself. If The Raspberry Pi processor itself is pretty forgiving of power droops because it runs at 3.3 volts. But the 5v USB ports are directly tied to input power, so undervoltage conditions will cause problems for USB devices, such as the RTL SDR dongle.

==Software Configuration==
===Creating a SatNOGS Account===
There are several different websites to be aware of. Most of our websites use a unified login provided by Auth0, so when you create an account on one of these sites it will work across all the others as well.

*[https://network.satnogs.org/ Network]: for registering your station and adding data to the network.
*[https://db.satnogs.org/ Database]: for all data on satellites and its transmitters.
*[https://community.libre.space Forums]: for questions and discussions.
*[https://wiki.satnogs.org/ Wiki]: this wiki for all kinds of documentation.

===Registering the station===
You can add your new ground station [https://network.satnogs.org/stations/edit/ here]. When following the link it will ask you to login. Either use your existing account or register a new one.

The following information is required:
* Station name, e.g. "Athens3-UHF"
* Location:
** Latitude (e.g., 38.0169)
** Longitude (e.g., 23.7312)
** Altitude above WGS84 in Meters (e.g., 20)
* At least one antenna.
** Click '''New antenna'''
** Choose the type (e.g. Turnstile)
** Add a range (e.g. VHF or UHF)
** Press '''Save changes'''

Fill out the form, click '''Submit''' and your station will be added to the Network. You can leave the other settings unchanged for now.

To help your fellow operators please consider placing the following information into the "Description" field for your station: Antenna gain and location, preamp info (if any), SDR device, some kind of contact info perhaps [[Get_In_Touch#Chat_with_us_on_our_Matrix_room |irc/matrix]] or [https://community.libre.space/ community forum] username or email address.

===Booting and Configuring Raspbian===
{{Warning|WARNING: This section describes steps which are not always required. When using ssh for setup, the steps might be different. This section should be updated to reflect this. }}

After you have the image burned onto a Micro-SD card, boot it! I would recommend hooking up a keyboard and HDMI monitor, you can watch the boot process. If it doesn't boot at all, double check that you wrote the SatNOGS Raspbian image correctly.

After a successful boot, log in with username '''pi''' and password '''raspberry'''

#Change your password! '''passwd'''
#Run '''sudo raspi-config''' to set up the base OS. ''Tab'' switches between the options and ''select''.
##4 Localisation Options: I1 Change Locale: en_US.UTF-8 UTF-8
##4 Localisation Options: I2 Change Timezone: None of the above: UTC
##4 Localisation Options: I3 Change Keyboard Layout:
##7 Advanced Options: A1 Expand Filesystem This will expand the ~2GB Micro-SD card partition to fill the entire SD card.

The Raspberry Pi needs to reboot to expand the filesystem, so do this now. It might take a while. '''sudo reboot''

====Disabling WiFi and Bluetooth====
{{Message|INFO: This step can be skipped. }}
To disable WiFi and Bluetooth, edit the /boot/config.txt file, and add the following lines at the bottom:

# Disable WiFi and Bluetooth
dtoverlay=pi3-disable-wifi
dtoverlay=pi3-disable-bt

Then reboot again. To make sure that it worked, run '''ifconfig''' and make sure that ''wlan0'' isn't listed. I'm not sure how to tell if bluetooth is turned off.

Note: Newer versions of Raspbian may require the following lines instead of the above.

# Disable WiFi and Bluetooth
dtoverlay=disable-wifi
dtoverlay=disable-bt

====Additional software====
I like to install this additional software with '''sudo apt install bmon''' ...

*bmon - a graphical network usage analyzer.
*vnstat - keeps track of your bandwidth usage
*vim - the world's best text editor ;)
*irssi - a terminal IRC client, for chatting on the #satnogs IRC channel

If you can't tell by now, I'm always a big fan of rebooting. It certainly doesn't take that long... '''sudo reboot'''

===Update the SatNOGS Client Software to latest version===
Once you have the SatNOGS OS image installed and running you should [https://wiki.satnogs.org/SatNOGS_Client_Setup#Updating_SatNOGS_Client_Software| Update the SatNOGS Client Software].

===Configuring the satnogs-client===
Now you can configure your new SatNOGS station. Plug in your RTL-SDR if you haven't already.

====Basic Configuration====
Then the actual configuration of the station:

#Run '''sudo satnogs-setup''' again.
#Use the up/down and TAB keys to navigate, and Enter to select an option.
#Basic Configuration:
##SATNOGS_API_TOKEN: After logging in to network.satnogs.org, this is in the upper right under "API Key" [no longer exsists? Add direct link]
##SATNOGS_SOAPY_RX_DEVICE: driver=rtlsdr
##SATNOGS_RX_SAMP_RATE: 2.048e6
##SATNOGS_RX_GAIN: Refer "Setting the gain" section below.
##SATNOGS_STATION_ELEV: station elevation in meters
##SATNOGS_STATION_ID: The ID number of your station.
##SATNOGS_STATION_LAT and LON: Latitude and Longitude in decimal degrees

Then back to the main menu and ''Apply'' to save the configuration. Ansible will run and update the system. If you want to quit, just keep pressing cancel to exit.

====Setting the gain====
The next step is to set the gain on the RTL SDR. The aim here (in the majority of cases) is to set the gain of your station to maximise sensitivity (best noise figure), but without limiting the available dynamic range of your station due to your local noise floor. This can be achieved in a fairly simple manner, by watching the level of the receivers noise floor as you slowly increase the receiver gain. At some point the noise floor will start to rise - at this point increasing the gain any further will of no use - you will only increase the noise level, and eat into your receiver's available dynamic range (for a RTLSDR, theoretically only 48 dB).

There may be situations where strong local interferers may require the use of a lower gain setting to avoid intermodulation products appearing in the passband, though these cases would be better solved with a suitable bandpass filter somewhere in the receive chain.

First, it is good to know the available gain range of your SDR. This can be accomplished by running <code>SoapySDRUtil --probe</code>, which provides a considerable amount of information about the connected SDR:
pi@satnogs:~ $ SoapySDRUtil --probe
######################################################
## Soapy SDR -- the SDR abstraction library
######################################################

Probe device

Found Rafael Micro R820T tuner
[INFO] [UHD] linux; GNU C++ version 8.2.0; Boost_106700; UHD_3.13.1.0-3
Found Rafael Micro R820T tuner

----------------------------------------------------
-- Device identification
----------------------------------------------------
driver=RTLSDR
hardware=RTLSDR
origin=<nowiki>https://github.com/pothosware/SoapyRTLSDR</nowiki>
rtl=0

----------------------------------------------------
-- Peripheral summary
----------------------------------------------------
Channels: 1 Rx, 0 Tx
Timestamps: NO
Other Settings:
* Direct Sampling - RTL-SDR Direct Sampling Mode
[key=direct_samp, default=0, type=string, options=(0, 1, 2)]
* Offset Tune - RTL-SDR Offset Tuning Mode
[key=offset_tune, default=false, type=bool]
* I/Q Swap - RTL-SDR I/Q Swap Mode
[key=iq_swap, default=false, type=bool]

----------------------------------------------------
-- RX Channel 0
----------------------------------------------------
Full-duplex: YES
Supports AGC: YES
Stream formats: CS8, CS16, CF32
Native format: CS8 [full-scale=128]
Stream args:
* Buffer Size - Number of bytes per buffer, multiples of 512 only.
[key=bufflen, units=bytes, default=262144, type=int]
* Ring buffers - Number of buffers in the ring.
[key=buffers, units=buffers, default=15, type=int]
* Async buffers - Number of async usb buffers (advanced).
[key=asyncBuffs, units=buffers, default=0, type=int]
Antennas: RX
Full gain range: [0, 49.6] dB
TUNER gain range: [0, 49.6] dB
Full freq range: [23.999, 1764] MHz
RF freq range: [24, 1764] MHz
CORR freq range: [-0.001, 0.001] MHz
Sample rates: 0.25, 1.024, 1.536, 1.792, 1.92, 2.048, 2.16, 2.56, 2.88, 3.2 MSps
The above output is for a RTLSDR, and we can see that there is information on the 'Full gain range', and 'TUNER' gain. The Full gain setting is an 'abstracted' gain range, which in this case just directly links to the 'TUNER' gain, as that is the only gain setting presented by the RTLSDR driver. Other SDRs (e.g. AirSpy) may present more gain controls. Anyway, we can see that the gain range is 0 through 49.6 dB. It's quite possible that there are only discrete gain steps within this range (and this is very true for the RTLSDR), but SoapySDR will hide that from us and automatically use the nearest valid setting.

Next up, we want a way of seeing a live spectrum from the SDR. This might be difficult, especially if you're just gone and mounted a RTLSDR in a metal box up a pole! Well, SoapySDR comes to the rescue again with SoapySDR Server - this allows us to serve up the SDR on the network, and access it with a client.

Note: SoapySDR Server is not currently installed by default. It can be installed by running the commands:
$ sudo apt-get install soapyremote-server
By default, SoapySDR Server may be configured to startup on boot. We probably don't want this, so run the following commands to ensure it is stopped, and will not startup on boot:
$ sudo systemctl stop soapyremote-server
$ sudo systemctl disable soapyremote-server

(These commands may result in errors indicating that the server wasn't running and/or enabled. This is OK!

[https://cubicsdr.com/ CubicSDR] is a good cross-platform client that can connect to a SoapySDR Server, and you can [https://github.com/cjcliffe/CubicSDR/releases download the latest release by clicking here].

On the RPi, you can manually start SoapySDR Server by running: <code>SoapySDRServer --bind="0.0.0.0:55132"</code> Leave this running.

Note: If you need to use the Bias-T option of an RTLSDR, you will need to activate this manually prior to running SoapySDRServer. This can be accomplished by [[Software Defined Radio#Using RTL-SDR.com V3 Dongle.27s Bias-T Power Supply|compiling the rtl_biast utility]], and running it with <code>./rtl_biast -b 1</code> . ('''NOTE: This advice may be outdated - need to confirm how to set the RTLSDRs bias on more recent SoapySDR versions)'''

Open up CubicSDR on another computer, on the same network as your SatNOGS station. It will pop up a window asking you to select a SDR device. With any luck, it will have auto-detected your SoapySDR Server, and it will show up in the 'Local Net' list. If not, you will need to select 'Remote', click 'Add', and then enter the IP address of your station. You should then have a SDR showing up in the list.
[[File:Screen Shot 2020-03-19 at 10.41.52 pm.png|alt=CubicSDR SDR Devices List|none|thumb|600x600px|CubicSDR SDR Devices List]]
You should now be able to click 'Start', and end up with a waterfall display. If the waterfall appears to glitch, or show a 'lumpy' pattern near the centre of the display, then this indicates packet loss between the SatNOGS station and your client. Try and connect via a direct LAN connection if possible.
In the settings menu of CubicSDR, disable "Automatic Gain" if it is set. This will allow manual control over the gain settings via sliders that will show up at the top left of the window.
[[File:CubicSDR Main Window.png|alt=CubicSDR Main Window (Annotated)|none|thumb|900x900px|CubicSDR Main Window (Annotated)]]
The above Figure shows the CubicSDR window, with the spectrum area, frequency selection, and gain settings annotated. Set the frequency to something suitable for your station. For example, if you are setting up a 70cm station, set a frequency of 437 MHz (437000000 Hz). For a 2m station, try 146 MHz.
Drag the gain slider so that the gain (visible at the bottom of the slider) is set to zero. Then, slowly drag it up until you see the noise floor start to rise. The gain at which this occurs is the gain you should set in SATNOGS_RF_GAIN.

To set the gain in satnogs go back to the RPI and stop the soapy remote server with ctrl-c. Run satnogs-setup, open the 'Advanced' menu, then the Radio settings. Set the gain in the SATNOGS_RF_GAIN variable.
[[File:SATNOGS RF GAIN.png|center|frame|Setting SATNOGS_RF_GAIN]]

Some SDRs may present more than one gain slider. In these situations, you will need to configure SatNOGS with each gain set individually. [[Software Defined Radio#E4000 Tuner Gain Settings|Refer here]] for more information on how to do this.

As an example, the following figure shows the noise floor observed on a station with a RTLSDR and a ~25dB masthead preamplifier, as gain levels on the RTLSDR are increased:
[[File:RTLSDR Noise Floor Variation with Gain Adjustment.png|alt=RTLSDR Noise Floor Variation with Gain Adjustment|none|thumb|900x900px|RTLSDR Noise Floor Variation with Gain Adjustment]]
We can see that between 0 db and 20 dB of gain there is essentially no change in the noise floor - this indicates the receive system is limited by the noise figure of the RTLSDR. As the gain increases through 30 dB, the noise floor starts to lift, indicating that we are now most likely limited by either the noise figure of the preamplifier, or the local noise environment. Any increase in gain past this point just results in reduction of the available receiver dynamic range.

CubicSDR DOES NOT autorange its waterfall, in contrast, SatNOGS DOES autorange its waterfall. When you adjust the gain in CubicSDR the waterfall background will dramatically change, but when you adjust the gain in SatNOGS the waterfall background will not change color. See the web page documenting autoranging waterfalls:

https://docs.satnogs.org/projects/satnogs-client/en/stable/userguide.html#satnogs-waterfall-autorange

'''Important Note: While CubicSDR is connected to the SDR, your SatNOGS ground station cannot run observations! Make sure to close CubicSDR when you have finished setting the gain.'''

===Hardware Configuration===
Basic hardware configuration is Antenna > Short coax > LNA > Coax > RTL SDR -> Raspberry Pi.

===LNA===
The way to measure the performance of an antenna is using a figure of merit called the Antenna gain-to-noise-temperature (G/T). It's a positive unitless number, higher the better.

G/T is comprised of antenna gain (in dB) on the top, and the system noise temperature (in Kelvins) on the bottom. There's a lot of somewhat-hard math involved, but here's the bottom line: to make your system perform better, you either need to increase the antenna gain or decrease the system noise temp. [https://en.wikipedia.org/wiki/Antenna_gain-to-noise-temperature Wikipedia]

Increasing the antenna gain is difficult, only because we decided on an omnidirectional antenna as the basis for this How-To. Omnidirectional antennas top out at maybe 4-6 dBi gain or so, and that's just from pushing the radiation pattern up to the sky away from the ground. Any more gain than that and it's not an omni antenna; it's got a direction that the antenna needs to be pointed in. And we want to stay away from pointing antennas for now.

Reducing the system temperature is the the way forward then. The RTL-SDR dongle has a noise figure of 6dB or so, depending on frequency, which is pretty horrible. But it turns out that the system noise temperature is largely determined by the first device in the receive chain. Since we can't change the antenna, adding a low-noise amplifier helps quite a bit. See this [https://www.youtube.com/watch?v=snifc_x_2sE youtube video] from Adam 9A4QV on how a LNA helps. (Also check out his other videos about the RTL SDR dongle, and SDR in general)

More info on SDR noise figures:

*[https://gitlab.com/librespacefoundation/sdrmakerspace/sdreval/-/raw/master/Report/pdf/Evaluation_of_SDR_Boards-1.0.pdf Evaluation of SDR Boards and Toolchains] from the [https://sdrmaker.space/ SDR Makerspace]

More info on noise and preamps:

*[https://en.wikipedia.org/wiki/Noise_temperature System noise from wikipedia], pretty high-level
*[https://www.rtl-sdr.com/tutorial-on-properly-positioning-a-preamp-lna-in-a-radio-system/ Where to put an LNA], from rtl-sdr.com
*[[SPF1589 LNA measurements|SPF5189 LNA measurements]]

Adding a LNA can also add its own set of problems, in that it may amplify strong local signals which may overload your SDR. When adding a LNA, you will likely need to back off the gain on your SDR to avoid this. It's also possible that the strong local signals may cause distortion to occur in the LNA itself, in which case you should consider the use of a filter between the LNA and the antenna. Some example products:

*If you are experiencing issues with FM broadcast stations, a [https://www.rtl-sdr.com/rtl-sdr-com-broadcast-fm-band-stop-filter-88-108-mhz-reject-now-for-sale/ FM band-stop filter] may help.
*[https://www.minikits.com.au/electronic-kits/rf-amplifiers/rf-preamplifiers MiniKits masthead preamps] include fairly low-loss bandpass filters for their target bands (2m, 70cm).

All filters will have some inherent loss, which adds to the system noise figure (or temperature, as discussed above), but this is a compromise that may need to be made to avoid distortion issues.

Finally, using a LNA near the antenna means that we can accept some losses from a long coaxial cable run between the LNA and the receiver, allowing us to situate the antenna away from sources of local noise that may impact overall performance.

As briefly discussed above, it's the first device in the receive chain which dominates the overall system noise temperature (or noise figure). In brief, as long as the losses in the coaxial cable are less than the gain of the LNA, your overall system noise figure won't degrade too much. As an example a 20m run of RG58 has a loss of ~10dB at 434 MHz. Using a LNA with a gain of 20dB and a noise figure of 1dB, the overall system noise figure is still only ~1.4 dB, and acceptable degradation.

===Antenna===
For testing on the bench, pretty much any antenna will do, however set your expectations accordingly:

*A vertical antenna (e.g. the telescopic whips that come with many RTLSDRs) will not receive high-elevation passes well, as they have a 'null' in their antenna pattern directly overhead. When a satellite is at a lower elevation it is further away, and so will be weaker.
*A dipole antenna (be it a straight, or a v-dipole) will have similar issues, though where the null is located will depend on how you orient the dipole. Either way, there will be some portions of a satellite pass with poor performance.
*If your antenna is located inside, near to your house mains wiring, or near other electrical devices, it may end up being swamped by lots of local electrical noise and end up being 'deaf' - in this situation a LNA will only make the situation worse.

Refer to the [[Antennas|Antennas page]] for more information on antennas which are well suited to satellite observations.

==Testing the station==
[[File:Pass predictions.png|300px|right]]
Now that you have the hardware and software up and running, go ahead and schedule some passes. Navigate to your station page, and click on the Schedule button on the right side of some promising passes. The green and red bars beneath the satellite name is a quick visual indication of the number of Good and Bad passes on the network. Unfortunately, this data is not time-stamped at all, so a satellite that had a lot of Good observations a long time ago, but recently died, would still show as Green.

===Recommended Satellite Transmitters for Station Performance Benchmarking===
A few known-good satellite transmitters to test with with (as of November 2020) are:

*For a station operating on the VHF Band:
**NOAA 15, 18, 19- The APT transmitters (very strong signals - considered to be the 'hello world' of satellite observations)
**ISS - If operating, the APRS transmitter is very strong, but may only transmit intermittently throughout a pass.
**CAS4A / CAS4B - Continuous CW and GMSK transmitters - a good example of a 'weaker' cube-sat signal.
**Max Valier Sat - Another weaker CW signal.
*For a station operating on the UHF band:
**FalconSat3 - The FSK downlink transmits continuously, and is an excellent benchmark for overall station performance. A high performing station may receive upwards of 600 data packets in a single pass.
**SpooQy-1 - Regular GMSK packets.
**OPS-SAT - Regular GMSK packets, fairly strong.
**ARMADILLO - A higher data rate signal, requiring a fairly good SNR to be able to decode the (hillarious) 19.2kbps GFSK packets.
**LUSAT - CW Signal Generator in space. Continuous, strong signal.

===Rating an Observation===
[[File:Waterfall Vetting Buttons.png|right|frameless]]
After each observation, you should rate it. More information [https://wiki.satnogs.org/Operation#Rating_observations here], but the bottom line is rate the observation:

*'''Good''' if the satellite is seen in the waterfall at all. Different modulations appear differently in the waterfall, but will appear
*'''Bad''' if the satellite is not seen.

Observations which do not produce any artefacts (Waterfall, audio, data packets) will automatically be considered as failed, and will eventually be deleted.

For a more detailed guide on testing, see [[Operation]]

===Calibrating frequency offset (PPM)===
If your observations result in signals which appear to be 'off centre' of the waterfall, then you may need to set a frequency offset correction. Guides on how to determine this correction via a few different methods are available here: [[Adjusting the SatNOGS Client#Frequency Offset Calibration]]

===Mitigating Local Noise===
If you are finding the signal-to-noise of your observation seems a bit low, or you aren't seeing any signals from the known-good satellites listed above, then your station may be limited by local electrical noise. A more comprehensive guide on how to identify sources of noise is being developed, but as a starting point:

*Turn on/off nearby electrical devices while an observation is running (or while looking at a waterfall using CubicSDR as described further above).
*Common sources of electrical noise include:
**LED lightbulbs or floodlights
**USB Chargers (or really any switch-mode power supply)
**Power-over-Ethernet systems
**Unshielded ethernet cables (or even shielded cables)
**HDMI and DVI cables, and computer monitors.

 

==Next Steps==
Now that you've got this station working on the bench, what's next?

*Buy/Build an antenna suited to satellite observations. Check out the [[Antennas|Antennas page]] for ideas.
*Mount your antenna away from obstructions, and ideally away from sources of electrical noise like ethernet cables, LED lights, and other electronic equipment.
*Situate your SDR and Raspberry Pi (or other computer) as far away as practical from your antenna. If you absolutely must mount it on the mast beneath the antenna and use a metal box, and run a separate DC power supply instead of using PoE (which can produce considerable amount of RF noise)

===Building a Box===

*[https://wiki.satnogs.org/No_rotator No-Rotator setup] (Note the warning at the top of this page)

[[ Category:Build ]]
[[ Category:Hardware ]]
[[ Category:Antenna ]]

Glossary

2021-10-22T15:47:03Z

Kerel+satnogs: Add link to spacecraft attitude

This is a list of common terms and abbreviations used in the satellite community. __NOTOC__

Altitude - Sometimes referred to as elevation, is the angle between the object and the observer's local horizon. For visible objects it is an angle between 0 degrees to 90 degrees
Attitude - Spacecraft orientation in space, see [https://en.wikipedia.org/wiki/Attitude_control#Spacecraft_attitude_control Spacecraft Attitude Control] 
Azimuth - The azimuth is the angle between the north vector and the perpendicular projection of the satellite (or star) down onto the horizon. Azimuth is usually measured in degrees (°). The concept is used in navigation, astronomy, engineering, mapping, mining and artillery. 
Dashboard -
Decoder -
Demodulator -
Elevation - The elevation is the angle above the horizon. Elevation is normally measured in degrees (°).The concept is used in navigation, astronomy, engineering, mapping, mining and artillery.
Fixed Ground Station - A ground station that uses fixed antennas that wait for the satllite to pass overhead. There are no moving parts in this system.
Glouton -
Ground Station - A hardware and software combination that comprises primarily of a receiver, SatNOGS client and antenna. There are two main types. Fixed and Steerable.
Helical Antenna -
Horizontal Co-ordinate System - Sometimes also called the az/el system, the Alt/Az system or the altazimuth system (from the name of the altazimuth mount for telescopes, whose two axes follow altitude and azimuth) is a celestial coordinate system that uses the observer's local horizon as the fundamental plane. It is expressed in terms of altitude (or elevation) angle and azimuth.
Observation - The scheduling and vetting of a particular satellite through a specific ground station. Observations are scheduled using the SatNOGS Network
RTL-SDR - A cheal USB 'dongle' based on a commonly available chipset that can be used as a broadband VHF and UHF receiver. There are a huge variety of dongles with a price ranging from $3 to $30+
Rotator - The Rotator is the mechanism that points the antenna at a satellite, and follows it as it passes overhead. There are multiple versions of the SatNOGS Rotator: * [[SatNOGS Rotator v1|Version 1]] * [[SatNOGS Rotator v2|Version 2]] * [[SatNOGS Rotator v3|Version 3]]
SatNOGS Client - Software used to handle scheduling and controlling observations at the ground station
SatNOGS DB - A database of all of the satellites that can be observed through the SatNOGS system. The database contains a brief explanation fo the satelitte, its transmitters and TLE's required to conduct an observation.
SatNOGS Network - The infrastructure based around a client and server that handles observations and the results of the obervations.
Satellite - In the context of spaceflight, a satellite is an artificial object which has been intentionally placed into orbit. Such objects are sometimes called artificial satellites to distinguish them from natural satellites such as Earth's Moon. Satellites are used for a large number of purposes. Common types include military and civilian Earth observation satellites, communications satellites, navigation satellites, weather satellites, and research satellites. Space stations and human spacecraft in orbit are also satellites. Satellite orbits vary greatly, depending on the purpose of the satellite, and are classified in a number of ways. 
Steerable Ground Station - A ground station that makes use of a rotator to point antennas at a satellite as it passes overhead. This set up will require a rotator.
TLE -
Turnstile Antenna -
Yagi Antenna -

[[Category:Hardware]]
[[Category:Software]]
[[Category:Build]]
[[Category:Operate]]
[[Category:Develop]]

Omnidirectional Station How To

2021-10-22T15:01:23Z

Kerel+satnogs: /* Configuring the satnogs-client */

[[File:Omnidirectional VHF Turnstile Antenna.jpg|alt=VHF Turnstile Antenna|thumb|VHF Turnstile antenna, [https://network.satnogs.org/stations/23/ SatNOGS Station 23]]]
This How-To is written to get you quickly receiving satellite data with an Omnidirectional antenna (an antenna that does not move).

==Prerequisites/Background==
I'm assuming that you are a bit familiar with amateur radio, or linux in general, or you already have a Raspberry Pi.

===Expectation Management===
First off, I'd like to set some expectations around a SatNOGS station with an omnidirectional antenna. Yes, you will be able to hear satellites, Morse code beacons, maybe even some voice contacts on a FM transponder. But for CubeSats with 1 watt transmitters at 9600 baud, it's going to be really difficult to actually decode any data with an omni antenna. You'll definitely see squiggly lines on the waterfall plot, but demodulating the signal and extracting satellite telemetry is going to be pretty difficult.

The only way to get more signal is a better antenna. And a better antenna with more gain is going to be more directional, which means you will need a way to point that antenna at the satellite, and this How-To just got a lot more complicated. So we're not going there.

A better preamp helps a bit, see the LNA section below.

===Hardware Required===
This is a list of the hardware for indoor/testing purposes:

*Raspberry Pi
**Power supply + cable (see note below)
**Up to 16 GB Micro SD card
**Ethernet cable
*RTL SDR Blog v3 dongle
*Various short lengths of coax
*Preamp/LNA - Or not if your coax is short, see LNA section below
*Omnidirectional antenna - just a dual mag-mount on a cookie sheet will work OK for stronger satellites

==Setting up the Raspberry Pi==
I chose the [https://www.raspberrypi.org/products/raspberry-pi-3-model-b/ Raspberry Pi 3 Model B] for my station. SatNOGS is known to work on the RPi 3B, 3B+ and 4 models.

===Downloading/Writing the SD image===
The SatNOGS team has done a great job creating a Raspbian image with all the required software.
The latest download is given in the [[Raspberry_Pi#Download|Download section]].

====Installing Image on Linux====
* Unzip the downloaded file:
<pre>unzip artifacts.zip</pre>
* Figure out which device is the SD card. SD cards are usually start with mmcblk.
<pre>sudo lsblk</pre>
* Write the image. This will take a while. Make sure you don't overwrite your host OS:
<pre>sudo dd if=<latest_image_date>-Raspbian-SatNOGS-lite.img of=/dev/mmcblk0</pre>

====Installing Image on Linux/Windows/MacOS (using Rasperry Pi Imager)====
{{Warning|WARNING: This section was recently added. Please test and if it works, remove this banner.}}

This section describes the installation of installing the previously downloaded image to an SD card using the cross-platform Raspberry Pi Imager. [https://www.raspberrypi.com/documentation/computers/getting-started.html#using-raspberry-pi-imager|This guides] explains the process using this tool in more detail.

* Download the latest version of [https://www.raspberrypi.com/software/|Raspberry Pi Imager]
* Connect an SD card reader with the SD card inside
* Open Raspberry Pi Imager and choose the previously downloaded image from "Choose OS > Use custom > artifacts.zip"
* Review your selections and click '''Write''' button to begin writing data to the SD card.

===Power notes===
Thinking I could save a few bucks, I used a no-name generic 2.4 amp "tablet" USB power supply I got as a freebie, and a micro-USB cable I use for charging my phone. What a mistake! The Micro-USB cable wire gauge was too small, so there was too much voltage drop on the cable, so the Raspberry Pi reported power problems every time it was doing anything.

Power problems are indicated by either a lightning bolt in the upper right of the monitor, or the red power LED flashes on the board itself. If The Raspberry Pi processor itself is pretty forgiving of power droops because it runs at 3.3 volts. But the 5v USB ports are directly tied to input power, so undervoltage conditions will cause problems for USB devices, such as the RTL SDR dongle.

==Software Configuration==
===Creating a SatNOGS Account===
There are several different websites to be aware of. Most of our websites use a unified login provided by Auth0, so when you create an account on one of these sites it will work across all the others as well.

*[https://network.satnogs.org/ Network]: for registering your station and adding data to the network.
*[https://db.satnogs.org/ Database]: for all data on satellites and its transmitters.
*[https://community.libre.space Forums]: for questions and discussions.
*[https://wiki.satnogs.org/ Wiki]: this wiki for all kinds of documentation.

===Registering the station===
You can add your new ground station [https://network.satnogs.org/stations/edit/ here]. When following the link it will ask you to login. Either use your existing account or register a new one.

The following information is required:
* Station name, e.g. "Athens3-UHF"
* Location:
** Latitude (e.g., 38.0169)
** Longitude (e.g., 23.7312)
** Altitude above WGS84 in Meters (e.g., 20)
* At least one antenna.
** Click '''New antenna'''
** Choose the type (e.g. Turnstile)
** Add a range (e.g. VHF or UHF)
** Press '''Save changes'''

Fill out the form, click '''Submit''' and your station will be added to the Network. You can leave the other settings unchanged for now.

To help your fellow operators please consider placing the following information into the "Description" field for your station: Antenna gain and location, preamp info (if any), SDR device, some kind of contact info perhaps [[Get_In_Touch#Chat_with_us_on_our_Matrix_room |irc/matrix]] or [https://community.libre.space/ community forum] username or email address.

===Booting and Configuring Raspbian===
{{Warning|WARNING: This section describes steps which are not always required. When using ssh for setup, the steps might be different. This section should be updated to reflect this. }}

After you have the image burned onto a Micro-SD card, boot it! I would recommend hooking up a keyboard and HDMI monitor, you can watch the boot process. If it doesn't boot at all, double check that you wrote the SatNOGS Raspbian image correctly.

After a successful boot, log in with username '''pi''' and password '''raspberry'''

#Change your password! '''passwd'''
#Run '''sudo raspi-config''' to set up the base OS. ''Tab'' switches between the options and ''select''.
##4 Localisation Options: I1 Change Locale: en_US.UTF-8 UTF-8
##4 Localisation Options: I2 Change Timezone: None of the above: UTC
##4 Localisation Options: I3 Change Keyboard Layout:
##7 Advanced Options: A1 Expand Filesystem This will expand the ~2GB Micro-SD card partition to fill the entire SD card.

The Raspberry Pi needs to reboot to expand the filesystem, so do this now. It might take a while. '''sudo reboot''

====Disabling WiFi and Bluetooth====
{{Message|INFO: This step can be skipped. }}
To disable WiFi and Bluetooth, edit the /boot/config.txt file, and add the following lines at the bottom:

# Disable WiFi and Bluetooth
dtoverlay=pi3-disable-wifi
dtoverlay=pi3-disable-bt

Then reboot again. To make sure that it worked, run '''ifconfig''' and make sure that ''wlan0'' isn't listed. I'm not sure how to tell if bluetooth is turned off.

Note: Newer versions of Raspbian may require the following lines instead of the above.

# Disable WiFi and Bluetooth
dtoverlay=disable-wifi
dtoverlay=disable-bt

====Additional software====
I like to install this additional software with '''sudo apt install bmon''' ...

*bmon - a graphical network usage analyzer.
*vnstat - keeps track of your bandwidth usage
*vim - the world's best text editor ;)
*irssi - a terminal IRC client, for chatting on the #satnogs IRC channel

If you can't tell by now, I'm always a big fan of rebooting. It certainly doesn't take that long... '''sudo reboot'''

===Update the SatNOGS Client Software to latest version===
Once you have the SatNOGS OS image installed and running you should [https://wiki.satnogs.org/SatNOGS_Client_Setup#Updating_SatNOGS_Client_Software| Update the SatNOGS Client Software].

===Configuring the satnogs-client===
Now you can configure your new SatNOGS station. Plug in your RTL-SDR if you haven't already.

====Basic Configuration====
Then the actual configuration of the station:

#Run '''sudo satnogs-setup''' again.
#Use the up/down and TAB keys to navigate, and Enter to select an option.
#Basic Configuration:
##SATNOGS_API_TOKEN: After logging in to network.satnogs.org, this is in the upper right under "API Key" [no longer exsists? Add direct link]
##SATNOGS_SOAPY_RX_DEVICE: driver=rtlsdr
##SATNOGS_RX_SAMP_RATE: 2.048e6
##SATNOGS_RX_GAIN: Refer "Setting the gain" section below.
##SATNOGS_STATION_ELEV: station elevation in meters
##SATNOGS_STATION_ID: The ID number of your station.
##SATNOGS_STATION_LAT and LON: Latitude and Longitude in decimal degrees

Then back to the main menu and ''Apply'' to save the configuration. Ansible will run and update the system. If you want to quit, just keep pressing cancel to exit.

====Setting the gain====
The next step is to set the gain on the RTL SDR. The aim here (in the majority of cases) is to set the gain of your station to maximise sensitivity (best noise figure), but without limiting the available dynamic range of your station due to your local noise floor. This can be achieved in a fairly simple manner, by watching the level of the receivers noise floor as you slowly increase the receiver gain. At some point the noise floor will start to rise - at this point increasing the gain any further will of no use - you will only increase the noise level, and eat into your receiver's available dynamic range (for a RTLSDR, theoretically only 48 dB).

There may be situations where strong local interferers may require the use of a lower gain setting to avoid intermodulation products appearing in the passband, though these cases would be better solved with a suitable bandpass filter somewhere in the receive chain.

First, it is good to know the available gain range of your SDR. This can be accomplished by running <code>SoapySDRUtil --probe</code>, which provides a considerable amount of information about the connected SDR:
pi@satnogs:~ $ SoapySDRUtil --probe
######################################################
## Soapy SDR -- the SDR abstraction library
######################################################

Probe device

Found Rafael Micro R820T tuner
[INFO] [UHD] linux; GNU C++ version 8.2.0; Boost_106700; UHD_3.13.1.0-3
Found Rafael Micro R820T tuner

----------------------------------------------------
-- Device identification
----------------------------------------------------
driver=RTLSDR
hardware=RTLSDR
origin=<nowiki>https://github.com/pothosware/SoapyRTLSDR</nowiki>
rtl=0

----------------------------------------------------
-- Peripheral summary
----------------------------------------------------
Channels: 1 Rx, 0 Tx
Timestamps: NO
Other Settings:
* Direct Sampling - RTL-SDR Direct Sampling Mode
[key=direct_samp, default=0, type=string, options=(0, 1, 2)]
* Offset Tune - RTL-SDR Offset Tuning Mode
[key=offset_tune, default=false, type=bool]
* I/Q Swap - RTL-SDR I/Q Swap Mode
[key=iq_swap, default=false, type=bool]

----------------------------------------------------
-- RX Channel 0
----------------------------------------------------
Full-duplex: YES
Supports AGC: YES
Stream formats: CS8, CS16, CF32
Native format: CS8 [full-scale=128]
Stream args:
* Buffer Size - Number of bytes per buffer, multiples of 512 only.
[key=bufflen, units=bytes, default=262144, type=int]
* Ring buffers - Number of buffers in the ring.
[key=buffers, units=buffers, default=15, type=int]
* Async buffers - Number of async usb buffers (advanced).
[key=asyncBuffs, units=buffers, default=0, type=int]
Antennas: RX
Full gain range: [0, 49.6] dB
TUNER gain range: [0, 49.6] dB
Full freq range: [23.999, 1764] MHz
RF freq range: [24, 1764] MHz
CORR freq range: [-0.001, 0.001] MHz
Sample rates: 0.25, 1.024, 1.536, 1.792, 1.92, 2.048, 2.16, 2.56, 2.88, 3.2 MSps
The above output is for a RTLSDR, and we can see that there is information on the 'Full gain range', and 'TUNER' gain. The Full gain setting is an 'abstracted' gain range, which in this case just directly links to the 'TUNER' gain, as that is the only gain setting presented by the RTLSDR driver. Other SDRs (e.g. AirSpy) may present more gain controls. Anyway, we can see that the gain range is 0 through 49.6 dB. It's quite possible that there are only discrete gain steps within this range (and this is very true for the RTLSDR), but SoapySDR will hide that from us and automatically use the nearest valid setting.

Next up, we want a way of seeing a live spectrum from the SDR. This might be difficult, especially if you're just gone and mounted a RTLSDR in a metal box up a pole! Well, SoapySDR comes to the rescue again with SoapySDR Server - this allows us to serve up the SDR on the network, and access it with a client.

Note: SoapySDR Server is not currently installed by default. It can be installed by running the commands:
$ sudo apt-get install soapyremote-server
By default, SoapySDR Server may be configured to startup on boot. We probably don't want this, so run the following commands to ensure it is stopped, and will not startup on boot:
$ sudo systemctl stop soapyremote-server
$ sudo systemctl disable soapyremote-server

(These commands may result in errors indicating that the server wasn't running and/or enabled. This is OK!

[https://cubicsdr.com/ CubicSDR] is a good cross-platform client that can connect to a SoapySDR Server, and you can [https://github.com/cjcliffe/CubicSDR/releases download the latest release by clicking here].

On the RPi, you can manually start SoapySDR Server by running: <code>SoapySDRServer --bind="0.0.0.0:55132"</code> Leave this running.

Note: If you need to use the Bias-T option of an RTLSDR, you will need to activate this manually prior to running SoapySDRServer. This can be accomplished by [[Software Defined Radio#Using RTL-SDR.com V3 Dongle.27s Bias-T Power Supply|compiling the rtl_biast utility]], and running it with <code>./rtl_biast -b 1</code> . ('''NOTE: This advice may be outdated - need to confirm how to set the RTLSDRs bias on more recent SoapySDR versions)'''

Open up CubicSDR on another computer, on the same network as your SatNOGS station. It will pop up a window asking you to select a SDR device. With any luck, it will have auto-detected your SoapySDR Server, and it will show up in the 'Local Net' list. If not, you will need to select 'Remote', click 'Add', and then enter the IP address of your station. You should then have a SDR showing up in the list.
[[File:Screen Shot 2020-03-19 at 10.41.52 pm.png|alt=CubicSDR SDR Devices List|none|thumb|600x600px|CubicSDR SDR Devices List]]
You should now be able to click 'Start', and end up with a waterfall display. If the waterfall appears to glitch, or show a 'lumpy' pattern near the centre of the display, then this indicates packet loss between the SatNOGS station and your client. Try and connect via a direct LAN connection if possible.
In the settings menu of CubicSDR, disable "Automatic Gain" if it is set. This will allow manual control over the gain settings via sliders that will show up at the top left of the window.
[[File:CubicSDR Main Window.png|alt=CubicSDR Main Window (Annotated)|none|thumb|900x900px|CubicSDR Main Window (Annotated)]]
The above Figure shows the CubicSDR window, with the spectrum area, frequency selection, and gain settings annotated. Set the frequency to something suitable for your station. For example, if you are setting up a 70cm station, set a frequency of 437 MHz (437000000 Hz). For a 2m station, try 146 MHz.
Drag the gain slider so that the gain (visible at the bottom of the slider) is set to zero. Then, slowly drag it up until you see the noise floor start to rise. The gain at which this occurs is the gain you should set in SATNOGS_RF_GAIN.

To set the gain in satnogs go back to the RPI and stop the soapy remote server with ctrl-c. Run satnogs-setup, open the 'Advanced' menu, then the Radio settings. Set the gain in the SATNOGS_RF_GAIN variable.
[[File:SATNOGS RF GAIN.png|center|frame|Setting SATNOGS_RF_GAIN]]

Some SDRs may present more than one gain slider. In these situations, you will need to configure SatNOGS with each gain set individually. [[Software Defined Radio#E4000 Tuner Gain Settings|Refer here]] for more information on how to do this.

As an example, the following figure shows the noise floor observed on a station with a RTLSDR and a ~25dB masthead preamplifier, as gain levels on the RTLSDR are increased:
[[File:RTLSDR Noise Floor Variation with Gain Adjustment.png|alt=RTLSDR Noise Floor Variation with Gain Adjustment|none|thumb|900x900px|RTLSDR Noise Floor Variation with Gain Adjustment]]
We can see that between 0 db and 20 dB of gain there is essentially no change in the noise floor - this indicates the receive system is limited by the noise figure of the RTLSDR. As the gain increases through 30 dB, the noise floor starts to lift, indicating that we are now most likely limited by either the noise figure of the preamplifier, or the local noise environment. Any increase in gain past this point just results in reduction of the available receiver dynamic range.

CubicSDR DOES NOT autorange its waterfall, in contrast, SatNOGS DOES autorange its waterfall. When you adjust the gain in CubicSDR the waterfall background will dramatically change, but when you adjust the gain in SatNOGS the waterfall background will not change color. See the web page documenting autoranging waterfalls:

https://docs.satnogs.org/projects/satnogs-client/en/stable/userguide.html#satnogs-waterfall-autorange

'''Important Note: While CubicSDR is connected to the SDR, your SatNOGS ground station cannot run observations! Make sure to close CubicSDR when you have finished setting the gain.'''

===Hardware Configuration===
Basic hardware configuration is Antenna > Short coax > LNA > Coax > RTL SDR -> Raspberry Pi.

===LNA===
The way to measure the performance of an antenna is using a figure of merit called the Antenna gain-to-noise-temperature (G/T). It's a positive unitless number, higher the better.

G/T is comprised of antenna gain (in dB) on the top, and the system noise temperature (in Kelvins) on the bottom. There's a lot of somewhat-hard math involved, but here's the bottom line: to make your system perform better, you either need to increase the antenna gain or decrease the system noise temp. [https://en.wikipedia.org/wiki/Antenna_gain-to-noise-temperature Wikipedia]

Increasing the antenna gain is difficult, only because we decided on an omnidirectional antenna as the basis for this How-To. Omnidirectional antennas top out at maybe 4-6 dBi gain or so, and that's just from pushing the radiation pattern up to the sky away from the ground. Any more gain than that and it's not an omni antenna; it's got a direction that the antenna needs to be pointed in. And we want to stay away from pointing antennas for now.

Reducing the system temperature is the the way forward then. The RTL-SDR dongle has a noise figure of 6dB or so, depending on frequency, which is pretty horrible. But it turns out that the system noise temperature is largely determined by the first device in the receive chain. Since we can't change the antenna, adding a low-noise amplifier helps quite a bit. See this [https://www.youtube.com/watch?v=snifc_x_2sE youtube video] from Adam 9A4QV on how a LNA helps. (Also check out his other videos about the RTL SDR dongle, and SDR in general)

More info on SDR noise figures:

*[https://gitlab.com/librespacefoundation/sdrmakerspace/sdreval/-/raw/master/Report/pdf/Evaluation_of_SDR_Boards-1.0.pdf Evaluation of SDR Boards and Toolchains] from the [https://sdrmaker.space/ SDR Makerspace]

More info on noise and preamps:

*[https://en.wikipedia.org/wiki/Noise_temperature System noise from wikipedia], pretty high-level
*[https://www.rtl-sdr.com/tutorial-on-properly-positioning-a-preamp-lna-in-a-radio-system/ Where to put an LNA], from rtl-sdr.com
*[[SPF1589 LNA measurements|SPF5189 LNA measurements]]

Adding a LNA can also add its own set of problems, in that it may amplify strong local signals which may overload your SDR. When adding a LNA, you will likely need to back off the gain on your SDR to avoid this. It's also possible that the strong local signals may cause distortion to occur in the LNA itself, in which case you should consider the use of a filter between the LNA and the antenna. Some example products:

*If you are experiencing issues with FM broadcast stations, a [https://www.rtl-sdr.com/rtl-sdr-com-broadcast-fm-band-stop-filter-88-108-mhz-reject-now-for-sale/ FM band-stop filter] may help.
*[https://www.minikits.com.au/electronic-kits/rf-amplifiers/rf-preamplifiers MiniKits masthead preamps] include fairly low-loss bandpass filters for their target bands (2m, 70cm).

All filters will have some inherent loss, which adds to the system noise figure (or temperature, as discussed above), but this is a compromise that may need to be made to avoid distortion issues.

Finally, using a LNA near the antenna means that we can accept some losses from a long coaxial cable run between the LNA and the receiver, allowing us to situate the antenna away from sources of local noise that may impact overall performance.

As briefly discussed above, it's the first device in the receive chain which dominates the overall system noise temperature (or noise figure). In brief, as long as the losses in the coaxial cable are less than the gain of the LNA, your overall system noise figure won't degrade too much. As an example a 20m run of RG58 has a loss of ~10dB at 434 MHz. Using a LNA with a gain of 20dB and a noise figure of 1dB, the overall system noise figure is still only ~1.4 dB, and acceptable degradation.

===Antenna===
For testing on the bench, pretty much any antenna will do, however set your expectations accordingly:

*A vertical antenna (e.g. the telescopic whips that come with many RTLSDRs) will not receive high-elevation passes well, as they have a 'null' in their antenna pattern directly overhead. When a satellite is at a lower elevation it is further away, and so will be weaker.
*A dipole antenna (be it a straight, or a v-dipole) will have similar issues, though where the null is located will depend on how you orient the dipole. Either way, there will be some portions of a satellite pass with poor performance.
*If your antenna is located inside, near to your house mains wiring, or near other electrical devices, it may end up being swamped by lots of local electrical noise and end up being 'deaf' - in this situation a LNA will only make the situation worse.

Refer to the [[Antennas|Antennas page]] for more information on antennas which are well suited to satellite observations.

==Testing the station==
[[File:Pass predictions.png|300px|right]]
Now that you have the hardware and software up and running, go ahead and schedule some passes. Navigate to your station page, and click on the Schedule button on the right side of some promising passes. The green and red bars beneath the satellite name is a quick visual indication of the number of Good and Bad passes on the network. Unfortunately, this data is not time-stamped at all, so a satellite that had a lot of Good observations a long time ago, but recently died, would still show as Green.

===Recommended Satellite Transmitters for Station Performance Benchmarking===
A few known-good satellite transmitters to test with with (as of November 2020) are:

*For a station operating on the VHF Band:
**NOAA 15, 18, 19- The APT transmitters (very strong signals - considered to be the 'hello world' of satellite observations)
**ISS - If operating, the APRS transmitter is very strong, but may only transmit intermittently throughout a pass.
**CAS4A / CAS4B - Continuous CW and GMSK transmitters - a good example of a 'weaker' cube-sat signal.
**Max Valier Sat - Another weaker CW signal.
*For a station operating on the UHF band:
**FalconSat3 - The FSK downlink transmits continuously, and is an excellent benchmark for overall station performance. A high performing station may receive upwards of 600 data packets in a single pass.
**SpooQy-1 - Regular GMSK packets.
**OPS-SAT - Regular GMSK packets, fairly strong.
**ARMADILLO - A higher data rate signal, requiring a fairly good SNR to be able to decode the (hillarious) 19.2kbps GFSK packets.
**LUSAT - CW Signal Generator in space. Continuous, strong signal.

===Rating an Observation===
[[File:Waterfall Vetting Buttons.png|right|frameless]]
After each observation, you should rate it. More information [https://wiki.satnogs.org/Operation#Rating_observations here], but the bottom line is rate the observation:

*'''Good''' if the satellite is seen in the waterfall at all. Different modulations appear differently in the waterfall, but will appear
*'''Bad''' if the satellite is not seen.

Observations which do not produce any artefacts (Waterfall, audio, data packets) will automatically be considered as failed, and will eventually be deleted.

For a more detailed guide on testing, see [[Operation]]

===Calibrating frequency offset (PPM)===
If your observations result in signals which appear to be 'off centre' of the waterfall, then you may need to set a frequency offset correction. Guides on how to determine this correction via a few different methods are available here: [[Adjusting the SatNOGS Client#Frequency Offset Calibration]]

===Mitigating Local Noise===
If you are finding the signal-to-noise of your observation seems a bit low, or you aren't seeing any signals from the known-good satellites listed above, then your station may be limited by local electrical noise. A more comprehensive guide on how to identify sources of noise is being developed, but as a starting point:

*Turn on/off nearby electrical devices while an observation is running (or while looking at a waterfall using CubicSDR as described further above).
*Common sources of electrical noise include:
**LED lightbulbs or floodlights
**USB Chargers (or really any switch-mode power supply)
**Power-over-Ethernet systems
**Unshielded ethernet cables (or even shielded cables)
**HDMI and DVI cables, and computer monitors.

 

==Next Steps==
Now that you've got this station working on the bench, what's next?

*Buy/Build an antenna suited to satellite observations. Check out the [[Antennas|Antennas page]] for ideas.
*Mount your antenna away from obstructions, and ideally away from sources of electrical noise like ethernet cables, LED lights, and other electronic equipment.
*Situate your SDR and Raspberry Pi (or other computer) as far away as practical from your antenna. If you absolutely must mount it on the mast beneath the antenna and use a metal box, and run a separate DC power supply instead of using PoE (which can produce considerable amount of RF noise)

===Building a Box===

*[https://wiki.satnogs.org/No_rotator No-Rotator setup] (Note the warning at the top of this page)

[[ Category:Build ]]
[[ Category:Hardware ]]
[[ Category:Antenna ]]

Omnidirectional Station How To

2021-10-22T14:59:19Z

Kerel+satnogs: /* Configuring the satnogs-client */

[[File:Omnidirectional VHF Turnstile Antenna.jpg|alt=VHF Turnstile Antenna|thumb|VHF Turnstile antenna, [https://network.satnogs.org/stations/23/ SatNOGS Station 23]]]
This How-To is written to get you quickly receiving satellite data with an Omnidirectional antenna (an antenna that does not move).

==Prerequisites/Background==
I'm assuming that you are a bit familiar with amateur radio, or linux in general, or you already have a Raspberry Pi.

===Expectation Management===
First off, I'd like to set some expectations around a SatNOGS station with an omnidirectional antenna. Yes, you will be able to hear satellites, Morse code beacons, maybe even some voice contacts on a FM transponder. But for CubeSats with 1 watt transmitters at 9600 baud, it's going to be really difficult to actually decode any data with an omni antenna. You'll definitely see squiggly lines on the waterfall plot, but demodulating the signal and extracting satellite telemetry is going to be pretty difficult.

The only way to get more signal is a better antenna. And a better antenna with more gain is going to be more directional, which means you will need a way to point that antenna at the satellite, and this How-To just got a lot more complicated. So we're not going there.

A better preamp helps a bit, see the LNA section below.

===Hardware Required===
This is a list of the hardware for indoor/testing purposes:

*Raspberry Pi
**Power supply + cable (see note below)
**Up to 16 GB Micro SD card
**Ethernet cable
*RTL SDR Blog v3 dongle
*Various short lengths of coax
*Preamp/LNA - Or not if your coax is short, see LNA section below
*Omnidirectional antenna - just a dual mag-mount on a cookie sheet will work OK for stronger satellites

==Setting up the Raspberry Pi==
I chose the [https://www.raspberrypi.org/products/raspberry-pi-3-model-b/ Raspberry Pi 3 Model B] for my station. SatNOGS is known to work on the RPi 3B, 3B+ and 4 models.

===Downloading/Writing the SD image===
The SatNOGS team has done a great job creating a Raspbian image with all the required software.
The latest download is given in the [[Raspberry_Pi#Download|Download section]].

====Installing Image on Linux====
* Unzip the downloaded file:
<pre>unzip artifacts.zip</pre>
* Figure out which device is the SD card. SD cards are usually start with mmcblk.
<pre>sudo lsblk</pre>
* Write the image. This will take a while. Make sure you don't overwrite your host OS:
<pre>sudo dd if=<latest_image_date>-Raspbian-SatNOGS-lite.img of=/dev/mmcblk0</pre>

====Installing Image on Linux/Windows/MacOS (using Rasperry Pi Imager)====
{{Warning|WARNING: This section was recently added. Please test and if it works, remove this banner.}}

This section describes the installation of installing the previously downloaded image to an SD card using the cross-platform Raspberry Pi Imager. [https://www.raspberrypi.com/documentation/computers/getting-started.html#using-raspberry-pi-imager|This guides] explains the process using this tool in more detail.

* Download the latest version of [https://www.raspberrypi.com/software/|Raspberry Pi Imager]
* Connect an SD card reader with the SD card inside
* Open Raspberry Pi Imager and choose the previously downloaded image from "Choose OS > Use custom > artifacts.zip"
* Review your selections and click '''Write''' button to begin writing data to the SD card.

===Power notes===
Thinking I could save a few bucks, I used a no-name generic 2.4 amp "tablet" USB power supply I got as a freebie, and a micro-USB cable I use for charging my phone. What a mistake! The Micro-USB cable wire gauge was too small, so there was too much voltage drop on the cable, so the Raspberry Pi reported power problems every time it was doing anything.

Power problems are indicated by either a lightning bolt in the upper right of the monitor, or the red power LED flashes on the board itself. If The Raspberry Pi processor itself is pretty forgiving of power droops because it runs at 3.3 volts. But the 5v USB ports are directly tied to input power, so undervoltage conditions will cause problems for USB devices, such as the RTL SDR dongle.

==Software Configuration==
===Creating a SatNOGS Account===
There are several different websites to be aware of. Most of our websites use a unified login provided by Auth0, so when you create an account on one of these sites it will work across all the others as well.

*[https://network.satnogs.org/ Network]: for registering your station and adding data to the network.
*[https://db.satnogs.org/ Database]: for all data on satellites and its transmitters.
*[https://community.libre.space Forums]: for questions and discussions.
*[https://wiki.satnogs.org/ Wiki]: this wiki for all kinds of documentation.

===Registering the station===
You can add your new ground station [https://network.satnogs.org/stations/edit/ here]. When following the link it will ask you to login. Either use your existing account or register a new one.

The following information is required:
* Station name, e.g. "Athens3-UHF"
* Location:
** Latitude (e.g., 38.0169)
** Longitude (e.g., 23.7312)
** Altitude above WGS84 in Meters (e.g., 20)
* At least one antenna.
** Click '''New antenna'''
** Choose the type (e.g. Turnstile)
** Add a range (e.g. VHF or UHF)
** Press '''Save changes'''

Fill out the form, click '''Submit''' and your station will be added to the Network. You can leave the other settings unchanged for now.

To help your fellow operators please consider placing the following information into the "Description" field for your station: Antenna gain and location, preamp info (if any), SDR device, some kind of contact info perhaps [[Get_In_Touch#Chat_with_us_on_our_Matrix_room |irc/matrix]] or [https://community.libre.space/ community forum] username or email address.

===Booting and Configuring Raspbian===
{{Warning|WARNING: This section describes steps which are not always required. When using ssh for setup, the steps might be different. This section should be updated to reflect this. }}

After you have the image burned onto a Micro-SD card, boot it! I would recommend hooking up a keyboard and HDMI monitor, you can watch the boot process. If it doesn't boot at all, double check that you wrote the SatNOGS Raspbian image correctly.

After a successful boot, log in with username '''pi''' and password '''raspberry'''

#Change your password! '''passwd'''
#Run '''sudo raspi-config''' to set up the base OS. ''Tab'' switches between the options and ''select''.
##4 Localisation Options: I1 Change Locale: en_US.UTF-8 UTF-8
##4 Localisation Options: I2 Change Timezone: None of the above: UTC
##4 Localisation Options: I3 Change Keyboard Layout:
##7 Advanced Options: A1 Expand Filesystem This will expand the ~2GB Micro-SD card partition to fill the entire SD card.

The Raspberry Pi needs to reboot to expand the filesystem, so do this now. It might take a while. '''sudo reboot''

====Disabling WiFi and Bluetooth====
{{Message|INFO: This step can be skipped. }}
To disable WiFi and Bluetooth, edit the /boot/config.txt file, and add the following lines at the bottom:

# Disable WiFi and Bluetooth
dtoverlay=pi3-disable-wifi
dtoverlay=pi3-disable-bt

Then reboot again. To make sure that it worked, run '''ifconfig''' and make sure that ''wlan0'' isn't listed. I'm not sure how to tell if bluetooth is turned off.

Note: Newer versions of Raspbian may require the following lines instead of the above.

# Disable WiFi and Bluetooth
dtoverlay=disable-wifi
dtoverlay=disable-bt

====Additional software====
I like to install this additional software with '''sudo apt install bmon''' ...

*bmon - a graphical network usage analyzer.
*vnstat - keeps track of your bandwidth usage
*vim - the world's best text editor ;)
*irssi - a terminal IRC client, for chatting on the #satnogs IRC channel

If you can't tell by now, I'm always a big fan of rebooting. It certainly doesn't take that long... '''sudo reboot'''

===Configuring the satnogs-client===
Once you have the SatNOGS OS image installed and running you can configure your new SatNOGS station. Plug in your RTL SDR if you haven't already.

First thing to do is [https://wiki.satnogs.org/SatNOGS_Client_Setup#Updating_SatNOGS_Client_Software|Update the SatNOGS Client Software], as their might be new changes waiting to be installed since the SD card image was last created.

====Basic Configuration====
Then the actual configuration of the station:

#Run '''sudo satnogs-setup''' again.
#Use the up/down and TAB keys to navigate, and Enter to select an option.
#Basic Configuration:
##SATNOGS_API_TOKEN: After logging in to network.satnogs.org, this is in the upper right under "API Key" [no longer exsists? Add direct link]
##SATNOGS_SOAPY_RX_DEVICE: driver=rtlsdr
##SATNOGS_RX_SAMP_RATE: 2.048e6
##SATNOGS_RX_GAIN: Refer "Setting the gain" section below.
##SATNOGS_STATION_ELEV: station elevation in meters
##SATNOGS_STATION_ID: The ID number of your station.
##SATNOGS_STATION_LAT and LON: Latitude and Longitude in decimal degrees

Then back to the main menu and ''Apply'' to save the configuration. Ansible will run and update the system. If you want to quit, just keep pressing cancel to exit.

====Setting the gain====
The next step is to set the gain on the RTL SDR. The aim here (in the majority of cases) is to set the gain of your station to maximise sensitivity (best noise figure), but without limiting the available dynamic range of your station due to your local noise floor. This can be achieved in a fairly simple manner, by watching the level of the receivers noise floor as you slowly increase the receiver gain. At some point the noise floor will start to rise - at this point increasing the gain any further will of no use - you will only increase the noise level, and eat into your receiver's available dynamic range (for a RTLSDR, theoretically only 48 dB).

There may be situations where strong local interferers may require the use of a lower gain setting to avoid intermodulation products appearing in the passband, though these cases would be better solved with a suitable bandpass filter somewhere in the receive chain.

First, it is good to know the available gain range of your SDR. This can be accomplished by running <code>SoapySDRUtil --probe</code>, which provides a considerable amount of information about the connected SDR:
pi@satnogs:~ $ SoapySDRUtil --probe
######################################################
## Soapy SDR -- the SDR abstraction library
######################################################

Probe device

Found Rafael Micro R820T tuner
[INFO] [UHD] linux; GNU C++ version 8.2.0; Boost_106700; UHD_3.13.1.0-3
Found Rafael Micro R820T tuner

----------------------------------------------------
-- Device identification
----------------------------------------------------
driver=RTLSDR
hardware=RTLSDR
origin=<nowiki>https://github.com/pothosware/SoapyRTLSDR</nowiki>
rtl=0

----------------------------------------------------
-- Peripheral summary
----------------------------------------------------
Channels: 1 Rx, 0 Tx
Timestamps: NO
Other Settings:
* Direct Sampling - RTL-SDR Direct Sampling Mode
[key=direct_samp, default=0, type=string, options=(0, 1, 2)]
* Offset Tune - RTL-SDR Offset Tuning Mode
[key=offset_tune, default=false, type=bool]
* I/Q Swap - RTL-SDR I/Q Swap Mode
[key=iq_swap, default=false, type=bool]

----------------------------------------------------
-- RX Channel 0
----------------------------------------------------
Full-duplex: YES
Supports AGC: YES
Stream formats: CS8, CS16, CF32
Native format: CS8 [full-scale=128]
Stream args:
* Buffer Size - Number of bytes per buffer, multiples of 512 only.
[key=bufflen, units=bytes, default=262144, type=int]
* Ring buffers - Number of buffers in the ring.
[key=buffers, units=buffers, default=15, type=int]
* Async buffers - Number of async usb buffers (advanced).
[key=asyncBuffs, units=buffers, default=0, type=int]
Antennas: RX
Full gain range: [0, 49.6] dB
TUNER gain range: [0, 49.6] dB
Full freq range: [23.999, 1764] MHz
RF freq range: [24, 1764] MHz
CORR freq range: [-0.001, 0.001] MHz
Sample rates: 0.25, 1.024, 1.536, 1.792, 1.92, 2.048, 2.16, 2.56, 2.88, 3.2 MSps
The above output is for a RTLSDR, and we can see that there is information on the 'Full gain range', and 'TUNER' gain. The Full gain setting is an 'abstracted' gain range, which in this case just directly links to the 'TUNER' gain, as that is the only gain setting presented by the RTLSDR driver. Other SDRs (e.g. AirSpy) may present more gain controls. Anyway, we can see that the gain range is 0 through 49.6 dB. It's quite possible that there are only discrete gain steps within this range (and this is very true for the RTLSDR), but SoapySDR will hide that from us and automatically use the nearest valid setting.

Next up, we want a way of seeing a live spectrum from the SDR. This might be difficult, especially if you're just gone and mounted a RTLSDR in a metal box up a pole! Well, SoapySDR comes to the rescue again with SoapySDR Server - this allows us to serve up the SDR on the network, and access it with a client.

Note: SoapySDR Server is not currently installed by default. It can be installed by running the commands:
$ sudo apt-get install soapyremote-server
By default, SoapySDR Server may be configured to startup on boot. We probably don't want this, so run the following commands to ensure it is stopped, and will not startup on boot:
$ sudo systemctl stop soapyremote-server
$ sudo systemctl disable soapyremote-server

(These commands may result in errors indicating that the server wasn't running and/or enabled. This is OK!

[https://cubicsdr.com/ CubicSDR] is a good cross-platform client that can connect to a SoapySDR Server, and you can [https://github.com/cjcliffe/CubicSDR/releases download the latest release by clicking here].

On the RPi, you can manually start SoapySDR Server by running: <code>SoapySDRServer --bind="0.0.0.0:55132"</code> Leave this running.

Note: If you need to use the Bias-T option of an RTLSDR, you will need to activate this manually prior to running SoapySDRServer. This can be accomplished by [[Software Defined Radio#Using RTL-SDR.com V3 Dongle.27s Bias-T Power Supply|compiling the rtl_biast utility]], and running it with <code>./rtl_biast -b 1</code> . ('''NOTE: This advice may be outdated - need to confirm how to set the RTLSDRs bias on more recent SoapySDR versions)'''

Open up CubicSDR on another computer, on the same network as your SatNOGS station. It will pop up a window asking you to select a SDR device. With any luck, it will have auto-detected your SoapySDR Server, and it will show up in the 'Local Net' list. If not, you will need to select 'Remote', click 'Add', and then enter the IP address of your station. You should then have a SDR showing up in the list.
[[File:Screen Shot 2020-03-19 at 10.41.52 pm.png|alt=CubicSDR SDR Devices List|none|thumb|600x600px|CubicSDR SDR Devices List]]
You should now be able to click 'Start', and end up with a waterfall display. If the waterfall appears to glitch, or show a 'lumpy' pattern near the centre of the display, then this indicates packet loss between the SatNOGS station and your client. Try and connect via a direct LAN connection if possible.
In the settings menu of CubicSDR, disable "Automatic Gain" if it is set. This will allow manual control over the gain settings via sliders that will show up at the top left of the window.
[[File:CubicSDR Main Window.png|alt=CubicSDR Main Window (Annotated)|none|thumb|900x900px|CubicSDR Main Window (Annotated)]]
The above Figure shows the CubicSDR window, with the spectrum area, frequency selection, and gain settings annotated. Set the frequency to something suitable for your station. For example, if you are setting up a 70cm station, set a frequency of 437 MHz (437000000 Hz). For a 2m station, try 146 MHz.
Drag the gain slider so that the gain (visible at the bottom of the slider) is set to zero. Then, slowly drag it up until you see the noise floor start to rise. The gain at which this occurs is the gain you should set in SATNOGS_RF_GAIN.

To set the gain in satnogs go back to the RPI and stop the soapy remote server with ctrl-c. Run satnogs-setup, open the 'Advanced' menu, then the Radio settings. Set the gain in the SATNOGS_RF_GAIN variable.
[[File:SATNOGS RF GAIN.png|center|frame|Setting SATNOGS_RF_GAIN]]

Some SDRs may present more than one gain slider. In these situations, you will need to configure SatNOGS with each gain set individually. [[Software Defined Radio#E4000 Tuner Gain Settings|Refer here]] for more information on how to do this.

As an example, the following figure shows the noise floor observed on a station with a RTLSDR and a ~25dB masthead preamplifier, as gain levels on the RTLSDR are increased:
[[File:RTLSDR Noise Floor Variation with Gain Adjustment.png|alt=RTLSDR Noise Floor Variation with Gain Adjustment|none|thumb|900x900px|RTLSDR Noise Floor Variation with Gain Adjustment]]
We can see that between 0 db and 20 dB of gain there is essentially no change in the noise floor - this indicates the receive system is limited by the noise figure of the RTLSDR. As the gain increases through 30 dB, the noise floor starts to lift, indicating that we are now most likely limited by either the noise figure of the preamplifier, or the local noise environment. Any increase in gain past this point just results in reduction of the available receiver dynamic range.

CubicSDR DOES NOT autorange its waterfall, in contrast, SatNOGS DOES autorange its waterfall. When you adjust the gain in CubicSDR the waterfall background will dramatically change, but when you adjust the gain in SatNOGS the waterfall background will not change color. See the web page documenting autoranging waterfalls:

https://docs.satnogs.org/projects/satnogs-client/en/stable/userguide.html#satnogs-waterfall-autorange

'''Important Note: While CubicSDR is connected to the SDR, your SatNOGS ground station cannot run observations! Make sure to close CubicSDR when you have finished setting the gain.'''

===Hardware Configuration===
Basic hardware configuration is Antenna > Short coax > LNA > Coax > RTL SDR -> Raspberry Pi.

===LNA===
The way to measure the performance of an antenna is using a figure of merit called the Antenna gain-to-noise-temperature (G/T). It's a positive unitless number, higher the better.

G/T is comprised of antenna gain (in dB) on the top, and the system noise temperature (in Kelvins) on the bottom. There's a lot of somewhat-hard math involved, but here's the bottom line: to make your system perform better, you either need to increase the antenna gain or decrease the system noise temp. [https://en.wikipedia.org/wiki/Antenna_gain-to-noise-temperature Wikipedia]

Increasing the antenna gain is difficult, only because we decided on an omnidirectional antenna as the basis for this How-To. Omnidirectional antennas top out at maybe 4-6 dBi gain or so, and that's just from pushing the radiation pattern up to the sky away from the ground. Any more gain than that and it's not an omni antenna; it's got a direction that the antenna needs to be pointed in. And we want to stay away from pointing antennas for now.

Reducing the system temperature is the the way forward then. The RTL-SDR dongle has a noise figure of 6dB or so, depending on frequency, which is pretty horrible. But it turns out that the system noise temperature is largely determined by the first device in the receive chain. Since we can't change the antenna, adding a low-noise amplifier helps quite a bit. See this [https://www.youtube.com/watch?v=snifc_x_2sE youtube video] from Adam 9A4QV on how a LNA helps. (Also check out his other videos about the RTL SDR dongle, and SDR in general)

More info on SDR noise figures:

*[https://gitlab.com/librespacefoundation/sdrmakerspace/sdreval/-/raw/master/Report/pdf/Evaluation_of_SDR_Boards-1.0.pdf Evaluation of SDR Boards and Toolchains] from the [https://sdrmaker.space/ SDR Makerspace]

More info on noise and preamps:

*[https://en.wikipedia.org/wiki/Noise_temperature System noise from wikipedia], pretty high-level
*[https://www.rtl-sdr.com/tutorial-on-properly-positioning-a-preamp-lna-in-a-radio-system/ Where to put an LNA], from rtl-sdr.com
*[[SPF1589 LNA measurements|SPF5189 LNA measurements]]

Adding a LNA can also add its own set of problems, in that it may amplify strong local signals which may overload your SDR. When adding a LNA, you will likely need to back off the gain on your SDR to avoid this. It's also possible that the strong local signals may cause distortion to occur in the LNA itself, in which case you should consider the use of a filter between the LNA and the antenna. Some example products:

*If you are experiencing issues with FM broadcast stations, a [https://www.rtl-sdr.com/rtl-sdr-com-broadcast-fm-band-stop-filter-88-108-mhz-reject-now-for-sale/ FM band-stop filter] may help.
*[https://www.minikits.com.au/electronic-kits/rf-amplifiers/rf-preamplifiers MiniKits masthead preamps] include fairly low-loss bandpass filters for their target bands (2m, 70cm).

All filters will have some inherent loss, which adds to the system noise figure (or temperature, as discussed above), but this is a compromise that may need to be made to avoid distortion issues.

Finally, using a LNA near the antenna means that we can accept some losses from a long coaxial cable run between the LNA and the receiver, allowing us to situate the antenna away from sources of local noise that may impact overall performance.

As briefly discussed above, it's the first device in the receive chain which dominates the overall system noise temperature (or noise figure). In brief, as long as the losses in the coaxial cable are less than the gain of the LNA, your overall system noise figure won't degrade too much. As an example a 20m run of RG58 has a loss of ~10dB at 434 MHz. Using a LNA with a gain of 20dB and a noise figure of 1dB, the overall system noise figure is still only ~1.4 dB, and acceptable degradation.

===Antenna===
For testing on the bench, pretty much any antenna will do, however set your expectations accordingly:

*A vertical antenna (e.g. the telescopic whips that come with many RTLSDRs) will not receive high-elevation passes well, as they have a 'null' in their antenna pattern directly overhead. When a satellite is at a lower elevation it is further away, and so will be weaker.
*A dipole antenna (be it a straight, or a v-dipole) will have similar issues, though where the null is located will depend on how you orient the dipole. Either way, there will be some portions of a satellite pass with poor performance.
*If your antenna is located inside, near to your house mains wiring, or near other electrical devices, it may end up being swamped by lots of local electrical noise and end up being 'deaf' - in this situation a LNA will only make the situation worse.

Refer to the [[Antennas|Antennas page]] for more information on antennas which are well suited to satellite observations.

==Testing the station==
[[File:Pass predictions.png|300px|right]]
Now that you have the hardware and software up and running, go ahead and schedule some passes. Navigate to your station page, and click on the Schedule button on the right side of some promising passes. The green and red bars beneath the satellite name is a quick visual indication of the number of Good and Bad passes on the network. Unfortunately, this data is not time-stamped at all, so a satellite that had a lot of Good observations a long time ago, but recently died, would still show as Green.

===Recommended Satellite Transmitters for Station Performance Benchmarking===
A few known-good satellite transmitters to test with with (as of November 2020) are:

*For a station operating on the VHF Band:
**NOAA 15, 18, 19- The APT transmitters (very strong signals - considered to be the 'hello world' of satellite observations)
**ISS - If operating, the APRS transmitter is very strong, but may only transmit intermittently throughout a pass.
**CAS4A / CAS4B - Continuous CW and GMSK transmitters - a good example of a 'weaker' cube-sat signal.
**Max Valier Sat - Another weaker CW signal.
*For a station operating on the UHF band:
**FalconSat3 - The FSK downlink transmits continuously, and is an excellent benchmark for overall station performance. A high performing station may receive upwards of 600 data packets in a single pass.
**SpooQy-1 - Regular GMSK packets.
**OPS-SAT - Regular GMSK packets, fairly strong.
**ARMADILLO - A higher data rate signal, requiring a fairly good SNR to be able to decode the (hillarious) 19.2kbps GFSK packets.
**LUSAT - CW Signal Generator in space. Continuous, strong signal.

===Rating an Observation===
[[File:Waterfall Vetting Buttons.png|right|frameless]]
After each observation, you should rate it. More information [https://wiki.satnogs.org/Operation#Rating_observations here], but the bottom line is rate the observation:

*'''Good''' if the satellite is seen in the waterfall at all. Different modulations appear differently in the waterfall, but will appear
*'''Bad''' if the satellite is not seen.

Observations which do not produce any artefacts (Waterfall, audio, data packets) will automatically be considered as failed, and will eventually be deleted.

For a more detailed guide on testing, see [[Operation]]

===Calibrating frequency offset (PPM)===
If your observations result in signals which appear to be 'off centre' of the waterfall, then you may need to set a frequency offset correction. Guides on how to determine this correction via a few different methods are available here: [[Adjusting the SatNOGS Client#Frequency Offset Calibration]]

===Mitigating Local Noise===
If you are finding the signal-to-noise of your observation seems a bit low, or you aren't seeing any signals from the known-good satellites listed above, then your station may be limited by local electrical noise. A more comprehensive guide on how to identify sources of noise is being developed, but as a starting point:

*Turn on/off nearby electrical devices while an observation is running (or while looking at a waterfall using CubicSDR as described further above).
*Common sources of electrical noise include:
**LED lightbulbs or floodlights
**USB Chargers (or really any switch-mode power supply)
**Power-over-Ethernet systems
**Unshielded ethernet cables (or even shielded cables)
**HDMI and DVI cables, and computer monitors.

 

==Next Steps==
Now that you've got this station working on the bench, what's next?

*Buy/Build an antenna suited to satellite observations. Check out the [[Antennas|Antennas page]] for ideas.
*Mount your antenna away from obstructions, and ideally away from sources of electrical noise like ethernet cables, LED lights, and other electronic equipment.
*Situate your SDR and Raspberry Pi (or other computer) as far away as practical from your antenna. If you absolutely must mount it on the mast beneath the antenna and use a metal box, and run a separate DC power supply instead of using PoE (which can produce considerable amount of RF noise)

===Building a Box===

*[https://wiki.satnogs.org/No_rotator No-Rotator setup] (Note the warning at the top of this page)

[[ Category:Build ]]
[[ Category:Hardware ]]
[[ Category:Antenna ]]