docs(rotator): name the Green Heron RT-21, which was already supported
The RT-21 speaks the Hy-Gain DCU-1 command set in its default protocol setting, and internal/rotator/dcu1 has driven that since it landed — AP1nnn/AM1 to point, AI1 to read back, over a COM port or over TCP. Nothing was missing except a way to find it: "Green Heron" sat in a parenthesis after "Hy-Gain DCU-1", which an operator scanning the list for RT-21 does not see. So the dropdown leads with the controller people actually own, and the hint says the two things that decide whether it works: the RT-21's protocol must be set to DCU-1 / Rotor-EZ (on GS-232 it belongs to the GS-232 entry instead), and with the Ethernet option TCP reaches it directly rather than through a serial-over-IP bridge, which is what the hint used to imply was necessary. The package doc now also records what is NOT here: the native Green Heron protocol is a third command set, with 0.1° readback and a real stop, and writing it from memory is exactly the mistake this repo warns about for wire protocols.
This commit is contained in:
+4
-2
@@ -11,7 +11,8 @@
|
||||
"OpsLog appears again after an update. The relaunch was starting the new build with its window hidden, so it ran with no window at all.",
|
||||
"Each satellite slice now gets both of its antennas, RX and TX, from its own band — the downlink slice was left with no transmit antenna at all.",
|
||||
"The satellite ground track no longer draws a straight line across the map when it crosses the antimeridian.",
|
||||
"A correction you make on the transmit VFO is now kept for the whole pass, and remembered for that transponder. Doppler tracking used to undo it a second later."
|
||||
"A correction you make on the transmit VFO is now kept for the whole pass, and remembered for that transponder. Doppler tracking used to undo it a second later.",
|
||||
"The Green Heron RT-21 is named in the rotator list. It speaks the DCU-1 command set OpsLog already drives, over its COM port or straight over TCP with the Ethernet option — set the controller to DCU-1 / Rotor-EZ."
|
||||
],
|
||||
"fr": [
|
||||
"Le tracé du ciel et la position passent dans leur propre colonne, à gauche de la carte. Largeur réglable, et la colonne se replie comme celle de droite.",
|
||||
@@ -23,7 +24,8 @@
|
||||
"OpsLog réapparaît après une mise à jour. La relance démarrait la nouvelle version avec sa fenêtre masquée, donc sans aucune fenêtre.",
|
||||
"Chaque slice satellite reçoit désormais ses deux antennes, RX et TX, depuis sa propre bande — la slice de descente restait sans antenne d’émission.",
|
||||
"Le tracé au sol du satellite ne trace plus une ligne droite en travers de la carte lorsqu’il franchit l’antiméridien.",
|
||||
"Une correction faite sur le VFO d’émission est désormais conservée pour toute la passe, et mémorisée pour ce transpondeur. Le suivi Doppler l’effaçait une seconde plus tard."
|
||||
"Une correction faite sur le VFO d’émission est désormais conservée pour toute la passe, et mémorisée pour ce transpondeur. Le suivi Doppler l’effaçait une seconde plus tard.",
|
||||
"Le Green Heron RT-21 est nommé dans la liste des rotators. Il parle le jeu de commandes DCU-1 que OpsLog pilote déjà, via son port COM ou directement en TCP avec l’option Ethernet — régler le contrôleur sur DCU-1 / Rotor-EZ."
|
||||
]
|
||||
},
|
||||
{
|
||||
|
||||
Reference in New Issue
Block a user