SatNOGS Setup - Revision history

Parker.link1: Add installer instructions in the software setup guide

2026-05-17T22:26:52Z

Add installer instructions in the software setup guide

Parker.link1: /* Rotator */ Clarify rotator configuration values

2026-05-17T22:16:57Z

‎Rotator: Clarify rotator configuration values

Parker.link1: /* Verification of correct installation */ Tiny formatting change with pre text

2026-05-17T22:00:23Z

‎Verification of correct installation: Tiny formatting change with pre text

Acinonyx: Fix reference to SoapySDRUtil invocation

2026-04-29T08:07:53Z

Fix reference to SoapySDRUtil invocation

Acinonyx at 09:03, 8 February 2026

2026-02-08T09:03:01Z

Acinonyx at 08:56, 8 February 2026

2026-02-08T08:56:15Z

Acinonyx: /* Missing features */

2025-01-12T07:45:34Z

‎Missing features

Acinonyx: /* Upgrading from legacy software */

2025-01-12T07:42:42Z

‎Upgrading from legacy software

Acinonyx: Improve warning

2025-01-11T13:57:51Z

Improve warning

Acinonyx: Add missing features

2025-01-11T13:40:55Z

Add missing features

@@ Line 4: / Line 4: @@
 ==Initial Setup==
-The <code>satnogs-setup</code> configuration tool is automatically executed during [[Raspberry Pi#Installation|the installation process]]. However, if needed, you can reconfigure the software at any time by running it again:
+The <code>satnogs-setup</code> configuration tool is automatically executed during [[Raspberry Pi#Installation|the installation process]].
   $ satnogs-setup

@@ Line 117: / Line 117: @@
 !Setting
 !Description
 |-
 |<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>
+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>
@@ Line 126: / Line 129: @@
 |-
 |<code>SATNOGS_ROT_PORT</code>
-|Serial port for Hamlib rotator, OR the network address of a rotctld instance (e.g. <code>localhost:4533</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
+|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.
 |}

@@ Line 278: / Line 278: @@
 To verify that the software is set up correctly, execute:<pre>
 $ sudo docker ps -f 'name=^(satnogs|ansible)_' --format "table {{.Names}}\t{{.Status}}"
-</pre>You should see an output that looks like this:<pre>
+</pre>You should see an output that looks like this:
 NAMES                    STATUS
 ansible_satnogs-config   Up 31 seconds
@@ Line 284: / Line 286: @@
 satnogs_rigctld          Up 31 seconds
 satnogs_satnogs-client   Up 31 seconds
-</pre>If you see that, great -- you're ready to [[Operation|schedule your first observation]]! If not, check out the [[Troubleshooting]] page.
+</pre>
 ==Backup & Restore the configuration==
 The configuration of your SatNOGS station is stored at <code>/var/lib/docker-bindmounts/ansible_ansible/etc/ansible/host_vars/ansible/config.yml</code>. If your station software is broken (e.g. due to a corrupt SD card), you can perform the following steps:

@@ Line 31: / Line 31: @@
-If your device is not listed there yet, use <code><nowiki>SoapySDRUtil --probe 2>&1| grep Antennas</nowiki></code> to get available antennas.
+If your device is not listed there yet, use <code>sudo docker exec -it satnogs_satnogs-client SoapySDRUtil --probe 2>&1| grep Antennas</code> to get available antennas.
 |-
 |<code>SATNOGS_RX_SAMP_RATE</code>
@@ Line 37: / Line 37: @@
-The command <code><nowiki>SoapySDRUtil --probe 2>&1 | grep Sample</nowiki></code> can be used to find all valid sample rates.
+The command <code>sudo docker exec -it satnogs_satnogs-client SoapySDRUtil --probe 2>&1 | grep Sample</code> can be used to find all valid sample rates.
 |-
 |<code>SATNOGS_STATION_ELEV</code>
@@ Line 85: / Line 85: @@
-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.
+Run <code>sudo docker exec -it satnogs_satnogs-client 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_RX_BANDWIDTH</code>
@@ Line 102: / Line 102: @@
 |<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>
+Available gain settings can be retrieved using <code>sudo docker exec -it satnogs_satnogs-client SoapySDRUtil --probe="driver=xxxx`</code>
 Example for Airspy: Use<code>"LNA=12,MIX=8,VGA=11"</code>See also: [[SDR#Airspy|Airspy support]]

@@ Line 277: / Line 277: @@
 ==Verification of correct installation==
 To verify that the software is set up correctly, execute:<pre>
-$ sudo docker ps -f 'name=^satnogs_' --format "table {{.Names}}\t{{.Status}}"
+$ sudo docker ps -f 'name=^(satnogs|ansible)_' --format "table {{.Names}}\t{{.Status}}"
 </pre>You should see an output that looks like this:<pre>
 NAMES                    STATUS
 satnogs_satnogs-client   Up 31 seconds
 </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>/var/lib/docker-bindmounts/ansible/etc/ansible/host_vars/ansible</code>. If your station software is broken (e.g. due to a corrupt SD card), you can perform the following steps:
+The configuration of your SatNOGS station is stored at <code>/var/lib/docker-bindmounts/ansible_ansible/etc/ansible/host_vars/ansible/config.yml</code>. If your station software is broken (e.g. due to a corrupt SD card), you can perform the following steps:
 #Backup the configuration file

@@ Line 239: / Line 239: @@
 |}
 ==Updating SatNOGS Software==
-{{Warning| An update can potentially interrupt a running observation!}}The software is updated automatically when <code>satnogs-setup</code> is executed.{{Message|Client version on SatNOGS Network is updated after the first observation with the new client.}}
+{{Warning| An update can potentially interrupt a running observation!}}<code>satnogs-setup</code> automatically checks for new playbooks and prompts the user to update when a new version is available.{{Message|Client version on SatNOGS Network is updated after the first observation with the new client.}}
 ===Upgrading from legacy software===
 {{Warning|IMPORTANT: Some essential features from the previous version are currently unavailable in the newer version. Please review the [[SatNOGS Setup#Missing_features|Missing Features Table]] before proceeding with the upgrade. If any of the missing features are critical to your setup, follow the [[Raspberry_Pi_Legacy|Legacy Software Installation Guide]] to install the legacy software.}}

@@ Line 257: / Line 257: @@
 |-
 | rowspan="2" |Post and pre-observation scripts
-|No path is defined or mounted.
+|No host path for scripts is defined or mounted.
 |[https://gitlab.com/librespacefoundation/satnogs/satnogs-ansible/-/issues/184 satnogs-ansible#184]
 |-
@@ Line 264: / Line 264: @@
 |-
 |Component versions in support report
-|The versions of components in the support report is not available.
+|The versions of components in the support report are not available.
 |[https://gitlab.com/librespacefoundation/satnogs/satnogs-config/-/issues/68 satnogs-config#68]
 |-
-|Cannot modify running software
+|Editing source code of running software
-|Containers are read-only.
+|Containers are read-only and no modification on the source code can be made.
 |[https://gitlab.com/librespacefoundation/satnogs/satnogs-ansible/-/issues/157 satnogs-ansible#157]
 |}

@@ Line 271: / Line 271: @@
 |[https://gitlab.com/librespacefoundation/satnogs/satnogs-ansible/-/issues/157 satnogs-ansible#157]
 |}
-To update from the legacy SatNOGS software execute the normal installation command:
+To upgrade from the legacy SatNOGS software, execute the normal installation command:
   $ curl -sfL <nowiki>https://satno.gs/install</nowiki> | sh -s --
 The command will clean-up the old software, install the new one and then bring up the SatNOGS configuraion menu-driver utility.

@@ Line 241: / Line 241: @@
 {{Warning| An update can potentially interrupt a running observation!}}The software is updated automatically when <code>satnogs-setup</code> is executed.{{Message|Client version on SatNOGS Network is updated after the first observation with the new client.}}
 ===Upgrading from legacy software===
-{{Warning|IMPORTANT: Some key features from the previous version are currently missing in the newer version!}}
+{{Warning|IMPORTANT: Some essential features from the previous version are currently unavailable in the newer version. Please review the [[SatNOGS Setup#Missing_features|Missing Features Table]] before proceeding with the upgrade. If any of the missing features are critical to your setup, follow the [[Raspberry_Pi_Legacy|Legacy Software Installation Guide]] to install the legacy software.}}
 ====Missing features====
 {| class="wikitable"
 !Feature