Files
OpsLog/internal
rouggy 9f5c482667 fix(catshare): echo PTT state so JTDX doesn't drop transmit
JTDX polls get_ptt DURING transmit to confirm the rig is keyed (WSJT-X does not,
which is why it worked and JTDX cut after ~2 s). We answered a blanket "0" (RX),
so JTDX concluded PTT had failed and dropped the over. get_ptt now echoes the
last PTT state commanded via set_ptt — always consistent with the client's own
command. Trace showed T 1 → three t→"0" polls → T 0.
2026-08-05 09:55:27 +02:00
..
2026-08-02 20:03:16 +02:00
2026-07-03 19:08:50 +02:00
up
2026-06-14 01:35:40 +02:00
2026-07-04 11:39:33 +02:00
2026-08-02 23:51:46 +02:00
2026-08-02 23:51:46 +02:00
2026-08-02 23:51:46 +02:00
2026-08-02 23:51:46 +02:00
up
2026-06-15 23:45:14 +02:00
2026-06-07 01:11:37 +02:00
2026-08-02 20:03:16 +02:00
2026-06-11 21:54:35 +02:00
up
2026-06-15 23:45:14 +02:00
2026-07-09 17:32:13 +02:00
2026-08-02 06:40:10 +02:00
2026-07-26 16:57:19 +02:00
2026-08-02 06:40:10 +02:00
2026-07-26 16:57:19 +02:00