SliceLogger v1.2.0.0

SliceLogger 1.2.0.0 is our biggest feature release yet. Contacts logged in N1MM Logger+ now land in your SliceLogger log automatically. The IARU band plans know about FT8, FT4, WSPR and the other digital sub-bands, so Mode fills in from the frequency. A new Display Size setting makes text and windows larger or smaller, Parks on the Air hunters get park auto-fill and a POTA log export, and Spot Display can tune any of your slices.

Upgrading? Do this once to see the new digital sub-bands

An existing installation keeps exactly the band plan rows it already had — new built-in rows are never merged in automatically. To get the new digital sub-bands, open Settings → Configuration → IARU Band Plans, select each region you use, and click Reset region to defaults. This replaces the whole region's plan, so note any of your own customizations first.

What's new — N1MM Logger+ contact capture

N1MM+ broadcasts every contact it logs over UDP. Turn on Settings → Apps → N1MM+ (default port 12060), add SliceLogger as a Broadcast Data destination in N1MM+, and each new contact is saved to your log within a second. Mode, band, name and location details are filled in for you, your N1MM+ comment and contest exchange are kept, and POTA activators are recognized. It is capture-only: edits or deletions made later in N1MM+ do not change your SliceLogger log. See the new N1MM+ Setup page in Help.

What's new — IARU band plan with digital sub-bands

• Digital sub-bands in all three regions — FT8, FT4, JT65, JT9, WSPR, MSK144, FST4, FST4W, and Q65 are nested inside the CW, digital, and phone segments, each with Submode, Source, and Version Date columns so you can see where its data came from.
• Mode from frequency — type 14.074 in Log a QSO with no radio or WSJT-X supplying a mode and Mode fills in as FT8. Click-tuning a spot with no mode uses the same sub-band lookup.
• 2190m and 630m are now covered, along with the HF bands.

What's new — Mode Learning

A mode you type that isn't in the built-in list — in a saved QSO or in a band plan row — is now remembered permanently and appears in the Mode dropdown the next time you start SliceLogger, instead of vanishing when you close it.

What's new — Display Size

Choose Settings → Configuration → Display and pick Small (90%), Normal (100%), Large (125%), or Extra-Large (150%). Everything resizes the moment you choose — text, buttons, menus, tooltips, maps, and charts in every window — with no restart, and your choice is remembered.

• Text and borders stay sharp at every size, and window sizes and positions are remembered at 100% so changing the size never scrambles your layout.
• An amber note warns you when a size is too big for your screen; turn on Shrink to fit my screen to use the largest size that fits.

What's new — Parks on the Air (POTA)

• Park auto-fill for hunters — when you work a POTA activator, SliceLogger finds the park on the pota.app spots list and fills SIG / SIG Info, shown in amber so you can check it. It never replaces a park you entered yourself (turn it off under Settings → Configuration → SliceLogger).
• POTA fields and log columns — POTA_REF, MY_SIG, MY_SIG_INFO, and MY_POTA_REF are stored with each QSO and handled by ADIF import and export, and the log grid can show SIG and SIG Info columns.
• File → Export POTA Log writes one file per park and station callsign, named the way POTA's uploader expects.

What's new — Spot slice picker

Right-click a row in the Spot Display to see your station's slices (the transmit slice marked in red) and tune whichever one you pick to that spot. A normal click still tunes the TX slice. In multiFLEX, only the selected station's slices are ever listed or changed.

Bug fixes and reliability

• Weather Radar home marker — the "Your Location" marker and the open Map Hub now update when your operator's coordinates, grid, or DXCC entity change, and the RBN login callsign follows the active operator.
• Netherlands Antilles contacts — QSOs from before the October 2010 split (PJ2, PJ4, PJ5, PJ6, PJ7) now resolve to the deleted DXCC entities and appear in the Award Tracker's deleted-entities list. Already-mistagged contacts can be corrected by a re-import; see the GitHub issue for the steps.
• Startup crash — fixed a crash on launch after closing a window while it was maximized or minimized.
• Rotator, SmartLink, and FlexRadio connections are retried at startup, fixing an intermittent blank azimuth and missing remote radios after a brief network hiccup. A rotator you disconnect no longer reconnects on its own.
• POTA export no longer fills in your home state, city, and station details on activation records that did not carry them, so a multi-state park is credited correctly.

A note from Tim, W4TME

This release grew out of operator requests — N1MM+ capture, bigger text, POTA support, and more control over your slices. Thanks to everyone who filed a bug report or feature request this cycle. 73.

SliceLogger v1.1.0.0

SliceLogger 1.1.0.0 adds two significant new capabilities. A new QTH Map shows exactly where the station you're working actually is — down to a precise coordinate or grid square when one's available, tightening out to state or country as the data gets less precise — and real-time QSO backup mirrors every logged contact out to up to three folders of your choosing as you work, so your log survives a drive failure without waiting on a scheduled export. Also in this release: an opt-in check for new versions right from the app, a fix for Weather Radar tiles failing to load, and a batch of accuracy fixes — including one for Country not always filling in on ADIF-imported records. Thanks as always to everyone who filed a bug report or feature request this cycle; several of the fixes below trace straight back to your reports.

What's new — QTH Map

A new 9th Map Hub tab plots where the station being logged (or edited) physically is, on the same street map used by Weather Radar. Like every other Map Hub tab, it pops out into its own window if you want it undocked.

• Zoom radius follows how precise the location data actually is — a tight zoom for an exact coordinate or 6-digit grid square, widening out to a state-level or country-level view as the available data gets coarser, and falling back to your own operator's home QTH when nothing else resolves.
• Country is now always shown in the map's station label, not just when City/State are blank — useful for a DX contact whose city alone (e.g. Irkutsk) doesn't make the country obvious.
• Stays in sync automatically as you fill out the Log a QSO form, and re-syncs whenever you switch back to the tab; a new Refresh button re-resolves on demand from the form's current state.
• Live-verified against real contacts, including compound callsigns (e.g., EA8/G6XML).

What's new — Real-time QSO Backup

Settings → Maintenance → Backup now supports mirroring every logged QSO, in plain ADIF format, out to up to 3 folders of your choosing — a different drive, a thumb drive, a network share, or a cloud-sync client's local folder.

• Writes as you go — each QSO is appended the moment it's logged, with its own serial write queue per target so a contest's rapid logging cadence never interleaves writes to the same file.
• Self-monitoring — a target that fails or goes slow is taken offline automatically (immediately on a hard I/O failure, after two slow writes in a row for a merely sluggish one), and self-heals the moment a later write succeeds, no action required. A status-bar indicator and a colored dot per target in the Backup tab flag a degraded target until it clears.
• "Back up now" runs a full re-seed of a target (oldest-first, so the file reads chronologically top-to-bottom) — useful to close the gap after a target was degraded, or any time you want a fresh full copy.
• Complements routine ADIF export as a second, set-and-forget backup method — live-tested against a real 2,921-QSO log and a physically removed/reinserted USB drive.

What's new — opt-in update check

• Settings → Configuration → Updates now has a toggle for a silent, automatic check on launch — off by default. When a newer release is found, a status-bar indicator appears (never a popup), leading to the same View Update / Remind Me Later / Dismiss dialog already used by the existing manual Help → Check for Updates.

Bug fixes

• Fixed Country not filling in on some ADIF-imported records. A record with no COUNTRY/DXCC field of its own — for example, a remote-station export that states only the callsign — previously sat with a blank Country until the next app restart. Country now resolves immediately at import time.
• Fixed Weather Radar tiles failing to load (403 errors). The base map now uses Esri's World Street Map tiles, which need no API key and render with more color depth than the previous base layer.
• Fixed occasional duplicate entries in the DX Spot Display caused by a timing race between seeding the display from its replay buffer and a live spot arriving at nearly the same moment — a spot could show up as two rows instead of one.
• Fixed the in-progress QSO arrow not appearing on the Grid, DXCC, WAS, CQ Zone, or ITU Zone maps after switching to that tab mid-QSO — it previously required a manual zoom-reset click to show up. Switching tabs now catches the map back up automatically.
• Fixed TIME_OFF sometimes missing entirely from manually-logged QSOs. A fast contact — common in CW — could log TIME_ON and TIME_OFF within the same displayed second, which was incorrectly rejected as an invalid pair and silently dropped TIME_OFF instead of recording it. A user reported this; it's now fixed.
• Fixed the Map Hub window staying minimized when reopened from the menu. If the Map Hub was minimized and you clicked its menu item again, it stayed minimized instead of coming back to the front; it now restores correctly.

A note from Tim, W4TME

This cycle's two headline features — the QTH Map and real-time QSO backup — both came directly out of things operators asked for: knowing at a glance where a contact physically is, and having a second, automatic safety net for the log beyond a scheduled export. As always, thanks for the bug reports and feature requests that keep pointing SliceLogger at what's actually useful. 73.

---

Free for every FlexRadio operator — Windows 10/11, a FlexRadio (Aurora / FLEX-8000 / FLEX-6000), and SmartSDR for the full integration.

Independent and unofficial — not formally affiliated with or endorsed by FlexRadio, Inc. SmartSDR, SmartLink, multiFLEX, Aurora, FLEX-8000, and FLEX-6000 are trademarks of FlexRadio, Inc. Power Genius XL is a trademark of 4O3A (SKY-SAT D.O.O.). Other product names belong to their respective owners.

SliceLogger v1.0.2.0

SliceLogger 1.0.2.0 is here, and it's the biggest Award Tracker update yet. Every award tab has been rebuilt against its real published rules — ARRL, RSGB, and eQSL/QRZ's own award programs — instead of the simplified approximations SliceLogger started with. On top of that: Band Tracking now follows your QSO's band across every map and the Spot Display, Trends gains a QSL confirmation-rate view and callsign analytics, and a new Chase List tab in Award Tracker tells you which worked-but-unconfirmed contacts would move the needle most. As always, thanks to everyone who filed a bug report this cycle — several of the fixes below trace straight back to your reports.

What's new — Award Tracker: real award rules

Nearly every award tab in the tracker has been reworked this cycle to match its real, independently-verified rules instead of an earlier approximation. The highlights:

• DXCC now carries the real ARRL endorsement ladder (100 through 305+, with finer per-band steps on 160/80/6m/2m/70cm), plus Honor Roll and #1 Honor Roll tracked against your current live entity count.
• WAS merges DC into Maryland per ARRL's real rule, tracks the correct 10-band (160m–10m plus 6m) endorsement list, and adds the real 5BWAS and Triple Play WAS awards.
• WAC now models ARRL's real 5BWAC structure (per-continent endorsements on each of 80/40/20/15/10m, plus 6 more real bands beyond that), rather than an invented flat 12-band list.
• VUCC had a real endorsement-increment bug fixed (1.25m/70cm and 33cm/23cm were swapped), and gained 10 missing real ARRL microwave bands.
• WAZ is simplified to an honest single "WAZ Mixed" zone count — CQ Magazine's own WAZ program, with its own per-band/per-mode structure, is a separate award this app doesn't model.
• ITU Zones is corrected from an invented 90-zone count to RSGB's real 75-zone structure, with the real 5-Band and WARC cross-band credit-sum rules.
• New eQSL award tabs — eDX100, eWAS, eWAC, eGrid, and eZ40 — are now real, independently-modeled awards (verified directly against eQSL's own published rules) that swap in under the eQSL confirmation lens, instead of just relabeling the ARRL numbers with an "e" in front.
• New QRZ award tabs — DX World, Grid Squared, United States, World Continents, and a US Counties award with a real 3,143-county catalog — model QRZ's own published award program the same way.
• New standalone FFMA (Fred Fish Memorial Award) tab tracks the 488 required 6m CONUS grid squares.
• Deleted/historical DXCC entities (Netherlands Antilles, East Germany, and others ARRL has since retired) now show as dimmed rows in the DXCC matrix instead of disappearing, with a tooltip citing the entity's last-valid date.
• Every award tab now shows a per-band total (worked/confirmed/total for a chosen band), and the milestone panel is sectioned into Core Awards, Endorsements, By Band, and By Mode so the easy wins aren't buried under decades of Honor Roll detail.

What's new — Chase List, Trends, and Band Tracking

• Award Tracker "Chase List" tab — ranks your worked-but-unconfirmed contacts by simulating each one's confirmation through the relevant award's own milestone rules, so you can see which QSLs would actually move an award forward instead of guessing.
• Trends "QSL" sub-tab — a matured-window confirmation-rate chart plus a QSL lag curve, so you can see how quickly (and how completely) your QSOs get confirmed over time.
• Trends "Callsigns" sub-tab — a top-15 callsign bar chart and a callsign-by-band heat map, correctly grouping portable/QRP-suffixed contacts (e.g. "/P", "/QRP") with their base station.
• Band Tracking — every map (DXCC, WAS, Grid, CQ Zone, ITU Zone, Propagation) and the DX Spot Display can now automatically follow the Log a QSO form's Band field, each with its own on/off toggle under Settings → Configuration → SliceLogger → Band Tracking. Previously only the DXCC Map had this.
• Grid Map "worked in the last 24h" activity ring — an always-on outline highlights recently-active grids alongside the existing status colors.
• Live "new DXCC entity / new state" hint — the status bar now flashes a hint while you're still filling out the Log a QSO form, before you save, the same way the existing "new grid" hint already worked. New-state messages also name the country (e.g. "DN in Dominican Republic") so a DX state/province code doesn't read like a typo.
• DX Spot Display header redesign — a collapsible confirmation-lens column and a new "Filters" popup tighten up the header, with the Band/Mode-lens picker style now consistent across every map and the Spot Display.
• WSJT-X and manual QSO entry now capture a real TIME_OFF alongside TIME_ON, giving every QSO an honest start/end pair for Club Log matching and any other duration-dependent use.

Bug fixes — your station callsign and ADIF import

• Fixed the "Your Station" display getting hijacked when editing an imported QSO. Selecting an existing QSO to edit was overwriting the top Operator box with that record's own stored station callsign instead of your actual active operator — so an imported record from a different callsign made the whole app appear to be logged in as someone else. Reported by VK2WN.
• ADIF import now warns you if an inbound record's station callsign doesn't match your active operator, with an option to normalize it, and QRZ Logbook/LoTW uploads now always authenticate as your active operator rather than trusting whatever a QSO's own stored value happens to be.
• Fixed imported QSOs not resolving Country for WSJT-X contacts logged while a different instance owned the locked form — those contacts previously kept a permanently blank Country/DXCC entity.
• Fixed 8 incorrect DXCC entity-number keys in the small-map fallback points (Ascension Island, Lakshadweep, Johnston Atoll, Midway Atoll, Clipperton Island, and the South Georgia/Sandwich/Orkney/Shetland group), found while chasing the Country-resolution fix above.

Bug fixes — achievement banner and status bar

• Fixed the Congratulations banner getting clobbered by a LoTW auto-upload, a manual LoTW/eQSL/QRZ Logbook sync, or a WSJT-X/FLDigi live status update landing right after you'd just earned it — all status-bar writers now check whether an achievement banner is still showing before overwriting it.
• The WSJT-X "Form locked by …" status-bar text is now reactive instead of a one-time snapshot that any unrelated status write could wipe with nothing to restore it.
• The WSJT-X lock banner on the Log a QSO form can now be turned off (Settings → Configuration → SliceLogger) if you find it redundant with the status bar; the red lock-conflict warning always stays visible regardless.

Other bug fixes

• Fixed the Trends tab's three chart-toggle radio buttons (heatmap count/rate, mode-mix count/share, QSL confirmation-rate denominator) resetting to their defaults every time the Analytics window was reopened.
• Fixed the shared Mode-lens dropdown (used by the DX Spot Display and the WAS/DXCC/ITU Zone maps) showing blank on open and failing to persist a chosen value in some cases.

A note from Tim, W4TME

This cycle was almost entirely focused on the Award Tracker: going tab by tab and replacing every initial award implementation with the comprehensive, independently-verified rules from ARRL, RSGB, and eQSL/QRZ's own published award programs. And the continued feedback provided through the SliceLogger GitHub Issues helped fix several data correctness issues, which are always my highest priority. Thanks as always for the bug reports that keep this honest. 73.

---

Also on Facebook and groups.io — join either for tips, feedback, and release chatter.

Free for every FlexRadio operator — Windows 10/11, a FlexRadio (Aurora / FLEX-8000 / FLEX-6000), and SmartSDR for the full integration.

SliceLogger v1.0.1.0

SliceLogger 1.0.1.0 is here. This release adds Club Log integration, ADIF export, multi-instance WSJT-X support, and new Award Tracker confirmation lenses — but the headline fix is underneath the hood: the callsign/DXCC resolver has been rebuilt essentially from the ground up, closing out a class of country-resolution bugs that several of you helped track down. Thank you for the reports, the diagnostics zips, and the patience — this one especially was worth getting right.

What's new

• Club Log integration — upload QSOs to Club Log automatically as you log them, or in a bulk pass from Settings. A new Club Log tab in Settings holds your credentials and auto-upload preference, and Log a QSO now shows a live, read-only commentary badge when Club Log's own DXCC data disagrees with what's on the form — informational only, it never changes your log for you.
• ADIF export — export a filtered subset of your log (by date range, band, mode, and more) or your entire log in one click, from the new ADIF Export window.
• Multi-instance WSJT-X support — run more than one WSJT-X instance against SliceLogger at once, with per-instance Slice-Letter mapping so contacts log against the right radio slice instead of colliding.
• New Award Tracker confirmation lenses — view your progress by QRZ, LoTW+QSL Card, or any confirmation source, in addition to the existing lens. A new Phone/CW/Digital Mode lens is also available across the Award Tracker, maps, globe, and Spot Display.

Bug fixes — DXCC and country accuracy

• The callsign/DXCC resolver has been rebuilt from the ground up. Rather than patching the previous lookup logic, SliceLogger now resolves every callsign against the full AD1C CTY.DAT country/prefix database directly, instead of falling back to a smaller, hand-maintained table for certain callsigns — which is what caused reports like Franz Josef Land (RI1FJL) resolving with a blank country and no DXCC entity. That specific case, and the broader class of callsigns it represents, is fixed. The new resolver has been validated against a corpus of over 63,000 real and reference callsigns with zero unexplained discrepancies, and went through hands-on testing with live QSOs before release.
• A small number of genuinely ambiguous callsign prefixes (where the prefix alone doesn't determine the DXCC entity — for example a "3Y0" DXpedition callsign, which could be Bouvet Island or Peter I Island) now correctly show as unresolved instead of a specific guess that could be wrong.
• Fixed DXCC resolution for a short base callsign with a call-area suffix resolving incorrectly in some cases.
• Fixed the Data Integrity Check's CTY.DAT-based check reverting a DXCC entity you'd already confirmed via Club Log back to CTY.DAT's own (sometimes less specific) answer.

Bug fixes — WSJT-X

• Fixed the WSJT-X instance-mapping "Add Row" button silently failing on a second click.
• Fixed a same-callsign frequency freeze that could occur with the new multi-instance mapping in place.
• Grid Square now fills automatically from an earlier overheard CQ when WSJT-X supplies none of its own for the logged contact.
• Corrected the same-station Tx-collision warning banner, which previously claimed the radio "refuses to transmit on either" instance when two same-station WSJT-X instances both have Enable Tx armed. Burn-in testing showed the real behavior is a round-robin: the radio transmits every other cycle while the other instance goes silent, until the older instance's Enable Tx is disabled. The banner now describes that behavior and is recolored red to reflect that it's a real condition needing prompt operator action.

Bug fixes — maps

• Fixed a visual spike on the DXCC Map's pending-QSO arrowhead and a related outline-rendering spike affecting map arrowheads generally.
• Refined the deleted-DXCC-entity guard to use each entity's own last-valid date instead of one shared cutoff, correcting a near-miss on a couple of historical entities.

Other bug fixes

• Fixed log grid column stretching and header double-click misbehavior, including a case where resizing a column from its left edge could be misidentified as resizing a different column.
• Fixed clicking a spot to tune silently dropping sub-kHz frequency precision.
• You can now multi-select and copy rows in the Search QSOs window.
• QRZ/HamQTH lookups now retry once on a failed session before giving up, instead of failing silently on the first attempt.

Database maintenance

The Data Integrity Check's DXCC Entity/Country/Zone cross-check (added as an optional review tool) has been removed after testing showed it flagging too many false positives on legitimate multi-entity callsign prefixes. Log a QSO's new Club Log commentary badge (above) takes its place as a safer, per-QSO second opinion — informational only, never an automatic correction. The Apply step in Data Integrity Check is also noticeably faster this release, and scans now show progress as they run.

---

A note from Tim, W4TME: The callsign resolver rebuild in this release started from a handful of reports that a specific DXCC entity — Franz Josef Land — was coming back blank. Chasing that down turned into a much bigger rethink of how SliceLogger resolves a callsign to a country in the first place, and I wanted to get it right rather than patch around the symptom. Thank you to everyone who reported a country-resolution bug this cycle, with a diagnostics zip or without — this fix is built on your reports. 73.

---

Free for every FlexRadio operator — Windows 10/11, a FlexRadio (Aurora / FLEX-8000 / FLEX-6000), and SmartSDR for the full integration. No trial, no upsell, and staying free. The one catch: no formal support desk — instead, a direct line to the developer who's actively building it and listening hard. Also on Facebook and groups.io for tips, feedback, and release chatter.

See the attached PDF for the full formatted release notes.

SliceLogger v1.0.0.0

SliceLogger 1.0.0.0 is here. After six 0.3.0.0 pre-release cycles built almost entirely on real user reports — FlexRadio connectivity, DXCC/award accuracy, QSL confirmations, and more — this release closes out that stabilization run with another full pass of fixes. Thank you to everyone who filed an issue, sent a diagnostics zip, or tested a build this cycle — this release is built almost entirely out of your reports.

What's new

• FT2 digital mode support — FT2 contacts (certified in ADIF 3.1.7) now import and log correctly as Mode MFSK / Sub FT2 instead of showing as generic, indistinguishable "MFSK." A new read-only Sub column next to Mode in the log grid shows the submode for FT2 and any other MFSK-family contact.

Bug fixes — FlexRadio and rotator connectivity

• Fixed FlexRadio disconnecting and reconnecting roughly every minute on an otherwise idle, healthy connection — a regression from an earlier idle-timeout fix that assumed the radio always pushes its own keepalive traffic. SliceLogger now actively probes the connection itself, so a quiet session no longer gets mistaken for a dead one.
• Fixed the rotator status bar getting stuck on "not responding" even after the connection had already recovered and heading updates were flowing normally again.

Bug fixes — DXCC and country accuracy

• Fixed a class of external-territory callsigns resolving to the wrong DXCC entity (for example VK9WX/Willis Island showing as Australia) — audited and corrected roughly 40 prefix mappings against ARRL's official current-entities list, and added a safety net so any future gap in that table can no longer silently override an already-correct lookup.
• Fixed "/R" (Rover) suffixed callsigns resolving to the wrong country — a rover-tagged call (e.g. on a VHF/UHF contest mobile) could be misread as a geographic indicator and resolve to an unrelated country on the other side of the world.
• Fixed "Russia" showing instead of "European Russia"/"Asiatic Russia" in a fallback naming path — display-only; the underlying DXCC entity and award counts were never affected.

Bug fixes — WSJT-X

• Fixed WSJT-X-logged QSOs silently dropping a POTA reference, County, or coordinates typed into the Extended Fields panel before clicking Log QSO in WSJT-X — those fields were captured on screen but never carried into the saved record.
• Fixed FT2, FST4, and FST4W contacts logged from WSJT-X saving as a bare, non-standard Mode with no submode recorded, instead of the correct MFSK/<submode> form.

Bug fixes — maps and space weather

• Fixed your home-location marker landing tens of miles from your actual location (up to roughly 70 miles at worst case, depending on latitude) on the Weather Radar, Propagation, WAS, DXCC, CQ Zone, and ITU Zone maps when only a 6-character grid square was set (no explicit Lat/Lon) — your full grid precision is now used for the map marker instead of being trimmed down to a coarse 4-character square first.
• Fixed the Kp Index tile reading misleadingly low during active geomagnetic storms — NOAA's real-time feed resets partway through each 3-hour reporting window, which could show a calm reading during a real storm. The tile now tracks the peak reading for the window instead of whatever the feed happens to show at that instant.

Other bug fixes

• Fixed several windows not reopening after being minimized — Award Tracker, Spot Display, the LoTW/eQSL/QRZ Upload dialogs, and Weather Alerts could all get stuck requiring a manual restore from the taskbar instead of reopening normally from the menu.

Database maintenance

A new, entirely optional Data Integrity Check (Settings → Database → Run Data Integrity Check…) is available if you want to review your log against fixes from this cycle and earlier — a few past bugs (DXCC entity resolution, Mode/SubMode formatting) could leave a QSO with data that was wrong at the time it was logged, even though the bug itself is long since fixed. It's not something every log needs — most operators won't have hit any of the underlying bugs — and nothing is changed automatically: every proposed correction is shown next to the current value, and you choose what to apply, per QSO or by category.

System requirements

Windows 10 (1809+) or Windows 11, 64-bit · Microsoft Edge WebView2 Runtime · .NET 8 Desktop Runtime (x64) · a FlexRadio Aurora, FLEX-8000, or FLEX-6000 running SmartSDR for full integration (you can log without a radio connected).

Getting started

The attached Release Notes PDF has the full list, or use Help → Getting Started inside the app any time.

---

A note from Tim, W4TME

Six pre-release cycles ago I set out to get SliceLogger's FlexRadio integration, DXCC/award accuracy, and QSL confirmation handling solid enough to call it stable — and the thing that actually got it there was the steady stream of real reports from real operators running real logs, several with diagnostics zips or their own hardware to confirm a fix. Nearly every item above traces back to someone taking the time to describe a symptom clearly. Thank you, and 73.

---

SliceLogger is free, and staying free — no trial, no upsell. Built by a ham, for hams. There's no formal support desk — instead, a direct line to the developer, who's actively building it and listening hard. Please report anything missing or unexpected.

Also on Facebook — join the SliceLogger group for tips, feedback, and release chatter.

Independent and unofficial — not formally affiliated with or endorsed by FlexRadio, Inc. SmartSDR, SmartLink, multiFLEX, Aurora, FLEX-8000, and FLEX-6000 are trademarks of FlexRadio, Inc. Power Genius XL is a trademark of 4O3A (SKY-SAT D.O.O.).

SliceLogger v0.3.0.0-rc.6

SliceLogger v0.3.0.0-rc.6 — a bug-fixes-only stabilization release, no new screens, mostly under-the-hood correctness fixes across FlexRadio connectivity, DXCC/Award accuracy, and QSL confirmation handling, plus one small addition. This is expected to be the last 0.3.0.0 pre-release before v1.0.0.0.

What's new

• Ad-hoc "Spot QSO" checkbox — a new checkbox in the Log a QSO form, just above the Log QSO button, sends a single contact to the DX cluster when logged (or updated) without turning on the global "spot every QSO" setting. Resets after each QSO so it never carries over to the next one, and works when editing an existing QSO too.
• First-run help page — a brand-new install now opens the Getting Started help page in your browser automatically the first time you launch SliceLogger, so the setup steps aren't something you have to already know to go looking for. Shown once; existing installs are unaffected.

Bug fixes — FlexRadio connectivity

• Fixed a duplicate slice-bar row — connecting to a radio could show the same slice twice under certain timing (most likely two connection attempts starting in close succession, e.g. auto-connect racing another connect). Only one real connection attempt is now ever in flight at a time.
• Fixed a silently dead FlexRadio connection — if the underlying connection died without a clean disconnect (most likely over SmartLink), SliceLogger could keep showing "Connected" indefinitely with a frozen slice bar. A read timeout now detects this and recovers automatically.
• Fixed cross-contamination between a Power Genius XL and a 4O3A TunerGenius XL connected at the same time — the two devices share the same underlying status protocol, which could confuse their identity and state. Filtered to Power Genius XL for now; TunerGenius XL support is planned once we have hardware to test against.
• Fixed forward-power readings being off on FLEX-6x00/8000-series radios — confirmed and corrected against a real wattmeter, matching SmartSDR's own reading within ±0.5 W at every power level tested.
• Fixed Radio Serial Number, Firmware Version, and Telemetry not populating for some users — traced to a Windows Firewall permission from the first-run prompt: only the Private network box was checked, not Public, which can silently drop the radio's telemetry stream whenever Windows reclassifies your network (this can happen after a Windows Update, with no warning). The Help docs now walk through this prompt clearly — see Radio Setup and SmartLink Setup.

Bug fixes — DXCC and Award Tracker accuracy

• Fixed the DXCC Entity field silently reverting when editing an existing QSO — a manual correction could be quietly undone on save.
• Fixed the DXCC "Worked" count being inflated by historical or deleted ARRL entity numbers (DXCC entities are occasionally merged, split, or retired) — old QSOs against a now-deleted entity no longer count toward your current total.
• Fixed the Award Tracker not refreshing when a QSO was edited, deleted, or added via ADIF import — it's now kept in sync with your log the same way every other award-related view already was.
• Fixed the WAS (Worked All States) report counting some non-US QSOs as worked states — a Venezuelan province code was colliding with a US state abbreviation.
• Fixed Puerto Rico, US Virgin Islands, and similar callsigns having their DXCC Country silently overwritten back to "United States" by callbook lookups — a callbook's own country field is postal/political, not DXCC entity, so it no longer overwrites an already-correct value.

Bug fixes — QSL confirmations and credentials

• Fixed LoTW, eQSL, and QRZ Logbook silently rejecting credentials that had accidental leading/trailing whitespace — passwords and API keys weren't being trimmed the way usernames already were.
• Fixed a LoTW auto-upload failure overflowing the main window's status bar with TQSL's raw, multi-line error output — failures now show a proper dialog with the full detail instead.

Other bug fixes

• Fixed the WSJT-X form locking fields it doesn't actually source — only Callsign, Frequency, Band, Mode, RST Sent/Rcvd, Grid Square, and TX Power stay locked during an active WSJT-X contact now. Operator Name, Country, and the whole Extended Fields panel (including QSL Sent/Rcvd) are editable throughout, so you can add a POTA reference or fix an address without waiting for the QSO to log.
• Fixed the Extended Fields panel being excluded from Tab order — tabbing through Address→Comment now works field-to-field as expected, and tabbing out of the last field saves the QSO.
• Fixed Settings tabs silently reverting each other's saved changes — unchecking auto-upload on more than one QSL tab (LoTW, eQSL, QRZ Logbook) in the same session and saving each could leave only the last save actually persisted.
• Diagnostics zips now capture more useful logs for the silent-failure reports above — several targeted logging points were added so a future report has an actual trace to work from.

System requirements

Windows 10 (1809+) or Windows 11, 64-bit · Microsoft Edge WebView2 Runtime · .NET 8 Desktop Runtime (x64) · a FlexRadio Aurora, FLEX-8000, or FLEX-6000 running SmartSDR for full integration (you can log without a radio connected).

Getting started

The attached Release Notes PDF has the full list, or use Help → Getting Started inside the app any time.

---

A note from Tim, W4TME

Thank you to everyone who filed a GitHub issue this cycle — nearly every fix above traces back to someone taking the time to report a real symptom clearly, several with a diagnostics zip or a live confirmation on their own hardware. That kind of detail is what makes finding the actual root cause possible instead of just guessing. Keep them coming — and thank you for your patience while this cycle focused entirely on stability rather than new features. v1.0.0.0 is next.

---

SliceLogger is free, and staying free — no trial, no upsell. As a pre-release, there's no formal support desk; what you get instead is a direct line to the developer, who's actively building it and listening. Please report anything missing or unexpected.

Also on Facebook — join the SliceLogger group for tips, feedback, and release chatter.

Independent and unofficial — not formally affiliated with or endorsed by FlexRadio, Inc. SmartSDR, SmartLink, multiFLEX, Aurora, FLEX-8000, and FLEX-6000 are trademarks of FlexRadio, Inc. Power Genius XL is a trademark of 4O3A (SKY-SAT D.O.O.).

SliceLogger v0.3.0.0-rc.5

SliceLogger v0.3.0.0-rc.5 — an emergency patch release, not the usual feature update. It fixes a false "older radio firmware detected" warning that a number of you hit on rc.4, along with two closely related bugs it exposed.

The bug: a wrong firmware warning claiming version 1.4.0.0

On rc.4, connecting to a radio could pop up "Older radio firmware detected" claiming the radio was running firmware version 1.4.0.0 — even on radios running current SmartSDR (4.2.x, 4.3.x, and newer). This is not a real firmware problem; your radio is fine. The warning is always wrong when it shows that specific version, and rc.5 fixes it so it can't happen again.

The root cause: SliceLogger was trusting the live radio connection's own self-reported version string for this check. That value doesn't reliably reflect the radio's real firmware — confirmed on both SmartLink and plain local-network connections, across multiple radio models (FLEX-6500, FLEX-6600, FLEX-6700, and Aurora AU-510M). SliceLogger now trusts the version reported by radio discovery / SmartLink's own radio list instead, which has been accurate in every case checked — including a direct hardware confirmation from an affected user before this release went out.

What's fixed in this release

• The false "older firmware detected" warning — described above, on both SmartLink and local-network connections. Also closes a narrower timing window where the warning could fire from a not-yet-confirmed version during the moment a connection was still being established.
• A stuck-dialog bug this exposed — connecting to a radio with no SmartSDR client running yet could show two message boxes at once (the firmware warning and the "no SmartSDR client running" notice), with the second one locking out the first so it couldn't be dismissed. The two now always appear one at a time.
• A rare timing edge case in SmartLink auto-reconnect — if you switched your active SmartLink account during the brief window while SliceLogger was waiting to auto-reconnect a radio that had just dropped, the reconnect could go out under whichever account was active at that moment instead of the one the radio belongs to. This never exposed any credentials or data — the worst case was a confusing failed or wrong-account reconnect attempt. SliceLogger now detects the mismatch and cancels the reconnect with a status message instead.

If you saw this warning before

Nothing else to do — just update to rc.5 and reconnect to your radio as usual. The warning was cosmetic (a wrong message box), not a sign of any real problem with your radio, your log, or your data.

System requirements

Windows 10 (1809+) or Windows 11, 64-bit · Microsoft Edge WebView2 Runtime · .NET 8 Desktop Runtime (x64) · a FlexRadio Aurora, FLEX-8000, or FLEX-6000 running SmartSDR v3.10.15+ for full integration (you can log without a radio connected).

---

A note from Tim, W4TME

Thank you to everyone who reported this quickly and clearly, and especially to the folks who tested a pre-release build directly with me to confirm the fix before this went out. That kind of feedback loop is exactly what makes a patch like this possible to ship with confidence.

---

SliceLogger is free, and staying free — no trial, no upsell. As a pre-release, there's no formal support desk; what you get instead is a direct line to the developer, who's actively building it and listening. Please report anything missing or unexpected.

Also on Facebook — join the SliceLogger group for tips, feedback, and release chatter.

Independent and unofficial — not formally affiliated with or endorsed by FlexRadio, Inc. SmartSDR, SmartLink, multiFLEX, Aurora, FLEX-8000, and FLEX-6000 are trademarks of FlexRadio, Inc.

SliceLogger v0.3.0.0-rc.4

SliceLogger v0.3.0.0-rc.4 — a bigger update than usual since 0.3.0.0-rc.3, headlined by a major rework of ADIF import, real DXCC trend and mode analytics, a live QSO arrow on the DXCC Map, GPS location auto-fill for GNSS/GPSDO-equipped radios, rotator heading calibration, and a substantially reworked DX Spot Display, alongside a long list of fixes.

ADIF import: consolidated and more accurate

Every ADIF-consuming path in SliceLogger — the general File → Import ADIF, plus the LoTW, eQSL, and QRZ Logbook importers — used to carry its own separate, hand-written copy of the logic that maps an ADIF record's fields onto a QSO. That meant a bug found and fixed in one path routinely had to be manually rediscovered and reapplied in the other three, and it happened more than once. All four now share one field-mapping path, so a fix (or an accuracy improvement) lands everywhere at once going forward.

• New fields captured on import that previously had no home in the database at all: MY_STREET, EMAIL, the QSL_VIA family, RX_PWR, and QSO_DATE_OFF/TIME_OFF.
• QRZ confirmation status now reads and writes the real ADIF-standard QRZCOM_QSO_UPLOAD_STATUS/QRZCOM_QSO_UPLOAD_DATE fields, instead of a SliceLogger-specific field that only this app understood — so a QRZ confirmation recorded by another logging program is now recognized correctly on import.
• Fixed LoTW ADIF import silently duplicating every FT4/JS8/Q65 QSO as a separate "MFSK" entry instead of matching it against the QSO already in your log, plus the same class of bug in the eQSL/QRZ confirmation sync path.
• Re-importing a file you've already imported is smarter now. Previously, a duplicate record was simply skipped — even if it carried confirmation data (LoTW, eQSL, QSL Card, or QRZ) your existing QSO didn't have yet. Now, a duplicate that carries new confirmation status updates the matching QSO already in your log instead of being silently discarded. See the note below if you want to take advantage of this for data you imported before rc.4.

Want the new confirmation data on QSOs you've already imported?

If you imported a log from LoTW, eQSL, QRZ Logbook, or another program before this release, you can pick up any confirmation status the earlier import missed by simply re-importing the same file again:

1. Open File → Import ADIF… and choose the same file you imported previously.
2. SliceLogger recognizes every QSO already in your log as a duplicate, as before — but now, any of them carrying confirmation data your log doesn't already have gets updated in place, rather than skipped.
3. The import summary reports this separately, e.g. "12 existing QSO(s) updated with confirmation status, 340 duplicate(s)."

No backup or log-clearing needed — nothing is deleted or duplicated, and QSOs that don't carry any new confirmation data are left untouched. This does not retroactively merge QSOs that were already stored as separate duplicate entries by the FT4/JS8/Q65 bug above; if you suspect you have any, check your log for a pair of otherwise-identical QSOs where one shows Mode "MFSK."

What's new in this release

• Analytics (renamed from Stats): DXCC and mode trend charts — a new DXCC entities worked/confirmed trend chart (LoTW, eQSL, and QSL Card lines together) and a mode breakdown chart with a mode-mix-by-year view. The Trends tab is now split into four sub-tabs (Growth, Bands, Modes, Activity Patterns) to cut down on scrolling.
• DXCC Map: live QSO arrow — while logging a QSO, the map draws an arrow to the station you're working, bent to the true great-circle path rather than a straight line, with a new/worked highlight ring and a Great Circle short-path/long-path panel matching the Grayline globe. A "Follow QSO band" toggle keeps the map in sync with whatever band is in the Log a QSO form. Small-nation callsigns (Palau, Micronesia, Lord Howe Island, and similar) that the underlying world map has no geometry for now resolve via CTY.DAT instead of silently having no arrow.
• GPS location prefill for GNSS/GPSDO-equipped radios — on a FLEX-8000 with GNSS or a FLEX-6000 with GPSDO, your Operator profile's latitude/longitude can auto-fill from the radio's own satellite-locked position instead of typing it in by hand.
• Rotator heading calibration — a new antenna offset field (−180° to 180°) on both the DCU-1 and GS-232A/B rotator integrations corrects a systematic heading error some controllers report, applied to both the displayed heading and Go To commands.
• DX Spot Display, reworked:
  • Reopening the window now seeds it with your recent spot history instead of starting empty at zero.
  • Columns (UTC, Freq, DX Call, Band, Mode, Spotter, Country, Comment) can be hidden individually, and the window's minimum width shrinks to fit whichever columns you keep.
  • A new Spotting Station Continents/Radius filter narrows the incoming feed by how far away (or which continent) the reporting station is from your own QTH — alongside a callsign-prefix filter.
  • The header's cluster node Callsign now stays in sync with your active operator automatically, with a per-node opt-out for shared/club logins.
  • The header shows a colored status dot for the connection state — green connected, orange while connecting or retrying, red once reconnect attempts are exhausted — instead of one uniform warning color.
• Previous-QSO detail — the duplicate-callsign banner in Log a QSO now always shows a "Previously Logged" count, with an opt-in setting to filter the main log grid to just that callsign's prior contacts instead of a separate popup list.
• Log grid remembers its layout — column order and width now persist across restarts instead of resetting every time.
• New SliceLogger logo and app icon, replacing the original placeholder mark everywhere in the app and help docs.

Improvements

• Renamed for clarity: "Cards" QSL menu item → "QSL Cards"; "Download from LoTW Logbook (ADIF)" → "Import LoTW Logbook (ADIF)" (it imports an already-downloaded file, it doesn't fetch anything); log grid "QSL Sent/Rcvd" columns → "QSL Card Sent/Rcvd"; Settings → Spots "Username" → "Callsign".

Bug fixes

• Fixed Kp Index and A Index showing no data — NOAA/SWPC now rejects requests with no User-Agent header, which this one service had never set.
• Fixed a FLEX-8600 false "older radio firmware detected" warning that could recur even after being fixed once, caused by a discovery beacon overwriting the connected radio's live, correctly-detected firmware version roughly once a second.
• Fixed the DXCC entity field going stale instead of clearing when a callsign becomes unresolvable.
• Fixed the DX Spot Display header getting stuck on "Connecting…" while spots were actively flowing in, through several rounds of hardening — including a case where the header simply never received the connection-succeeded notification even though the underlying connection was fine, now self-corrected the moment a spot actually arrives.
• Fixed the DX cluster band filter appearing stuck on a previously-selected band after being cleared and saved — some cluster software persists accept/reject filters against the login itself rather than the network session, so a stale filter could silently survive a reconnect.
• Fixed a real concurrency bug where double-clicking two spots in quick succession could overwrite the Log a QSO form with the wrong grid square, depending on which radio reply happened to arrive last rather than which spot was clicked last.
• Fixed SettingsViewModel leaking a FlexRadio property-change subscription.

System requirements

Windows 10 (1809+) or Windows 11, 64-bit · Microsoft Edge WebView2 Runtime · .NET 8 Desktop Runtime (x64) · a FlexRadio Aurora, FLEX-8000, or FLEX-6000 running SmartSDR v3.10.15+ for full integration (you can log without a radio connected).

Getting started

The attached Release Notes PDF has the full list, or use Help → Getting Started inside the app any time.

---

A note from Tim, W4TME

Thank you to everyone who has filed a GitHub issue or suggested an enhancement this cycle — several of the fixes and features above exist because someone took the time to report them clearly. A well-written issue makes tracking down the real cause, and actually fixing it, far more efficient than a general "something's wrong" message ever could. Keep them coming.

---

SliceLogger is free, and staying free — no trial, no upsell. As a pre-release, there's no formal support desk; what you get instead is a direct line to the developer, who's actively building it and listening. Please report anything missing or unexpected.

Also on Facebook — join the SliceLogger group for tips, feedback, and release chatter.

Independent and unofficial — not formally affiliated with or endorsed by FlexRadio, Inc. SmartSDR, SmartLink, multiFLEX, Aurora, FLEX-8000, and FLEX-6000 are trademarks of FlexRadio, Inc. Power Genius XL is a trademark of 4O3A (SKY-SAT D.O.O.).

SliceLogger v0.3.0.0-rc.3

SliceLogger v0.3.0.0-rc.3 — the third pre-release under the SliceLogger name, in as many weeks. A focused update since 0.3.0.0-rc.2 that adds automatic QSL uploading, a propagation-history heat view for the Grid Map, an in-app update checker, and a long list of fixes and refinements, including improved fidelity when importing logs from other programs.

What's new in this release

• Automatic QSL upload after logging — LoTW, eQSL, and QRZ Logbook now upload automatically right after you log a QSO, plus a background confirmation sync at startup. No more manual QSL Card Update runs for routine confirmations.
• Grid Map: Propagation History heat view — tints grid squares by contact density so you can see which paths reliably propagate, independent of confirmation status.
• Help → Check for Updates — checks GitHub Releases for a newer version, with an opt-in toggle to include pre-releases.
• GNSS/GPSDO state annunciator — the radio bar now color-codes GNSS/GPSDO running state (green when locked, amber while locking/warming up, red otherwise).
• A4 mailing label sheets — added Avery L7160/J7160 as a sheet option alongside the existing Avery 5160, for EU/international customers.
• Spots: ISO country code column — DX Spot Display now shows the spotted station's country without widening the window.
• ADIF import: SIG/SIG_INFO support — POTA/SOTA/IOTA-style activity data now imports and round-trips; FT4/MFSK mode also now imports correctly (was misclassified).

Bug fixes

• Fixed LoTW and eQSL confirmation status being silently dropped during ADIF import when the source logger reports a confirmation without a companion date field — a pattern seen in exports from N3FJP's Amateur Contact Log and Log4OM. SliceLogger now falls back to using the QSO's own date so the confirmation is preserved instead of lost. (QSL Card Sent/Rcvd — physical postal cards — are intentionally not derived this way: real-world AC Log data shows its generic confirmation flag tracks confirmation via any method, not specifically a card exchanged by mail, so SliceLogger no longer treats it as one. See the note below if this affects QSOs you've already imported.)
• Fixed Aurora transceivers (AU-510/520 series) reading TX power 2–5x too high compared to an external wattmeter.
• Fixed a LoTW/QRZ confirmation sync hang on large logs (30,000+ QSOs) — syncing was committing to the database once per record; it's now batched, with progress reporting.
• Fixed the WSJT-X Log a QSO form's frequency display not updating when switching radio stations.
• A Spot click on a form that WSJT-X has locked now clearly flags the conflict instead of silently doing nothing.
• Spots forwarded to the radio's panadapter now carry a real timestamp — every spot previously showed 1970/01/01 00:00:00Z in its tooltip, and the radio's spot lifetime/expiration didn't work correctly without one.
• Weather Conditions is now guarded against a blank/unconfigured station location silently showing the wrong ("Null Island") weather; added the attribution Open-Meteo requires.
• Fixed the Settings dialog being mistakenly minimizable while open — doing so left the main window disabled with no way to restore it, which looked exactly like the app hanging.
• Fixed the log grid's selection color washing out to a low-contrast shade when focus left the grid (e.g. clicking Edit), making the callsign and QSL confirmation dates hard to read.
• Log a QSO fields now select their contents on focus — a prefilled value like RST's "599" is selected when you tab in, so typing replaces it immediately instead of requiring a manual delete first; also fixes a related bug where a digital-mode signal report could get corrupted with a stray "+".
• Normalized "Paper QSL" terminology to "QSL Card" throughout the app and help docs.
• The PGXL amp's Operate/Standby annunciator is now bold and amber in Operate for better at-a-glance visibility.
• Widened the QSL Card Update window's left panel to match the other confirmation-picker windows (was noticeably narrower, with lopsided margins).
• Compact Mode could be resized narrow enough to clip the Your Station bar's collapse/expand button off the edge of the window; raised the minimum width to prevent it.
• Fixed the Grid Map's orange "Needed Grid Highlight" squares sometimes showing no locator label — it required a second, unrelated label toggle ("Show Not Worked Labels") to also be on.
• Added a color-key legend to the Grid Map (a new "Legend" button in the header) explaining what each grid square color means — the bright-orange "never worked" highlight and the dark-goldenrod "worked but not yet confirmed" highlight were easy to mistake for each other.

If you already imported an AC Log or Log4OM file

QSOs imported before the ADIF confirmation-date fix above are already in your log with blank LoTW/eQSL confirmation dates — simply re-importing the same file again won't pick it up, since SliceLogger skips records it already has rather than updating them. To bring those confirmations in:

1. Back up first: File → Export ADIF… to save your current log (this captures anything you've logged or edited since the original import).
2. Clear your log: Settings → Maintenance → Database → Delete ALL log entries (two confirmations required — this cannot be undone, which is why step 1 matters).
3. Re-import your original AC Log or Log4OM file first, via File → Import ADIF… — this is what lets the corrected reader populate the confirmation dates.
4. Then import the file you exported in step 1 — it restores everything logged or edited since the original import, and duplicates of the QSOs you just re-imported are automatically skipped.

The order in steps 3 and 4 matters — reversing them leaves the fix without effect. If any of those QSOs were already picked up by a separate LoTW/eQSL/QRZ sync since your original import, a small number may show a slightly less precise confirmation date afterward — the confirmed status itself is unaffected, only the exact date shown.

System requirements

Windows 10 (1809+) or Windows 11, 64-bit · Microsoft Edge WebView2 Runtime · .NET 8 Desktop Runtime (x64) · a FlexRadio Aurora, FLEX-8000, or FLEX-6000 running SmartSDR v3.10.15+ for full integration (you can log without a radio connected).

Getting started

The attached Release Notes PDF has the full list, or use Help → Getting Started inside the app any time.

---

SliceLogger is free, and staying free — no trial, no upsell. As a pre-release, there's no formal support desk; what you get instead is a direct line to the developer, who's actively building it and listening. Please report anything missing or unexpected.

Also on Facebook — join the SliceLogger group for tips, feedback, and release chatter.

Independent and unofficial — not formally affiliated with or endorsed by FlexRadio, Inc. SmartSDR, SmartLink, multiFLEX, Aurora, FLEX-8000, and FLEX-6000 are trademarks of FlexRadio, Inc. Power Genius XL is a trademark of 4O3A (SKY-SAT D.O.O.).

SliceLogger v0.3.0.0-rc.2

SliceLogger v0.3.0.0-rc.2 — the second pre-release under the SliceLogger name, a focused update since 0.3.0.0-rc.1 built from your rc.1 feedback.

What's new in this release

• QRZ Logbook integration — upload and sync confirmations with your QRZ.com Logbook, joining LoTW and eQSL with the same status-glyph treatment in the log grid.
• Search QSOs — a new Find menu window searches your whole log by callsign, band, mode, and date range, independent of any QSL service — the fast way to find and edit a contact once your log is too long to scroll. The LoTW, eQSL, QRZ, and QSL Card windows picked up a shared look and feel as part of this work.
• Compact Mode — a header toggle hides the log grid and shrinks the main window down to just the Log a QSO form, for a smaller desktop footprint. Your preferred size is remembered.
• Stats → Trends tab — a new tab in the Statistics window: a QSO-growth line, a per-band bar chart, and month/hour rate heatmaps.
• JTAlert sync — Settings → Apps → JTAlert adds on-demand alert-database sync for JTAlert users.

Improvements

• Statistics gained a paper-QSL column, a Confirmed % column, and a confirmation conversion-rate column.
• The radio picker blocks a redundant reconnect to the radio you're already connected to.
• Help menu setup and reference topics are now grouped under a Setup How-To submenu.
• A firmware-version warning appears on connect if your radio's SmartSDR firmware is below the tested minimum.
• Award Tracker remembers which VUCC field group was expanded across close and reopen, and auto-expands the first one.
• Log a QSO now saves on Enter once the required fields are filled in — no more reaching for the mouse.

Bug fixes

• Fixed a false-collision bug where two different DX-prefix-override operators sharing the same prefix (e.g. 3D2/W1ABC and 3D2/K5XYZ) could get their dedup and QSL confirmations cross-matched.
• Fixed dedup and QSL confirmation matching not recognizing callsign suffixes like /0, /P, and /M as the same station.
• ADIF import now rejects records with a malformed callsign instead of logging them.
• Fixed the Beam Heading/Distance display going stale after clearing a QSO or editing an existing one.
• TX Pwr no longer auto-fills from the radio until the callsign has been verified.
• Fixed a spurious "+" sign appearing while typing a CW or phone RST.
• Fixed stale Country, CQ Zone, and ITU Zone data surviving a callsign switch.
• Fixed spot click-to-tune not filling the Log a QSO form in some cases, and out-of-range spots are now handled gracefully.
• Fixed the Spots window's Clear button getting clipped at the window's minimum size.
• Clearer messaging when SmartLink disconnects mid-negotiation.
• Fixed eQSL sync abandoning the remaining batches after one batch failed.
• The app now always disconnects cleanly from FlexRadio and SmartLink on exit.
• Fixed a missing warning when bundled map resources can't be found.
• Fixed the password fields in Settings (LoTW, QRZ, HamQTH, eQSL, QRZ Logbook API key, and the Spot cluster node) scrambling input when typed manually — the cursor was jumping back to the start after every keystroke. Pasting a password was unaffected.
• Fixed Mode staying stuck on whatever the first QSO of the session used instead of following your radio's transmit slice — most noticeable in multiFLEX when switching between stations operating on different modes.
• Fixed a fresh-install race where the very first launch could fail to auto-connect to a saved radio if Windows Firewall's permission prompt hadn't been answered yet.

System requirements

Windows 10 (1809+) or Windows 11, 64-bit · Microsoft Edge WebView2 Runtime · .NET 8 Desktop Runtime (x64) · a FlexRadio Aurora, FLEX-8000, or FLEX-6000 running SmartSDR v3.10.15+ for full integration (you can log without a radio connected).

Getting started

The attached Release Notes PDF has the full list, or use Help → Getting Started inside the app any time.

---

SliceLogger is free, and staying free — no trial, no upsell. As a pre-release, there's no formal support desk; what you get instead is a direct line to the developer, who's actively building it and listening. Please report anything missing or unexpected.

Also on Facebook — join the SliceLogger group for tips, feedback, and release chatter.

Independent and unofficial — not formally affiliated with or endorsed by FlexRadio, Inc. SmartSDR, SmartLink, multiFLEX, Aurora, FLEX-8000, and FLEX-6000 are trademarks of FlexRadio, Inc. Power Genius XL is a trademark of 4O3A (SKY-SAT D.O.O.).