manual: updated pstrotator settings descriptin. Source: implemented plausibility checks for pstrotator port range and changed ui blocking problem on the spid workaround

2026-09-11 11:45:27 +02:00 · 2026-08-16 03:05:46 +02:00
parent 422e6cf4b7
commit 8fa5360752
12 changed files with 845 additions and 97 deletions
@@ -0,0 +1,77 @@
+---
+title: PSTRotator Control
+icon: 🧭
+category: Station Control
+since: "1.31"
+summary: Point the antenna at a selected chat station and use the azimuth reported by PSTRotator throughout the KST4Contest operating context.
+description: KST4Contest calculates the direction of a selected station, sends it to PSTRotator and uses the reported antenna position for filters, priorities, timelines and map displays.
+tagsList:
+  - PSTRotator
+  - antenna rotator
+  - azimuth
+  - QTF
+  - UDP
+  - SPID
+related:
+  - priority-score
+  - timeline
+  - airscout
+---
+
+## Why connect the rotator to the chat client?
+
+A station selected in the chat already has a locator and a calculated QTF. Entering the same direction manually into another application adds another small task at precisely the point where the operator is preparing a contact.
+
+KST4Contest can send that direction directly to PSTRotator.
+
+![PSTRotator control for the selected station](/manual/assets/pstrotator_turn_antenna.png)
+
+## Sending a direction
+
+Press **Turn ant1 to …** in the Further Info section of the selected station.
+
+KST4Contest:
+
+1. calculates the azimuth from both station locators;
+2. disables PSTRotator tracking mode;
+3. sends the target as an integer azimuth; and
+4. receives the current position reported by PSTRotator.
+
+The function uses UDP. PSTRotator receives commands on the configured control port and reports its position on the following port.
+
+With the default control port `12000`, KST4Contest therefore listens on `12001`.
+
+## One position, several consumers
+
+The reported azimuth becomes the current QTF in KST4Contest. The value is subsequently used by:
+
+- the direction filter;
+- direction-opportunity detection;
+- the Priority Score;
+- the antenna sector on the map;
+- the AP and sked timeline; and
+- the `MYQTF` message variable.
+
+This shared use is intentional. The antenna should not be shown pointing in one direction while the filters and candidate calculations continue to assume another.
+
+## SPID compatibility check
+
+Some SPID configurations occasionally fail to react to the first direction command.
+
+KST4Contest checks the reported position after two seconds. If no movement was reported and the target has not been reached, it sends one compatibility sequence through `0°` and then repeats the intended target.
+
+The check runs in the background and does not block the user interface.
+
+## Limits of the integration
+
+The current interface controls and evaluates azimuth only. It does not provide elevation tracking.
+
+The reported QTF describes what PSTRotator returns. Whether the antenna mechanically reaches that exact position still depends on the rotor, controller, calibration and configured offsets.
+
+UDP also provides no delivery confirmation. Correct host, port, return port and firewall settings remain necessary.
+
+In plain terms: KST4Contest removes the repeated transfer of a direction from one window to another. It does not turn an uncalibrated rotor into a calibrated one.
+
+[Read the complete setup and port assignment in the manual.](/manual/en/configuration/#pstrotator-settings-from-v131-fully-configurable-from-v140)
+
+[Open the PSTRotator website.](https://www.pstrotator.com/)