Nexus 1.3.0
Released 13 August 2026. The current release is 1.24.0. Download it · Every version
Added
-
RTTY has a TX button now, like MMTTY — key up once and type.
The RTTY dock gained a TX button. Click it and the transmitter comes up and stays up: type and the characters go out as you type them, and between keystrokes the air carries diddle (the LTRS idle every RTTY station sends), so the far end holds sync instead of hearing you drop out at the end of every line. Click TX again and it sends the rest of what you typed and unkeys. No more pressing Enter for every line, which is what this was reported for. The F-key macros type into the live transmission while it is up rather than queueing a separate over behind it, and Enter puts a new line on the air instead of sending. Enter-per-line still works exactly as before when the TX button is off — nothing about the old way changed. Because this is the one transmission in Nexus that keys with no fixed end, it is wrapped in more stops than anything else, not fewer. Stop TX, the dock's Esc/Stop macro, the TX-enable switch and Esc (RTTY now has the keyboard shortcut CW always had) each cut it instantly. So does anything that takes RTTY off the rig without you pressing a stop at all — leaving the RTTY section, tuning to a frequency you are not licensed for, starting a tune carrier, or switching radios — each of which unkeys within about a fiftieth of a second. Your TX watchdog applies exactly as it does to any other over (typing keeps it happy, walking away does not), and above it sits a hard ten-minute ceiling on a single continuous over that nothing can extend, so a stuck key cannot buy an unattended carrier. If the app itself locks up, the transmitter unkeys on its own within about a second rather than staying keyed. Continuous TX and the auto-sequencer will not run at the same time, and each says so if you try.
-
A beam heading next to the country, everywhere the country appears.
Band Activity, the Call Roster, the Tempo roster, the Needed board, Spots, the chase panes, the pounce banner, the selected-station card, the DXpedition views and the map's tooltips all print the short-path bearing from your grid straight after the entity name —
Fed. Rep. of Germany 47°— which is where every other logger puts it and where it was asked for. When the station sent a grid the heading is measured to that square. When it did not, it is measured to the middle of its DXCC entity and marked with a tilde,~47°, because the middle of a continental country is nowhere near most of the stations in it: every US callsign resolves to one point in Missouri, so a~heading is a hint about which way to turn, not a number to trust a beam to. Hover it and it says so, and says "short path", which is what all of these are. If your grid is not set in Settings, or cty.dat has no location for the country, nothing is shown at all — an honest gap rather than a confident 0° pointing due north. The roster's existing Brg column, which used to read "—" for any station heard outside a CQ, now fills in the same way and sorts on it. -
Find a setting by typing what you call it.
Settings has a search box in its header, and it searches the words on the control rather than only the headings above them — "COM port", "sound card", "PL tone", "WPM", "keps", "stop bits", "no RF" all land on the right page even though none of those phrases is a heading. Picking a result takes you there, and if the setting lives inside a collapsed Advanced group it opens the group with the control in view, so you arrive looking at the thing rather than at the heading above it.
-
Every "Settings ▸ …" pointer in the app now takes you there.
The app named a Settings path in about 228 places and none of them were clickable — including several that named tabs which no longer existed. Setup health's own "no RX audio" light said to check the audio device below and then left you to find it. Those are buttons now. The rotator's "not answering" chip, for one, now opens the rotator settings — nearly always a wrong model or port — instead of naming a location and leaving you to hunt for it.
-
Nexus can hand your log to TQSL on a timer.
Settings ▸ Confirmations ▸ LoTW gained Upload to LoTW automatically — every few hours it runs the same batch the Logbook's "Upload to LoTW" button runs, signed by your own TQSL. It is off until you turn it on, and it is deliberately not a per-QSO push like the other services: LoTW takes one signed batch and gives back one result for all of it. Two things it will not do. It refuses to run at all while Sign from ADIF location is on — that mode signs the whole batch from wherever you are now, so a timer that fired after you moved would sign last week's contacts with this week's grid, and there is no undoing that at ARRL. And if a batch is ever refused — no certificate, wrong Station Location, one bad record — it stops and says so once, rather than re-signing and re-sending the same batch every six hours forever. Save any LoTW setting to start it again.
-
You can now tune off the ham bands from the app, and receiving there works properly.
Two things were wrong once you got off-band, and both are fixed. First, you could not get there: the wheel, the scope click, the ◄/► buttons and typing a frequency all refused anything outside the band plan, some with an "outside the band plan" error and one silently — so WWV or a shortwave broadcaster could only be reached by turning the knob on the radio. They all tune anywhere now. A fast wheel flick still stops at the band edge so you cannot leave a band by accident, and it tells you where it stopped instead of calling it an error; one more scroll goes past. Second, the parts of the app that ask "is this station new *on this band*" stay quiet while there is no band to ask about, rather than treating the empty band as one nobody had ever worked. The all-time questions still answer, so an entity you have never worked anywhere is still flagged as new wherever you hear it. The Band Activity pane says "off the band plan" instead of going blank, the decode pane no longer clears itself when you tune back to the band you came from, and the frequency readout only turns TX-red when your licence actually says so, rather than whenever the dial leaves the band plan. Transmitting is deliberately unchanged. Nexus does not refuse to transmit merely because a frequency is off its band table — that table is written around the US allocations, and the table is not the law everywhere. The UK 60 m allocation starts at 5.2585 MHz, below the 5.3 the table calls the bottom of 60 m, so a blanket refusal would have blocked operators working their own legal frequencies. If you have told Nexus your US licence class it still fails closed off-band, exactly as before; if you have not, it trusts you, exactly as before. Leaving the bands still cuts a transmission that is in progress.
-
SSTV can be told a custom frequency is FM.
The USB/FM pick is now in the SSTV cockpit's band control on 10 m and up, so a local FM repeater or simplex channel you type in yourself can be worked like the built-in ones. It is deliberately not offered below 29 MHz, where the app does not command FM at all.
-
One Units setting — metric or imperial, everywhere.
Distances, temperature and wind speed now follow a single Units choice (Settings ▸ Station): automatic from your system's region, or metric/imperial by hand. It covers the spots that were still imperial — the station recall card, the roster distance column, Memories, the repeater search, and APRS weather. Every transmitted value stays native; only the display converts. From F4MQS.
-
Hide stations you've already confirmed on this band.
A new −Conf switch on Band Activity drops stations you hold an award-grade confirmation from (LoTW or card) on the current band, so you can chase what you still need — while a station that's still new on the band always shows. Asked for by F4MQS.
-
Hide callsigns by name or prefix.
A new "Hide calls" control on Band Activity takes a list of callsigns or
VP8*-style prefixes and drops them from the panes — a display filter, separate from the block list your auto-CQ honors. From F4MQS. -
A real blocklist — and your auto-responder honors it.
Alt-double-click a decode or roster row and the call goes on a persistent blocked list (it survives restarts; the same list is editable under Settings ▸ Modes ▸ Auto-CQ & Caller Selection). While you run CQ, a blocked station answering you is passed over for the next caller — with every caller blocked, the run keeps calling. Base-call matched, so blocking PD2BS also covers PD2BS/P. On screen, blocked calls render dimmed as before; a new "Hide blocked" checkbox on the roster and a −Blk switch on Band Activity remove them entirely — except the station you are actually working, which no filter ever hides. Asked for from the field ("make sure that list is referenced when auto responding to my CQs").
-
Pause the country filter without losing your ticks.
The Countries menu gains a Pause switch: turn the whole exclusion off and back on without re-ticking your list.
-
Hide any DXCC entity, not just the common 18.
The Countries menu gains an "Other country…" search over the full entity table, alongside the quick-pick list. From F4MQS.
-
The band system now reaches 24 GHz.
The band table, the frequency pickers, the override editor and the typed-dial entry all know 33 cm, 13 cm, 9 cm, 6 cm, 3 cm and 1.25 cm — ADIF's registered names, so a QO-100 contact finally logs
BAND:3cminstead of an empty field LoTW rejects. US transmit privileges follow the regulation exactly: Technician-and-above segments for 33 cm, both 13 cm segments (the 2310–2390 gap between them stays locked — it isn't amateur spectrum), 6 cm, 3 cm and 1.25 cm; 9 cm carries a band label but no US privileges (that allocation was removed), so it reads TX LOCKED for US classes and works normally for Open-class operators. Each license class's band dropdown shows only its own bands, exactly as on HF. The microwave bands also join the per-band grid tracker as the real ARRL VUCC bands they are (5 grids each at 2.3 GHz and up). A provably same-band 10 GHz satellite split is now allowed on the Main/Sub Icoms (both legs are named and equal — the old refusal said "could not confirm", and now it can); a cross-band or off-table split still refuses. Above 24.25 GHz everything still fails closed. From the QO-100 field report. -
The Yaesu FT-890 is in the rig picker by name.
It worked before only if you knew to type its Hamlib model number.
Changed
-
The connector dots tell you whether your contacts are actually getting out.
Settings ▸ Connections painted every dot from "is a password saved?", which is not the question anyone opens that panel to ask. Revoke your ClubLog app-password, rotate a QRZ Logbook key, mistype an HRDLog upload code — the secret is still in your keychain, so the dot stayed green while nothing reached the service. Each row now reports the last time Nexus really talked to that service: working with when it last got through, failing with the service's own reason, paused when ClubLog's auth kill-switch has tripped (which until now only ever appeared as one line in a log you had probably scrolled past), and stored — not verified yet in amber for a credential nothing has been sent through. That last one is the point: no news is not good news, and it no longer pretends to be. For LoTW, eQSL, QRZ Logbook and ClubLog the history comes out of your own log file, so it survives a restart — the panel has real history the moment you upgrade. HRDLog.net and Cloudlog leave no such trace, so they read "not verified yet" after each restart until your next contact goes out.
-
"Sync LoTW now" said the wrong thing and is now "Download confirmations".
It only ever pulled confirmations down; operators reasonably read "sync" as two-way and believed their contacts had gone to ARRL when they had not. The button now says which direction it goes, and points at Upload to LoTW (N) in the Logbook for the other one.
-
SSTV now respects your high-duty power cap, not your SSB one.
SSTV has no operating mode of its own — it runs as Phone — so its power ceiling came from Max power ▸ Phone, the cap you set for speech. An SSTV frame keys continuously for up to 290 seconds at close to 100% duty, which is exactly what the digital cap is for, and RTTY already used it. SSTV now takes the lower of your digital and phone caps, so it can only ever come down, never up. Worth watching your PA the first time you send a picture.
-
Japan's APRS channel wants a local check.
Nexus derives your APRS channel from your grid, and ships 144.660 for Japan while its own band-pack data says 144.640/660. If you're in JA, confirm the channel before you beacon — the picker changes it in one click.
-
SSTV has a Settings section.
It was the only mode with a cockpit and no settings, so every choice you made — transmit mode, drive — was gone by the next launch, and the one thing that did persist (the ISS pass auto-arm) was filed under Rig & CAT, where nothing else is about a satellite. Settings ▸ Digital ▸ SSTV now holds all of it: a default transmit mode, so a station that always sends Scottie 1 stops re-picking it; an SSTV transmit power that is remembered and applied at Send — leave it blank and Nexus never touches your power, which is what it has always done; and a switch for starting the receiver when the SSTV screen opens, on by default, for operators who keep SSTV up as a monitor on a shared rig. Your callsign is still burned into every transmitted picture and still has no off switch: an SSTV over carries no other identification.
-
APRS remembers your station.
The beacon symbol, comment, digipeater path and the RF channel lived in the screen and reset on every restart, so a European operator's rig was retuned to the US channel each launch and their beacon identity retyped each session. All of it now persists, under Settings ▸ Digital ▸ APRS ▸ Over the air. The channel is derived from your grid square when you have not picked one — open APRS in Europe and it lands on 144.800 with nothing configured, and fixing your grid updates it without a restart. There is also a beacon SSID control for the first time (-9 mobile, -10 iGate, -7 handheld): leave it on From my callsign and Nexus sends exactly what your callsign already spells out, which is what it has always sent. Beaconing gains the two alternate-table symbols a fixed station wants, digipeater and iGate.
-
Settings has a tab for each way you operate — Phone, CW and Digital.
The single Modes page held eleven sections, so the mode you came for sat behind every other mode's: a CW operator scrolled past the whole FT8 section and six weak-signal modes to reach their keyer. It now splits into the three the left-hand rail already shows. SSTV, APRS, RTTY, Tempo and the weak-signal modes (Q65, MSK144, JT65, FST4, WSPR) each keep their own named section under Digital. The Frequencies tab folds in there too, honestly renamed Working frequencies (FT8/FT4) — that table only ever held FT8 and FT4 rows, while its name promised every band plan you own.
-
The audio settings sit with the COM port again.
Picking the serial port and picking the sound card are the same job — on a one-cable interface they are the same cable — but they had drifted more than a thousand lines apart, with the satellite and rotator settings in between, so setting up a rig meant scrolling past hardware you may not own. Audio now renders directly under the CAT settings, the way WSJT-X and fldigi have always had it.
-
Rig Control is now "Rig & CAT", and holds only that.
It had quietly become the place everything rig-adjacent landed. Band-edge tones, the per-mode power caps, the setup backup, rig sharing and the permission for other programs to key your transmitter move to a new Transmit limits & sharing section. Nothing changed about what they do.
-
Accessibility settings moved to Appearance
, beside text size and density, instead of living under Spots & Alerts.
-
Settings uses the whole window.
It rendered in a 1100px column down the middle, so on any ordinary monitor a page that would have fitted was scrolled instead, with half the screen sitting empty beside it. Settings now fills the window and lays its sections out in columns as the room allows. Controls that gain nothing from being wider — a rig name, a dropdown, a line of explanation — are held to a readable width rather than stretched across the glass, and nothing changes at all on a small laptop screen, where the column was never the constraint.
Fixed
-
SSTV on an FM channel now transmits in FM, not USB-D.
Reported from an FTDX10 and an IC-9700: pick the 144.500 SSTV channel and the radio goes to FM, then press Send and it jumps to USB-D — an SSB signal on an FM repeater. Two separate faults did that. Sending an image asked only which sideband, so it overrode FM entirely; and Send itself re-entered the Phone section, which released the FM channel it had just been put on. An image on an FM channel is now sent in the rig's FM data submode (FM-D / PKTFM), so the sound card still reaches the modulator and the emission stays FM, and the repeater shift and PL tone stay applied through the picture. A radio that does not have FM-D is left in plain FM — never a sideband.
-
The line under the SSTV waterfall stops naming a frequency you are nowhere near.
Sitting on a 2 m repeater, it said "Images on this band appear at 145.800 FM" — the ISS downlink, most of a megahertz away. It now says that only when the calling channel is near enough to describe where you are.
-
The SSTV status line names the control you actually have to find.
It said "Audio input"; the setting is called "Input Device (RX)".
-
Test CAT now tells you when it couldn't run, instead of pointing at your settings.
Pressing Test CAT while the radio engine was down — its sound-card open failed at launch, which silently takes CAT down with it — reported "No CAT status yet — set your rig + PTT method, Save, then test", sending you to re-check settings that were fine. A test that gets no answer now says exactly what is known, including the engine's own error when it left one. A Test CAT pressed around a settings Save is no longer silently swallowed by the rebuild — it runs right after. From the QDX-on-Linux report.
-
Linux: the sound card you picked actually opens now.
Since 1.0.1 the device menu listed cards correctly, but the code that opened your pick checked it against the audio library's probe list — and the probing held each card open, so a card's
plughwentry was "busy" against its ownhwentry, your saved pick never matched, and Nexus silently fell back to the default device (the capture loop akhepcat documented; the tune tone on the PC headphones instead of the CM108 on mw0cqu's FT-847). Devices are now probed one at a time and released between probes, and picking one card for both input and output shares a single open instead of fighting itself. And when the menu saved a card'splughw:CARD=…name but the audio library only ever offers that same card ashw:CARD=…— a different access path to one physical device, which is what mw0cqu's capture showed — Nexus now matches by the card itself and opens it anyway, instead of reporting a card that is plainly there as "not available". (#2, #8) -
A DXpedition Fox's two-in-one message is recognized outside Hound mode.
A Fox packs two messages into one transmission —
KR4FQG RR73; W3DIY <YS/WE9G> -06. In ordinary FT8 that line never highlighted, even when the RR73 half was ending your QSO. It now lights up when either half is addressed to you, counts as the sign-off it is, and the row's country and worked-before read the Fox's callsign. Display only, deliberately: auto-sequencing from a Fox frame outside Hound mode is a separate question. From KR4FQG. -
A decode addressed to a hashed or portable form of your call highlights as yours.
<YS/WE9G>when you are YS/WE9G,W1ABC/Pwhen you are W1ABC — the auto-sequencer already answered these forms; now the decode row shows them as directed to you, the way WSJT-X does. From KR4FQG. -
The logbook edit form can view, correct and add a QSO's POTA park.
The park showed in the logbook's Park column but the edit dialog had no control for it, so a missed or wrong park number meant editing the ADIF by hand. Edit now carries Park (worked) and Park (mine) inputs — and an edit no longer risks dropping a QSO's other OTA/IOTA references.
-
ClubLog uploads no longer hammer, and catch up after you fix the password.
A missing ClubLog application password used to retry every two seconds about twenty times with the same error and then silently drop the contact; fixing the password retried nothing. Now a missing credential pauses ClubLog for the session with one notice, genuine failures back off, and entering the password re-queues every QSO that never uploaded. From F4MQS.
-
QSOs logged while HRD is closed are no longer lost.
The push to HRD Logbook was fire-and-forget — if HRD wasn't running, the contact vanished. Nexus now queues it and sends when HRD is reachable, with a reachable/queued indicator under the HRD setting.
-
A portable-callsign warning for QRZ.
A QRZ logbook is tied to one exact callsign, so a /P operator uploading against their base-call book has every contact rejected. Test Connection now compares the book's owner to your station callsign and warns plainly, and QRZ's terse "Unable to add QSO" errors get a plain-language explanation. From F4MQS.
-
Clicking a spot no longer sends the radio haywire.
On a rig with no data submode — an FT-950 was the report — clicking a spot asked for a mode the radio refused, and Nexus kept asking: it re-commanded the dial about fifty times a second, indefinitely. The frequency readout stopped following the VFO knob, the S-meter froze, and the radio fought you for the dial. Nexus now stops re-asking once the rig has refused a mode, and changing band no longer re-asks for a mode that was already refused. From the FT-950 report.
-
Changing the audio device no longer risks taking the app down.
Swapping the sound backend — an ordinary device change, or switching radios — could collide with the device enumeration that runs whenever Settings opens or Detect is pressed, and the collision could kill the process outright, with no error and nothing in a log. The two now take turns. This is not the startup crash reported against 1.2.0, which is still open.
Every version
- 1.24.0 11 Nov 2026
- 1.23.0 5 Nov 2026
- 1.22.0 1 Nov 2026
- 1.21.0 26 Oct 2026
- 1.20.0 22 Oct 2026
- 1.19.0 16 Oct 2026
- 1.18.0 12 Oct 2026
- 1.17.0 7 Oct 2026
- 1.16.0 3 Oct 2026
- 1.15.0 26 Sept 2026
- 1.14.0 20 Sept 2026
- 1.13.0 16 Sept 2026
- 1.12.0 14 Sept 2026
- 1.11.1 8 Sept 2026
- 1.10.3 4 Sept 2026
- 1.10.2 3 Sept 2026
- 1.10.1 1 Sept 2026
- 1.10.0 31 Aug 2026
- 1.9.2 29 Aug 2026
- 1.9.1 26 Aug 2026
- 1.9.0 25 Aug 2026
- 1.8.1 23 Aug 2026
- 1.8.0 23 Aug 2026
- 1.7.6 21 Aug 2026
- 1.7.5 20 Aug 2026
- 1.7.0 18 Aug 2026
- 1.6.1 17 Aug 2026
- 1.6.0 16 Aug 2026
- 1.5.0 16 Aug 2026
- 1.4.0 15 Aug 2026
- 1.3.0 13 Aug 2026
- 1.2.0 10 Aug 2026
- 1.1.0 10 Aug 2026
- 1.0.5 8 Aug 2026
- 1.0.2 6 Aug 2026
- 1.0.1 5 Aug 2026
- 1.0.0 4 Aug 2026
- 0.28.2 3 Aug 2026
- 0.28.0 3 Aug 2026
- 0.27.0 2 Aug 2026
- 0.25.0 1 Aug 2026
- 0.24.0 31 Jul 2026
- 0.21.5 29 Jul 2026
- 0.21.0 29 Jul 2026
- 0.20.0 28 Jul 2026
- 0.19.7 27 Jul 2026
- 0.19.6 26 Jul 2026
- 0.19.4 26 Jul 2026
- 0.18.0 25 Jul 2026
- 0.17.22 25 Jul 2026
- 0.17.21 25 Jul 2026
- 0.17.20 25 Jul 2026
- 0.17.19 25 Jul 2026
- 0.17.18 25 Jul 2026
- 0.17.17 25 Jul 2026
- 0.17.16 25 Jul 2026
- 0.17.15 25 Jul 2026
- 0.17.14 25 Jul 2026
- 0.17.13 25 Jul 2026
- 0.17.12 25 Jul 2026
- 0.17.11 25 Jul 2026
- 0.17.6 25 Jul 2026
- 0.17.5 25 Jul 2026
- 0.17.4 25 Jul 2026
- 0.17.3 25 Jul 2026
- 0.17.2 24 Jul 2026
- 0.17.1 24 Jul 2026
- 0.16.4 24 Jul 2026
- 0.16.3 24 Jul 2026
- 0.16.2 24 Jul 2026
- 0.16.1 24 Jul 2026
- 0.16.0 24 Jul 2026
- 0.15.24 24 Jul 2026
- 0.15.23 24 Jul 2026
- 0.15.22 24 Jul 2026
- 0.15.21 24 Jul 2026
- 0.15.20 24 Jul 2026
- 0.15.18 24 Jul 2026
- 0.15.17 24 Jul 2026
- 0.15.16 23 Jul 2026
- 0.15.15 23 Jul 2026
- 0.15.14 23 Jul 2026
- 0.15.1 22 Jul 2026
- 0.15.0 21 Jul 2026
- 0.14.0 21 Jul 2026
- 0.13.0 19 Jul 2026
- 0.12.0 18 Jul 2026
- 0.11.1 18 Jul 2026
- 0.11.0 18 Jul 2026
- 0.10.0 17 Jul 2026
- 0.9.7 17 Jul 2026
- 0.9.6 16 Jul 2026
- 0.9.5 16 Jul 2026
- 0.9.4 16 Jul 2026
- 0.9.3 16 Jul 2026
- 0.9.2 15 Jul 2026
- 0.9.1 15 Jul 2026
- 0.9.0 15 Jul 2026
- 0.8.9 15 Jul 2026
- 0.8.8 14 Jul 2026
- 0.8.7 14 Jul 2026
- 0.8.6 14 Jul 2026
- 0.8.5 14 Jul 2026
- 0.8.4 13 Jul 2026
- 0.8.3 13 Jul 2026
- 0.8.2 13 Jul 2026
- 0.8.1 12 Jul 2026
- 0.8.0 12 Jul 2026
- 0.7.1 12 Jul 2026
- 0.7.0 12 Jul 2026
- 0.6.0 11 Jul 2026
- 0.5.2 11 Jul 2026
- 0.5.1 10 Jul 2026
- 0.5.0 10 Jul 2026
- 0.4.1
- 0.4.0
- 0.3.0
- 0.2.0 3 Jun 2026
- 0.1.0