hamradiotools

Nexus 1.8.0

Released 23 August 2026. The current release is 1.24.0. Download it · Every version

Fixed

  • Linux: the AppImage starts on Wayland desktops again (#138).

    It was bundling its own copy of libwayland-client, which loses to a newer compositor on the host — Nexus opened to a blank white window on Fedora 44 and never drew anything. That library now comes from your system, where it belongs. Only that one is dropped; its siblings are still bundled, because nothing in the report pointed at them and removing them on a guess is how you break somebody else's desktop.

  • Nexus no longer gives up on the rigctld you chose because the machine was busy for a moment.

    Deciding whether a rigctld works meant running it once, and any failure to start it counted against the binary — including the failures that say nothing about it at all. A system briefly out of process slots, a signal landing mid-call, or the file still being held open by the installer that had just written it would all read as "this rigctld is no good", and Nexus would quietly substitute its own instead of the one you pointed it at. Those three are now retried; a rigctld that genuinely is not there or not runnable still answers straight away.

  • A station that sends you RR73 gets your 73 back.

    If DXpedition "Hound" mode had been left switched on, every ordinary contact inherited the Fox rule — the QSO ended on the other station's RR73 and Nexus sent no parting 73, then switched Enable-Tx off before it could. From your side it looked like a normal contact; from theirs you simply vanished, and they went on repeating RR73. Hound is a per-DXpedition mode now: it is off again at every launch, you turn it on for the DXpedition, and the amber HOUND badge marks the session while it is on. Working a real Fox is unchanged.

  • Hold Tx, and the waterfall's RX/TX markers, survive a settings save.

    Pressing Hold Tx or dragging a marker changed the live setting, but any later save from the Settings window posted an older copy back over it and then stored that — so the setting looked as though it had never been saved at all. None of the three is editable in Settings; they only travelled in the form, so a save could only ever undo them. Restoring a backup still sets all three from the backup.

  • The Needed board respects the New-grid band choice.

    With "New grid" set to VHF+, HF grid needs were still listed on the board. The band choice reached the roster and the decode rows when it was added, but not the board, which had stopped sharing that code path earlier so that turning the CW or Phone features off would not hide needs there. Both hold now: the board's own mode filters still show everything, and the band choice applies.

  • A contact the run gave up on can still be logged.

    If a station answered you, exchanged reports and then went quiet — a club station working several people at once does this routinely — Nexus stopped calling them after a few overs so your CQ run kept moving. That part is right. But it also threw the contact away, so when the station finally came back with RR73 the Log button said "nothing to log" about a QSO whose reports are in your own ALL.TXT. The exchange is kept now, and pressing Log writes it with the contact's own start time. Nothing is logged automatically that wasn't before — only you saw them come back, so it stays your call.

  • The Band Activity list marks each period once again, not every decode.

    Once about three hundred decodes had built up, the dim time-and-band bar that separates one T/R period from the next started appearing between every single line. It was comparing each decode against one from the far end of the buffer instead of the row above it, so the period looked different every time — which is why it began "after a while" and why switching the All/CQ filters shuffled it without fixing it.

  • A station answering your CQ makes a sound again.

    The alert for somebody calling you was being held back for the whole time you were calling CQ — the one stretch where it is the only thing you are listening for. It stays quiet once you are into the exchange, which is what it was always meant to do.

  • Nexus stops interrogating the system keyring every few seconds.

    On Fedora it could crash GNOME's keyring service over and over for as long as Nexus was open, once any online service had been set up. Nexus was asking the keyring whether each password was still there every five seconds; it now asks once and then only when you actually save or clear one.

  • OmniRig gets time to start.

    If OmniRig was not already running, Nexus gave Windows a second and a half to launch it and gave up — but a cold start takes longer than that, so the connection failed for no visible reason and then worked later. Starting another program that uses OmniRig first appeared to "fix" it, because that program had done the launching. Nexus now waits twenty seconds for a start, while keeping the short timeout for ordinary commands so a stuck server still cannot hang the radio.

  • The OmniRig "needs administrator" message points at the fix.

    It used to suggest starting OmniRig yourself, which can fail for the same reason the launch did. OmniRig does not need administrator to reach a radio, so the message now explains how to clear that flag — including where Windows hides it when the checkbox already looks clear — and treats running everything as administrator as the last resort it is.

  • Nexus starts properly on a system with no regional settings.

    On a machine running with a plain C locale the FT screen came up as an error instead of a cockpit.

  • A busy PC can no longer produce a phantom CAT failure.

    A rig reply interrupted by the operating system was being read as a dead radio, and on a longer reply it could be cut short and accepted as complete.

  • Linux: the AppImage no longer carries its own copy of a system graphics library

    , which is what left Nexus showing a blank white window on Fedora 44.

Added

  • Nexus tells you when the radio is armed to transmit at 0% power.

    A rig at zero still keys, still shows TX, and still looks like a perfectly normal over from where you are sitting — it is silent only to the station you are working, so there is nothing to notice. The status lane now says NO RF POWER while that is true, and the diagnostic log records it. Nothing is changed on your behalf: the power is not raised, not clamped, and no transmission is held back. Worth knowing on a Yaesu in particular, which keeps a separate power level for SSB, DATA, CW and AM, so a level you set in one mode does not follow the rig into another.

  • The log table shows your Comment, and marks rows carrying a private Note.

    Both fields could be typed and saved, and neither was ever shown again — the only way to read a note was to open a contact you had no way of knowing held one. The Comment now has its own column, and a contact with a private Note carries a 📝 you can hover for the full text. (The callsign recall card beside the log entry already showed both; that is unchanged.)

  • AM on the Phone screen.

    Pick AM beside AUTO/USB/LSB/FM and Nexus commands the rig to AM with a 6 kHz filter — an SSB-width filter cuts half of a double-sideband signal away and the audio comes out thin. It is offered on the bands AM is actually worked (the windows below 10 MHz, and 10 m / 6 m and up), not on 20 m where a 6 kHz signal has no room. Your power comes down automatically. A rig making 100 W PEP on SSB makes about 25 W of carrier on AM, so the same drive flat-tops the peaks. AM gets its own ceiling — a quarter by default, adjustable — and it is always the LOWER of that and your phone cap, so it can only ever reduce power, never raise it.

  • The Phone waterfall has frequencies on it.

    It showed you a signal without telling you where it was, so clicking to tune was a guess. There is a scale along the bottom now, in MHz to the kHz you would dial. It reads absolute frequency rather than an offset from your dial, because the question it answers is "where will this click put me". If Nexus does not know your dial — no CAT — it shows no numbers rather than invented ones.

  • The Needed list shows the frequency, not just the band.

    A rare one on 20 m is a different proposition from a rare one on 14.074 — the exact spot frequency is now a column, and you can sort by it to see what is worth swinging the dial for. Needs worked out from your log rather than spotted have no exact frequency, and say so with a dash instead of an empty cell.

  • Reset all settings to factory defaults.

    There was no reset at all: a clean start meant finding settings.json in a config folder and deleting it — and doing that while Nexus is running resets nothing, because the app holds the old configuration in memory and writes it straight back on the next save. The new control is in Settings → Radio → Transmit limits & sharing, beside Back up. It asks first, and the dialog says what SURVIVES: your contact log is untouched, and stored passwords stay in your keychain — clearing those stays a separate, deliberate act rather than a surprise buried in a reset.

  • An unanswered CQ run takes a breather instead of holding the frequency.

    Nexus now calls CQ eight times, waits three minutes, and calls again — both numbers are yours to change in Settings ▸ Auto-CQ, and clearing the call count restores the old behaviour of calling until you stop it. You are still listening throughout the pause: anyone who calls you is worked normally, and answering resets the count, so a run that is getting replies never pauses at all. This is a deliberate difference from WSJT-X, which repeats CQ indefinitely.

  • You can record a QSL card that arrived in the post.

    The Logbook could already note a card you had SENT, but there was no way to say one had come back — even though a paper card is one of only two confirmations that count towards DXCC, and the only one no online service can tell Nexus about. It is in the QSL menu on each row, and it can be unticked again.

  • "Hide worked" explains itself.

    It hides stations you have worked EXCEPT those that still fill a need, which is why a B4 chip can survive it — you worked that call on another band, and it is still a new slot here. The checkbox now says so.

Every version