Nexus 1.21.0
Released 26 October 2026. The current release is 1.24.0. Download it · Every version
Added
-
A Stats tab on the Contest screen.
Beside the scoreboard, Stats shows how the contest is going, live, from your contest log: contacts, on time and breaks (a break between two contacts counts as off time from the contest's own minimum: 60 minutes in CQ WW and CQ WPX, 30 in Sweepstakes, and 30 minutes, stated as a default, in a contest with no minimum on record; the scoreboard's On time and Off time and the Score Summary follow the same rule), the overall rate over your on time, your best 60 minutes, the current rate, the time since your last contact and today's contacts in UTC. A bar for each UTC hour of the contest shows contacts per hour. Distance gives your longest contact (call and country) and the average, measured from your grid to the grid the station sent where the exchange carries one, otherwise to the centre of its country. Bands and modes have bars, countries are listed with their counts (Show all for the rest) with the number of DX contacts, and grids worked are counted where the contest exchanges a grid. Your contest's own multiplier board shows what is worked and what is still needed, and the score shows its points, multipliers and total. Dupes and contacts in a banned mode are left out of the counts, as the score leaves them out. Share stats saves a picture of the stats to your Downloads folder for you to share; nothing is posted. The checklist that opens when you turn Contest mode off has See the contest stats, which opens the tab and leaves Contest mode on. The tab changes no contact and transmits nothing, and works the same from a Remote computer.
-
A contest setup that walks you through it.
Set up a contest… on the Contest screen (and Start contest… in Settings ▸ Contesting) opens a dialog in five steps: the contest, with the ones running or starting this week first and every window in UTC; what it sends, filled in from Settings, showing only the boxes that contest uses and the exact reason it cannot start yet while you type; your entry, asking only the Cabrillo lines that contest's log writes; your radio and mode, where a mode the contest does not allow (FT8 at the Illinois QSO Party) is a warning with a way to CW or Phone, never a block; and Start. Start saves once with Contest mode on, saving only the answers the setup showed for that contest, checks the station really entered the contest and says "Illinois QSO Party is on · S&P". If it did not enter, it says why and puts back everything it saved: your answers, the mode, and a contest it ended, which then runs again. Start never calls CQ. Cancel saves nothing. Starting a different contest while one runs asks you to confirm that it ends the running one; its contacts stay apart. For ARRL Field Day the power is one question, QRP, LOW or HIGH with ×5, ×2 or ×1 beside it, plus whether you run on battery or natural power for ×5, and it sets both Power category and the power multiplier. Change setup… reopens it while a contest runs. There, a new county, state, class or section goes out through I moved and takes effect on your next contact, where the contest allows a station to move; every other field you send is shown as read when the contest starts (stop the contest, then start it, to change it). "You send" is always what the station is sending, and a contest stopped elsewhere while the dialog is open shows as not running. If a contest is started or stopped elsewhere while the setup is open, Start saves nothing and goes back to the contest step, where a contest it would end asks for your confirmation again. A move that took effect is kept and said even when saving the other changes fails. When a contest on the picker starts within a week, the Contest screen and the Contests pane show one quiet line with Set up…; there is no pop-up.
-
Contest over? offers more.
The checklist that opens when Contest mode goes off can now export the Summary, lists the Cabrillo lines the sponsor requires that your log leaves out with a box for each one Settings can fill (what you type is saved just before the Cabrillo export), and shows where the sponsor takes the log, with a Copy button. Nexus never opens that address or sends the log. Nothing is ticked to begin with, as before.
-
POTA activations: today's count, dupes, two-fers, park grid and P2P.
The activation strip on the POTA/SOTA view now counts what POTA counts: the contacts from your park since 0000Z, each call, band and mode once, shown as "US-1234 7 of 10 · 3 to go" and marked valid at ten. At 0000Z the count starts again from 0 of 10, the activation keeps running and a notice says so; yesterday's contacts export as their own file. The Logbook's activation export list counts the same way, so its "under 10" agrees with the strip; the file still holds every contact. Type two or more parks to activate a two-fer ("US-1234, US-5678"): each contact is logged once carrying both, each park gets its own count, and the per-activation export writes one file per park. While you activate, the log form shows "Dupe today @ US-1234" with the earlier contact's band, mode and time when the call was already worked today on that band and mode from the same park of theirs. It only warns; the contact still logs. The "Dupe 20m" badge for a station worked on the band at any time is hidden meanwhile. Your contacts carry the park's grid from the park list as MY_GRIDSQUARE instead of your home grid, and you can type a more precise one in the strip; Settings keep your home grid, which comes back at Stop. When the park list has no grid for the park, the contacts carry none and the strip says "No park grid: type one". An activation now survives a restart or a crash: it is taken up at launch paused, with a "Still activating US-1234?" notice. Until you press Still activating (on the notice or the strip) nothing is tagged with the park, so contacts made at home after a field day that ended without Stop stay home contacts; Stop ends it. A contact waiting in the confirm-before-log popup carries the park, grid and state of the activation it was made in, whatever runs when you confirm it. While you activate, every POTA activator on the board shows a P2P badge, and the strip counts today's park-to-park contacts, park by park on a two-fer. A hunter in two parks counts once toward your ten, and once as park to park, while the per-activation export writes that contact once per park of theirs so each of their parks gets its P2P credit; your log keeps it as one contact. The same hunter again on the same band and mode from another park of theirs adds nothing to your count, and is not marked a dupe, since they need it. A hunter on a summit or a WWFF area is not counted as park to park. A park typed with the old K- prefix is accepted, with a reminder to check it before upload.
-
Contest contacts made during a POTA activation count for the activation.
A contest contact logged while an activation runs carries its park or parks, program, state and the park's grid, exactly as any other contact made then, and keeps them when it is merged into the Logbook, so it counts toward the activation's ten, shows in its contacts and export, and counts in the activator awards. They are recorded when the contact is logged, not at the merge: a contact logged while the activation is paused (taken up at launch, before Still activating) or after Stop carries none, and editing a contest contact before the merge keeps them. Your Cabrillo and the contest ADIF export are unchanged. Contest logs from earlier versions open as before.
-
POTA activator achievements in Awards.
A new POTA activator panel counts your activations from the log, by the same rule as the activation strip (ten different contacts — call, band and mode — from a park in one UTC day): valid activations, days that fell short, parks activated and the next achievement (10, 20, 30, 40, 50, 75, 100 …), Repeat Offender (activations at one park, a tier every 20), Kilo (1000 contacts from one park) and Rover (parks activated in one UTC day: Warthog 5 up to Lion 30), each as POTA defines it, with a table of your parks. Each call you activated under is counted on its own, as POTA counts each account; a portable /P counts as the plain call (KD9TAW/P is KD9TAW), while /M or any other suffix stays a call of its own. pota.app still awards from the logs you upload there.
-
Your park on the map.
With the Parks on the air layer on, the park you are activating is a filled, named diamond, and parks you have activated are outlined diamonds. The park list you downloaded now keeps each park's own position, so a park is drawn at its pin rather than its grid square.
-
Re-tag contacts with your park after the fact.
Logbook ▸ Clean up ▸ Bulk edit (below) sets or clears MY_POTA_REF; a two-fer typed as
us-1234, US-5678(or with;between the parks) is stored the way an activation stamps it (US-1234,US-5678), and the preview says which of the contacts were already sent to LoTW, eQSL, QRZ or Club Log (they keep the park they were sent with; nothing is sent again) and which are in an activation file you already exported, naming the files to export again. That warning covers any bulk edit of those contacts (a grid or power set on them too), not only a park change; a two-fer re-ordered changes no file and is not flagged. A file is remembered as exported only once it is saved. It is one change, undone with one Undo. Activation files exported before this version are not known to it. -
POTA activators: a spot comment, a re-spot prompt when you move, and QRT at Stop.
Spot me now has a comment box beside it (QRV when left blank, up to 30 characters), and the comment goes to both pota.app and the DX cluster. On a two-fer, one confirm names every park and each park is spotted on pota.app on its own, under the same one-minute repeat limit; the cluster spot names them all ("POTA US-1234 US-5678 QRV"). Re-spot and QRT work the same way. When the dial has sat at least 1 kHz (CW and digital) or 3 kHz (phone) away from where you were spotted for 20 seconds, a notice says "Moved to 14.062. Re-spot?" with one button; the button is Spot me, with the same confirm and the same one-minute repeat limit, and nothing is posted unless you press it and confirm. Once you have spotted, the checklist Stop opens offers Post QRT, unticked every time; tick it and End activation asks before spotting QRT on the frequency you were spotted on, then ends the activation. The cluster spot is kept within a node's 30-character comment column by naming the later parks of a two-fer or more as a count ("POTA US-1234 US-5678 +1 QRT"), never by cutting your comment.
-
An Activation pane, an "Activation over?" checklist and a Logbook view of the activation.
A new Activation box shows the activation running now: each park's count today in the strip's own words ("US-1234 7 of 10", "3 to go" or "valid") with its park-to-park count, how long the activation has run, how long until 0000Z starts the counts again, the rate (as the contest rate meter reads it) and this activation's contacts, newest first. Put it in any cockpit's box, the dashboard rail or Conditions like any other box, or open it in a window of its own with Activation window on the POTA/SOTA strip. It sends nothing. Stop on the strip now opens a checklist before the activation ends: each park's count, Export the ADIF files for POTA (one per park per UTC day the activation ran, exactly the files the Logbook's per-activation export writes, to Downloads), Post QRT once you have spotted, and reminders for a K- park, contacts that carried no grid, a state line with no state picked, and that you upload the files at pota.app yourself. Nothing is ticked until you tick it, Keep activating changes nothing, and a QRT still asks before it posts. When a park's contacts today were made under more than one call (KD9TAW and KD9TAW/M, say), the strip, the pane and the checklist say so with each call's count, because POTA counts each call separately; the checklist lists each call's file. If the log cannot be read for the checklist it says so instead of offering no files, and a checklist left open past 0000Z lists the new day's file. While an activation runs, the Logbook has a This activation button that shows only its contacts: its park, on each UTC day it ran, a two-fer and a run past 0000Z included; Filters ▸ Save keeps it under a name, and Filters has a new My park / summit field (your own reference, matched whole: US-1000 does not find US-10000, and a contact hunting that park is not yours).
-
{MYPARK}and{HISPARK}in CW macros, and a POTA set.{MYPARK}sends every park of the activation, separated by spaces as a two-fer is sent on CW;{HISPARK}sends the park of the station you are hunting. Each is left out when there is none. While a park activation runs and no contest does, the CW keys you have not made your own are the POTA set: F1CQ POTA DE {MYCALL} {MYCALL} K, F2! UR 5NN 5NN {MYSTATE} {MYPARK} BK, F3TU 73 {MYCALL} POTA, F6 your parks. Edit a key from the dock as usual. While you activate,{MYSTATE}sends the state your contacts carry (the park's, or the one you picked on a state line), not your home state. -
WPX and WAE chips on the Needed board, off by default.
Settings ▸ Spots & Alerts ▸ Alerts has two new switches, Show WPX prefix needs and Show WAE country needs. With one on, a station on the board that would be a new WPX prefix, or a new Worked All Europe country, on that band and mode (CW, phone or digital) gets a WPX or WAE chip, counted the way the Awards page counts them. They are off as they ship because almost every station is a new prefix. A chip changes nothing else: no sound, no pop-up, and each row's headline and order stay the same.
-
Import shows what a log file holds before anything is written.
Import ADIF in the Logbook now opens a preview: how many records and their date range, how many are new and how many are already in your log (by the log's own duplicate rule, and how many of those would gain confirmations), the problems it found with examples (no call, a date or time it cannot read, a value that is not of its field's type, an unknown band or mode), and which fields the file carries. You then choose Import, Import new only (contacts already in your log are left exactly as they are) or Cancel. Either import is still one step that Undo, or Recently deleted later, takes back. A file over 200 MB is refused with its size; split it and import the parts. A record with more than 2,000 fields, which only a damaged file has, is not imported at all, and the preview and the report say so. A file naming more than 10,000 different fields, which no real log does, is refused before its preview.
-
ADX and Cabrillo logs can be imported.
ADX (ADIF's XML form) is read with the same field mapping as an .adi file. A Cabrillo contest log is read with its contest's own exchange template (Sweepstakes, CQ WW, CQ WPX, ARRL and Winter Field Day, ARRL VHF and the QSO parties), each column going to its ADIF field (serials, sections, zones, class, RST), with each side's whole exchange also kept as STX_STRING/SRX_STRING; a contest with no template keeps the call, band, mode and time, the RST when both sides send one for the line's mode, and the exchange as text. A line is never stored under a report, a serial or your own call: a line whose other station cannot be told is listed in the preview and not imported. Whatever has no field of its own is listed in the preview.
-
A no-loss report after every import.
It accounts for every field of the file: stored, written back in the log's spelling (20M becomes 20m), kept byte for byte as another program's field, or not stored, with the reason. Save it as a text file from the import window.
-
Novice and Advanced licence classes.
Holders of the grandfathered US Novice and Advanced licences can now pick their class in the setup wizard and Settings ▸ Station, and the transmit lockout holds them to their own segments: a Novice to CW on 80, 40 and 15 m, 10 m from 28.0 to 28.5 MHz (data below 28.3, single-sideband voice above), 222–225 MHz and 1270–1295 MHz; an Advanced to everything a General has plus 3.700–3.800, 7.125–7.175, 14.175–14.225 and 21.225–21.275 MHz phone. Power limits (200 W on HF, 25 W on 222 MHz and 5 W on 23 cm for a Novice) are still yours to keep: the lockout checks frequency and mode, not power. The settings file stays readable by older versions of Nexus: they see a Novice as a Technician and an Advanced as a General, and this version still opens it as the class you picked.
-
Find and merge duplicate contacts.
Logbook ▸ Clean up ▸ Duplicates lists contacts logged more than once: the same call, band and mode within 5 minutes (the log's own duplicate window), or within an hour for possible ones. Different calls are never one contact (W1AW/KH6 and W1AW/KL7 stay apart), and neither are copies under two station calls (a portable /P aside: KD9TAW/P is KD9TAW), two operators, two grids (FN31 and FN31PR are one grid), two activations or a satellite beside a terrestrial contact. Merging keeps one copy (the fullest is suggested, and of equally full ones the one already uploaded) and gives it everything the others held, every confirmation included; its upload marks stay its own, except that a copy whose station call differs from the merged contact's or the kept copy's only by /P passes on the upload marks the merged contact lacks, whichever spelling you keep, so LoTW is never sent the contact a second time under the other spelling. A field the copies disagree on is shown for you to choose, and a confirmed copy's value, a QSL-sent mark (sent or cleared), a comment, notes or a contest exchange is never replaced without your choice. A hunter's two-fer, a summit on one copy and a park on the other, keeps both. The other copies go to Recently deleted, nothing is sent to any service, and Undo takes the whole merge back; upload marks passed on by a /P copy stay.
-
Bulk edit.
Logbook ▸ Clean up ▸ Bulk edit sets or clears your grid, station call, operator, rig, power, propagation mode, satellite, or your POTA/SOTA reference on the contacts you ticked or every contact the list shows. A preview counts what will change before you confirm. It never changes the worked call. A station call replaced with another call is the call a contact is uploaded under, so those contacts' upload marks are cleared and the next upload sends them under the new call, and their LoTW, eQSL and QRZ confirmations, matched under the old call, are cleared with their dates; paper QSL cards and award credit stay. Filling in a blank station call (with any call, whatever Settings now says), clearing one, or adding or removing /P clears no upload mark or confirmation. A contact with no station call is uploaded under the call in Settings, so a fill or a clear can change the call contacts go under to a service they have not been sent to yet: the confirm names how many, under which call instead of which (as sent, /P included), and waits until you tick that you understand. If the contacts it would send under another call are no longer the ones you ticked for (the call in Settings changed since the preview, say), the edit is refused and nothing changes. The confirm says what Undo cannot take back: anything uploaded under the new call stays on that service. The preview says how many of each before you confirm. Every other field keeps its confirmations. The edit is made on exactly the contacts the preview counted. Undo takes the whole edit back, but never puts back a blank station call that would send a contact under the call in Settings now rather than the call it was made under: that call stays, and Undo names the call in Settings the blank would have sent them under, or says Settings has no call.
-
Update from callbook.
Logbook ▸ Update from callbook (also a tab in Clean up) fills the empty fields of the contacts you ticked, or of every contact the list shows, from your callbook lookups: each call asks QRZ, then HamQTH, then callook.info for a US call, as you have them set up, the next only when the one before has no record. It fills the name, e-mail, web page, QSL route and the station's LoTW/eQSL/paper-QSL habits on any contact, and where the station is (grid, QTH, state, county, IOTA, CQ and ITU zone, latitude/longitude and UTC offset) only on contacts from the last 12 months, because a callbook says where a station is now; older contacts keep those blank, and the preview says how many. A field a contact already holds is never changed, a contest exchange's fields are never touched, and the call, country, upload marks and confirmations stay as they were; nothing is uploaded. A preview shows the contacts, the distinct calls, the services it will ask, how many calls are already in the lookup cache, the time the rest take, and per field how many contacts could be filled. It looks one call up every 2 seconds, whichever service answers, and stops at 250 lookups a day across runs (both in Settings ▸ Logbook ▸ Callbook lookups); answers from the cache cost nothing. It runs in the background with progress and Stop, and however it ends, what it found is one change that Undo takes back; run it again to pick up the rest. You can close the dialog while it runs: the Logbook tells you when it ends, with Undo. A lookup that fails, such as a QRZ sign-in turned down, stops it, and so does QRZ answering three calls in a row with no record, which is how QRZ refuses lookups. While the radio transmits, a large update waits to change the contacts until the transmission ends. It follows QRZ's published XML rules: one sign-in per session, Nexus names itself on every request, and QRZ's own messages are shown. If QRZ refuses service for the account, the update stops and Nexus does not ask QRZ again for 24 hours, in any lookup. On an account without the QRZ XML subscription the update leaves QRZ out and uses HamQTH and callook.info. HamQTH is credited in Settings and in the preview, and callook.info's few minutes offline each day leave those calls for the next run instead of stopping it. Calls the callbook does not know are listed and left alone. From a Remote computer you can preview it; the update itself is started at the station.
-
Check the log.
Logbook ▸ Clean up ▸ Check lists invalid grids, a DXCC entity the call's prefix does not match, a missing band or one its frequency is not in, an end time before the start or a date in the future, and POTA, SOTA or IOTA references not in their format, each with a proposed fix. A confirmed contact's DXCC or band, a grid list and an end time that is not a midnight wrap are listed without one, and so is a DXCC entity the call's prefix cannot settle (K1ABC logged as Hawaii, 3Y0PI logged as Peter I). Only the fixes you tick are made, as one change Undo takes back.
-
Contest entry: the country of the call, ten last contacts, and Edit on each of them.
While you type a call in a contest, the line above the Call box shows its country as the contest counts it, with the CQ zone its prefix usually has in a contest whose exchange is a CQ zone (for example "Fed. Rep. of Germany · CQ 14", and "Sicily · CQ 15" for IT9 in CQ WW, which counts Sicily as a country of its own); a DUPE warning on that line comes first. Nothing is filled in for you: the zone box still only shows the zone as a hint, because a portable station sends its own. The Last contacts list under the entry now shows the ten newest contacts instead of five, and each has an Edit button that corrects it in place, the same edit as the full log's (Enter saves, Esc leaves it as it was, and the caret goes back to Call), with the dupe marks and the score following. Contacts logged while an edit is open do not close it. As on the full log, an edit is refused at a club and through Remote, and if the contest was already merged into your logbook you are told to fix the logbook copy too, on a line under the list that stays in view until the next edit or contact. Only one edit of a contact is open at a time: Edit or Ctrl+Y while another is open takes you back to it. If the same contact is edited (its call included) or removed in another window (the contest logger window and the Contest screen) while your edit is open, your edit closes and says which, and a save pressed before that change reaches your window is refused, so an older edit never writes its values back over the newer one.
-
Logbook filters, saved filters and sorting on up to three columns.
The new Filters button beside the search box filters the whole log by call (prefix or
*/?pattern), band, mode, dates, DXCC entity, continent, CQ and ITU zone, grid, state, county, IOTA, park or summit reference, contest, words in the comment, name or QTH, QSL state per service (LoTW, eQSL, card, QRZ: confirmed, sent, not sent; Club Log: sent, not sent) and award need (contacts whose DXCC, WAS, WAZ, VUCC or FFMA band slot is worked but not yet confirmed). Save a filter under a name, recall, rename or delete it. Shift-click a column header to sort by it next; grid, state, IOTA, county and contest now sort too. -
Callbook answers are kept on this computer.
A call you looked up is answered from a local cache for 30 days (Settings ▸ Logging & Connectors ▸ Confirmations ▸ Callbook cache, adjustable), and offline at any age; refresh one call or clear the whole cache there. No password or sign-in key is ever kept. US calls that QRZ and HamQTH do not answer are also asked of the free callook.info.
-
Station card.
Click a call (or press Enter on it) in the Logbook, Spots, the decode list's QRZ link, the roster's ↗ and the station cards' QRZ, the map's path line or the log strip's new Card button, and one card shows what Nexus knows about it: distance and bearing, the contacts you have made as a band × mode grid of worked and confirmed, the last one, what it would be new for on the band and mode you are on, its latest spot, and what your log recorded about it, with Lookup for the callbook (name, QTH, county, IOTA, zones, e-mail, web, QSL route, LoTW/eQSL/card, their local time and photo) and a QRZ button for the page. Opening it asks nothing over the internet. Esc or a click elsewhere closes it, and it never covers the TX strip, Stop TX or the TX dock. Settings ▸ Appearance can also open it when the pointer rests on a call (off by default).
-
More from the callbook on every contact.
When you have looked a station up (the callsign card or the log strip), the contact you log with that call keeps what the lookup said: county, IOTA, CQ and ITU zones, position, e-mail, web page, QSL manager, whether they use LoTW, eQSL or paper cards, and their UTC offset, plus name, QTH, grid and state when you left them empty. This works for every way a contact is logged, the FT auto-log too, which uses the answer already on screen and never waits for a lookup. Nothing you typed is replaced. Where the station is (grid, county, zones and so on) is taken only from their own callbook entry, not a home call's entry for a /P or a station at a park. A zone or location from the callbook gives way to LoTW's when LoTW confirms the contact.
-
LoTW sync keeps the QSL details.
A LoTW confirmation now also fills the station's grid, county, IOTA, ITU zone and prefix when the contact had none.
-
Logbook columns.
A Columns button replaces "More columns": show or hide each column, drag a column's edge to resize it, and the choice is kept in your settings. New columns show what the log already stored: their grid, IOTA, county, CQ and ITU zones, continent, distance, the QSL sent and received dates, each service's upload state and the contest exchange; IOTA can now be edited, and the contact view shows these too.
-
More awards: WPX, WAE, WWFF and Worked All Provinces.
The Awards page now counts CQ WPX prefixes, DARC's Worked All Europe countries with their band points and class, WWFF references worked with the hunter levels, and the Canadian provinces it already counted but never showed.
-
Custom awards.
Define your own award from a list of calls, prefixes, grids, references or ADIF field values, with band and mode filters, and export or import the definitions as a file.
-
A whole-log DXCC chart.
Every DXCC entity against every band, shaded confirmed, worked or needed, with a mode filter.
-
What to QSL.
A list of the unconfirmed contacts whose confirmation would fill a slot an award still needs, most valuable first, with the QSL route where the log holds one.
-
The Fred Fish Memorial Award (FFMA) on the Awards page.
A new card counts the 488 grid squares of the 48 contiguous states worked and confirmed on 6 m, with the squares still needed listed beside the other chases, and a needed 6 m square on the Needed board now says FFMA.
-
70 cm, 33 cm and 23 cm are full bands for openings, need alerts and awards.
A grid, zone or state worked on one of them no longer shows as new there, tropo openings on them are detected (moonbounce is not), 33 cm gets a weak-signal channel and a CW calling dial, and the 70 cm and 23 cm CW dials move to the ARRL calling frequencies, out of the moonbounce segments.
-
One Devices list at the shack.
Settings ▸ Remote access lists every computer, phone and browser that can reach the station once, under you or the person you invited, with how it connects, where it stands, and Approve, Allow to transmit and Remove on the row. It replaces the separate lists of browsers, computers, paired computers and people.
-
One Connect to my station… entry on the computer you operate from.
It replaces Remote stations… and Stations on this network… in Settings ▸ Remote access: Nexus looks for your station on this network first and connects, opens the code pairing if this computer is not paired yet, or offers to sign in and reach it over the internet; the station list, a typed address and the code stay under Advanced.
-
Every contact keeps its history, and every change can be undone.
The contact view now ends with a History section: each change to the contact, when it was made, what it changed (old → new) and who made it — you, an import, a LoTW, eQSL or QRZ download, the automatic fill, the contest log, a Remote computer. Each change has Undo, which puts back the fields it changed that have not changed since; an undo is itself a change, so it can be redone. Recently deleted in the Logbook lists deleted contacts with Restore, which brings one back exactly as it was. After a delete, an import or a purge, the message offers Undo, and a whole import or purge is undone in one step — that import or purge, and never a contact logged after it. An undo never puts a contact back beside the same contact logged again after it was deleted (the same station, band and mode within 5 minutes), and Restore anyway puts it back when they are two different contacts; a contact the log held beside it before the delete, such as a rover worked from two grids minutes apart, never stops it coming back. An import's undo keeps any contact you have edited, that has been confirmed or uploaded, or that you imported again, since; the message names them. A whole undo does not name a contact you already undid on its own as one it could not undo. Undoing more than a few hundred contacts at once waits until you stop transmitting, or a voice message or APRS frame finishes, because it holds up the radio while it is made; the message then stays up and says so, and its Undo works once you stop. Recently deleted also lists each recent purge and import with Undo this purge or Undo this import, so a whole one can still be undone after its message has gone, and each recent whole undo with Redo. Each asks first, naming how many contacts, from when, and whether they leave the log or come back to it. Undoing a whole purge, import or undo is done only at the station: a computer driving it through Remote sees the list but cannot press it. The history is kept in the logbook database, so it survives a restart. Undoing a change to a contact merged from a contest, or putting back a deleted one, keeps what its exchange carried (the zone, county, state or grid the other station sent) in the contest's own columns, and the history shows a change to one of them as, for example,
STATE (contest). Every edit is kept for good; a deleted or purged contact's full copy is kept for 90 days, which Keep deleted contacts for (days) under Settings › Config › Data & log folder changes. An undo never sends anything to QRZ, Club Log, eQSL or LoTW; an undo that changes a callsign marks the contact to be sent again with your next upload, as correcting a callsign does. -
JTTY sends from a remote computer.
Driving a station from another computer, JTTY's Send, F-keys, live typing and sign-off now transmit, under the same guards and Stop as the other remote modes.
-
Allow to transmit, at the shack.
A device added by signing in is held from transmitting until you let it. Settings ▸ Remote access now shows such a device, browser or computer, once it has station control, as "Waiting for you to allow it to transmit" with an Allow to transmit button beside it; one press lifts the hold. A device still waiting for Approve is offered Approve instead, which lifts the hold as well. The button works only on the station's own screen: a remote computer or browser can never press it, so a held device cannot allow itself. Stop is never held.
-
The shack asks when a signed-in device is waiting to transmit.
Nexus at the shack pops up "Allow Laptop to transmit?" with the device's key, and Allow to transmit or Not now. Not now leaves it listening and tuning only, and the button stays in Settings ▸ Remote access. The held computer now says the same: listening and tuning only, until Allow to transmit is pressed at the shack.
-
A held remote computer sees its hold in every mode
, with "or about N min" when the station would lift it by itself; a voice message cut short by leaving Phone is now announced.
-
Approvals given at the shack last across a station restart.
A browser added by signing in that you let transmit (with Approve or Allow to transmit) stays allowed after Nexus or the station restarts, once the station has heard the device list again, and so do your own computers and phones once the station has sent you the new-device notice. A guest's computer or phone is held again after a restart until you press Allow to transmit again. Revoking its station control, removing it, the device expiring or no longer being listed, cancelling, or revoking station access ends that approval for good, and the device is held again until you allow it. Turning Remote off only pauses it, as it pauses the device's other grants. Devices on your own network are unaffected.
-
Spot a station from anywhere — now on the phone cockpit and on every Spots row.
The one-click Spot button, which opens the review popup that posts a DX-cluster spot from your station's login, used to live only on the Operate and DXpedition screens. It now also sits on the phone/SSB cockpit's toolbar (seeded with the call you are logging) and on each row of the Spots board (seeded with that spot's call and frequency). The confirm popup is unchanged — every spot is still reviewed before it goes out.
-
A "show all spots" step on the Needed board while a contest is running.
The Needed board shows only stations you still need, which during a contest — when you want to work everyone, not just new ones — can leave the phone board looking empty. While a contest is running the board now shows a short bar with one click to the full, un-gated Spots view (filter to Phone there for SSB). Outside a contest nothing changes.
-
An SDRplay receiver as the scope's source, through SDRconnect (needs a bench check).
Settings ▸ Radio has a new Scope source section: The radio (as before, and as it comes) or SDRconnect (SDRplay). With an SDRplay RSP fed from the rig's RX OUT (or a splitter with transmit protection) and SDRplay's own SDRconnect program running with its WebSocket API on, the RF scope pane and the Phone and CW scopes draw the receiver's whole span, each station at its own frequency, with the dial, the passband and spots on it as usual. The receiver's centre follows the rig's dial, on every change or only when the dial nears the edge of the span. Nexus only reads the receiver's IQ and sets its centre frequency: it never transmits through SDRconnect and sends it no CAT. SDRconnect is a separate, free, closed-source program from SDRplay that you install; Nexus ships and loads nothing of SDRplay's. When SDRconnect is not running, sends no IQ, or sends IQ at a rate other than the one it reports, the scope's status line says which and Nexus keeps trying. Built and tested against the published SDRconnect WebSocket API 1.0.3 only: it has not yet been run with a real RSP and SDRconnect, so treat it as untested on real hardware until a bench check confirms the IQ rate, where a carrier is drawn, retuning while the knob turns, and whether RX OUT stays quiet while you transmit.
-
JTTY, WSJT-X's new keyboard mode, to receive and to send (needs a bench check on the air).
A JTTY screen sits under Digital, beside PSK. It has WSJT-X's eleven JTTY frequencies (20 m at 14.090), its Rx, Tx and F Tol boxes, its All decodes and QSO frequency panes, and a waterfall with Rx and Tx cursors. Nexus decodes JTTY as WSJT-X does, and sends what WSJT-X sends: text you type and Send; WSJT-X's F1–F8 contest messages, with a Call box and a serial number; and Live, which keeps the transmitter up while you type and sends your words as you go. Every send needs TX On and your license class across the whole signal, and the TX watchdog runs for JTTY, though WSJT-X's does not. Stop TX, Esc and the dock's Esc/Stop cut it at once, and leaving the JTTY screen stops it. A JTTY session stops 10 minutes after it starts, the text still going out after Send, the sign-off or live typing included, at the station and from afar. Opening JTTY turns TX on as opening PSK does, but not after a Stop. A call becomes clickable, is spotted to PSK Reporter and reaches the Needed board only once it has been decoded in two separate messages. JTTY comes from the WSJT-X 3.3.0-beta4 test release and no WSJT-X general release has it yet, so the other station needs a WSJT-X 3.2 or 3.3 test release. Not yet tried on the air: a bench check should confirm keying, power and ALC at your data power, and that a WSJT-X station copies what Nexus sends.
-
JTTY contacts log as JTTY, and export as
MODE=MFSK SUBMODE=JTTY, as ADIF 3.1.8 registers it.A log with a bare
MODE=JTTYstill reads as JTTY. LoTW does not list the JTTY mode yet and TQSL would drop such a contact, so a LoTW upload holds JTTY contacts back, leaves them marked not uploaded, and says so. The WSJT-X UDP Status names the mode JTTY, and no Decode messages go out for it, as from WSJT-X. -
JTTY in contests.
In ARRL Field Day, F2, F6 and F8 send your class and section in JTTY's compact exchange form, and %E in typed text is your class and section, as in WSJT-X. Winter Field Day allows JTTY for 2027; its classes do not fit that form, so a Winter Field Day exchange goes as typed text, which a WSJT-X station reads the same way.
-
Log space weather on each contact (off by default).
Settings ▸ Logging & Connectors ▸ Integrations & Feeds ▸ Propagation has a new switch. On, every contact you log carries the planetary K index, A index and solar flux (ADIF K_INDEX, A_INDEX, SFI) from the latest reading Nexus fetched, and nothing when that reading is more than 3 hours old.
-
Each contact logs the worked station's continent and the distance to it
(ADIF CONT, and DISTANCE in km from your grid to theirs when both are known).
-
Disable a second radio without deleting it.
With two or more radios, each card in Settings ▸ Radio has a Disable button. A disabled radio keeps its whole setup, but Nexus stops watching it and lets go of its CAT port, so another program on the same computer can use that rig. Auto band-routing skips it. Enable brings it back. The radio you are operating can't be disabled: make another radio active first.
-
A disabled radio leaves the radio switcher.
Its pill is gone from the header's radio switcher, and its Make active button in Settings ▸ Radio is greyed out until you enable it, so a click can't open its port again. Enable it and the pill comes back. With only one radio left enabled, the switcher hides as it does for a one-radio station. A computer driving the station through Remote cannot make a disabled radio active either.
-
The Call Roster's Hide worked can reach back a set time.
Beside Hide worked on the FT8/FT4 Call Roster is the same window picker the Spots panel has: Any time (the default, and what Hide worked did before), Until 0000Z, 1 h, 4 h, 24 h or 7 days. A station you last worked before the window shows again, which suits special-event calls such as 13 Colonies and Route 66 that are on the air all week. Nexus remembers the choice.
-
Callsigns on the FT8/FT4 waterfall.
Each station decoded in the last period is labelled along the top of the waterfall, over its own audio frequency, and the station in the DX Call box is shown in red. When the labels crowd, they stack in up to three rows, a station calling you and then the strongest first, and a count says how many had no room. Clicking a label moves your RX offset there, as clicking the waterfall does. The Calls button in the waterfall's header turns the labels off.
-
A Comment box in the Log this QSO? pop-up.
With logging set to ask first, the pop-up that shows a finished FT contact now has a Comment box under the call, grid and reports. What you type there is logged as the contact's comment (ADIF COMMENT), so a note no longer means editing the contact on QRZ afterwards. The box opens with the comment the contact already has, such as the dB reports when you log those to comments; leave it alone and that is logged as before.
-
Choose how long the pop-ups in the bottom-right corner stay.
Settings ▸ Spots & Alerts ▸ Alerts has a new Keep pop-ups up for at least menu: each pop-up's own time (as before, and as it comes), 10, 20, 30 or 60 seconds. It only makes a pop-up stay longer: an error still stays at least 12 seconds, and one that stays until you close it still does.
-
−B4 can hide only the stations you have worked on this band.
A small menu beside Band Activity's −B4 chip picks what it hides: Any band (every station worked before, as −B4 always did, and still the default) or This band, which keeps a station you have worked only on another band on screen so you can work it for a new band. The Rx Frequency pane follows the same choice, and with This band chosen, hovering over its −B4 says it hides only stations worked on this band, and where to change that.
-
Tempo can come off the left-hand menu.
Settings ▸ Appearance ▸ Features now has a switch for Tempo (the TempoFast/TempoDeep chat) under Operate, like the ones for RTTY, SSTV and the other modes. It is on, as before, unless you turn it off; off, Tempo leaves the menu, and if Nexus was last in Tempo it starts in FT8/FT4 instead.
-
Nexus Remote: download your data or delete your account from the Remote page.
The Your account card has Download my data, and Delete account, which deletes only after you type DELETE. A paid plan is cancelled first, and nothing is deleted if it cannot be. Your stations, devices and invitations go; the sign-in record is removed on request.
-
Your own signed-in devices pair with your station automatically, over your network and over the internet.
When you sign a computer, phone or browser in to your Nexus Remote account, it is granted control of your station without a trip to the shack to approve it — on your home network and across the internet alike. Code pairing and approving a device at the radio still work exactly as before. For safety, a device added this way cannot transmit for its first 15 minutes: it can listen and take control at once, but transmitting waits out the hold (Stop is never held). A device that joins on your own network is never held, and approving a device at the shack lifts its hold at once. A device signed in over the internet can also transmit once its 15 minutes pass — but only after the email telling you it was added has actually been sent to your account; until then it stays held, so approve it at the shack to let it transmit. That email names the device, the station and when, and how to remove it if it was not you. Restarting Nexus does not start a device's hold over: once the service has confirmed that email, the station remembers it, and after a restart the device is held only for what was left of its 15 minutes, once your account's device list confirms it again.
Changed
-
Settings ▸ Contesting: Start contest… and Stop contest… instead of the Contest mode switch.
Start opens the contest setup and Stop opens the end-of-contest checklist, both at once, without Save. Settings can no longer save Contest mode on with an exchange the station cannot start with. With a contest running, a Save that switches to a contest the station cannot enter yet is refused, with the reason, and so is one when the station cannot be asked. Start and Stop follow the station, so a contest started or stopped on the Contest screen since Settings opened shows as it is, and a Save made after another radio was picked elsewhere keeps Contest mode and the picked contest as the station holds them, unless you changed the pick on the form. Field Day saved on with a blank class or section shows Waiting for Class + Section, not Off. Every other field on the tab is unchanged.
-
The Contest screen says what Running does.
Its Running button now says that on an FT mode it turns TX on and calls CQ, and the screen's note no longer claims the screen never transmits. What the button does is unchanged.
-
The Tempo 23 cm channel moved from 1296.200 to 1296.185 MHz
, below the 1296.200–1296.400 beacon segment and inside the weak-signal segment of the ARRL band plan. Older Nexus builds still call on 1296.200 and will not hear this one; tune there by hand to reach them.
-
In a contest, FT8 and FT4 Search & Pounce no longer calls stations by itself.
S&P now only listens, as in WSJT-X: you start each contact with a double-click on a CQ, or a reply to one from a logging program. That contact still runs itself to RR73 and the log, and S&P then waits for your next pick. Leaving TX on never calls anyone, and nothing is queued while TX is off. With Disable TX after sending 73 on, TX now goes off after every S&P contact. In ARRL Field Day and Winter Field Day on FT8, FT4, FT2, FT1 and DX1, a double-click on a CQ while you are in the contest's S&P answers it with your class and section and logs it in the contest. On FST4, Q65, MSK144 and JT65, and in other contests on FT2, FT1 and DX1, a double-click works the station as a normal QSO, as before.
-
In a contest, FT8 and FT4 Running stops after each contact.
Once a contact is logged and your last over (the 73, or the RR73) has gone out, TX goes off and Nexus stops calling CQ, as WSJT-X does with Auto Seq on. While TX is off the run takes no caller, as WSJT-X does with Enable Tx off: a station that answers your earlier CQ is not answered and nothing is logged. Press Call CQ, the Contest screen's Running or TX On to call CQ again, in the same period as before; each sends the CQ. A station that answers your CQ while you are calling it is worked as before, and the contact still runs itself to the log. The AUTO-CQ sign on the FT cockpit goes out while the run is stopped. The Contest screen's Running stops the same way on FT2, FT1 and DX1. Outside a contest, Call CQ still goes back to CQ after each contact.
-
Nexus Remote is free during the beta, with no 14-day limit.
Where the service runs the beta, the Remote page says "Free during the beta" instead of counting a trial's days, internet use no longer runs out, and attaching a station no longer promises a trial. Everything else about who may use Remote is unchanged.
-
The Nexus Remote page explains itself before you sign in.
Signed out, it shows how to get started, what works and what does not yet, who can transmit and how Stop works, and where to send a report ([email protected], with
nexus-diag.log). It says Remote is free during the beta. Signed in with no station yet, it lists the three steps at the shack. Its messages that named Settings ▸ Station ▸ Remote access now name Settings ▸ Remote, where the card lives. -
The phone scope starts snappier.
The phone panadapter and waterfall now default to the Fast analysis window (85 ms, was 171 ms), so a signal appearing or a fading one dropping shows about twice as fast. Voice is wide enough that the slightly coarser frequency resolution is not visible; if you want the finer Balanced or Sharp window back, the scope's window button still sets it, and your choice is remembered. The passband trace also settles and falls back faster on phone — its averaging default drops from 250 to 100 ms and its peak-hold from 250 to 150 ms — so the trace tracks the band more like a live SDR panadapter instead of lagging behind it. Separately, the rig scope and the radio's RF panadapter pane now refresh about 30 times a second instead of 20 (the window, averaging and peak-hold changes above are the phone scope's alone; CW, the digital waterfalls and the RF panadapter keep their own trace settings). The faster refresh pairs with the FlexRadio change below.
-
A FlexRadio panadapter updates twice as often (needs a bench check on a real Flex).
Nexus now asks a FlexRadio to stream its panadapter at 30 frames a second instead of 15, so the scope and waterfall from a Flex move about twice as live, closer to SmartSDR's own feel. It roughly doubles the data the radio sends over the network (still modest). Not yet run against a real Flex: a bench check should confirm the higher rate does not disturb a second radio sharing the connection before this is relied on.
-
The station decides every decode alert, so every screen hears the same ones.
Someone calling you, a new DXCC entity or grid (a rare grid loudly), a watch-list station, an opted-in CQ and a park newly on the air are now decided once, at the station, from your alert settings, your watch list (its CQ-only, minimum SNR and label with it) and your area filter. The desktop and a computer driving the station both show what it raises, with the same sounds, pop-ups and Work button as before. The new-park beep no longer needs the main window to be polling.
-
FT8: the full decode starts from the audio the early decode has already cleared, as in WSJT-X, and still finds every station the old way found (needs a check on the air).
At 13.5 seconds into the period Nexus now takes the stations the early decode found at 11.8 seconds out of the audio, as WSJT-X does, and the full decode at 14.4 seconds searches what is left. It no longer finds those stations again first: what they hid comes out in its first search, and only new decodes reach the decode list and the QSO sequencer. On a busy band this is what puts a weak reply on your frequency in the decision for your next over: with 80 stations in the period it arrives about 14.6 seconds into the period instead of 15.1, after your over had started. Taking the stations out can damage a few weak ones right beside them, which WSJT-X then misses; Nexus searches the original audio once more after the full decode and adds only the stations the period has not shown yet, so on busy test recordings it finds about 3 % more stations than before and none fewer. That second search runs after the first, so the decoder is busy about twice as long after 14.4 seconds, and the few stations only it finds show up about a second later than they used to; on a computer too slow for it, it stops in time for the next period's decoding. FT4 has no early decode, in WSJT-X or in Nexus, and is unchanged.
-
The log-entry boxes no longer show made-up example values.
An empty box in the contest log line and in the Logbook's add-a-contact form used to show a sample in grey, such as W1AW in Call, 1D and WI in Field Day's Class and Section, a county in a QSO party's county box, and FN31, 20m and a park reference in the Logbook form. A sample like that could read as a value already filled in. Those boxes are now blank. Hints that are words or formats stay, such as Call, Name, RST, MHz and the UTC date format. The park box now reads "Park (reference or name)", and the CQ WW zone box still shows the zone the country file gives for the call typed.
-
No other screen shows made-up example values in an empty box either.
Settings (Station's callsign, grid, name and state, the Field Day class and section, Your station data, the club event boxes, the port and address boxes, Blocked callsigns, Station power), the setup wizard, the POTA/SOTA activation box, Repeaters' place box, APRS's watched calls, the hide-calls filter, the watch list and the spot comment no longer show a sample such as KD9TAW, WI, 1D, K-1234, COM16 or 192.168.1.50. Words that say what goes in a box stay ("Select or type", "empty = off", "host:port"), and so does a box's real default, such as the rigctld port 4534 or the APRS-IS server.
-
FT8/FT4: the test of what Nexus refuses to send names the refused messages.
The build's test that compares every FT8 and FT4 over against WSJT-X's own encoder took the list of messages Nexus refuses to send from the very check it was there to test, so that check refusing a message Nexus should send would still have passed. The test now names the refused messages, and such a mistake fails the build. Nothing you see on the air or on screen changes.
-
Remote has its own Settings tab.
The sign-in, pairing and device-approval card that used to sit at the bottom of the Station tab now lives on a dedicated Remote tab, next to Station, so it is easier to find. Nothing on the card changed, and every switch keeps its setting; the Icom-network and rig-sharing settings on the Radio tab, and the "Conditions on a TV" setting on the Appearance tab, stay where they are.
-
Signing a station in to Remote no longer starts with a dead button.
The station-name box on the Remote card fills in with your callsign on arrival, so Sign in and Pair a station work straight away (you can still change the name). If you have not set a callsign yet, a short line beside the box says to type a name.
Removed
-
Nexus Remote: the old Remote page's FT8/FT4 transmit permission.
The page that used it is gone, so the station no longer takes FT8/FT4 or held-contact commands from a browser, and Settings ▸ Remote access no longer offers Also allow FT8/FT4 transmit from the Remote page or the switch to allow or revoke it. A browser streaming the station is unchanged: it operates Nexus as you would at the shack, transmit included, and its Stop TX works as before. A browser you approved with that permission keeps its station controls after you update; only the old permission is dropped.
-
Nexus Remote: the remote logging permission.
It was for the old Remote page's Log QSO form, which is gone; all it still did was let a browser take control without station controls. Settings ▸ Remote access no longer shows Allow remote logging or Revoke logging permission, approving a browser gives it station controls only, and a browser now needs station controls to take control. End remote control works as before. A browser streaming the station logs with Nexus's own log form, as you would at the shack. A browser that had only remote logging left after an update has nothing; approve it again or allow its station controls to give it control.
Fixed
-
Contest DX multipliers: Sicily is Italy, except in CQ WW.
The Tennessee, Texas and Illinois QSO Parties counted a WAE area (Sicily, African Italy, Shetland, Bear Island, European Turkey, the Vienna International Centre) as a DX multiplier separate from its DXCC country, so working IT9 and I claimed two where those contests count one. They now count DXCC countries only, and the contest entry names the country the same way (IT9 shows Italy). CQ WW, whose rules count the WAE areas as countries, still counts Sicily and Italy as two and shows IT9 as Sicily. Logs with no WAE-area contact score as before.
-
Technician and Novice: only CW and single-sideband voice on 28.3–28.5 MHz.
The transmit lockout let a Technician send AM, FM and SSTV pictures there, which 47 CFR 97.307(f)(10) does not allow. They are now refused for a Technician and a Novice, and the refusal says why. Nexus cannot hear what another program sends, so there it no longer lets other programs key the radio through the CAT broker or TCI, whatever the radio's mode; the connection log says why. Nexus's own PTT, voice keyer and CW still key there. General, Advanced and Extra are unchanged.
-
Typing in the middle of a call no longer jumps the cursor to the end.
Type the suffix first, go back to the start and type the prefix, and the cursor now stays after each letter you type, as in any text box: "abc", Home, "dl1" gives DL1ABC. This holds in the contest entry (the Contest screen, the cockpit strip and the logger window), the log entry, the contact editor and every other box that capitalises as you type.
-
Merging a contest into the logbook keeps the grid the other station sent.
In the ARRL VHF contests the grid in the exchange went into the exported file but not the logbook's own Grid column, so those contacts were missing from the Grid column, grid searches and anything that counts grids until the log was imported again. A name and a QTH sent in an exchange now land in the Name and QTH columns the same way. Contacts merged before this get theirs once, on the first start of this version, wherever their own Grid, Name or QTH is empty; one you filled in yourself is never touched. Their uploads carry the same grid, name and QTH as before. The copy is one change: Recently deleted in the Logbook lists it for as long as Settings keeps deleted contacts (90 days unless you changed it), and one Undo there blanks every field it filled again, while the contest exchange keeps the values; after that, each contact's own history still undoes its copy.
-
WAZ counts the zone a CQ WW contact sent.
A contest merged into the logbook kept the CQ zone the other station sent only with the contest's columns, and the awards counted the zone of its callsign's country instead: a W1 station operating from California sends zone 3 and was credited zone 5. The same contacts now count for a custom award on the county, section or class their exchange carried, a LoTW download no longer adds a second, different grid, zone or county beside the ones they sent, and a contact that already got one that way uploads only the one the station sent. With Sign from ADIF location on, a LoTW upload of a merged VHF contest contact signs the grid you sent in the exchange (a rover's grid at that moment) rather than adding the grid in Settings beside it; with a named TQSL Station Location, nothing about the signing changes.
-
A merged contest contact's state is the one its exchange carried, everywhere.
Its uploads already carried the state the other station sent; WAS, the WAS needs, the statistics, the Logbook's State column, its sort and filter and the edit form now show and count that state too, where they used the state looked up from the callsign. Editing State in the Logbook replaces the exchange's state, so the upload, WAS and custom awards all follow the edit.
-
Other programs can no longer transmit past a band or segment edge from a dial just inside it.
Nexus cannot tell where in the sideband another program puts its audio, so a key from the CAT broker or TCI is now allowed only when everything from the dial to 3 kHz above it (below it on LSB) is inside your license privileges for the mode. With the dial at 14.149 MHz, a data program at its usual 1500 Hz sent at 14.1505 MHz, past a General's 14.150 MHz data limit. A key already held drops if you retune that close to an edge, and stays off until the program keys again; the connection log says how far the program's audio could reach. If the radio reports a different sideband than Nexus set (DATA-L after a front-panel change), that side is checked too; AM is checked on both sides of the dial and FM as Nexus checks its own FM, so a General at 14.026 MHz whose radio was switched to AM is refused. A retune from Nexus keeps the radio's last reported mode for this check until the radio is read again. The mode is read between overs, so a change at the radio during an over counts from the next one. In a CW-only segment, such as 50.0-50.1 MHz, other programs can key only while the radio is in CW. In Phone and CW the check is the one Nexus applies to its own voice and CW, and Nexus's own transmissions are judged as before. On 60 m, a key from a channel's USB dial (5.3305, 5.3465, 5.3715 or 5.4035 MHz, within 50 Hz) is judged at the channel as before, since a channel is narrower than 3 kHz, and only while the radio reports upper sideband (USB or its DATA form) or nothing; anywhere else on a channel, and in the 60 m segment, the whole passband is checked.
-
With Follow the radio's split on, a long over on a split set at the radio runs to its end.
Nexus cannot read the radio's split while it transmits, and the last reading counted as too old after 6 seconds, so an FT8 over or a phone over was cut off part way. The reading now holds until the over ends, for up to 2 minutes, and is read again right after; this covers another program's over through Nexus too. A reading already too old when you key is still refused, and a key held past 2 minutes on a split set at the radio is refused as before.
-
Driving the shack from another computer, Skip Tx1 shows and sets the shack's own setting
, as at the shack; a refused change is shown.
-
Nothing else can key the radio while a voice-keyer message is playing.
A Remote microphone press or a program on TCI could start transmitting over a message still going out. Both are now refused until the message ends, and Stop still ends it at once. A TCI program that sends a transmit-off while a message plays now stops the message, as it already stops FT, CW, RTTY and Tune.
-
Remove at the shack now removes a computer everywhere.
Remove on the Devices list ends both its internet access and its place on your network, when Nexus can confirm they are the same computer; one it cannot confirm is listed on a row of its own for each, each with its own Remove. If the computer signs in again, it comes back held until you allow it to transmit. Taking back an invitation also takes that person's computers off your network at once, even while the internet is down; a guest's computer Nexus cannot tell the owner of goes too, and is named on the card so whoever uses it can sign in again.
-
Driving the shack from another computer: the screen now shows the shack's own mode.
It follows the shack's Phone, CW or FT section instead of the last one this computer showed, so a Phone band change gives USB or LSB, never DATA; picking a mode is sent to the shack, and a refusal is shown instead of switching. The TX On/Off button beside Tune in Phone now works from there, through all of the shack's transmit checks, and a refused Tune is shown.
-
Driving the shack from another computer: CW's TX On/Off button beside Tune now works
, as Phone's does, so Enter Sends Message can send once you turn TX on; a refusal is shown, and Enter still never turns TX on.
-
Driving the shack from another computer: a refused press now says why, and nothing that belongs to the shack pretends otherwise.
CQ, Tune in every screen, the popped-out Operate window's buttons, JS8 typeahead, band picks, tuning, AGC, RF power and CW speed show the reason when they are refused, and a refused power or speed slider goes back to the rig's level. Opening the contest logger window no longer brings up "Nexus could not start". A send refused because TX is off now says "turn TX on first". Repair clock, Clear test contacts, the Field Day club's Give and Remove, the Remote access card and the Connections log say they are at the shack, and the first-run setup wizard no longer opens by itself on that computer.
-
Driving a station from another computer, TX no longer turns itself off after a second, or after every over.
Letting go of the PTT, Tune off, Phone's Lock, leaving Phone or hiding the voice keyer, and the contest S&P chip each stopped everything at the station, the TX On you had just pressed included. Each now ends only its own transmission, as on the station's own screen; Stop TX and the voice keyer's Stop still stop everything.
-
A computer driving a remote station opens that station again next launch, not its own.
When you Operate a paired station from this computer, Nexus drives that station and keeps its own station off. Closing Nexus and opening it fresh — from the icon, or after a reboot — used to start this computer's own station instead, dropping you out of the shack you were driving. Now a fresh launch connects again to the station you last drove, at the address you reached it at; the connecting banner and Leave are still there to come back to this computer's own station, or to wait, if that station is off or gone. Press Leave, or Operate a different station, and that is what the next launch opens. A station you have since removed is not reconnected to.
-
No more empty window flashing on screen as Nexus starts, on Windows, when it last closed maximised.
Before the splash gave way to the app, a launch that reopened a maximised window showed an empty full-screen frame for a moment and took it away again. The window is now maximised out of sight and appears once, when the app is ready.
-
WSJT-X UDP: a logger's Replay gets back everything Band Activity holds.
When JTAlert, GridTracker or a logger asks Nexus to replay the decodes, as it does when it starts while Nexus is running, Nexus sent only the last period's. It now sends every decode Band Activity still holds, oldest first, each with the start of the period it was heard in and marked not new, as WSJT-X does. Once you erase Band Activity, a logger clears it or a band or mode change wipes it, a Replay sends only what has been heard since; a logger's Clear of Rx Frequency alone leaves it. Erase Band Activity and restart the program: nothing comes back until the next period is decoded.
-
WSJT-X UDP: a logger's free text goes into Tx 5, and out as Tx 5, as in WSJT-X.
Free text from JTAlert, GridTracker or a logger became a chat broadcast, which the FT8 and FT4 screen never sent (and on FT8 in Tempo a piece of it could go out reading as another station's call). Now the text goes into Tx 5. When the program asks for it to be sent, it is your next over, as when you click Tx 5, and an over on the air switches to it, as in WSJT-X; an empty text that is not sent clears Tx 5. It goes out only while TX is on, and it never turns TX on or restarts the TX watchdog. When it does not go out, Tx 5 still shows it and Nexus says why: TX is off, it is text FT8 or FT4 cannot encode (as for the free text you type), the contest screen sends its own exchange, or the program asked to send Tx 5 without its text. Tempo sends it as a chat broadcast, as before, on the Tempo tiers only. With TX off, Enter fills Tx 5, says TX is off and nothing keys. Enter on
W9XYZ K1ABC TNX 73says FT8 cannot encode it and nothing keys. Repeat on FT4, and once on the contest screen (the run goes on). -
Nexus Remote: Save to this computer saves only the station's own kinds of file.
The second PC saves a recording (.wav), an SSTV picture (.png or .bmp) or ALL.TXT, and nothing else. Any other file is refused with a message that names it, and nothing is written to the Downloads folder.
-
FT8/FT4: a logging program's Clear of Rx Frequency clears only that pane.
When a program connected over the WSJT-X UDP link asks to clear the Rx Frequency window, Nexus now empties only its Rx Frequency pane, and a clear of Band Activity empties only Band Activity, as WSJT-X does. Before, any clear from such a program emptied both decode panes.
-
FT-991, FT-710 and FTDX10: the ALC meter works again behind your own older rigctld.
Since 1.19.0 Nexus reads these radios' ALC with a raw
RM4;through rigctld. A rigctld from Hamlib before 4.6 (Hamlib 4.5.5, for example, which many Linux distributions still ship) never answers that raw read, so a radio reached over Network through such a rigctld showed ALC as "not reported" after the first few reads. When the raw read never answers, Nexus now reads ALC the way 1.18.0 did, through Hamlib, for the rest of the session. This changes the CAT reads made while transmitting, so it needs a check on an FT-991 behind its own rigctld. -
Remote: a paired computer can no longer make the station hold hundreds of megabytes in unfinished calls.
A call too big for one message is sent in pieces, and the station limited each call to 16 MiB but let a computer leave 16 of them unfinished at once, about 256 MiB a connection. The station now holds at most two calls of the largest size unfinished on a connection, 32 MiB, and closes a connection that sends more. A large ADIF import, a voice message and an SSTV picture from the other computer go through as before.
-
Remote: a flood of Stops or call-outcome questions from a paired computer no longer slows the station.
Each Stop on the command link started a thread of its own, so thousands of Stops a second could crowd the station's screen and radio loop out. Each kind of Stop now runs on one thread: the first runs at once, a different kind of Stop still runs at once beside it, and Stops of the same kind that arrive while one is running are run once more as soon as it finishes, so a Stop is never lost or held back. At most eight runs of one kind, each with different arguments, wait at once; a Stop past them is answered busy, so varying the arguments no longer makes the waiting list or the work grow. Every Stop still ends the computer's transmit permission the moment it arrives. Questions about what became of earlier calls are answered one after another on one thread.
-
Phone, CW, RTTY, PSK and Satellites contacts now log when they started and ended.
A contact logged from the entry strip starts when its call was entered, typed or clicked in, and ends when you press Log, as a JS8 contact already did; until now both were the moment you pressed Log. A contact typed in under "Logged on another radio" with its own UTC time starts and ends at the time you typed.
-
Every new contact names its operator.
With Operator at the key left blank, your station call is logged as the operator (ADIF OPERATOR), as the box's hint always said. The N3FJP push now sends the contact's own operator instead of always your station call.
-
Your grid and state are logged on each new contact.
New contacts carry your grid from Settings ▸ Station (ADIF MY_GRIDSQUARE) and, on everyday contacts, your State (MY_STATE); a park or summit activation still logs the park's state, never your home one. QRZ, Club Log, eQSL, HRDLog, Cloudlog/Wavelog and the ADIF export receive them. Your LoTW uploads leave out a grid or state Nexus filled in itself, so TQSL keeps signing from your Station Location exactly as before; a grid that came with the contact (from WSJT-X, typed in the Logbook, or imported) goes to LoTW as it always did.
-
Contest and Field Day contacts keep their radio, power and grid, and gain an end time, in the Logbook.
Each contest contact records the radio, station power and grid in use when it was logged, keeps them across a restart, and carries them, with its time as its end time, when the contest is merged into the Logbook. As on everyday contacts, your LoTW uploads leave that grid out; in a VHF contest the grid you sent in the exchange is the one logged.
-
A contact logged for an earlier time is not given today's station details.
A contact whose start is more than 3 hours before you log it (typed in afterwards with its own UTC time, or added in the Logbook) gets no grid, state, operator, rig or power from your current settings, since they may not be what you used then; fill them in yourself if you want them. Anything you enter on the contact is kept, and contacts you log as you make them are unchanged. A contact waiting for your confirm (Prompt before logging) keeps the station details from the moment it was made, however late you confirm it and whatever you changed in Settings meanwhile.
-
A TCI radio's contacts name the radio.
The rig logged for a contact made on a TCI radio is the radio the SDR program reports, such as SunSDR2DX, instead of "TCI".
-
Your station power is logged on every new contact.
The watts in Settings ▸ Digital ▸ Station Housekeeping ▸ Station power go on each new contact as its power (ADIF TX_PWR), and out with it to QRZ, Club Log, eQSL, HRDLog, Cloudlog/Wavelog and the WSJT-X UDP messages your logger reads. Leave it blank and contacts are logged without a power, as before. A contact that already carries a power keeps it.
-
A contest's contacts keep their operator and station call in the Logbook.
Merging a contest into the Logbook dropped the "Operator at the key" each contact was logged with, and stamped the station call in use at the merge rather than the one the contact was made on.
-
Linux: the PC .deb and AppImage run on Ubuntu 22.04, Mint 21, and Debian 12.
They were built on Ubuntu 24.04, which made glibc 2.39 the minimum, so on Debian 12 (bookworm), Ubuntu 22.04 and Mint 21.x the package installed and then the app did not start, and an installed Nexus could not take an update without upgrading the whole distro. Both files are now built inside an Ubuntu 22.04 container and need glibc 2.35 (
ldd --versionshows yours). The Raspberry Pi packages are unchanged. -
FT8/FT4: a call or Call CQ made during the other station's period sent its over twice (needs a check on the air).
Double-clicking a station in the Call Roster or Band Activity, or pressing Call CQ, before your own period began keyed the over at the start of your period as it should. About 2 s later, when the decode of the period just heard finished, Nexus keyed the same over again: Rx Frequency and ALL.TXT showed your message twice, a second or two apart, and the second copy went to the sound card behind the first. Now the over goes out once, with one line, as WSJT-X sends it. A call made after your period has started was never affected. Check on the air: double-click a station during their period, and Rx Frequency and ALL.TXT show your call once.
-
CW: the pitch box can be typed to any pitch again.
Typing into the CW cockpit's Pitch box forced each key into 300–1200 Hz as it was pressed, so typing 650 gave 300 and then 1200; only the arrows could reach a pitch in between. The box now keeps what you type, applies it once it is a pitch in range, and puts an out-of-range entry back into range when you press Enter or leave the box. The decoder passband's F low and F high boxes in Settings ▸ Digital had the same fault and are fixed the same way.
-
CW: the cockpit no longer comes back on your old pitch.
After you changed the pitch in the CW cockpit, the radio kept the new one, but going to another page and back showed the pitch you had before, with the scope marker on it. The cockpit now shows the pitch you set.
-
FT8/FT4: the strip says so when the TX watchdog stops a call.
Calling a station that never answers goes on until the TX watchdog turns transmit off, and the strip then showed only "AwaitReport" beside TX off. It now shows "TX watchdog stopped the call" in red in place of the state, and the window's taskbar button flashes once (a dock bounce on macOS), as WSJT-X does. TX On calls again. How long Nexus calls is unchanged.
-
Signing in and pairing again from another computer.
A sign-in refused because your email address is not confirmed yet now says to confirm it, not "The sign-in was cancelled"; Stations on this network has one Sign in… button, with Link to your account… on a station paired with a code; and a station that no longer knows this computer offers Pair again with its address filled in, in that window and on the client banner, instead of reconnecting to it on every start.
Security
-
A computer no longer takes the station's internet key on Nexus Remote's word alone.
Before, when you added the internet road to a station paired with a code (its owner not yet signed in at the station) or to a station you were invited to, the computer kept the station key the service listed without checking it. Now:
- At home, linking a station paired with a code asks the station itself for its key over your network, before anything is added. If the service named a different key, you are told so and nothing is added.
- Away from the station, or as an invited guest, the station's row shows This station's key for the internet road in the same eight groups the station shows under Remote access. The internet road carries nothing until you compare the two and press It matches. For a station paired with a code, the hold also clears by itself the next time you Operate it on your network and the station names the same key.
- It doesn't match, for a station paired with a code, removes only its internet road: the pairing on your network stays, so you can still operate at home and add the internet road again later. For a station you were invited to, it forgets the station.
- Both of those apply only to a station paired with a code on this version or later, which the computer now records in its credential store when the pairing is made. A station paired with a code on an earlier version is treated like an invited one: its hold clears only with It matches, and It doesn't match forgets it, so you pair it again with a code.
- The station's Approve question for a computer now shows This station's key too, so both keys are read out in the same call.
- Every internet road's row now shows the station's key. A computer that already has an internet road checks it quietly the next time it reaches the station on your network; if the station names another key, that road is turned off and says why. Nothing else changes for roads that already work, and nothing has to be paired again.
- Your radio was never reachable this way: the station only ever lets in a computer you approved there.
-
The station itself now ends a press from a second computer after 3 minutes.
Phone's Lock from another computer had a 3-minute limit, but only that computer kept it: if it failed to let go, the station's own limit was the 10-minute microphone ceiling. Now the station ends any one press from afar 3 minutes after it began, by its own clock, whatever the other computer does. Answering Still talking? there still keeps the Lock on for another 3 minutes, with no break in the audio. A PTT held from afar for more than 3 minutes now ends too; press it again to go on. Lock at the station's own screen is unchanged.
-
A machine on your network can no longer keep your second computer out of Nexus Remote.
A device opening many slow connections from many addresses could take all four of the station's connection places, so a computer you paired could not connect, or reconnect after a Wi-Fi drop. Connections still being set up no longer take those places, and when too many are waiting the oldest is dropped. An open session and Stop were never affected.
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