From a966abd9dfdec369d1241320ec8b96561c79893d Mon Sep 17 00:00:00 2001 From: Gregory Salaun Date: Tue, 4 Aug 2026 18:46:44 +0200 Subject: [PATCH] fix(cw): show the Kenwood/Elecraft keyer as connected when CAT is up The keyer panel synthesised a "connected" status for the icom/flex/yaesu rig engines but not kenwood, so the Kenwood/Elecraft engine fell back to the (disconnected) WinKeyer hardware status and always showed "not connected" even though its CAT link was up. --- frontend/src/App.tsx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/frontend/src/App.tsx b/frontend/src/App.tsx index 83e09a0..f4d757f 100644 --- a/frontend/src/App.tsx +++ b/frontend/src/App.tsx @@ -5703,11 +5703,11 @@ export default function App() { // exactly when its CAT backend is. Yaesu was missing from this // list, so the panel fell back to the WinKeyer status — which // reported disconnected, no WinKeyer being attached. - status={cwSource === 'icom' || cwSource === 'flex' || cwSource === 'yaesu' + status={cwSource === 'icom' || cwSource === 'flex' || cwSource === 'yaesu' || cwSource === 'kenwood' ? { connected: catState.backend === cwSource && catState.connected, busy: false, wpm: wkWpm, version: 0, - port: cwSource === 'flex' ? 'CWX' : cwSource === 'yaesu' ? 'CAT' : 'CI-V', + port: cwSource === 'flex' ? 'CWX' : cwSource === 'yaesu' || cwSource === 'kenwood' ? 'CAT' : 'CI-V', } : wkStatus} ports={wkPorts}