jks

One additional thing to check. If you can, log into the Kiwi Beagle and type "scs avahi-daemon". See if it is running. If it's not running then restart it by typing "scre avahi-daemon", check the status again with "scs", and see if pings to kiwisdr.local begin to work. Also check that "cat /etc/hostname" on the Beagle prints "kiwisdr" as the host name.

Okay, sounds like they're just giving you an ONT with E/GE ports and leaving the rest to you.

Awesome!

Wrap that stuff in a <style> ... </style> and chuck it in the box at the bottom of the webpage tab of the admin page that says "Additional HTML/Javascript for HTML element (e.g. Google analytics)". Then you don't have to edit any files and the changes will persist across software updates. And it's easier to experiment with. No need to restart the Kiwi or anything. Just edit the stuff in the box and reload the user connection to see the result. Edits in the box are saved to the Kiwi configuration as you type each time you press the return key (arguably a bug).

i.e.

@media only screen 
and (max-device-width: 600px)
{
#id-readme {
display: none;
}

#id-control {
transform: scale(.8);
transform-origin: bottom right;
right:0 !important
}

div#id-top-bar * {
font-size: 0.9em;
}

#id-band-container {

display: none;
}
}

Awesome!

Wrap that stuff in a <style> ... </style> and chuck it in the box at the bottom of the webpage tab of the admin page that says "Additional HTML/Javascript for HTML element (e.g. Google analytics)". Then you don't have to edit any files and the changes will persist across software updates. And it's easier to experiment with. No need to restart the Kiwi or anything. Just edit the stuff in the box and reload the user connection to see the result. Edits in the box are saved to the Kiwi configuration as you type each time you press the return key (arguably a bug).

i.e.

@media only screen 
and (max-device-width: 600px)
{
#id-readme {
display: none;
}

#id-control {
transform: scale(.8);
transform-origin: bottom right;
right:0 !important
}

div#id-top-bar * {
font-size: 0.9em;
}

#id-band-container {

display: none;
}
}

Along with the "--nb" option I just added, the latest kiwirecorder now has passband defaults for all the modulation modes. So if you say "--lsb" without specifying the passband with "-L/-H" it will use the same default passband as the Kiwi browser interface.

Okay, I just added "--nb" and related options. See the kiwirecorder help ("make help") and the "nb:" target in the Makefile.

Okay, I just added "--nb" and related options. See the kiwirecorder help ("make help") and the "nb:" target in the Makefile.

Along with the "--nb" option I just added, the latest kiwirecorder now has passband defaults for all the modulation modes. So if you say "--lsb" without specifying the passband with "-L/-H" it will use the same default passband as the Kiwi browser interface.

Along with the "--nb" option I just added, the latest kiwirecorder now has passband defaults for all the modulation modes. So if you say "--lsb" without specifying the passband with "-L/-H" it will use the same default passband as the Kiwi browser interface.

Currently the noise situation is terrible on that Kiwi. You've got a very bad case of Ethernet noise every 60 kHz in certain places (e.g. especially 20m). Also, there is a very loud carrier every 200+ kHz. Then there is a terrible switcher starting at 40 kHz with each harmonic getting successively wider in bandwidth. This is probably responsible for a lot of the broadband noise at HF.

All of this makes it difficult to judge what's going on.