Nexus 1.16.0
Released 3 October 2026. The current release is 1.24.0. Download it · Every version
Added
-
Layouts for Conditions, one tap away.
Layout in the Conditions header, and the top of ⊞ Panels, offers ready-made arrangements: Standard (every pane in its usual place at the usual widths, as Connect opened in 1.15), Frame + bar (the new default: Bands for you over Openings on the left, Chase over Getting Out on the right, a full-height map between them, and across the top a bar with your callsign and grid, a big UTC clock, your local time and the day's indices), Map first, List first, Dashboard and Frame. In Frame + bar every other box is one click away as a tab behind those four. The picker says which layout is on screen, or Custom once you move or resize something, and Undo last change puts back what a pick replaced, column widths included. Frame also ticks Satellites on the map so a wall display shows the birds moving; untick it and it stays off. Each window keeps its own layout, the dashboard window and the TV page have the same picker, and the map's own choices (globe or flat, layers, colours) are left alone.
-
Bands for you: the band advice as tiles.
A new Conditions box shows one tile per band, big enough to read from across the desk, 160 m up to 6 m in band-stack order, plus 4 m and 2 m when there is an opening there. Each tile gives the band and its word, with the same word and colour as the map's Band conditions list and the band menu: Open in green with a solid outline, Marginal in amber with a dashed outline, Closed with no colour and dimmer letters. A dot shows what you are hearing now, ★ marks the Band Advisor's best band, a ring marks the band your radio is on, and on 6 m, 4 m and 2 m the mode of an opening is named (Es, Tropo, Aurora, F2, MS). Hover a tile for who hears you, the best direction and when the band is expected to open or close next; click it to show that band on the map. With no fresh data the tiles are hollow and grey, never green. The box takes the Band Advisor's place in the Standard layout and on the TV page, and the Band Advisor's ranked list is one pick away in the box's menu.
-
Conditions' pop-out is a dashboard window.
⧉ Pop out opens a large window, 1600 × 1000 or your whole screen if it is smaller, showing Conditions' full layout instead of the narrow stacked one. A bar across its top shows your callsign and grid, a big UTC clock beside your local time, and the day's SFI, Kp, sunspot number, A, X-ray and solar-wind speed. With no live data each number is a dash, and old data says how old it is. Kp, X-ray and the wind turn amber when the Space Wx gauges reach their warning level (Kp 4 and up, an M or X flare, a wind of 600 km/s or more); in the light theme the number stays dark with an amber underline. Close the window and it comes back on the same monitor, in the same place and at the same size, or in the middle of your main screen if that monitor is gone. On Windows its Stay behind button keeps it behind your other windows even when you click on it, so it can fill a screen behind Nexus without covering the cockpit; until you click back into Nexus the keyboard is the dashboard's, so Esc stops nothing then, and the Stop TX button always works. The TV page has the same bar.
-
A dashboard rail beside the cockpits.
Tick Dashboard rail in a cockpit's ⊞ Panels menu, or press Dashboard at the right end of the NOW bar, and a column of Conditions boxes stands at the right of the cockpit: the Clock, Bands for you, Space Wx and Getting Out, so the time, the bands and who hears you stay in view while you operate. It is off until you turn it on, and Operate, Phone, CW, RTTY, PSK, SSTV, APRS and JS8 each remember their own choice. Any Conditions box can take a place in the rail, each with its own text size, and the rail's width and the split between two boxes can be dragged or moved from the keyboard. The rail appears only on a large window (about 1600 px wide at your zoom, which includes a 1366×768 laptop at its usual 85 %), and the cockpit beside it is never narrower than it is on a 1024×768 screen. Clicking a station in the rail never changes the station your cockpit is working, a spot or HUNT in the rail moves the radio as it does on Conditions, and the rail has no transmit control.
-
A Spots box and a POTA / SOTA box.
Pick Spots or POTA / SOTA from any Conditions box's menu. Spots lists every spot on the air with the Spots screen's search and Filter chips (Heard on my continent and Hide worked start on, as they do there). POTA / SOTA lists the activators on the air with the POTA, SOTA and Both tabs, Hide worked today, Refresh and HUNT, and its band, mode and sort choices on its Filter button. A click on a spot, or on HUNT, moves the radio to the station and opens the right screen, from the main window and from the dashboard window alike. Nothing transmits. Each box keeps its own filters, so a chip in a box never changes the Spots or POTA / SOTA screen. A narrow box shows fewer columns, and the list scrolls inside the box. The TV page shows no spot list, and each box says so there.
-
Several panes in one slot, as tabs.
A pane's ⋯ menu has Add a tab: pick a pane and it joins that slot, and the slot's title becomes a row of tabs. Click a tab to switch, or use the arrow keys, Home and End on it; ⋯ ▸ Remove … from this slot takes a pane out. A pane is only ever in one slot, so adding one from another slot moves it, and each slot reopens on the tab it was showing. In the dashboard window and on the TV page, ⋯ ▸ Rotate the tabs shows a slot's tabs one after another, every 10 s to 2 min, and waits while the mouse or the keyboard is in the slot; the main window never rotates. The ready-made layouts are one pane per slot: picking one, or Reset layout, takes the tabs away, and Undo brings them back.
-
A text size for each pane, and its page in the manual.
Every Conditions pane has a ⋯ button beside its ✕. Its A+ Larger text and A− Smaller text step that pane's words from 80% to 160% of your Text size, 10% a press; the pane keeps its place and its size, and scrolls if its text no longer fits. Each pane keeps its own size in each window, a picked layout keeps the sizes, and Reset layout puts every pane back at 100%. The same menu names the pane in the manual, such as ? Space Wx in the manual, and opens that part of the Nexus manual in your browser.
-
A Clock box.
Pick Clock from any Conditions box's menu: UTC in large digits with your computer's local time under it, today's date, your grid, and today's sunrise and sunset there in UTC (point at that line for the times on your own clock). The digits grow with the box, so a wide box reads from across the room. Where the Sun stays up or down all day it says so, and with no grid in Settings it asks for one instead of guessing a place. It needs no network, so it keeps time when every feed is down.
-
Space Wx shows the sunspot number, the solar-wind speed and 30-day trends.
Beside Bz, the Space Wx box shows the solar wind's speed in km/s, in the warning colour from 600 km/s, the speed at which the Insights feed says a fast stream is arriving. Under the gauges, which now sit two to a row, are two lines for the last 30 days from NOAA's daily solar indices, the solar flux and the sunspot number, each with its newest value and the day it is from. When the newest day in NOAA's file is three or more days old the box says so; if the file has never arrived it says the trend is unavailable rather than drawing a line, and a day NOAA has no value for is a gap in the line, not a drop to zero. The TV page shows the same.
-
Getting Out lists everyone who hears you.
The Getting Out box lists every station that has decoded you in the last half hour, not only the first six, most distant first: the call, the direction and distance, the band, the SNR they heard you at and how long ago. The list scrolls inside the box, and a click still shows the station on the map.
-
The sun and the moon on the map.
The map and the 3-D globe show the sun where it is overhead all the time, not only during a solar flare, and the moon where it is overhead, as much lit as the real one and on the side you see lit from where you are. Both move once a minute, with the greyline, and on the Globe view each is hidden while it is on the far side of the planet. A new Sun and moon layer in the Layers menu turns them off. During an M-class flare the flare layer's own animated sun takes the sun's place, so there is only ever one sun on the map.
-
Ten ready-made themes, and a System theme.
Settings ▸ Appearance ▸ Theme shows Light, Dark and System, which follows your computer's light or dark setting and changes when it does, as three cards with a line on each one's character. Below them are ten more, each with its name, a line on its character and a swatch of its colours. Rig looks: Amber LCD (black chassis, amber digits), Green LCD, Blue VFD and Silver chassis. Modern: Midnight (true black, for OLED screens and dark rooms), Slate, Lagoon, Ember, Nebula and Paper (a warm cream page). Silver chassis and Paper are light themes and the rest are dark. Every one is checked for contrast in every mode: the scopes and meters stay dark, and the transmit red, the ON AIR sign, alerts, and the signal and Needed colours are the same in every theme. A waterfall or scope on the Auto palette takes the theme's own palette (Amber CRT on Amber LCD, SDR Green on Green LCD, Blue on Blue VFD, Cividis on Paper…), and on a dark theme the map's land, sea and coastlines take the theme's colours too. Dark stays the default and a theme you already picked is kept. The theme is remembered per computer, and your backup carries it.
-
Pick your own colours.
Settings ▸ Appearance ▸ Colours lets you change five colours, each from a few choices that are checked for contrast in every theme, with High contrast or Field mode on, and on the dark displays: the Accent (selected chips, focus rings, your own chat bubbles: Cyan, Blue or Violet), the Readout (the frequency digits: Cyan, Amber, Green or Violet), OK / green (good signal, RX, confirmed: Green, Teal or Mint), Amber (warnings and marginal signal: Amber, Gold or Yellow) and Cyan (information chips: Sky, Cyan or Blue). Each colour has its own Reset, and nothing changes until you pick something: the first choice in each row is the colour you have today. Teal is the green that stays furthest from the reds for a red-green colour-blind operator. The transmit red, the ON AIR sign, the alert orange and the Needed colours cannot be changed, so a keyed transmitter and an alert always look the same, and the frequency digits still turn red when the dial is outside your licence privileges, whatever colour you pick for them. A pick is remembered per computer, like the theme.
-
Night: a darker, warmer screen after dark.
Settings ▸ Appearance ▸ Theme has a Night row: Off, On, or Auto, which turns Night on at dusk and off at dawn at your grid square (when the sun is 6° below the horizon there). Night dims and warms the panels, the text and the accent colour in every theme, and the meters and the frequency readout dim with the room. The transmit red, the ON AIR sign, alerts, and the signal and Needed colours stay exactly as they are. A waterfall on the Auto palette turns Amber CRT at night; a palette you picked by name never changes. Auto needs your grid square (Settings ▸ Station): without one Night stays off, and the row says so. With High contrast on, every word stays at least 7:1 against its background at night. It is remembered per computer, like the theme.
-
A Text size setting: Normal, Large or Larger (#215).
Settings ▸ Appearance ▸ Workspace has a new Text size row, directly under UI scale. Large makes every word on the screen 12% bigger and Larger 25%, Band Activity, the Call Roster and the Logbook included, while the rest of the layout keeps its size. UI scale zooms the whole screen instead, so a bigger scale fits less on it; the two can be combined. Normal is exactly the size text has always been, and the choice is kept per computer, like the theme. The numbers drawn on the waterfall and the scope, the map's labels and the other drawn graphics follow UI scale only.
-
A Touch density for touchscreens.
Density (Settings ▸ Appearance ▸ Workspace) has four choices: Comfortable, Standard, Compact and Touch. Touch is Comfortable with bigger places to tap: the larger buttons grow from 44 to 48 pixels tall, and the small chips (the decode filters, the Settings choices, the top bar's toggles) get a 36-pixel box. Comfortable spaces the decode, roster and log rows a little further apart than Standard. The middle setting, labelled Comfortable while Density had two choices, is now called Standard: whichever you had stays picked, and nothing on the screen moves.
-
One-tap looks.
Settings ▸ Appearance ▸ Workspace starts with a Look row: Shack, Field / POTA, Night, Contest, Big & clear and Touch. One tap sets several of the rows below together, and the row lights up the look that is on screen, or says Custom when your own mix matches none of them. Shack is the app as installed. Field / POTA turns Field mode on for sunlight and Night turns Night on; both put text size and density back to Normal and Standard. Contest is Compact, Big & clear is Larger text with High contrast and Comfortable spacing, and Touch is the Touch density; those three keep Field mode and Night as they are. No look changes your theme, UI scale, colours or waterfall palettes. Hover a look to see what it sets; after a tap, Undo puts back what it replaced.
-
Drag to resize, on every screen, from the mouse or the keyboard.
Every divider you can drag now also works from the keyboard: Tab reaches it, a thin accent ring shows which one has the keyboard, the arrow keys move it (hold Shift for a bigger step), Home and End take it to either end, and Backspace or a double-click puts it back. A screen reader says each divider's name and its position. New dividers:
- Phone, CW and JS8: the width of the log column, and with three columns a second divider shares the width between the other two. Moving one never reloads the log form or the voice keyer, so a half-typed contact stays where it is.
- JS8: the height between Activity and Band activity, between Stations and Inbox, and under the waterfall.
- RTTY and PSK: between the decoded text and the log, and under the waterfall. SSTV: under the picture area, which keeps growing with the window until you move it.
- Operate: in the Classic layout, between Band Activity and the Rx Frequency column and between Rx Frequency and the Tx1–Tx6 messages; in the Roster layout, between the Call Roster and the side rail. ⊞ Panels ▸ Side rail on the left moves the rail to the left of the window.
- APRS: between the map and the column with the beacon form, the message form and the station list, so the station table can show its last columns; the Map on the left button swaps the map and the column.
- Conditions: the height of the row of panes under the map. Logbook: the height of the 3-D globe. Satellites and Awards: the line between the two columns. Each window keeps its own heights and widths, fitted to the window when it changes size, and ⊞ Panels ▸ Undo last change and Reset layout cover them. A layout you set before this opens exactly as you left it. The dividers also sit in the gap between panes now instead of taking room of their own, so the panes beside them get back 12 px (8 px in Operate). They stop exactly where the scope or waterfall stops, where dragging past that point used to leave a dead stretch that moved nothing, and they follow the pointer at any UI scale.
-
Phone, CW and JS8: arrange the panes.
⊞ Panels on these three cockpits now starts with an Arrange section: the screen's three columns, each listing the panes on screen in it, and beside each pane ▲ ▼ to move it up or down in its column and ◀ ▶ to move it into the column beside it. Phone's voice keyer and JS8's log move up and down only, so a message being sent, a recording in progress or a half-typed contact is never cut off by a move. Phone's and CW's log form stays at the foot of its column, and CW's Rig controls stay at the top of the middle one. Undo last change and Reset layout cover a move like any other change, each window keeps its own arrangement, and until you move something each cockpit looks exactly as it did.
-
Spots and Needed on the Phone and CW screens (#345).
⊞ Panels on the Phone and CW cockpits has two new entries, Spots and Needed, and both start unticked, so nobody's screen changes on the update. Tick one and it joins the screen, in space that used to sit empty on a wide window; on a narrower window both go at the bottom of the left-hand column, with a divider between them that you drag to share the height. Spots opens on the spots in the phone part of the band, or the CW part on the CW screen, on the band your radio is on, and moves with the radio when you change band; Needed opens on the phone or CW needs. Their Filter chips widen them to other modes and other bands, and each pane keeps its own filters, so a chip on the Phone or CW screen never changes the Spots or Needed screen. A click on a row does exactly what it does on those screens: the radio goes to the station and the call goes into the log, and a spot in another mode, once you have widened the list to it, opens its own screen. Nothing transmits. Reset layout unticks both again.
-
Repeaters: Save to Memories.
Every FM repeater's row has a Save to Memories button, and Save all to Memories saves every FM repeater the list shows. The memory carries the frequency, offset, tone or DCS code, narrow FM, the callsign and the site, and in its notes the town, the links (AllStar, IRLP, DMR ID) and the DMR colour code. A repeater already in Memories shows In Memories instead, and nothing is saved twice, even when the same machine comes from another directory. The rows no longer carry a ☆: star a saved repeater in Memories to put it on the cockpit strip.
-
Repeaters shows the repeaters it found on a map.
After a fetch, a map of the search sits beside the list (above it on a narrower window): the radius ring around the place, or the corridor along a route, with each machine's callsign beside its dot. Point at a dot and its row lights up; point at a row and its dot is ringed. A click on a dot brings its row into view and opens a card with Save to Memories and Add to channel list. The map shows hearham's listings only, each where hearham places it: RepeaterBook's terms do not allow its listings on a map, and the RSGB list is not mapped yet, so the words under the map say how many machines it leaves off.
-
Repeaters lists the repeaters along a route.
Press Route to… in Near, give the place you leave from and the place you are going (My station, a grid or a city), and Repeaters lists the repeaters within a corridor of the straight line between them, in the order the trip passes them; each row reads how far along the route the machine is ("120 mi"), and the line under it how far off the route. The corridor is 25 mi either side to start with, with 10 and 50 mi chips. Add all to channel list adds them in that order, so the CHIRP or CSV export is one list for the drive. A long US route asks RepeaterBook about the first nine states it reaches and names the states it did not ask about, whose machines are then hearham's alone; a long UK route does the same with the RSGB list.
-
Repeaters finds the repeaters on a frequency.
Type a frequency into the list's filter, Filter: call or MHz (147.18, 147.180, 438.5125, or 438,5125 with a decimal comma), and the list shows every repeater on it, within 2.5 kHz, whatever the band, digital and on-air filters are set to: a DMR or off-air machine on that frequency is listed rather than hidden, and the count line says the filters are not applied. A neighbouring channel never matches (147.18 does not find 147.195 or 147.1875). A callsign or town filters the list as before.
-
Repeaters shows how a repeater links, and the export carries it.
A repeater hearham lists with an AllStar or IRLP node, or with its DMR ID, has a line under its row with those numbers and its DMR colour code ("AllStar 2462 · IRLP 3570 · CC1"); a node hearham gives without naming its network reads "node 7230". The CHIRP and CSV files write the same after the town in that channel's comment ("Rockford; IRLP 3570; CC1"), since neither has a column for them.
-
UK repeaters from the coordinator's own list, one row per machine.
For a UK location, Repeaters reads the RSGB's repeater list (ETCC, ukrepeater.net) for the locator squares around it, at most nine per search and each kept on your PC for a week, and merges it with hearham into one row per machine. Where the two differ, the coordinator's values are programmed and the row is flagged with what each listed. Around Manchester that fixes GB3BW's tone (88.5 Hz, where hearham has 82.5) and GB3XN's input (438.525 MHz; hearham lists it as simplex, so a radio programmed from it could not open the machine), and a machine hearham lists only by its DMR side, like GB3XL, becomes one FM channel with its CTCSS tone and colour code. Every row says where it came from and how old that is ("RSGB + hearham · no date · fetched 2d ago"). With a RepeaterBook token its rows and hearham's merge the same way, and a machine hearham lists once per mode or per linked node is one row. The RSGB list is a beta service: when it cannot be read, Repeaters says so and shows hearham's machines alone. The CSV and CHIRP files credit every directory their rows came from.
-
JS8: JS8Call's allow and deny lists.
Settings ▸ Digital ▸ JS8 has JS8Call's three lists, comma-separated and empty by default as in JS8Call: Only auto-reply to these callsigns, Never auto-reply to these callsigns and Never acknowledge heartbeats from these callsigns. A station is matched by its call as heard or its base call, so W1AW covers W1AW/P. A station the first two keep out is not acted on at all, as in JS8Call: no reply, no relay, its message not filed, nothing held for it.
-
JS8: each automatic reply asks you first, as JS8Call does.
JS8Call ships with "Ask for confirmation before sending autoreply transmissions" on, and so does Nexus now (Settings ▸ Digital ▸ JS8). An answer to a query, an ACK, a relay or a heartbeat acknowledgement waits in the dock as JS8Call's question, "A transmission is queued for autoreply … would you like to send this transmission?", with Yes and No. Yes sends it in the next period, through every TX check; No sends nothing, and so does no answer: after 89 seconds it is No, JS8Call's 90-second box as it counts. A message held for another station is handed over only on Yes. Turn the setting off and replies go by themselves, in the next period.
-
JS8: messages are acknowledged, as JS8Call acknowledges them.
When a MSG addressed to you, or to a group you joined, lands in your Inbox, or a station leaves a MSG TO: with you for someone else, Nexus answers the sender with an ACK (
W1AW ACKfor a message from W1AW), the reply a JS8Call station sends, so the sender knows it arrived; one that came through a relay is acknowledged back along the same relay path. It is an automatic reply like the others: it needs TX on and AUTOREPLY on (the default, as in JS8Call), asks for your Yes first unless you turned that off, and is dropped, not sent later, if TX is off, your locator is missing or the frequency is outside your privileges when its turn comes. A message to @ALLCALL, to another station or to a group you have not joined is never acknowledged, and a copy that arrives while the ACK is still waiting does not get a second one. -
JS8: send your grid to a station in one click, as in JS8Call.
Each station in the JS8 cockpit's Stations pane has a new button beside the quick queries, GRID followed by your locator. One click sends that station your locator, the way JS8Call's "GRID … - Send my current station Maidenhead grid locator" does. It is greyed out while Settings has no locator, or one JS8 will not send (such as EN5), and its tooltip then says what to set.
-
JS8: the
<MYGRID4>and<MYGRID12>macros, as in JS8Call.Type either in a JS8 message, or put it in your INFO or STATUS text (Settings ▸ Digital ▸ JS8), and it goes out as the first 4 or the first 12 characters of the locator in Settings. An INFO or STATUS reply sends the current value, so it follows the locator when you move.
-
JS8: band activity aging, as in JS8Call.
Settings ▸ Digital ▸ JS8 has a new Band activity aging (minutes) field, 2 by default as in JS8Call, so the Band activity pane looks different out of the box: a row whose newest decode is 2 minutes old or more leaves the pane, unless RX is on its offset (a double-click on a row puts RX there). Set it to 0 to keep every row, as before. Nothing about decoding or transmitting changes, and a row comes back as soon as its offset decodes again. Up to 1440 minutes, a day.
-
JS8: callsign aging, as in JS8Call.
Settings ▸ Digital ▸ JS8 has a new Callsign aging (minutes) field, off (0) by default as in JS8Call. Set it, and a station you have not heard for that many minutes drops off the JS8 Stations pane, unless it is the one you have selected or it has an unread message for you, and your automatic HEARING? replies leave it out. It is not saved with the heard list either, so it does not come back when Nexus restarts. Up to 1440 minutes, a day, as in JS8Call.
-
The rotator strip on the RTTY, PSK, SSTV and JS8 screens.
Phone, CW and FT already had it: the antenna's heading in the cockpit header, with → CALL and LP to turn toward the station you are working the short or the long way, and ■ to stop the rotator. → CALL turns toward the call in the Call box on the RTTY and PSK screens, the station you selected on the JS8 screen, and on the SSTV screen the station whose picture you would reply to (the last callsign heard in a picture's ID). A station with no rotator sees nothing new, and the strip asks the rotator nothing while its screen is not the one showing.
-
The Rotor pane shows and sets the elevation of an az/el rotator.
On a rotator with an elevation axis, such as a Yaesu G-5500 on its GS-232B or GS-232A, the Rotor pane shows the elevation under the bearing (
EL 45°) and has anel°box beside the bearing box: type an elevation and press Enter, for EME, a pass you steer by hand, or parking the antenna. It takes only what the rotator can reach (0–180° on a G-5500) and refuses anything else before sending it, and the bearing stays where it is. While the antenna is on its way the pane shows→ EL 30°, as it does for a bearing. The one ■ STOP stops both motors. Nexus asks the rotator's own control program whether it has an elevation axis, so a rotator without one gets exactly the pane it had. -
PstRotatorAz by name in the rotator picker.
Settings ▸ Radio ▸ Rotator now offers PstRotatorAz / PstRotator (UDP), Hamlib's model 3 for YO3DMU's PstRotatorAz, which used to be reachable only as "Other Hamlib model #…" 3. PstRotatorAz takes its commands over UDP, so for this entry the port box asks for its address (
127.0.0.1:12000on the same PC), and the hint under it says to turn on UDP Control in PstRotatorAz's Setup. The hint also warns that Hamlib's backend for it, including the one Nexus ships, writes the bearing it sends with a formatting bug (123.4° goes out as123.400002.2), so PstRotatorAz may not turn to it. Nobody has tried that against a real PstRotatorAz yet. A rotator already set up as model 3 is unchanged and now shows by name. -
The Yaesu G-5500 / G-5500DC by name in the rotator picker.
The G-5500 has no computer port and no Hamlib model of its own: it is driven through a Yaesu GS-232B or GS-232A interface. So Settings ▸ Radio ▸ Rotator now names it on those two entries, Yaesu G-5500 / G-5500DC — GS-232B interface and — GS-232A interface, each still any GS-232B or GS-232A. A GS-232 clone board still belongs on GS-232 (generic). A rotator you have already set up is unchanged. The rotator guide and the settings reference say which entry to pick, and the guide's list of rotator models now matches the picker entry for entry: it still called the DF9GR ERC entry by its old name.
-
Wavelog and Cloudlog on your own network over plain http (#378).
A Wavelog or Cloudlog on your LAN with no certificate can now take uploads at an
http://address, as long as that address is on your own network: 192.168.x.x, 10.x.x.x, 172.16–31.x.x or 127.x.x.x (or a local IPv6 address), or a name whose every address is one of those. The upload goes to the address that was checked and nowhere else. Your API key travels unencrypted on that network, so Settings says so under the Base URL as soon as you type anhttp://address, and the Connections log says where it went, once a session for each address. Any otherhttp://address is refused before anything is sent, as before;https://is unchanged; and Nexus never follows a redirect with your key. -
Watch list: a note on each entry (#390).
Every entry on the watch list (Settings ▸ Spots & Alerts) has a note field of its own, for why the call is there and when it can come off, such as
Samoa DXp 9/27-10/3. Type the note when you add the entry, or later in the field on its row: it is saved when you leave the field or press Enter. Empty the field to remove the note. Your existing watch list comes up exactly as it was, with no notes, and a note changes nothing about what alerts or what the Call Roster, the Stations list and Spots mark. -
Call Roster: show only the stations within a distance you choose (#386).
The Call Roster's filter row has a new picker beside Hide blocked. Pick Within 1000 mi, for example, and the stations farther from your grid square than that leave the list, so a band full of stations you cannot reach stops crowding the ones you can. The choices run from 250 to 5000, in miles or kilometres as the Units setting says (Settings ▸ Station ▸ Operator & Radio). It starts at Any distance, which shows every station, as before. A station you have not heard send a grid yet has no known distance, so it always stays on the list, and so does the station you are working. The choice is remembered with the roster's other filters.
-
A switch for the pop-ups in the bottom-right corner (#391).
Settings ▸ Spots & Alerts ▸ Alerts ▸ Pop-up notifications, on unless you turn it off. Off, the confirmations (Logged QSO, Saved, a QSY, an upload to QRZ) and the alerts (a new DXCC, a station calling you, a band opening, space weather, a DXpedition you chase coming on) stop popping up; their sounds are unchanged. What must be seen still pops up: every error, every notice about transmitting, the radio or the log (TX locked, nothing to log, TX turned back on), and every message with a button, such as an alarm's Stop, an Undo or an update's Download. Pop-out windows follow the same switch.
-
The mouse wheel moves the Phone cockpit's sliders (#384).
Point at a slider and scroll. AF gain, RF gain, squelch, noise reduction, mic gain, the speech processor, the monitor and the Sub receiver's levels move 2% a notch, RF power 1%, the manual notch 10 Hz, the Icom scope reference 0.5 dB and the Flex one 5 dB. The scope's G and Z move one step, where scrolling over them used to tune the radio. A trackpad works the same way. A slider moves exactly as it would under your hand, so RF power stays within your power limit and nothing done with the wheel keys the transmitter. Only the slider under the pointer moves, never one you clicked earlier, and a scroll that starts elsewhere and passes over a slider keeps scrolling.
-
New York QSO Party.
Pick it under Settings ▸ Contesting ▸ Contest and the workspace runs the NYQP committee's own 2026 rules: the third Saturday of October from 1400Z for twelve hours, every US band except 30, 17 and 12 m (60 m and everything from 6 m up count), phone 1 point, CW 2 and digital 3. New York stations send RST and their county as the sponsor's three-letter code; the rest of the US and Canada send their state or province, and everyone else sends
DX. The county box takes the name as well as the code:Monroebecomes MON. Washington, Delaware and Ontario are also the name of a state or a province, so for those you pick from the list. A station counts once per band on phone, CW and digital, a New York station that changes county is a new station, and a station on a county line is logged once for each county. Duplicates stay in the log, marked and scoring nothing, because the sponsor uses them to cross-check the other logs. New York stations multiply by New York counties, US states and Canadian provinces, with New York itself counted from your first New York county; everyone else multiplies by the New York counties worked. FT8 and FT4 earn no credit, because their contest messages have no room for a county. The Cabrillo export writesCONTEST: NY-QSO-PARTYand your county code asLOCATIONfor a New York entry, as the sponsor's sample log does. -
Running the shack over Parsec? Nexus can stop a latched transmission when the link drops.
Settings ▸ Radio ▸ Transmit limits & sharing has a new switch, Stop latched transmissions if my Parsec session drops, off unless you turn it on (Windows only). Nexus watches Parsec's own log on the shack PC, and if the Parsec session that was connected drops, or the log can no longer be read, it stops a latched PTT, continuous RTTY or PSK, and Tune, exactly as their own Stop does. The Now-Bar then says what was stopped and when, until you transmit again. It only ever stops: it never keys, never turns TX back on, and leaves FT8/FT4 alone (an over ends by itself and the TX watchdog still applies). Parsec itself can take about a minute to give up on a session after a pulled network cable, so this backs up the TX watchdog rather than replacing it. The line under the switch shows what Nexus last read from Parsec's log.
-
Ctrl+K finds a setting.
In Settings, Ctrl+K (⌘K on a Mac) puts the cursor in the search box at the top, from anywhere in the panel, and the empty box shows the shortcut. It works only while Settings is open, and it takes no key a cockpit uses: Esc, the space bar and the F-keys still stop and send exactly as before.
-
Cividis joins the waterfall palettes, and the palettes are in Settings too.
Cividis is marked colour-blind safe: it looks almost the same to red-green colour-blind eyes as to everyone else. Settings ▸ Appearance ▸ Waterfall & scopes has the palette Phone, CW, RTTY and SSTV share and the FT waterfall's own, the same two settings as the pickers in the cockpits. Turbo stays the default, and a palette you picked stays picked.
-
Reduce motion, in Settings.
Settings ▸ Appearance ▸ Performance ▸ Motion: Follow the computer (as before) or Reduce, which turns off the animations and fades and helps a slow computer keep up. Alerts still show; they just stop pulsing. Remembered per computer.
-
Your backup carries how Nexus looks.
Settings ▸ Config ▸ Backup & reset now saves the theme, colours, text size, density, Night, motion, the waterfall palettes and the Logbook globe with the rest of your setup, and Restore puts them back. A backup made before this restores exactly as it always did, and Field mode and UI scale stay with each computer.
-
Remote: stream the station to your browser (Beta, Windows, off by default).
With Stream this station from my browser on at the shack (Settings ▸ Station ▸ Remote access), a browser you have approved, while it holds control, is shown this Nexus window, works it with its own mouse and keyboard, hears the station's receive audio and can talk on the rig with its own microphone. Each station card on the Remote site has one big Stream button and a small Listen for the station's audio alone; the old watch-and-control page is hidden on the site while streaming is in Beta. A browser that is not approved yet asks with that same Stream button, and Nexus at the shack asks Let Chrome on Windows stream this station? (with the browser's own name) with the browser's key, the same key the site shows, and Approve or Deny; the question never approves by default, so Enter alone denies. Each browser holds its own key, so a browser approved before this update, or one whose site data was cleared, must be approved once more. Settings ▸ Station ▸ Remote access is one card: the streaming switch, where the station stands with the Remote service, and your browsers with their keys and Approve or Remove; the rest folds under Advanced, unchanged. Only the Nexus window is sent, never the rest of the PC's screen, and what you click and type reaches Nexus and no other program. Nexus must stay open and not minimized at the shack; Windows draws its yellow capture border round the window while a stream is attached, and Nexus keeps the PC awake until the last stream ends.
- Stopping: Stop TX stays at the top of the stream page the whole time, and says Stopped only once nothing at the station is transmitting. While a browser is attached, every transmission at the station stops within five seconds if its connection drops, and within seven if its picture freezes. Turning streaming off at the shack, or Remote access off for your account, ends a running stream within seconds, and switching to another browser tab ends it too. After 15 minutes with no click, key or PTT from your browser the page asks "Still there?", and with no answer within a minute the stream ends.
- Talking: the page's PTT, and the space bar over the picture in Phone, arm an over, and the rig keys only when your voice starts arriving, so a held PTT with the microphone off or muted puts nothing on the air. The over ends 200 ms after your voice stops or the PTT is let go, no over lasts longer than 10 minutes, and the page reminds you to give your call sign before each ten minutes of a run of overs is up. The rig must take its SSB audio from USB; on most radios the factory setting is the front microphone, and the page says so when the rig shows no power out while your voice is arriving.
- Listen and a stream can run at the same time: the station encodes its receive audio once and sends it to both.
- Not yet on every network: the browser and the shack connect directly, with no relay yet. From another network (a phone on cellular, a friend's Wi-Fi) a stream connects; from the shack's own network it connects only if your router loops traffic back to its own public address, which many home routers do not, and the page then says the connection was lost after about 15 s. A fix is planned for 1.16.1.
Changed
-
The transmit buttons are in one place on every screen: FT's strip, under the scope.
TX On/Off, Tune, ATU and Stop TX now sit in one row under the scope or waterfall on Phone, CW, RTTY, PSK, JS8 and SSTV, in FT's order and at the size the header's buttons had, so Stop TX is in the same spot whichever mode you are in. On Tempo the row moves from the top bar to just under the Tempo header, with Hold Tx, and gains ATU. On APRS it replaces the TX On/Off chip and adds Stop TX (Tune and ATU too, when the radio reports a tuner). The row stays in the window when a large text size makes the screen scroll: at 150 % and 175 % the header's Stop TX could sit under the transmit bar on Phone, CW and PSK. Each mode keeps its own send area. On Phone and CW the first button only shows whether transmit is enabled, because those screens enable it themselves. Tune lights while its carrier is up, as on FT, and FT's transmit buttons are now the same size as everyone else's.
-
ON AIR is now a solid red sign you cannot miss.
While the rig is keyed, the TX state in the cockpit header (Phone, CW, RTTY, PSK, SSTV, JS8 and Tempo), Operate's ▲ TRANSMITTING in the QSO strip and the TX plate in the top bar all show as a steady red pill with white lettering and an outline. It reads in the dark and light themes, and with High contrast or Field mode on. The top bar's plate no longer blinks. The pill takes the same room keyed or not, so nothing beside it, Stop TX included, moves when you key. The receive state looks as before, and the TX colour itself is unchanged.
-
Connect is now Conditions, and it opens in Frame + bar.
The view the navigation bar called Connect is Conditions (formerly Connect): the button reads Conditions, and its tooltip and the window's title say "(formerly Connect)". Your saved layouts and settings are unchanged. After the update Conditions opens once in Frame + bar, in the main window, the dashboard window and on the TV page, whatever layout it had. If you had arranged it yourself, your arrangement is kept: Layout ▸ Your earlier layout brings it back exactly, boxes, tabs, widths and splits, in one tap. Standard is the first choice in Layout, and Reset layout still puts every pane back. The switch happens once and never again, even after a reinstall or a restore from a backup, and a dashboard window you never arranged follows the main window, as it always has. On the TV page Frame + bar leaves out the boxes the page can never fill (Chase and its tabs, the rotor, the amplifier and the band scope): Space Wx and the Kp outlook take Chase's place.
-
Conditions has no radio controls, so its map and panes get the whole height.
The bar across the top of the window, with the frequency, the band list, TX Off, Tune and Stop TX, is no longer shown on Conditions; every other screen still has it. To stop a transmission while Conditions is on screen, press Esc, or go to any other screen and press Stop TX there. The UTC clock is at the end of Conditions' own header now, in every layout, with your local time beside it if you turned that on in Settings ▸ Workspace.
-
Conditions' boxes have clearer names, and their menus are grouped by what the boxes are for.
The headline box is now Best band, the card that floats over the map is Propagation, and Best Band → Region is Bands by region, so nothing else on the screen is called "Conditions" and the two band boxes no longer read alike. A box's picker and ⋯ ▸ Add a tab list the boxes under Bands, Space weather, Activity and Station instead of Panels, B2 and B3.
-
Program is now Repeaters.
The view the navigation bar called Program is called Repeaters everywhere: the navigation button, its tooltip, the view's title, Settings ▸ Appearance ▸ Features, the window title, the RepeaterBook token's notes and the guide, in all five languages. The channel list's Save to Memory Bank is now Save list to Memories: it always wrote the list into Memories, the same place a row's Save to Memories writes to. Your saved channel lists, your settings and the RepeaterBook token are unchanged.
-
Repeaters uses the whole window, and is simpler to work.
The page fills the width instead of sitting in a column in the middle. On a wide window (1920×1080, and 1366×768 at the default scale) the Search card is a compact strip across the top, and under it the map and the list sit side by side, each the full height, so the list shows many more rows: about seven at 1920×1080 where it showed two. On a narrower window the map sits above the list, and the channel list keeps its own column. Near is the one place that says where to search: My station, or one box that takes a grid square or a city (the Grid and City chips are gone), and Route to…. The list's own filter sits with the list, reads Filter: call or MHz and clears with one ✕; a place typed into it is offered as a search instead of quietly emptying the list ("Search near "woodstock, il" instead?"). The count line says what the filters hide, with one tap to show it all: "21 of 25 shown · nearest first — 4 hidden by On-air only · Show all". The bands are one control, FM / +Digital / On-air only one Show group, Auto says its radius in words ("50 mi: about how far 2m+70cm reach from a car or a handheld"), and a row's buttons say what they do: Tune, Save to Memories and Add to channel list. The page has the Conditions look, three cards (Search, Results and Channel list) with every word at 4.5:1 or better in every theme. An off-air repeater fades by colour and stays readable instead of being drawn see-through, and on a small screen at a large zoom the channel list no longer covers the results' Tune and Add buttons.
-
On a small window the top bar takes two lines instead of four.
A small window is one under 1100 pixels wide after the text scale: 1024×768 at 100 % or more, 1366×768 at 125 % or more, 1920×1080 at 175 %. There, Needed, Spots, DXped, Logbook, Awards, Stats, Field Day, POTA/SOTA, Memories, Repeaters and Settings leave the FT items out of the bar: the eleven mode buttons, the Tx cycle, the slot countdown, Sync and DT. Those are on FT and Tempo. TX Off, Tune, Stop TX and Hold Tx stay in the bar; on Field Day that is still the screen's Stop TX. On FT and Tempo the eleven mode buttons become one button that shows the mode in use and opens the list of all eleven, and Auto, Tx 1st and Tx 2nd lose their small "cycle", "even" and "odd" captions, so FT's bar fits on one line at 1024×768 and 100 %. Larger windows are unchanged.
-
A band says the same thing everywhere.
The map's Band conditions list, the Band Advisor, the band menu and the NOW bar now show the same word and the same colour for each band.
- A band you are hearing now is Open and green, even when the propagation model calls it closed. A summer Es opening on 10 m or 6 m used to show a grey "Open".
- The NOW bar says what the band menu says, in the same word. For a band the model calls open but nobody has heard yet it now says "20m Open" (it used to say "quiet"), and "20m Marginal" where the list says Marginal. A closed band shows in grey instead of red.
- Open, Marginal and Closed are shown in English in every language, like the band names, on the list, the Band Advisor, the band menu, the NOW bar and the band tiles. The NOW bar used to put them in the interface's language.
- The Band Advisor's word is the same outlined word as the list's. A closed band's row is no longer faded to half strength, which made its text too faint to read; its band name and word are dimmer instead.
-
The light theme keeps its displays dark.
The frequency readout in the cockpit header, the S-meters, the transmit meters (SWR, ALC, PO, COMP), the RX audio level meter, CW's zero-beat bar, the waterfall's frequency scale and legend, the MSK144 Fast Graph and the small audio spectrum (Settings and Conditions) now stay dark in the light theme, like the waterfall itself. Everything around them stays light: think of a light-coloured radio with dark display windows. The meter colours and the readout's digits are the ones the dark theme uses, so a strong signal or a high SWR looks the same whichever theme you run. In the dark theme they look as before. The waterfall's TX and RX markers, and the RX line in PSK and the Mark line in RTTY, now take the app's own TX and RX colours instead of colours of their own.
-
The light theme's highlight colour is a little darker, so it reads better.
The blue of selected buttons and chips, links, your own chat bubbles, the focus outline and the top bar's frequency digits is a deeper shade of the same blue. Words in it, and white words on it, now meet the usual 4.5:1 reading contrast on the light panels, where they were about 3.5:1. The dark theme is unchanged.
-
Settings ▸ Appearance is in sections.
Workspace keeps the looks and the sizes (UI scale, text size, density); Theme has the theme, High contrast, Night and Field mode; then Colours, Waterfall & scopes, Map & globe (the Logbook globe) and Performance. Every setting works as before, and searching still finds each one.
-
The waterfall's RX and TX markers show how wide the signal is, as in WSJT-X.
On FT8, FT4, FST4, FST4W, Q65 and JT65 each marker is now two lines, one on its frequency (where the single line was) and one on the signal's top tone, joined by a bar: along the top of the waterfall for TX (red) and along the bottom for RX (green). The widths are the ones WSJT-X's Wide Graph draws: 43.75 Hz on FT8, 62.5 Hz on FT4, and on Q65, JT65 and FST4 they follow your submode and T/R period. Clicking works exactly as before: left-click sets RX, right-click or Shift-click sets TX for a split, and Ctrl-click sets both. A click inside a marker tunes to the spot you clicked. WSPR, MSK144, FT2 and the Tempo modes keep the single line.
-
Most settings changes no longer hold up the radio.
A band pick, the Pwr slider, a TX offset, a switch in Settings: each used to make the loop that runs the radio wait while the settings file was written to disk, a few milliseconds on a fast drive and longer on a slow one or while an antivirus scanned the file. The file is now written in the background, always with the newest change, and Nexus writes the last one before it quits, restarts, reopens for another radio or installs an update. Some changes still save on the spot, because whether the save worked decides the change: changes made from Remote, restoring a backup, the RTTY and PSK macro editors and the satellite Doppler switch. What each setting does, and when it takes effect, is unchanged.
-
Phone: Space presses the buttons in ⊞ Panels.
When a button in the ⊞ Panels menu has the focus (an Arrange move, Undo last change or Reset layout), Space now presses it, as it does anywhere else. Before, Space keyed the transmitter there and the button did nothing. Everywhere else in Phone, Space is still push-to-talk. Letting go of Space still unkeys, wherever the focus has moved.
-
JS8: replies are skipped when JS8Call skips them.
No automatic reply is made while your message box holds text (you are typing, a reply waits there, or a message of yours is going out) or while a message to you is still arriving; a reply already queued waits until the box is free. A heartbeat acknowledgement waits for no message to be arriving, as in JS8Call, rather than for your own queue to be empty. While the idle watchdog stands nothing is filed or held either, and a message to your call as you set it (a /P or a prefixed call) is yours, as JS8Call reads "to me".
-
JS8: with AUTOREPLY off, a reply goes in your message box for you to send, as in JS8Call.
JS8Call still answers a query to you with AUTO unchecked: it types the answer (an SNR, GRID, INFO, STATUS or HEARING reply, the ACK for a MSG, a relay) into its message box, and you send it or not. Nexus did nothing. Now the answer is put in the JS8 message box, the To box and command cleared, exactly as it would go out, once the box is empty and nothing of yours is going out; it never keys by itself, and Send keys it as your own message. QUERY MSGS and heartbeats are still answered only with AUTOREPLY on, as in JS8Call. A relay with AUTOREPLY off now waits in the box too, where it used to go out by itself.
-
JS8: an automatic reply goes out in the next period, as JS8Call sends it.
JS8Call keys a reply in the period right after the one the query came in; Nexus first counted it down for one period and two seconds and so answered two periods late, by which time the other station had often moved on. Now a reply made by itself (the confirmation off) is queued as it is made, in view in the dock's queue, and keys at the next boundary, through every TX check as before (the TX latch, your callsign and locator, your privileges, the idle watchdog, one frame per period, Stop TX, and Drop queue to take it back). A reply you confirm goes at the boundary after your Yes. The countdown and its Cancel are gone; No is the veto now.
-
JS8: no automatic replies to questions sent to @ALLCALL, as in JS8Call.
A station asking everyone (@ALLCALL) for SNR, INFO, STATUS, GRID or HEARING used to get an answer from every Nexus station with autoreply on. JS8Call stations never answer those, and Nexus now doesn't either. Questions sent to your call, or to a group you joined, are answered as before. Nexus also stays quiet where JS8Call does: no reply to INFO? when your info is empty or to GRID? when no locator is set, and an @ALLCALL QUERY MSGS gets an answer only when a message is waiting for that station (at most once every 15 minutes), never a NO. Settings' Auto-reply hint and the cockpit's AUTOREPLY tooltip say what is answered.
-
JS8: a HEARING? reply no longer names the station that asked, as in JS8Call.
A station asking who you hear used to find its own call in your reply, usually first, taking one of the four places. The reply now lists the four stations you heard most recently, not counting the one asking.
-
JS8: the heartbeat goes out as JS8Call's does.
With a six-character locator in Settings every heartbeat went out on two periods in a row, because the last two characters spilled into a second frame; it now carries the four-character square, as JS8Call's does, and is one frame. If your offset is 1000 Hz or lower the heartbeat stays on it; above that it takes a free spot between 500 and 999 Hz, and the Activity pane, Band Activity and ALL.TXT now show the offset it was sent on, not your own. With HB-ack on, the acknowledgement of a heartbeat you heard takes such a free spot too, whatever your offset, where it used to go out on your own offset. A spot counts as taken when any decoded frame was heard there, including the middle frames of a long message, and your own offset always counts as free, as in JS8Call. The timer counts as JS8Call's does, and anything you send, or a message addressed to you, restarts it. A heartbeat that comes due while TX is off is skipped, where it used to go out the moment you turned TX back on. Not yet checked on the air: turn HB on with a 5-minute interval and check that one heartbeat goes out about five minutes later, shown in the Activity pane at an offset between 500 and 1000 Hz.
-
JS8: nothing is transmitted without a valid locator, as in JS8Call.
With the Grid field in Settings (Operator & Radio) empty, JS8 used to transmit anyway, and heartbeats and CQs went out without your square; a slip such as "EN5" made every heartbeat go out as two frames. JS8 now takes only a locator JS8Call's own Settings would accept: 4 to 12 characters in whole pairs (EN52, EN52HW, EN52HW12 and so on), in upper or lower case. Without one, Send, CQ and the query buttons are refused with a message saying where to set it, an automatic reply or heartbeat that comes due is dropped, and what was already queued is dropped too, as JS8Call drops its queue, rather than going out the moment a locator is set. A repeating CQ and the heartbeat stay armed and carry on at their next times once the locator is fixed, and a message already going out when the locator is cleared still finishes. FT8 and FT4 keep their own rule.
-
JS8: @APRSIS and @JS8NET work as in JS8Call: you can send to them, but not join them.
With either in the To field, Send used to refuse; JS8Call sends to both like any group, and so does Nexus now. A JS8Call station that gates to APRS-IS forwards what it hears addressed to @APRSIS:
@APRSIS GRID <locator>puts your position on APRS-IS, and@APRSIS CMD <text>puts<text>on APRS-IS as a packet from your call, such as an APRS message to another station or to a gateway. While either is in the JS8 Groups field, Settings will not save: it says "… is a group that cannot be joined" and where to take it out, as JS8Call's Settings refuses its OK. If an earlier Nexus saved one in your settings, it stays in the field but is not joined, so traffic to it gets no automatic replies.
Fixed
-
Esc stops transmit on every operating screen and on Satellites.
It did nothing on Tempo, SSTV, APRS and Satellites, and on Phone it stopped only the voice keyer. Now on each of them it does what Stop TX does (on Tempo, the top bar's; APRS and Satellites draw no Stop TX of their own), from anywhere on the screen, a text field included, as it already did on FT, CW, RTTY, PSK and JS8. A menu or dialog that Esc closes still closes on the same press. Phone's space bar is unchanged.
-
A send that could not go out is dropped, never sent later on its own.
When transmit was off (for example after leaving a mode's screen part-way through a message) or the frequency was outside your license privileges, what was still waiting used to be held, and it went out by itself as soon as transmitting was allowed again: TX back on, or a tune back inside your privileges. It is now dropped, and the screen's warning or status line says why, so nothing keys on your return: send it again. Moving from one mode's screen to another mode's drops what was still to go too; screens that are not a mode's own, such as the map or the logbook, do not count. What you send once transmitting is allowed goes out exactly as before, and Stop TX and the TX switch work as they did.
- CW: the word already being keyed finishes, since the keyer is handed one word at a time. Before, the rest of a message kept keying from Phone, RTTY or PSK. The CW ID after an FT8 73 is sent from the FT8 screen as before.
- RTTY and PSK: if a dropped RTTY over belonged to an auto-sequencer QSO, the auto QSO stops and says so, and an RTTY auto QSO ends when you leave the RTTY screen. An over already going out finishes if you move to Phone, CW, RTTY or PSK, and stops if you move to a digital mode, which turns transmit off.
- The voice keyer: a message played on a frequency outside your privileges did nothing and said nothing; the keyer's "Could not play F1" note now says why, and so do its other failures.
- SSTV: a picture waiting for the radio to be free is dropped, and a warning line beside Send says why. Before, CW, RTTY and PSK held it, and it went out when you came back to Phone.
- APRS: a beacon, a message or an automatic ack is dropped, and the APRS screen's status line says why. A frame waiting only because something else is on the air still goes out when the radio is free, and there is still no automatic beaconing: every beacon is one you send.
- JS8: a message you sent, the rest of one already going out, a repeating CQ's call, and an automatic reply or heartbeat that comes due, are dropped, and the JS8 screen says why. The frame on the air when you turn TX off still finishes, and a repeating CQ keeps its schedule.
-
SSTV: a picture stops going out when its transmission stops.
Leaving the SSTV screen for FT8 while a picture was being sent turned transmit off and dropped PTT, but Nexus went on feeding the rest of the picture to the sound card. On a radio keyed by its audio (VOX, or a data port that keys on audio) that put the radio straight back on the air, and the rest of the picture, up to five minutes of it, went out with transmit off. The same happened when a tune, a radio switch or another screen's Stop ended the transmission part-way through a picture. Now the picture stops with the transmission, at once, and the warning line beside Send says it was stopped and why. With a screen reader, a picture stopped part-way is announced once, as "SSTV transmit stopped", and "finished" only when the whole picture went out. SSTV's own Stop, TX Off and Stop TX work as before.
-
The TX plate, the screen reader, the amplifier lock and Operate's QSO strip follow every transmission.
Each followed only FT8/FT4-style timed overs, so during a Phone over, CW, RTTY, PSK or SSTV, a tune carrier, or with the mic keyed at the radio itself:
- the top bar's TX plate read a green RX while the cockpit's ON AIR sign was red;
- "Transmitting" and "Receiving" for a screen reader, and the optional TX / RX earcon (Settings ▸ Appearance ▸ Accessibility & eyes-free), stayed silent;
- the amplifier strip's Standby/Operate and band ◀ ▶ buttons stayed live with an amplifier that reports no transmit state of its own (the Elecraft KPA), or one whose own flag still read idle, though changing band on a keyed amplifier can damage it;
- Operate's QSO strip showed "▼ Receiving" in green while the rig was keyed. They now follow the ON AIR sign. Nothing about when or how the radio keys has changed. Not yet checked with an amplifier connected: key a voice over and check that the strip's buttons go grey until it ends.
-
Stop TX stands out in every theme.
In the dark themes, Stop TX in Operate and in the top bar had an outline barely darker than the strip around it, and it wrote white on the red when the pointer was over it, which was hard to read. The cockpit headers' Stop TX had a faint outline in the dark themes too, and its word faded under the pointer. Now every Stop TX has a solid red outline in every theme, dark and light, high contrast and night. It turns solid red under the pointer, with the word in the page colour. SSTV's Stop sits on the page colour too while a picture is going out, and so does Roam's Stop, which shares the look. Nothing else about the buttons changed: the same place, size, words and keys.
-
A file Nexus cannot read is kept, never saved over.
When one of these files was damaged, cut short, or written by a newer Nexus with a value this one does not know, Nexus started empty and soon wrote over it, and everything in it was gone: the QSOs waiting in the "Log this QSO?" popup, your saved Repeaters channel lists, the JS8 inbox, Tempo messages waiting to send, Tempo conversations, and the Assistance record (Settings ▸ Contesting ▸ Contest Category), which is evidence for an unassisted contest entry. Now Nexus keeps the file, untouched, under a new dated name beside it (such as
pending_qso.unreadable-20260930-142233.json), and says where. If the file cannot be moved aside, Nexus leaves it where it is and does not write over it.- Field Day and contest contacts: when part of the contest log's backup could not be read (cut off by a crash, or damaged), Nexus restored what it could and the next contact rewrote the backup without the rest; a backup it could not open at all restored nothing, and the next contact replaced every earlier contact of the event. Now Nexus restores the contacts it can read and keeps the backup itself under a new dated name. If the backup cannot be moved aside, Nexus does not write over it, and keeps this session's contest contacts in memory.
- Settings: an unreadable
settings.jsonwas already set aside assettings.json.corrupt, but always under that one name, so a second set-aside replaced the first, and nothing on screen said it had happened. Each one is now kept under a new dated name (such assettings.unreadable-20260930-142233.json), and Nexus says where. If the file cannot be moved aside, Nexus saves no setting over it rather than writing the default settings over yours.
-
Two windows sharing one data folder no longer undo each other's changes.
With two Nexus windows on one data folder (the two-radio setup), a change you made to a contact in one window could, rarely, undo a change the other window had just made to the same contact: an upload stamp, a QSL mark, an edit. It could also bring back a contact the other window had just deleted, and neither window said so. The logbook now refuses to save over a change it has not seen. Your change is made again on the contact as it now stands, and both changes stay; if the other window deleted the contact, or changed what you were editing, you are told so instead. Clear log removes only the contacts this window had, where it also removed contacts the other window had logged since, and a contact the other window logs while this one starts is no longer missing from its duplicate check and worked-before marks. Update both windows, because a window still running 1.15 can still undo the other's changes.
-
Saving in one place no longer undoes a change made in another.
The Contest view's bonus and power chips, switching CW macro sets, and Save in Settings each saved a copy of every setting, taken when that screen opened. Whatever had changed since, anywhere else, went back: "use one radio" turned simultaneous radios on again, a seat swap made in the pop-out scoreboard was undone, and the radio was sent back to the frequency it was on when the screen opened. Each now saves only what you changed there. Use one radio in the launch picker also stays chosen now, where the next setting you changed turned simultaneous radios back on and the picker returned at the next launch.
-
Armed satellite and DXpedition alarms survive a reset of Nexus's window storage.
They were meant to be kept with your settings, like the satellites and DXpeditions you chase, but were kept only in the window's own storage, which a reinstall or a reset of the webview's data clears. They now live with your settings, so an armed alarm, and a pass or a window that already fired, survive both.
-
Nexus no longer turns a TS-590S down to 5 W (#381).
Nexus reads the radio's power back so the power slider follows the radio's own knob. On some radios the Hamlib driver answers that read by setting the power to learn its range: it turns the radio up to full power for an instant and then leaves it at its minimum, 5 W on a TS-590S. It did this on every connect and after every mode change, so switching to FT8 or RTTY did it again. Nexus no longer asks these radios for their power: the Kenwood TS-590S, TS-590SG, TS-2000, TS-50S, TS-450S and TS-930, the TRC-80, the Elecraft K2, the Hilberling PT-8000A, the QRP Labs QCX/QDX, the (tr)uSDX, the FX4, SDRuno and SDR Console. A power you set in Nexus still goes to the radio and still stays under your per-mode limits. On these radios the slider no longer follows the knob, so a power turned up at the radio is not pulled back under a limit. Not yet checked on the air: on a TS-590S, set 80 W at the radio, connect Nexus, and switch to FT8 and then RTTY; the radio should still be at 80 W.
-
A sound card on the radio's rear jack now transmits under CAT PTT: a new Transmit audio source setting (#381).
When Nexus keyed a radio over CAT, the radio transmitted from its microphone input, so on a TS-590S with a SignaLink on the rear ACC2 jack nothing from Nexus went out, although VOX worked. Settings ▸ Radio ▸ Rig & CAT now has Transmit audio source (CAT PTT), Front/Mic or Rear/Data, per radio. With Rear/Data, Nexus keys the radio's data input instead, as WSJT-X's Rear/Data choice does, for everything whose audio Nexus plays: FT8 and the other digital modes, RTTY sent as audio, PSK, SSTV, APRS, the voice keyer, the soundcard CW keyer and Tune. The Phone cockpit's PTT and RTTY sent on an FSK keying line key the radio as before. Front/Mic is the default and keys every radio exactly as before. The choice appears only for CAT PTT on a radio whose Hamlib driver can key either input: the Kenwood TS-480, TS-590S, TS-590SG, TS-890S and TS-990S, the Yaesu FTDX-5000, the ELAD FDM-DUO and a few more. On an FTDX-5000, Hamlib selects the rear input by changing the radio's menu 103, and nothing changes it back, so check that menu before you work phone. Not yet checked on the air: on a TS-590S with a SignaLink on ACC2, choose Rear/Data and press Tune, then send an FT8 over; the radio should put out power both times.
-
The S-meter and the receive controls come back on a radio that answers slowly (#385, #376).
Nexus reads the radio's settings back a few at a time and stops when a poll has used its time. Each poll started again at the top of the list, so on a radio that takes a while to answer each read it never reached the bottom. The Yaesu FTX-1 is one: its Hamlib driver waits 50 ms after every command. There the S-meter stayed blank, and the Receiver pane listed RF, NB, NR, the notches, AGC and SQL under "Not on this radio" although the radio has all of them. The radio's mode, the VOX, COMP and monitor switches and the monitor level were never read either, and a receive filter width you picked was never sent. A poll that runs out of time now hands the rest of the list to the next one, so every setting gets its turn. A radio that answers quickly is read exactly as before. Not yet checked on the air: on an FTX-1, the S-meter should move within a few seconds of connecting, and the Receiver pane should show RF, NB, NR, the notches, AGC and SQL.
-
Yaesu FTX-1: Nexus no longer sends the three commands its Hamlib driver gets wrong (#385).
Checked against Yaesu's own FTX-1 CAT reference, the Hamlib driver Nexus uses for the FTX-1 turns three of Nexus's controls into different commands. The monitor switch becomes MOX, which makes the radio transmit. The monitor level becomes the monitor's on/off switch. The ATU button changes the radio's TUNER SELECT menu to INT (FAST) and tunes nothing. No control in Nexus sent the monitor switch yet, but the ATU button did, and the monitor level would have now that the radio's settings are all read. On an FTX-1, Nexus now sends none of the three: there is no ATU button (press TUNE on the radio), and the Transmitter pane lists MON under "Not on this radio" although the radio has a monitor, so set it on the radio. Everything else is sent as before. Not yet checked on the air: on an FTX-1, there should be no ATU button and no MON slider, and the radio's TUNER SELECT menu should stay as you set it.
-
Settings has the switch to follow the radio's own split.
1.9.1 added following the radio's own split and said to turn it on in Settings, but there was never a switch for it: the only way was to edit settings.json. Settings ▸ Radio ▸ Rig & CAT now has Follow the radio's split, beside Split operation, off by default. Turn it on and a split you set at the radio is the one Nexus checks your licence privileges against; if the radio says it is split but not where it transmits, Nexus will not transmit. Nexus never asks a radio whose split can only be read by moving it.
-
Settings says which Rig & CAT controls belong to every radio.
With two or more radios, the note over the radio cards said that editing another radio would not change the one you are operating, and the manual said every Rig & CAT control is per radio. Seven are station-wide, one setting for all your radios: Interface keys RTS on the CAT port, Split operation, Follow the radio's split, Wheel tuning sensitivity, and under Advanced, Sharing port, Serial handshake and Keying line at startup. The note and the manual now name them, so changing one while you edit another radio no longer surprises the radio you are operating.
-
A rotator controller switched on after Nexus comes online by itself.
Nexus runs Hamlib's rotator program for you, and that program quits at once when the controller's port is not there, which is what a USB controller that is still switched off looks like. Nexus used to start it again only when you saved Settings or switched radios, so every command failed with "Connection refused (os error 61)" until you did. Now it tries again every 5 seconds while a rotator is set up, and the rotator answers a few seconds after you switch it on, with nothing to save. While the controller is off, a command says "The rotator controller isn't answering. Is it switched on and plugged in?", and the Rotor pane and the rotor strip say the same. A rotator that answers but reports no position, such as the Hy-Gain DCU-1, keeps its own message, and an external rotctld that refuses the connection is named by its address.
-
Pointing the rotator at a callsign aims at the station, not the middle of its country.
The → button on a cockpit's rotor strip, the ↗ on Needed rows and the other point-at buttons used to turn the beam to the centre of the station's country: from JO21EV that is 207° for EC1DD, whose own grid is at 227°, and 299° for AA1AA instead of 291°. They now aim at the station itself when Nexus already knows where it is: the grid in the log form (typed, or filled in from the callbook), a grid the station sent on FT8, FT4 or JS8 this session, what a callbook lookup returned, or the grid on your last contact with it. A closer location, such as a six-character grid or the callbook's own position, is used only when it lies inside the square the station is sending, so a callbook address never overrides where a portable station says it is. Nothing is looked up when you point. The message after pointing says what the bearing was taken to: the station's grid, its callbook position, or the centre of its country when nothing closer is known. The long path is still the exact opposite heading.
-
Turning the beam keeps an az/el rotator's elevation where it is.
On a rotator with an elevation axis, such as a Yaesu G-5500 on its GS-232B or GS-232A interface, every azimuth move made by hand also sent the elevation to 0°: a click on the Rotor pane's compass, a typed bearing, the ↗ on a Needed row and the → and LP buttons on a rotor strip each laid the antenna flat on the horizon. Nexus now reads where the antenna is and sends its elevation back with the new bearing. It asks the rotator's control program (Hamlib's rotctld) whether the rotator has an elevation axis rather than going by its name, so an azimuth-only rotator, such as a Rotor-EZ, a DCU-1, a SPID Rot1Prog or a Green Heron RT-21, gets exactly the command it always did. If that program is too busy to answer, the move is refused with a message saying so rather than guessed. A satellite pass steers both axes as before.
-
LP on the rotator strip turns the antenna the long way (#338).
In 1.15.0 the LP button on the Phone, CW and FT screens turned the antenna the short way, exactly like → CALL, and its message gave the heading without saying which path. LP now asks for the long-path heading, and its message says "long path". → CALL is unchanged.
-
The Rotor pane's ■ STOP reads in the light theme, and its → line clears when you press it.
Its red was the dark theme's, and on a light theme's pane it read faintly (about 2.2:1), on the one button that stops the antenna turning. It now takes the same red as the cockpits' Stop TX in every theme. The line that shows where the antenna is going (
→ 200°) and the dashed target on the compass stayed after STOP until the antenna reached a heading it was no longer going to, so a stopped antenna looked as if it were still turning. They now clear as soon as the rotator confirms the stop; if the stop does not reach it, they stay, since the antenna may still be moving. -
The park box fills in for the activator you click, and only for them (#383).
Clicking a second activator's spot while the first one's park was still in the log strip could leave the park box empty, though the hunt line above it named the park, and with no callbook the first activator's park could stay in the box and be logged on the second contact. After a hunted contact was logged, the empty log strip could show that contact's park again and keep it. The box now takes the park of the station you clicked and clears once its contact is logged, and a park filled in from a spot leaves the box when you type a different station's call, so it is never logged on someone else's contact. A park you type before the call belongs to the call you type next; click an activator's spot instead and it is a new station, with the spot's park. An activator spotted again at another park fills the new park, an activator spotted with a portable suffix (KE7G/P) fills too, a prefix form (VE7/KE7G) no longer shows the "call ≠ hunt" warning, and two different portable stations (KE7G/P and KF7XYZ/P) are no longer taken for the same one.
-
A WSPR beacon is spotted on the frequency you set.
Nexus started WSPR's four tones at your TX offset, so stations decoding it with WSJT-X or wsprd spotted it 2.2 Hz higher, and that is what reached WSPRnet: set to 1500 Hz on a 10.1387 MHz dial, it was spotted at 10.140202 instead of 10.140200. The tones are now centred on the offset, the way WSJT-X sends WSPR. The message, the timing and the schedule are unchanged.
-
Repeaters never shows a repeater list it could not read as "no repeaters".
A search could come back saying "No FM repeaters within 50 mi." where there are plenty, with nothing to say why: the hearham list kept on this PC was whatever hearham's address had last answered, an error page included, and it was read as an empty list for up to a week. Now only a list that reads is kept, a kept one that does not is fetched again on the next search, and a list that still cannot be read is an error with Retry, not an empty area. When RepeaterBook answered but hearham's list could not be read, the machines shown are RepeaterBook's and Repeaters says that hearham's are missing, where before they went missing without a word.
-
Repeaters reads more of the hearham directory, and programs it right.
- FM machines the directory writes as
YSF/FM,DMR/FM,D-STAR/FMorP25/FM, 514 of them, most in Florida, New England, Missouri and Minnesota, were hidden unless the digital filter was on, and could not be added to a channel list. They are now listed and can be added, saved to Memories and exported as FM channels, and aYSF/FMmachine keeps its +YSF badge. - A machine the directory marks narrow, hearham's
NFMor a RepeaterBook bandwidth of 12.5 kHz (55 machines in the hearham directory), goes out asNFMin the CHIRP and CSV files and is saved to Memories as NFM, so the radio uses the narrow deviation the machine expects. A narrow machine already in Memories as FM is still that one memory. Tune and recalling the memory still set the radio to ordinary FM: Nexus has no narrow-FM setting for the rig on any radio yet. - A DCS machine's code, written in the tone field as
DCS023,D023,DCS 043,DPL411and a few other spellings, is now exported, in the CHIRP and CSV files and when saved to Memories, where 138 FM machines went out with no code and would not open. Tune still sets no code on the radio: Nexus has no DCS setting for the rig. - A machine that takes its DCS code only on its input (32 hearham machines, and a RepeaterBook machine with a DCS code in PL but not in TSQ) is exported as DCS on transmit only, CHIRP's Cross mode
DTCS->, with the receiver left open. As DCS both ways, it kept the radio squelched on a machine whose output carries no code. CHIRP files carry two more columns at the end,RxDtcsCodeandCrossMode. - A machine that runs FM and a digital mode, whose entry writes the FM tone beside the digital settings (
CC1/146.2,NAC293/100.0), gets its FM tone and DMR colour code: 40 machines get their tone. A code that is not one of the 104 standard ones, or an entry that lists two different tones, still gets none rather than a guess.
- FM machines the directory writes as
-
Remote: Listen plays the station's audio.
Since Listen arrived in 1.13.0 it never played on the Remote site: the page's own security policy refused the audio player the page builds, so every press ended with "The station has no audio to send right now." while the station was sending audio. Behind that, the player also failed on the first packet it was given. Now Listen starts when you press it, and you hear the station.
-
The older Remote page, hidden in 1.16 while streaming is in Beta, has its fixes too.
For the browser in control, Esc stops transmit on FT, CW, RTTY, PSK and JS8 the way Stop TX does, and a Remote Stop says "Stopped" only when nothing is transmitting. Turning the beam keeps an az/el rotator's elevation, and pointing the antenna at a station works again.
-
JS8: a message sent to you is kept in the Inbox, as JS8Call keeps it.
A MSG addressed to you, or to a group you joined, now lands in the JS8 Inbox as unread, with the path it was relayed along. The station that sent it is flagged ⚑ in the Stations pane and moves to the top of the list, just under any station you pinned with ★, and a notice says a new message arrived. Mark it read or delete it in the Inbox. Before, a message to you went by in the activity list and was kept nowhere, although the Inbox said such messages appear there. Nexus now also answers it with an ACK, as JS8Call does (see Added). Messages to you stay until you delete them (the newest 100 are kept); messages held for other stations still go after 48 hours, and a flood of messages to you can never push one of those out.
-
JS8: Nexus no longer relays, stores or answers traffic addressed to other stations.
With relay on (the default), Nexus relayed any relay request it heard on the band, even one addressed to another station or to @ALLCALL. It also stored MSG TO: messages meant for someone else, and could hand a stored message to a QUERY MSG sent to another station. JS8Call acts only on what is addressed to your call or to a group you joined, and so does Nexus now. A QUERY MSG for a message that isn't there now gets no answer, as in JS8Call.
-
JS8: with RELAY off, a message left for another station is no longer held.
Holding MSG TO: messages for the stations they are addressed to is what Settings lists under Relay, and JS8Call holds them only with relaying on; Nexus held them with Relay off too, and offered and delivered them later. Holding another station's message is third-party traffic, so with RELAY off it is now neither held nor acknowledged.
-
JS8: messages held for other stations, and replies to portable stations, follow JS8Call.
A MSG TO: for VE3/W1AW or W1AW/MM was held under that whole call, so W1AW asking QUERY MSGS was told NO; JS8Call holds every such message under the base call, W1AW, and offers it to a station by the call it is heard under or by its base call, and Nexus now does the same. A message left with no text is held and acknowledged, as in JS8Call, but never offered. And every automatic reply to a station heard as W1AW/P named it W1AW; each now names the station as it was heard, as a JS8Call station's reply does.
-
JS8: the idle watchdog works as JS8Call's does.
When it had turned auto-reply, relay and the heartbeat off, changing any setting put those switches back on underneath while it still stood, so a query heard then was answered after your next send; now nothing is answered, relayed or delivered while it stands, and nothing heard meanwhile goes out later. Turning a switch or the repeating CQ back on ended it for one second only; now each send, each switch on or off, Drop queue, Yes or No, Read or Delete in the Inbox and a speed choice starts the idle count again, as each key press or click does in JS8Call. A send that ended it left auto-reply and relay off while the dock showed them on; they now come back on, as Settings has them, while HB and the repeating CQ stay off until you turn them on. The watchdog's notice and the dock's line now say exactly that, in all five languages.
-
JS8: the idle time is counted, in the STATUS reply and on the cockpit's idle chip.
With no STATUS text set, a STATUS? reply said "IDLE 0" however long you had been away, and the JS8 cockpit's idle chip always read 0. Both now count the minutes since you last sent something or opened JS8, and the reply writes it as JS8Call does: "IDLE 5M", "IDLE 1H", "IDLE 2D".
-
JS8: Band activity and the Stations pane place each signal as JS8Call does.
An offset reads in whole hertz with the fraction dropped, as JS8Call shows it, so a signal at 1500.9 Hz is on the 1500 row, not 1501, in Band activity and in the Stations pane alike. A signal at an offset already on the list stays on that row, and one near two rows joins the lower of them, where it used to join whichever row had been listed first and two rows could show the same offset. A station drifting a little at Fast or Turbo no longer shows as two rows: the pane allows 16 Hz at Fast and 32 Hz at Turbo, JS8Call's own tolerances, and keeps 10 Hz at Normal and Slow.
-
JS8: a CQ goes out as one frame when your locator has six characters.
With a six-character locator in Settings, every CQ, clicked or repeated, went out on two periods in a row: first a CQ with no locator, then the locator on its own. It now carries the four-character square, as JS8Call's CQ does, so it is one frame again. A four-character locator is unchanged.
-
JS8: with a compound callsign, directed messages announce your square, as JS8Call's do.
A compound callsign such as KD9TAW/QRP starts each directed message and reply with a frame that announces the callsign, and JS8Call puts your four-character square in that frame. Nexus sent it without one; it now carries the square. A /P callsign is not compound and is unchanged.
-
Space Wx says how old its solar-wind reading is, and never reports a wind of 0 km/s.
While NOAA's DSCOVR data is not coming in, Nexus keeps its last good reading, and the Bz gauge used to show that reading as if it were current. Past 30 minutes the gauge now says when it was made ("last reading 45m ago") instead of how the field looks now, and with no reading at all it says "no solar-wind reading" instead of leaving Bz off the box; the wind speed is not shown from a reading that old. When DSCOVR's plasma data does not answer, or is not from the same half hour as the magnetic field's, the wind's speed and density, and a missing Bt, are sent as not known instead of 0. The Insights feed no longer reports a solar wind of 0 km/s, or raises a solar-wind warning ("turned stormy", "fast stream") from a reading more than 30 minutes old.
-
The Globe map draws only what is on your side of the planet.
A spot, a decoded station, a park, a DXpedition, an APRS station or a satellite on the far side of the planet was drawn on the side facing you, where a line from it straight through the Earth comes out: a 20 m spot in Sydney showed over the eastern Pacific on a globe centred on the US Midwest. Now only what is on your side is drawn, and only that answers a hover or a click. The same goes for your QTH marker when you turn the globe away from it, a satellite's trail, the long path of the Selected path layer, Band heat, the Ionosonde MUF, Aurora oval, Proton polar cap and Flare blackout markers, the grid labels and the CQ-zone numbers. An opening's wedge stops at the edge of the globe instead of showing through the planet, its band and mode tag written just inside the edge when its far end is behind the planet, and on the Flat map a long wedge follows its bearings, where a 20 m F2 opening over the pole was drawn as a thin sliver straight across the Atlantic and Africa. The Beam map and the 3D globe are unchanged.
-
The Band conditions list on the map is readable in every theme (#382).
The band names are now drawn in the theme's own text colour. Before, they used the computer's default button colour, so with Windows in light mode they came out black on the dark theme and could hardly be seen. The Open, Marginal and Closed words are now lettered in the text colour too, and the band's green, amber or grey shows as the tint and outline of each word. In the light theme those words had been too faint to read comfortably. A closed band's word is dimmer, so it recedes.
-
Conditions fits small windows and large zooms.
With the app pinned at a large zoom on a smaller screen (for example 175 % on 1920×1080), each side pane shrank to a sliver: its title was cut off and its pane picker and ✕ could not be reached. Now every pane keeps its title bar, with its picker and ✕, in view and a line of the pane under it, and where even that does not fit, Conditions scrolls. When the map is too narrow for both, as at 1024×768, the Layers panel starts folded so it no longer hides the band names in the Band conditions list; once you fold or unfold it yourself, your choice is kept. A window narrow enough to stack the panes in one column under the map no longer draws them over each other: each pane takes its own full height, and the stack scrolls.
-
Chase rows keep their country, and Chase DX says which map it opens.
In a narrow Chase or Chase Feed box the country and its beam heading were cut short ("South Orkney Is." showed as a few letters). Now, where the call, its need chip, the point button and the age leave them no room, they go on the line under the call, whole. Chase DX's tooltip said "Beam map, need-colored, live openings", but it has opened on the Globe since the map picker arrived; it now says "Globe, need-colored, live openings", in every language.
-
Operate at a large zoom: Call Roster, Band Activity and Rx Frequency show their rows.
With the app pinned at 100 % on a 1024×768 screen, Operate squeezed the decode panes down to their title bars with nothing to scroll, and at 125 % on 1366×768 they disappeared. Now the waterfall gives way first, each pane keeps a usable box that you scroll between, and past that the cockpit scrolls. The QSO strip with Stop TX and Tune stays on screen while you scroll. At 175 % on 1366×768 the strip used to sit below the bottom of the window, where the mouse could not reach it; the cockpit now scrolls to it. At the automatic zoom on a 1024×768 or larger screen nothing moves.
-
Tempo at a large zoom: the station list, the conversation and the waterfall rail no longer sit on top of each other.
With the app pinned at 100 % on a 1024×768 screen (or 125 % on 1366×768, 175 % on 1920×1080), all of Tempo's panes landed in the same place: the waterfall rail covered the station list and the conversation, and the station search box sat over the first Band Activity rows. They now stack one under another and Tempo scrolls.
-
Tempo's side panels no longer squeeze the conversation out.
Panel widths saved on a wide monitor, or panels dragged wide on a big window that was then made smaller, could leave the conversation between the stations list and the waterfall with no width at all. The two panels now always leave it at least 360 pixels, about a phone's width. When they have to give way, the panel you moved last keeps its width. A double-click on one of these dividers now resets only that panel; Reset layout still resets both.
-
Band Activity and Rx Frequency scroll instead of cutting off on a short window.
When a decode pane's header, with its filter chips, is taller than the pane (a small window with large text, or a big UI scale), the pane now scrolls and its decode list keeps at least one row. Before, the list and the lowest chips were cut off with no way to reach them. In the Classic layout the Tx1–Tx6 panel scrolls inside its column in the same situation instead of running off the bottom of the window. Nothing changes on a window where everything already fits.
-
At 1024×768 the Call Roster's QRZ link and the Stations filters no longer cut off.
A worked station's B4 and LoTW marks pushed the QRZ link (↗) out of the Call Roster's Call column, which is now a little wider; on a wide window nothing changes. On a narrow window the Stations filters in the Classic layout take a second line instead of cutting off the Needed filter.
-
A long callsign in the Logbook ends in "…" instead of being cut through its last letter.
The call column could not shorten a call the way the other columns shorten their text, so a call wider than the column was sliced off at the edge.
-
Easier to read in the light theme.
Words lettered in green, amber, red, grey or the accent colour were hard to read on the light page. In the light theme they now take the theme's text colour, and the colour stays beside them: as an underline, as a bar beside a line, or on the chip's or row's border.
- On Conditions: the Band Advisor's Open / Marginal / Closed, Band Outlook's Excellent / Good / Fair, its mode chips and its MUF, the band names in the 24-hour chart and the Best Band table, the Space Wx lines and scale chips, the Kp outlook's storm line, the Chase panes' need chips and "open now" lines, the openings' band names, Getting Out's reports, Satellite Passes' next pass time, the scope's AUDIO badge, and the satellite, rotor and amplifier panes' warnings. The Kp outlook's bars are dark enough to see.
- The NOW bar's band condition, who hears you, the top need, the Cluster, Phone and PSKR pills and PROP LIVE / PARTIAL / CACHED, and the LIVE / PARTIAL / CACHED / NO LIVE DATA chip on the map's bar and in DXpeditions.
- Need chips (NEW ONE, ZONE, BAND, MODE, GRID, STATE, LoTW, DXPED, POTA, SOTA and WATCH) in Band Activity, on the Call Roster and the Stations list, on the Needed board, in Spots and in Satellites.
- The POTA / SOTA board's HUNT, each spot's park or summit reference, its NEW PARK and BAND OPEN badges, and the park and call in the Hunting line.
- The band name on the band chip (the top bar, the cockpit headers, Phone's and CW's band picker, and Settings ▸ Station), where 20m's green read about 1.5:1, on the Logbook globe's band picker and on the Field Day band board, where the band's colour moves to an underline.
- The NEW tag on a propagation opening, now black on its amber, and the update prompt's Install and restart (or Download) button, now lettered in white.
-
Easier to read in the dark theme.
Need chips lettered their word in the need's own colour, which in many places was hard to read, and a DXPED chip nearly vanished; the word now takes the theme's text colour, the need's colour stays on the chip's border, and on a Band Activity row already in a need's colour that chip is an outline. The POTA and SOTA chips, and their marks on the band strip, the band map and the spot legend, take the theme's own green and purple. The Band Advisor faded a closed band's row, and Band Outlook a closed mode chip, by making them see-through; they now fade by their colour, so "Closed" and its reason stay readable. The six violet bands (2200m, 630m, 160m, 70cm, 33cm and 23cm) are lettered in a slightly lighter violet on the band chip, at least 4.5:1. On the hunted POTA / SOTA row the frequency and WORKED TODAY read clearly, and the Kp outlook's amber is a little lighter, with its storm red now the critical orange.
-
Checkboxes, sliders and other built-in controls follow Nexus's theme.
The parts of the screen your computer draws for Nexus (checkbox boxes, slider tracks, the arrows on number fields and a number of buttons) followed your computer's light or dark setting rather than the theme you picked, so with the two different some of their words could not be read. That covered the amplifier strip's Operate/Standby and band ◀ ▶ buttons, where the green word "Operate" all but disappeared, SSTV's manual-receive Start, the picture viewer's Previous, Next and Save, JS8's station queries and inbox Read, Delete, Cancel and Drop, the status chips at the top of Settings ▸ Radio, the Spot button in Operate's call roster, the × that removes an SSTV text overlay and the watch list's ×. They now follow Nexus's theme, and a Spot button with no station selected dims. POTA's Start and Download and the Satellites ⧉ now look like the rest of Nexus instead of plain grey browser buttons. Nothing changes when your computer's setting matches the theme, which it always does with the System theme.
-
One update prompt.
On Windows, macOS and the Linux AppImage, where Nexus updates itself, the "update available" notice with its Download button no longer turns up beside the prompt that installs the update. Settings ▸ Check for updates now works the same way: it downloads a newer version and offers to install it (again, even if you chose Not now), or tells you that you are up to date. If an update fails to install, its message now has a Download button that opens the download page. The notice still appears when Nexus cannot check for updates itself, and it stays on the .deb packages (the PC one and both Raspberry Pi ones). The PC .deb no longer downloads the AppImage in the background and offers an Install button that could not work there. Installing is still your call: Install waits while you transmit, tune, work a station, run CQ or have TX enabled, and the beta channel works as before.
-
Less work for the computer while nothing is happening.
The main window redrew itself two and a half times a second on a timer, even with nothing new to show, on top of the redraw that each new reading from the radio already brings. It now redraws only when something has changed. The unread counts in the Tempo station list update exactly as before.
-
Settings: commas, and spaces in the quick-reply chips, can be typed in the list fields (#370).
Six boxes on Settings ▸ Digital that hold a list ate the separator as it was typed, so
W1ABC,K2DEFcame out asW1ABCK2DEFand a chip could not sayTNX QSO: APRS-IS Watched calls, the digipeater path, JS8 Groups, and the Chat, QSO and Band / CQ quick-reply chips. Each box now keeps what you type, and shows the list as it was read when you leave it (@ARES, @SKCC). Save keeps what is in the box even when you press Enter without leaving it. A pasted list worked before and still does, and every list is read exactly as before: an empty digipeater path still means direct, with no digipeaters. -
The SSTV picture viewer no longer misses an arrow key pressed as it opens.
On a busy computer, a ← or → pressed the moment the pictures appeared could be ignored, because the keys were connected to the pictures a moment after they were drawn. They are now connected as the pictures appear.
Corrections to 1.15.0
A released section is history and is not rewritten, so a credit it overstated is corrected here.
-
#174
reads as if every new-one alert can be kept to the continents and countries you pick. Only the alerts raised from your own decodes can: the new-one, new-grid and CQ alerts. The Pounce new-one alert works from cluster and RBN spots and still sounds for a spot from anywhere, because it has no "spotted from" filter yet.
Every version
- 1.24.0 11 Nov 2026
- 1.23.0 5 Nov 2026
- 1.22.0 1 Nov 2026
- 1.21.0 26 Oct 2026
- 1.20.0 22 Oct 2026
- 1.19.0 16 Oct 2026
- 1.18.0 12 Oct 2026
- 1.17.0 7 Oct 2026
- 1.16.0 3 Oct 2026
- 1.15.0 26 Sept 2026
- 1.14.0 20 Sept 2026
- 1.13.0 16 Sept 2026
- 1.12.0 14 Sept 2026
- 1.11.1 8 Sept 2026
- 1.10.3 4 Sept 2026
- 1.10.2 3 Sept 2026
- 1.10.1 1 Sept 2026
- 1.10.0 31 Aug 2026
- 1.9.2 29 Aug 2026
- 1.9.1 26 Aug 2026
- 1.9.0 25 Aug 2026
- 1.8.1 23 Aug 2026
- 1.8.0 23 Aug 2026
- 1.7.6 21 Aug 2026
- 1.7.5 20 Aug 2026
- 1.7.0 18 Aug 2026
- 1.6.1 17 Aug 2026
- 1.6.0 16 Aug 2026
- 1.5.0 16 Aug 2026
- 1.4.0 15 Aug 2026
- 1.3.0 13 Aug 2026
- 1.2.0 10 Aug 2026
- 1.1.0 10 Aug 2026
- 1.0.5 8 Aug 2026
- 1.0.2 6 Aug 2026
- 1.0.1 5 Aug 2026
- 1.0.0 4 Aug 2026
- 0.28.2 3 Aug 2026
- 0.28.0 3 Aug 2026
- 0.27.0 2 Aug 2026
- 0.25.0 1 Aug 2026
- 0.24.0 31 Jul 2026
- 0.21.5 29 Jul 2026
- 0.21.0 29 Jul 2026
- 0.20.0 28 Jul 2026
- 0.19.7 27 Jul 2026
- 0.19.6 26 Jul 2026
- 0.19.4 26 Jul 2026
- 0.18.0 25 Jul 2026
- 0.17.22 25 Jul 2026
- 0.17.21 25 Jul 2026
- 0.17.20 25 Jul 2026
- 0.17.19 25 Jul 2026
- 0.17.18 25 Jul 2026
- 0.17.17 25 Jul 2026
- 0.17.16 25 Jul 2026
- 0.17.15 25 Jul 2026
- 0.17.14 25 Jul 2026
- 0.17.13 25 Jul 2026
- 0.17.12 25 Jul 2026
- 0.17.11 25 Jul 2026
- 0.17.6 25 Jul 2026
- 0.17.5 25 Jul 2026
- 0.17.4 25 Jul 2026
- 0.17.3 25 Jul 2026
- 0.17.2 24 Jul 2026
- 0.17.1 24 Jul 2026
- 0.16.4 24 Jul 2026
- 0.16.3 24 Jul 2026
- 0.16.2 24 Jul 2026
- 0.16.1 24 Jul 2026
- 0.16.0 24 Jul 2026
- 0.15.24 24 Jul 2026
- 0.15.23 24 Jul 2026
- 0.15.22 24 Jul 2026
- 0.15.21 24 Jul 2026
- 0.15.20 24 Jul 2026
- 0.15.18 24 Jul 2026
- 0.15.17 24 Jul 2026
- 0.15.16 23 Jul 2026
- 0.15.15 23 Jul 2026
- 0.15.14 23 Jul 2026
- 0.15.1 22 Jul 2026
- 0.15.0 21 Jul 2026
- 0.14.0 21 Jul 2026
- 0.13.0 19 Jul 2026
- 0.12.0 18 Jul 2026
- 0.11.1 18 Jul 2026
- 0.11.0 18 Jul 2026
- 0.10.0 17 Jul 2026
- 0.9.7 17 Jul 2026
- 0.9.6 16 Jul 2026
- 0.9.5 16 Jul 2026
- 0.9.4 16 Jul 2026
- 0.9.3 16 Jul 2026
- 0.9.2 15 Jul 2026
- 0.9.1 15 Jul 2026
- 0.9.0 15 Jul 2026
- 0.8.9 15 Jul 2026
- 0.8.8 14 Jul 2026
- 0.8.7 14 Jul 2026
- 0.8.6 14 Jul 2026
- 0.8.5 14 Jul 2026
- 0.8.4 13 Jul 2026
- 0.8.3 13 Jul 2026
- 0.8.2 13 Jul 2026
- 0.8.1 12 Jul 2026
- 0.8.0 12 Jul 2026
- 0.7.1 12 Jul 2026
- 0.7.0 12 Jul 2026
- 0.6.0 11 Jul 2026
- 0.5.2 11 Jul 2026
- 0.5.1 10 Jul 2026
- 0.5.0 10 Jul 2026
- 0.4.1
- 0.4.0
- 0.3.0
- 0.2.0 3 Jun 2026
- 0.1.0