jks

There is a new version of the antenna switch extension available.

Important installation notes:

• Let your Kiwi update to v1.449 first.
• Use my repo, not Kari's, until he merges my changes (e.g. via "gclone" command below).
• Install can be accomplished from the Kiwi admin page "console tab".

Get a Linux shell either using the admin page console tab or ssh/PuTTY directly into your Kiwi. Type:

New features and fixes:

• Can limit access three ways: local connections only (owner/admin effectively), local connections plus users connecting with a password (for Kiwis with split user password access), everyone can access. For the split password case you must add "&p" to the URL as described here: http://kiwisdr.com/quickstart/index.html#id-user-urlp-prot
• Support for KMTronic LAN Ethernet IP 8 channels WEB Relay device. https://info.kmtronic.com/kmtronic-lan-ethernet-ip-8-channels-web-relay-board.html
• Other user connections are notified via a popup when the antenna is changed. The popup closes automatically after 3 seconds. This may need some refining. There has also been the suggestion that an autoscale be performed on an antenna switch if in auto aperture mode.
• Message is displayed to user if antenna switch parameters have not yet been configured by admin.
• Installation time is much faster as entire Kiwi software rebuild is no longer done.

If the Linux "lsblk" command doesn't see the mmcblk1 device (note "1", not "0" which is the on-board filesystem) then as far as Linux is concerned the sd card isn't plugged in (or recognized). The Kiwi software has nothing to do with it at that point. That's why the lsblk command is run in the script -- to show that state of the sd card before doing anything.

So while everything is still running try pushing on the sd card to eject (unlatch) it, then re-seat it and try the backup again. I sometimes find I have to do this a couple of times. I don't know why.

From the CHANGE_LOG file:

Look carefully at the BBG-W. Seeed violated the BeagleBone cape spec and the Kiwi board can't even physically plug into it (those double-high USB connectors physically interfere). As a result there has been no software development for it.

It's a huge headache to construct sd card images of the current release. So I don't do it often. v1.390 was the last. We all depend on the autoupdate over the network.

The build is progressing now, but very slowly. Something seems to be taking a lot of cache space in main memory. I don't understand why. There are no processes that seem out of place.

A USB-to-WiFi dongle is a lot of work and grief unless you know what you're doing.

A much easier solution is to use a wired-Ethernet to WiFi mini-router: https://www.tp-link.com/en/home-networking/wifi-router/tl-wr802n More info here: http://forum.kiwisdr.com/index.php?p=/discussion/1653/connecting-kiwi-via-wifi/p1

The worst problem there is dealing with the required 5V power input as the supplied adapter is a potentially noisy switcher. Although you might be able to get 5V from the BBG/BBB USB-A "host" port. Anyone actually doing that?

There is a fix for this in the next update. It's tricky because Kiwi owners may have arbitrarily edited the definition of bands[] in config.js in ways that my fix may not have anticipated. Although my fix tries to take this into account.

The whole situation will be better addressed when the contents of config.js are absorbed into the admin user interface and config database. But that's a complicated change that will not happen anytime soon.

Beginning with v1.436 the band identifiers will not be displayed if their frequency is less than the frequency scale offset. But the remaining empty white space is not reclaimed because right now that is difficult to do (for historical reasons). It will have to wait for a major rewrite of that part of the code.

Feb 2021: Alpha "Khabarovsk" (nearest town Elban) as received from the Kiwi in Khabarovsk about 200 km distant. MSK signals VTX3 India and NWC Australia also present.