jks

Just change the hardcoded "dtb-4.14-ti" to "$(DIR_DTB)". That's what I've done for the next release.

Sorry (for those of you old enough: )

Hi Mark,

This is a common problem, so you're in good company. I have emailed you two API keys for your Kiwis. Just enter them in the appropriate place on the connect tab of the admin page with the hostnames of your choice (presumably "emeraldsdr" and "emeraldsdr1"). Make sure to change the menu item at the top of the page to say "reverse proxy". Then use the restart button on the admin control tab.

The DDNS becomes irrelevant when using the proxy. Your hostnames will be emeraldsdr[1].proxy.kiwisdr.com:8073 (note: always 8073)

Hi Mark,

This is a common problem, so you're in good company. I have emailed you two API keys for your Kiwis. Just enter them in the appropriate place on the connect tab of the admin page with the hostnames of your choice (presumably "emeraldsdr" and "emeraldsdr1"). Make sure to change the menu item at the top of the page to say "reverse proxy". Then use the restart button on the admin control tab.

The DDNS becomes irrelevant when using the proxy. Your hostnames will be emeraldsdr[1].proxy.kiwisdr.com:8073 (note: always 8073)

Ha, I know what this is. Because SAS is producing twice the data, like IQ mode, that fact needs to be taken into account by the internal recording code.

Already fixed for the next release..

Alright, so as soon as I mentioned the idea of taking a royalty cut to fund the increased component cost Seeed's attitude about the production situation changed instantly. We're working now on getting another 100 units built.

So it appears the Debian project and Beaglebone.org have stopped making updates to the Debian 8 (Jessie) release. For the Beagle, Debian 8.11 seems to be the last release. It has been run by a number of customers for a long time and also by us. So it seems safe now for Kiwi owners generally to do an upgrade and get the benefit of whatever security patches there have been between 8.5 and 8.11.

To do this login as root using ssh/PuTTY and use the following commands. (this can not be done from the Kiwi admin console tab)
If you haven't logged in this way in a while remember that your Debian root password has likely been changed to either the Kiwi admin password or the Kiwi's serial number if no Kiwi admin password has been set. The Debian root password has not been touched if you had set it to something other than the default of having no password.
See this post for details: http://forum.kiwisdr.com/discussion/1801/v1-354-security-improvements-debian-root-password-no-longer-unset-blank

cdp
mst      (stops the Kiwi server)
cd
pkup     (shell alias for "apt-get -y install debian-archive-keyring; apt-get update")
pkug     (shell alias for "apt-get -y dist-upgrade")

(lots of output, takes roughly 10 minutes)

reboot

A few minutes after the reboot the Kiwi server should be responding again. If you login to the Beagle and type the "dog" command you should see:

Debian 8.11
BeagleBoard.org Debian Image 2016-05-13
Linux kiwisdr 4.4.9-ti-r25 #1 SMP Thu May 5 23:08:13 UTC 2016 armv7l GNU/Linux

There is still the open question of how the Kiwi distribution, and thousands of Kiwi customers, will migrate to the current Debian 9 (Stretch) and/or Debian 10 (Buster) releases which are available for the Beagle. This needs time for research as there are many issues involved.

Not on any pulldown from the control panel. You have to use the label editing feature since you are defining the mask for a particular frequency and mode (passband). http://kiwisdr.com/quickstart/index.html#id-user-marker

On the DX label edit panel it's the last entry ("masked") on the "type" pulldown. You will see the blackout in the waterfall immediately.

Okay, I see what's happening. The change back in January to separate kiwisdr.com and sdr.hu registration is not fully reflected in the status code transmitted to update rx.kiwisdr.com. So the 15 minute response time won't apply in all cases. Rather, your listing will be removed after three days by the "inactivity" timeout. I have reduced this inactivity timeout to three hours instead. So your listings are now gone..

Okay, I see what's happening. The change back in January to separate kiwisdr.com and sdr.hu registration is not fully reflected in the status code transmitted to update rx.kiwisdr.com. So the 15 minute response time won't apply in all cases. Rather, your listing will be removed after three days by the "inactivity" timeout. I have reduced this inactivity timeout to three hours instead. So your listings are now gone..