Nexus 0.28.0
Released 3 August 2026. The current release is 1.24.0. Download it · Every version
Added: log a contact from the Satellites section
Reported after a clean pass: "the doppler shift change are working amazing, I was following the bird with my manual rotor and it was perfect. The problem came when I tried to log someone, as I dont have a spot to log within the satellites section to log my sat qso's."
There is now a log strip in the bird's detail column, directly under the Doppler readout. It is not a new form — it is the same log strip the Phone and CW cockpits use, with the same callbook lookup, the same recall card and the same prior-contact history, put where you are working the pass. It sits above the transponder cards and the globe on purpose: with both hands on a rotator and seconds between overs, a form at the bottom of the column is a form you don't use. It is there whether or not a pass is armed, and it stays after the bird sets, so you can catch up on a contact once your hands are free.
It logs an ordinary contact. The call, your dial, your band, the mode you are on, the time — exactly what the Phone strip logs from the same state. It does not tag the contact as a satellite QSO: LoTW wants the ADIF PROP_MODE and SAT_NAME fields for that, and Nexus does not write them. The strip says so under the fields, so nobody waits on satellite credit that isn't coming. If you want it, add both fields yourself in whatever you upload from — LoTW turns away a contact carrying only one of the pair, so half the tag is worse than none.
Three things it does not do yet. None of them is a decision that satellite work should stay this way — they are the price of dropping the existing strip in unchanged instead of building a satellite-aware one, and each is meant to be closed.
-
Your satellite grids land in the wrong place, in Nexus and at ARRL.
Nexus decides "was this a satellite QSO?" from
PROP_MODE=SATalone; LoTW wants that and the satellite's name. With neither written, a contact logged here counts toward neither the Satellite VUCC totals on the Awards screen nor the satellite needs board — and its grid does not simply go uncounted. Nexus keeps per-band grid counts for 160 m through 2 m only, so anywhere outside that range — 2200 m and 630 m below it, and 1.25 m, 70 cm, 23 cm, 13 cm, 9 cm, 5 cm, 3 cm and 1.2 cm above it — the grid lands nowhere at all. On the bands that do have a slot — for satellite work that means 2 m, the downlink of every U/V bird, and 10 m, where AO-7's mode A comes down — it lands in your terrestrial VUCC count for that band, which is a grid ARRL's rules say a satellite QSO does not earn. LoTW files the upload the same way. If you chase VUCC, add both fields by hand before you sign. -
During Field Day it logs to the general log, not the contest log.
The Phone and CW strips switch to the Field Day log while a session runs; this one is not wired to Field Day yet, so a satellite contact made during FD scores the club nothing. Log those from the Phone or CW cockpit for the duration — adding them to the FD log later files them on the band you are on then, not the band you worked.
-
The recorded mode comes from your sideband
, so it names a voice mode when you are on a data mode:
SSBon the WSJT-X tiers (every channel there commands USB),FMon Tempo's three FM simplex channels. Right for voice and CW, wrong on a data mode. Log a contact from another radio lets you set the mode by hand, but its picker offers SSB / FM / AM / CW / RTTY / FT8 / FT4 and nothing else — so of the data tiers it covers FT8 and FT4 only. On Q65, JT65, MSK144, WSPR, FST4 or Tempo, log the contact and then correct its Mode in the Logbook, whose mode field takes any text. All three are written up in the guide's satellite chapter.
Fixed: contacts logged during a pass no longer carry a satellite name LoTW rejects
This one is in the version you are running now. Since 0.24.0, any contact logged while you had a transponder held was written with PROP_MODE=SAT and a SAT_NAME — and the name was the bird's catalog name, "SAUDISAT 1C (SO-50)" rather than "SO-50". LoTW rejects a record naming a satellite it doesn't recognise (ARRL: "if you enter the satellite name as AO7 instead of AO-7 the data will be rejected") — the signing tool won't even sign it — so those contacts could never earn satellite credit, and the batch each one rode in came back marked Rejected.
It also caught contacts that had nothing to do with a satellite. The hold is only handed back when the pass ends — and a transponder you pick without arming a pass is never handed back at all — so an HF contact made an hour later got tagged as a satellite QSO too, and went out that way to LoTW, eQSL, ClubLog, QRZ Logbook and Cloudlog.
Nexus no longer writes either field for any contact it logs. Records that arrive carrying them — a foreign ADIF import, or one you fixed by hand — are untouched, on import, on export and in the logbook.
That has a cost inside Nexus too, and it is not permanent. The same PROP_MODE=SAT field is what Nexus reads to decide a contact was a satellite QSO, so with nothing writing it your Satellite VUCC totals and the satellite needs board no longer see contacts Nexus logs for you either — and on a band Nexus keeps a per-band grid count for (2 m most commonly, since it is every U/V bird's downlink) the grid is counted toward your terrestrial VUCC for that band instead, which is not a grid a satellite QSO earns. Writing a satellite name Nexus can stand behind is work that has not been done yet, not work that was ruled out.
Writing just PROP_MODE=SAT is not a shortcut — that was looked at and rejected, not overlooked. TQSL refuses to sign a contact whose propagation mode is SAT when it names no satellite ("PROP_MODE = 'SAT' but no SAT_NAME"), exactly as it refuses a name it doesn't recognise. Half the tag costs you the whole QSO at LoTW — including the DXCC and WAS credit an untagged upload does earn — and it takes the upload with it: Nexus asks TQSL to skip bad records rather than abort, so the batch signs without that one and comes back marked Rejected, and it will keep coming back that way every time you upload while the record is in your log. Until Nexus can write a name it can stand behind it writes neither, and adding both fields by hand restores everything: the LoTW credit on your next upload, and the in-app totals the next time Nexus starts and re-reads the log file.
Contacts already logged that way are left alone, and deliberately: some of them were real satellite QSOs that want the name corrected, some were ordinary contacts that want the tag gone, and nothing in the record tells them apart — that call is yours. To find them, search your log file (~/.config/tempo/log.adi, or %APPDATA%\tempo\log.adi on Windows) for SAT_NAME, and edit it there with Nexus closed. The guide's satellite chapter walks through it.
Fixed: the microwave bands go out to N1MM / N3FJP in metres
The band field on the club-log wire is a metre count — "20", "0.7". Nexus converted 70 cm, 33 cm and 23 cm by hand and guessed at everything else by chopping the letters off the end, which cannot tell centimetres from metres. So every other centimetre band left as a bare number: a 13 cm contact was broadcast as "13", a 3 cm contact as "3".
Those are not hypothetical bands. The Q65 band plan ships 13 cm, 9 cm, 5 cm, 3 cm and 1.2 cm channels (JT65 the first three), and the band you pick is the band that goes on the wire. Nobody is known to have been caught by this — what is on record is that Nexus could send it.
Centimetre bands are now converted by the same rule the three hand-written ones already followed, so 13 cm goes out as "0.13". The three values that have always gone out are unchanged, no band was added to any list, and nothing else about what Nexus broadcasts moved.
Fixed: the ⊞ Panels menu no longer offers a checkbox that changes nothing, and it gains a Voice Keyer entry
From the bench: "what do the Panels selection / deselection of Rig Scope Controls and TX meters do on the Phone tab? I don't see them anywhere on my screen whether enabled or disabled. Nothing falls away when I uncheck either of them."
Both entries were live checkboxes with nothing behind them on that station. Rig Scope Controls — and its twin, Scope Controls in CW — drive the radio's own panadapter: the span you set there changes the hardware sweep, not the on-screen zoom. On the audio bandscope there is no rig scope to command, so the pane cannot appear however the box is ticked. TX Meters work, but in Phone and CW the meters read only while you are keyed, so on receive there is nothing on screen either way — and the one moment the tick shows is mid-over, when you are not in a menu.
The menu now says which is which, the same way the DSP row has always only offered the functions your rig reports. An entry with nothing on screen behind it right now carries the reason in a line under it — "your radio is not streaming its own scope — these appear with an Icom CI-V or FlexRadio panadapter" — so you learn why instead of hunting for a pane that was never going to mount, and the line clears by itself the moment a native scope streams. TX Meters carry "readings appear on transmit" in Phone, CW and Operate alike. Nothing is removed from the menu: an entry with a reason on it tells you more than a missing one.
The same two questions turned out to have five more answers in the same menus, and they read the same way now. In Phone and CW, DSP Functions / DSP Toggles and RX DSP Levels depend on what your radio reports over CAT — on a rig that reports neither, those panes could never appear and the boxes did nothing. In CW, Sent Echo holds what you have transmitted this session, so at every start-up it is empty and its box moved nothing at all until your first over; it now says so, and the line clears when you send.
The line explains the screen; the tick is still yours. Every box in the menu can be ticked and unticked whenever you like, whatever your rig is doing, and what you choose applies the moment that panel has something to show — untick Sent Echo at start-up and it stays away after your first over, instead of making you transmit before you can hide a panel you do not want. Once you have unticked one, its line goes: the panel is off your screen because you said so, and a note still claiming your rig is the reason would be telling you something that is no longer true. Tick it back and the line is there again in the same instant, if it still applies.
The menu also gains one entry it never had: Voice Keyer in Phone. If you work with a mic and never touch the F-key slots, you can now put that pane away and the panes around it take the room. It was held out until now by a blunt rule — nothing that transmits gets a checkbox — and the rule is narrower now, because what it was really protecting is one thing: you must never be unable to stop a transmission. That is held by the controls that sit outside the panes entirely: on Phone, PTT in the transmit bar (and the Space bar, which is the same key), Stop TX and Tune in the header; on CW, Stop TX and Tune, and Esc, which does what Stop TX does; on the Operating screen, Stop TX and Tune in the operating strip, and Esc; on RTTY, Stop TX, the TX-enable button and both aborts in the transmit bar; on SSTV, Stop and the TX-enable button. None of them is in a Panels menu, so no combination of ticks and no saved layout can put them out of reach — that is the guarantee, and it is the only thing the rule protects.
Two buttons on the Operating screen are worth naming because they are not on that list, and an earlier draft of this note said they were. TX On/Off turns transmit off for the next cycle and lets the over already going out finish — that is deliberate, it is how WSJT-X's Enable Tx behaves, and the button says so when you hover it. S&P stops a CQ run and drops what is queued behind it; it does not cut the over on the air. Stop TX is the immediate halt on that screen, and Esc reaches it without the mouse. On RTTY and SSTV the TX-enable button does cut the over in flight, because those modes have no next cycle to wait for — which is why it is on their lists and not on Operate's.
Everything else follows from it. Whether a pane can start a transmission has nothing to do with whether you can put it away — the Operating screen's Tx messages and its decode lists have always been yours to hide, and Stop TX sits in the operating strip either way. And a pane may carry a stop button of its own, which goes away with the pane: the voice keyer's ■ Stop is one, and RTTY's Auto on toggle is another. Those are conveniences sitting on top of the guarantee, not the thing holding it up. Put the voice keyer away mid-message and you lose its ■ Stop — and Stop TX, Tune and PTT are all still exactly where they were.
Separately, and because it is worth telling you rather than because anything requires it: unticking Voice Keyer while a message is playing stops the message rather than leaving it transmitting behind a pane you just closed, and it throws away a recording you are part-way through making. Neither is what "hide a pane" sounds like, so the entry says both before you tick.
Undo last change puts the keyer away by the same door, so it now says the same thing before you press it. (Untick the keyer, tick it back, start a recording, press Undo — the recording used to go with no word at all.) And whichever door you came through, Nexus says what it did when it did it: an over it cut short, or a recording it binned — so walking off the Phone screen without opening a menu tells you too. Stopping an over used to be the silent one of the two, which was backwards. If the recorder cannot be stopped, that is what it says, instead of reporting a discard that did not happen.
Reaching all of this from the keyboard works the way the rest of Nexus does: every entry is a tab stop, takes focus with an undimmed focus ring, and reads its reason aloud with the panel name — the operator who cannot see the line under it is the one it was written for. Esc closes the menu and puts focus back on the ⊞ button you opened it with, instead of dropping you at the top of the app to tab your way back down. A panel you have torn off still reads as "popped out", but the words no longer run into the panel's own name when a screen reader speaks it — and that tag no longer sticks. Only the Operating screen's panels were being un-popped at start-up, so a "popped out" recorded anywhere else stayed on the entry for good, over a panel that was in fact sitting docked in front of you. Every screen's panels are checked at start-up now. And the menu itself no longer runs off a short screen: with eight entries and their reasons it scrolls inside its own box, so Undo last change and Reset layout stay where you can reach them at any window size or UI zoom.
Fixed: the focus outline in light mode was a hair under the readable minimum
The ring Nexus draws around whatever has keyboard focus is one colour used everywhere. In light mode it measured 2.999:1 against the page background, where the accessibility standard for a focus indicator asks for 3:1 — not enough to look broken, and enough to be genuinely hard to follow on a bright screen or a laptop panel at an angle. It is the same blue, one shade darker, and it clears the bar on the page, on panels and inside the ⊞ Panels popover. Contrast for the ring is measured in the test suite now rather than inferred, in both themes.
Fixed: a rotator that stops answering no longer takes the dial with it
Reported from a live pass: "I saw a first Doppler shift, then it snapped back to the none statement", and "after 5 seconds it snaps back to 'None — leave the dial to me', even though I didn't change it."
One cause behind both. When rotor commands stopped getting answers, the track gave up on the rotator — correctly, rather than hammering it for the rest of the pass — but it ended the whole pass on the way out. That ran the end-of-pass handback: your transponder went back to none, Doppler stopped, and the picker in the Satellites section reset itself a couple of seconds later. A track that never had a rotator was fine; a track whose rotator quit lost the radio too.
The mast and the dial are separate things now, and losing one does not surrender the other. A rotator that stops answering is let go and nothing else changes: the pass clock, the Doppler correction and the transponder you picked all run to a real LOS. The track stops claiming an antenna — it drops to Doppler only and shows no commanded angles, because it is not commanding anything — and it tells you, once, that the rotator went quiet and the pointing is yours. The sky dome keeps showing where the bird actually is, which is what you need to turn the antenna by hand.
Losing the pass itself is unchanged: the bird setting hands your dial back, and so does the rare case of orbital elements the propagator can no longer follow — there, the same model computes both the pointing and the Doppler shift, so there is no correction left to make and holding your radio would be a lie.
The rotor readout in a cockpit header keeps up with it. That strip shows a dim "ROTOR —" when a rotator is configured but silent, and it used to show only that — so a pass that had just lost its rotator, and was still steering your radio, went nameless everywhere outside the Satellites section. It now shows both: the honest dash for the mast, and beside it the bird, what Doppler is holding, and the ■ that stops the track.
At the end of a pass whose rotator went quiet, Nexus still sends one stop — the controller may be back by then, and a stop can only ever take motion away. It does not run "park" or "go to ready" for that pass: you were told the pointing was yours, so the antenna stays where you left it. A pass that kept its rotator parks as configured, unchanged.
Fixed: changing band or radio no longer kills your PTT
Reported from the bench: work a satellite on the Icom, come back to Phone, pick 20 m — which hands the station back to the Yaesu — and the PTT button pressed but the radio would not key. Nothing on screen said why. The cure the operator found was leaving the section entirely: go to FT8, come back to Phone, and PTT worked again.
Under the hood, a band change and a radio handoff both stop transmit — they have to, or the FT8 sequencer would keep calling a station that is no longer on your band, and a switch would leave a carrier up on the rig you just left. Stopping transmit also drops the Enable-TX latch, which is right for FT8: the sequencer would otherwise re-arm itself on the very next slot. But in Phone, CW and RTTY that same latch is the microphone, and the Phone cockpit has no switch for it — so the latch went down and stayed down, your press was quietly discarded, and only re-entering an operating section (which arms transmit on the way in) put it back.
Those halts now put the latch back exactly where you left it, in Phone, CW and RTTY only. The carrier is still cut, a held PTT is still released, and the newly selected radio still comes up unkeyed — the switch just does not take your microphone away with it. Everything it never should have touched is untouched: FT8 still stands down on a band change, TX Off still means off across a QSY, a tripped transmit watchdog still holds, and Stop TX still means stop in every mode.
This covers every way the active radio can change — band routing, satellite routing, band coverage, and the radio button in the top left — plus a band change with no switch at all, and spinning the rig's own VFO across a band edge.
Keeping the microphone across a switch means the radio loop can now be asked to transmit during the moment a two-radio handoff is still in flight — the fraction of a second where the app is holding the radio you just switched away from. It will not: nothing keys in that window, and the same rule covers a tune carrier, a queued CW word, an RTTY over, an APRS beacon, a voice message, an SSTV image and an FT8 slot. Most of that work is held rather than dropped and goes out on the right radio a moment later — a mic press you are still holding, a tune, a queued CW word. What is timed to a slot is not held: an FT8 over whose slot boundary passes during the handoff is missed rather than sent late, which is the right answer for a mode where a late transmission is a wrong one. Testing CAT works the same way: while the port is handed to the baud-ladder probe, the app will not report a key it cannot actually send.
One thing deliberately does not follow you: another program sharing the radio through the CAT broker. Your own microphone stays live across a band change because you made it; a shared client cannot see that you moved until its next poll, so its key is refused until you arm transmit again — exactly as before.
Fixed: picking 160, 80 or 40 m in Phone no longer lands on a locked-out frequency
Pick 40 m from the Phone band list as an Extra and the radio landed on 7.1250 — the exact bottom of the Extra phone band. On the low bands you transmit below the dial, so a signal there runs 2.8 kHz under the band edge: the app locked transmit out, the PTT button came up 🔒 TX LOCKED, and it did it on a band you are fully licensed for. The same thing happened on 160 and 80 m, at every license class.
The band list now parks you a full sideband clear of the edge — 7.1278 for that Extra, 7.1778 for a General — which is the first frequency you can legally key on that band. It is the same place switching into Phone has always landed; the band list was the one path that had its own idea. The high bands are unchanged: there you transmit above the dial, so the segment start was already clear.
Fixed: "pin this radio" on a pass now holds
Reported from the bench: "I tried pin this radio and it goes pinned, then goes unpinned." The switch showed 🔒 for a moment and flipped itself back to 🔓 a couple of seconds later.
Peg-lock belongs to the live radio roster, alongside which rig is active and how bands route to it. Saving the settings form can never move any of that — a form loaded before you switched rigs would otherwise yank you back to the old one — so the roster is put back exactly as it was after every save. The pin on the pass rail was written as a settings save, which meant it was one of the things being put back: the click went nowhere, the switch lit anyway, and the rail's own two- second re-read of the setting showed the truth and turned it off again. It now goes through the control that owns the setting, the same one behind the 🔒 in the top bar, so it sticks until you click it again.
Worth knowing if you saw this: the pin was not merely failing to display. It never engaged, so a transponder pick could still hand the bird to whichever rig your routing preferred, exactly the thing you clicked to prevent.
Fixed: a Doppler correction no longer rewrites the mode every three seconds
From an operator's CI-V trace of a live pass: 110 seconds carried 38 mode commands and 38 data-mode commands — one pair per Doppler correction — on a bus already busy with the dial, the meters and the panadapter. On an Icom a mode write can bump the filter with it.
A Doppler step was arming the same "apply this now" flag an operator's own QSY uses, and that path re-asserts the mode deliberately: picking CW while already on a CW frequency has to command the radio to CW. It also clears the give-up ladders — and that was the worse half. Re-armed every three seconds they could never fire, so a radio that cannot reach a downlink would be asked for the whole pass instead of being given up on once.
Corrections now move the dial and nothing else. They reach the radio on exactly the same loop pass they always did — the mode still follows a bird change, a section change or a re-arm, and the dial still gets there every few seconds.
Added: Lock on — put the radio back on the bird
Move the dial inside the transponder's passband and Nexus already follows you: that is you chasing a station across the passband, and your uplink moves with you (mirrored, on an inverting bird). Move it outside — by hand, or because the rig came back somewhere else — and the dial is somewhere the pass does not describe, with no way back short of hunting for the transponder you already had selected. Lock on is that way back: one click re-runs the pick you already made, so the routing, the band, the commanded mode and both legs all come with it, and you land back in the middle of the passband.
It sits on the Dial line under the bird's name, with the line that names the rig being driven, and it is there from the moment you pick a transponder. That is the point: picking one tunes the radio straight away, so the dial is live — and can get away from you — long before you arm a pass and long before the bird is up. The way back is there through all of it: pick made and nothing armed, a pass armed and waiting for AOS, and mid-pass with Doppler correcting. The one state it stays out of is the one where it would have to guess. With no transponder picked there is nothing to put you back onto, and picking one for you would be picking your uplink.
Fixed: the radio mode now follows the transponder, instead of staying in FM
Working a pass, picking an FM bird and then a linear one left the radio in FM — on a linear transponder, which is silence. Reported from a live session: "should I expect the radio modes to change when I move to each one like in other areas? It's not; it's staying in FM."
The satellite path could force FM and could force nothing else. An FM bird (SO-50, AO-91, the packet digipeaters) parked the rig in FM, correctly — but a linear, CW or beacon transponder asserted no mode at all, so the radio fell back to whatever the terrestrial section policy said. For a station whose Phone mode is FM — one station-wide setting, written whenever you tune an FM repeater, and reset by nothing — that policy answers FM on every frequency above 29 MHz. SO-50 and RS-44 are both on 70 cm, so nothing incidental cleared it either. Picking a hand-chosen FM in the Phone cockpit during an FM pass had the same effect and lasted longer: that choice only expired on a band change, so it outranked every later linear pick for the rest of the session.
Now a held transponder names the mode in both directions, and a new pick re-asserts it over a mode chosen for the previous bird. What the transponder decides is FM-versus-linear and which sideband; what your operating section decides is the form — plain SSB in Phone, the DATA submode in Digital, CW in the CW section. So FT8 through a GEO transponder still gets DATA (plain USB there transmits no RF on a normally-wired rig).
And you can always overrule it. The transponder's mode comes from SatNOGS, whose vocabulary is open and crowd-maintained, and plenty of birds get worked in ways nobody wrote down — so picking a mode by hand in the Phone cockpit during a pass now wins for the rest of that pass, on an FM bird as well as a linear one. The uplink stands down at the same moment rather than swapping sidebands underneath you, which is what it already did. Picking a transponder again is you asking for that bird's tuning back, and re-asserts it. (Previously an FM bird could not be overruled at all: it was decided above the mode picker, which is exactly the case Nexus is most likely to have wrong.)
Two judgement calls worth stating, because they are deliberate:
-
A transponder that advertises CW is worked in USB, not CW.
Through a linear transponder you copy the tone inside the SSB passband — that is how it is done, and it is what everything in Nexus's passband and Doppler model already assumes. Commanding the rig's CW mode would make the displayed dial mean something rig- and menu-dependent while Doppler is steering it, and it would lose an inverting transponder's sideband swap entirely. A CW beacon is not special-cased for the same reasons; it copies perfectly well as an audio tone in USB.
-
A transponder that publishes an LSB downlink is now put in LSB
and its uplink mirrored accordingly. That was an inverted-sideband error before — the exact mistake the transponder machinery exists to prevent — and on an inverting bird it inverted the uplink with it. Data downlinks (BPSK, PSK31, FT8, MFSK and the rest) are worked on the linear path as they always were; only the FM-carried ones (AFSK, FSK, GMSK, DUV, satellite SSTV) command FM, unchanged.
Fixed: a satellite downlink Nexus cannot name is no longer refused
"There are some frequencies that say in sat that it isn't in my band plan — you should allow me to go to those." Correct, and the refusal was ours, not the law's. Nexus's band table stops at 23 cm, so QO-100 at 10.489 GHz — and every IC-905-class microwave bird — was declined with "outside the band plan", on an operator running Open class with no restriction of any kind.
The band table exists to route a QSY to the right radio and to label a contact. It is not a permission system, and it was never asked whether the tune was legal. A downlink it cannot name now tunes like any other, and the missing label is reported as missing rather than guessed: the pass rail drops its band chip but still names the rig and the frequencies, the log strip drops the band slot instead of printing an empty one, and the logged band is left empty with the frequency carrying the truth.
Routing still works, and works from what you actually wrote. A rule that names bands cannot claim a dial that has no band, and no per-radio band list is consulted (asking either with a blank would have matched every catch-all and sent the bird to whichever rig owns "everything else"). But a rule with no band selector — "satellite work goes to the IC-9700", the shape Nexus itself recommends — answers the same for every band and therefore for no band, so it still routes these birds to the rig you designated. Where nothing answers, the existing fallback applies: if the active rig cannot reach the downlink and exactly one other radio could, the pass goes to it.
Nothing about transmit permission moved. The licence-class gate is a separate check on the transmit path and is untouched: an Open-class operator may key 10 GHz, and a Technician or General is still locked out there exactly as before. The 0.27.0 refusal that declines an unverifiable cross-band split on the Main/Sub Icoms is also unchanged — it deliberately fails closed when it cannot prove both legs share one band, which is still the case above the table's ceiling, so the band table was fixed around rather than extended.
Fixed: a refused satellite uplink now says what to change
Both satellite split refusals were true and neither told the operator what to do about it. On an IC-9700 holding a cross-band bird under a VFO A/B mapping, the CAT status explained that Nexus has no verified cross-band A/B split for that radio and that nothing was written — and stopped there, with the working layout one selector away and unnamed.
Each refusal now ends with a cure clause chosen by the radio in play, using the same rule the CI-V daemon itself uses to decide whether it can serve a rig:
-
An IC-9700 or IC-905 on a serial/USB port.
The A/B refusal names the layout that does carry a cross-band uplink there — Main = downlink / Sub = uplink — and both places it can be picked (Settings ▸ Radio ▸ Satellite Doppler, or the mapping selector on the pass rail). Ask for that layout while something other than Nexus's own CI-V backend is serving the radio and the refusal names the switch that changes it (Settings ▸ Radio ▸ Rig Control ▸ Native Icom CI-V), plus Test CAT for what is serving right now. It names the switch rather than telling you to turn it on, because it may already be on.
-
An IC-910 or IC-9100, and any radio reached over the network rather than a serial port.
There is no cure to name, so none is invented: the refusal says the native CI-V backend has no path to that radio, so no VFO mapping carries that pass's uplink there. No switch to hunt for, and no selector to work through one entry at a time.
-
Every other radio that can reach the Main/Sub refusal
— the mapping can be picked on any rig — gets the same honest dead end. What is refused has not changed, and neither has the transmit path: these refusals still write nothing to the radio, still transmit nothing, and still leave the receive dial being corrected wherever it already was.
Added: the pass rail offers the mapping that can carry the pass
Naming the working layout in the CAT status is one thing; you still had to go and set it. The pass rail now offers it — one click, on the button that is already there.
Nexus suppresses every uplink offer once you have chosen and confirmed a mapping, so it can never nag you into replacing your own choice. That rule is right everywhere except one place: when the mapping you chose provably cannot carry the pass you are on. Then the rail shows switch mapping, naming the layout that can and the radio it applies to, and the Doppler row stops reporting an uplink it is computing and having refused every tick.
Offering a correction to a choice that cannot work is not overwriting your choice. Nothing changes until you click:
-
The offer appears only when the uplink was genuinely written and genuinely refused for this pass, on a radio where…
The offer appears only when the uplink was genuinely written and genuinely refused for this pass, on a radio where Nexus's own CI-V backend is switched on and can serve it — i.e. only when switching actually gets you an uplink.
-
A mapping that works is never second-guessed.
Work a V/V bird on VFO A/B on the same IC-9700 and the rail says nothing: that is how that pass is worked, and the split lands.
-
Where no working mapping is known — an IC-910, an IC-9100, a network-connected rig, or an Icom whose native CI-V is…
Where no working mapping is known — an IC-910, an IC-9100, a network-connected rig, or an Icom whose native CI-V is switched off — nothing is offered, because there is nothing that one click could fix. Those stations get the refusal text above instead. The click goes through the same confirmation path as every other mapping change, records it for the radio the button names, and still means Nexus writes nothing to the transmit VFO you have not consented to.
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