jks

v1.332 has a fix that should work for any Kiwi "stuck" on v1.329 due to the first antenna switch extension issue. For those Kiwis stuck because of the second issue the manual intervention described above will be required. I have not found many Kiwis with this second problem.

v1.332 has a fix that should work for any Kiwi "stuck" on v1.329 due to the first antenna switch extension issue. For those Kiwis stuck because of the second issue the manual intervention described above will be required. I have not found many Kiwis with this second problem.

Got a Kiwi (running v1.330+) on your local network with an unknown local IP address? Like a new Kiwi out-of-the-box? Now from a browser on the same local network you can connect to my.kiwisdr.com and be automatically redirected to the Kiwi. The local IP address of the Kiwi will then show in the browser address bar.

This feature is similar to that provided by other IoT devices. It requires that the Kiwi have access to the Internet when it starts up. And that the computer running the browser is on the same local network as the Kiwi. If there are multiple Kiwis on the network the browser will display a table of Kiwis by serial number and a link that will connect to each one.

Our documentation lists 5 different methods of determining a Kiwi's IP address. But each has its limitations and disadvantages. Now there is a sixth method that is particularly convenient.

If you want to opt-out of your Kiwi sending this information to kiwisdr.com each time it starts then set the switch on the network tab of the admin page to NO: "Register this Kiwi on my.kiwisdr.com on each reboot?".

This feature has not been tested with IPv6 or mixed IPv4/IPv6 local networks. So there is likely some debugging required.

The only way you will get the "Sorry, this KiwiSDR server is being used for development right now" message is if on the "control" tab of the admin page you have set the "enable user connections?" switch to "no" AND you have left the "reason if disabled" field blank. Set the switch back to "yes" and you should be fine (no restart is required).

Above, the "ku" ("kiwi up") command was mentioned. But I think everyone meant to say "up" ("update") which is the command to manually update the software and rebuild from scratch. This is essentially the manual version of what the automatic software update does. See the link in Stu's post.

The "up" command cannot be used from the console tab of the admin page. That's why you get the error message (there is a different procedure needed in this case). The "cdp" "up" command sequence can only ever be used from a root ssh/PuTTY login to the Beagle. But that is not the solution that is needed here.

v1.318  August 27, 2019
    FAX extension:
        Add LPM (lines per minute) selection. Automatically set 60 LPM for JJC/JSC
        Frequency list corrections; added XSG Shanghai; removed BMF Taipei
    S-meter extension:
        Don't clear graph on frequency change. Instead draw vertical division marker: red when
        frequency change, green when mode change.
    Better detection of missing audio panner API on some browsers.