Overview
Rotator control aims your antenna at the selected satellite for the whole pass. OrbitDeck computes the live azimuth and elevation from the orbit and your station (the same look angles the Home and Sky Radar screens show) and sends them to the rotator on a steady loop. Before acquisition it can pre-position to the AOS bearing; after loss of signal, or when you disconnect, it parks the antenna at a bearing you choose. Where the controller can report its position, OrbitDeck reads it back and warns you if the antenna stops following.
Rotator control works only while OrbitDeck is in the foreground, because iOS suspends Bluetooth and networking for apps in the background. Turn on Keep screen awake on Home (Settings → Display) to leave it running during a pass.
Protocols
OrbitDeck speaks these rotator protocols directly; the Protocol menu in settings lists them all:
- Yaesu GS-232A/B: the ubiquitous ASCII protocol (
W aaa eee to point) used by Yaesu GS-232 controllers and the many clones and Arduino projects that emulate it. For a controller without an elevation axis, turn on Azimuth-only controller: OrbitDeck then sends the azimuth-only M aaa command (and queries the position with C), hides elevation, and flip mode is unavailable. Serial.
- Easycomm I / II / III: the open ASCII standard used by many home-built and open-source controllers (
AZ… EL…). Easycomm III is accepted with the same grammar as II (velocity fields are not used). Serial.
- SPID Rot2Prog (MD-01/02): the binary frame protocol of SPID Elektronik controllers. MD-01/02 answer each point command with a position frame, which OrbitDeck checks; an original Rot2Prog doesn't, so the link is verified with a status query instead. A garbled, short or missing reply is resent up to 3 times before an error is shown. Serial.
- SAEBRTrack: the compact whole-degree ASCII format (
AZnnnELnnn) used by SAEBRTrack and SatPC32-style Arduino controllers. Fire-and-forget (no position read-back, no stop command). Serial.
- rotctld (Hamlib NET rotctl): the Hamlib network rotator daemon over TCP (default port 4533). Because
rotctld can drive virtually every rotator Hamlib supports, this is the most flexible option: run rotctld on a computer near the rotator and point OrbitDeck at it. Network.
- PstRotator: the popular Windows rotator program's UDP control input (default port 12000). OrbitDeck pushes the tracking bearing to PstRotator, which drives your actual rotator. Network.
- OZ9AAR URC: the OZ9AAR Universal Rotator Controller over TCP with a JSON command format (
{"GOTO":[az,el]}, default port 1111). Network.
| Protocol | Link | Position read-back | Stop command |
| GS-232A/B | BLE serial | Yes | Yes |
| Easycomm I / II / III | BLE serial | Yes | Yes |
| SPID Rot2Prog (MD-01/02) | BLE serial | Yes | Yes |
| SAEBRTrack | BLE serial | No | No |
| rotctld | TCP, port 4533 | Yes | Yes |
| PstRotator | UDP, port 12000 | No (one-way) | Yes |
| OZ9AAR URC | TCP, port 1111 | Yes | No |
rotctld is the recommended path for a rotator that OrbitDeck doesn't speak natively: Hamlib's driver list covers Yaesu, SPID, Green Heron, Prosistel, M2, EA4TX and dozens more, and OrbitDeck only needs the TCP address. (The Green Heron RT-21 Az/El, in particular, uses two independent serial links, one per axis, so it can't be driven directly from a single BLE adapter; reach it through rotctld on a nearby computer instead.)
Connections & adapters
How OrbitDeck reaches the rotator depends on the protocol:
- BLE serial adapter (GS-232, Easycomm, SPID, SAEBRTrack): a Bluetooth Low Energy UART adapter (Nordic UART Service or a generic write+notify pair) wired to the rotator controller's serial port. This is the same class of adapter used for wired rig control; see the adapters that work on the Rig Control page.
- Network (rotctld, PstRotator, OZ9AAR URC): a plain TCP or UDP connection over your local network to the computer or controller running the daemon. Enter its IP address and port.
Bluetooth Classic (SPP) adapters are not supported on iOS. Apple restricts Bluetooth Classic to MFi-certified accessories, so HC-05/HC-06-style serial adapters cannot be opened by a normal app. Use a BLE UART adapter for serial rotators, or reach the rotator over the network with rotctld.
Setting it up
- Open Settings → Rotator control → Antenna rotator and turn on Enable rotator control.
- Choose the Protocol. Network protocols reveal a Host and Port; serial protocols reveal the BLE adapter picker and serial rate (and, for GS-232, Azimuth-only controller).
- For a network rotator, enter the daemon's Host / IP and Port; the default fills in automatically (4533 for rotctld, 12000 for PstRotator, 1111 for OZ9AAR URC). For a serial rotator, tap BLE adapter, pick your adapter from the scan, and set Serial rate to match the controller.
- Set the pointing, alignment and park options as needed, then tap Done. After connecting, the self-test confirms the link and movement.
Controlling on Home
With a rotator configured, a Rotator card appears on Home. Tap Connect; the status dot turns green and the card shows:
- The current mode as the title: Tracking <satellite>, Pre-positioning · AOS in …, Parked, Tracking Sun · el …, Manual · az … el …, External control (rotctld server) and so on.
- A Target picker: Satellite, Sun, Moon or Manual (see Targets).
- The commanded Azimuth, always as a 0–360° compass heading with its compass point (for example 274° W), whatever range the rotator itself is commanded in, so a −86° in ±180° mode or a 405° in 0–450° mode still reads naturally; and the commanded Elevation (marked flipped during a flipped pass; hidden for an azimuth-only controller).
- With read-back, the Actual position reported by the controller, and a warning if it isn't following.
- A small transmit line confirming each command was sent, or the error if it wasn't.
- Manual control, which opens the manual control sheet.
The rotator follows whichever satellite is selected on Home (subject to the mid-pass lock). Tap Disconnect to stop; OrbitDeck sends the antenna to its park position on the way out. A station with a rotator but no radio gets the Stop all button on this card.
Targets: Sun, Moon & manual
- Satellite: normal tracking of the selected satellite.
- Sun: for sun-noise checks of your system's G/T and antenna pointing.
- Moon: for EME. The Moon's position is corrected for parallax (up to about 1°, which matters with a narrow beam).
- Manual: hold a fixed bearing, starting from where the antenna is now; jog or type a new one in Manual control.
Sun/Moon below horizon (in Control & diagnostics settings) chooses what happens while the Sun or Moon is down: Park (go to park and wait for it to rise) or Hold last bearing. Any target other than Satellite pauses satellite tracking until you set it back.
Point from the map tools. The Grid distance & bearing tool has Point rotator (SP) and LP buttons that send the short-path or long-path bearing to a connected rotator at 0° elevation, as a manual target, for terrestrial contacts or beacon checks.
Manual control
Open Manual control from the Home card (or from Control & diagnostics in settings). With the rotator connected it offers:
- Live status and the same commanded/actual position rows as the Home card.
- Target picker, and Resume satellite tracking whenever another target is active.
- Jog azimuth (−10, −5, −1, +1, +5, +10°) and Jog elevation (−5, −1, +1, +5°), stepping from the current manual target or, when entering manual, from where the antenna is.
- Go to: type an azimuth (and elevation) and tap Go. These are true bearings; alignment offsets and magnetic correction are applied as in tracking.
- Stop: sends the protocol's stop command and holds where the antenna is; nothing more is sent until you set a target. SAEBRTrack and OZ9AAR URC have no stop command, so Stop holds and the rotator finishes its current move.
- Park (house icon): go to the park position and hold there.
The controls are grayed out while the rotator isn't connected.
Position read-back & stall warning
On protocols with a position query (see the table), turn on Read back position (on by default). OrbitDeck polls the controller about once a second (backing off to every 5 seconds if it stops answering) and shows the Actual azimuth and elevation beside the command. If the reported position stays away from the command and hasn't moved by a degree for 10 seconds, the status dot turns to the warning color and the card shows Rotator isn't following the command — check for a stall, limit or jam. Arriving at the target or any movement clears it. PstRotator's UDP control is one-way and SAEBRTrack has no safe position query, so neither shows an actual position.
Failed commands & retry
If a point command fails to reach the rotator (a dropped Bluetooth write, a network error), OrbitDeck keeps retrying that same position instead of skipping it and waiting for the next one, waiting 2 seconds between tries at first and backing off to 10 seconds while the failures continue. Meanwhile the card shows This position hasn't reached the rotator yet — the last point command failed; retrying. This matters most for slow or fixed targets (a geostationary satellite, the Sun, a manual bearing), which may not move far enough to send a new command for a long time. If the link itself drops after a good connection, OrbitDeck reconnects after a short pause so pointing survives a brief Wi-Fi or server blip.
Self-test & monitor
- Self-test (in Control & diagnostics): with the rotator connected, tap Run self-test. It checks that the link is ready, reads the position, sends a move to the current position (testing the command without motion), then turns the azimuth 5° and back, checking whether the antenna actually moved. The antenna moves. On PstRotator and SAEBRTrack, which can't report their position, it only resends the current position and confirms the command went out. Tracking pauses during the test and resumes afterwards. Each step shows pass, fail or info with the reply received and a hint for anything that fails.
- Monitor: turn on Record traffic to see every command (>) and reply (<) on the rotator link with timestamps: text protocols as text, SPID as hex. It keeps the last 500 lines, with Copy, Share and Clear, and is useful to include with a bug report.
Changing satellites mid-pass
From the pre-position lead before AOS until LOS, the rotator stays on the satellite it's tracking when you select another one. The card asks Point at <satellite>? with Switch and Keep <current>; if you keep it, the card shows Finishing the <satellite> pass. This is the same rule CAT uses, so the antenna and radio stay together. Automatic satellite switching always moves both, and Follow selection while connected in the CAT settings lifts the lock for both.
Pointing options
- Track above elevation: only track above this elevation (0–45°); below it the antenna waits or parks. Set to 0 to track the whole visible pass.
- Pre-position lead: how many seconds before AOS to aim at the rise bearing so the antenna is already there when the satellite appears (default 120 s; off disables pre-positioning). This lead also sets when the mid-pass lock begins.
- Slew lead: optionally aim a few seconds ahead of the satellite while tracking, to compensate for a rotator's mechanical lag on fast, high passes (off disables).
- Deadband: the smallest change in bearing (default 3°) that triggers a new move, so the rotator isn't nudged needlessly during slow stretches.
- Update rate: how often OrbitDeck recomputes the target and, if it has moved enough, sends it (default 1000 ms).
With PstRotator (UDP, where a lost packet goes unnoticed) OrbitDeck also resends the current target every couple of seconds. On the other links (rotctld and URC over TCP, and BLE serial) it sends only when the target has moved by at least the
Deadband, or to
retry a failed command, so an unchanged position isn't sent again.
Alignment & park
- Azimuth offset / Elevation offset: a fixed correction added to every command to compensate for a mast or controller that isn't perfectly aligned.
- Send magnetic bearings: if your controller is set up to magnetic north rather than true north, OrbitDeck subtracts the local magnetic declination so the antenna still points at the true bearing.
- Park azimuth / Park elevation: where the antenna goes on loss of signal, between passes, on Stop all, and when you disconnect.
Flip & azimuth ranges
OrbitDeck matches the axis convention of your rotator and handles high, near-overhead passes cleanly:
- Azimuth range: 0–360° (0 = North, the usual case), −180…+180° (centered on North), or 0–450° (overlap) with a 90° overlap to avoid a cable wrap at North. In 450° mode OrbitDeck looks a few seconds ahead (Az lookahead) and pre-commits to the upper turn when a North crossing is imminent, so it doesn't spin all the way around mid-pass. The Home card always displays the bearing as a 0–360° compass heading.
- Flip mode (overhead passes): for an elevation rotator that reaches past 90°, OrbitDeck can flip an overhead pass (azimuth +180°, elevation 180−el) so the antenna tips over the top instead of whipping 180° in azimuth as the satellite transits the zenith. It only flips passes that would otherwise cross the azimuth seam (0/360°, or 180° on a ±180° rotator). The decision is made once per pass, looking at the whole pass from AOS, and held until LOS, so the antenna never flips back partway through a pass. Flip mode isn't available for an azimuth-only controller.
Stop all
Stop all (red, on the rig card, or on the rotator card for a station without a radio) appears whenever something is running. After a confirmation it releases PTT, stops FT4, packet and remote-voice transmit, ends rigctld/rotctld client control, disconnects the radio, and parks and disconnects the rotator. See Rig Control.
rotctld server
OrbitDeck can act as a Hamlib rotctld server, so Gpredict or another rotctld client on your local network can point the connected rotator through OrbitDeck, whatever protocol OrbitDeck uses to reach it. It's at the bottom of the rotator settings screen, in rotctld server, and is off by default.
- Turn on Run rotctld server. The TCP port defaults to 4533 (any port from 1024 to 65535; tap Apply after changing it).
- The section shows the Status, this device's local network address(es) with the port to enter in the client, the number of Connected clients and the Last command.
- In the client, choose Hamlib NET rotctl and enter that address and port.
What clients can do
P az el (set position), S (stop), K (park), p (get position), _ (info) and q (quit); \dump_state reports your configured azimuth range and maximum elevation.
- A set-position, stop or park pauses OrbitDeck's own tracking until that client disconnects or quits; the settings section then shows A client is pointing the rotator with a Resume OrbitDeck tracking button. Stop all also hands control back.
- Positions are sent as given: the client owns its own calibration, so OrbitDeck's offsets and magnetic correction are not applied.
- Get-position reports the last commanded position.
Client approval and limits
The rotctld server shares the rigctld server's approval rules. Require approval for new clients (on by default, one setting for both servers) holds a client on another device until you answer the Allow network client? prompt, which appears on any screen, or its row in the server section: Allow once, Always allow (adds the address to this server's Always allowed list; swipe to remove it) or Deny. Unanswered requests are denied after 30 seconds or when OrbitDeck goes to the background; clients on this device are always allowed. Connections over a VPN or cellular are refused. The server runs only while OrbitDeck is in the foreground or a background audio session is active, and the connection isn't encrypted, so use it on a network you trust. See the rigctld server section for details.
Permissions & privacy
The first time you connect, iOS asks for Bluetooth (serial rotators) and/or Local Network (network rotators and the rotctld server) permission. These connections go directly from your device to your rotator or its host computer over Bluetooth LE or your local network; nothing is sent to the developer. See the privacy policy.
Troubleshooting
- Adapter not found: make sure the BLE adapter is powered, in range, and not already connected to another app; confirm Bluetooth permission was granted. Unnamed adapters still appear in the list (sorted by signal strength).
- Network connects but nothing moves: confirm the host IP and port, that the daemon is running and reachable on your subnet, and that iOS Local Network permission was granted (if denied, the connection can look ready while packets are silently dropped). For PstRotator, match the UDP Control Port (Communication → UDP Control Port, default 12000). The monitor shows exactly what was sent and what came back.
- "Retrying" warning on the card: the last point command failed to send; OrbitDeck is retrying. If it persists, check the link.
- "Rotator isn't following the command": the controller reports a position that isn't moving toward the command. Check for a mechanical stall, an end stop or limit, or a controller in manual mode.
- Antenna points the wrong way by a fixed amount: set the azimuth/elevation offset, or enable Send magnetic bearings if your controller is referenced to magnetic north.
- Rotator spins around at North: choose the 0–450° overlap range if your rotator supports it, or the −180…+180° range, to match its axis.
- It waits instead of tracking a low pass: lower Track above elevation.
- It doesn't move to the satellite I just selected: during a pass the rotator stays on the engaged satellite until you tap Switch (see Changing satellites mid-pass).
- Gpredict can't reach OrbitDeck's rotctld server: check that the server says Listening, use the address and port shown, stay on the same Wi-Fi (not over VPN or cellular), and answer the approval prompt within 30 seconds with OrbitDeck in the foreground.
- Verifying without hardware: run
rotctld -m 1 -T 0.0.0.0 -t 4533 -vvvvv (Hamlib's dummy rotator) on a Mac/PC and point OrbitDeck at it; the verbose log shows each P <az> <el> command arriving.