Pressing Save in Preferences tore down the CAT link and the shared CAT server
unconditionally. Two consequences an operator sees at once: WSJT-X and JTDX are
thrown off their rig mid-QSO with an error box, and every spot disappears from a
FlexRadio panadapter — a Flex reconnect clears them by design, so the wipe on
save was the reconnect, not a stray command. Switching profile re-applies the
same settings and did exactly the same.
Two signatures decide it now. catLinkSig covers what shapes the physical link
(backend, host/port, COM port and baud, CI-V address, network credentials);
catShareSig covers the protocol and port of the rigctl/TCI server, which is the
socket WSJT-X actually holds. Same string in, same connection out, so there is
nothing to gain by rebuilding it. The poll interval, command delay, transverter
offset and spot options are applied to the running manager as before — the tests
pin that a spot option in particular can never trigger a reconnect, since that
is the one that would wipe the panadapter.
Also, two things the log would not say:
- WSJT-X/JTDX report their Enable Tx state in every Status and we wrote it
nowhere. When a station is called and nothing goes out, that flag is the whole
answer — a Reply does what a double-click does, it cannot arm a transmitter —
and the only way to see it was to watch a button in another window. Logged on
change, so it costs a few lines a QSO.
- The antenna log said "steppir connected" before anything had talked to it,
which made an unopenable serial port look like a working link with tracking
switched off. It says "configured", which is what it knows.
