jks

Thanks! I forgot that the URL scan list is also entered as the first entry in the local menu.

Someone was kind enough to make a review entry for the Kiwi over on eham.net

If anyone wants to contribute a review to the entry that would be very much appreciated.

Thanks

@dl7awl Sorry, there was some missing text on that page describing that the new button on the admin backup tab must be used. I've fixed that now.

@ww6d I'm surprised you thought some sort of formatting of the sd card was necessary. That should not be the case. The procedure writes the new Debian 11 image to the raw sd card device (no formatting required). Then afterwards mounts the created partition on the card to write the Kiwi configuration information.

Also, the documentation section you mention "Re-flashing once you have the SD card" is referenced directly at the end of the upgrade instructions (even including a link!) So there should not have been any confusion about this.

I think this is a conflict between who controls the LEDs during the sd card backup script running. I believe it's on my list of things to fix.

Update: Okay, fixed for the next release.

Yep, a typo made in the Verilog code last July if you can believe that. Didn't show itself until I built v1.807. Fixed in v1.808..

It's not automatic. I have to do it by hand. It's published every six months at eibispace.de

I see A25 is out, so I'll try and get that in the next Kiwi release.

Nice. Well, it's all about the field strength. Very likely you can build something useful that will not be detectable outside of your immediate location.

And, you can use your Kiwi to test it -- the timecode extension!

I just replied to your email before I saw this post. So I'll include my email reply here:

So it turns out the default dx.json is stored on every Kiwi in case it turns up missing during a software install. If you bring up the admin console try these commands to see the differences:

In my case it showed dx.json had a few new lines not present in the default file.

You can replace the "wc" (word count) with a "cp" to copy the default file to the current dx.json. You can use "diff" to see the actual text differences.

You should immediately restart (admin control tab) so the server doesn't overwrite the dx.json file you just restored.

If all channels are full you'd have to "kick" a channel via the button on the admin status page to create a free channel for you to connect.

Alternatively, you can reserve one of the channels by setting a user password on the admin security tab and then set "number of channels not requiring a password even if password is set" to 3 (assuming you're using 4-channel mode). Then that channel will always be available for your use. You won't have to actually give the password if you're connecting from the local network.

You could also use the "camp" interface to wait in queue for a free channel to become available if you don't want to permanently reserve a channel and don't want to kick someone. But you will be waiting an arbitrary amount of time in that case. The camp panel appears automatically when you attempt to connect when all channels are full.

It's fine to use the default serial number as the Kiwi name for a publicly listed Kiwi. Lots of people do that.

KiwiSDR 2 radios are available again in our online store: https://kiwisdr.nz

Thanks for your support.