v1.823, 824
From the CHANGE_LOG file:
v1.823 November 16, 2025
DX label frequency list menus:
When click-holding on a DX label a menu will now appear if there are multiple labels that
have the same label text. The menu allows the frequencies of these multiple labels to be
selected directly. This works for all the label databases: stored, EiBi and community.
Example: Click-hold on the 10 MHz WWVH/WWV label and a menu with all the WWV frequencies
(2.5, 5, 10, 15, 20 MHz) appears. A menu entry "open ext" will be shown if a label has an
associated extension. If a label only has a single frequency (e.g. WWVB, DCF77) click-holding
will immediately open the extension (if any). Type 'h' with the cursor in the label area for
a complete description.
Updated to EiBi-B25 database. (thanks MeolsKopite)
Proxy service: The proxy service client (frpc) is now managed in its own process such that it
will better respond to timeout / restarts when the Kiwi restarts faster then the network router.
For example after a power failure.
When the current frequency is exactly between adjacent or overlapping bands the frequency step
buttons now make more sense. Example: Current frequency is 7300 kHz when in ITU R2 (Americas)
mode where the 40m amateur band ends, and the 41m broadcast band begins, at 7300.
Previously the leftmost "-" step button (or 'alt-j' shortcut key) would step down -5 kHz into
the amateur band instead of -1 kHz as it should. (thanks Steffen)
Admin GPS tab:
Checkbox "Acquire if Kiwi busy?" now defaults to checked (true) for a new Kiwi run for the
first time. This change will not disturb any change to the setting you may have made using
the admin interface. (thanks NU6F)
Added SBAS satellites for development purposes. No SBAS corrections are currently done.
TDoA: Changed timeout value so message "Timeout: excessive runtime" will appear instead of the
more obscure "Protocol timeout" when the TDoA algorithm runs too long.
Added IP address to the "denied connection" log messages triggered by bots. (thanks F5LFE)
Comments
Good morning...
I don't know if it's my problem, but after the latest update, extensions are no longer automatically activated if managed in the Extension field in the DX labels.
I noticed that the extension is activated if I press Shift and right-click, having to choose it as the first item in the menu that opens as the first item in the list.
Yeah, I kind of goofed with that. For now instead of shift-right-click just click-hold to get the menu with the "open ext" entry. Shift-right-click also gives you the browser's right-click menu which is awkward.
I'll revert behavior of the shift/ctrl/alt/option modifier keys in a new release here shortly.
Okay, fixed in v1.824. Apologies for that.
An email I sent to the guy who requested SBAS support (which will be under development for some time). SBAS is Satellite Based Augmentation System. Geostationary satellites providing GPS location improvement data.
So v1.824 of the Kiwi software has SBAS selection and tracking (with some problems). It's mostly so I could try it on Kiwi's in various locations and see the status of the received SBAS sats and what message types (MTs) they are receiving. So far I've only checked from here in NZ (122:SPAN/AU-NZ, 130:BDSBAS/China, 137:MSAS/Japan) and the UK (121,123,136:EGNOS/EU). There is no MT decoding other than tow/week from MT12 and almanac status info from MT17. Lots of work needed.
To use, go to the admin GPS tab. Uncheck Navstar, QZSS, Galileo. Click SBAS "Select" button. Menu appears. Click "log msgs" entry. Re-select menu. Click "all" entry. After a while you should see SBAS entries in the channels with colors appearing in the "subframe" column if MTs are being seen. The subframe numbers don't correspond to MT numbers since there are 64 MTs. Currently the subframe number is just incremented and blinked when a new MT is detected.
Once you know which SBAS sats you can hear you can use the "none" menu entry to clear the list and then select just the ones you want to search for (to speed up the search).
There is a bug currently that enabling the SBAS mode breaks the regular Kiwi user connection realtime response (i.e. the audio breaks up etc). I'm trying to figure out why. No doubt related to the higher nav data rate of the SBAS sats.
With "log msgs" selected you will see various messages in the admin log tab related to SBAS.
Examples:
S130 MTs seen: 0 2
S137 MTs seen: 2 7 9 10 18 26 28 63
S122 MTs seen: 0 1 3 4 7 9 10 12 17 18 25 26 27 62
S137 MT17 status: #0 S137 ranging=0 corrections=1 integrity=1 service=MSAS
S137 MT17 status: #1 S129 ranging=0 corrections=1 integrity=1 service=MSAS
The "S" indicator in the status column of the GPS tab:
Blue: An MT0 was seen indicating sat should not be used for high-precision safety-of-life applications (e.g. aircraft landings)
Green: MT0 not seen (S137 MSAS/Japan is an example of this)
Good introduction: https://sgu4823.wordpress.com/wp-content/uploads/2012/11/l4-2_sbas_signal.pdf
Very interesting, thanks. Couldn't the timing accuracy be further improved, if the location was assumed to be stationary?
Yes. See here about RTK: https://en.wikipedia.org/wiki/Real-time_kinematic_positioning