jks

He mentioned in his email to me (but not in the post above) that it was set in continuous mode.

Okay, I see what's wrong. It's because I'm an idiot.

Will be fixed in the next release..

The EXT socket you used to open DRM can be used to open any of the extensions. You just change ext_switch_to_client=X where X is the name of the extension as it appears in the extension menu on the Kiwi UI. As mentioned before, you can very easily use the browser debug window "network" tab to see exactly what socket command are being sent by the Kiwi Javascript client code -- commands that you will have to send yourself. This is much easier than reading the code to see what it's doing. Select the EXT socket and HTTP response tab.

A lot extensions can run without any parameters needing to be set. E.g. the cw_decoder, cw_skimmer and FT8 extensions because their default parameters will just work. All you have to do is somehow display their decoding output. In the case of the cw decoders that means processing the cw_chars=... message. And ignoring messages like cw_plot and bar_pct if test mode is active. For FT8 just process the chars=... message.

Send a close or stop and blur messages when done (varies by extension for historical reasons).

You can use the test mode message to debug with to get a strong pre-recorded CW signal that will decode 100%. Similarly for FT8 mode. No tuning to an active CW/FT8 frequency required.

@XPloRR Sorry, traveling on vacation. Squelch should work on NBFM/NNFM. I didn't write the squelch code so I can't give exact answers. But the squelch level value seems to change depending on the passband width. So a squelch-close value required for NBFM won't quite be the same as for NNFM. ANd similarly for the non-FM modes. But it should work (it does work if you try using the Kiwi UI).

Please see latest production status info at the end of this thread.

I received 5 prototypes three days ago (Oct 7) built by MacroFab. They work fine. I'm in the middle of characterizing them. The photo below lists most of the new hardware features (click for larger).

Some of the prototypes will be sent to beta testers who have exceptional reception and can split an RX antenna between a Kiwi-1 and Kiwi-2 so we can do some A/B comparisons. We should also have samples of the new enclosure soon.

@XPloRR Do you write iOS apps as well? We've had many requests for a comprehensive Kiwi iOS app over the years. But no success in getting anyone to do it who would be remunerated by selling licenses on the app store (i.e. we have no money to fund development ourselves).

Related: I mentioned previously that I bought a license. But currently there is no feedback when you enter the license key. So unclear if it's been accepted or not. Perhaps the linkage with the licensing backend isn't setup yet.

Cautionary tale from Clint KA7OEI's blog about an Ali Express "SDR TX/RX Switch": https://ka7oei.blogspot.com/2025/02/ali-express-sdr-txrx-switch-design-not.html

Hi John. Not sure what might have happened. The TDoA station list is generated dynamically by the same process that generates the rx.kiwisdr.com list, which in turn causes map,kiwisdr.com to be updated.

But the reference station list is static, and it disappearing would indicate more of a kiwisdr.com web server problem or Internet problem. The web server logs for the refs.cjson file at that time are:

[23/Jul/2025:12:13:29 +0000]

[23/Jul/2025:13:20:42 +0000]

(all UTC) So, the web server didn't see any requests at precisely 12:36Z. So my guess would be a temporary Internet routing problem between your location and tdoa.kiwisdr.com (same server as kiwisdr.com).

I didn't initially want enable the proxy service by default for Kiwi-2 (because of all the backend overhead/cost it incurs). But I got talked into it because so many people have Internet service with no incoming connections allowed these days (essentially anyone in the US and anyone on Starlink).

v1.7 includes the source code of the "chunk" package that was removed in Python 13 and replaced by "chunkmuncher". Which then could not be installed in all versions of Debian 13 (including a new package called "standard-chunk").

Including the source directly should eliminate all these problems (hopefully).