A focused follow-up to the v1.9.12 CW keying work: remote CW text now keys correctly on Yaesu rigs whose USB keying line is set to RTS, plus a clearer diagnostic when the wrong rig model is selected.
CW keying
-
RTS keying now works on driver-quirked serial ports. When a CW Key Port can't be controlled directly (common on Linux and Android USB-serial adapters), POTACAT keys it through a small Python helper. That helper only ever pulsed DTR — so radios set to PC KEYING = RTS (the wiring N1MM proves out on the FT-891 and FT-710 Standard port) went into transmit with no Morse. It now honors your per-rig DTR/RTS keying-line choice and drives the correct line. Both lines are also forced low before the port opens, so an RTS-keyed radio is no longer briefly held in transmit at the start of a message.
-
A clearer "no Morse coming out" hint. If your rig is a Yaesu with a CW Key Port configured but text is still going out over the CAT
KYcommand — the symptom when the generic "Yaesu" model is selected instead of the exact one — the log now says so and points you to pick the FT-891 or FT-710 model, where CW text is routed through the key port instead. -
Fixed a cosmetic double line in the log where each CW frame was recorded twice. The command was only ever sent once; the radio was never double-keyed.
Windows, macOS (Intel + Apple Silicon), and Linux (x64 + arm64) installers are attached below; the app auto-updates from here.