Yaesu Web Control

Feedback wanted — especially if your setup isn't mine. I operate FT8 on an FTdx101MP with an SDRplay RSP1B/RSP1 for the spectrum display, so that's the combination that actually gets tested. YWC now does everything I personally need, which means I've run out of my own ideas for what to add next — new features from here on depend on what other operators ask for. If you use another mode (SSB, CW, RTTY, other digital modes), another supported radio (FTdx101D, FTdx10, FT-710, FTDX3000), or a different SDR, even a one-line "works fine" or "this is annoying because…" on the Discussions tab tells me something I can't find out on my own. Bug reports, layout issues, and feature requests are all equally welcome.

Yaesu Web Control (YWC) is a continuation of my FTdx101_WebApp with more Yaesu transceivers added and more controls.

Supported transceivers:

Transceiver	Power	Receivers	Notes
FTdx101MP	200 W	Dual	All features supported
FTdx101D	100 W	Dual	All features supported
FTdx10	100 W	Single	Two VFOs; no rear-panel IF output for spectrum
FT-710	100 W	Single	Two VFOs; no rear-panel IF output for spectrum
FTDX3000	100 W	Single	Two VFOs; no memory tag (MT) command

Other Yaesu transceivers (FT-991A, FTDX5000, etc.) can be added too — the CAT protocol is well documented and most of the groundwork already exists. What's missing is someone who owns the radio and can test against it as support is built. If that's you, open a Discussion and let's talk.

Main Page

VOX, CW and FM Repeater Panels

Calibration Page

⚠️ Warning

This software interacts with radio hardware. I have used only the official Yaesu CAT commands as per the manual, however, you use entirely at your own risk. Please read the licence. Always verify transmit frequencies, power levels, and settings before use.

📖 Why This Application Exists

I wrote this application because I can't see the FTdx101MP controls without using a magnifying glass. I've added support for partially sighted users by utilising NVDA and windows narrator. As a ham who uses WSJT-X, JTAlert, and Log4OM, I thought it would be nice to add buttons to start them from the app as it saves openning up the individual programs. I've added memory channel banks and functions to read and save etc. You don't need to save to the transceiver unless you specifically want them on it, taking your transceiver to another location for example. Please read the settings carefully as you can overwrite the transceivers memories.

Tablet testing has been limited — feedback from tablet users is particularly welcome.

🌱 Why Sponsorship Matters

I’m retired and maintain this project on a limited income, funding all development tools personally. AI‑assisted coding has been invaluable for building features quickly, but it isn’t free.

If this project has helped you, please consider sponsoring it. Even small contributions make a real difference and help keep the development tools running.

Important - .NET 10 is now built into this app so there is no need to download and install it.

⚠️ Windows Security Warnings on First Install

Because the installer is not code-signed, Windows and third-party antivirus tools will warn you before it runs. This is expected — the file is not malware. Follow these steps if you hit a block:

Norton (or other antivirus) flags the file as malware This is a false positive caused by the executable being unsigned and newly downloaded. In Norton, go to Security → History, find the quarantined file, and choose Restore & Exclude (or the equivalent Allow option in your antivirus).

Right-click → Properties → Unblock Windows marks files downloaded from the internet as untrusted. Before running the installer, right-click the file, choose Properties, and if you see an Unblock checkbox at the bottom of the General tab, tick it and click OK.

"This app can't run on your PC" — Smart App Control If Smart App Control is enabled it will block unsigned apps entirely. Go to Settings → Privacy & Security → Windows Security → App & Browser Control → Smart App Control and switch it to Off, then restart your PC and try again.

The screenshot below shows the Smart App Control setting:

These are one-time steps — once the app is installed you won't see them again.

📡 Spectrum Display

The application includes a real-time spectrum display and waterfall, intended for use with a Software Defined Radio (SDR) connected to the transceiver's 9 MHz IF output on the rear panel if it has one. From v2.3.0 YWC supports two SDRs — one per VFO — on dual-receiver radios (FTdx101MP / FTdx101D). See the "Why two SDRs?" notes below for the hardware rationale.

⚠️ SDR safety — read before connecting

An SDR receiver's front end is extremely sensitive and can be destroyed by even a small amount of TX RF.

FTdx101MP / FTdx101D / FTDX3000 (have IF output): connect the SDR to the rear-panel IF OUT RCA socket only. This is an internal low-level signal — safe during TX. Do not connect to an antenna port.

FTdx10 / FT-710 (no IF output): if you connect an SDR to an antenna port you must disconnect it during TX, or use a dedicated receive-only antenna well away from your TX antenna, or fit a T/R relay or PIN-diode T/R switch in front of the SDR. Transmitting with the SDR coax wired directly to your TX antenna will damage the SDR.

In all cases, an antenna physically close to your TX antenna can still couple enough RF into the SDR to damage it. When in doubt, disconnect.

YWC also shows this warning on the Settings page when an SDR is configured, and a more prominent danger banner appears if your selected radio is an FTdx10 or FT-710.

Supported SDR devices:

SDRplay RSP1 / RSP1A / RSP1B / RSP2 / RSPdx / RSPduo — supported via the SDRplay API v3. The SDRplay API must be installed separately from sdrplay.com. I run YWC with an RSP1B (main IF) and an RSP1 (sub IF) on an FTdx101MP and that is the configuration most thoroughly tested.
RTL-SDR, Airspy, and HackRF — supported via the bundled SoapySDR driver interface. No separate SoapySDR installation is required — the necessary drivers are included in the installer. These devices have not been tested by me — feedback from users is very welcome.

Features:

Variable span: 62.5 kHz, 125 kHz, 250 kHz, 500 kHz, 1 MHz, or 2 MHz
Dual-SDR mode: one SDR per VFO on the FTdx101MP / FTdx101D, with a Mono A / Mono B / Both layout toggle, Stacked / Side-by-side option, and independent span per panel
Click anywhere on a spectrum panel to tune the corresponding VFO to that frequency (panel A tunes VFO A, panel B tunes VFO B)
Mouse wheel over a spectrum panel tunes that VFO up/down in 1 kHz steps
Frequency axis labels automatically track each VFO

Why two SDRs? (and why two RSP1Bs rather than one RSPduo)

The FTdx101MP and FTdx101D have two independent receivers, with separate rear-panel IF output sockets (IF OUT MAIN for VFO A, IF OUT SUB for VFO B). Watching both bands at once requires two SDRs — one wired to each socket.

At first glance an SDRplay RSPduo looks like the obvious choice — it has two independent tuners in one box. Why do I run two separate RSP1Bs instead?

Bandwidth. An RSPduo in dual-tuner mode is capped to roughly 2 MHz total shared between the two tuners — so each receiver gets ~1 MHz at best. Two separate RSP1Bs each give you the full 10 MHz the chip can deliver (YWC currently uses 2 MHz spans per side but the headroom is there).
Price. Two RSP1Bs at retail are only marginally more expensive than one RSPduo — and you also get two completely independent radios you can move around your shack rather than one device locked to dual-tuner mode.
Failure isolation. If one RSP locks up, YWC's worker for that VFO restarts independently; the other receiver keeps streaming.

If you already own an RSPduo, it works fine — set it up as your VFO A SDR and the second tuner is available for other software. YWC just won't be able to drive both tuners from one RSPduo (the SDRplay API's dual-tuner mode requires special handling we haven't yet implemented).

Why an SDRplay RSP, not a £25 RTL-SDR dongle?

RTL-SDR dongles are supported and work — but for a serious HF-watching setup they leave a lot on the table compared to an RSP1B:

Bit depth. RTL-SDR is 8-bit; RSPplay RSPs are 14-bit. That's a 36 dB dynamic-range advantage to the RSP, which on a typical 40m evening means weak signals stay visible right next to a S9+30 ragchew instead of disappearing under intermodulation hash.
HF coverage. Most RTL-SDR dongles need a separate upconverter to receive HF (they were designed for VHF/UHF TV reception, not HF). RSPs cover 1 kHz to 2 GHz natively, no upconverter, no extra cable, no insertion loss.
Front-end filtering. RSPs include selectable bandpass filters; RTL-SDR dongles have essentially none. With a kilowatt-class transmitter on the next band a dongle will overload long before an RSP does.
Reference clock stability. RSPs use a TCXO; the cheap dongles drift visibly during a warm-up. For spectrum display centred on the radio's IF, that drift shows up as the whole spectrum sliding sideways over the first ten minutes.

For my FTdx101MP-with-9MHz-IF setup, the SDRplay-API path is what was developed against; RTL-SDR users are welcome to try the SoapySDR path but it has not been bench-tested.

What's that brief pause when I change the span?

When you click a different span button (250k → 2M for example), the spectrum freezes for about three seconds before it resumes at the new bandwidth. The header badge shows "Connecting…" during that window.

That delay is hardware, not software. Changing the sample rate means YWC asks the SDR's worker process to close the device, reopen it at the new rate, and restart streaming. The SDRplay API takes roughly a second to release a device cleanly and another second or so to reinitialise it. With two SDRs running in dual-SDR mode both go through the cycle at once. The spectrum data you see during the pause is the last frame from before the change — it's intentionally frozen rather than blanked so the screen doesn't go black for three seconds.

This is normal and expected. The first time you see it you'll probably blink; from the second time on it's just how RSPs reconfigure.

Project direction

Active development is currently focused on bug fixes and polish for the supported radios, plus rolling out voice control as an accessibility feature for partially sighted and blind operators — hands-free band changes, frequency entry, mode switching, and rig status without needing to see the screen.

Voice control v1 shipped in v2.4.0-pre1 (2026-06-24) and has been extended through the v2.4.0 pre-release series, most recently with independent per-VFO control (separate mic buttons for VFO A and VFO B) and a full Voice Language Pack Manager for editing phrases and macros. It uses Windows' built-in speech recognition (SAPI 5 / System.Speech) running locally on the user's PC, driven by an editable phrase pack tuned to ham-radio vocabulary, with a press-and-hold microphone button beside each VFO panel — the command targets whichever VFO's button you're holding (single-receiver radios show only one button). Recognised audio never leaves the PC; no cloud account, no public endpoint, no DNS or tunnel setup. A microphone connected to the PC is the only hardware requirement. See USER_MANUAL.md §17 Voice Control for what voice does, the full command list, and how to enable it. Feedback from real users is what's wanted right now — please try it and report back.

On the abandoned Amazon Alexa route: an earlier proof of concept routed voice through an Echo device over a Cloudflare tunnel into YWC. It worked end-to-end including signature verification, but setting it up required the user to own a domain, run a Cloudflare account, configure a custom Alexa Skill in the Amazon Developer Console, and install cloudflared — well over an hour of fiddly setup for the average ham. The local-SAPI approach above is dramatically simpler (one Windows speech-pack install, one Settings toggle) and runs entirely offline. The Alexa branch is therefore retired; the local mic approach is the supported path going forward.

Which radios get tested?

YWC supports the FTdx101MP, FTdx101D, FTdx10, FT-710, and FTDX3000. I own and test on the FTdx101MP; support for the other four models is implemented against the published CAT documentation and refined when users on those models report. If you use one of the other four models, please consider dropping a one-liner on the Discussions tab — even just "works fine on my FT-710" is useful. It tells me which models have actual users behind them and where to focus calibration improvements.

Staying informed about updates

Recent versions of YWC include an in-app update check that pops up a banner the first time you run it after a new release lands. If you're already running v2.2.x or later you'll get those notifications automatically — no action needed.

If you're on an older version that pre-dates the update check, or you want to know about a new release before you've launched the app, any one of these will keep you in the loop:

GitHub release notifications (most reliable, free, no spam):
1. Make sure you're signed in to GitHub
2. Visit https://github.com/mm5agm/Yaesu_Web_Control
3. Click the Watch dropdown at the top-right of the page
4. Choose Custom and tick only Releases
5. Save — you'll get one email per release, and nothing in between
RSS / Atom feed — if you use a feed reader (Feedly, NewsBlur, Inoreader, Thunderbird, etc.), subscribe to https://github.com/mm5agm/Yaesu_Web_Control/releases.atom — new releases appear in your reader without any account or email signup.

If you're talking to another Yaesu operator running an older YWC, a heads-up that a new version exists is the most reliable way it reaches them. Word of mouth still works — there's no email list of all downloaders and no way to reach the very early users who don't fall into any of the channels above.

Release Notes

2026-07-10 - v2.4.1

Bug-fix release, out of the normal cadence, because the bug it fixes turned out to block basic connectivity for real users on day one of v2.4.0.

Settings page silently failing to save (#65)

Reported by yozhin (FTdx10) and independently by Steve K3FZT (FTdx101MP, via the Groups.io list) within hours of the v2.4.0 release. The SDRplay install path field in Settings → SDR Spectrum Display was a non-nullable string, which under this project's <Nullable>enable</Nullable> triggers an implicit "required" validation rule — invisible in the UI, but enough for the browser's client-side validation to silently block the entire Settings form from submitting whenever that field was blank (the default for almost everyone). No error appeared anywhere; clicking Save just did nothing.

For Steve this wasn't just an annoyance — it meant he couldn't change the serial port away from the shipped default (COM3) to match his own PC, so YWC couldn't reach his FTdx101MP at all even though nothing else was using the port. Fixed: the field is now nullable, matching the pattern already used by the other optional Settings fields, and a second latent bug (the field's value was never actually copied into the saved settings object, even before this) is fixed alongside it.

English (US) voice control language pack

Added a US-English variant of the built-in Voice Control phrase pack (same commands, "meters" instead of "metres", the one UK-only trigger phrase dropped) — install it via Settings → Voice Control → Preview import using the pack shipped at /voice-packs/YWC-VoicePack-en-US-v1.zip. See USER_MANUAL.md §17.7 for how to author and share further language packs.

2026-07-10 - v2.4.0

Headline release: Voice Control v1 — hands-free operation via on-PC speech recognition, previewed across four pre-releases and now fully landed with independent per-VFO mic buttons and a full Voice Language Pack Manager. Alongside it: the dual-VFO S-meter gauge is back, frequency ▲/▼ buttons now repeat while held, spectrum panels gained a draggable splitter, and a batch of CAT-command fixes reported by Alessandro IK2XRW, Thomas OZ1JTE, Bill W1WRH, solson888, and Jacek SP3L.

Headline feature — Voice Control v1

Hands-free voice control of common operating actions, previewed across v2.4.0-pre1 through pre4 and now landing as a full feature. Recognition runs entirely on-PC via Windows' built-in speech engine (SAPI 5) — no audio ever leaves the machine. See USER_MANUAL.md §17 for the complete reference.

Independent mic button per VFO, on the Index page next to each VFO's band/mode controls (replacing an earlier single navbar button) — press and hold VFO A's button to control VFO A, VFO B's to control VFO B. Only one VFO listens at a time; single-receiver radios (FTdx10, FT-710, FTDX3000) show just VFO A's button.
Full command set: set frequency, change band, step up/down with a configurable step size, band up/down, set mode, swap VFOs, set attenuator/preamp/AGC/AF gain, nudge IF filter width, transmit on/off, split on/off, spoken status read-back ("what frequency", "what mode", "what band"), help, and a macro group (noise reduction, noise blanker, copy A↔B, fine step, roofing filter).
Spoken confirmation after every command ("Move to fourteen point zero seven four megahertz, successful") — the safety net against misrecognition, since a misheard command is easy to catch by ear before it does anything unwanted.
Low-confidence matches are rejected rather than fuzzy-fitted to the nearest rule, so background noise or an ambient TV can't accidentally trigger a command.
Voice Language Pack Manager (Settings → Voice Control): a full phrase editor with hot-reload (no restart needed to change wording), a macro editor for custom CAT command sequences, per-row "Try it" mic testing, a Test this pack dry-run modal for checking phrases without touching the radio, version history (last 5 saves/imports, one-click undo), and export/import of shareable .zip language packs with per-collision merge resolution.
Diagnostics panel (Settings → Voice Control) shows engine state, last phrase heard, last intent matched, active language, installed pack version, and last recognition confidence — plus a filtered Voice Control Log on the Diagnostics page for troubleshooting without digging through the raw log file.
Multi-language architecture, though only English (UK) ships as the built-in default today — the Active language dropdown, pack import, and hand-authored Commands.<culture>.json files are all already wired up for anyone who wants to contribute another language.

Dual-VFO S-meter gauge restored

v2.3.9 dropped the top-row S-meter to a single gauge (VFO A/MAIN only), on the belief that the SUB receiver's SM1; reading was junk on the FTdx101 family. That belief was never re-verified and turned out to be wrong. The second gauge is back: on dual-receiver radios (FTdx101MP/D) the top meter row now shows two S-meter gauges and two 30-second history strips, one per VFO, confirmed against a live FTdx101MP. Single-receiver radios (FTdx10, FT-710, FTDX3000, FT-991A) are unaffected — they only ever had one gauge.

Also fixed while working on this: the S-meter history strip(s) would slowly grow wider the longer YWC stayed open. The strip's canvas was styled at 100% of a container that only set a min-width, so the container's actual width ended up depending on the canvas's own backing-store size — every resize made the canvas a little bigger, which made the container a little bigger, which triggered another resize. The container now has a fixed width, so the strip holds steady.

Frequency ▲/▼ buttons now repeat while held

The optional on-screen frequency ▲/▼ buttons (Settings → Accessibility → "Show frequency arrow buttons") used to step the selected digit once per click, which made reaching a distant frequency a lot of clicking. Press-and-hold now repeats that same step every 500 ms until released — mouse, touch, and keyboard (Enter/Space) all supported.

Spectrum display — draggable splitter

Each SDR spectrum panel has a draggable splitter between spectrum trace and waterfall. Hover the boundary; the cursor becomes a vertical-resize arrow. Drag up to give the spectrum more vertical room (useful for low-signal work), drag down to give the waterfall more history. The ratio is persisted per-VFO in browser localStorage and operates independently on each panel in a dual-SDR setup. Default is unchanged (45 % spectrum / 55 % waterfall), so users who don't touch it see no difference.

Fullscreen shortcut no longer hijacks browser find (Ctrl+F)

YWC's fullscreen toggle is F (bare letter, no modifiers) per §13 Keyboard Shortcuts. The handler had a missing-modifier-check bug that also fired on Ctrl+F, which meant the browser's find-in-page box never appeared on any YWC page — Ctrl+F just put the app fullscreen. Fixed: the handler now only triggers on bare F, so Ctrl+F (Windows/Linux) and ⌘+F (Mac) pass through to the browser as the user expects.

Fldigi launch button (#52)

YWC now has a fifth external-app slot for Fldigi, requested by Bill W1WRH. Same pattern as the existing WSJT-X / JTAlert / Log4OM / GridTracker buttons: configure the path in Application Setup, tick Show, save, and the launch button appears on the main page after GridTracker. Defaults to hidden so existing users see no change until they opt in. Process detection uses the fldigi.exe task-manager name.

PROC button + level slider now actually drive the radio (#51)

Reported by solson888 on the FTdx10, confirmed on the FTdx101MP too — the universal bug was that YWC was sending PR0;/PR1; for the speech-processor on/off button, but per the Yaesu CAT manual that's a read command, not a set. The radio dutifully read back its state and changed nothing. YWC now sends the correct PR00;/PR01; set commands. (Bench testing also confirmed the manual's P2 values are wrong — the documented 1=OFF / 2=ON is actually 0=OFF / 1=ON. The CAT manual will be reporting itself shortly.) The PROC level slider now reads the value back from the radio after each write so the on-screen number is always what the radio really has, not just what YWC sent.

Audio Filter popout (replaces broken IF Low Cut)

The "IF Low Cut" dropdown on each VFO panel was sending the SL CAT command — which is not documented for any current Yaesu HF transceiver (FTdx101MP/D, FTdx10, FT-710, FTDX3000, FT-991A). The radio silently ignored it, so the control was a phantom: changing the dropdown looked like it was doing something but nothing actually reached the radio. Confirmed by Jacek SP3L on FTdx10 (#48) and my own FTdx101MP.

The fix replaces the dropdown with a new Audio Filter button on each VFO panel that opens a dedicated popout dialog exposing the full per-mode passband shaping the radio actually has:

LCUT FREQ — low-cut cutoff frequency, OFF or 100–1000 Hz in 50 Hz steps
LCUT SLOPE — 6 dB/oct or 18 dB/oct
HCUT FREQ — high-cut cutoff frequency, OFF or 700–4000 Hz in 50 Hz steps
HCUT SLOPE — 6 dB/oct or 18 dB/oct

The radio stores these values per mode class (one set per SSB / AM / FM / PSK-DATA / RTTY / CW), so changing mode automatically restores that mode's stored settings. The dialog reads the current mode's values when opened and writes back via the Yaesu EX (menu) command; on the FTdx101 family the values are shared between MAIN and SUB when both receivers are in the same mode (the dialog shows a discreet "VFO B is also in SSB" note when that's the case). On older radios where some entries aren't exposed via CAT — e.g. FT-991A in FM has no LCUT/HCUT settings, FTDX3000 in RTTY has no LCUT SLOPE — the corresponding control is greyed out.

One Audio Filter button per VFO panel; both dialogs can be open simultaneously on dual-receiver radios. Each dialog is independently draggable and remembers its position. Per-radio EX address tables for all five supported models are bundled in wwwroot/data/audio-filter-ex-map.json.

SDRplay API auto-detect + install-path Settings field (#53)

IK2XRW Alessandro discovered that on his system YWC couldn't find sdrplay_api.dll even though the SDRplay API was installed, because Windows P/Invoke search doesn't reach the SDRplay install folder unless its x64 directory was added to PATH (which it wasn't on his machine). YWC now actively searches for the DLL rather than relying on PATH:

A new user-configurable SDRplay install path field in Settings → SDR Spectrum Display (advanced, blank = auto-detect)
YWC's app directory next to Yaesu_Web_Control.exe
C:\Program Files\SDRplay\API\x64\sdrplay_api.dll
C:\Program Files (x86)\SDRplay\API\x64\sdrplay_api.dll
Fall back to default Windows DLL search (which honours PATH)

The Settings page also shows what the auto-detect resolved to (Auto-detected: <path> in green) or a warning if nothing was found, and includes a Browse… button that opens a native Windows folder picker on the YWC host's desktop. The picker refuses (with a clear error) when called from a remote browser, since the dialog only appears on the host machine.

For most users with a standard SDRplay install the change is invisible: the SDR just works without needing to touch PATH. For users like Alessandro who had to copy the DLL into YWC's folder as a workaround, the copy is no longer needed.

ZIN button for CW (#55)

Requested by IK2XRW Alessandro. Triggers the radio's CW Auto-Zero-In function (ZI CAT command) — the radio nudges the VFO so the received CW signal sits exactly at the operator's preferred CW pitch.

After Alessandro's feedback that S&P-mode operating doesn't fit well with popout-only controls, ZIN appears in two places:

One ZIN button in each VFO panel's header — always visible, no popup needed. Each button targets its own VFO explicitly: VFO A's button fires ZI0; (MAIN); VFO B's fires ZI1; (SUB on the FTdx101 family; silently maps to MAIN on single-receiver radios).
Plus the existing ZIN button on the Speed WPM row of the CW Keyer popout — kept because some operators prefer keeping their CW controls clustered. This one follows whichever VFO is currently active per VS.

Spectrum click — crosshair follows the clicked frequency

When you click the spectrum to QSY, the spectrum recentres on the new VFO frequency. The live crosshair (the vertical line that tracks your mouse position) used to stay at its pixel position — which meant the frequency under the cursor briefly shifted by hundreds of Hz after the click, until you next moved the mouse. The crosshair now jumps to the canvas centre at click time, where the clicked frequency now sits, so the readout label stays on the frequency you just picked. The next real mouse movement resumes normal tracking.

Spectrum display — Low/High/Gain sliders for noise-floor tuning (#53)

Three continuous sliders on each spectrum panel replace the static four-option dB-range preset dropdown:

Low (−160 to −60 dBFS) — noise floor (bottom of the scale). Drag up to push the static noise shelf out of view; drag down to reveal signals buried near the floor.
High (−100 to 0 dBFS) — ceiling (top of the scale). Leave at 0 for a full-range view or tighten to compress empty headroom.
Gain (0 to +30 dB, shown as +N dB) — pre-display digital gain applied to the FFT data before the floor/ceiling window. Lifts the whole trace proportionally. Labelled Gain rather than "Zoom" to avoid confusion with the existing frequency-span buttons.

The Low and High sliders enforce low < high: dragging one past the other nudges the other slider rather than rejecting the input. Changes take effect on the next SDR frame — no restart, no page reload. Settings persist server-side in appsettings.user.json per VFO, so a browser reload or a second browser inherits the same calibrated view.

VC Tune preselector hidden for hardware revisions that don't support VT CAT (#59)

The FTdx101MP's VC Tune preselector is physically present on many units and works from the front panel. However, some hardware revisions — confirmed on units returning ID0682 — do not expose VC Tune over CAT. Sending VT VCT commands to these units returns ?;?; (CAT error) even on fully up-to-date firmware (MAIN V01-28 / DISPLAY V01-51 / DSP V01-20).

YWC now reads the radio's ID; response on startup and compares it against a list of known-unsupported hardware IDs. When the radio is on the list the VC Tune controls are hidden entirely. The physical preselector is unaffected and continues to work normally from the front panel.

DX Spots list — click now sets mode as well as frequency (#57)

Requested by IK2XRW Alessandro. Clicking a row in the DX Spots popup now follows the QSY with a band-plan-aware mode change, matching what spectrum-panel clicks have always done. Click an FT8 spot from USB and the radio flips to DATA-U; click a CW spot from FT8 and it flips to CW-U; and so on. The mode is derived from the band-plan (not from the spot's free-text comment) so it's consistent and reliable.

Esc key now closes the Memory panel (#61)

Reported by Thomas OZ1JTE. The Frequency Entry keyboard has always closed on Esc; the Memory panel did not, because it opens as a non-modal dialog (so the rest of the app stays usable while it's open) and non-modal <dialog> elements don't get the browser's built-in Esc-to-close behaviour the way modal ones do. Esc now closes the Memory panel too, including when it's open at the same time as the Frequency Entry keyboard.

2026-06-22 - v2.3.9

The release that finally closes out Jacek SP3L's R1–R12 single-receiver UI spec on #34 (a saga that ran from pre1 to pre8 across eight pre-release iterations — thank you Jacek), plus a major frequency-keyboard accessibility round driven by Yuri W4YSW, plus the radio-state init cluster (#38–#47) that was making YWC start up out of sync with the radio on a bunch of controls.

Single-receiver radio UI — R1–R12 fully landed

The v2.3.8 release implemented Jacek SP3L's R1–R12 spec for the FTdx10 / FT-710 / FTDX3000 / FT-991A single-receiver path. Eight pre-releases of v2.3.9 closed out the rough edges that Jacek's hands-on testing surfaced:

VFO-B-as-active case (R7/R8). Pressing Split with VFO-B as the receive VFO was showing panel A as white (should be grey — TX) and panel B as grey (should be white — RX), inverted from what the radio was actually doing. The fix is a simpler invariant — white = active RX VFO, grey = the other one, in both normal and split mode — applied to panel coloring, SPLIT TX badge position, and red card border.
Outbound P1=0 routing. When the user clicked a receive-control on a single-receiver radio (Contour, APF, IF Width, IF Shift, AF Gain, NR, NB, NB Level, NR Level, Auto Notch, Manual Notch on/off + freq, AGC, IPO, Attenuator, RF Gain, Squelch, IF Low Cut), the command was being sent with the wrong P1 parameter on radios where P1 is hardcoded to 0. Thirteen endpoints fixed in one pass.
TX button position in split mode. The TX button now sits on the TX VFO's panel even when the FT command doesn't move (FTdx10 split-mode quirk).
SPLIT TX badge follows the actual TX VFO. Was previously hardcoded to VFO B's header and never shown/hidden by code.
S-meter relocated to the top meter row. Yaesu radios only have one calibrated S-meter (tied to MAIN on FTdx101, the only physical receiver on single-receiver rigs), so showing it once at the top is the honest presentation. The per-VFO S-meter gauges are gone; the 30-second history strip moves with it.
Transient S-meter zero-flash debounced. The radio occasionally returns a transient zero to SM0; during FA auto-info bursts (typically while the dial is being turned). Three-consecutive-zeros debounce on the zero path only — non-zero readings still propagate instantly so the needle stays snappy when there's signal.

Frequency display accessibility — Yuri W4YSW

The VFO frequency display is now fully keyboard-driven. Tab into a display (a blue focus ring appears), then:

ArrowUp / ArrowDown — step the selected digit by ±1.
PageUp / PageDown — step the selected digit by ±10.
ArrowLeft / ArrowRight — move the selection cursor.
Home / End — jump to the leftmost (most significant, tens of MHz) or rightmost (least significant, Hz) digit.

First arrow-press with no digit selected just highlights the kHz digit — a second press steps it. This protects against an accidental ArrowUp changing the radio without you realising a digit was selected.

Optional on-screen ▲/▼ buttons sit next to each VFO's frequency display when Settings → Accessibility → Show frequency up/down arrow buttons is on. Each click steps the selected digit by 1, the same as a single ArrowUp/ArrowDown. Off by default so users with mouse wheels see the uncluttered default. Useful for head-tracking input, on-screen keyboard users, and reduced-dexterity operators.

The selected digit highlights yellow. Selection persists across the ~10 Hz polling cycles so you can press ArrowUp ten times in a row and the selection stays put. Click outside the display + ▲/▼ controls to deselect.

USER_MANUAL chapter 13 (Keyboard Shortcuts) has the full reference table; §16.7 covers the accessibility-focused summary.

Radio-state init fixes (Jacek SP3L #38–#47)

A cluster of bug reports from Jacek showing YWC starting up displaying stale values for things that the radio actually had set differently — IPO/AMP showing OFF when the radio was on AMP1, Auto Notch showing OFF, Manual Notch showing OFF, NB OFF, NR OFF, etc.

Radio init no longer overwrites radio state on connect. Root cause of #40–#46. YWC was reading the radio state correctly during connect, then immediately overwriting most of it from persisted-state-on-disk. Fixed: persisted state is now a fallback only for fields the radio doesn't report, not a blanket overwrite.
Dropdowns render with actual radio state on first paint. Was rendering the persisted state and only updating after the first SignalR push, leading to a visible flicker.
NR / DNR Level (RL command) added, with FTdx10-aware UI rework (#47). The level slider was missing; the FTdx10 has just one NR with a level whereas FTdx101 has NR1 / NR2 modes. UI now adapts per model.
DNR label. Was rendered as "no." rather than "No." (the proper abbreviation of "Number").

Other improvements

Settings page reorganised as collapsible sections. Each settings category is a native HTML <details>/<summary> block — built-in keyboard accessibility, screen-reader support, and no JavaScript required. The Accessibility section is the first one, just below the network access URLs.
USER_MANUAL §15.7 — what the TX button does. Common confusion for new users (raised by Luis LU1CBQ on Groups.io): the TX button sends TX1; to the radio to put it in transmit mode without engaging YWC's audio routing, useful for tune-up / external amplifier testing / digital-mode latency checks. The §15.7 FAQ entry explains this.

2026-06-17 - v2.3.8

A quick follow-up to v2.3.7 (two days ago) — we don't normally ship this close together, but Jacek SP3L's hands-on testing on his FTdx10 surfaced a UI behaviour problem that the Yaesu manual was too ambiguous to anticipate. Working out what single-receiver VFO panels should do in normal mode versus split mode needed empirical testing: which VFO is "active", which controls respond, what happens when split is engaged via the front panel versus YWC, what about the frequency field on the inactive panel? Jacek wrote a 12-point spec (R1–R12) describing the answers from his point of view, posted on #34, and v2.3.8 implements it. Plus a few filter-scope improvements that came out of the testing.

Single-receiver radio UI rework (FTdx10, FT-710, FTDX3000, FT-991A)

Driven by Jacek SP3L's R1–R12 spec in #34.

Split-mode greying flipped. In normal mode the inactive VFO is grey (as before). In split mode the TX VFO is grey and the RX VFO is white — the opposite. The TX-side controls are read-only-but-displayed; the RX side is where the operator's attention belongs. Previously the same greying applied regardless of split, which left the operator looking at a greyed-out RX VFO they actually needed to interact with.
TX button and SPLIT badge follow the grey panel in split mode. Implicit from the new greying logic — both already track the TX VFO.
TX frequency editable on the grey panel in split. When in split mode the grey panel IS the TX VFO; you need to be able to set the TX frequency without un-splitting first. Click a digit and scroll the mouse wheel, or use the keyboard-icon button next to MHz to type one in. Other controls (mode, IF Width, notch, etc.) stay read-only on the grey panel — they show their stored values for reference but can't be edited.
Antenna selector hidden on radios with a single antenna jack — FTdx10 and FT-991A. Showing a per-VFO antenna dropdown on a radio with one ANT jack was visual noise.

Filter scope display improvements

Wide CW filters now fit on the canvas. At 3 kHz and 12 kHz CW the audio passband centres on +700 Hz and extends into negative Hz on the lower side; the axis previously ran 0–3.5 kHz and clipped the left half of the trapezium right off the canvas edge. The axis now tracks the current passband, so the full trapezium with both red slope lines is visible at every IF Width.
Trapezium fills more of the canvas at narrow filters. Where a 300 Hz CW filter previously occupied ~10 % of the panel width with the rest empty, the axis now zooms to the passband at all widths — making the trapezium, contour arrowhead, manual notch marker, and APF marker proportionally bigger and easier to read.
Contour slider range matches the current passband. Setting contour to 2 kHz on a 300 Hz CW filter has no audible effect — the contour position is outside the filter. The slider now restricts to the current passband's audio range (clamped to the radio's hard CAT range as an outer bound), so every position on the slider has an audible effect. When the IF Width narrows past the current contour value, the value is clamped in place and pushed to the radio automatically.

Other fixes

Filter-scope axis labels at the canvas edges no longer get clipped. The leftmost "-1k" label was rendering as just "k" on wide CW because the centred text placement put half the label off-screen — now the first and last labels are left- / right-aligned to the canvas edges.
TX0; safety command sent to the radio on both connect and disconnect, so YWC never leaves the radio in transmit even if the operator closes mid-transmit. Some Yaesu firmwares preserve MOX/TX state across power cycles, so a radio powered off mid-transmit could otherwise come back up still keying.

Bug fix

#35 take 2 (Jacek SP3L) — RF Power read-back on connect. The v2.3.7 fix added PC; to YWC's "read these properties from the radio on startup" list, but the loop that processes that list discarded responses instead of routing them through the state dispatcher — so YWC kept showing the persisted Power value (e.g. 5 W) on startup instead of reading the radio's current value (e.g. 33 W). The same loop was silently failing for ~20 other properties too (MIC Gain, Speech Processor, AGC, IPO, Attenuator, NR, NB, NB Level, Auto Notch, RF Gain, Squelch, AF Gain, Monitor, CW Pitch/Speed/Break-in, VOX) which now all populate correctly on startup.
#37 (Jacek SP3L) — RF Power slider max on non-FTdx101MP radios. The slider's max value only named the two FTdx101 variants explicitly; every other 100 W radio (FTdx10, FT-710, FTDX3000, FT-991A) fell through to a 200 W default, letting operators drag the slider to 150 W on a 100 W radio. The slider now reads its max from a single radio-model lookup, and clamps the displayed value if it ever exceeds the new max (e.g. when changing radio model in Settings during a session).

Diagnostics page improvements

A few quality-of-life changes during the FTdx10 testing this round:

Start / Stop capture instead of always-on. The Diagnostics page no longer fills its event-log buffer continuously while you're not looking — press Start to begin capturing, Stop to halt. An idle Diagnostics tab now uses zero buffer and zero render work.
Inline COM Ports / CAT Status panels. The two buttons used to open new browser tabs (and the back arrow didn't return you to Diagnostics); they now expand collapsible panels inline on the Diagnostics page itself. New /api/ports endpoint backs the COM Ports panel.
Render throttling and pre-filtering. With a filter set, the log buffer fills only with matching events, and the on-screen render runs at most 10 Hz — both make rare events (like SplitMode toggles) survive long enough to be inspected at meter-poll rates.
VFO / Split investigation preset. New "Split investigation set" entry in the filter dropdown selects the minimal set of properties that actually fire during a split toggle and A↔B swap test — useful when capturing diagnostics for a split-mode bug report.

2026-06-15 - v2.3.7

Reporter-driven release across five contributors — Jacek SP3L, Thomas OZ1JTE, Ken KN2D, plus my own bench testing. The biggest single change is a UI overhaul for single-receiver radios (FTdx10, FT-710, FTDX3000) driven by Jacek's hands-on testing. Eight new features and improvements; six bug fixes; one calibration update; one accessibility improvement specifically for screen-reader users; the v1 of the Voice Control documentation lands as a preview.

New features

Per-band antenna memory. Each band now remembers which antenna (Ant 1 / 2 / 3) you last used on it, independently per VFO. Set Ant 1 on 20 m, Ant 2 on 6 m once, and from then on switching bands restores the right antenna automatically. The Yaesu radios don't recall this internally when frequency is changed via CAT (only via the front-panel BAND button), so YWC now does the remembering. Setting an antenna writes immediately to disk, and a startup backfill auto-populates empty fields on existing installs so you don't have to manually click through every band.
ATU long-press auto-tune trigger (Jacek SP3L, #34). Press and hold the ATU button for ≥500 ms to start the radio's auto-tune cycle (CAT command AC002;). Button turns red "Tuning…" for the duration; tap during a running tune to stop it early. Short tap still toggles ATU on/off as before — matches the radio's own front-panel TUNE button.
Per-VFO ATU state sync (Jacek SP3L, #34). On single-receiver radios the ATU on/off state is remembered per VFO by the radio firmware and re-applied when you swap A/B. YWC now re-queries the ATU state after a VFO swap so its button matches.
Diagnostics block now shows host CPU and Memory. The About page's "Copy diagnostics" output (which feeds bug reports automatically) now includes the CPU model + logical core count and total physical RAM of the host PC. Useful for triaging performance-related reports — particularly relevant now that dual-SDR support means a shack PC might be running two SDR worker processes plus radio polling plus spectrum render.

User interface — single-receiver radios

VFO panels reflect what's actually possible on the radio (Jacek SP3L, #34). On FTdx10, FT-710, and FTDX3000, only one physical receiver chain exists inside the radio — VFO B is effectively a frequency/mode memory slot, not a real sub-receiver. The UI now greys out the inactive VFO panel on these radios to make this clear: its receive-side controls (AGC, NB, NR, IF Width, etc.) are still editable but only take effect once you swap that VFO to be active via the A↔B button. On dual-receiver radios (FTdx101MP/D) both panels remain fully active because each VFO genuinely is its own receiver.
Single spectrum panel on single-receiver radios. The spectrum display layout used to show a single panel on single-receiver radios but kept the "Stacked / Side-by-side / VFO A / VFO B / Both" toggle visible. The toggle is now hidden when only one physical receiver exists; the single panel always tracks the active VFO.

Accessibility

Spectrum tick / crosshair / segment label font sizes increased. The MHz frequency tick labels under the spectrum (10 → 13 px), the dB-scale Y-axis labels (10 → 12 px), the band-plan segment markers like FT8/CW/SSB (11 → 13 px), and the hover-crosshair frequency readout (11 → 14 px) are all larger so they're readable without a magnifying glass.
Screen reader announcements made less talkative (Thomas OZ1JTE, #20). Three changes addressing his feedback that the screen reader was reading every passed-over button on the way to the target:
- ARIA live region changed from polite (queues announcements) to assertive (each new announcement interrupts the previous) — directly matches Thomas's request that "the speech queue should be cleared/cancelled whenever a new reading is triggered".
- Hover-to-announce debounce 200 ms → 400 ms — Memories table sweeps now only announce the element you deliberately pause on.
- Frequency display ARIA debounce 300 ms → 500 ms — rapid wheel scrolling announces only the settled value, not intermediates.

Bug fixes

Installer no longer fails with file-lock errors when upgrading (Ken KN2D). The NSIS installer's Install section had no provision for stopping a running YWC before copying new files — so upgrading on top of a running app produced "Error opening file for writing: ...Accessibility.dll" with Abort/Retry/Ignore, repeating for every locked DLL. Added a taskkill of Yaesu_Web_Control.exe and Yaesu_Sdr_Worker.exe at the start of Install with a 1.5 s settle delay.
RF Power no longer reset on YWC startup (Jacek SP3L, #35). YWC was overwriting whatever Power you'd set on the radio's front panel while YWC was off, with its own last-saved value. Same anti-pattern as the MIC GAIN / Speech Processor fix from #16 in v2.2.0. The radio is now the source of truth on connect; YWC reads the current Power via the PC; query and the UI follows.
RF Power slider now follows front-panel changes (Jacek SP3L, #36). The SignalR Power handler was updating the per-VFO powerSliderA element but not the unified powerSlider used on single-receiver radio layouts, so a front-panel power change moved the numerical label but left the slider visually frozen. Also: "100W" → "100 W" with a space, per Jacek's closing note on #36.
RF Power label now shows the exact radio value, not the snapped slider position. Edge case caught while bench-testing #35: if the radio is set to an odd value like 91 W, the slider has step=5 so it snaps to position 90 — and the label was reading from the snapped slider position, showing "90 W" while the radio was at 91 W. The label now reflects the exact value the radio reports; the slider position is a visual approximation.
Front-panel TUNE button state now propagates to YWC. Pre-existing parser bug: CatMessageDispatcher was reading byte P1 of the AC reply for ATU on/off state, when the Yaesu CAT manual defines P1 as "Fixed at 0" — the actual state lives in P3. Send-side was always correct (YWC's ATU button commands worked fine), but radio-initiated changes silently failed to update the UI. Fixed.
Direct CAT command replies now flow through state correctly. Pre-existing bug uncovered while implementing the ATU work: CatMultiplexerService.OnMessageReceived consumes replies to outgoing commands BEFORE the dispatcher sees them, so any post-command state queries (like the new post-swap AC; refresh) silently returned a value to the controller but never updated state. The affected paths now parse the reply in the controller directly.

Calibration

FTdx10 default S-meter calibration updated with real-world measurement from Jacek SP3L (Discussion #30). The shipped default's +40 dB point moved from raw=208 to raw=213 to match what Jacek measured on his radio. PWR / SWR / Compression / ALC / TPA / IDD / VPA all agreed with the existing default, so only this one point changed.

Documentation

"Project direction" section added to README. A short evergreen statement about how YWC develops, which radios get tested, and how reporter-driven the project is. Aimed at new users and prospective sponsors.
VOICE_CONTROL.md preview included. A 700+ line document covering the in-progress voice control feature (Alexa via Cloudflare Tunnel). The feature itself is not shipping in v2.3.7 — it's still gated on an open Amazon support case. The docs ship as a preview so interested users can review the setup commitment and judge whether they'll want voice control once the feature lands. The document includes a clear "not yet shipped" banner at the top.
Spectrum span list typo fixed in README. The spectrum-display feature list was missing the 62.5 kHz and 125 kHz spans.
USER_MANUAL aligned with all of the above. Seven sections updated to describe the new behaviour: Power section (radio-as-source-of-truth), VFO Panels (single-receiver greying), ATU button (short tap vs long press), Antenna control (per-band memory), Backup & Restore table (Antenna added to per-band list), Diagnostics (CPU/Memory mention), Screen Reader Support (assertive + debounces).

Update post-release

#20 — FTdx10 IF Width dropdown 3.0 kHz entry — RESOLVED. Thomas OZ1JTE re-tested v2.3.6 after restarting YWC and found the 3.0 kHz dropdown entry was present and all step increments tracked correctly. The original report appears to have been a stale-state issue (browser cache, in-memory state, or a UI not refreshing) that cleared with a restart. Issue #20 closed 2026-06-15. No code change in v2.3.7 was related to this; the dropdown table was unchanged.

2026-06-12 - v2.3.6

Two reporter-driven bug fixes plus a significant calibration improvement. Recommended update for everyone running v2.3.5.

Bug fixes

YWC no longer changes the radio's frequency on startup or tab navigation. Reported by Jacek SP3L (#33), reproduced on my FTdx101MP. On every Index-page load, YWC was auto-tuning the radio to the last-clicked band segment for each VFO (e.g. snapping to the saved FT8 frequency on 20m even if you'd just manually tuned the rig somewhere else). The auto-tune call has been removed; the segment dropdown still restores its visual value, but YWC no longer pushes a frequency back to the radio. The rig's current frequency is the source of truth.
S-meter calibration now correctly drives the gauge needle. Reported by Jacek SP3L (#29), reproduced and traced on my FTdx101MP. The v2.3.3 fix wired the SignalR refresh and the numeric-table loader, but two further bugs prevented the needle from moving correctly:
1. Label-to-number translation was missing. S-meter calibration files store labels as strings ("S0", "S1", "+10", "+60"). The loader was falling back to identity (raw ADC value) for those, so the gauge needle ended up on a raw 0-255 scale instead of the calibrated S-unit 0-60 scale.
2. Static gauge tick positions didn't match the visual labels. The gauge labels are drawn at evenly-spaced angles on the dial, but our needle-position mapping assumed they sat at the numeric majorTicks values. Calibrating raw→S5 put the needle at a position that visually corresponded to S3 — exactly Jacek's "2 S-units low" complaint.
Both fixed. Calibration changes now reach the gauge needle live via SignalR push, and the needle points at the correct S-unit label.

Other fixes

0+60 typo in the last S-Meter entry of all 6 shipped calibration default files corrected to +60. I noticed this while bench-testing #29.
Dev-mode no longer corrupts the shipped calibration files. When running from source (dotnet run), the calibration Save endpoint was writing to wwwroot/calibration.default.<model>.json instead of the user's APPDATA file. That meant a developer doing routine calibration testing would silently overwrite the shipped defaults committed to the repo. Now both dev and release builds always write to the user's APPDATA file.

Documentation

USER_MANUAL §10 expanded with a proper step-by-step calibration procedure:
- §10.1 S-Meter calibration walkthrough — emphasises the [RF/SQL] knob must be in "RF" mode (not SQL), uses the lower of the two FTdx101MP front-panel knobs (MAIN AF / RF-SQL), and describes the dummy-load + RF-gain-walk technique that needs no extra test equipment.
- §10.2 Power meter calibration via known TX power levels.
- §10.3 Brief notes for ALC / SWR / Compression / IDD / VPA / TPA.
The S-Meter writeup was prompted by discovering the on-rig meter behaviour during calibration: the S-meter is displayed automatically during receive on the FTdx101MP/D, and is NOT selectable from the touchscreen meter chooser (which is for TX-time meters only).

2026-06-11 - v2.3.5

Fixes Test Connection properly. If you have v2.3.4 installed, please update — v2.3.4 made the button safe (no longer crashes) but it still reported a false-negative "Radio did not respond" on every click because the probe-validation logic was wrong.

Bug fixes (all in the Test Connection flow)

Probe-validation no longer demands a trailing semicolon. The CAT multiplexer strips the ; terminator as part of response parsing, so the validation check probe.Contains(';') always failed against the parsed reply (e.g. ID0682 rather than ID0682;). Validation now requires the reply to start with ID and be at least 6 characters long — enough to be sure we got back a real radio identifier.
Stay on Settings after success. Previously a successful Test Connection click redirected the browser to the home page after 1 second — leftover behaviour from when this button was "Reinitialize" and made sense as "init then start using the radio". For a confirmation-only Test Connection, the redirect was jarring. Now the button just shows "Connection succeeded — radio ID 0682" for 3 seconds and reverts.
Friendlier success message. Was "Radio responded (ID0682)" — reads like internal debug language. Now reads "Connection succeeded — radio ID 0682".

2026-06-11 - v2.3.4

Critical hotfix on v2.3.3. If you have v2.3.3 installed, please update.

Bug fix

Settings page "Test Connection" button no longer crashes YWC. v2.3.3 wired Test Connection to run the same heavyweight startup initialization sequence the app uses on launch (multiplexer connect
- ~30 CAT read queries + state restoration). That's safe at startup when nothing else is running yet — but on a running system it races with the 10 Hz meter poller, the SDR workers, and any in-flight WebUI commands, and on my bench it consistently crashed the YWC process on the first or second click.
Replacement: Test Connection now sends just the ID; probe through the existing CAT client (which the multiplexer queues correctly alongside the running meter polls). The deep init only runs if the multiplexer is genuinely disconnected — i.e. the original "configure Settings, then verify connection" use case.

Other improvements:

Probe timeout raised from 1 s to 2 s so a Test Connection click during a busy multiplexer queue has time to surface the response.
Error wording slightly tightened (the message used to talk about "COM port opened but the radio did not respond" — which assumed re-init had run; with the new logic it just talks about CAT).

2026-06-11 - v2.3.2

Small hotfix on top of v2.3.1 — suppresses a startling Windows dialog that could pop up on the Settings page for users who have certain other SDR software installed.

Bug fix

Windows "Entry Point Not Found" dialog suppressed. The Settings page's auto-scan (new in v2.3.0) enumerates SoapySDR plugins (HackRF, RTL-SDR, Airspy etc.). If the user has a hackrf.dll or similar in C:\Windows\System32 from another SDR application (SDR#, HRD, SDR Console, etc.), Windows may load that DLL ahead of YWC's bundled one — and if it has different libusb dependencies, the OS pops up a modal "Entry Point Not Found" error dialog. YWC was already handling the underlying plugin-load failure gracefully (the unloadable plugin just doesn't appear in the device list), but the dialog itself is startling. Now suppressed via SetErrorMode at process startup; the plugin load still fails silently for users with the conflict, but no dialog interrupts the session.

There are no other changes in v2.3.2 — see v2.3.0 / v2.3.1 below for the actual feature set of this release line.

2026-06-11 - v2.3.1

Hotfix on v2.3.0. No user-facing changes — v2.3.0 itself shipped with a broken installer build and v2.3.1 is the same code with the build pipeline fixed. If you've never installed v2.3.0 (no installer was produced), just install v2.3.1 and read the v2.3.0 release notes below for what's new.

Build pipeline fix

Worker exe was missing from the published installer. The new Yaesu_Sdr_Worker.exe (for the dual-SDR architecture) is built by a separate .csproj and copied into YWC's output via <None Include> items in the main .csproj. The path patterns assumed no RuntimeIdentifier was set — true for dotnet build / dotnet run but false for the CI's dotnet publish -r win-x64, where outputs go into a win-x64 subfolder. CI publish failed with MSB3030: Could not copy the file Yaesu_Sdr_Worker.exe because it was not found.

Fixed with a second <ItemGroup Condition="'$(RuntimeIdentifier)' != ''"...> block that uses the RID-suffixed path during publish. Both paths now resolve correctly: local dev dotnet run AND CI's dotnet publish -r win-x64.

2026-06-11 - v2.3.0

The first big-ticket v2.x feature: one SDR per VFO on dual-receiver radios, plus a handful of bug fixes from real reporter feedback on v2.2.2.

Headline feature — Dual-SDR

On the FTdx101MP and FTdx101D, both receivers have their own IF output socket; YWC can now drive an independent SDR on each, with two synchronised spectrum panels on the main page.

Per-VFO SDR assignment. The Settings page SDR section gained two dropdowns — VFO A SDR and VFO B SDR — so you can tell YWC which physical SDR is wired to which VFO's IF output. Either can be left empty for a single-SDR setup; the existing single-SDR behaviour is preserved.
Two spectrum panels on the main page when both VFOs are configured, each tracking its own VFO's frequency. Click on panel A tunes VFO A; click on panel B tunes VFO B.
Independent span per VFO. Each spectrum panel has its own 62.5k / 125k / 250k / 500k / 1M / 2M span buttons — set VFO A to 2 MHz for a wide overview of the calling band while VFO B sits at 62.5 kHz zoomed on the QSO. 62.5k and 125k spans are new in this release (narrowest span the SDRplay API can deliver via decimation, useful on the narrow amateur bands).
Layout toggles above the spectrum panels (only visible when both VFOs have an SDR):
- VFO A / VFO B / Both — show just one panel or both side by side.
- Stacked / Side by side — stack the two panels vertically (more detail per panel) or place them horizontally (both at half-width). Both choices are remembered across page reloads.
Hold and persistent-cursor scope features. Each panel has a Hold button that freezes its display at the current frame (yellow Hold badge
- "HOLD" canvas banner). Shift-click anywhere on a spectrum to drop a cyan persistent-cursor "bookmark" at that frequency — useful for marking a station to come back to while tuning around.
Per-region band-edge guard rails. Red dashed lines marking the edges of each amateur band now reflect the region selected in Settings — UK operators see 3.500–3.800 MHz for 80m, not the US 3.500–4.000 limits.
Settings page Scan now surfaces SDRs that are currently held by a running worker, labelled "(in use)", so you can see your active device even though the SDRplay API hides it from a fresh enumeration call.

Other new features

Per-model meter calibration. YWC now ships separate default S-meter / power / SWR / ALC calibration tables for each supported radio (FTdx101MP, FTdx101D, FTdx10, FTDX3000, FT-710). The FTdx101MP tables are measured; the others are placeholders pending real user measurements — please share yours via Discussion #30 so other users of your radio benefit.
"Reset to Defaults" button on the Meter Calibration page. Use it after changing radio model in Settings to pick up the new model's shipped defaults instead of editing files manually.
Test Connection now actually probes CAT. The Settings page Test Connection button used to report success the moment the COM port opened, with no actual radio communication. It now sends a CAT ID; query and requires a parseable reply before declaring success — and the failure message names the most common cause (a virtual port sharer like VSPE / OmniRig sitting between YWC and the radio).
Band plans are now externalised to wwwroot/bandplan.default.json. Future regulator updates (RSGB, FCC, JARL) can ship as a one-file drop into the install folder, no full app reinstall required.
Filter scope panel now shows the active roofing filter in the top-right corner. Previously, choosing 12k vs 3k roofing produced the same trapezium when the DSP filter was the limiting factor (which is most of the time) — there was no visible way to tell which roofing was selected. Now a small "Roof 12k" / "Roof 3k" label removes the ambiguity.

Bug fixes

WSJT-X frequency-bounce on the FTdx10 (Issue #22, Bill W1WRH). YWC's rigctld bridge used to send a fresh CAT query on every get_freq from a Hamlib client, which raced against YWC's own CAT poller. WSJT-X's display briefly bounced back to the old frequency for a second or two after every set. Now reads from the cached RadioStateService state (which set_freq updates immediately), so WSJT-X tracks instantly.
Calibration saves were being silently ignored at the gauge (Issue #29, Jacek SP3L-Jacek). Two layered bugs: the frontend's in-memory calibration tables weren't refreshed after a save, and the numeric S-meter table was never loaded from the backend at all (only the snap-to-nearest label table was). Both fixed; calibration changes now propagate to all open browser tabs live via SignalR.
Dead DX cluster examples in Settings (Issue #27, djrino). All four example clusters listed on the Settings page were dead; replaced with five verified-alive servers led by dxspider.co.uk:7300.
WSJT-X rig control on FTdx10 (Issue #22, Bill W1WRH). YWC's rigctld bridge rejected PKTUSB / PKTLSB / PKTFM mode commands with "E_MODE: Unsupported mode for this rig" — WSJT-X's standard FT8 mode-set call. Added Hamlib → Yaesu mode translation so the FTdx10's WSJT-X CAT path no longer drops control every 20 seconds.

Settings file migrations (silent, no user action)

Legacy single SdrDeviceKey → split into SdrDeviceKeyA and SdrDeviceKeyB. Old value auto-promoted to A on first read; legacy field cleared on next save.
Legacy single SdrSampleRateHz → split into SdrSampleRateHzA and SdrSampleRateHzB. Same pattern.
sdrplay:<serial> → sdrplay:hw<N>-<serial> (hwVer prefix). Auto-applied the first time the SDR scan runs.

Architecture (under the hood)

The SDRplay API v3 service enforces one Selected device per host process — we confirmed this against the actual hardware with a four-pattern probe before committing to the design. So YWC main no longer opens an SDR directly. Each configured SDR runs in its own Yaesu_Sdr_Worker.exe process, with FFT frames streamed back to YWC over a localhost TCP socket. The worker exe is shipped alongside Yaesu_Web_Control.exe and managed automatically — you'll just see one or two extra entries in Task Manager when YWC is streaming.

Full architectural reasoning is in docs/decisions/0001-dual-sdr-architecture.md in the repo.

Reporters credited

Special thanks to Bill W1WRH (PKTUSB CAT translation + frequency-bounce race), Jacek SP3L (S-meter calibration discovery + the per-model calibration system that grew from it), djrino (DX cluster examples replaced + the Test Cluster Connection button), Juergen WB4EM (Test Connection real-probe fix + the FAQ entry about Silabs USB driver conflicts from other ham software), and Antonino Rinaldi (DX cluster country flags + QRZ click-through on the roadmap).

2026-06-09 - v2.2.2

A small hotfix on top of v2.2.1, primarily addressing one reporter-filed bug and one regression that v2.2.1 itself introduced.

Bug fixes

Sticky navbar actually works now. v2.2.1's release notes promised this feature but shipped with sticky-top applied to the wrong element — the <nav> inside <header>, where position: sticky couldn't track body scroll. The class is now on <header> where it does what was intended. The User Manual no longer needs Page-Up to get back to the nav links.
DX cluster examples in Settings replaced — closes #27 (djrino). The in-line examples (cluster.dl4ny.de:7300, dxc.k4ldc.com:7300) on the Settings page were both at hostnames whose DNS no longer resolved. Anyone copying them faithfully got a silent failure. v2.2.2 lists five verified-alive clusters led by dxspider.co.uk:7300. The USER_MANUAL §6.6 list was already correct.

New features

Test cluster connection button. Settings → DX Cluster section gains a yellow Test cluster connection button. Click it and YWC opens a TCP connection to the host/port/callsign typed into the form (without saving them), sends the callsign, reads ~10 seconds of output, and shows the transcript in a popup. The button turns solid green with a "Cluster connection successful" label after a successful test, so it is unambiguous what's working and what isn't — exactly the diagnostic that would have made the #27 silent-failure obvious in 10 seconds.

Internal / preparing for v2.3.0

SDRplay device key format migrated to sdrplay:hw<N>-<serial> so the upcoming dual-SDR work can distinguish two devices that happen to share a serial — notably the original RSP1's factory-default 0000000001 placeholder. Existing v2.2.x keys (sdrplay:<serial>) continue to work and are silently rewritten to the new format on the next Save Settings. No user action required. New FAQ §15.2 explains the background.
Default set/qra example locator updated to IO85CX (my actual square). Cosmetic only.

2026-06-09 - v2.2.1

A quick hotfix on top of v2.2.0 — closes one silently-affecting bug, adds a hardware-safety warning, and includes two small UX fixes.

Bug fixes

WSJT-X "orange rig" failure (#22, W1WRH). YWC's rigctld bridge was rejecting Hamlib's PKTUSB mode name with E_MODE: Unsupported mode for this rig. whenever WSJT-X tried to set the mode at connect time. The result was WSJT-X dropping the rig control indicator to orange and re-trying every 20 seconds in an infinite loop. Bug affects any radio when the WSJT-X profile is set up to push mode explicitly (typical on fresh installs). The read path was already translating outbound DATA-USB → PKTUSB correctly, but the write path didn't accept it coming back — inconsistent. Fix accepts PKTUSB / PKTLSB / PKTFM and translates them to DATA-U / DATA-L / DATA-FM. Similar translation added for CW / CW-R / RTTY / RTTY-R.

New features and improvements

⚠️ SDR safety warnings. Connecting an SDR to a TX antenna — or an antenna close to one you're transmitting on — can permanently damage the SDR's front end. README and User Manual §6.3 now carry a prominent safety section explaining the safe connection options (IF output, dedicated RX antenna, or T/R switch). The Settings page shows a corresponding warning whenever an SDR is configured, and a more prominent red danger banner if the selected radio is an FTdx10 or FT-710 (no IF tap, SDR must connect to an antenna).
Sticky top navigation bar. The top nav (About / User Manual / Home / Settings / Application Setup / Meter Calibration / Memories / Accessibility Labels) now stays visible when scrolling. Particularly useful in the long User Manual — no more page-ups to get home.
About page — bug-report links consolidated. Two slightly-different bug-report links previously caused confusion. The plain "Report a bug" link (no diagnostics) has been removed; only the Report a bug button under the Diagnostics block remains, since the diagnostics block is what makes the report actually actionable.

2026-06-06 - v2.2.0

A focused bug-fix release on the back of v2.1.0 — closes seven reporter-filed bugs, smooths several internal rough edges, and substantially refreshes the Log4OM documentation now that we understand exactly what works (QSO logging) and what doesn't (Log4OM's own live frequency display).

Yaesu Web Control passed 100 downloads on 2026-06-06. Thank you to every operator who's tried it, and especially to those who took the time to file bug reports — almost every change in this release came from a real user report rather than from me hypothesising.

New features

Settings: HTTP port is now configurable, with automatic fallback. YWC was previously hardcoded to port 8080 and would fail to start if anything else (Plex, Jenkins, MiniTool ShadowMaker, etc.) had already grabbed it. v2.2.0 adds an HTTP Port field in Settings (default 8080), and at startup tries the configured port plus nine fallbacks, binding the first free one. The tray-icon tooltip and the browser auto-open URL both follow the actually-chosen port. If all ten are taken, a dialog names the owning process for each. (#13, Manuel Cobreros Gómez)
Settings: "Restart YWC to apply your changes" banner + one-click Restart Now button. Some settings (radio model, web server address, HTTP port) need a full app restart to take effect. v2.2.0 detects when these change, shows a prominent banner, and provides a Restart Now button that gracefully stops and (for the installed build) auto-relaunches YWC. (#9)
Click-to-tune now works in the waterfall. Previously you could click the live spectrum to QSY VFO A; now you can also click any signal trail in the waterfall and the radio jumps to that column's frequency. Natural way to chase a signal you've been watching drift down the screen.
Front-panel antenna change now syncs to the UI. Switching antennas on the radio's front panel now updates the YWC antenna dropdown within a couple of seconds. (The radio doesn't auto-broadcast antenna changes, so YWC polls for them.)

Bug fixes

FTdx10: IF Width dropdown off-by-one above 2900 Hz. Selecting "3.2 kHz" set the radio to 3.0 kHz; selecting "4.0 kHz" was unreachable. Missing 3 kHz entry restored to the SSB bandwidth table. (#20, Thomas OZ1JTE)
YWC was overwriting MIC GAIN and PROC LEVEL on every connect. Stored values were being pushed to the radio at startup, wiping any front-panel tweaks the operator had made. Removed all three writes — the radio is now the source of truth, and YWC reads back the current values on connect. (#16, SP3L-Jacek)
Log4OM (and other apps with spaces in their path) refused to launch. The command-line parser was splitting at the first space. Rewritten to a strict, predictable contract: wrap the path in double quotes if it contains spaces; everything after the closing quote is passed as arguments. Existing unquoted paths are auto-migrated on first read. New USER_MANUAL §7.1 documents the rule with examples. (#15, SP3L-Jacek)
SDR scan: RSPdx and RSP1A were mis-identified. HwVerToModel had model names shifted by one slot at codes 3-5 (so RSPdx showed as "RSP DUO") and was missing RSP1A's hwVer 255 entirely. Fixed to match the official sdrplay_api.h header. (#10)
Settings Save was silently doing nothing when optional fields were empty. A subtle interaction between <Nullable>enable</Nullable> and jQuery unobtrusive validation caused empty DX-cluster inputs to silently abort the form POST — no banner, no log entry, no save. The genuinely- optional fields are now nullable in the model so the client-side block doesn't trigger.
Tray-icon Exit could take 30+ seconds. Four contributing causes identified and fixed; Tray → Exit now completes in about 1.2 seconds end-to-end and the browser cleanly shows a "Yaesu Web Control has stopped" overlay.
FTdx101 Power needle disappeared after exiting YWC. During normal operation YWC sets the radio's meter to MS13 (Comp + SWR) so it can read SWR; without restoring on quit, the Power meter stayed blank. v2.2.0 sends MS01 (Power) on shutdown so the needle is back when YWC closes. FTdx101MP/D only. (Discussion #6, F1UBW / Régis)
CAT dispatcher: front-panel control changes didn't always reach the UI. Coverage now includes PA (IPO/preamp), RA (attenuator), BC (auto notch), CO (contour/APF) and AN (antenna), plus the existing handlers. (#17, SP3L-Jacek)
Power gauge jitter during transmit. Smoothing window extended from 7 to 15 samples (≈1.5 s at 10 Hz polling) to handle the steepness of the PWR calibration curve above 100 W. SWR smoothing stays at 7 samples so high-SWR faults are still seen quickly.

Documentation

Log4OM section (§9.3) overhauled. New "Known limitation — live frequency display" callout makes it clear that Log4OM's main-window frequency indicator stays OFFLINE against YWC's rigctld, but that's purely cosmetic — QSO logging via the WSJT-X → ADIF path captures the frequency correctly. Four screenshots prove it end to end.
GridTracker section (§9.4) expanded with screenshots of the General and Logging tabs.
External Applications section (§7.1) has a new path-quoting subsection with examples — including the JTAlert-with-/wsjtx pattern.
Calibration help text corrected (it was still pointing at the pre-rename AppData folder).

Known issues carried forward

Log4OM NextGen's live-frequency display still doesn't update from YWC's rigctld. Investigated extensively; this is a feature gap rather than a regression (same symptom reproducible on YWC v1.5.4). QSO logging works regardless via the WSJT-X → ADIF path documented in §9.3. Tracked as issue #18.
WSJT-X loses rig control after a frequency change on FTdx10. Reported by W1WRH against v2.1.0; appears to be an FTdx10-specific edge case in YWC's rigctld readback path. Awaiting reproduction logs. Tracked as issue #22.

2026-06-03 - v2.1.0

A "tidy up the seams" release on the back of v2.0.0 — adds the About page, system tray icon, full backup/restore, ADIF import, and a long list of UX polish + bug fixes that came out of testing.

New features

About page. New About link in the top navigation bar. Shows version, build date, copyright, project description, supported radios, and links to the User Manual / GitHub Issues / Discussions / source / sponsor. Includes a Diagnostics block (radio model, COM port, baud, browser, OS, .NET runtime, band plan, SDR device, cluster login) with two buttons:
- Copy diagnostics — puts the whole block on your clipboard
- Report a bug on GitHub — opens a pre-filled bug-report form on GitHub in a new tab (template already chosen, diagnostics already inserted; you only need to type the description)
System tray icon. A small YWC icon now appears in the Windows system tray when the app is running. Right-click for menu: Open Yaesu Web Control · About · Open user data folder · Exit. Double-click to open the browser. Provides a visible "the app is alive" indicator and a clean way to shut it down — no more Task Manager dance.
Unified backup / restore. The Settings-page backup is now a single zip containing settings, memories, memory banks, calibration overrides and label customisations. Replaces the v2.0.0 settings-only version. Atomic — every replaced file is preserved as a .bak, and the whole import rolls back if any single file fails.
ADIF memory import. Memories page gains an Import from ADIF… button. Reads any standard ADIF file (e.g. a Log4OM export), creates a memory for each unique frequency/mode pair, skips duplicates by label so re-importing is safe.
"Show only watched callsigns" toggle. New checkbox in the DX Watch popup. When ticked, the spectrum overlay and DX Spots list hide every spot that doesn't match a watch-list entry — declutter on busy bands without losing the watched-callsign alerts.
Spectrum click sets mode automatically. Click anywhere on the spectrum and the radio not only QSYs but also flips mode to match the segment (DATA-U around 14.074, USB in the SSB sub-band, CW below the digital sub-band, etc.).
Segment dropdown auto-syncs to your current frequency. Tune via the radio knob / spectrum click / on-screen keyboard — the per-VFO Segment dropdown follows.
Red band-edge guard rails on the spectrum. Dashed red vertical lines at the upper and lower edges of every amateur band in the visible window. Visually obvious when you've tuned outside the allocation.

Improvements & polish

GitHub Issues now have a template picker. New .github/ISSUE_TEMPLATE/ files give every new issue a structured skeleton (Describe / Steps / Expected / Actual / Diagnostics / Screenshots).
README gains live download / latest-release badges via shields.io.
DX cluster watch list now updates live — edit the list and the next incoming spot is matched against your new entries without restarting YWC.
Mem button is now bold black instead of pale blue — easier to read against the toolbar.
In-app User Manual now renders USER_MANUAL.md directly (single source of truth via Markdig). Edits to the markdown show up in the app on next page load, no separate Razor file to keep in sync. Heading anchors match GitHub's exactly, so TOC links work.
UTC clock info popover in the top bar — explains where the time comes from and how to verify Windows time-sync.
About / Report a bug on GitHub flow makes future bug reports two clicks (one if you're already signed in).
Browser zoom shortcuts documented (Ctrl + + / − / 0) — useful for partially sighted operators.
GNU GPL v3.0 licence explicitly named on the About page (was just "the project licence" before).
All remaining "FTdx101 WebApp" references in source / configs / scripts renamed to "Yaesu Web Control" to match the rebranding from earlier.

Bug fixes

Long-standing latent bug in the outer SignalR handler. A ReferenceError was silently swallowing every FrequencyA event past line state.lastBackendFreq.A = update.value; (the state variable was defined inside an IIFE further down the file, not in the outer scope). The frequency display was kept up to date by an unrelated polling loop in the IIFE, which is why nobody noticed — but it blocked every later addition to the FrequencyA path, including this release's segment-dropdown auto-sync.
FTdx10 SWR meter now uses the documented RM6 read directly, not the FTdx101-specific MS13+RM0 workaround. (Reported by OE5HMR.)
Settings backup endpoint rewritten to atomic zip-based flow with per-file rollback on any error.

Reminder

YWC is Windows-only.
Bug reports and discussion belong on GitHub (Issues / Discussions) — searchable, threaded, traceable. With v2.1.0, the About page's Report a bug on GitHub button makes this near-frictionless.
The user manual is comprehensive: read it from inside the app via the User Manual link in the top nav (full screenshots), or on GitHub at USER_MANUAL.md.

2026-06-01 - v2.0.0

A major-version release covering ~20 user-facing features added since v1.8.0. Worth the version bump because the app has crossed a threshold from "Yaesu control panel" to "comprehensive shack companion."

New features

DX cluster integration

Direct TCP/telnet connection to your chosen cluster server (user-selectable host, post-login command list).
Incoming spots overlaid on the spectrum display as clickable yellow callsign labels — click to QSY VFO A.
New DX Spots list panel (toolbar button) — sortable, scrollable table of cluster activity. Works whether or not an SDR is connected. Click a row to QSY.
DX Watch popup — keep a list of callsigns or prefixes (G4*, P29VR, etc.). When one is spotted, you get a draggable popup alert, an audible beep, and the spot is drawn in bright red on the spectrum.
DX cluster connection state shown as a coloured badge in the spectrum corner.

Memory channels

YWC Starter Bank: ~40 region-aware memory entries shipped with the app (FT8/FT4 watering holes, 60m channels, SSB/CW DX windows, RTTY centres, beacons). Appears as a built-in entry at the top of the Banks dropdown.
Every memory now optionally stores antenna, IF width, IF shift, roofing filter, NB on/off, NB level, NR level, AGC mode, and power — not just frequency and mode. Click a memory tile and the radio is configured exactly the way you left it.

Spectrum display

Click anywhere on the spectrum to QSY VFO A — and the mode now follows automatically (DATA-U around the FT8 watering holes, USB in the SSB sub-band, etc.).
Dashed red band-edge guard rails at the upper and lower edges of every amateur band in the visible window.
Cyan tick marks at standard CW / FT8 / FT4 / RTTY / SSB activity centres, with vertical label stacking where close pairs would otherwise overlap.

VFO controls

B→A copy and A→B copy toolbar buttons — copy the other VFO's frequency and mode without enabling split.
Per-VFO status line inside each VFO panel — band, mode, frequency, power and split state at a glance, banner-coloured to match the receiver.
Segment dropdown auto-syncs to your current frequency. Change frequency on the radio knob, the spectrum, or via the on-screen keyboard — the dropdown follows.

Accessibility / convenience

Voice announcements (Web Speech API) — optional spoken cues for band, mode, TX/RX state, manual freq entry, DX alerts and TX timeout. Designed for partially sighted operators.
UTC clock in the top bar with a click-for-details popover.
TX timeout warning banner + repeating beep when TX has been on continuously beyond a configurable threshold (default 120 s).

External apps

GridTracker launcher — joins WSJT-X, JTAlert and Log4OM as a one-click launchable app with green/red status.

Configuration

Settings backup / restore — export your full configuration as a single JSON file and re-import on another PC.
New FAQ section in the manual — first entry covers the one-time radio menu change (REAR SELECT = USB) needed for WSJT-X DATA-mode TX audio.

Bug fixes

A long-standing latent bug in the SignalR RadioStateUpdate handler was silently swallowing exceptions, blocking new features from running. Found and fixed via the segment-sync diagnostic in this cycle.
FTdx10 SWR meter now uses the documented RM6 command directly rather than the FTdx101-specific MS13+RM0 workaround. Reported by OE5HMR.
DX watch list updates take effect live without restarting the app.

Removed

The "Use USB audio for DATA modes" toggle on the Settings page. Testing in this cycle proved the CAT commands it sent were not actually REAR SELECT — the auto-config feature had never worked. Configure REAR SELECT manually on the radio (see FAQ §15.1 in the manual).

Reminder

YWC is Windows-only.
Bug reports and discussion belong on GitHub (Issues / Discussions) — searchable, threaded, traceable.
The user manual is comprehensive: read it from inside the app via the User Manual link in the top nav (full screenshots), or on GitHub at USER_MANUAL.md.

2026-05-30 - v1.8.0

Fixed / Improved

IF Width dropdown is now mode-aware. The SH command takes the same code regardless of mode but the resulting bandwidth differs per mode — in SSB code 8 = 1650 Hz; in CW the same code 8 = 400 Hz. Until now the dropdown showed SSB labels in every mode, so selecting "1.5 kHz" while in CW actually gave 350 Hz on the radio. The dropdown now rebuilds with the correct labels each time the mode changes, and the Filter Function Display uses the mode-aware width when drawing the passband.
IF Width dropdown is automatically hidden in AM and FM modes. The SH command does not apply in these modes (the radio uses fixed filters or a separate NA narrow toggle), so the row disappears rather than showing misleading SSB labels.

2026-05-29 - v1.7.1

Fixed

IF Width mapping was wrong on the FTdx101MP/D (carried over from the original v1.0 implementation). The dropdown showed 9 linear steps from 200 Hz to 3.0 kHz, but the actual FTdx101 SH command uses 22 non-linear steps with code 0 = mode-dependent default (typically 3 kHz). The labels in the dropdown did not match what the radio actually did — selecting "3.0 kHz" gave 1650 Hz, selecting "200 Hz" gave 3000 Hz. The Filter Function Display rendered the wrong passband for the same reason. Replaced with the correct 22-step table per Table 3 of the FTdx101MP/D CAT Operation Reference Manual. Identical structure to the FTdx10 fix in v1.7.0.

Thanks to Régis F1UBW for the detailed bug report with screenshots that made this reproducible.

2026-05-29 - v1.7.0

🙏 Testers wanted

I personally operate SSB and FT8 on the FTdx101MP only. I still need testers for:

FT-710, FTdx10, FTDX3000 — basic operation, split, memories, and all controls
VOX, CW Keyer, and FM Repeater — I don't use these myself; please test the popup panels and report whether the controls match the radio's behaviour

Please report any issues or feedback on the GitHub issues page. Even a quick "works fine on FT-710" is genuinely helpful.

Fixed

AF Gain silenced the radio on every startup (FTdx101MP, FTdx101D) — the app was sending AG0000; to the radio on connect when no AF Gain had been previously saved, forcing the volume to zero. Now the AF Gain is read from the radio on connect; the slider shows the radio's actual value
AF Gain slider showed 0 on page load — the slider's initial Razor value was hardcoded to 0 rather than reading from radio state. Fixed
IF Width dropdown completely wrong on FTdx10 — the bandwidth lookup table was 16 linear steps (400 Hz–3.4 kHz) when the FTdx10 actually has 23 non-linear steps with code 0 = 3 kHz (the wide default). Replaced with the correct 23-step mapping in both the dropdown and the Filter Function Display
IF Width dropdown went blank when the radio sent an unrecognised filter code — the SignalR handler now silently keeps the dropdown's last valid selection if the incoming code is not in the option list (e.g. CW-mode SH codes that don't appear in the SSB dropdown)
TX button flickered momentarily on hardware PTT — the meter polling loop was counting busy-radio null responses as "TX off", and the TX-off debounce was too short. Null responses are no longer counted, and the debounce was raised from 2 to 5 readings (~2.5 s)
Contour Filter Function Display arrow not appearing when toggling Contour on — the panel was only updating via SignalR echo; now updates immediately on click

Added

RF Gain — slider 0–255 per VFO in the receiver controls. Useful for taming overload from strong nearby signals when AGC and IPO alone are not enough. Read from the radio on connect
Squelch — slider 0–255 per VFO. Shown automatically only when the VFO is in FM, FM-N, DATA-FM, or DATA-FM-N mode; hidden in other modes. Read from the radio on connect
CW Pitch — sidetone pitch slider in the CW Keyer panel, 300 Hz to 1050 Hz in 10 Hz steps. Read from the radio on connect
TX Monitor on/off toggle — Mon button in the toolbar now toggles the TX monitor on and off (ML0 CAT command), in addition to the existing volume slider. Both the on/off state and level are read from the radio on connect
Per-band IF Width / IF Shift / Mode memory — when you switch away from a band, the app saves the current filter and mode for that band; when you return to it, those settings are automatically restored on the radio. Saved per-VFO and persisted between sessions. Have a 500 Hz CW filter on 40m and a 2.4 kHz SSB filter on 20m; the app will switch between them as you change bands
USB audio for DATA modes — a Settings checkbox that makes the app configure the radio on every connect to route DATA mode audio (FT8, FT4, RTTY, PSK etc.) through the USB audio codec rather than the rear DATA/ACC connector. Enable this if you run WSJT-X via USB and don't have the rear connector wired. Supports FTdx101MP/D, FTdx10, FT-710, and FTDX3000

Improved

Read all settings from radio on connect — the initialisation sequence now queries ~30 settings (IF Width, RF Gain, Squelch, AF Gain, MIC Gain, Speech Processor, Monitor, NR, NB, NB Level, Auto Notch, AGC, IPO, Attenuator, CW Speed, CW Pitch, CW Break-in / delay, VOX state / gain / delay) so the UI reflects the radio's actual current state immediately. The app no longer overwrites the radio's state with software defaults
IF Width read on connect (all models) — the persisted IF Width is no longer written back to the radio at startup; instead the radio's current filter is read and the dropdown updates to match
User Manual — updated to cover RF Gain, Squelch, CW Pitch, Monitor button, per-band memory, and the USB audio for DATA modes setting

2026-05-27 - v1.6.1

🙏 Testers wanted

I personally operate SSB and FT8 on the FTdx101MP only. I need testers for:

FT-710, FTdx10, FTDX3000 — basic operation, split, memories, and all controls
VOX — I don't use VOX; please test the VOX panel and report whether the controls match the radio's behaviour
CW Keyer — I don't operate CW; please test speed, break-in modes, semi break-in delay, and the M1–M5 memory keyer buttons
FM Repeater — I don't use FM repeaters; please test shift, offset, CTCSS encode/decode, and the Apply button

Please report any issues or feedback on the GitHub issues page. Even a quick "works fine on FT-710" is genuinely helpful — it tells me what I can stop worrying about.

Fixed

Radio power-off detection — the Connect button now automatically switches to red/Disconnected within a few seconds when the radio is powered off or stops responding. Previously it remained green until the app was restarted
Contour filter display — the white arrow on the Filter Function Display was not appearing when Contour was toggled on if the radio was not connected at the time of the click. Fixed; the arrow now appears immediately on toggle

Added

Pop-up panel position memory — the VOX, CW Keyer, and FM Repeater panels now remember their on-screen positions between sessions. Drag them wherever is convenient — they reappear there next time

Improved

Screen reader / NVDA — aria-label attributes added to all toolbar buttons (Mem, VFO-B, A↔B, Split, +5k, Connect, Power), clarifier controls, memories toolbar, dialog close buttons, and action buttons for consistent NVDA and Windows Narrator announcements

2026-05-27 - v1.6.0

Added

ATU Tune button — initiates a tuner cycle (AC CAT command); shows ATU On/Off state
NB Level control — noise blanker depth dropdown (1–20) inline next to NB On/Off, per VFO
TX Monitor level — monitor level slider (0–100) in the TX controls row (ML command)
Manual Connect/Disconnect button — manually connects or disconnects the CAT serial link; useful when the radio is powered on after the app starts
Connection health monitoring — the Connect button automatically switches to red/Disconnected within a few seconds if the radio powers off or stops responding, with no action required from the user
VOX pop-up panel — VOX on/off toggle, gain, hang delay, and anti-VOX sliders (VX/VG/VD CAT commands)
FM Repeater pop-up panel — shift direction, offset (kHz), CTCSS mode, and CTCSS tone selects with an Apply button (RS/RO/CT/CN CAT commands); 50 standard CTCSS tones
CW Keyer pop-up panel — speed (WPM), break-in mode (Off/Semi/Full), and semi break-in delay controls (KS/BI/SD CAT commands)
CW Memory Keyer M1–M5 — five memory message buttons in the CW panel; clicking a button sends the message via the radio's KY CAT command
CW Message Editor — M1–M5 messages are editable on the Settings page and persisted to application settings
IF Low Cut (TX bandwidth) — DSP low-cut filter select per VFO, range OFF–1.1 kHz in 100 Hz steps (SL CAT command), inline next to IF Width
Read all settings from radio on connect — app now queries ATU, VOX, FM repeater, CW keyer, and NB level on startup/reconnect so the UI reflects the radio's current state
Pop-up panel position memory — the VOX, CW Keyer, and FM Repeater panels remember their on-screen positions between sessions; drag them wherever is convenient and they reappear there next time

Improved

Screen reader / NVDA — aria-label added to all toolbar buttons, clarifier controls, memories toolbar buttons, and dialog close buttons for consistent NVDA and Windows Narrator announcement

2026-05-26 - v1.5.6

Fixed

User Manual screenshots missing — the pictures/ folder was not included in the installer, so all screenshots in the WSJT-X, JTAlert and Log4OM setup sections showed as broken images. Fixed; all screenshots now appear correctly.
Browser launch on first install — on some machines the browser opened but did not navigate to the app on the very first launch after installation. A short delay is now applied before opening the browser to ensure the web server is fully ready.

2026-05-26 - v1.5.5

Fixed

Update notification — the startup check for new versions was silently failing due to a JavaScript error, so the update banner never appeared. Fixed; users will now see a notification in the bottom-right corner when a newer version is available.
Update notification dismiss — clicking Dismiss now remembers the decision in browser storage so the banner does not reappear on every page load. It will reappear automatically when a newer version is released.

2026-05-26 - v1.5.4

Added

Speech processor control — PROC on/off button and PROC Level slider (0–100) added to the main panel alongside Mic Gain. The state is persisted and restored to the radio on startup. Available on all supported radios.
Memory panel right-click context menu — right-click any memory tile to Recall, Rename, change Mode, or Delete without opening the full editor.

Fixed

Screen reader / NVDA — frequency display no longer announces every scroll step. Only the final tuned frequency is announced after scrolling stops, preventing a rapid stream of readings.

Changed

Toolbar button order corrected to WSJT-X → Log4OM → JTAlert (the correct startup order for these applications).
In-app user manual updated: WSJT-X, JTAlert, and Log4OM setup sections rewritten with screenshots; PROC controls documented.
Exe file properties — version number, product name, company, and description are now visible on the Windows Details tab (right-click the exe → Properties → Details).

2026-05-25 - v1.5.3

New

Banks dropdown in Mem popup — switch memory bank directly from the floating Mem panel without opening the full Memories editor. The dropdown appears alongside the Save to Rig buttons and is hidden when no banks have been saved.
Startup update check — on launch the app silently checks GitHub for a newer release. If one is available a dismissible banner appears with a Download link.

Fixed

VFO A↔B Swap button missing on FTdx10 and FT-710 — both radios have full dual-VFO operation and support the SV CAT command. The Swap button is now shown on all supported models.

Changed

User manual — updated to document the Banks dropdown, startup update check, and corrected VFO swap availability.

2026-05-24 - v1.5.2

Fixed

Server freeze / ERR_CONNECTION_REFUSED — the app was shutting itself down whenever the user switched browser tabs or minimised the window for more than 30 seconds. The shutdown timer is now only triggered when the browser tab is actually closed or navigated away from.
Memory recall frequency offset (~700 Hz) — when recalling a memory channel on FTdx10 (and other modes that apply a carrier offset, such as CW), the VFO would land roughly 700 Hz from the correct frequency. The recall sequence now sets the mode first, then the frequency, so the radio applies the correct offset before tuning.
VFO-B Show/Hide toggle not responding — a duplicate click listener in the JavaScript caused the toggle to cancel itself. Fixed; the Show/Hide VFO-B button now works reliably.
Swap button entering Memory mode on FTdx10 — the Swap button sent the SV CAT command before the radio mode was set, causing incorrect VFO-B behaviour. Fixed in v1.5.3 — the Swap button is now correctly available on all models.
VDD supply voltage meter reading 44.7 V on FTdx10 — the Temperature, IDD (drain current), and VDD (supply voltage) meters are specific to the high-voltage PA board in the FTdx101MP, FTdx101D, and FTDX3000. These meters are now hidden for FTdx10 and FT-710.

Changed

User manual — updated to document meter availability by model, VFO swap limitation on single-receiver radios, the 30-second shutdown grace period and how to force-quit using Task Manager, Log4OM rigctld setup, and Omni-rig conflict note.

2026-05-22 - v1.5.1

Fixed

User manual band plans — the manual only mentioned UK and USA. It now documents all four supported plans: IARU Region 1 (Europe, Africa, Middle East — includes 4m), Region 2 (Americas), Region 3 (Asia-Pacific), and Japan (JARL), including which bands are available in each region and the 60m channel differences.

2026-05-22 - v1.5.0

Added

FT-710 and FTDX3000 support — the app now supports the FT-710 and FTDX3000 in addition to the FTdx101MP, FTdx101D, and FTdx10. Select your radio in Settings. The FTDX3000 supports split operation; the memory tag (MT) command is not available on that model.
Split frequency and Swap VFO — a Split button enables split TX/RX operation (transmit on VFO B while receiving on VFO A). A Swap button exchanges the VFO A and VFO B frequencies in one click.
Clarifier — the clarifier (RIT/XIT) offset is now displayed and controllable from the main panel.
Radio Memories panel — a new collapsible Memories panel on the main page shows a summary of your stored memories. Click Edit to open the full Memories editor.
Memories page — a dedicated page for managing radio memory channels: add, edit, and delete entries, import all channels from the radio, and export to a JSON file for backup.
Save to Mem buttons — each VFO panel has a Save to Mem button that saves the current frequency and mode to a memory channel in one click.
Memory Banks — on the Memories page you can save the current set of memories as a named bank (e.g. "Contest", "Daily"), then load or delete banks. Useful for switching between different operating setups without re-entering frequencies.
Viewport-too-narrow warning — a dismissible banner appears when the browser window is narrower than the minimum supported width, with a suggestion to zoom out. It hides automatically when the window is widened.

Fixed

Memory import returning 0 channels — the import used the recall command (MR{ch}0;) instead of the read command (MR{ch};). The radio silently ignored the recall form, so all 100 channels imported blank. All channels now import correctly.
isFtdx10 ReferenceError — a JavaScript error fired when toggling VFO-B visibility on non-FTdx10 models if the VFO-B script ran before the model variable was set. Fixed.
Memories panel drag handler hijacking Edit link clicks — clicking the Edit navigation link in the memories panel was sometimes intercepted by the drag handler. Fixed.
Memories frequency input — the memories editor was expecting raw Hz values; it now accepts MHz (e.g. 14.074) matching the rest of the UI.
Delete-all memories — deleting all memories left a stale count in the panel header. Fixed.

Changed

App renamed to Yaesu Web Control — the application was previously named FTdx101_WebApp. It is now Yaesu Web Control throughout the UI, documentation, and file paths. Settings stored under %APPDATA%\MM5AGM\Yaesu Web Control\ are migrated automatically on first run.

2026-05-17 - v1.4.0

Added

Roofing filters per model (Settings) — the Settings page now shows the correct roofing filter information for each radio. The FTdx101MP comes fully loaded with all five filters as standard (12 kHz, 3 kHz, 1.2 kHz, 600 Hz, 300 Hz) — no configuration needed. The FTdx101D has 12 kHz, 3 kHz, and 600 Hz as standard, with checkboxes to tick the optional 1.2 kHz and 300 Hz filters if installed. The FTdx10 section explains that its roofing filter is selected automatically by the radio based on DSP bandwidth and mode, with informational checkboxes for the optional YF-130CN (1.2 kHz) and YF-130CW (300 Hz) filters.
VFO-B show/hide toggle — the VFO-B button in the toolbar now works: click it to collapse or reveal the VFO B panel. The last state is remembered across sessions.
IF Width Reset button — a Reset button next to the IF Width dropdown (for both VFO A and VFO B) resets IF Width to the widest bandwidth in one click, matching the Zero button that already exists for IF Shift. (Subsequently removed — the dropdown already provides direct access to every option including the default.)
FTdx10 IF Width options — the FTdx10 now shows the correct IF Width options (400 Hz – 3.4 kHz, 16 steps), replacing the FTdx101 values that were shown previously.

Fixed

Mouse wheel tuning without clicking a digit — wheeling the mouse over the VFO frequency display no longer requires clicking a digit first. Wheeling now automatically selects the 1 kHz digit and begins tuning. Previously, wheeling without a prior click was silently ignored (felt like a lockup).
Frequency keyboard locale bug — on European locales where . is a thousands separator, NVDA would read "28.000000 megahertz" as "28 million megahertz". The announcement now strips trailing zeros (e.g. "28 megahertz" or "14.074 megahertz").
Segment dropdown double-announcement — hovering the band segment dropdown caused NVDA to announce the selected option twice (once from the live region, once from NVDA's own select handling). The live region no longer duplicates the selected option text for dropdowns.
TX-only meters not announcing a value — hovering the VDD, IDD, or Compression meter canvases before the radio had transmitted would announce the meter name only, with no reading. A "—" placeholder is now shown until the first real reading arrives.
PA Temperature showing stale value on startup — the temperature meter previously displayed the persisted value from the previous session on startup, which could appear unrealistically high if the radio had been warm. It now shows "—" until the first live reading arrives from the radio.
Roofing filter dropdown direction — the roofing filter now lists options narrow-to-wide (300 Hz → 12 kHz) to match the IF Width dropdown direction.
FTdx10 roofing filter removed from VFO panels — the FTdx10 selects its roofing filter automatically based on mode and DSP bandwidth; there is no CAT command to control it. The dropdown has been removed from the VFO panels for FTdx10 users.
Navigation bar inaccessible to screen readers on non-main pages — the navigation bar was hidden from the accessibility tree on every page (Settings, User Manual, Diagnostics, etc.), making it impossible for NVDA or Narrator users to navigate between pages. It is now only hidden on the main control panel page, where the omission is intentional.

2026-05-12 - v1.3.2

Fixed

FTdx10 Settings badge — the Current Configuration panel on the Settings page was showing an incorrect configuration for the FTdx10. It now correctly shows "100W · Single RX". The FTdx10 has two VFOs (used for split operation and easy frequency switching) but only a single receiver — it cannot receive on two frequencies simultaneously.

2026-05-12 - v1.3.1

Fixed

FTdx10 VFO B panel — the FTdx10 has VFO A and VFO B (used for split operation and memory), but only a single receiver — it cannot receive on two frequencies simultaneously. The VFO B panel is shown so that split TX/RX and memory operation are accessible.

2026-05-12 - v1.3.0

Added

Accessibility Labels editor — a new Accessibility Labels page (available from the navigation bar) provides a web-based editor for all screen reader labels. Labels are grouped into sections (Band Buttons, Meters, VFO Controls, Frequency Keyboard, Radio Controls, Spectrum Display, Navigation) and can be edited and saved without touching any files. Changes take effect automatically when you switch back to the main page. A Reset to Defaults button restores all labels in one click.
Spectrum display labels — the RF spectrum canvas and the four span buttons (250k, 500k, 1M, 2M) are now included in the Accessibility Labels editor.
Navigation bar label — the application home link in the navigation bar is now included in the Accessibility Labels editor.

Improved

NVDA meter announcements — meter gauges are now hidden from NVDA's accessibility tree (aria-hidden). An ARIA live region takes over all meter announcements. When you hover over a meter, NVDA announces the meter name (from your saved label) followed by the current reading — for example, "Amplifier supply voltage meter: 50.2 V". This fixes a long-standing bug where canvas-gauges was re-injecting its own title attribute at 10 Hz, overriding any label the user had saved.
No announcements on startup — the main control panel now uses role="application", which prevents NVDA from reading the page in browse mode on load. The navigation bar is hidden from the accessibility tree, so the list of page links is no longer announced when the app opens.
Label changes take effect without F5 — after saving labels on the Accessibility Labels page, switching back to the main page automatically reloads the labels without a manual refresh.
Frequency keyboard button — the keyboard open button now uses a numeric (⑁) icon for clearer visual identification.

Fixed

Attenuator (ATT) — the CAT command format was wrong. The FTdx101 uses a single-digit code (0–3) but the app was sending and parsing the dB values (00/06/12/18) directly. ATT changes now work correctly in both directions.
IF Width — the SH command format was wrong (missing leading zero and incorrect digit count). IF Width changes and restores on startup now work correctly.
IF Shift — the IS command format was wrong (the FTdx101 uses a sign character and absolute Hz value, not a 0–9999 linear scale). IF Shift changes and restores on startup now work correctly.
Label saves not taking effect — the browser was caching labels.json responses. The fetch now uses cache: no-cache to ensure the latest saved labels are always loaded.

2026-05-11 - v1.2.3

Added

On-screen frequency keyboard — a keyboard icon button (🖮) now appears next to the MHz label on each VFO panel. Click it to open a floating number pad for typing in a frequency directly. The keyboard pre-fills with the current VFO frequency, supports cursor movement, backspace, and clear, and validates the entry before sending it to the radio. The keyboard is draggable, resizable, and remembers its position and size across sessions. All keys have accessible labels for screen readers.
Auto-shutdown when browser is closed — when the last browser tab is closed, the app waits 30 seconds and then exits automatically. Reopening the page within those 30 seconds cancels the shutdown.
Version number in navbar — the current app version is now shown in the top-left corner of every page.

Fixed

AppVersion display — the version was showing as "vunknown" due to disabled assembly attribute generation. Now reads from a simple constant that is updated alongside the installer version.

2026-05-11 - v1.2.2

Fixed

Installer no longer requires .NET 10 — the app is self-contained and bundles its own runtime. The installer was incorrectly blocking installation on machines without a system-wide .NET 10 installation.

2026-05-10 - v1.2.1

Fixed

Calibration data location — calibration.user.json was being written to the wrong AppData subfolder (MM5AGM\FTdx101\WebApp\ instead of MM5AGM\Yaesu Web Control\). It now lands in the correct folder alongside appsettings.user.json and radio_state.json.
Labels file — labels.json is now copied to %APPDATA%\MM5AGM\Yaesu Web Control\ on first run so users can easily locate and edit it.

2026-05-10 - v1.2.0

Added

FTdx10 support — the app now works with the Yaesu FTdx10 as well as the FTdx101MP and FTdx101D. Select FTdx10 in Settings to enable it.
- VFO B panel and its toggle button are hidden automatically (the FTdx10 has one VFO).
- Power slider limited to 100 W.
- SDR Settings page shows a notice that the FTdx10 has no rear-panel IF output.
Band button keyboard navigation — Tab moves focus into the band group; Left/Right arrow keys move between bands and switch immediately. Correct radiogroup ARIA semantics applied.
User manual — comprehensive built-in user manual covering all features, external application setup, meter calibration, diagnostics, and accessibility.
Diagnostics page — live meter readings table (raw 0–255 values, CAT command, last-updated time) and a scrollable SignalR event log with per-property filtering, pause, clear, and save-to-file controls.

Fixed

SWR calibration — corrected to use the reflection-coefficient formula so SWR readings now scale accurately from raw CAT values.
Band button screen reader support — NVDA and Windows Narrator now consistently announce the full band name (e.g., "20 metres, radio button") when hovering over or focusing a band button. Previously NVDA would sometimes read the short label ("20m") or nothing.
Accessible labels — removed abbreviations that caused screen readers to mispronounce meter names (e.g., "PA" expanded to "Power Amplifier" by NVDA).

Changed

SDR Settings — description updated to clarify that the FTdx10 has no IF tap, and that an antenna-connected SDR will show absolute RF frequencies rather than a VFO-centred view.

2026-04-22 - v1.1.0

Fixed

AF Gain slider — no longer jumps back to its previous position after release. The slider now sends the CAT command directly to the radio instead of only updating internal state.

Added

IF Shift zero-reset button — a Zero button next to each VFO's IF Shift slider resets it to centre instantly.

Changed

IF Width and IF Shift values are now persisted across restarts and restored to the radio on startup.
Slider appearance — Power, MIC Gain, and AF Gain sliders now use the native browser appearance for a cleaner, more consistent look.
Auto Notch / Man Notch dropdowns widened so the full option text is visible without the dropdown arrow overlapping it.

2026-04-21 - v1.0.0

Added

Band segment dropdown — each VFO now has a Segment selector (CW / FT8 / SSB / RTTY) that tunes directly to the standard frequency for that segment on the current band. UK and USA band plans are selectable in Settings. 60m shows named channels. Last-used segment per band is remembered across sessions.
Noise Blanker (NB) — ON/OFF control added to both VFO panels alongside NR.
Manual Notch frequency slider — continuously adjustable 10–3200 Hz slider added below the Manual Notch on/off control for both VFOs.
Spectrum crosshair — hover over the spectrum to see the exact RF frequency at the cursor position.

Changed

CAT initialisation sequence trimmed from ~100 commands to 43, reducing startup time.
Band plan (UK/USA) setting added to the Settings page.

2026-04-17 - v0.9.0 RC1

This is a release candidate for what may be the final major release. Please test and report any issues via the GitHub issues page.

Added

Spectrum display and waterfall — real-time spectrum and scrolling waterfall via SDRplay RSP1 (or any SoapySDR-compatible device) connected to the FTdx101MP 9 MHz IF output.
- Variable span: 250 kHz, 500 kHz, 1 MHz, or 2 MHz
- Click on the spectrum to tune VFO A to that frequency
- Mouse wheel over the spectrum tunes VFO A up/down in 1 kHz steps
- Frequency axis labels track VFO A in real time
- Centre frequency displayed at the top of the spectrum

Changed

Layout compacted throughout to fit on a single screen without scrolling
Mic Gain slider moved alongside Power slider
AF Gain slider moved alongside Roofing Filter for both VFO A and VFO B
Copyright notice moved into the navigation bar
Application buttons row and navigation bar made more compact

2026-04-10 - v0.7.7

Changed

Meter gauges repositioned above the VFO panels

2026-04-06 - v0.7.6

Changed

Minor fixes and improvements
Ctrl + F goes to full screen, ESC to get back to normal
Updated main page screenshot to reflect new VFO controls layout.

2026-04-06 - v0.7.5

Added

VFO controls panel — new two-column controls section alongside the band buttons for both VFO A and VFO B:
- AGC — OFF / FAST / MID / SLOW / AUTO
- IPO/AMP — IPO / AMP1 / AMP2
- ATT (Attenuator) — OFF / 6 dB / 12 dB / 18 dB
- NR (Noise Reduction) — OFF / NR1 / NR2
- Auto Notch — OFF / ON
- Man Notch (Manual Notch) — OFF / ON
All six controls are fully two-way: changes made on the radio front panel are reflected in the app automatically via CAT AI mode.
Control values are persisted and restored on startup.
Buy Me a Coffee donate button added to the toolbar (PayPal).

Changed

Frequency display moved below the S-meter/band buttons row to free up horizontal space for the new controls panel.
VFO controls layout uses a compact two-column grid with bold labels and values.
Selects return to normal appearance immediately after a value is changed (no lingering highlight).

2026-04-06 - v0.7.4

Changed

Minor fixes and improvements

2026-04-05 - v0.7.2

Changed

Refactor frontend: consolidate SignalR handlers and add orchestrators layer
Release script works

2026-04-01 - Major Rewrite Foundation

This release marks a near-complete rewrite of the application.

Changed

Front-end architecture migrated to ES module-based structure.
Gauge rendering moved to class/factory modules for clearer extension points.
UI behavior split into focused modules to reduce monolithic script complexity.

Improved

Clearer separation between CAT polling, UI rendering, and calibration logic.
Better maintainability for adding new controls and gauges.
Lower risk of regressions when updating individual UI features.

2026-04-03 - Meter and Calibration Updates

Added

New gauges: Compression, IDD, and VDD.
Full multi-gauge calibration editor page with per-gauge cards.
Per-gauge Save buttons in addition to global Save Calibration.
TX control button on the Meter Calibration page.

Changed

Lower-row gauge order updated to: SWR, Power, Compression, ALC, Temp, IDD, VDD.
Calibration schema normalized to use Radio point values consistently.
Calibration storage routing now supports:
- Development save target: wwwroot/calibration.default.json
- User save target: %APPDATA%\\MM5AGM\\FTdx101\\WebApp\\calibration.user.json

Fixed

IDD meter polling corrected to dedicated CAT command path.
Power display rounding now uses integer output (no decimal noise).
Gauge title/value width stability improved to prevent label width jumping.
Compression/ALC behavior aligned to TX state to reduce idle-mode jumping.
AF Gain confirmation tolerance and timeout adjusted to reduce false revert alerts.

Name		Name	Last commit message	Last commit date
Latest commit History 820 Commits
.claude		.claude
.github		.github
Controllers		Controllers
Grammars		Grammars
Models		Models
Pages		Pages
Properties		Properties
Services		Services
Tests		Tests
Workers/Yaesu_Sdr_Worker		Workers/Yaesu_Sdr_Worker
docs		docs
pictures		pictures
scripts		scripts
soapysdr-dist		soapysdr-dist
wwwroot		wwwroot
.gitignore		.gitignore
.release-please-manifest.json		.release-please-manifest.json
Audit.md		Audit.md
CALIBRATION.md		CALIBRATION.md
CHANGELOG.md		CHANGELOG.md
CLAUDE.md		CLAUDE.md
CNAME		CNAME
LICENSE		LICENSE
Plan.md		Plan.md
Program.cs		Program.cs
README.md		README.md
RadioHub.cs		RadioHub.cs
USER_MANUAL.md		USER_MANUAL.md
VOICE_CONTROL.md		VOICE_CONTROL.md
Yaesu_Web_Control.csproj		Yaesu_Web_Control.csproj
Yaesu_Web_Control.slnx		Yaesu_Web_Control.slnx
appsettings.json		appsettings.json
generate-icon.ps1		generate-icon.ps1
index.html		index.html
installer.nsi		installer.nsi
libman.json		libman.json
radio_state.json		radio_state.json

Folders and files

Latest commit

History

Repository files navigation

Yaesu Web Control

Main Page

VOX, CW and FM Repeater Panels

Calibration Page

⚠️ Warning

📖 Why This Application Exists

🌱 Why Sponsorship Matters

Important - .NET 10 is now built into this app so there is no need to download and install it.

⚠️ Windows Security Warnings on First Install

📡 Spectrum Display

⚠️ SDR safety — read before connecting

Why two SDRs? (and why two RSP1Bs rather than one RSPduo)

Why an SDRplay RSP, not a £25 RTL-SDR dongle?

What's that brief pause when I change the span?

Project direction

Which radios get tested?

Staying informed about updates

Release Notes

2026-07-10 - v2.4.1

Settings page silently failing to save (#65)

English (US) voice control language pack

2026-07-10 - v2.4.0

Headline feature — Voice Control v1

Dual-VFO S-meter gauge restored

Frequency ▲/▼ buttons now repeat while held

Spectrum display — draggable splitter

Fullscreen shortcut no longer hijacks browser find (Ctrl+F)

Fldigi launch button (#52)

PROC button + level slider now actually drive the radio (#51)

Audio Filter popout (replaces broken IF Low Cut)

SDRplay API auto-detect + install-path Settings field (#53)

ZIN button for CW (#55)

Spectrum click — crosshair follows the clicked frequency

Spectrum display — Low/High/Gain sliders for noise-floor tuning (#53)

VC Tune preselector hidden for hardware revisions that don't support VT CAT (#59)

DX Spots list — click now sets mode as well as frequency (#57)

Esc key now closes the Memory panel (#61)

2026-06-22 - v2.3.9

Single-receiver radio UI — R1–R12 fully landed

Frequency display accessibility — Yuri W4YSW

Radio-state init fixes (Jacek SP3L #38–#47)

Other improvements

2026-06-17 - v2.3.8

Single-receiver radio UI rework (FTdx10, FT-710, FTDX3000, FT-991A)

Filter scope display improvements

Other fixes

Bug fix

Diagnostics page improvements

2026-06-15 - v2.3.7

New features

User interface — single-receiver radios

Accessibility

Bug fixes

Calibration

Documentation

Update post-release

2026-06-12 - v2.3.6

Bug fixes

Other fixes

Documentation

2026-06-11 - v2.3.5

Bug fixes (all in the Test Connection flow)

2026-06-11 - v2.3.4

Bug fix

2026-06-11 - v2.3.2

Bug fix

2026-06-11 - v2.3.1

Build pipeline fix

2026-06-11 - v2.3.0

Headline feature — Dual-SDR

Other new features

Bug fixes

Settings file migrations (silent, no user action)

Architecture (under the hood)

Reporters credited

2026-06-09 - v2.2.2