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.

Update to v1.311, then login to the Beagle as root and do the following:

cdp
mst
cdk
nano admin.json [or other text editor of your choice]
[go to end of file and replace "options":0 with "options":1]
[save changes]
cdp
ku
[wait 1 minute]
ms

Now look for these messages in the log where "eth0" is hopefully replaced with your USB WiFi's identifier. The last two lines should have the local network address of the WiFi interface. Connecting to the admin page should now work.

Sep 12 00:55:28 www kiwid[1551]: 00:00:32.181 ...     getifaddrs: IF lo fam=17 flags=0x10049 UP RUNNING
Sep 12 00:55:28 www kiwid[1551]: 00:00:32.188 ...     getifaddrs: IF eth0 fam=17 flags=0x19043 UP RUNNING
Sep 12 00:55:28 www kiwid[1551]: 00:00:32.191 ...     getifaddrs: IF usb0 fam=17 flags=0x1003 UP
Sep 12 00:55:28 www kiwid[1551]: 00:00:32.193 ...     getifaddrs: IF lo fam=2 flags=0x10049 UP RUNNING
Sep 12 00:55:28 www kiwid[1551]: 00:00:32.193 ...     getifaddrs: IF eth0 fam=2 flags=0x19043 UP RUNNING
Sep 12 00:55:28 www kiwid[1551]: 00:00:32.193 ...     getifaddrs: CHECK eth0 fam=2
Sep 12 00:55:28 www kiwid[1551]: 00:00:32.194 ...     DDNS: IF IPv4 0xc0a80167 /24 0xffffff00 eth0
Sep 12 00:55:28 www kiwid[1551]: 00:00:32.194 ...     getifaddrs: IF usb0 fam=2 flags=0x1003 UP
Sep 12 00:55:28 www kiwid[1551]: 00:00:32.194 ...     getifaddrs: IF lo fam=10 flags=0x10049 UP RUNNING
Sep 12 00:55:28 www kiwid[1551]: 00:00:32.194 ...     getifaddrs: IF eth0 fam=10 flags=0x19043 UP RUNNING
Sep 12 00:55:28 www kiwid[1551]: 00:00:32.194 ...     getifaddrs: CHECK eth0 fam=10
Sep 12 00:55:28 www kiwid[1551]: 00:00:32.194 ...     DDNS: IF IPv6 LINK-LOCAL /64 eth0
Sep 12 00:55:28 www kiwid[1551]: 00:00:32.194 ...     DDNS: private IPv4 <192.168.1.103> 0xc0a80167 /24 0xffffff00 eth0
Sep 12 00:55:28 www kiwid[1551]: 00:00:32.194 ...     DDNS: private IPv6 LINK-LOCAL  /64 ff:ff:ff:ff:ff:ff:ff:ff:00:00:00:00:00:00:00:00: eth0

All there is at the moment is the user/admin guide ("operating information", which grew from the "quick start" page) http://kiwisdr.com/quickstart/index.html Even that is unfortunately incomplete (some commands and options are not documented).

There is a architecture design document, but it is very old and somewhat out-of-date: https://www.dropbox.com/s/i1bjyp1acghnc16/KiwiSDR.design.review.pdf?dl=1

There is no "tour" guide of the software/files. That was always a low-priority task. Sadly we don't have many software contributors, although the ones we do have are doing some absolutely stellar work. And of course our many forum contributors are providing a great service to our user base.

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.

Will be in today's v1.320:

	marker_s:      [ '1 sec', '5 sec', '10 sec', '15 sec', '30 sec', '1 min', '5 min', '10 min', '15 min', '30 min', '1 hr' ],

Will be in today's v1.320:

	marker_s:      [ '1 sec', '5 sec', '10 sec', '15 sec', '30 sec', '1 min', '5 min', '10 min', '15 min', '30 min', '1 hr' ],

In v1.318/319 there is support for multiple LPM settings. And the preset for JJC/JSC now selects 60 LPM and was tested (see below). XSG now replaces BMF. And JFC/JFW/JFX has been added per mt-utility.blogspot.com/2010/02/1800-utc-8658-utc-fax-confirmed-jfx.html (I had a successful reception on 16907.5) The frequency for HSW64 was fixed.

A speculative entry was added for GM-11F Ukraine (see: mt-utility.blogspot.com/2009/12/so-who-is-gm-11f.html)
That post is 10 years old. Since 1430Z is 0230 am for me could someone try listening at that time and see if GM-11F is still on the air?

Will be in today's v1.320:

	marker_s:      [ '1 sec', '5 sec', '10 sec', '15 sec', '30 sec', '1 min', '5 min', '10 min', '15 min', '30 min', '1 hr' ],

Will be in today's v1.320:

	marker_s:      [ '1 sec', '5 sec', '10 sec', '15 sec', '30 sec', '1 min', '5 min', '10 min', '15 min', '30 min', '1 hr' ],