Skip to content

Known Bugs ​

Active issues + workarounds. Maintained by hand; reported bugs land in the bugs@funkwelt.net inbox.

Active ​

  • HRDLOG.net upload (new in v1.46.0) is being road-tested. Auto-upload, backfill and the status column are implemented and the response parser is tested against the documented server replies — but a test against a live HRDLOG account is still pending (HRDLOG's upload-code mail delivery was broken at release time). If you have an account: feedback to bugs@funkwelt.net is very welcome. With a wrong upload code, auto-upload pauses automatically.
  • Rotator control (new in v1.29.0) is still being road-tested. The logic, the embedded rotctld binary and the 22 model profiles are covered, but a test against real rotator hardware is still pending — feedback from users with a rotator connected is very welcome. For USB: plug the rotator in via a USB-serial adapter, pick the model under Settings → Rotor (serial parameters are pre-filled and stay editable), select the port, connect. The preset serial defaults come from Hamlib; if your controller differs, they can be adjusted per configuration. If a connection fails, check the port, baud rate and model number first.

Fixed in v1.63.0 — 2026-11-13 ​

  • CAT: The IC-705 WLAN connection dropped after a few minutes ("CI-V channel no longer responds", followed by auto-reconnect). The radio's retransmit requests for whole ranges were answered only at the end points.
  • CAT: The Xiegu G90 (and other Icom-compatible rigs) connected briefly and disconnected at once, in a loop. During connection setup the app now waits once, up to 8 s, for the first mode reply.
  • CAT/Rotor: rigctld and rotctld kept running after a crash or force quit and held the serial port and TCP port (4532/4533).
  • CAT: The settings showed a green status next to a configuration that was not the connected one; the status now names the connected configuration.
  • Winlink: The bundled ardopcf kept running after a crash or force quit and held the audio device and TCP ports.
  • Winlink: Cancel in the middle of the level assistant's two-tone signal could leave the transmitter keyed.
  • Logbook: The banner shown after clicking a cluster spot took a row of its own; Notes and DX de slipped out of view.
  • Logbook: The F-macro buttons were considerably taller than the voice buttons V1–V4.
  • Logbook: Grey F buttons reported "No SSB recording" without naming the profile in which it is missing.
  • Radio/CAT panel: The status row of the active radio showed a selection arrow with nothing behind it.
  • FT8: The FT8/FT4 switch was greyed out during reception without explanation.

Fixed in v1.62.0 — 2026-11-06 ​

  • DX cluster: Callsigns with prefixes outside the old 180-entry table (JF, JG, JI–JQ, 7J–7N, BH, BI …) showed as "Unknown" without a position on the map. The lookup now uses the AD1C country file.
  • DX cluster: Spots whose spotter could not be resolved bypassed the spotter radius; at 500 km Chinese spotters appeared. They are now hidden.
  • DX cluster: The spot time of pota.app spots (no time zone given) was discarded, the time column stayed empty and could not be sorted.
  • DX cluster: Every open bandmap redrew on every spot regardless of band; with three bandmaps in a contest, three times per flush.
  • Logbook: ATNO pill and DXCC counter compared country names; "Germany" (QRZ) and "Fed. Rep. of Germany" (spot) counted as two countries, and a DL spot could light up as ATNO. The DXCC code now decides.
  • Log analysis: Contest QSOs without locator and without LAT/LON were missing from the map ("0 with position"). They now appear at the country centre, marked as estimated.
  • FT8: The reply to a CQ from your own period only went out two slots later; the Tx clock is now replanned immediately on a period change.
  • FT8: "Start/stop receiving" existed twice (header and "Operation" section).
  • Settings: After a restart the Wavelog upload showed "Not configured" until you pressed "Test connection"; QSOs silently did not reach Wavelog. With one operator profile the saved settings now apply at start.
  • CAT: The IC-705 WLAN password was stored in plain text in the settings; it now lives in the keychain, migrated on first start.
  • Keychain: Migrating plain-text credentials deleted the old values even when writing to the keychain failed.
  • Forecasts: The footer claimed D-layer absorption was not taken into account although the traffic light includes it since this version.
  • Licences: For FFTW "MIT" was read as the licence instead of the institute, the claim of a bundled wsprd source archive was wrong, the ardopcf overview had the wrong file name; several full texts were missing.

Fixed in v1.61.2 — 2026-11-02 ​

  • CAT: With an IC-705 Wi-Fi configuration and "Connect automatically at launch", the app crashed about a second after launch when the radio could not be reached at the stored IP (e.g. new DHCP address) – without a crash report, and the IP could no longer be corrected. The sockets are now protected against the triggering signal; the app reports "Connection to the radio failed" instead.

Fixed in v1.61.1 — 2026-11-01 ​

  • FT8: The message field was preset to CQ POTA … when the module opened and the CQ menu only offered POTA – regardless of the CQ modifier field and the log type. A manual call via Transmit therefore always announced POTA. The transmit text now follows the modifier and the log like Tx6 and the auto-sequencer.

Fixed in v1.61.0 — 2026-10-31 ​

  • CAT: Every input in the CAT window was written straight into the active configuration; a quick test with another model overwrote it with no way back. Now it is only saved with Save or Save as….
  • DX cluster: Digimode spots (FT8, FT4, JS8, PSK, VARA, FreeDV) below 10 MHz switched the transceiver to LSB-D, where the signals cannot be decoded; SSB spots on 60 m to LSB instead of USB.
  • DX cluster: FT8/FT4 spots tuned to the signal frequency instead of the dial frequency; words like "TEAM" or a locator like "FM18" in the comment switched to AM or FM.
  • FT8: The radio was only set to dial frequency and data mode on a band change, not when opening, connecting or starting to receive.
  • Winlink: Cancel while calling let the modem keep transmitting for up to 20 s (ARDOP) or 60 s (VARA).
  • Windows: Closed single windows (DX map, DX cluster, band plan and others) kept computing invisibly and cost CPU.
  • CAT: S-meter and clocks made the logbook window re-measure its size several times per second (14 % CPU with a transceiver connected).

Fixed in v1.60.0 — 2026-10-25 ​

  • Logbook: Under contest load (cluster with many spots, CAT connected) the UI was sluggish, clicks in the spot list landed late and the app sat at 25–50 % CPU. The cause was a re-layout of the whole logbook window on every change of an app object (S-meter, voltage, spot flush).
  • CAT: The supply voltage was written to the radio state on every poll even when unchanged, triggering needless redraws.
  • DX cluster: The spot cache was written synchronously in the foreground every 25 spots, stalling rendering.

Fixed in v1.59.0 — 2026-10-25 ​

  • CAT: When switching the active configuration (e.g. TS-2000 → IC-7300) the brand/model pickers overwrote the new configuration with the factory values of the old brand's first model — CAT went nowhere.
  • DX cluster: Despite the fix in 1.58.0 the propagation indicator could turn green without a fresh spotter or with a single nearby one (grayline, time of day, solar flux); model values now lift to yellow at most.
  • Logbook: A QSO edited after the upload silently differed from QRZ, Club Log, eQSL, LoTW, Wavelog and HRDLOG; it is now flagged and resent (schema v23).
  • Logbook: DXCC, WAS and WAZ counters counted eQSL as confirmation; now only LoTW or a paper card.
  • Contest: A wrongly assigned operator could only be corrected via "Assign OP"; the QSO editor now has an operator field.
  • Contest: The Super Check Partial search ran synchronously over all callsigns on every keystroke and made typing sluggish.
  • Spot list: New spots pushed the rows away under the mouse and the click hit the next station; the list now holds still.
  • CPU: Contest and outdoor forms, macro row, spot tables, dupe/MULT marking and the cluster filter recomputed completely on every CAT poll or spot flush (around 40 % processor load in a contest).

Fixed in v1.58.0 — 2026-10-23 ​

  • DX cluster: The propagation indicator turned green with a single nearby spotter or repeated reports from the same spotter; it now needs fresh spots (15 min) from different nearby spotters.
  • Logbook: A spot put POTA/SOTA into the DX form as your own reference (MY_SIG) — and reported it that way to QRZ, Club Log and LoTW —, WWFF was lost, and a spot without a reference kept the previous one. Existing QSOs are not changed.
  • Logbook: An IOTA entry was lost (now its own field, schema v21).
  • Logbook history: The band filter listed "20M" and "20m" twice and sorted alphabetically instead of by frequency.
  • Clocks: UTC clocks, the running "Time On", the auto-refresh of LLOTA/GMA spots and the 30-s clock in the FreeDV module could stand still.
  • FT8: Transmissions to partners with special or prefixed callsigns (DL2024E, HB9/DL1ABC) were not counted — Tx2 ran until the watchdog, no completion after RR73. A portable log sent the home locator. A caller who stopped answering was put back at the end of the queue.
  • Update check: The "up to date" message showed the server's date instead of the app's own version and build.
  • Outdoor status: Grouping the activations was slow for large logs.

Fixed in v1.57.0 — 2026-10-15 ​

  • DX cluster: The separate map window (⇧⌘M) drew neither the QTH marker nor the path line; spotter lines broke at the date line; the solar flux came from the oldest instead of the newest NOAA entry; the propagation indicator mixed spotters from different bands; lower-case POTA/SOTA/WWFF/WCA references in comments were not recognised; a full callsign from the DXpeditions list marked every spot with the same prefix.
  • Grayline: The window ("LIVE") and the map terminator stopped advancing.
  • Contest: Live scoring, Cabrillo and EDI used the global instead of the log callsign; the factory macro F2 sent the report twice; CW macros picked up hidden fields; the serial number restarted at 001 after an ADIF import; "20M" and "20m" counted as two bands in statistics, header and map filter; a template with field width 0 made the field disappear.
  • Logbook: "Backup + Delete" deleted even when the ADIF backup failed; the QRZ confirmation sync lost matches on a log switch; the LoTW sync checked only the open logbook and the "Mark QSL via LoTW sent" switch had no effect (same for the Club Log switch); the history map stayed empty with a foreign filter; "Top 10 DXCC" counted "Unknown" and spelling variants separately.
  • Outdoor: SOTA/POTA/WWFF live counters did not follow the programme rules; the SOTA chaser CSV had shifted columns; an older SOTA response could overwrite a newer fetch.
  • Voice macros: Stop did not reliably prevent keying, consecutive macros interfered; a recording kept running after closing Settings.
  • QTH locator: Clicking a marker moved the other station; after dragging, line and area stayed put; "Fit path" showed only one station at equal latitude or longitude; the English legend showed "60 %%".
  • Calculators: The common-mode choke calculator crashed at coax diameter 0, the ATU wire calculator at very long lengths.
  • CAT: The app's own rigctld/rotctld survived the app as an orphan and kept port and serial device busy.

Fixed in v1.56.0 — 2026-10-10 ​

  • Logbooks: a missing or empty logbook path could create an empty file that then triggered “Logbook could not be opened” on every launch; logs that failed to open silently vanished from the list.
  • Outdoor wizards: “HB/AG-001, HB/AG-003” or two WWFF references in the main field produced a combined session; QSOs were assigned to several summits.
  • Outdoor export: WCA/GMA logs with several references ended up in one file, files with the same name from different programs overwrote each other, BAND could be invalid, omitted QSOs were not reported; the SOTA export ran without your own callsign.
  • Contest: IARU HF did not score the received ITU zone; after switching log or template, old input stayed in the form, and the operator of the previous log could be written into the new log’s QSOs.
  • Lookup & upload: LoTW sync did nothing, the upload status did not reach the originating log; an “&” in a QRZ upload truncated fields; a hanging callbook server left the spinner turning forever.
  • CAT: Icom frequencies beyond the BCD width were sent garbled; an IC-705 Wi-Fi configuration required a serial port; after a reconnect, replies from the old connection could be applied.
  • Rotator: elevation was reset to 0 on every move; with a north offset the mechanical range was limited incorrectly.
  • SSTV: transmitting was possible without a usable TX device, and a double-click started twice. WSPR: receive reports were lost when changing bands.
  • Schedules mixed local time and UTC; save errors went unnoticed.
  • Band plan: frequencies in segment gaps were assigned to the first sub-segment. Grayline terminator and SOTA points in Awards corrected.
  • Helper windows (Grayline, Band Plan, Cluster …) could be opened several times; “Settings…” appeared twice in the menu.
  • Calculators: the magnetic loop voltage was wrong; broken NEC files could disrupt the simulator.

Fixed in v1.55.0 — 2026-10-03 ​

  • Winlink: closing the Compose window discarded unsaved changes, a double-click on “Put in Outbox” queued the message twice, and deleting in the trash did not ask first.
  • Winlink: with PTT via the CAT connection a keying or unkeying error went unnoticed; with CAT disconnected the session started without keying. The level assistant and a radio session could run at the same time, and connecting from the gateway window transmitted without a visible cancel.
  • Winlink: “Reply” in Sent/Outbox/Drafts went to yourself; refreshing the gateway list within the one-hour limit did nothing visible; “Production”/“Test server” did not restore a changed port.
  • ⇧⌘R had two meanings (Reset CAT and Winlink “Send & Receive”); Reset CAT is now ⌃⇧⌘R.
  • Contest map up to 100 % CPU with large logs (since 1.54.0); program maps with stale popups, no re-centring on log switch and silently omitted QSO lines.
  • After switching the log type, the old program map stayed open without a highlighted tab.
  • Bandmap: stacked callsign labels, legend covering the plot, missing bands in the quick selector and “New bandmap”.
  • Schedules: the countdown showed local time while the card next to it showed UTC.
  • An invalid locator (e.g. “ZZ99” from an ADIF import) could crash a map.
  • Band plan: the WARC filter showed 60 m as well in R1 and nothing in R2/R3; the frequency lookup gave no feedback.
  • License: an invalid input replaced a valid license and switched to demo mode.
  • Demo limit: QSOs from WSJT-X & Co. were dropped silently, SSTV wrongly reported “logged”.
  • Mail links: “&”, “=”, “+” or “?” in the text cut off bug reports, license requests and renewal mails.
  • Update: quitting while the app was being replaced could leave an incomplete bundle; signature errors appeared as “UpdateError error 2”.
  • Keychain: a failed save could delete the previous entry (Winlink, Lookup & Upload, Operators); the settings export went ahead despite unreadable credentials.
  • Settings: Station, Operators, cluster port, rotor network port and spot frequency accepted invalid values. An emptied cluster list refilled itself after a restart; cluster commands could go to a node that was not connected.
  • Macros: a cancelled re-recording deleted the previous recording; preview could not be stopped.
  • The third-party overview listed four instead of five helper programs; numerous German leftovers in the English interface translated.

Fixed in v1.54.0 — 2026-09-27 ​

  • Correct WAS state persistence/counting; UTC year and band grouping in statistics.
  • Clear save/load failures for memories and QSO/eQSL images.
  • Hunter ADIF without an own reference; Cabrillo/EDI warnings before export.
  • Stale History/Bandmap selections removed, narrow-window controls improved and numerous English labels/dialogs completed.

Fixed in v1.53.0 — 2026-09-26 ​

  • CAT menu reflects the connection state.
  • English status text, tooltips and contest operator dialogs completed; DEV localization packaging fixed.
  • Contest operator management remains accessible with an empty operator list.

Fixed in v1.52.0 — 2026-09-25 ​

  • Full VHF frequency display in the logbook and a larger QRZ photo popup.
  • Settings remain resizable after reopening.
  • 6 m/4 m always selectable, correct FreeDV spot mode and POTA selection matching source availability.
  • Clear empty-state messages; radius and follow-radio filters remain accessible and can be reset in the logbook.

Fixed in v1.51.0 — 2026-09-19 ​

  • QSO edits refresh the callsign sidebar and the context of visible table cells correctly.
  • Different path spellings or symbolic-link aliases no longer load and count the same log file multiple times.
  • Newly created logs are remembered as the last opened log; adding an existing .htlog file refreshes global awards immediately.
  • Failed saves retain form input. Entry forms report success only after saving succeeds; the edit dialog remains open on failure.
  • ADIF reimport preserves SFI, K and A indices and complete own multi-SOTA references. An additional HAM-Tools field retains the summit list while the standard SOTA field remains a single reference.

Fixed in v1.50.0 — 2026-09-17 ​

  • SSTV send on Yaesu: rig keyed but no audio/ALC — in USB/LSB the modulation comes from the microphone. The app now switches to DATA-U via CAT before sending and back afterwards ("Data mode while sending" toggle, on by default).
  • SSTV receive silent on dual-receiver rigs (FTDX-101, FTX-1): audio was on the right codec channel, the app read the left one only. Now picks the louder channel automatically.
  • SSTV receive without microphone permission only reported "no audio" — now a banner with the cause and a button into System Settings.
  • SSTV tones came out of the Mac speaker when no TX device was selected — the Send card now warns above the PTT button.

Fixed in v1.49.0 — 2026-09-12 ​

  • No fixes — pure feature release (FreeDV: double-click stays, Radio/CAT panel).

Fixed in v1.48.2 — 2026-09-12 ​

  • FreeDV Reporter: 80–100 % CPU once connected — every server event (heartbeats from 75 stations) re-rendered the whole view and rebuilt the table. Events are now coalesced (max. 1/s, only on visible changes) and the table reloads only changed rows.

Fixed in v1.48.1 — 2026-09-12 ​

  • FreeDV receiver: 100 % CPU with the decoder running, app unusable — the whole FreeDV view was re-rendered on every level update. The "Reception" panel is now its own view, updates throttled.
  • Reception panel: "Stop" was not translated in the English UI.

Fixed in v1.48.0 — 2026-09-12 ​

  • No fixes — pure feature release (RADE receiver in the FreeDV module).

Fixed in v1.47.1 — 2026-09-12 ​

  • No fixes — pure feature release (frequency arrow buttons in the Radio/CAT panel).

Fixed in v1.47.0 — 2026-09-03 ​

  • No fixes — pure feature release (FreeDV module, SUBMODE, help audit).

Fixed in v1.46.1 — 2026-08-31 ​

  • The settings import was overwritten again on app quit — the imported values were gone after the restart. The import now locks all write-back paths and quits the app after the success alert; simply repeat the import with 1.46.1.

Fixed in v1.46.0 — 2026-08-31 ​

  • The «configured?» indicator of the QRZ/HamQTH lookups read from the wrong settings domain. It only worked because older app versions had left copies there. Fixed as part of the keychain migration.

Fixed in v1.45.2 — 2026-08-31 ​

  • CAT via «Network (rigctld)» failed with wfview. wfview's rigctld server reports frequencies in float format («21078000.000000») instead of whole hertz — HAM-Tools rejected the response, and after several connection attempts the misleading message «No rigctld reachable» appeared, even though the TCP connection was established. Frequency and passband are now parsed tolerantly (integer first, float as fallback). Every wfview setup was affected; Hamlib's own rigctld was never affected.

Fixed in v1.45.1 — 2026-08-28 ​

  • Yaesu FTX-1: the TUNE button did not start a tuning cycle. The FTX-1 defines the tuner command differently than the FT-710/FTDX-10 — the previously sent AC002; is invalid there and was silently ignored by the radio. The FTX-1 profile now sends AC103; (tune start for the internal, INT-FAST and external tuner; verified on real hardware). An ATAS antenna is not covered yet. The tuner type must be selected on the radio for the active antenna — the button only starts the cycle.

Fixed in v1.45.0 — 2026-08-18 ​

A pure feature release (WSPR filtering and measurement sessions). Two things were straightened out along the way that felt like bugs in practice:

  • The clock warning depended on the current selection. The estimated clock offset was derived from the spots currently on screen. With the new time filter that would have meant: look at a measurement from the day before yesterday and you are told forever about a clock that was wrong back then — while one that is wrong today goes unreported. The estimate now deliberately looks past the filter, always at the most recent receptions.
  • The header counted something other than the list below it. It showed the total contents of the database while the list showed an excerpt. Both figures now refer to the same time range; the total is in the tooltip.

Fixed in v1.44.0 — 2026-08-16 ​

A pure feature release (WSPR module). Two fixes are included nonetheless, both outside WSPR and found while building the module:

  • USB-D was not being set on Icom radios over the network connection. On Icom sets the data mode is not a mode of its own but USB plus a flag sent as a second command — that was missing, so the radio stayed in voice mode and took its audio from the microphone instead of the USB codec. This affected Winlink too, which announces the same switch.
  • The PTT stayed keyed when the app quit. If HAM-Tools was closed during a transmission it dropped the radio connection but never released the keying — the transmitter would have been left sending a continuous carrier. This affected SSTV and Winlink too.

Fixed in v1.43.0 — 2026-08-15 ​

Antenna calculators — all 17 recomputed against the NEC2 engine, ten corrected:

  • Yagi: the velocity factor sat on top of factors that already are build dimensions. The front-to-back ratio of the 3-element version dropped from 27.7 to 4.7 dB as a result.
  • Moxon: the same error with a stronger effect — the front-to-back ratio inverted, the antenna radiated backwards, at an SWR of 18.
  • Magnetic loop: the radiation resistance was 158 times too large (area coefficient applied to the circumference). Efficiency and bandwidth were far too optimistic as a result.
  • Ground plane: the 36 Ω shown belongs to the ground-mounted monopole; the elevated version with four horizontal radials sits at 21 Ω. The velocity factor was the same for every droop angle, leaving the horizontal variant with 33 Ω of reactance.
  • Windom: "200–300 Ω" was a harmonic-band figure, not a fundamental-band one.
  • J-pole and Slim Jim: the feedpoint sat too low, and no amount of moving the tap could compensate, because the length was wrong.
  • Dipole: the impedance range was too narrow at the upper end.
  • EFHW: the 2450 Ω shown was 49 × 50, derived backwards from the assumed transformer.
  • Hexbeam: the feedpoint was stated as 50 Ω; measured it is 28–32 Ω.
  • Spiderbeam: the performance figures applied to neither of the two calculation modes.

Antenna simulator:

  • Ground-mounted antennas were not bonded to ground. A wire ending at z = 0 counted as hanging free — with no error message, only wrong numbers. The bundled templates are all elevated and were unaffected.
  • Lumped components acted multiplied by the segment length instead of at the value entered. Changing the segment count silently changed the antenna along with it.

Fixed in v1.42.0 — 2026-08-15 ​

  • The apex delta in the loop calculator used the wrong ratios. 18/41/41 gives barely 22 Ω instead of the promised 50 Ω. Recomputed and corrected to 24/38/38; the flat 40/30/30 variant has been dropped.
  • The quad loop, dipole and inverted-V simulator templates were not resonant. They followed the rounded rule of thumb instead of measured figures. Every template has now been recomputed against the engine.
  • The band plan page of the web version had been broken since the band data was restructured — it read a structure that no longer existed. Because that also broke the rebuild of the entire web version, toolbox.funkwelt.net had been stuck on its early-June state.

Fixed in v1.41.0 — 2026-08-15 ​

  • The antenna simulator would not start without internet. It loaded the web version; without a connection all you got was “not reachable”. The compute core is now inside the app.
  • In the radiation pattern the azimuth cut sometimes pointed the wrong way. NEC2 also emits negative zenith angles, and a negative angle points where the positive one with azimuth + 180° points — for a Yagi the main lobe was therefore drawn backwards. The numbers gave no hint of it.
  • In the elevation plot the forward and backward lobes lay on top of each other, because the absolute value of the angle was used.
  • The delta loop template was not resonant. The 1005/f rule of thumb applies to the horizontal full-wave loop; the equilateral triangle fed in its bottom side needs about 1.066 λ of perimeter.

Fixed in v1.40.3 — 2026-08-15 ​

  • The License area in the settings could not be opened. With fourteen tabs the tab bar no longer fitted the window; “External Loggers” and “License” ended up in a » menu whose entries are not clickable. Anyone installing HAM-Tools fresh could not reach activation. The areas now sit in a sidebar, which cannot overflow.

Fixed in v1.40.2 — 2026-08-13 ​

  • The automatic QSY failed whenever the chosen gateway was not the last one used. The connect dialog wiped its own channel selection on opening; without a channel there is no dial frequency and therefore no retune. A second attempt at the same gateway then worked — which is why the fault looked random.
  • The quick path “Receive & send → over ARDOP” showed no frequency, because the remembered gateway was lost along with it.
  • The last channel used was missing from the connect dialog's picker when it was not among the twelve nearest gateways — the selection visibly fell back to “Manual”.

Fixed in v1.40.1 — 2026-08-12 ​

  • The level assistant could only measure with a connected CAT module — on the rigctld path all readings stayed empty, without explanation.

Fixed in v1.40.0 — 2026-08-12 ​

  • The ARDOP modem's drive level could not be set — it always ran at full amplitude, which regularly overdrives in data mode. A slider and the level assistant close that gap.

Fixed in v1.39.1 — 2026-08-12 ​

  • Winlink demanded a second rig configuration and then fought the CAT module over the serial port. Winlink now uses the existing CAT connection.
  • The gateway directory did not show which row was ARDOP and which was VARA — for gateways offering both on the same frequency this led to the wrong connect dialog.
  • Sorting by distance, bearing, dial, bandwidth and source did nothing.
  • The gateway window stayed open after connecting, and “Show all gateways …” opened a second window on top of the first.

Fixed in v1.39.0 — 2026-08-12 ​

  • The gateway choice was limited to three Swiss stations and absent entirely for VARA. The list now comes live from the Winlink web services.

Fixed in v1.38.1 — 2026-08-11 ​

  • Crash when displaying the terrain profile (regression in 1.38.0). As soon as the elevation data arrived and the chart with its legend was about to be drawn, the app quit. Every completed path was affected — both in the module and in the separate profile window.

Fixed in v1.38.0 — 2026-08-11 ​

  • The new-logbook form could not be scrolled. In the program wizards (POTA, SOTA, WWFF, BOTA, LLOTA, GMA) the sheet extended past the screen edge on smaller displays, leaving the lower fields and the create button unreachable. Confirming with ⏎ worked, but blindly.

Fixed in v1.37.7 — 2026-08-10 ​

  • Self-spot carried the award references of the previously clicked station. After a spot click, the POTA/SOTA/WWFF reference, spotter and comment stayed in the form even after entering a different callsign — and went out to the cluster with your own spot.

Fixed in v1.37.6 — 2026-08-10 ​

  • Power on battery too low below full control setting (introduced in 1.37.5). At half setting the app showed 2.5 W instead of 5 W. The battery acts as an upper limit, not a scaling factor.

Fixed in v1.37.5 — 2026-08-10 ​

  • Transmit power shown and logged twice as high on battery. Portable radios deliver less power on their internal battery than on mains (IC-705: 5 instead of 10 W); the calculation only knew the fixed catalogue value. The app now evaluates the supply voltage.

Fixed in v1.37.4 — 2026-08-09 ​

  • CAT auto-detection took a very long time. It stubbornly tried every combination of model, port and baud rate — with a manufacturer offering many models that could take ten minutes or more. The device identity reported by the USB port is now evaluated and the matching combination checked first; the baud rates 1200/2400/4800, unusable for radios, are skipped.
  • The app started in the wrong logbook. Since operator profiles (1.37.0), the logbook assigned to the profile was opened at startup instead of the last used one — which also left you in the wrong entry mode (e.g. Outdoor instead of DX).

Fixed in v1.37.3 — 2026-08-09 ​

  • Transmit power stayed wrong after switching radios. After moving from a 100 W transceiver to a QRP rig (e.g. IC-7610 → IC-705) the app kept showing the old power — and wrote it into every newly logged QSO. The conversion only ran when the power control changed; if it stayed at 100 %, it was never recalculated. Now a radio or band change triggers the recalculation too (maximum power is band-dependent). QSOs already logged can be corrected in the logbook.
  • "Create new log" ran off the bottom on small screens. On MacBooks the "Cancel"/"Create" buttons were unreachable and the window had no scrollbar. The form area now scrolls while the title and buttons stay put.
  • Log types in the create dialog were German in the English interface. "Allgemeines Log (Lebens-Log, Tages-Log, …)", "≥4 QSO/Gipfel" and the other type descriptions are translated.

Fixed in v1.37.2 — 2026-08-08 ​

  • More German leftover strings in the English interface. License status/errors, cluster connection states, Data tab, WSJT-X bridge states, CAT error messages, band plan warnings, Wavelog "Instance URL" — around 50 messages, reported by Beatriz DJ0DE and Samantha DJ4SB.
  • DX cluster: a 4th cluster "could not be clicked". The deliberate limit of three simultaneously active clusters was never explained anywhere — the checkbox just silently snapped back. A clear notice now appears in the list.
  • Wavelog: station profile picker only populated after "Test connection". Profiles now load automatically when the tab opens.

Fixed in v1.37.1 — 2026-07-30 ​

  • Winlink status messages German-only. The exchange status and error messages (status bar, session log, alerts) appeared in German in the English interface — they originate in the WinlinkMail module and bypassed translation. Now fully bilingual (~50 messages).

Fixed in v1.37.0 — 2026-07-22 ​

Feature-only release (operator profiles) — no fixes to existing functionality. Newly created profiles are stored robustly and survive future app extensions without data loss.

Fixed in v1.36.1 — 2026-07-22 ​

  • German leftover strings in the English interface. Logbook empty states, frequency tooltip, calculator input fields and result tiles (14 calculators), DX cluster tabs, contest/outdoor dialogs bypassed translation as data values / string variables — now bilingual. Reported by Tudor YO8VET and Michael KB9ZDD.

Fixed in v1.36.0 — 2026-07-21 ​

  • Band plan was Region 1 only. Operators in the Americas (R2) and Asia-Pacific (R3) saw wrong band edges, and the awareness pill wrongly reported locally permitted frequencies as "outside band". Now switchable between all three IARU regions. Note: the R2/R3 plans follow the major national band plans (ARRL, WIA) — individual calling frequencies may differ, feedback welcome.
  • Band plan content in German in the EN interface. Band descriptions, sub-segment texts and the primary/secondary badges were stored as data and bypassed translation — now fully bilingual.

Fixed in v1.35.1 — 2026-07-20 ​

  • Data folder: ~/Documents/HAM-Tools reappeared despite a custom storage location. The QRZ image cache created the Documents path hard-coded on every launch, before the setting took effect — deleted folders came back. Folders are now created only at the configured location. Note: when changing the storage location, existing data is deliberately not moved automatically — move your logs by hand if needed.

Fixed in v1.35.0 — 2026-07-20 ​

  • Travel mode had no effect: the "Real-Time Upload" master switch (Settings → Lookup & Upload) was never checked by the auto-uploads — they kept running even with the switch off. It now really pauses all services; existing configurations are migrated automatically.
  • English interface: multi-selection context menus in German. "Upload N QSOs to QRZ Logbook / Club Log / eQSL / LoTW", the CAT auto-detect info line and "spotted N×" in the DX cluster appeared in German in the English interface.
  • English interface: duplicate window menu and German band plan filters. The German "Fenster" menu sat next to the English system "Window" menu (the bandmap entries are now part of the system menu); the band plan type filters were untranslated.

Fixed in v1.34.2 — 2026-07-19 ​

  • The app would not start on Intel Macs at all — macOS reported "this application is not supported on this Mac", regardless of the macOS version. The release was built for Apple Silicon only. From 1.34.2 HAM-Tools is a true Universal Binary. Affected Macs need to install the DMG from the website once — the update check runs inside the app and cannot help there. (Reported and verified on a 2019 iMac by KB9ZDD)
  • On English-language systems the app could still start in German, because the application package did not declare its languages.
  • The calculator section was entirely German in the English interface — 324 labels (result rows, section cards) plus the status lines in the license settings never reached the translation catalogue. Terminology corrected as well (velocity factor instead of shortening factor, reported by G4BDS).

Fixed in v1.34.1 — 2026-07-19 ​

  • The English interface still showed German in several places: sidebar and calculator names ("Drahtantennen", "Logbuch"), the demo banner at the very top, and the band/mode/continent filters in the DX cluster window. All translated. Plus a layout bug where longer English labels in the cluster filter bar were squeezed into vertically stacked letters. (Reported by VK5PSY, KR4EBP)
  • The Yaesu FTX-1 could not connect via CAT. There was no dedicated profile; with an FT-991 profile the frequency partly came through, but capability discovery ran into a timeout ("Protokoll-Fehler … Operation timed out") and PTT had no effect. It now has its own profile, "FTX-1 (Beta)". (Reported by DJ0DE/DJ4SB)
  • DX cluster: connection attempts hung on "connecting…" forever when the far end does not answer — typically when trying to add web services like DXHeat, DXSummit or DXWatch as a cluster. Those offer no telnet access. The attempt now aborts after 15 seconds with an explanatory message, and the hint appears in the settings and the FAQ.

Fixed in v1.34.0 — 2026-07-19 ​

  • The English interface showed German text in many places — status lines ("Kein Radio aktiv", "Idle — nicht verbunden"), filter labels ("Alle", "8 Bänder"), counters ("39 Spots (gefiltert)"), map footers, session sheets and various hint texts. Three structural causes in the string catalog and code fixed, around 200 texts translated — the EN interface is now consistently English.

Fixed in v1.33.0 — 2026-07-18 ​

  • The English interface showed some 1.32.x texts in German (map overlays menu, SSTV audio hints, rotator explanations). All stragglers are translated; the language catalog is complete again.

Fixed in v1.32.1 — 2026-07-09 ​

  • App no longer launched on macOS 26.5.2 — crash right at open. (Crash report July 9) macOS 26.5.2 rejects the app's embedded map-data bundle; the app therefore aborted while drawing the atlas world map (new in 1.32.0) for the first time, before the window appeared. Loading of all bundled data is now robust and can no longer take the app down. Affected Macs: install the current DMG manually once — the auto-updater never gets to run on a crashing 1.32.0.

Fixed in v1.32.0 — 2026-07-08 ​

  • Maps could not zoom out to show the whole world. (Bug report July 8, HB9HJL) The cause is a hard MapKit limit: Apple maps on the Mac show at most 180° of longitude no matter how far you zoom out. The grayline and DX world maps therefore render themselves now (custom atlas engine, Natural Earth data) — the whole world is always reachable there. All remaining map tabs (POTA, SOTA, BOTA, WWFF, GMA, WCA, LLOTA, contest, QTH locator, history) get uniform generous camera bounds and now zoom out to the MapKit limit (~half the world).
  • IC-705 Wi-Fi: "connected" but no reaction after ~2 minutes. (BUG-20260708-1630-LQ, HB9HJL) After Wi-Fi packet loss the CI-V data channel on the radio could die while the control channel kept answering pings — the existing watchdog saw traffic and never fired. New CI-V watchdog: if all CI-V replies stay out for ~10 s despite active polling, the session is treated as broken and reconnects automatically. Not yet verified against real hardware — feedback welcome on whether the hang is gone.

Fixed in v1.31.1 — 2026-07-04 ​

  • Cluster → world map: the selected station was not visible. Pins were only rendered for spots within the time window (default 60 min) — an older spot selected in the list centred the map on an empty area. The selected spot now always gets its pin; stations without resolvable coordinates report "⚠︎ position unknown" in the info bar. (BUG-20260704-1247, HB9HJL)
  • The grayline window could not be made small enough for a 15" display. Minimum size lowered from 640×420 to 420×300. (BUG-20260704-1247, HB9HJL)
  • Plus two feature requests: SSTV calling frequencies as a menu with CAT QSY (80 m–2 m), and double-clicking a log entry shows it in the entry panel at the top with QRZ card and picture. (HB9HJL)

Fixed in v1.31.0 — 2026-07-03 ​

  • LLOTA spots tab: QRT spots stayed in the list, comment was stale. For re-spotted activations the list showed the oldest instead of the newest comment of the spot history — activations reported as QRT therefore stayed in the list, and the displayed comment/spotter was outdated. The newest history entry now counts: QRT spots disappear, and a re-spot after QRT counts as QRV again.
  • LLOTA spots tab: spots from other apps with MHz frequencies displayed wrongly (e.g. 0.014 instead of 14.275 MHz). llota.app stores the frequency string as-is, and not every app sends kHz — the parser now recognises both formats.
  • LLOTA spot with an old-format reference failed without explanation. Sessions with references from before the llota.app format migration (June 30, e.g. DE-0003) hit a bare server error with the new self-/AutoSpot. The app now translates old references to the 4-letter format automatically (LLDE-0003).

Fixed in v1.30.0 — 2026-07-02 ​

  • Auto-suggest field toggles had no effect. The "which fields to fill" toggles in the lookup settings (name, QTH, locator, country, …) were not read by any code — lookups always filled all fields. They now filter every lookup result centrally, consistently across all forms. (Bug mail BUG-20260620-2117-LK concerned the same settings area: the greyed-out fallback picker is also live now with the multi-service lookup engine.)
  • English UI had gaps. 157 strings from releases 1.24–1.29 (SSTV, Rotor, GMA, WCA) appeared in German in the English UI — all translated.

Fixed in v1.29.1 — 2026-07-02 ​

  • IC-705 Wi-Fi: a lost connection went unnoticed. If the Wi-Fi link to the radio dropped or the IC-705 was switched off, the CAT indicator stayed green as if everything were still connected — the direct Wi-Fi connection (UDP) produces no error when the other end silently disappears. A watchdog now detects the drop after 6 seconds of radio silence, and HAM-Tools reconnects automatically (up to 3 attempts; the budget refills after 60 s of stable connection). If the radio is really off, it ends with a clear error message. (BUG-20260702-1702-PA, HB9HJL)
  • IC-705 Wi-Fi: clicking VFO B tore down the CAT connection (e.g. in the SSTV radio panel). The VFO command was sent internally to the rigctld client, which is not connected in Wi-Fi mode, instead of to the radio. The VFO now switches natively via CI-V — the button works now. In addition, all controls that only exist via the USB/rigctld path (volume, TX power, squelch, mic gain, keyer, antenna, NB/NR/notch/tuner, CW keyer, voice memory, TUNE) are now cleanly inactive in Wi-Fi mode instead of tearing down the connection when clicked. (HB9HJL)

Fixed in v1.29.0 — 2026-06-29 ​

  • Pure feature release (antenna rotator control, see changelog) — no bug fixes.

Fixed in v1.28.2 — 2026-06-28 ​

  • Header-less reception could be colour-shifted (green cast/slant). When tuning into a transmission mid-picture (no VIS header), the first image line was anchored to a single sync pulse — if that one was jittered by noise or QSB, the whole picture inherited a constant offset of the colour sub-scans. The line-0 anchoring now uses a phase consensus across all sync pulses (circular averaging), so jitter and outliers drop out and the picture stays stable. Clean reception is unchanged, and live reception benefits too (it uses the same timing routine). Covered by a new mid-stream-plus-noise regression and an independent cross-check against a third-party encoder (pysstv).

Fixed in v1.28.1 — 2026-06-28 ​

  • SSTV reception failed silently when the VIS header was missing. If you tuned into a transmission mid-picture, or QSB destroyed the header, reception appeared frozen even though a valid signal was present — the image data was there, only the mode was unknown. The decoder now identifies the mode in that case automatically from the line timing (auto-decode when unambiguous, otherwise a candidate suggestion), and reception gives honest status feedback throughout instead of a silent standstill. Covered by new core tests (all 14 modes detected header-less; noise/silence/wrong modes rejected).

Fixed in v1.28.0 — 2026-06-24 ​

  • Mostly an SSTV upgrade release (see changelog): hands-free auto-start, an improved gallery and TX display. Plus a real decoder robustness fix: a mistuned radio made reception fail (beyond ~100 Hz offset the VIS header was no longer recognised). The decoder now calibrates the offset out automatically from the VIS leader (up to ±150 Hz), so VIS detection, sync and colours are back on target. Covered by new weak-signal and offset regression tests.

Fixed in v1.27.0 — 2026-06-21 ​

  • Feature-only release (new SSTV module) — no fixes to existing modules.

Fixed in v1.26.3 — 2026-06-20 ​

  • Still-high CPU load in a contest with CAT (follow-up to 1.26.2, measured ~55 % → ~30 %). Profiling pinpointed the main cause: the SCP callsign suggestions were recomputed from the MASTER.SCP database on every render — i.e. on every S-meter tick (2×/s with CAT) — an expensive string scan on the main thread. Now cached (recomputed only when the callsign changes). Plus an S-meter throttle: the display only updates on a visible change. (BUG-20260620-1548-3C, -1703-UK)

Fixed in v1.26.2 — 2026-06-20 ​

  • Crash when switching Contest → DX (with the Contest cluster window open). The window was missing an internal data-object injection; fixed. (BUG-20260620-1318-PY)
  • High CPU load in a contest with CAT active (80–90 %, sluggish UI). The contest stats panel recomputed the full score over all QSOs on every incoming cluster spot. The band activity heatmap is now decoupled from the scoring — it only recomputes when a new QSO is added. (BUG-20260620-1548-3C, -1703-UK)
  • Grid contest: locator pre-filled from the callbook. As you type a callsign the received locator field auto-fills from QRZ/HamQTH (only when empty; the value heard on air wins) and correctly updates when switching to the next spot. (BUG-20260620-1343-UP)

Fixed in v1.26.0 — 2026-06-16 ​

  • Mostly a feature release (GMA — Global Mountain Activity, the seventh outdoor program — see changelog). Included: the minor gap noted in v1.25.0 is now closed — WCA (and GMA) are selectable as cross-ref partners directly in the new-log wizards of all other outdoor programs.

Fixed in v1.25.0 — 2026-06-15 ​

  • Pure feature release (WCA / COTA — Castles On The Air, the sixth outdoor program — see changelog). No bug fixes. (Minor known gap: the WCA cross-ref section is not yet in the other 5 programs' new-log wizards — but tagging a session with WCA afterwards always works via "Edit cross-refs".)

Fixed in v1.24.3 — 2026-06-15 ​

  • Voice-memory buttons (V1–V5) briefly dropped CAT on rapid clicks (Yaesu). The unacknowledged voice command ran into a read timeout that was treated as a disconnect — now tolerated, with a budget-free resync. The non-functional stop button next to the voice buttons was also removed.
  • Logbook: switching from an LLOTA session back to DX did nothing. You had to switch to Contest (or another type) first, then DX. The mode switch didn't account for WWFF/BOTA/LLOTA; it now covers every non-standard mode. (BUG-20260614-0616-3M)

Fixed in v1.24.2 — 2026-06-15 ​

  • Yaesu tuner control dropped the CAT connection. Reproduced and fixed for the first time on real Yaesu hardware (FTDX-10): (1) the tuner toggle (now »ATU«) occasionally timed out on the relay click and tore down CAT — now caught with a silent retry (also covers VFO switches, antenna selection and the sliders); (2) the case previously listed under "Active" — "tuning (or clicking a spot right after) wedges CAT, reset needed" — is resolved: the tuning cycle now triggers a deterministic, budget-free CAT resync that works however often you tune (status briefly shows »Tuning…«). The 15-second workaround is no longer needed.

Fixed in v1.24.1 — 2026-06-13 ​

  • DX cluster tab stuttered on incoming spots (CPU bursts up to 77 %, "layout storm"). Caused by rebuilding the table columns + re-filtering on every render. Fixed by caching the filtered spot list / spotter evidence and a differential table reload (only on an actual row change).
  • High CPU load with CAT active (~60 %): the logbook (QSO entry, solar panel, content tree) re-rendered on every S-meter tick of the rig. Now down to ~23 % — only the radio panel still reacts live to the transceiver values.

Fixed in v1.24.0 — 2026-06-13 ​

  • Pure feature release (LLOTA — Lakes and Lagoons On The Air, the fifth outdoor program — see changelog). No bug fixes.

Fixed in v1.23.0 — 2026-06-13 ​

  • Pure feature release (send eQSL cards by mail — see changelog). No bug fixes.
  • Also: the English translation was completed (eQSL texts plus propagation/split strings from 1.21/1.22 that still showed in German in the English UI).

Fixed in v1.22.1 — 2026-06-13 ​

  • A normal spot click switched the active VFO (Icom rigs with two VFOs) (reported by HB9HJI, IC-7610): since the split-from-spot feature (1.22.0) HAM-Tools sent a split-off command to the rig on every spot click — even for a plain spot with no split hint. On Icom rigs with two VFOs (e.g. IC-7610) this switched the active VFO to B even though the frequency was set correctly on VFO A. The split-off command is now only sent when split was actually active before.

Fixed in v1.22.0 — 2026-06-12 ​

  • IC-705 WLAN: the last entered credentials could get lost (found in-house): the radio IP, user and password of the direct WLAN connection were tied to the active CAT configuration and could disappear on a config switch or app restart. They are now stored app-wide.
  • IC-705 WLAN: reconnecting often required a TRX power cycle (found in-house): on quit HAM-Tools did not log off cleanly, the IC-705 kept its single network session, and reconnecting failed until the rig was power-cycled. Now: clean log-off on quit + automatic reconnect retry that keeps trying until the radio releases the session.
  • Otherwise a feature release (split from the spot comment — see changelog).

Fixed in v1.21.0 — 2026-06-12 ​

  • Pure feature release (propagation intelligence: grayline world map, "Prop" traffic light per spot, "Open now" matrix and the world map in the logbook cluster — see changelog). No bug fixes.

Fixed in v1.20.1 — 2026-06-07 ​

  • Moving columns could wreck the tables (found in-house, BUG-20260607-1706-TJ): on macOS 26, dragging a column in the spot tables (DX cluster, POTA, SOTA, WWFF, BOTA) or the QSO table led to scrambled cell contents, phantom columns, a frozen UI or — with a column arrangement saved by an older version — a crash. Root cause is an Apple bug in SwiftUI's table code; all six tables now run on a native NSTableView foundation. One-time side effect: the column order resets to the default after the update (visibility is preserved).

Fixed in v1.20.0 — 2026-06-07 ​

  • POTA: "already logged" was not visible per station (reported by HB9HJL): the ATNO filter works per park, the cluster ATNO status per country — whether the specific station was already in the log was not shown anywhere. Now: green ✓ marker per activator call (24h, with band tooltip) + "Hide logged" filter.
  • Otherwise a pure feature release (distance displays, continent multi-select, worked-B4 filter — see changelog).

Fixed in v1.19.1 — 2026-06-07 ​

  • TX power was stuck at 100 W and never tracked (reported by HB9HJL, thanks!): the power field in the QSO form now automatically follows the TRX power read via CAT, in actual watts; QSOs logged via WSJT-X/N1MM carry the logger's power, falling back to the CAT power.
  • Orphaned rigctld processes could block CAT startup: with several HAM-Tools installations around (e.g. release app + test build), their rigctld background processes survived force-quits, held the CAT port and caused "CAT err". CAT start now cleans up all HAM-Tools-owned rigctld leftovers (externally started rigctld instances are left alone).

Fixed in v1.19.0 — 2026-06-06 ​

  • Auto-lookup wrongly required QRZ credentials: Users with only HamQTH configured got no automatic callbook lookup on tabbing out of the call field or clicking a spot, and the bulk-lookup button in the QSO table stayed grayed out. Both now work with any configured callbook (QRZ or HamQTH).
  • Calls with /P, /M etc. were not found on QRZ (reported 2026-06-06, already fixed in 1.18.0 — listed here for completeness): the lookup now falls back to the base call for portable/mobile suffixes and prefix notation.

Fixed in v1.18.0 — 2026-06-06 ​

  • The README inside the DMG falsely claimed "not notarized" for signed builds — the text now reflects the actual signing status (the fix had been waiting for a while and only takes effect from this DMG build on).

Fixed in v1.17.5 — 2026-06-06 ​

  • A second tune shortly after the first left CAT permanently dead (HB9HJL test of 1.17.4: the first tune healed itself ✅, the very next one didn't): the auto-reconnect's 30 s anti-loop guard blocked the healing. Now a budget of 3 reconnects in a row, refilled after 60 s of stable connection.

Fixed in v1.17.4 — 2026-06-06 ​

  • CAT still died after the tune cycle (3rd round with HB9HJL, Yaesu — despite the 1.17.3 tolerances, sometimes ~10 s after tuning without interaction): suspected rigctld serial desync. The app now automatically reconnects once (~2–3 s) when the connection is declared dead instead of showing "CAT err"; only an immediate second death (rig off, cable unplugged) shows the error message.

Fixed in v1.17.3 — 2026-06-06 ​

  • Switching spots right after a TUNE still dropped the CAT connection (follow-up report by HB9HJL after 1.17.2): after the tune cycle the rig keeps responding late for a while — a single polling timeout killed the connection. Now: 3-strike tolerance in the poll loop, automatic retry for frequency/mode commands, and status self-healing.

Fixed in v1.17.2 — 2026-06-06 ​

  • Clicking a spot changed the receive bandwidth on Yaesu rigs (reported by HB9HJL): along with the mode, the Hamlib default filter width was applied (e.g. ~1.2 kHz), overwriting the bandwidth selected on the radio. Spot clicks and mode buttons now leave the filter selection untouched.
  • TUNE dropped the CAT connection (reported by HB9HJL, Yaesu): during the ATU tune cycle the rig stays CAT-silent for several seconds — the app ran into a polling timeout and went offline with "protocol error: … Operation timed out". It now waits out the tune cycle and resumes polling normally.

Fixed in v1.17.1 — 2026-06-06 ​

  • One-click update still aborted with "The request timed out" (live report during the 1.16.0→1.17.0 update, despite the 1.15.0 retry/resume): the real cause was the download code itself — byte-by-byte processing throttled it to ~0.2 MB/s (70 s for 14 MB; curl: 1 s), and the stalled TCP stream triggered the timeout after 30 s of standstill. Now chunked: under 1 second. The update to 1.17.1 runs the old code one last time — workaround if needed: "Load in browser".
  • Persistently high CPU load (32–50%) with a connected cluster: three render hogs (heatmap recomputation per cell, window invalidation per spot, database scan per render in the "recent QSOs" panel) — now a stable ~6%.

Fixed in v1.17.0 — 2026-06-06 ​

  • The WWFF reference DB could not be loaded ("A server with the specified hostname could not be found"): the source wwff-cc.org no longer resolves via DNS. The download now uses the official directory CSV from wwff.co; if everything fails, the app shows a direct browser download link for manual CSV import.
  • WWFF parser: in the wwff.co format the state column (region) overwrote the active/deleted status — 1,349 deleted refs would have slipped through as active. Also: IUCNcat is now recognized, the plain-text country wins over the DXCC code.
  • POTA/WWFF/BOTA export failed with a portable call (e.g. HB9HJI/P as the log call): the slash in the filename was interpreted as a subfolder, the export silently failed — with the misleading message "no active log or missing write permissions". Filenames are now sanitized (HB9HJI-P@…) and export alerts show the actual error.
  • Callbook lookup with portable calls (BUG-20260606-0613-XF): HB9HJI/P, /M and prefix notation returned "not found" — now falls back to the base call.

Fixed in v1.16.0 — 2026-06-06 ​

  • The "ATNO only" filter in the POTA spots tab was missing although this help site already documented it — now implemented (together with "Manual only" against RBN noise).
  • Self-spot docs corrected: the spot button never worked in hunter mode (activator only) — help text and docs wrongly claimed it did.

Fixed in v1.15.0 — 2026-06-06 ​

  • One-click update aborted with "The request timed out" on unstable connections. A single network stall threw away the whole download. Now: up to 3 attempts with automatic resume at the drop point (HTTP range resume). The previous workaround was "Im Browser laden" (download in browser).

Fixed in v1.14.4 — 2026-06-06 ​

  • SWR display in the radio panel had disappeared (since 1.9.12). The SWR row only appeared after transmitting with a measurable SWR (> 1.0) — with a perfectly matched antenna it never showed up at all. Cause: the rework of the CAT capability detection in 1.9.12 lost the unlock-on-connect step. The row now reappears right after the CAT connect.

Fixed in v1.14.3 — 2026-06-05 ​

  • No fixes — mini feature release (Help menu → "HAM-Tools Help" opens the online docs in the app language).

Fixed in v1.14.2 — 2026-06-05 ​

  • One-click update hung at "Relaunching…" (1.14.0/1.14.1). The update was already installed correctly at that point — only the automatic relaunch never came: the open update sheet swallowed the quit command. Workaround when updating from 1.14.0/1.14.1: quit the app manually and reopen. From 1.14.2 onward the relaunch completes automatically (forced quit after a grace period + helper waits for the old process to exit).

Fixed in v1.14.1 — 2026-06-05 ​

  • No fixes — mini feature release ("Reset" button for skipped updates). Also the first live run of the one-click update introduced in 1.14.0.

Fixed in v1.14.0 — 2026-06-05 ​

  • No user-facing fixes — pure feature release (one-click update + English help site). Note: the new "Install now" flow ships with this release and will run for real for the first time with the next update — if anything snags, "Download in browser" always works.

Fixed in v1.13.0 — 2026-06-05 ​

  • No user-facing fixes — pure feature release (IC-705 WLAN control). Known limitation: the IC-705 allows only one network connection at a time; after an unclean disconnect the radio holds the session until it times out — then either wait a moment or toggle Network Control off/on at the radio.

Fixed in v1.12.1 — 2026-06-04 ​

  • No user-facing fixes — pure feature release (DXpedition alert in the DX cluster). One internal robustness fix only affects the development build.

Fixed in v1.12.0 — 2026-06-03 ​

  • Hexbeam calculation: the turning radius was slightly too large. The value was based on an approximation instead of the real original G3TXQ table. Corrected to 0.1539·λ; the info text and the vertical band spacings were adjusted accordingly.

Fixed in v1.11.1 — 2026-06-02 ​

  • The Hexbeam in the antenna simulator was only a simplified approximation (bidirectional pattern, front/back not trustworthy). The geometry was derived from a single radius instead of from the real curved "M/U" wire routing. The sim now uses the real, tuned G3TXQ geometry from the original EZNEC model (W driver + U reflector) — NEC-verified resonant with clear directivity (20m: ~10.5 dBi gain, ~10.5 dB front/back over ground). The "simplified model" note is gone.

Fixed in v1.11.0 — 2026-06-02 ​

  • Yagi / HB9CV / Moxon "Open in Sim" produced an almost bidirectional radiation pattern (barely any front/back). The velocity factor was counted twice — once in the build dimensions and again implicitly by NEC (which models the end shortening via the wire diameter itself). The antennas were thus ~5% too short, and the reflector lost its inductive effect. The simulation now uses the physical lengths without the extra factor. NEC-verified: Yagi front/back 3 → 27 dB, SWR of Moxon/HB9CV from ~13/7 down to ~1.2/2.0.
  • Magnetic Loop & EFHW shortening simulated without their reactance. The tuning capacitor (Magnetic Loop) and the loading coil (EFHW shortening) were discarded when the model was imported into the simulator — the antennas were therefore not resonant (SWR ∞). The lumped components are now carried over as well.

Fixed in v1.10.9 — 2026-06-01 ​

  • No fixes — pure feature release (internet/cluster connection indicator in the logbook top bar).

Fixed in v1.10.8 — 2026-05-31 ​

  • WSJT-X did not run in parallel with HAM-Tools (user report HB9HJL). As long as HAM-Tools was connected via CAT, it held the serial port exclusively — WSJT-X could not reach the radio. Now HAM-Tools' embedded rigctld can be kept open as a local server (127.0.0.1:4532) that WSJT-X & Co. attach to in parallel (Settings → CAT → "Share CAT"). The server stays alive even when HAM-Tools drops its own connection.
  • Yaesu: TUNE did not trigger a tuner match but switched the tuner off (user report HB9HJL). The TUN pill only toggles the tuner on/off. New: a separate TUNE button starts a real match on modern Yaesu rigs (AC002;). Hidden on rigs without a CAT tuner (FT-817/857/897) — the exact tune command is overridable per profile.

Fixed in v1.10.7 — 2026-05-29 ​

  • Moxon Rectangle produced an antenna ~24% too long. The constants in the calculator came from an unverified source and led to resonance at 11.4 MHz instead of 14.2 MHz (20 m). Now Cebik W4RNL MoxGen polynomials, dependent on wire diameter — verified against the official Cebik wire Moxon table. Material picker wire 2 mm / aluminum tube 12 mm + validity warning outside the model range.
  • POTA/WWFF/BOTA ADIF export wrote the multi-park list as a comma list in MY_SIG_INFO. But the upload platforms pota.app / wwff.co / wwbota.net require a separate file per activation target. Now: one ADIF per park/ref/bunker with a single MY_SIG_INFO, filename {call}@{ref} YYYYMMDD.adi. Activator call normalized consistently to the log's activator everywhere (solves the WSJT-X "STATION_CALLSIGN mixed" problem).
  • Spiderbeam multi-band Lel values were systematically too long. 23 table values (5-band, low-sun, WARC, original) corrected per DF4SA build manual v2.20 §2.3.2 ("Lel = table value − 8 cm" for insulated enameled copper wire).
  • Hexbeam calculator scaled all bands linearly from 20 m. Now band-specific values directly from the WiMo HEX6B build manual (G3TXQ Rev. V2.1) for 20/17/15/12/10/6 m, others via extrapolation.
  • Spiderbeam single-band could only do flat Yagi. Added V-shape mode with spreader half-arm, fixed "mm" → "cm" label, aligned multiband arm values.
  • HB9CV had no gamma-match design. Inner-conductor Ø, spacing and trimmer capacitance are now calculated, plus a material toggle tube/wire.
  • Groundplane: drift between app and web (1.02 vs 1.05) — both now consistently 1.02.

Fixed in v1.10.6 — 2026-05-26 ​

  • Second TRX did not connect / "Port busy" (user report HB9HJI). After a crash, force-quit or USB replug, a rigctld process stayed on the hard-wired TCP port 4532 and blocked new connections. The app now cleans up orphaned rigctld processes before every connection attempt (exact binary-path match via libproc).
  • Transceiver menu showed "Enable CAT" despite being connected. The entry was driven by an internal switch instead of the real connection → "enable" even when connected, and a click would disconnect. Now "Connect/Disconnect CAT" based on the actual state, consistent with the Start/Stop button.

Fixed in v1.10.5 — 2026-05-26 ​

  • IC-9700 did not connect over CAT (user report HB9HJI). With two Icom devices using CP210x USB (IC-9700 + IC-7610) on the same Mac, their ports were indistinguishable in the picker (usbserial-XXXXX) → the wrong one was chosen and rigctld aborted with "Exit -1". The port picker now shows the USB identity (CP210x serial number). Plus: the real rigctld error message (exit code + stdout/stderr) instead of "no stderr", a band-plausibility warning on a mismatching frequency, Icom flow control always None, CI-V placeholder = model default.

Fixed in v1.10.4 — 2026-05-26 ​

Three fixes from the live test (user reports HB9HJI) plus export-spec conformance:

  • Serial number not editable when editing. The contest QSO editor had no fields for serial/exchange — now Serial, Sent Exch and Recv Exch are editable (like the columns of the log table).
  • Contest rate far too high. "Rate 10/60 min" extrapolated over the span since the first QSO in the window (a few dense QSOs → absurd values). Now a fixed window width as the divisor (N1MM behavior).
  • DX cluster "Cont." filter filtered by the DX instead of by the spotter. "Cont. = EU" now shows only spots from spotters in EU (propagation view). The country column and Band Activity stay with the DX continent.
  • Export conformance (Cabrillo/ADIF/EDI). Cabrillo: CATEGORY-MODE: SSB instead of PH, new CATEGORY-ASSISTED/CATEGORY-TRANSMITTER, LOCATION: DX for international calls, invalid CATEGORY-TIME omitted. ADIF: MY_ANTENNA instead of the undefined ANTENNA. Cabrillo + EDI: CR-LF line endings. Checked against the WWROF v3, ADIF 3.1.5 and REG1TEST specifications.

Fixed in v1.10.3 — 2026-05-25 ​

  • EDI export: wrong scoring block for VHF contests. In the EDI/REG1TEST export the bands field of the count lines was wrong (CQSOs=n;0 instead of n;1; CWWLs/CExcs/CDXCs without a third field). Now matches the VHF Managers Handbook + RUMlogNG reference; checked against real IARU R1 145 MHz and DARC VHF logs. QSO lines, QRB distances and point totals were already correct.

Fixed in v1.10.2 — 2026-05-25 ​

Pure feature release (new "Recent QSOs" panel in the DX sidebar) — no bug fixes.

Fixed in v1.10.1 — 2026-05-25 ​

Three fixes from the live test of 1.10.0 (user reports HB9HJI):

  • ATNO falsely reported "NEW MODE". In the DX cluster the ATNO pill showed "NEW MODE" for entities long since worked in SSB. Cause: the sideband mode derived from the frequency (USB/LSB) was compared against the ADIF mode SSB from the log. Sidebands are now folded together (USB/LSB = SSB, CWR = CW, RTTYR = RTTY).
  • FT8/FT4 was shown as SSB/USB. The mode detection required an exact hit on the dial frequency; but FT8 signals are spread across the ~3 kHz wide AF passband above the dial QRG. Now the whole passband is recognized, plus added dial frequencies for 4 m and 2 m FT4.
  • The QRZ image area made the entry form jump. Without a loaded image the profile column did not hold its width — the fields jumped to the right, and back to the left with an image. Fixed image box with a placeholder, no more jumping. New: clicking the image opens it at triple size.

Fixed in v1.10.0 — 2026-05-24 ​

Core/refactor release — no classic bug fixes, but two scoring corrections that come with the new engine:

  • Canton/district multipliers with a full exchange. When the multiplier value sits as a token in a multi-part exchange (e.g. 599 ZH, 599 B07), it is now recognized correctly — previously the multiplier evaluated the whole field and therefore counted 0 (Helvetia/Christmas-contest cantons, WAG district).
  • USKA 50 MHz (CW/SSB): no more grid-square multiplier. The final score is the pure km sum per the official USKA regulations (previously incorrectly multiplied by grid squares).

Fixed in v1.9.18 — 2026-05-24 ​

Contest-scoring fix from the live test (user report HB9HJI):

  • Helvetia Contest score computed completely wrong. A 219-QSO log showed 411 pts × 23 mult = 9,453 instead of the correct 1,328 × 110 = 146,080. Three errors: (1) points counted HB QSOs as 1 instead of 10 and all non-HB flatly as 3 instead of 1 (same continent EU) / 3 (DX) — contrary to USKA regulation §2.7. (2) The multiplier counted only cantons and deduplicated them globally, instead of counting cantons AND DXCC entities per band. (3) The stats panel showed 23 instead of 66 cantons in the total row. Now correct, with a new "Entities" column and robust country resolution (HB→Switzerland, otherwise grid, otherwise prefix). DXCC prefix table extended by missing EU sub-prefixes (DL block, BE, NL, PL, BY).
  • Export buttons in outdoor logs showed the full DX/contest menu. In BOTA/POTA/SOTA/WWFF logs Cabrillo + EDI appeared (and ADIF for SOTA), even though the portals require other formats. Now log-type-specific: SOTA → CSV only, POTA/WWFF/BOTA → ADIF only, Standard/Contest → ADIF + Cabrillo + EDI.

Fixed in v1.9.17 — 2026-05-23 ​

Critical hotfix from the live test:

  • Outdoor log creation "Create" button silently disabled for unknown refs. All four outdoor wizards (BOTA/POTA/SOTA/WWFF) required a DB match on the entered ref. New refs (not yet in the bundled CSV) or unusual spellings led to canCreate == false, but the .borderedProminent button stays visually active — a click did nothing. Now a non-empty query is enough, the DB lookup is a bonus for auto-fill. Orange hint line when the ref is not in the DB.
  • Multi-ref hopping section was hidden for unlooked-up primary refs. It now appears as soon as a non-empty primary query exists.

Fixed in v1.9.16 — 2026-05-23 ​

UX hotfix from the live test:

  • The Outdoor tab opened the POTA sheet directly without a choice. Anyone wanting to activate SOTA, WWFF or BOTA first had to cancel the POTA wizard and re-navigate via the sub-picker. Now a program picker with all four options appears on the Outdoor click (when no outdoor log exists yet).
  • WWFF/BOTA logs were ignored on the Outdoor click. The "does an outdoor log already exist?" check only looked at POTA and SOTA — anyone with a WWFF or BOTA log still saw the POTA wizard. The order is now POTA → SOTA → WWFF → BOTA, so it switches correctly to any existing outdoor log.

Fixed in v1.9.15 — 2026-05-23 ​

Privacy hotfix — three forgotten setup leftovers with the author's call, caught retroactively on the first run of the new pre-release user-data check:

  • Sidebar subtitle "HB9HJI Funkwelt" hardcoded. In the main window at the top under "HAM-Tools" stood the author's call instead of a neutral or dynamically adopted value. Now dynamic from the station settings, empty when no callsign is set.
  • Previous-QSOs popover help text named "HB9HJI" as the example for the base-call match explanation. Switched to a generic "DL1ABC".
  • The QTH Locator field showed "JN47PN" as a placeholder without an "e.g." prefix — it looked like a default value. Standardized to "e.g. JN47PN".

Extends the privacy wave from v1.9.7 (five spots back then). The new pre-release check has been a fixed pipeline step before build-dmg.sh since today.

Fixed in v1.9.14 — 2026-05-23 ​

Outdoor-logger polish + 1 self-reported bug:

  • SOTA chaser logs could not be exported as CSV at all. The SOTACSVExporter checked "are there own summits in the log?" and, for chaser logs (which by definition have no own summits), silently returned an empty file list. So you had a cleanly kept chaser trip but no CSV to upload to sotadata.org.uk. Now its own chaser column schema + a new pre-export sheet with a role picker.
  • Per-summit activation status was summed across all summits of a log. With multi-summit hopping it showed "12/4 — activation valid", even though no individual summit had reached 4 QSOs yet. But the SOTA rule is per summit + UTC day separately. Now correct with a SOTASessionStatus helper and per-activation pills in the form.
  • WWFF activation status had the same bug (X/44 summed across all refs), and Hunter had no live status at all. Now solved analogously with WWFFSessionStatus + a Hunter block "N refs · M programs · R2R K".
  • POTA activation status as well (X/10 summed across all parks/days). Brought into line identically.
  • BUG-20260522-2040-AW: "Not all fields correct after a QRZ lookup" (HB9HJI, v1.9.12). In the standard log, after a second QRZ lookup the "Country" field kept the value of the previous station while other fields were correct. Root cause: clearCallbookFields() in QSOEntryPanel cleared 11 fields, applyCallbookResult() wrote to 12 — country was in the apply but not in the clear. One-line fix + symmetry invariant explicitly documented.

Fixed in v1.9.13 — 2026-05-23 ​

Contest-season cleanup + a few spec points we had been interpreting creatively so far:

  • Contest ADIF sent RST twice. STX_STRING/SRX_STRING contained the report again ("59 LU") in addition to the dedicated RST_SENT/RST_RCVD. The USKA/DARC cross-check doubled it during evaluation. Now only the exchange data (canton/state/grid/zone) in STX_STRING/SRX_STRING.
  • Cabrillo without a T column (Cabrillo 3.0 spec). Some contest robots rejected the files with "Parse error: missing T-field at column 80" because the transmitter-ID value at the end of the line was missing. Now 0 is appended automatically — and CREATED-BY switched at the same time from hardcoded "HAM-Tools 1.5" to dynamic BuildInfo.appVersion.
  • ADIF: MY_GRIDSQUARE only for POTA/SOTA QSOs. For normal DX and contest logs the field was missing entirely. LoTW therefore did no QRB cross-check for VHF QSOs (where the field is mandatory), and Club Log could not derive the geographic assignment for some awards (WAB etc.). Now written for every QSO, generically from the station settings.
  • Contest form: the cursor stayed on the exchange field after Enter. At 100 QSOs per hour a noticeable click/tab detour. Now @FocusState with the cursor jumping back to "Call" after each submit + auto-uppercase for canton/state/grid/zone (so "so" doesn't land lowercase in the log).
  • The USKA 50 MHz contest template had the wrong date + wrong time category. The date was on the 2nd weekend of June instead of the 3rd, the time category was 6 h instead of 24 h. Plus the template name was just "USKA 50 MHz" — now "USKA / IARU R1 50 MHz Contest" so it is clear which rule-set variant applies.
  • The RadioControlPanel footer had been static since 1.9.4. It permanently said "Idle — not connected" even when the CAT connection had long been up. A TODO from the CAT refactor that slipped through all the bug reports. Now the real CATController.Status in the footer.

Fixed in v1.9.12 — 2026-05-22 ​

Feature release — pure additions, no regressions from 1.9.11:

  • Logbook ADIF export was "all or nothing". Until now the "Export ADIF" button always exported the complete active log. Impractical for a lifetime log with a few thousand QSOs when you only wanted to upload a slice (a contest day, the last 50 QSOs for Club Log). Now: ⌘/⇧ click in the QSO table marks a selection, the button changes to "Export ADIF (N)" and writes only those N rows.
  • The CAT panel had no sliders for volume and TX power. The RUMlog/HamLog models show AF/RF sliders — we only had mode/VFO/split buttons. Now two new sliders between the S-meter and the status badges. Drag-and-release pattern: during the drag the update runs locally, on release it goes to the rig once — saving round-trips.
  • SWR was nowhere visible. On every TX you had to look at the rig display to see whether the standing-wave ratio was okay. Now a live SWR bar in the panel during transmit, color-coded (≤ 1.5 green, ≤ 2.0 yellow, > 2.0 red).
  • TX/RX badges were placeholders. The two small RX / TX pills next to the PWR value had no live read and always stayed gray. Now the app reads the PTT status (t command) on every poll tick and colors the badges accordingly — whether the PTT comes from the mic, data or CAT.
  • No quick DSP toggles. Standard functions like Noise Blanker, Noise Reducer, Auto-Notch and antenna tuner were only reachable at the rig — with a faint CW station coming in you waste time at the knob. Now four toggle pills under the status badges; a click toggles the function at the rig.

Fixed in v1.9.11 — 2026-05-21 ​

Live-test feedback from 1.9.10 (5 bug mails via the in-app reporter):

  • Previous popover found no /P /M /QRP QSOs (BUG-20260521-2000-QP). LogbookDatabase.findQSOs(matching:) compared calls exactly — anyone searching for "HB9XYZ" found no "HB9XYZ/P" entries even though they were in the log. Now base-call match: the longest part between the "/" separators is compared on both sides. The empty state additionally diagnoses "X logs searched · base-call match".
  • "Fetch QSL confirmations" hidden only in the QSL tab (BUG-20260521-1958-WJ). Users looked for the buttons in the settings, where the credentials also live. The buttons are now mirrored in Settings → Lookup & Upload → QRZ.com / LoTW, with the hint "(also available in the QSL tab)".
  • Contest cluster lacked a worked filter + mult marking (BUG-20260521-2005-CT). In contest mode a filter bar now appears at the top with a toggle "👁 Hide worked" + a conspicuous green "MULT" badge next to multiplier candidates + a color legend. Appears only when activeLog?.type == .contest.
  • Frequency entry did not control the radio (BUG-20260521-1937-SS). The text field in RadioControlPanel was editable, but commitFreqText() only set radio.frequencyMHz locally — no cat.setFrequencyMHz(). The poll loop overwrote the value ~200 ms later with the real radio frequency, so from the user's view "nothing happened". Now the commit sends the frequency to the radio when CAT is active, with an optimistic UI update to avoid flicker.
  • The USB port had to be re-selected after every reboot (BUG-20260521-1954-YH). With FTDI/CP210x chips macOS may assign the stick a different path suffix after boot; the stored path was then dead and Connect failed silently. New SerialPortDiscovery.resolve(stored:) logic: if the path is gone and exactly one USB serial port is present, it is adopted automatically + persisted in CATSettings (info toast "ℹ️ USB path migrated: old → new"). On ambiguity, a clear error message with a candidate list.

Fixed in v1.9.10 — 2026-05-21 ​

  • LoTW path setup was terminal-heavy. The "tqsl binary" field in the LoTW settings was a plain text field — when the auto-detection did not find the app (TQSL.app instead of Tqsl.app, an unusual install location, Homebrew), the user had to hunt for the path with mdfind or find in the terminal. Now a "📁 Browse…" button to the right of the field that opens a Finder picker and automatically extracts the binary from the .app bundle.
  • Yaesu voice-memory V5 slot was missing. The TRX voice-keyer row showed only V1–V4 for Yaesu profiles, even though the supported models (FT-991/A, FT-710, FTDX-10, FTDX-101D/MP) have 5 slots in hardware. A fifth button added — the code comment even pointed at the "we only map 4" TODO itself. ICOM stays at 4 slots (hardware limit).

Fixed in v1.9.9 — 2026-05-21 ​

  • The Schedules tab was a placeholder with no content. The tab bar showed "Schedules" with a calendar icon but a disabled tooltip "coming in a later phase". The tab is now fully implemented: skeds + DX events with a countdown, QSO-form pre-fill, cluster filter, status menu and macOS notifications. Persisted in ~/Documents/HAM-Tools/Cache/schedules.json. Docs under Modules → Schedules.

Fixed in v1.9.8 — 2026-05-21 ​

  • The TRX voice-keyer UI was ICOM-only. The V1–V4 buttons in DX/contest/outdoor forms showed "ICOM Voice / IC-7300/7610/9700/705" and were silently meant for ICOM only — Yaesu/Kenwood/Elecraft users could not click to see whether their Hamlib backend supported it by now. Now brand-specific display, with the buttons always active as long as CAT is connected.
  • RPRT -11 in the status line was cryptic. For voice-memory calls that the Hamlib backend does not implement, "sendVoiceMem rejected: RPRT -11" appeared. Now an understandable message: "This function is not (yet) supported by the Hamlib backend for this TRX model."

Fixed in v1.9.7 — 2026-05-21 ​

  • Privacy leak: the DXCluster default callsign was hardcoded HB9HJI, the QTH locator hardcoded JN47PN in five places (cluster, world map 2×, QTH locator, grayline), and the API user agent contained "HAMTools/2.0 HB9HJI". On a fresh install without an entry in the station settings, other users started with the author's identity in the cluster login + distance calculation; on every API request to pota.app/sotadata.org.uk/wwff-cc.org the author's call was sent in the HTTP header. All defaults set to "", the user agent is now HAMTools/<appVersion>.
  • Cluster spot time mismatch (BUG-20260520-1945-JS): depending on the source, the spot list showed Mac local time, RBN skimmer "UTC" strings with local content, or no time zone at all. Now DXSpot.displayTime always renders from the timestamp date in UTC (HHmmZ).
  • Mode multi-select + band sorting (BUG-20260520-1943-G8): the mode filter was single-pick, now multi-select (Set<String> with migration). The band filter list is sorted by wavelength instead of alphabetically.
  • TRX setup submenu closes (BUG-20260520-1942-B3): CATController as an @ObservedObject in TransceiverCommands triggered per-second CommandMenu rebuilds via the status poll loop. Now a let reference, the status is read only on click.
  • Spot cap too small (BUG-20260520-1942-AA): SpotPersistence.maxSpots 500 → 2000. On a contest weekend with 4+ DXSpider nodes, 500 were full in ~50 s.
  • Grayline performance (BUG-20260520-1940-33): nightCells was a computed property → 2592 polygon constructions per body render. Now a @State cache with recompute only in onAppear/onChange. Plus grid step 5° → 10° (648 instead of 2592 polygons).

Fixed in v1.9.6 — 2026-05-20 ​

  • LoTW: the station-location picker found no locations configured in tqsl 2.5+, because only the old path ~/Library/Application Support/TrustedQSL/station_data.xml was tried — current tqsl stores them under ~/.tqsl/station_data.xml. A second path candidate added; the picker now automatically shows what was set up in the tqsl GUI.
  • LoTW: tqsl exit codes 9 and 10 were swapped. A tester with an incorrectly entered station location got "LoTW server not reachable" instead of the correct "Location not found" message. Mapping verified from a tqsl 2.8.4 live test: 9 = CONNECTION_FAILED, 10 = COMMAND_ERROR.
  • LoTW: "Station Location X could not be found" landed in the generic CLI-argument error branch and showed an unhelpful text. A dedicated plain-text detection in interpret() now outputs "check in Settings → LoTW" directly.

Fixed in v1.9.5 — 2026-05-20 ​

  • LoTW upload reported "Network: LoTW server not reachable" even though the upload actually succeeded. Cause: the word "Connection" in an intermediate tqsl log line triggered the network branch in interpret(). The success plain-text match ("uploaded successfully" / "queued for processing") now runs BEFORE the network heuristics. In addition the subprocess now starts with an explicit HOME/PATH + cwd=$HOME (some app-sandboxing scenarios delivered an empty environment that confused tqsl). Error alerts now show the last 500 characters of the raw tqsl output as a diagnostic aid.

Fixed in v1.9.4 — 2026-05-20 ​

  • LoTW upload: tqsl exit codes were mapped to the old 1.x scheme (0/3/4/6) — the current tqsl 2.5+ version uses codes 0–11 with completely different semantics. The UploadOutcome on success/duplicate/network error was therefore unreliable. Codes re-derived from the tqsl source (apps/tqsl.cpp), duplicates additionally detected by text match in stdout (tqsl 2.5+ no longer signals them via exit code).

Fixed in v1.9.3 — 2026-05-20 ​

  • Startup crash on macOS 26.3.x: HAM-Tools.app crashed immediately after login with EXC_BREAKPOINT in SCPService.loadRawFile. The cause was a forgotten Bundle.module direct call — the tolerant AppResource helper (built in 1.8.16 for exactly this class of bugs) was overlooked in the new contest SCP code. Now switched over; SCPService finds the MASTER.SCP file regardless of bundle format (flat or canonical Contents/ layout). Testers who could no longer start after 1.9.2: load 1.9.3 manually, after which auto-update works normally again.

Fixed in v1.9.2 — 2026-05-20 ​

  • The right sidebar still jumped to varying widths after the 1.9.1 release as soon as you switched between Contest and Standard/Outdoor. Cause: HSplitView identified ContestStatsPanel and PropagationPanelView as two different child views and reset the splitter on every switch. Both panels now sit in a shared outer VStack, with the frame modifier on the outside — so HSplitView always sees the same view identity. Frame additionally pulled in tighter (min 230 / ideal 255 / max 290).
  • The ICOM voice-keyer brand restriction was only visible via a .help() tooltip on the text label. SwiftUI on macOS triggers the hover tooltip on plain text views unreliably — users therefore did not see the restriction. The model list is now inline as a second text view next to "ICOM Voice": IC-7300/7610/9700/705.

Fixed in v1.9.1 — 2026-05-20 ​

  • Light theme: the CAT frequency display was invisible, black-on-black — the foreground hung on theme.textPrimary (nearly black), the background on theme.bgLog (nearly black). Switching to theme.logText (green radio display) makes the display consistently readable in all themes.
  • Light theme: the sidebar headlines (Send DX Spot, Propagation, Solar Data, My Spots, Band Activity) were barely readable in light pastel gold on a white panel. In the light theme now theme.accentOrange (#E07000) as the headline tone; Dark/Ham Classic stay unchanged at the classic gold, Matrix uses the cyan accent.
  • The contest wizard did not save the band category chosen in the Cabrillo picker — the value was lost on creation, and the cluster filter and Cabrillo export always fell back to the template default. Schema v12 migration adds log_meta.contestBandCategory; all three consumers (cluster tab, export sheet, stats panel) now read the log value first.
  • The right panel jumped to up to 340px ("too wide") when switching between DX/Outdoor/Contest. Both sidebar variants (Propagation, Contest Stats) now use identical frame values (min 250 / ideal 285 / max 320), so HSplitView can no longer pull to the upper stop.
  • The "Band Activity" headline wrapped to two lines on a narrow sidebar (the picker with width: 100 left too little room). lineLimit(1) + the picker narrowed to 88px — the headline stays strictly single-line.

Fixed in v1.9.0 — 2026-05-19 ​

  • DX cluster heatmap picker (Band Activity, right panel): the 15/30/60-min choice only had a visual effect — the numbers in the heatmap kept computing with the old value. The picker in the panel and the bandMatrix calculation were decoupled across two independent states. Now a computed property directly in the panel, AppStorage-based. Plus a "5 min" option, so that with a full cluster (~500 spots in the 15-min retention) you can see a difference at all.
  • The app was not launchable in English (and was never really English). Three bugs at once: SwiftPM does not automatically compile the string catalog into its runtime form; the generated localization files landed only in the SwiftPM sub-bundle (invisible to SwiftUI); Info.plist lacked the CFBundleLocalizations/DevelopmentRegion entries. All three places fixed — the language picker in the Appearance tab now does what it should.
  • DX map QTH centering did not take effect after an interactive camera move: MapCameraPosition.region was discarded by SwiftUI as "equal" when the user had previously moved the map manually. Now with a .camera(MapCamera(...)) snapshot, it animates cleanly back to your own QTH.

Fixed in v1.8.16 — 2026-05-19 ​

  • Callbook lookup: when clicking a new cluster spot or on a manual call change + Tab, the First/Last/Street/City/State/Email/Locator/zones of the previous station stayed put, even though the image and header already showed the new station. applyCallbookResult only filled empty fields; now a shared helper clears up before every fresh lookup.
  • Radio/CAT frequency display: the right segment was only 2 digits (10 Hz resolution) — "7.095.00". Now 3 digits with full 1 Hz resolution: "7.095.000".
  • The program maps (POTA/SOTA/WWFF/BOTA) had the same MapKit-stall risk as the History tab before 1.8.15. The hard cap + overflow banner is now extended to all program maps.

Fixed in v1.8.15 — 2026-05-18 ​

  • History tab crash: with "Period = All" and a large standard log, the app could completely "disappear" when clicking the History tab — the process kept running, but no window was visible anymore. Cause: a MapKit render stall from too many annotations + polylines. Three protective layers: a hard cap on 1500 annotations, a line limit of 500, and the "All" option removed from the period picker (max "2 years").

Fixed in v1.8.13 — 2026-05-18 ​

  • The auto-update check reported "HAM-Tools is up to date" even though a newer version was available on the server — isNewerBuild() compared only the build date as a string, so hotfix releases from the same day (1.8.11 → 1.8.12 → 1.8.13) were not detected. Now a numeric semver comparison is primary, the build date only as a tiebreaker. Effective from the 1.8.13 build — anyone on 1.8.12 or older must update manually once from /app/dmg/latest.dmg.
  • Multi-cluster: host or port changes to an already active cluster node were ignored by the pool resync (the old client kept running). applyActiveNodes() now does a field diff and selectively restarts affected clients.

Fixed in v1.8.12 — 2026-05-18 ​

  • App startup crash on macOS 26.5 (real cause): macOS 26.5's Bundle.init(url:) returns nil for SwiftPM resource bundles in some setups — Bundle.module then falls back to its fatalError fallback and the app crashes directly in BOTARefService.init. The 1.8.11 fix (rebuilding the bundle format canonically) did not fix this. From 1.8.12 Bundle.module is bypassed entirely: a new AppResource helper searches for the resource bundle itself, tolerates different bundle layouts and returns nil instead of crashing.

Fixed in v1.8.11 — 2026-05-18 ​

  • App startup crash on macOS 26.5 (first attempt — see v1.8.12 for the real fix): bundle-format correction in build-dmg.sh. On its own it did not yet bring success, but it remains in the build for clean code-signing hygiene.

Fixed in v1.8.10 — 2026-05-18 ​

  • POTA ADIF upload rejected with "Only a single STATION_CALLSIGN value is supported per log file" — when logging FT8 over WSJT-X spots, the my_call could switch mid-session from the home call to the portable call (e.g. HB9HJI ↔ IT/HB9HJI/P). Now two safeguards: the WSJT-X importer always takes the activation callsign chosen in the log wizard for outdoor logs; in addition the POTA export also unifies old mixed logs.
  • The mode picker in the Radio/CAT panel was dimmed and not clickable without a CAT connection — logging without a radio (e.g. a remote/travel setup) was thus nailed to the last active mode. Now always clickable; without CAT, FT8/FT4/JT65/JT9/PSK31/JS8/Q65/MSK144 are additionally selectable (Hamlib does not know these directly — they run at the TRX over PKTUSB).

Fixed in v1.8.9 — 2026-05-17 ​

  • Club Log upload: 403 Forbidden for email addresses with @ and other special characters — the form encoding was not RFC-3986-compliant and was blocked by Club Log's nginx WAF. Now strictly RFC-3986-encoded.
  • The standard DX log warned "Already worked" on repeated logs of the same call (lifetime log/regular net/daily log) — pointless there. The dupe warning is now only in program logs (POTA/SOTA/WWFF/BOTA) and contests.

Fixed in v1.8.8 — 2026-05-17 ​

  • POTA ADIF upload was rejected by pota.app — the export used the older undocumented field MY_POTA_REF. Now standard-compliant with MY_SIG=POTA + MY_SIG_INFO.
  • WWBOTA ADIF: the old stub produced no uploadable file — now the official format with MY_SIG=WWBOTA and a comma list in MY_SIG_INFO for multi-bunker.
  • POTA multi-park hopping: pota.app refused comma lists in MY_SIG_INFO — the export now automatically writes a separate file per park.
  • QRZ auto-fill in POTA/SOTA/WWFF/BOTA logs adopted only the name, the rest stayed empty — the ADIF was DXCC-incomplete. Now additionally QTH, locator, country, continent, CQ/ITU zone.
  • The hopping field on log creation showed only checkmarks without context — now the full name + details (park/summit/bunker) per entry.
  • The band plan was a cramped sub-tab in the logbook — now its own window (⌘⇧P, menu Window → Band Plan Window).

Fixed in v1.8.7 — 2026-05-16 ​

  • The update system compared the minimum macOS version as a string — "10.9" would have falsely counted as higher than "10.15". Now a strictly numeric version comparison.
  • The incompatible-update dialog showed an enabled "Open download" button even though the DMG would not run on the system. Now disabled with a clear reason.

Fixed in v1.8.6 — 2026-05-16 ​

  • FAQ link "Undo updates?" pointed to /app/dmg/ — the path returned 403 instead of a version listing. Now a directory index of all DMG versions.
  • The top-nav download pointed to a version-specific DMG and went stale with every release — now a version-less latest.dmg with an auto symlink.

Fixed in v1.8.5 — 2026-05-15 ​

  • The bandmap was restricted as a sub-tab in the logbook — now additionally openable as a pop-up window per band, with several visible in parallel on a second monitor.
  • DX propagation: no global day/night view — a new grayline map as its own window.
  • The settings gear in the logbook top bar was easily overlooked — removed, settings now via the app menu "HAM-Tools → Settings…" (⌘,) or the Transceiver menu.

Fixed in v1.8.4 — 2026-05-15 ​

  • The CAT connection dropped after a QSY or mode change — a race condition between the poll loop and write operations on the same rigctld TCP socket. A new client lock in the CATController serializes all operations.
  • A spot click forcibly switched from the DXClusters sub-tab to the Log sub-tab. You now stay where you are — the draft fills in the background.
  • The DX cluster table showed "SSB" as the mode, even though LSB/USB is correctly derivable depending on the band (now automatic).
  • The "Settings…" entry in the Transceiver menu did not respond (the old NSApp selector replaced by the SwiftUI API).
  • 13" MacBook Air layout: the right sidebar (Propagation/Solar/Band Activity) did not fit on the screen, you had to scroll.

Fixed in v1.8.3 — 2026-05-15 ​

  • The BOTA map sub-tab appeared incorrectly in the standard DX log (only meaningful in the BOTA program log)
  • The "New Contest" sheet was too small → the buttons "Cancel / Create" were cut off in the categories step
  • The POTA columns "State" and "Their Park" were shown in the standard log, even though they only make sense in POTA logs
  • The QSO table's column selection was only reachable via header right-click → a new "Columns" button in the toolbar with all 32 columns + reset
  • The spot tables (DX/POTA/SOTA/BOTA/WWFF) had no reorder/hide-show function → switched entirely to a SwiftUI Table

Fixed in v1.7.1 — 2026-05-13 ​

  • A cluster click did not fill the contest/POTA form — a race condition between QSOEntryPanel and the specialized form
  • The mode picker in the contest showed all modes instead of only those matching the Cabrillo mode category
  • The "New…" button for a CAT config did not copy the serial port along with it
  • The DX cluster in the contest showed spots in all modes instead of only the contest mode

Fixed in v1.7.0 — 2026-05-13 ​

  • The sidebar with 42 tools was cluttered → 3 top items (Logbook / DX Cluster / Calculators) with an accordion
  • The band plan was its own sidebar entry → moved into a logbook sub-tab
  • The DX cluster only connected on a tab click → now globally at app start

Report a Bug ​

In the app: Cmd+Shift+B or menu bar → Help → Report Bug… By mail: bugs@funkwelt.net

HAM-Tools © HB9HJI · Funkwelt