hamradiotools

Nexus 1.20.0

Released 22 October 2026. The current release is 1.24.0. Download it · Every version

Added

  • TCI connection (Beta): Nexus can talk to an SDR program's own TCI server.

    In Settings ▸ Radio ▸ Rig & CAT, Connection has a new choice, TCI (SDR program) — Beta, for ExpertSDR3 (SunSDR), Thetis 2.10.3.14 and later, and piHPSDR. You set the program's address and TCI port; there is no Rig Model, rigctld or virtual COM port to set up. Find TCI server looks for the program at that address (the port you typed, then 50001 and 40001) and says what answered, such as the program's version and the radio it drives; it only reads, and never transmits or changes the radio. The setup wizard looks for a TCI server on this computer when it opens and offers it, and has an SDR program (TCI) choice. The connection carries the dial, the mode and, with Audio over TCI on, the receive audio; Nexus transmits on it, can draw the program's panadapter and can put Nexus's needed spots on it (the entries below). The SDR-program setup guide no longer says Nexus cannot use TCI.

  • Transmitting on a TCI radio (Beta).

    On a radio whose Connection is TCI, Nexus now transmits through the SDR program. PTT on the Phone screen keys the program's own microphone, and Tune keys its tune carrier at its own tune drive. With Audio over TCI on, as it comes, Nexus's own audio goes to the program over TCI, with no virtual audio cable: FT8, FT4, JS8 and the other digital modes, RTTY, PSK, SSTV, APRS, the voice keyer and the Remote microphone. FT8 and FT4 keep WSJT-X's mid-over switch: a decode that moves the contact while you transmit changes the rest of the over to the next message, never making the over longer. Nexus keys one of these overs only once the program has taken Nexus's audio, never on the program's microphone; an over whose audio the program stops taking is ended, with the reason on screen; and Stop TX ends an over at once, sending none of the rest. With Audio over TCI off, a TCI radio keys like any CAT radio: Nexus plays its audio on the sound card and the program transmits its own input, which you route from Nexus with a virtual audio cable. CW goes out over TCI with the Soundcard keyer; through the program's own keyer it is not ready yet. Every Nexus transmit safeguard applies as on any other connection. Programs that use the radio through Share by TCI are not changed by this: they still may not send FT8, FT4 or the other slot-timed modes.

  • TCI (Beta): Nexus's needed spots on the SDR program's own panadapter.

    On a TCI radio, Spots on the SDR panadapter (Settings ▸ Radio ▸ Rig & CAT, off as it comes) now puts the stations on the Needed board that have a frequency (cluster and skimmer spots, and your own decodes) on the SDR program's panadapter, each in the colour the board gives its need, the most wanted first and at most 100 at once. A spot goes once its station has not been heard for 15 minutes, and all of Nexus's spots go when you turn the switch off, change to another radio or Nexus closes the connection. Click one in the SDR program and Nexus tunes to it, as a click on the Needed board does; the click does nothing else: it never turns TX on or starts a contact, and while Nexus is transmitting it is ignored. A click on a spot Nexus did not put there, or on the program's B receiver, is ignored too. When the switch comes on, and when the connection closes, Nexus clears the panadapter's spots, which in some programs also clears spots another program put there. AetherSDR is the exception: its clear would take off every spot it shows, its own cluster and skimmer spots too, so there Nexus takes off only its own, one by one, sends the colours the way AetherSDR draws them, and puts each spot up again before AetherSDR's 30 minutes for it are over. In an unassisted contest entry the Needed board has no cluster spots, so the panadapter has none either. piHPSDR's TCI has no spots.

  • Share by TCI: programs on this computer can use the radio through Nexus.

    Settings ▸ Radio ▸ Transmit limits & sharing has a new switch, Share by TCI, below Share this radio with other programs. It is off as it comes. Turned on and saved, it makes Nexus a TCI server on this computer: WSJT-X, JTDX, MSHV, Log4OM and other programs that speak TCI connect to the address it shows (127.0.0.1:40001, with a Copy button) and use whichever radio Nexus runs. They follow and set the dial, switch the sideband, may lower the power but never raise it, and get the receive audio Nexus hears. Only programs on this computer can connect, never another computer or a web page. Programs on TCI may transmit is a separate switch, off as it comes and set at the station only: with it on, a program can Tune, key the radio's microphone on the Phone screen and send a logger's CW macros on the CW screen, which Nexus's own CW keyer sends at the program's speed; every Nexus transmit safeguard still applies, and no program can turn TX on. FT8, FT4 and the other slot-timed modes may not transmit through TCI yet, until the delay Nexus adds to a program's timing has been measured. The programs connected are listed with what each is doing and the last thing Nexus refused it, each with a Disconnect. Settings will not save the CAT sharing port and the TCI server port as the same number. A new guide, Share by TCI, covers turning it on and setting up each program.

  • TCI (Beta): the SDR program's own panadapter in Nexus's scope.

    On a TCI radio, SDR panadapter in the scope (Settings ▸ Radio ▸ Rig & CAT, off as it comes) now draws the SDR program's own spectrum in the RF scope and in the Phone and CW scopes: the program's whole receive bandwidth (48 kHz as the programs come) around its receiver, each station at its own frequency and the dial where it is. If the program stops sending it, the scope says so rather than holding an old picture. A program whose TCI has no panadapter (piHPSDR's) leaves the scope as it was, and Nexus's log says why. Turning the switch off, or changing to another radio, stops it. It is a stream of its own: receive audio and keying over TCI work as before.

  • Share by TCI: a program's own transmit audio (Beta).

    With Programs on TCI may transmit on, a program on this computer can now put its own audio on the air through Nexus while Nexus is on the Phone screen, a logger's voice macro for one. Nexus keys the radio when the program's first audio arrives and plays that audio and nothing else, the way it plays its own (the sound card, a Flex's DAX, or an SDR program over TCI), never keying the radio's microphone for it. On a Flex with native audio, where the radio takes its own microphone on the Phone screen, a program's audio is refused, as APRS and SSTV are. When the program lets go, the last of its audio plays out before the radio unkeys. It ends at once on Stop TX, Esc, TX Off, a logger's UDP Halt Tx, the Remote's Stop, the high-SWR cutoff, a band or radio change, the switch turned off, the program's own stop or its lost connection, 0.3 seconds with no audio from it, and 10 minutes on the air. Programs on a Flex's native connection with Flex native DAX audio on now hear the radio's own receive audio (DAX) instead of the sound card's; the Icom network connection carries no audio, so there they hear the sound card. FT8, FT4 and the other slot-timed modes from programs stay refused, and so does any over from a program whose last mode request was a data mode (DIGU or DIGL), on whatever screen Nexus is: WSJT-X asking for DIGU and then keying is held like FT8 even on the Phone screen. A program must also ask for a voice mode (USB, LSB, AM or FM) before its own audio goes out. One that has asked for no mode, as WSJT-X, JTDX and MSHV do with their Radio mode at None (their default), or that asked for CW, is refused. WSJT-X and JTDX ask for a mode only when it differs from Nexus's: with their Radio mode at USB while Nexus is already in USB, they ask for nothing and are refused too. Last refused then says to set the program's Radio mode or to use Nexus for FT8, and that some programs ask for their mode only when it differs from Nexus's.

  • Share by TCI: spots from programs on Nexus's band map (Beta).

    With Spots from programs on, as it comes, the spots a program on this computer sends over TCI (a logger's cluster spots, Log4OM's for one, or a skimmer's) show on the band map and on the Phone and CW screens' band activity, beside the cluster's and kept apart from them. Each shows where it came from: TCI 2 is the program Settings lists as Connection 2, and its mark is dotted. Nexus keeps at most 200 from one program and 500 in all, the oldest going first, and each goes 30 minutes after it was sent. A program can take back its own spots and no other program's. They all go when the program disconnects, when you turn Spots from programs or Share by TCI off, and in an Unassisted contest entry, where Nexus shows no spots at all. A program's callsign, mode and text are shown as plain text. A click on one of these spots tunes Nexus there and does nothing else: it never changes the screen, turns TX on or starts a contact, and while anything is on the air it changes nothing. Every click on a spot in Nexus, a cluster spot worked as much as a program's spot tuned, is passed back to the programs as an SDR program passes it on, so a logger can pick up the station. A spot or a click never transmits.

  • Every contest log numbers its contacts 1, 2, 3…

    The contest screen's log and the logger window's last contacts show each contact's number in a first column, in every contest. In a contest that sends a serial (Sweepstakes, CQ WPX) the number is the serial that contact was sent; in every other contest it counts the contacts in the order you logged them, dupes included. A removed contact's number is never given to another contact (as in N1MM), an edit keeps the number, Clear test contacts starts again at 1, and after a restart the count carries on where it was. The exported ADIF writes the number as STX, and so does each contact's copy in your Logbook. Your sent exchange and the {EXCH} macro carry a serial only in a contest whose rules ask for one.

  • The N1MM broadcast now carries each contest contact's number.

    Scoreboards and loggers that listen for N1MM's contact broadcast receive the number you sent in N1MM's own sent-number field: the serial in a serial contest, the contact's QSO number in every other contest. Ordinary (non-contest) contacts are broadcast as before.

  • Contest operating time.

    The contest screen's scoreboard shows On time and Off time beside the rate meter, and the Score Summary states both. As the sponsors count it, a break of 30 minutes or more between two contacts is off time; the rest from your first contact to your last is on time. Cabrillo has no field for it, so the file is unchanged.

  • CW and Phone: a Resume line when the contest is not running.

    If Contest mode is on but the contest session is not running (it did not start again when you opened the screen, or it stopped while you were on it), the log line said nothing and showed the everyday form, with no exchange boxes and no dupe check. It now shows "Contest mode is on, but the contest is not running" and a Resume button. Resume puts the contest back in S&P and never starts calling CQ.

  • Contest screen: "Work this contest in CW" and "Work this contest in Phone".

    The Contest screen and the Contest Logger window log and keep score but never transmit. With Contest mode on, these two buttons take the main window to the CW or Phone screen, where the contest's log line has Enter Sends Message, Running / S&P and the F-key messages. Pressed in another window, they bring the main window to the front on that screen. If the contest had dropped out, it picks up again in S&P; it never starts calling CQ. A one-time note beside them explains that sending happens there. "Got it" hides the note on this computer.

  • Contest screen: a big clock.

    The Contest screen's top line now shows the time large enough to read at a glance: UTC first, your local time beside it. It is the same clock as the top bar's, so the two always agree, and it is on the screen in the main window, the popped-out Contest screen and the Contest Logger window.

  • Contest screen: drag to resize the log and the last contacts.

    A divider above the Contest screen's log sizes the log against the county/section board above it, and a divider under the last contacts sizes them against the screen below. Drag either, or focus it and use the arrow keys (Shift for bigger steps, Home and End for the ends); double-click or Backspace puts it back. Each window remembers its own sizes (the main window, the popped-out Contest screen and the Contest Logger window), and a size too big for a smaller window is fitted to it when the window opens.

  • Contest entry: Shift+Space goes back a box.

    Space already moves to the next box, as in N1MM; Shift+Space now moves back the other way (from Call it goes to the last box), so a wrong entry is fixed without the mouse. Shift+Tab still works, and Alt+W still wipes the line and returns to the Call box.

  • Contest entry: the county/state box fills itself from your own log.

    When you type a call, the box takes the county or state from your last contact with that station in this contest, else from your call-history file, else from your most recent contact with them anywhere in your log (looked up by call, so a big log costs nothing). A small word over the box says where it came from: "this contest", "call history" or "log 2025". Space or Tab into the box selects it, so typing replaces it, and nothing you typed is ever written over. A station already in the log on this band and mode is not filled from this contest or the log: what it sends now decides dupe or new county, and the amber line shows where you worked it from. Mobiles and rovers (/M, /R) are never filled.

  • Contest entry: an early "Worked" warning at QSO parties.

    As soon as the call is in, a station you already logged on this band and mode turns the Call box amber and lists the counties or states you worked it from ("Worked: COOK, DUPA"), before you type the county. It turns red (DUPE) only when the county you type is one already logged, and a rover in a new county clears it, since that contact still counts. The list narrows as you type the county. In the cockpits' contest entry, the contest logger window and the Contest screen's entry.

  • Contest: frequency markers on the band map, as N1MM's Mark.

    With Contest mode on, press Alt+M in the contest entry, or right-click the band map, to mark the frequency you are on; the call in the entry goes with it, or none if the entry is empty. The marker sits on the band map at its frequency: click it, or press Enter on it, to tune straight back (never while transmitting: Nexus says why and stays put), and press Delete on it to remove it. It goes by itself once you log that call on that band. Markers are yours alone: nothing is posted or spotted, and they are kept for this contest across a restart.

  • Contest: Spot me.

    A Spot me button beside Running / S&P on the Contest screen posts ONE spot of your call on your current frequency to the DX cluster Nexus is connected to, with a short comment beside it ("ILQP CQ" for the Illinois QSO Party, and so on; edit it as you like). One spot per press, then the button waits a minute before it will spot again, so a double-click never sends two. Nothing is ever spotted without your press. With no cluster connected, no callsign set, or a contest whose rules allow no spotting (or spotting only over the air), Nexus says so and sends nothing.

  • CW speed match.

    With Match WPM on in the CW contest strip (or Settings ▸ CW), when you answer a station (your call, your exchange, a reply macro) Nexus sends at the speed it measured for that station, kept between the slowest and fastest you set in Settings ▸ CW (15 and 35 WPM to start). Your CQ, and everything after the answer, goes at your own speed, and your speed control never moves. If Nexus has not copied that station's call in the last few seconds, it sends at your own speed. Off until you turn it on.

  • Contest: Spot me asks twice where self-spotting may be against the rules.

    Many contests that let you use spots still forbid spotting yourself (CQ WW, CQ WPX, CQ WW RTTY, the California QSO Party). There, and in any contest whose rules Nexus has not checked on this, the first press of Spot me sends nothing and says "This contest may not allow self-spotting"; press Spot anyway within 10 seconds to post. Contests whose rules allow it (the ARRL VHF contests, Winter Field Day over RF, the Tennessee and Ohio QSO Parties) spot on one press as before.

  • Spot me on the Spots board.

    The Spots board (the Spots view, the Spots pane in Phone and CW, and the Spots box in any cockpit) has its own Spot me: one press posts ONE spot of your call on your current frequency to the DX cluster Nexus is connected to, with the comment beside it, "CQ CW", "CQ SSB" and so on for the mode you are on. Edit it as you like: Nexus keeps the last comment you typed for each mode, and emptying the box brings "CQ" and the mode back. It shares the Contest screen's one-minute wait, so a spot from either button holds both. Nothing is ever spotted without your press. With Contest mode on, the running contest's rules apply exactly as on the Contest screen. With no cluster connected or no callsign set, Nexus says so and sends nothing.

  • Logbook: export just the contacts you pick.

    Ctrl-click (⌘-click on a Mac) rows in the Logbook to pick them, Shift-click to pick a run, or press Space on the focused row; Esc clears. Export selected saves those contacts as an ADIF file in your Downloads folder, each written exactly as the whole-log export writes it. A new search or filter clears the picks, so nothing you can no longer see is exported. When an export (selected, date range or CSV) holds no contacts, the Logbook now says so and writes no empty file.

  • Click a contact to edit it.

    A previous contact in a cockpit's lookup card now opens the Logbook with its editor already on that contact, the same form the Logbook's ✎ opens, and Save there saves it exactly as an edit made from the Logbook does. In Awards, each contact in the confirmation checklist has a ✎ that does the same. A contact changed or deleted elsewhere since it was listed is not overwritten: Nexus says so and leaves you in the Logbook to find it.

  • A Recent contacts box under the log entry.

    Phone, CW, JS8, RTTY and PSK can show your last five contacts, newest first, right under the log form; click one to open it in the Logbook's editor and fix a busted call or a wrong report. Five reaches back past the contact you just logged without crowding the form. Turn it on in ⊞ Panels ("Recent contacts"); it starts hidden, so your screen does not change until you do. It sits inside the log pane under the form and uses only the room the form leaves, so the form and its Log button stay where they were; on a short window the log pane scrolls to it, and the stop and transmit controls stay where they are.

  • Contest entry: an optional "RST sent" box.

    Turn on "Show the RST sent box" in Settings ▸ Contesting ▸ Contest, and the contest entry gets an RST sent box just before the received report, as N1MM shows Snt and Rcv. It holds the report the contact logs as sent: 59 on phone, 599 on CW and digital. Space and Tab skip it, so a run goes Call, received report, exchange as before; click it, or press Shift+Tab from the received report, to change it. A report typed there (two digits on phone, three on CW and digital) is logged as sent for that contact only, and goes into the Cabrillo and ADIF files; the next contact goes back to 59 or 599. It is in the cockpits' entry, the contest logger window and the entry-only pop-out, and it is shared between them like the other boxes. It shows only in a contest whose exchange sends a report, so Field Day has none. Off by default, and then nothing changes.

  • Phone's Lock (hands-free PTT) now works from a computer driving your station.

    Tick Lock, click PTT once to talk and again to stop, as at the shack. It is the same press as holding PTT, so it stops the same ways: Stop TX, a dropped link, your microphone going quiet for a fifth of a second, or leaving Phone. A Lock from afar also has a time limit: after 3 minutes on the air it ends by itself. Twenty seconds before that, Phone asks "Still talking?"; click Keep talking or press K for 3 more minutes. The shack's own Lock and the rig's VOX are unchanged.

  • Contest band map: dupes and new multipliers are marked.

    While a contest runs, the Band activity strip, the pop-out band map and the Spots list in the CW and Phone cockpits mark each spotted station the way contest loggers do. A station you already worked on that band and mode, under the contest's own dupe rule, is struck through and dimmed, with "dupe" in its tooltip (the Spots list also says DUPE). A station that would be a new multiplier wears a MULT tag, and its tooltip names the multiplier, for example "new mult: county COOK" or "new mult: country Japan". The dupe check is the same one behind the log strip's DUPE badge, and the multipliers are worked out by the contest's own scoring. A multiplier that comes from the exchange (a county, a section, a zone) is known only for a station you worked before, from what it sent you then; Nexus does not guess it for a station it has never logged. Outside a contest nothing changes.

  • Contest band map: multipliers predicted from your call-history file.

    With a call-history file imported for the running contest, a station you have never worked now shows MULT? (an outlined tag, so it reads differently from a confirmed MULT) when the county, state, section or zone the file gives it would be a new multiplier. The tooltip says where it came from, for example "predicted from call history: county LAKE"; for a county-line station the file lists with several counties, it marks every county that would count and names the line. The value is read the way the log strip's call-history fill reads it, and counted by the contest's own scoring, so a province the file gives by name counts once even where the contest lists two spellings of it (Prince Edward Island in the Illinois QSO Party predicts PEI). Once you have worked the station, what it sent you counts instead of the file. No file, no entry for the call, call history turned off (or Unassisted), or no contest: no prediction.

  • PstRotatorAz: Nexus now talks to it directly.

    The rotator picker's PstRotatorAz / PstRotator (UDP) entry no longer goes through Hamlib's PstRotator backend, which sent every bearing garbled (90° went out as 90.000000.2) and could not stop the rotor. Nexus now sends PstRotatorAz the commands its own manual documents, so pointing at a call or a bearing, STOP and the compass all work. STOP is sent twice, because UDP has no acknowledgement. When PstRotatorAz does not answer, the compass shows "—" instead of the target or 0°. Nexus listens for PstRotatorAz's replies on its UDP Control Port + 1 (12001 by default); if another program holds that port, the Connections log names it and says how to move PstRotatorAz to another port. A station already set up with this entry keeps its settings.

  • Contest statistics per operator.

    In a multi-operator contest the Contest screen's score area now has an Operators section: each operator's QSOs, points and the multipliers they worked first, with their share of the total, their rate over the last 10 and 60 minutes, their best clock hour, and a band × mode table. Dupes, banned modes and removed contacts count for nobody, as in the score; contacts logged with no operator named are their own row, shown as —. The Summary export carries the same section. A new Operators box, for Conditions, the dashboard window and the rail beside a cockpit, shows who is at the key and the leaderboard while a contest runs.

  • RTTY: a tuning scope beside the decoded text.

    The classic crossed-ellipse picture: a tuned signal draws a square "+", and a mistuned one turns the cross clockwise when the signal sits high and counter-clockwise when it sits low, with the same reading in words under it ("Tuned", "Signal 20 Hz low"). ◀ ▶ under it move the decoder 5 Hz at a time (hold to repeat); in AFSK that moves your transmit tone too, so they are off while you transmit. It is the ⊞ Panels entry Tuning, shown by default, and it works on a second computer driving the station with Nexus's own Remote client. Netting is refused while transmitting, from the waterfall too: a click mid-over used to move the AFSK tone of the over on the air. (idea: the Diddle project by WW2DX)

  • RTTY waterfall: callsign tags, span and speed buttons, and a brighter picture.

    A station the decoder copies sending its own call (DE W1AW, or CQ TEST W1AW W1AW) gets a small tag at the top of the waterfall, on the frequency the decoder heard it. Click a tag to net onto that station; like a click on the waterfall, it does nothing while you transmit. Tags fade after 3 minutes without being heard and are gone after 5. A call that is only named (the K1ABC in K1ABC DE W2XYZ) is not tagged, and text copied across a net or a retune is not used. In a running contest, a station already in the log is struck through and dimmed. The header has span buttons (1k, 2k, 3k, 4k; the audio waterfall covers 0–4 kHz, so there is nothing wider to show) and speed buttons (Fast, Med, Slow), and both are remembered. The RTTY waterfall now draws through a contrast curve: the noise floor stays dark and a keying mark/space pair stands out about twice as strongly on Inferno or Viridis, and somewhat more on Turbo. Its rows, and the SSTV waterfall's, now also come at an even pace: they used to arrive every third or fourth frame, so the scroll stuttered. The other waterfalls keep the row timing they had.

  • Nexus Remote: on the shack's own network, Remote stays free.

    When an account can no longer use Remote over the internet, because its trial is over or its paid plan has lapsed, Stream and Listen still work from a browser already approved for the station, as long as that device is on the same network as the shack. The stream is held to that network at both ends and never goes through the relay. A shack running an older Nexus is named as the reason the stream cannot start.

  • Nexus Remote: one trial per callsign and per shack computer.

    Approving a station now sends the station callsign from Settings ▸ Station and one-way hashes of this computer's hardware and installation IDs; the IDs themselves never leave the computer. When the service refuses the approval for one of these reasons, Nexus at the shack says which one and what to do about it.

  • RTTY: AFSK on USB.

    Settings ▸ Digital ▸ RTTY has a new AFSK sideband choice: LSB (standard, the default and unchanged) or USB. On USB, Nexus puts the rig in its upper data mode (DATA-U, USB-D or DIGU) and swaps the AFSK tones itself, so mark stays high on the air and the decoder still copies. Reverse now only flips the sense for a station sending upside down; its help text no longer tells you to use it for USB. True FSK is unchanged.

  • Yaesu FT-1000 and FT-1000D in the rig list.

    Both now appear in the default list beside the FT-1000MP and use their own Hamlib driver (the FT-1000 driver is marked Beta by Hamlib).

  • Nexus Remote: operate the shack from a second Windows PC with Nexus on it (Beta).

    On your own network, choose Operate from this computer beside your shack in Stations on this network: the second PC shows the full Nexus screens for the shack's radio, plays its receive audio and sends your microphone, and Phone PTT, CW from the keyboard and its macros, FT8 and FT4 (answering, Call CQ and contest S&P, timed by the shack) and JS8 work as at the shack. Stop works from the second PC on its own road, and the shack unkeys within about 5 s if the network or the second PC drops. Passwords and remote-access settings stay at the shack, both PCs must run the same version, and there is no paddle from afar. It is in the regular Windows installer, a Beta like the rest of Nexus Remote, and needs no special build.

  • Nexus Remote: operate from the second PC over the internet too (Beta).

    For a shack paired with a code, press Sign in… on its row in Stations on this network and sign in to Nexus Remote in your web browser; a shack added by signing in has the internet road from the start. Either way, approve the PC at the shack under Remote access: until then the road waits. From then on, when the shack is not on the network you are on, Operate from this computer reaches it over the internet instead, and it moves back to your own network by itself when the shack answers there again. The internet road is part of Remote's paid service; on your own network it stays free. Stop keeps its own road over the internet as well, so nothing transmits unless that road is working; on a network that blocks it (some hotels and offices) you can still watch, tune and log, and transmitting is off. After 15 minutes with no click, key or PTT, Nexus asks "Still there?" and ends the internet link a minute later if nobody answers. Receive audio waits 120 ms before playing over the internet (60 ms on your own network) to ride out the internet's jitter.

  • Nexus Remote: add your station to a second PC by signing in, with no code (Beta).

    In Stations on this network on the second PC, press Sign in… and sign in to Nexus Remote in your web browser with the account your station is linked to, or one its owner invited to operate it. The station is then on that PC on its own network in one step, with no code to type and nothing to press at the shack. Over the internet the PC waits until you approve it at the shack under Remote access, where Nexus asks with the PC's key: a sign-in alone never lets a PC or a browser operate the station over the internet. Nexus finds the station on the network by name, or asks for its address, and before it connects it checks that the station Nexus Remote lists is the one its owner signed in for at the shack; the shack checks the PC's sign-in itself in turn. The station must be signed in to Nexus Remote at the shack first (Settings → Station → Remote access). A PC already paired with a code has Sign in… on its row: it links that pairing to your account and adds the internet road; for a station not yet signed in at the shack the road waits for Approve there, as before. Pair with a code instead… stays for such a station. A PC invited only to listen is not added; listen in your web browser instead.

  • Nexus Remote: a signed-in PC keeps its place on the station's network by signing in again every 30 days.

    The station takes a PC on its own network for 30 days from that PC's sign-in, with the internet up or down. In the last week the PC's row in Stations on this network says by what day to sign in again and offers Sign in again, and Operate from this computer signs in again by itself, opening the browser while you operate, so the link is never dropped for it.

  • Nexus Remote: signing in shares less about you.

    The Remote web page's sign-in no longer asks your account for your name, nickname or picture, and neither does any sign-in in Nexus. The shack's own sign-in (Settings → Station → Remote access → Sign in to Nexus Remote) does not ask for your email address either: Nexus Remote passes that sign-in on to every computer that you, or someone you invite, signs in on, so a guest's computer never receives your address. A second PC's sign-in carries its verified email address, which is how your shack recognises a person you invited.

  • Nexus Remote: add your station from a PC that has never been on its network (Beta).

    A laptop away from home, or a friend you invited who lives elsewhere, can now sign in from Stations on this network and keep the station: when Nexus does not find it on the network the PC is on, press Not on this network and the station is added over the internet, waiting until you approve the PC at the shack under Remote access. Operate from this computer then drives it over the internet road (part of Nexus Remote's paid service). The first time that PC is on the station's own network, press Sign in… on the station's row there once: the station is then on the PC on its network too, with the same keys and no second device at Nexus Remote, and from then on it signs in again every 30 days as any other.

  • Nexus Remote: a signed-in PC paired again with a code stays on the station's network (Beta).

    A PC added by signing in is taken on the station's own network for 30 days from its sign-in, and to stay longer it signs in again, which needs Nexus Remote. Pairing it again with a code ends the 30 days: it then stays until you remove it at the shack, as any PC paired with a code does, and signing in from its row later starts the 30 days again. So if Nexus Remote cannot be reached, pair that PC again with a code: Pair a computer at the shack, then Pair with a code instead… on the PC. With the internet up or down, its row in Stations on this network then no longer asks you to sign in again by a date, and Operate from this computer no longer signs in again by itself. Remove such a PC at the shack: removing it on the Nexus Remote web page no longer takes it off the station's network. If the shack cannot save the change, it refuses the pairing ("The station could not keep the pairing.") and the PC keeps its 30 days.

  • Nexus Remote from a second PC: every JS8 switch, and satellite tracks that end when the second PC goes.

    HB, Relay, HB ACK and HB NET now turn on from the second PC, as Auto-reply already did, and Stop or a dropped second PC still ends every JS8 transmission. A satellite track started from the second PC stops, and hands the radio's dial back, within seconds of that PC dropping, as a transmission does; a track started at the shack runs on.

  • Nexus Remote from a second PC: APRS, SSTV and Chat transmit too.

    From the second PC you can now send an APRS beacon or message, arm APRS Monitor (which lets automatic acks go out), send an SSTV picture, and in Chat send a message or broadcast, resend one, run CQ and turn on the presence beacon, and a CQ run started from the Operate mode menu works as well. Stop on either PC ends each, and if the second PC drops the shack unkeys within about 5 s. Automatic APRS acks, the presence beacon and the Chat CQ run started from the second PC switch off on Stop, when it drops, or when its permission to transmit is withdrawn, and a Chat message it queued is dropped (shown as not sent, ready to resend), so nothing it left keys later; APRS keeps receiving. A settings save from the second PC cannot turn on the presence beacon, JS8's automatic replies, relay, heartbeat acks or APRS-IS relay, or a WSPR beacon, and a stale Settings save at the shack no longer turns the beacon or those JS8 switches back.

  • Nexus Remote: Tune, ATU, RTTY and PSK now work from the second PC (Beta).

    Tune, the radio's own tuner (ATU), RTTY and PSK sends, continuous TX with typing, and RTTY Auto's CQ and answer now work from the second PC as at the shack. Every transmit check at the shack still applies, including the tune carrier's time limit and continuous TX's own limit. Stop on either road ends each of them, and so does losing the second PC for about 5 s: continuous TX and an RTTY Auto run end too, and nothing keys again until you start it again.

  • Nexus Remote: take control from a second PC.

    When another PC is operating the shack, the banner now offers Take control. Confirm it and anything the other PC is transmitting stops at once, a satellite track ends, and this PC starts with TX off; the other PC's banner says it lost control and offers to take it back the same way. The shack's own screen and every Stop still work as before.

  • Nexus Remote: the shack's recordings, ALL.TXT and SSTV pictures reach the second PC.

    The SSTV gallery and its picture viewer now show the shack's pictures on the second PC (they were blank), and Save a copy saves the shack's picture there. Where the shack shows Reveal in folder for ALL.TXT, the QSO recordings and the SSTV gallery, the second PC shows Save to this computer, which copies the shack's file into its Downloads folder. Only those three folders can be read from afar.

  • Elecraft KPA1500 over the network.

    In Settings ▸ Radio ▸ Amplifier, a KPA1500 can now be reached by its IP address instead of a USB cable: pick Network (KPA1500) under Connection and type the address from the amplifier's NET IP ADDRESS menu (port 1500). Nexus uses the amplifier's UDP server, which any number of programs can share, so Elecraft's KPA1500 Remote keeps working alongside. Readings, Operate/Standby and the band buttons work as they do over USB, with the same refusals while you transmit; an amplifier that stops answering shows "Not answering".

  • RTTY screen: the waterfall shades the mark and space tones, and Auto-tune nets onto a signal.

    A band now fills the waterfall between mark and space where the decoder is listening, and follows the AFC. It turns red while you transmit. Auto-tune, in the waterfall's header, finds the nearest signal near the current tones whose two tones sit at your shift, passing over single carriers and signals at another shift, and nets onto it. Netting moves your transmit tones too, so Auto-tune is off while you transmit.

  • Contest logger window: drag it small and keep it in front.

    The contest logger window (the contest screen's ⧉ Logger window) now drags down to 420×320, small enough to drop in a corner beside another program; its call, exchange boxes, Log button, dupe warning and newest contact stay on screen, and the boxes wrap to a second row instead of shrinking. Keep in front on its bar keeps the window in front of Nexus and your other programs, even while you work in another one; press it again to let the window stack as an ordinary window. The window reopens at the size and place you left it, brought back onto a monitor that is still attached, and pinned if it was pinned. ⧉ Pop out entry on the Contest screen's entry opens the same window with the entry alone (the call, the exchange, the dupe warning and Log, without the last contacts or the rest of the contest screen); it shares the contact with your entry, and Enter in either logs it once. Entry only on that window's bar switches between the entry alone and the whole window.

  • Spots pops out into its own window.

    ⧉ Pop out in the Spots header opens the board in a window of its own, for a second monitor, as the Needed board's does. It is the whole board: the search, the filters, Hide worked and Spot me. Clicking a row tunes the radio to the spot and the main window opens the matching screen, as from the Needed window. The window's filters are its own: it opens with your Spots view's filters, and closing it forgets them. The Spots box in the popped-out Conditions window now has Spot me too, as it has in the main window.

  • CW: a turn cue for when you copy with the decoder.

    A small lamp at the start of the CW send row says whose turn it is (≋ W1ABC sending, ▶ Your turn · F3, ⏸ Hold · W2XYZ, ? Not sure · F7), and the F-key that fits glows again: F2 to answer a CQ, F3 when a station comes back to you, F4 when they sign. "Your turn" waits for the other station to stop AND end its over (K, KN, BK, QRZ, part of your call with "?", a CQ), so a pause alone only says "Not sure"; your own over heard back through the radio never counts as theirs. When a DX comes back to you in a pileup no key glows, and the lamp says Your turn · send 5NN TU. The Decode pane's speed now reads them 18 · you 25 WPM, and a click sends at their speed for this contact. It never transmits: every send is still your own key press. It shows with the AI decoder on and the Decode pane shown, never in an unassisted contest entry, and unticking Turn Cue in ⊞ Panels hides it, after a restart too, until you tick it again. A screen reader hears "Your turn" and "Hold" once per over; a short chirp is there too, off until you turn on CW turn sound in Settings ▸ Appearance ▸ Accessibility & eyes-free. The cue lands about a second after the other station stops: in time for a ragchew or a CQ, tight in a contest, and too slow to win a pileup, where it tells you when not to call.

  • Every save of the contest log now keeps backup copies beside it.

    The contest log (fieldday_backup_<n>.adi) is the only copy of a contest's contacts until you merge them into the Logbook. Each time it is saved, Nexus also writes a copy to a fieldday_history folder next to it: %APPDATA%\tempo\fieldday_history\ on Windows, ~/.config/tempo/fieldday_history/ on Linux and Mac, and tempo-r<n> in place of tempo for a second radio's window. It keeps the last 10 saves (….save-000123.adi, the highest number is the newest) and one copy per hour (….hour-20261017-21.adi, the hour in UTC) for the last 48 hours. A big contest log is well under 1 MB, so the folder stays a few MB at most. Nexus never reads these copies back on its own, and a copy that can't be written never stops a contact from being logged. To use one: quit Nexus, copy the backup you want over fieldday_backup_<n>.adi (keep the damaged file somewhere first), rename it to that name, and start Nexus again. You can also import a copy into the Logbook like any ADIF file.

Changed

  • Nexus Remote: inviting someone to operate says what that gives them.

    Under Settings ▸ Station ▸ Remote access ▸ People, with Operate chosen, the form now says that someone invited to operate can do all you can from another computer: transmit under your callsign, edit, export or delete your log, upload with your saved logins (LoTW signed with your certificate), spot under your call and read your Winlink mail. Invite to operate only someone you would hand the shack to; Listen gives none of that.

  • Windows: FT8, FT4 and the other WSJT-X modes finish decoding sooner.

    The FFT library in the Windows build now uses the processor's SSE2 and AVX instructions, as WSJT-X's own Windows build does; until now it used none. On one Windows PC the early FT8 decode took 17-36 % less time and the full decode 1-21 % less, and the decodes were exactly the same. There is nothing to set: the library picks what the processor has when Nexus starts, and a processor without AVX works as before. Linux and Mac builds are unchanged.

  • FT8/FT4: a late reply changes the over already on the air, as in WSJT-X.

    When your partner's reply is decoded after your over has started (a weak R-report or RR73 that only the full decode finds), Nexus used to send the old message to the end of the over and the right one an over later. It now switches the rest of the over to the new message, as WSJT-X does: the over keeps its start and end, and ALL.TXT gets a second Tx line for it. Programs that listen on the WSJT-X UDP feed (GridTracker, JTAlert) are told the new message as the over switches. A Tx button clicked during an over switches it the same way.

  • Flex native audio (Beta): the late-reply switch works on DAX too.

    With Nexus's own Flex client sending the over over DAX, a reply decoded after the over has started now switches the rest of it to the new message, as on a sound card. Nexus sends the radio only the audio that is due, so the part not yet sent is replaced; the over keeps its start, its end and its PTT, and Stop TX still cuts it at once.

  • FT8/FT4: an RR73 answering your report is answered with 73, as in WSJT-X.

    When the station you sent your report to rogers it with RR73 (or RRR) without sending its own R-report first, Nexus kept sending the report. It now sends 73 and the QSO is complete, as WSJT-X does; if the RR73 is decoded while the report is already on the air, the rest of that over becomes the 73. A bare 73, an RR73 from another station, or one sent to another station changes nothing.

  • FT8/FT4: which late replies change the over on the air, as in WSJT-X.

    Once an over carries your RR73 or 73, no reply changes it any more: WSJT-X turns Enable Tx off as it sends one, so a reply decoded then cannot move it. A CQ run that logs the contact and goes back to CQ, or gives up on a caller who went quiet, now lets the over on the air finish: before, the rest of your RR73 or report could become the CQ. If you close with RRR and your partner's 73 arrives while the RRR is on the air, the contact is over, so the rest of that over is your CQ, as WSJT-X does it: a 73 answering your RRR moves WSJT-X on to its CQ message (Tx6) and turns its Enable Tx off. TX turns off after that over with "Disable Tx after sending 73"; either way nothing is sent after it.

  • Contest FT8/FT4: a late reply changes the over on the air inside a contact.

    In the Contest screen's Running and S&P, a reply decoded after your over has started now switches the rest of that over to your next message, as WSJT-X does: your exchange becomes the RR73 when the runner's rogered exchange arrives, and the rogered exchange becomes the 73 when the caller's RR73 arrives. It never starts a contact: a CQ on the air is never switched to an answer, and an over to one station never becomes a call to another.

  • FT8/FT4: an RR73 answering your RRR is answered with 73, as in WSJT-X.

    If you close with RRR (Settings: RRR instead of RR73) and your partner answers it with RR73 or RRR, Nexus now sends 73, once, and the QSO is complete; before, it closed without one. If the RR73 is decoded while your RRR is already on the air, the rest of that over becomes the 73, and "Disable Tx after sending 73" turns TX off after it as usual. The contact is logged once. After your RR73 nothing changes: your partner's 73, RR73 or RRR gets no reply. A Hound never sends the 73: by Fox/Hound mode's own rules the Fox's RR73 ends a Hound's contact and the Hound sends nothing more, as in WSJT-X, since a 73 would only add noise where the Fox transmits.

  • FT8/FT4 Call CQ: a caller's RR73 to your RRR gets one 73, then the run calls CQ.

    With "Roger with RRR (not RR73)" on, a Call CQ run now answers the caller's RR73 (or RRR) to your RRR with 73, once, as WSJT-X does, and then calls CQ again. Before, the run went back to CQ without a reply, and when that RR73 was decoded while your RRR was on the air, the rest of the RRR became the CQ. If the RR73 is decoded late, while the next over is already on the air, the rest of that over becomes the 73. TX stays on, the contact is logged once, and a repeat of the caller's RR73 gets nothing more. Only the caller's own RR73 or RRR to you counts.

  • Contest entry: the sample text in empty boxes is quieter.

    The grey examples ("W1AW", "599", a county) are now in normal weight instead of bold, and a shade darker in the dark themes, so they no longer read like something typed in. They stay readable in every theme.

  • The AI CW decoder keeps up with the signal.

    Clicking a spot, changing band or typing a frequency no longer leaves the decode pane blank for about 13 seconds while the decoder refills: copy of the new station starts about a second after it does. Letters now land about a second after they are sent instead of two to three seconds, in small steps instead of bursts. The last few letters, the ones the decoder is still unsure of, show at once in a dimmer colour and turn normal when it confirms them; it may still correct a dim letter. Only confirmed letters are used for anything: the callsign chips, the report and name the log picks up, and the copy seen from a Remote client. The decoder works harder for this: about half of one CPU core where it used a sixth, never more than two thirds of a core on a slow computer, and on Windows it runs at a lower priority than the radio and audio.

  • From the Remote client, Settings now shows which logbook credentials are saved at the station, and the connector Test buttons work.

    The saved / not saved badges (and the Icom network password's) are read at the station and come back as yes or no; they no longer look empty, as if nothing were saved. QRZ Logbook, N3FJP and Cloudlog/Wavelog Test run at the station with the key stored there and answer only whether it worked, with a message. No key or password crosses the link: a QRZ reply that echoes the key has it masked, or is withheld. Typing or clearing a credential is still done at the station itself.

  • Stations on this network now leads with Operate from this computer.

    It is the first and main button beside each station: Nexus runs on this PC and the radio follows your own clicks and pop-outs. Streaming the station's screen is still there as a smaller button after it, for when you only want to see the shack's screen.

  • FT8, FT4 and FST4: when the other station repeats its report or grid, your repeated reply carries the new signal report, as WSJT-X 3.0 does.

    Heard at +20 and then again at +27, Nexus now sends R+27 the second time instead of R+20, and logs +27 as the report sent. Nothing else about the sequence or its timing changes; other modes keep the report fixed, as WSJT-X does.

  • Phone voice keyer: a slot's Record, Import and Delete buttons now sit on the left of the slot, away from Play, and Delete can be undone.

    They used to sit right under Play, where Delete was easy to hit by mistake. After Delete the slot reads empty and "Deleted F1 (CQ)" offers Undo for about 8 seconds; Undo brings back the same recording under the same name, and only after that does the recording really go. Play, the F-keys and ■ Stop work as before.

  • Remote: Settings on a computer driving the station now shows which settings can only be changed at the station.

    The transmit limits and safety stops, the switches that let other programs or a browser transmit, the PTT method, port and lines, the licence class, the TQSL path, the addresses your logging-service keys are sent to, and the keys themselves are greyed out there and say "Set at the station", with the station's own value. A save from that computer already left them as the station had them; before, the form let you edit them and quietly put them back. At the station itself nothing changes.

  • Nexus Remote: every setting only the station can change, in one list.

    A save of Settings or of a profile from a computer driving the station keeps the station's own value of each of these. What lets the station transmit with nobody at a key, or lets another program or a browser transmit: the WSJT-X UDP API and its address, Share this radio with other programs (the CAT broker) and its PTT, JS8's API over TCP and UDP and its APRS-IS relay, Share by TCI with its port, Programs on TCI may transmit, CW macros and Spots from programs, the Remote stream, the WSPR and FST4W beacons' Transmit %, and a CQ run's pause. The guards on a transmission: the TX watchdog, JS8's idle watchdog, the tune limit, the Parsec stop, "Disable TX after sending 73", the CQ, reply and Chat retry limits, RTTY Auto's repeats, the high-SWR cutoff and its level, the power ceiling for each mode, and the licence class. The lines that key the radio: the PTT method, port and line and the CAT port's RTS, DTR and handshake settings, the CW keyer backend, keyline port and line and the WinKeyer port, the RTTY keying backend with its FSK port and line, and each radio's Let Nexus send CW, Tune and ATU through the native Flex client. The TQSL path. Where your keys and passwords are sent: the Cloudlog/Wavelog URL, the Field Day club host, and an Icom network radio's address and port. And the Club Log and Cloudlog keys themselves.

  • The assistance record and the contest-category note name the CW decoder, not the AI CW decoder.

    An unassisted entry turns off the classic decoder as well as the AI one, and CQ WW's rule names "a CW decoder". With the AI switch off, the classic decoder still copies CW, while the record (Settings ▸ Contesting ▸ Your entry) showed the AI CW decoder as off. The source is now the CW decoder, on whenever any CW decoding runs, which is everywhere but an unassisted entry. Rows recorded before keep the name they were written with.

  • Declaring NON-ASSISTED offers the Unassisted entry switch.

    In Settings ▸ Contesting ▸ Your entry, picking NON-ASSISTED under Spotting assistance writes it into your Cabrillo log but turns nothing off: the CW decoder, the spots, Super Check Partial and call history stay on until you switch Unassisted entry on. While the switch is off, a line beside the picker now says so, with a button that turns it on. Nothing turns it on unless you click.

Removed

  • Nexus Remote: the old browser workspace that was hidden in 1.17.0.

    Remote is the shack's own screen streamed to your browser; the watch-and-control workspace it replaced is gone from the page.

Fixed

  • FT8: a period with almost no receive audio is not decoded, as in WSJT-X.

    When a whole period's receive audio is under half a bit (0.5 LSB rms), as with the rig's audio muted, the input turned right down or the cable pulled, WSJT-X does not decode it at all. Nexus did, and after a busy period its a7 decoder could "hear" that period's stations again in a few stray bits of noise. In a QSO such a line could read as your partner's RR73 or R-report: Nexus then sent the next message and logged a contact that was never finished. Such a period now gives no line in Band Activity, ALL.TXT, the WSJT-X UDP feed or PSK Reporter, and the QSO repeats its last message as WSJT-X does. Receive audio at any working level decodes exactly as before.

  • Band Activity and Rx Frequency: a line's time is the start of the period it was heard in, as in WSJT-X and ALL.TXT.

    The time was when the line reached the list, so a line the full decode found at :34 read :34 under the :15 period's separator. It now reads :15; hold the pointer over the time to see when the line arrived. A line heard before a band or mode change shows the period it was heard in, and your own transmissions still show when they were sent. With an MSK144, FST4, Q65 or JS8 T/R period other than the usual one, the period separators show the right time now too.

  • WSJT-X UDP: each decode carries the start of the period it was heard in, as WSJT-X sends it.

    JTAlert, GridTracker and loggers were given the moment Nexus sent each decode. A decode from the full pass, which finishes a second or more into the next period, carried a time in that next period (a decode of the 12:00:15 period sent at 12:00:31 said 12:00:31), and an early-pass decode a time 12 seconds into its own. Each decode now carries its period's start, 12:00:15, and so does a logger's Replay. ALL.TXT already wrote that time.

  • CW: "Colors" in the scope's head sits with its colour picker.

    The word stood against the zero-beat reading, in the same small capitals, and read as part of it, while the picker sat in the middle of the row. The word and the picker are now one group after the zero-beat reading, set off from it by a thin line, and clicking the word opens the picker. On the Phone screen the colour picker sits beside the scope strip's ✕ too, where it had stood a third of the way along the row.

  • CW on the Soundcard keyer no longer warns of a PTT problem after a message that went out whole on a TCI radio.

    Each word after the first asks for the transmitter again while the first word's key still holds it, and the TCI connection refuses a second key while one of Nexus's is on the air. The CW screen read that as "the rig didn't accept PTT" and suggested the WinKeyer or the CAT keyer (which keys nothing on TCI), though every word had gone out. Those words now leave the CW screen as the message's first word left it. A message whose first key the radio refuses still says so, as before.

  • Moving from SSTV to the Phone cockpit no longer retunes the radio.

    If you reached an SSTV frequency on the radio's own knob, or Nexus opened on the SSTV screen, clicking Phone moved the radio to the phone segment's default frequency or your last phone frequency. It now stays on the SSTV frequency until you move it: by tuning, a band or memory pick, or a spot. Leave Phone and come back, and you return to where you left it. A frequency your licence may not use for phone (7.171 MHz for a General, 28.680 MHz for a Technician) still moves you to a legal phone frequency, as before.

  • On a 2 m FM SSTV channel, clicking Phone keeps the radio in FM.

    On the SSTV screen, picking an FM image channel (144.500 MHz, or a frequency you set to FM there) puts the radio in FM, and clicking Phone kept the frequency but switched the radio to USB. Phone now keeps FM there, and its AUTO mode button reads FM, until you move off the channel from Nexus (a typed frequency, a band, memory or spot pick), go to another mode, or pick a mode on Phone's mode buttons. Looking at another screen and coming back to Phone keeps it too. Phone reached any other way still follows your phone mode setting.

  • With two radios, a frequency you pick right after an FM channel goes to the radio meant for it.

    With 2 m FM set to go to one radio and 2 m SSB or FT8 to another, a band pick or a typed frequency made while the radio sat on an FM channel (an SSTV image channel such as 144.500 MHz, or a repeater Nexus tuned) went to the FM radio, which was then put in USB or DATA-U. It now goes to the radio set up for the mode it is tuned in. Memory and spot picks already did.

  • ISS SSTV auto-arm now puts the radio in FM.

    At the start of an ISS pass, with the SSTV or Satellites screen open, the auto-arm tuned 145.800 MHz but left the radio in the last mode you used (DATA-U after FT8, USB after Phone), so no picture could come through. It now holds 145.800 MHz in FM, as picking that channel on the SSTV screen does, and with two radios it uses the one set up for 2 m FM. After RTTY it also tuned 2.125 kHz high and then did not put your frequency back at the end of the pass; it now tunes 145.800 MHz exactly. At the end of the pass your own frequency comes back on its own radio, in its own mode. A satellite you are working keeps its mode.

  • SSTV's FM channels and the ISS auto-arm now transmit on the channel, with no repeater offset or tone.

    After you had tuned a repeater, the SSTV screen's 145.800 and 144.500 MHz FM channels, the ISS auto-arm's park on 145.800 MHz, and Phone kept on either channel all used that repeater's offset and tone: the radio was set to transmit 600 kHz away, with the tone. On 144.500 MHz that is 143.900 MHz, outside the 2 m band: with a US licence class set, transmit was locked out there, and with License Class set to Open nothing stopped it. These channels are now simplex with no tone, as APRS is. A repeater you tune still gets its own offset and tone, and so does a frequency you set to FM yourself on the SSTV screen.

  • With two radios, an FM channel picked on the SSTV screen goes to your FM radio.

    With 2 m FM set to go to one radio and 2 m SSB to another, picking 145.800 or 144.500 MHz FM on the SSTV screen (or a frequency you set to FM there) went to the SSB radio and put it in FM. It now goes to the radio set up for 2 m FM, as the ISS auto-arm and a repeater tune do.

  • The ISS SSTV auto-arm leaves a satellite you are working alone.

    With a transponder picked on the Satellites screen, an ISS pass made the auto-arm retune to 145.800 MHz, and Doppler tuning pulled the radio straight back to your satellite. While a satellite holds the radio, the auto-arm now only tells you the ISS is up, as it does on other screens, and arms if you release the satellite while the ISS is still up. On the SSTV screen that notice says the satellite pass has the radio, instead of asking you to open SSTV.

  • RTTY's band channels now put your signal on the RTTY frequency with AFSK keying.

    Picking a channel in the RTTY cockpit, entering RTTY on a band, or picking a band for RTTY tuned the radio to the channel's frequency as if it were the signal. With AFSK (the default) the signal sits a mark tone (2.125 kHz) below the dial, so on 20 m it went out at about 14.081 MHz, among the FT4 signals, and on 17 m and 12 m among FT8's and on 15 m among JS8's. With AFSK these picks now tune a mark tone higher (14.0851 MHz on 20 m, as the channel list shows), so the signal lands on the channel's frequency, as with FSK. FSK is unchanged.

  • An unassisted contest entry now stops all CW decoding, not only the AI decoder.

    With Settings ▸ Contesting ▸ Unassisted entry on, the classic decoder still copied CW into the Decode pane, offered the calls it heard as chips and filled His Call with its best guess. CQ WW's rules count a CW decoder as QSO-finding assistance, which an unassisted entry may not use. Now neither decoder runs: no copy, call chips or His Call guess, no report or name for the log strip and no speed, and the Decode pane says why. CW speed match sends at your own speed. A call you type is still the one the F-keys send. Ending the entry brings the decoder back as you had it, with nothing from before or during the entry. Assisted entries and everyday operating are unchanged.

  • The speed beside the CW Decode pane's title no longer shows a station heard long ago.

    The classic decoder measures it, and clicking a call chip sets your keyer to it, but it stayed at the last speed measured however long ago that was, so a click could send your next over at the previous station's speed. It now shows, and a chip click now uses, only a speed from keying heard in the last 10 seconds, the rule CW speed match already had. With none, no speed is shown and a chip click leaves your keyer speed alone.

  • Clicking a spot or tuning to another frequency forgets the CW speed with the copy.

    A spot clicked within 10 seconds of the last station showed that station's speed beside the Decode pane's title, and a call chip's click set your keyer to it. The decoder now starts afresh at the new frequency: the speed shows once the new station is heard, timed from its own keying, and CW speed match times it the same way.

  • The contest-category note no longer calls your own radio's decodes exempt.

    Under "What this means for your contest category" it said your radio's own decodes are not assistance under either CQ WW's or ARRL's rules. Both count any technology that identifies a callsign or multiplier, and CQ WW names a CW decoder. The line now says what keeps feeding the Needed board in an unassisted entry, your radio's own digital decodes such as FT8 and FT4, that neither ruleset sets them apart, and not to use the board to find stations if your contest counts them.

  • In an unassisted entry the CW Copilot pane says why it is empty.

    It said "Decoded calls appear here…", but no CW is decoded then. It now shows the Decode pane's line: "Unassisted entry: the CW decoder is off. CQ WW counts it as assistance."

  • FT8 and FT4 no longer transmit on top of another program keying your radio through Nexus.

    With "Other programs may key transmit" on, a program sharing the radio through Nexus's CAT broker (WSJT-X, VarAC) could key for a transmission of its own while your FT8 or FT4 CQ or QSO was armed, and at the start of your next period Nexus sent its own over under that program's key: two signals from one transmitter. Nexus now sends nothing while the other program holds the key. Your CQ or QSO stays armed and stays where it was, and its message goes out in your first period after the program lets go. Stop TX still drops the other program's key and stops everything. JS8 and Nexus's other timed modes wait the same way.

  • Mac: an IC-7300's sound card opens again.

    macOS names that radio's USB sound card "USB Audio CODEC" with a space at the end. Nexus listed and saved the name with the space, then dropped it when opening the device, so the radio you chose never matched: there was no receive audio, the error said "USB Audio CODEC" is not available, and Nexus would not key the radio because transmit audio could not open either. Nexus now opens the device by the name exactly as saved, and ignores spaces at the ends of a name only when nothing matches exactly. Any other sound card macOS names with a space at the end is fixed the same way. Nothing to change in Settings.

  • Programs that share your radio through Nexus are no longer hung up on for asking what the radio can't tell them.

    Three such questions in a row, such as a notch, squelch or preamp reading on a radio that does not report one, closed the program's connection. That included Nexus's own connection to a TCI radio, which was dropped and reopened over and over while it read the radio's levels. Now only lines that are not rig-control commands at all count, so a web page or a port scanner writing to the CAT broker's port is still hung up on.

  • TCI (Beta): closing the connection no longer cuts off Nexus's last commands to the SDR program.

    When Nexus closed its TCI connection (changing radio, saving the connection, quitting) while the program was sending receive audio or its panadapter, the connection could end in a network reset rather than a clean close. A program that writes before it reads, or whose computer drops what it has not read when a reset comes, then never read Nexus's last commands: the transmitter's stop, the panadapter's stop, and the stop Nexus sends again when the program has not confirmed the transmitter went off. Nexus now reads on for up to 0.2 s after its close, until the program answers it, so the connection ends cleanly and the program has read everything sent before.

  • TCI (Beta): a stop can no longer wait behind an SDR program that sends or reads slowly.

    Nexus read each message from the program until it was whole, so a program sending one a byte at a time, the bytes under 20 ms apart, held Nexus in that one read. Stop, and Nexus's own checks that end an over the program is not taking Nexus's audio for or has not confirmed it ended, waited until the message was done, which could take hours. Each read now gives up after 20 ms and carries on with the message next time, so a stop and those checks come on time whatever the program sends. Connecting gives up after 3 s however slowly the program answers, rather than after minutes. Writing was the same the other way: each piece of a message to the program had 2 s, so a program reading a few bytes at a time could hold one message, such as a block of Nexus's transmit audio, and a stop behind it, for as long as it kept reading. Each message now has 2 s in all. A program that takes longer is treated as a lost connection: if Nexus was transmitting it says the radio may still be transmitting, then connects again and sends its stop first.

  • Share by TCI (Beta): a program's mode request no longer outlives its connection.

    A program's own transmit audio goes out only after that program asks for a voice mode (USB, LSB, AM or FM). A mode request that arrived just as you pressed Disconnect, or as Share by TCI stopped, could be kept after the program was gone, and once Share by TCI started again the program listed under the same Connection number counted as having asked for it, though it had asked for nothing. Nexus now lets a mode request already under way finish before it ends the program, forgets it with the program, and takes none once the program's end has begun.

  • Share by TCI (Beta): a program that takes what Nexus sends a few bytes at a time is now disconnected after 5 s.

    A program that stopped reading was already treated as gone after 5 s, and whatever it had on the air ended with it. One that still read a few bytes every few seconds was not: Nexus waited on it for as long as it kept reading, and the program stayed connected, holding any key it had. What Nexus sends a program at one time now has 5 s in all; a program that takes longer is disconnected as a lost connection, and whatever it was transmitting ends. A program that keeps up is not affected.

  • A logger can no longer turn TX back on after you stop it.

    With the WSJT-X UDP feed on, a Reply from GridTracker or JTAlert used to arm TX even after Stop TX, Esc or a TX watchdog trip, and cleared the trip. Now that Reply is ignored until you turn TX on yourself, and the watchdog trip stays until you do. A logger's free text with "send" no longer turns TX on either: as in WSJT-X, it goes out only if TX is already on. A logger's Halt TX still stops at once.

  • Remote on a Linux station: Stop's own road survives Nexus being paused.

    Stopping and continuing Nexus at a Linux station (Ctrl+Z then fg in a terminal, or a debugger) ended the station's end of Stop's road and of the audio road for good. A Stop from the second PC then had the command link alone, and presence could no longer be renewed, so what was on the air stopped within about 5 s and starts from afar were refused; the audio went quiet. The station now carries on reading both roads.

  • Remote from a second PC: working a spot there no longer turns TX on at the station.

    A CW, Phone, RTTY or PSK spot worked from the second PC opens that screen at the station too, and the station's own window turned TX on as it opened it, though nothing had been pressed to transmit. With TX on, the station's own PTT and a program keying the radio over the CAT share could transmit with nobody asking. The station's window now opens the screen and leaves TX as the second PC left it, off until you turn it on. A spot worked at the station turns TX on as it always has, and Stop TX still holds TX off everywhere.

  • Programs that listen to Nexus the way they listen to WSJT-X now see what you are transmitting.

    GridTracker, JTAlert and the like got your decodes but not your TX message, and were always told TX was off. Nexus now reports the message on the air, whether TX is enabled, the report you are sending, the station's grid and a tripped TX watchdog, as WSJT-X does, and tells them the moment one changes rather than once a period. What Nexus transmits, and when, is unchanged.

  • JS8 sends to your own groups.

    A group you added in Settings, such as @MAGNET, was refused as "not a callsign or @group JS8 can address". It now goes out the way JS8Call sends it, a message or a command alike, and a message to a group you joined is marked as yours. Compound calls such as KD4JRX/WFD can be put in the To box too. A name JS8Call cannot send to is still refused, and the message now says a group is @ and up to 8 letters or digits.

  • JS8 sends to a portable call.

    W1AW/P in the To box, typed or picked from a station heard as portable, was refused as "not a callsign or @group JS8 can address". It now goes out as JS8Call sends it, a message or a command alike: a directed frame to W1AW with JS8Call's portable flag set, the same frame byte for byte. Other suffixes are unchanged: W1AW/M, W1AW/1 or W1AW/QRP goes as a compound call, as JS8Call sends one, and a call JS8Call cannot send to is still refused.

  • FT8 and FT4: a weak reply that arrives late in the period now counts for your next over.

    Nexus now decodes at the same moments as WSJT-X. FT8's full decode runs 14.4 seconds into the period instead of after the period ends, and FT4's one decode runs at 6.05 seconds instead of at 5.5 and again at 7.5. A weak RR73 or report that only the full decode finds is then known before your next over starts, so Nexus answers it instead of sending its last message again. If that decode is still running when your over starts, its result still counts as soon as it is done. The early FT8 decode at 11.8 seconds is unchanged.

  • FT8 and FT4: each decode counts the moment it is found, as in WSJT-X.

    Nexus handed a decode pass's results to the QSO sequencer and the decode list only when the whole pass had finished. It now hands each decode on as soon as it is found, and your RX frequency is looked at first, as in WSJT-X. A weak reply on your frequency is then in the decision for your next over even on a slower computer, where it used to arrive after your over had started and the over went out again. The decodes themselves are unchanged and each still appears once, in the list, in ALL.TXT and to loggers and PSK Reporter, which now also get each one as it is found. A CQ run whose best-caller choice is strongest, farthest or CQ callers first still compares all the answers a pass brings before it picks one. The early FT8 decode at 11.8 seconds now stops at 13.4 seconds if it is still running, as WSJT-X's does, so a slow computer no longer loses that period's full decode to it.

  • The diagnostic log now says when a period's decode was dropped.

    When the decoder is still busy as a period ends, Nexus skips that period's decode, and it said so only on a console that Windows never shows. The line, with how many periods have been dropped so far, now goes to the diagnostic log too, so a computer too slow for the T/R period shows up in the log you send with a report.

  • The Log button stays on screen in the Phone, CW, JS8, RTTY and PSK screens.

    At 1280×800 the log form was taller than its pane, so Log and Spot sat below the fold. The "logs to … as" line and the Log/Spot buttons now stay together at the bottom of the log pane while the fields above them scroll. The callsign card below them is never covered.

  • The contest entry's boxes are full size in the Phone, CW, RTTY, PSK and JS8 screens.

    The Call and exchange boxes under the log showed small 14 px text. They now use the entry's large 30 px lettering and 58 px height.

  • A rotator set to a serial port that is not there now says so, once.

    On a Mac a USB serial port's name changes when the controller is plugged into a different socket or hub, so a saved port can stop existing. Nexus used to start the rotator daemon every 5 seconds anyway and fill the Connections log with "launched" and "exited" lines that never named the port. It now writes one line naming the missing port and the serial ports that are there, and starts the rotator by itself as soon as the saved port appears.

  • CW: the classic decoder copies fast stations from the first few characters.

    A station sending at about 34 WPM or faster used to be timed wrong when the decoder had not yet heard anyone, or had last heard a slow station: 40 WPM read as 14 and the copy came out as E's and I's. It now finds the speed of anyone sending 15 to 50 WPM within about six characters, also through noise and uneven hand keying, and a weighted keyer reads at its real speed. Slow and hand-sent CW copies at least as well as before.

  • Contacts held during a contest are no longer forgotten by a restart.

    While Contest mode is on, a contact logged in the Logbook waits to go to QRZ, Club Log and the other services until Contest mode is turned off. That waiting list now survives closing Nexus: after a restart the contacts still wait, and go once, a few seconds apart, when you turn Contest mode off. A contact stays on the list until it has gone, so closing Nexus part-way through sending a long contest sends the rest at the next start, and nothing twice. If Nexus cannot read the list, it keeps the file untouched, says where on screen, and the contacts stay in your Logbook.

  • The CW and Phone screens go back into the contest.

    With Contest mode on, a visit to Chat or a change of FT mode could leave the contest, and the CW and Phone log lines then showed the everyday form: no exchange boxes, no dupe check, the casual macros. Opening the CW or Phone screen now enters the contest again in S&P, as the Contest screen already does. It never starts calling CQ, and a station already in the contest keeps running or S&P.

  • Field Day and contest FT: only your caller's own RR73 closes the contact.

    In the Contest screen's Running on Field Day's messages (ARRL Field Day, Winter Field Day, and FT1, DX1 or FT2 in any contest), an RR73, RRR or 73 sent to you by another station logged your contact with the station you were working and went back to CQ before that station had confirmed; its own RR73 then got no 73. Now, as in WSJT-X, another station's confirmation is ignored: nothing is logged or sent to it, and your caller keeps getting your R and exchange until its own RR73 logs the contact, with your 73 in ARRL Field Day on FT8 and FT4 as before. The ARRL VHF contests and the contests with the standard messages already worked this way.

  • Field Day S&P: only the station you called completes the contact.

    In the Contest screen's S&P on Field Day's messages (ARRL Field Day, Winter Field Day, and FT1, DX1 or FT2 in any contest), once you had answered a station's CQ, a rogered exchange sent to you by a different station logged that station and sent it your RR73, and the station you had called then never got its RR73 or a place in your log. Now, as in WSJT-X, that exchange is ignored: nothing is logged or sent to it, and your exchange keeps going to the station you called until its own rogered exchange logs the contact and gets your RR73. The ARRL VHF contests and the contests with the standard messages already worked this way.

  • Field Day: a station signing W9XYZ/M is logged as W9XYZ/M, not <W9XYZ/M>.

    In the Contest screen on Field Day's messages (ARRL Field Day, Winter Field Day, and FT1, DX1 or FT2 in any contest), a station whose call ends in a suffix such as /M, /4 or /QRP sends its exchange with its call in angle brackets, and a contact with it went into your contest log that way: in the ADIF and Cabrillo files you export, and in the dupe check, so S&P answered that station's next CQ and worked it again. The call is now logged without the brackets, as the ARRL VHF contests and the contests with the standard messages already log it and as WSJT-X does, so that station's next CQ is a dupe like any other. What you send on the air during the contact is unchanged.

  • Field Day: your RR73 and 73 to a station signing W9XYZ/M are the ones WSJT-X sends.

    In the Contest screen on Field Day's messages, closing a contact with a station whose call has a suffix such as /M, /4 or /QRP, or a prefix such as PJ4/, sent <W9XYZ/M> K1ABC RR73, a different message from the one WSJT-X sends. Nexus now sends WSJT-X's, W9XYZ/M <K1ABC> RR73 and W9XYZ/M <K1ABC> 73: that station's call in full and yours in angle brackets, the same message bit for bit. Your exchange and your roger to that station are unchanged, and so is everything when your own call has a suffix or a prefix.

  • Field Day: when you run, a station signing W9XYZ/M can now close the contact.

    In the Contest screen on Field Day's messages, a station whose call has a suffix such as /M, /4 or /QRP and runs WSJT-X sends its RR73 or 73 with your call in angle brackets and its own in full, <K1ABC> W9XYZ/M RR73. Your run did not take that as sent to you: it sent the station your roger and exchange again, and the contact was never logged. It now takes it as WSJT-X does, logs the station as W9XYZ/M and, in ARRL Field Day on FT8 and FT4, answers with WSJT-X's 73 before calling CQ again.

  • Field Day: a call shown as <...> is no longer answered or logged.

    In the Contest screen on Field Day's messages, a station whose call has a suffix or a prefix shows as <...> until Nexus has heard that call in full. When you ran, Nexus answered such a caller's exchange, addressed to <...>, and logged the contact with the call ...; in S&P it answered a CQ from <...>. Nexus now passes such a message by, as WSJT-X does in Field Day. Once the station has sent its call in full (in a CQ, for example), its next message is worked as usual.

  • ARRL VHF contests and contests with the standard messages: your 73 to a station signing W9XYZ/M no longer goes out with another station's call.

    In the Contest screen, closing a contact with a station whose call has a suffix such as /M, /4 or /QRP, or a prefix such as PJ4/, your 73 read W9XYZ/M K1ABC 73, which goes on the air as W9XYZ K1ABC 73: the call without its suffix, which is a different station. In the contests with the standard messages your RR73 to such a station read <W9XYZ/M> K1ABC RR73, a different message from the one WSJT-X sends. Nexus now sends WSJT-X's, W9XYZ/M <K1ABC> 73 and W9XYZ/M <K1ABC> RR73, the same message bit for bit, as it already does in Field Day. Your grid, report and roger are unchanged, and so is everything when your own call has a suffix or a prefix.

  • Contests: double-clicking a CQ from <...> no longer answers it.

    With the contest switch on, a station whose call has a suffix or a prefix can show as <...> until Nexus has decoded its call in full. Double-clicking its CQ, or a logger's Reply to it, switched to the contest's S&P, turned TX on, moved RX and TX onto the station and sent your exchange or grid to <...>, a call no one could read. It now does none of that and says why, as WSJT-X answers no <...>. Once the station's call shows in full, a double-click works it as usual.

  • FT8/FT4: your RR73 and 73 to a station signing W9XYZ/M are the ones WSJT-X sends.

    Outside a contest, closing a contact with a station whose call has a suffix such as /M, /4 or /QRP, or a prefix such as PJ4/, sent <W9XYZ/M> K1ABC RR73 and <W9XYZ/M> K1ABC 73: the right two calls, but a different message from the one WSJT-X sends. Nexus now sends WSJT-X's, W9XYZ/M <K1ABC> RR73 (or W9XYZ/M <K1ABC> RRR when you prefer RRR) and W9XYZ/M <K1ABC> 73: that station's call in full and yours in angle brackets, the same message bit for bit, and the Tx panel's Tx4 and Tx5 show them that way. This holds when your own call ends in /P or /R too. Your grid, report and roger are unchanged, and so is everything when your own call has another suffix or a prefix.

  • ARRL VHF contests and contests with the standard messages: S&P no longer answers a CQ from <...>.

    With TX on in the Contest screen's S&P, a station whose call has a suffix or a prefix can show as CQ TEST <...> EN37 until Nexus has decoded its call in full. S&P answered that CQ, sending your grid to <...>, a call no one could read. It now passes such a CQ by, as Field Day's S&P already did and as WSJT-X answers no <...>, and answers the station's next CQ once its call shows.

  • FT8/FT4: double-clicking a CQ from <...> no longer answers it outside a contest either.

    A station whose call has a suffix or a prefix can show as <...> until Nexus has decoded its call in full. Double-clicking its CQ with the contest switch off, or a logger's Reply to it, turned TX on, moved RX and TX onto the station and sent your grid to <...>, a call no one could read. It now does none of that and says why, as it already did with the contest switch on and as WSJT-X answers no <...>. Once the station's call shows in full, a double-click works it as usual.

  • Contests with the standard messages: when you run, a station signing W9XYZ/M that runs WSJT-X now gets an answer.

    Such a station calls you with your call in angle brackets, its own in full and no grid, <K1ABC> W9XYZ/M. Your run did not answer it and kept calling CQ, unless that station had Skip Tx1 on. It now answers with your report, <W9XYZ/M> K1ABC -12, as WSJT-X does, and the contact goes on as usual and is logged as W9XYZ/M, with no grid. A first call from <...>, or one where both calls have a suffix or a prefix, is still not answered; the ARRL VHF contests and Field Day are unchanged.

  • FT8/FT4: a caller shown as <...> is no longer answered.

    A station whose call has a suffix or a prefix can show as <...> until Nexus has decoded its call in full. When you called CQ, outside a contest or Running in an ARRL VHF contest or a contest with the standard messages, and such a station called you with its grid or its report, Nexus answered it, sending your report or roger to <...>, a call no one could read; a best-caller choice could even pick it over a station whose call shows. Double-clicking any other message from <...>, a logger's Reply to one, or clicking <...> in a list started a contact with <...> too. Nexus now passes such a caller by and answers the next station that called you in the same period, or calls CQ again; a click on <...> changes nothing and says why. WSJT-X answers no <...>. Once the station's call shows in full, it is answered and worked as usual. Field Day already passed such a caller by.

  • FT8/FT4: typing 73 to a station signing W9XYZ/M no longer sends it to W9XYZ.

    In a contact with a station whose call has a suffix such as /M or /QRP, a prefix such as PJ4/, or a shape such as YW18FIFA, the free text you type for the next message (73, RR73, RRR or a report) went out as W9XYZ/M K1ABC 73, which goes on the air as W9XYZ K1ABC 73: another station's call (with YW18FIFA, a cut-off YW18FIFA K1AB). The same happened to your own call when it has a suffix or a prefix. Nexus now sends the message WSJT-X sends for the two calls, such as W9XYZ/M <K1ABC> 73 (your call in angle brackets) or <W9XYZ> K1ABC/QRP 73, the same message bit for bit and the same one Nexus's own 73 is. Other free text, and contacts where both calls are plain or both have a suffix or a prefix, go out as before.

  • FT8/FT4: clicking the Tx3 row sends what the row shows.

    With your call ending in /P or /R and a station signing W9XYZ/M or PJ4/W9XYZ, no report can ride your roger, so the Tx panel's Tx3 shows <W9XYZ/M> K1ABC/P RRR. Clicked, it went out as W9XYZ/M <K1ABC/P> RRR, the Tx4 message. It now goes out as the row shows it, as WSJT-X sends what its Tx3 box holds; the automatic sequence already sent it that way.

  • FT8/FT4: free text that FT8 cannot send no longer keys a steady tone.

    Nexus puts both calls in front of the free text you type for the next message, so TNX 73 becomes W9XYZ K1ABC TNX 73: a message FT8's encoder cannot build. Nexus transmitted it anyway: on FT8, one steady tone for 13 seconds; on FT4 nothing went out, though Band Activity and ALL.TXT showed it sent. With a station signing W9XYZ/M, TNX went out as a message naming nobody (<...>). Now such a message is never transmitted, whether it comes from the free-text box, a Tx row (Tx 5 as typed or filled from a macro), a click during an over, the contest screen or Remote, and Nexus says why: after two calls only a report, R-report, RRR, RR73 or 73 fits, and free text on its own, as in Tx 5, holds 13 characters. The message you had queued stays queued. Text FT8 can send goes out as before.

  • WSJT-X UDP: a Replay no longer marks old decodes as new.

    When a logger such as JTAlert or GridTracker asks Nexus to replay the decodes, Nexus sent them marked New, as if just heard, so a program could alert on them again. They now go out marked not new, as WSJT-X sends them. Decodes as they are heard are still New.

  • Nexus names itself to QRZ.

    QRZ asks every program that talks to it to say what it is, and may limit one that does not. Callbook lookups and Logbook uploads now say Nexus/ and the version you run. Your callsign is not sent in it.

  • Esc stops transmitting in the contest's pop-out windows.

    With the contest entry, the Contest screen, a scoreboard or a band map in a window of its own, Esc there did nothing to a CW message or a voice message on the air; it only cleared the entry. Esc in any of those windows now stops transmitting, the same as Esc on the main window, and still clears the entry.

  • CW: Esc (Stop TX) ends a CW message sooner.

    A WinKeyer, the serial keyline and the soundcard keyer now stop before Nexus asks the radio to stop its own CW, so a slow radio no longer holds them keying. A word the serial keyline had not started yet is dropped instead of being sent after the stop. On an FT-710 or FTX-1 keyed over CAT, the stop now also sends Yaesu's own playback stop, so the rest of the word is cut off.

  • CW: on a radio that cannot be stopped mid-word, Esc leaves at most the word being sent.

    On a Flex over SmartSDR CAT, and on Yaesu radios keyed over CAT that have no CW stop (FT-991A, FTDX10 and others), Nexus hands the radio one word at a time, timed at the speed it keys. With a Flex on SmartSDR CAT, the CW settings suggest SmartSDR CAT's WinKeyer port or the Flex native client, which both stop mid-word.

  • CW: on those same radios, Nexus's CW speed wins.

    Nexus sends its speed to the radio at the start of every message, so a speed turned on the radio (SmartSDR, a Maestro, the front panel) lasts only until your next message, and Nexus's CW speed control is never changed by it. Words can no longer pile up behind a slower radio and keep sending after Esc.

  • Remote: Operate from this computer now works at an address you type.

    When nothing answers where a paired station was, Stations on this network asks where it is now. That box offered only Stream; it now offers Operate at this address first, with Stream still beside it. Nexus checks it is the same paired station there, as it does everywhere, and keeps trying that address while you operate, so it can move back to your network on its own. You can also type the station computer's name, like shack-pc.local. Nexus looks the name up each time it tries it, so it still works after the station gets a new address, and says so plainly when no computer answers to the name. Once Operate opens at what you typed, Nexus remembers it with that station and tries it first next time. The station's row shows it, with Change and Clear; Forget removes it with the pairing.

  • Remote: logging-service keys stay at the station.

    A computer driving the station no longer receives the logging-service keys kept in the station's settings: Settings there shows only whether one is saved at the station, and a save from it can no longer change, clear or replace one. When a logging service refuses an upload or a download and repeats the key or password it was sent, Nexus now hides it from the message, on every screen. Through a browser stream of the station's window, logging-service passwords and keys can no longer be saved, forgotten or edited; do that at the station itself. At the station, the logging-service key shown in Settings now appears as dots until you press Reveal. While a browser stream is showing the station's window, the key is hidden, even if you revealed it before the stream began, and Reveal is unavailable until the stream ends.

  • Remote: the addresses Nexus sends your logging-service keys to can only be changed at the station.

    A settings save from a computer driving the station no longer changes the Cloudlog/Wavelog URL, the club host a Field Day position joins, or an Icom network radio's address and port, so it cannot send the station's stored Cloudlog key, club key or radio password to another server. The rest of the save, user names included, still applies. Every other service Nexus signs in to (QRZ, LoTW, eQSL, Club Log, HRDLog, HamQTH, World Radio League, Winlink, RepeaterBook) already uses a fixed address.

  • PstRotatorAz: "localhost" as its address now works like 127.0.0.1.

    Windows looks "localhost" up as the IPv6 address first, so Nexus listened for PstRotatorAz's replies there while PstRotatorAz answered on IPv4, and the compass showed no position. Nexus now takes the IPv4 address when a name has one.

  • Test CAT reports its own test.

    A dial message that appeared while Test CAT was waiting, such as "rig set to …" or a frequency read outside the radio's range, could be shown as the test's result. Test CAT now waits for its own probe and reports that probe's line.

  • Nexus Remote from a second PC: a voice-keyer message now stops when that PC's permission to transmit is withdrawn.

    Every other transmission started from the second PC already ended then; a voice message already playing kept going to its end. Stop TX and the second PC going away already stopped it.

  • Remote: transmit safety settings are set at the station only.

    A settings save from a computer driving the station no longer changes what lets the station transmit with nobody pressing a key (the WSJT-X UDP control, the CAT broker's PTT, JS8's API, the Remote stream, a CQ run's restart after its pause) or what guards a transmission (the TX watchdog, JS8's idle watchdog, the tune limit, the high-SWR cutoff, the power ceilings, the CQ, reply and retry limits, "Disable Tx after 73", Parsec presence stop, the licence class, and the PTT method, port and serial lines). Each keeps the station's value, and the licence class can no longer be set from afar. The station's own Settings window changes them as before.

  • Security: settings that name a program Nexus runs can only be changed at the station.

    The TQSL path, the program the station runs to sign a LoTW upload, could be changed by a settings save from a computer driving the station from afar, so that computer could point it at any program on the station. A save from afar now keeps the station's own TQSL path; it is set in Settings at the station. It is the only setting that names a program.

  • Contest entry: a dupe is now plain to see.

    Typing a call already in this contest's log (by the contest's own dupe rule) puts a red DUPE badge on the Call box with when and where you worked them, for example "DUPE 14:32 20m CW", and colours the box. Before, the only sign was a small grey line under the boxes. It shows in the cockpit's entry strip and in the contest logger window, and a screen reader announces it. Pressing Enter on a dupe still logs it, marked as a dupe that scores nothing, as every contest Nexus scores asks; the message now says "as a DUPE" instead of looking like any other contact. With Enter Sends Message on, a dupe still never gets your exchange: in Run it gets QSO B4, once, and in S&P nothing is sent.

  • CW: the power, ALC and SWR meters now track while the radio sends CW, as they do in SSB.

    When the radio's own keyer, a WinKeyer or the serial keyline sent the CW, Nexus did not read the transmit meters at all (unless the radio happened to report itself keyed), and the meter strip showed the last word of every send, and any one-word send, as off the air. The meters are now read for every word Nexus sends, on every keyer, and blank when it ends or Stop TX cuts it. The high-SWR cutoff, if switched on, now also sees the last word. The 150 ms meter cadence is unchanged.

  • CW now owns the transmitter until its last word ends.

    Nexus counted CW as transmitting only while words were still waiting to go, so during the last word of every send (and all of a one-word send, such as the CW ID after an FT 73) another program's PTT over the CAT broker, the radio's ATU tune-up, a voice message on a Flex, an RTTY, PSK, SSTV or APRS over, or a Remote start could key on top of it. Each now waits or is refused with "CW is sending" until the word ends. Stop TX and TX Off end it at once, and the word's own length (plus a quarter second) is a hard end, so a missed end can never hold the transmitter.

  • Tune, Phone PTT, the voice keyer and FT overs no longer key on top of CW.

    These never asked whether CW was sending, so a Tune or a PTT press during a CW send, a voice-keyer message (on every radio but a Flex with the radio holding the mic), or an FT slot that came due during the CW ID after a 73, keyed over the CW word. Tune, PTT and the voice keyer now stay off while CW is sending (the status, and the keyer's message, read "CW is sending — stop it first"); a voice message queued just before CW started is dropped, not played later. Stopping a tune, letting go of PTT and stopping a voice message always work, and Stop TX still ends everything at once. An FT slot that starts while CW is sending is skipped, as one is while tuning: the QSO stays where it was and the next free slot sends the same message.

  • IC-7300, IC-705, IC-905 and IC-7300MK2: scope span, reference level and Center/Fixed now work.

    With Native Icom CI-V on, these radios refused every scope span button ("SCOPE SPAN REFUSED … did not answer when asked whether its scope is in Center mode"), and the reference level and Center/Fixed controls did nothing, whatever the scope was set to. Nexus left one byte out of those commands that Icom's own command tables show for these models. The IC-9700, IC-7610 and IC-7760 send exactly what they sent before.

  • Contest contacts no longer upload to QRZ, ClubLog and the other logging services while the contest runs.

    With contest mode on, a contact logged anywhere but the contest entry strip (the everyday log form, the Logbook, a screen that had left the contest) went to every logging service the moment it was logged. It now waits: the contest's contacts go out when you merge the contest log into your Logbook, as designed, and any other contact logged while contest mode was on goes out, paced, when you turn contest mode off. LoTW's automatic upload waits for the end of the contest too.

  • Nexus Remote: updating the second PC no longer locks you out of the shack without warning.

    While the PC is operating a shack, its update notice no longer offers a plain Install. It says which version is waiting and which version the shack runs, and that installing here now ends remote operation until the shack runs the same version. Update the shack first, or both together. Install anyway works only once you tick the warning, and after Leave the update installs as usual. When the shack does refuse a different version, the banner now names both versions and says which side to update.

  • FT-1000 and FT-1000D owners: clicking a spot tunes the radio.

    With neither radio in the rig list, the nearest choice was the FT-1000MP, and its driver reads these radios' frequency in the wrong format. Nexus sent the spot's frequency, read back a wrong one and followed it, so the dial never settled on the spot. Choose FT-1000 or FT-1000D in your radio settings instead of FT-1000MP. An FT-1000MP itself was not affected.

  • Fetch LoTW works on a large account the first time.

    The first download (and the one after Download everything again) asked LoTW for every confirmation at once, which LoTW could not finish on a big account: it answered "503", and every retry asked for everything again. Nexus now asks a year of contacts at a time, newest first, and keeps each year as it arrives; the Connections log shows "piece n of m". If LoTW stops answering, Nexus says which year it reached and the next Fetch LoTW continues from there. Later downloads still ask only for what is new.

  • Nexus Remote: the shack's screen fits the browser window.

    Ctrl (⌘ on a Mac) with +, − or 0, Ctrl with the scroll wheel and a trackpad pinch now zoom the browser page instead of going to the shack, and on a short or zoomed window the controls move to the side rail when that shows the shack's screen larger. Stop TX stays in view at every size.

  • Nexus Remote: a stream that "Still there?" ended no longer keeps the page connected.

    The page now sleeps as a hidden tab does, after Stop has finished with this browser, and Start reconnects it.

  • Phone screen: a refused ATT, PRE or monitor-level change says what failed.

    When the radio does not take one of these, the message now reads "Nexus could not set ATT.", "Nexus could not set PRE." or "Nexus could not set the monitor level." instead of a Remote sentence about station control permission.

  • Nexus Remote: the shack's Nexus window takes the shape of the browser showing it.

    A full-screen browser of a different shape from the shack's monitor showed the shack's screen with wide empty bands round it. While a browser streams, the shack's Nexus window now takes the shape of the browser's picture area, as large as the shack monitor's work area allows, on the monitor it is already on, and goes back to its own size, place and maximized or full-screen state when the stream ends, however it ends.

  • Nexus Remote: pairing a station while a trial already runs under another sign-in says so at the shack.

    It used to say access was denied. It now says the email address already has a trial under a different sign-in (Google instead of a password, for example) and that signing in the first way, then pairing again, adds the station.

  • Icom network connection: the SWR reading no longer shows "SWR?".

    On the "Icom network (LAN / Wi-Fi)" connection (IC-7610, IC-9700, IC-705, IC-905, IC-7760, IC-7300MK2) the SWR figure comes through the same calibrated scale as an Icom on USB with Native Icom CI-V, so it now reads as a trusted number and the high-SWR cutoff can be turned on. An IC-7300MK2 on USB still shows "SWR?": Nexus drives it through Hamlib there, not through its own CI-V scale.

  • FT screen: the transmit meters no longer stretch and shrink at the start of an over.

    The meters beside the Tx messages used to appear one at a time as the radio reported them, so SWR alone spread across the whole space and then shrank as ALC, power and compression arrived. From the moment the radio keys, SWR, ALC, PO and COMP now each have their own place at a fixed width, empty until their reading comes in. A meter the radio does not report is marked unavailable once the over ends, not a fraction of a second after it starts.

  • CAT: a frequency the radio cannot be on is no longer taken as a tune, or sent back to the radio.

    With the wrong rig model picked (the FT-1000MP driver on an FT-1000D, for one), or a garbled reply, the radio could be read as sitting on 115.2 MHz while its own driver says it covers 0.1–30 MHz. Nexus took that as a turn of the knob, moved its dial there, and sent 115.2 MHz back to the radio on the next mode change. Now a reading outside the radio's own receive range is ignored, the dial stays where it was (Remote shows the same dial), and the CAT status says once what the radio reported and suggests checking the rig model in Settings → Radio. A radio whose range Nexus cannot read is followed exactly as before.

  • Elecraft KPA1500 set to 57600, 115200 or 230400 baud now connects.

    Nexus tried only the KPA500's four speeds (4800 to 38400), so a KPA1500 set to one of its three faster ones showed "Not answering" even when it was cabled correctly. All seven speeds Elecraft documents are now tried. A KPA500 is asked at its four speeds first, in the same order as before.

  • RTTY screen: a click on the waterfall no longer moves your transmit tones during an over.

    Netting moves the AFSK transmit tones as well as the decoder, so a click while transmitting slid the signal you were sending to wherever you clicked. While an over is on the air or queued, continuous TX is on or Tune is keyed, a click now does nothing, and the waterfall's hint says tuning is held.

  • Nexus Remote: a PC that signs in while the shack reads its device list keeps its 30-day limit (Beta).

    A PC added by signing in, and not paired again with a code, now always leaves the station's network 30 days after its last sign-in, and removing it on the Nexus Remote web page always takes it off. Before, four things changed the shack's list of PCs added by signing in (a PC signing in on the station's network, each device list the shack hears from Nexus Remote, a PC paired again with a code, and a PC leaving after its 30 days), and two at the same moment could lose one change. At worst a PC that had just signed in stayed on the station's network with no 30-day limit, and removing it on the web page did not take it off. The shack now makes these changes one at a time.

  • Nexus Remote: the second PC shows its own key, so you can check it before you approve it at the shack.

    When the internet road waits for Approve at the shack, the shack asks "Let … operate this station?" and says to approve only if the key matches the one Nexus shows on that computer, but the second PC showed no key of its own. Stations on this network now shows This computer's key for the internet road on that station's row, and the line after Sign in shows it too while the road waits for Approve, in the same eight groups of four as the shack. The station's own key there is now written in capitals, as the shack writes it.

  • Stations on this network: after pairing, the line names the button that is there.

    It said to press Stream, but a paired station's row leads with Operate from this computer. The line now says to press that.

  • The built-in guide's Remote access section matches Remote as it is now.

    It still called Remote an early pilot on a test service, and described the Remote page's own FT8/FT4 controls and Log QSO form, which the page no longer has. It now says that a browser streaming the station needs only station controls, and that the logging and FT8/FT4 transmit permissions under Advanced are not used by the Remote page any more.

  • Native Icom CI-V: closing the connection always tells the radio to stop transmitting.

    When Nexus closes its own CI-V connection to an Icom (CAT restarting, a radio switch, Nexus closing), on USB or over the Icom network connection, it first sends the radio its transmit-off command and waits for it to go through. If the radio had stopped answering, with commands piled up ahead of that one, the wait ran out (1.3 s on USB, 4.1 s on the network connection) and the connection closed without the command ever being sent, so a radio that was transmitting stayed on the air. The transmit-off command is now always sent once as the connection closes, and nothing else is sent then.

  • CW sent through the radio's own keyer no longer passes a ; to Kenwood, Yaesu and Elecraft radios, where it would be read as a radio command.

    With the CAT keyer (Settings ▸ CW ▸ Keyer backend: CAT), a word holding a ;, a control character or a character Nexus has no Morse for (an apostrophe, ", an accented letter) is no longer handed to the radio on any radio: the CW screen says which character, the whole message is refused before anything keys, and Enter Sends Message logs nothing. Typed CW, F-key macros, Enter Sends Message and CW sent from a computer driving the station all keep to this, by the same rule that TCI programs' CW already kept. A callbook name or state that {HISNAME} and {HISSTATE} key keeps only the characters the keyer can send, so the rest of it still goes out. The WinKeyer, the serial key line and the soundcard keyer key exactly as before.

  • Turning off Remote over this network takes effect at once, however slow the disk.

    Turning it off in Settings ▸ Station ▸ Remote access, or pressing End remote control, saved the setting before it closed the station's port, ended the other computers' sessions and took back their control of the station. While the disk was busy, or something held the settings file open, those computers stayed connected and anything they had on the air kept going until the save finished. Now the port closes and the sessions end first, and the setting is saved after.

  • Nexus Remote: Save to this computer never replaces a file already in the second PC's Downloads folder.

    A station file whose name is taken there, such as ALL.TXT saved a second time, is saved as ALL (1).TXT, then ALL (2).TXT, the way a browser names a download, and the file that was there keeps every byte. The message after the save names the file it went to.

Security

  • Nexus Remote: a config profile saved from a computer driving the station no longer carries the settings set at the station only.

    Profiles are kept at the station, and loading one there applies what it holds. A profile saved from a computer driving the station now keeps the transmit limits and safety stops, the switches that let other programs or a browser transmit, the PTT method, port and lines, the TQSL path and the addresses your logging-service keys are sent to as the station's own profile of that name has them, and a new one carries none of them, so loading it keeps the station's own. Profiles saved at the station, and loading them there, are unchanged.

  • Nexus Remote: a saved profile sent from a computer driving the station that the station cannot read in full is refused.

    Nothing of that save is written, so a profile saved there can never change the settings that are set at the station only. If the station's own saved profiles cannot be read in full, they are not sent to that computer, so no logging-service key saved in a profile leaves the station, and a save from that computer leaves them as they are.

  • Nexus Remote: the CW and RTTY keying lines and the Flex client's Beta are set at the station only.

    A settings save from a computer driving the station now keeps the station's CW keyer backend, its keyline serial port and line and the WinKeyer port, the RTTY keying backend with the FSK serial port and line, and each radio's Let Nexus send CW, Tune and ATU through the native Flex client switch. On that computer they are greyed out and say "Set at the station", with the station's own value. The station's own Settings window changes them as before.

  • The certificate checks behind Nexus's downloads no longer trust the distrusted emSign certificates.

    Nexus's HTTPS (propagation data, maps, the update check and the other downloads) now uses the releases of its certificate libraries that drop the emSign certificates whose private keys were exposed (RUSTSEC-2026-0381, 0382 and 0383, published 20 October 2026). Nothing to do on your side.

  • The in-app updater no longer carries the zip library

    , which three new advisories (RUSTSEC-2026-0367, -0368 and -0369) cover. Nexus's updates are installers, not zip files, so the advisories' code was never used; it is now not built in at all.

  • The radio-sharing ports now cap how much Nexus reads for one command.

    When Nexus shares a radio with other programs over the Hamlib rigctld text protocol — the CAT broker and the SDR-program daemons — a single local connection that sent one over-long command, or a stream that was never a complete command, could make Nexus hold it in memory without limit. Every such port now bounds the length of one command line and ends a connection that runs past it; nothing in an over-long line reaches the radio, and ordinary sharing clients, whose commands are short, are unaffected. These ports are reachable only from this computer, as they have always been.

  • The PstRotatorAz link's rotator port now caps how much it reads for one command.

    With the rotator set to PstRotatorAz, Nexus answers rotator commands on this computer in the Hamlib rotctld text protocol, which its Rotor pane and other rotator programs use. A single local connection that sent one over-long command, or a stream that was never a complete command, could make Nexus hold it in memory without limit. The port now bounds the length of one command line and ends a connection that runs past it; nothing in an over-long line reaches the rotator, and rotator programs, whose commands are short, are unaffected. The link is new since 1.19.0, so no earlier release is affected, and the port is reachable only from this computer.

  • The PstRotatorAz link's rotator port now hangs up on a web page.

    A page open in a browser on this computer can send a request to the port Nexus answers rotator commands on. Nothing in such a request moved the antenna, but only because of where a browser's request happens to put a blank line. The port now ends the connection at the request's first line and answers it nothing, as the radio-sharing port does; rotator programs are unaffected.

Every version