jks

We're also adding a washer to one of the case screws and recommend that you add a ground wire to the case if your antenna connection does not provide a good ground. It is important to provide a ground path for any static charge dissipation.

All the currently supported switches, including Ethernet-based switches, are listed here: https://github.com/jks-prv/KiwiSDR/tree/master/pkgs/ant_switch

There is not a proper pointer to that in the base documentation, so I will fix that. Thanks.

It depends on what you mean by "log" as there are some subtle differences. Not all messages appearing in the admin log tab are recorded in the Linux syslog. The ones prefixed with an "L" are. They should be recorded in /var/log and persist across reboots and power failures. The other ones are interesting but not deemed worthy of taking up filesystem space.

In the past someone did figure out how to do remote syslog recording. I don't know if that had any adverse impact on the Kiwi realtime performance (i.e. causing the audio to break up).

The admin "users" tab never persists across restarts because of how it works.

Random shutdowns are always power supply, or power supply cable, problems (voltage brownout). If we've learned anything in the past 10 years it's that.

The admin page, config tab, colormap setting only applies if no override exists in browser storage from a previous visit to the particular Kiwi. Usually the first time you visit it (or after a storage/cache clear).

If it's starting with csdr just change it to kiwi on the user WF tab (bottom left colormap tab) which will change browser storage and apply to the next visit.

You can bring up the browser console and check storage to see the actual current setting.