SatNOGS Setup - Revision history

Acinonyx: Add link to Hamlib section

2026-07-17T17:44:19Z

Add link to Hamlib section

2026-07-17T17:41:50Z

Fix reference, elaborate on NETROTCTL

2026-07-17T17:39:13Z

Update Hamlib settings table

2026-07-17T17:25:03Z

Remove implemented missing feature

2026-07-17T17:23:28Z

Fix hostname of rigctld

2026-07-02T17:48:39Z

Remove reference to curl installation method

2026-06-10T00:11:52Z

‎Basic Configuration: RX_DEVICE settings

2026-05-17T22:26:52Z

Add installer instructions in the software setup guide

2026-05-17T22:16:57Z

‎Rotator: Clarify rotator configuration values

2026-05-17T22:00:23Z

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

@@ Line 125: / Line 125: @@
 |<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://github.com/Hamlib/Hamlib/wiki/Supported-Rotators#45 list of rotator models in Hamlib]. If you are connecting to a separate rotctld instance (see Hamlib section below), use <code>ROT_MODEL_NETROTCTL</code>.
+Use the macro name for your rotator model from this [https://github.com/Hamlib/Hamlib/wiki/Supported-Rotators#45 list of rotator models in Hamlib]. If you are connecting to a separate rotctld instance (see [[SatNOGS Setup#Hamlib|Hamlib]] section below), use <code>ROT_MODEL_NETROTCTL</code>.
 |-
 |<code>SATNOGS_ROT_BAUD</code>

@@ Line 125: / Line 125: @@
 |<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://github.com/Hamlib/Hamlib/wiki/Supported-Rotators#45 list of rotator models in Hamlib]. If you are connecting to a separate rotctld instance (see Hamlib section below), use <code>ROT_MODEL_NETROTCTL</code>.
 |-
 |<code>SATNOGS_ROT_BAUD</code>
@@ Line 131: / Line 131: @@
 |-
 |<code>SATNOGS_ROT_PORT</code>
-|Serial port for Hamlib rotator, OR the network address of a rotctld instance (e.g. <code>rigctld:4533</code>).
+|Serial port for Hamlib rotator, OR the network address of a rotctld instance (e.g. <code>rigctld:4533</code>) if <code>ROT_MODEL_NETROTCTL</code> is used.
 |-
 |<code>SATNOGS_ROT_THRESHOLD</code>

@@ Line 176: / Line 176: @@
 !Description
 |-
-|<code>HAMLIB_UTILS_ROT_ENABLED</code>
+|<code>ROTCTLD_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.
+|Whether or not to enable the Hamlib 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>
+|<code>ROTCTLD_MODEL</code>
-|Options for rotcld:
+|Rotator model number. A list of supported rotators and their numbers can be found [https://github.com/Hamlib/Hamlib/wiki/Supported-Rotators#45 here].
-For a yaesu rotator, use <code>-m 601 -r /dev/ttyACM0 -s 9600 -T 0.0.0.0</code>
+|-
+|<code>ROTCTLD_PORT</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>
+|TCP listerning port of rotctld daemon. The default port is 4533 if no value is specified.
 |}

@@ Line 252: / Line 252: @@
 !Description
 !Related issue
 |-
 |Installation of experimental software

@@ Line 131: / Line 131: @@
 |-
 |<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>rigctld:4533</code>).
 |-
 |<code>SATNOGS_ROT_THRESHOLD</code>

@@ Line 4: / Line 4: @@
 ==Initial Setup==
-The <code>satnogs-setup</code> configuration tool is automatically executed during [[Raspberry Pi#Installation|the installation process]].
+The <code>satnogs-setup</code> menu-driven configuration interface is automatically brought up during [[Raspberry Pi#Installation|the installation process]].
-The installer can be executed on a [[Raspberry Pi]] or on a Debian 12 laptop/desktop computer. It configures the system, and then spawns the <code>satnogs-setup</code> configuration utility:
+If needed, you can always reconfigure the station at any time by running it again:
   $ satnogs-setup

@@ Line 27: / Line 27: @@
 |-
 |<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]].
+|If you are using an RTL-SDR, use <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>.
+See [https://github.com/pothosware/SoapyRTLSDR/wiki#modules pothosware/SoapyRTLSDR/wiki#modules] for other SDR modules. If multiple devices are attached to your station, you should also specify the serial number of the desired device: e.g. <code>driver=uhd,serial=3164495</code>.
 |-
 |<code>SATNOGS_ANTENNA</code>

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