jks

Today's v1.427 release adds a "frequency scale offset" field for each antenna on the admin page, extensions tab, "Antenna switch" entry. After updating to v1.427 you must also install the latest version of the antenna switch extension from github.com/jks-prv/KiwiSDR-antenna-switch-extension

When any antenna is selected the new offset values will be used and completely override (and overwrite) the offset value from the admin page config tab. A value of zero means no offset, so the usual frequency scale of 0 - 30 (or 32) MHz.

Any active user connections will get a popup panel requesting a page reload when the offset changes. No offset change is made when "antenna mixing" is enabled because it isn't clear what to do in that case.

From the CHANGE_LOG file. The user interface is definitely rough, but at least you can give channel nulling a try in this update.

To null, use SAM mode and select the "audio" tab on the main control panel. On the bottom SAM line you should find the "channel null" menu. Select "null LSB" or "null USB". Make sure the PLL carrier is around 0 Hz (+/- 100 Hz maybe). If it's way off then make sure you're tuned to the station center frequency, switch to AM mode briefly, then back to SAM. The PLL should lock.

Use the spectrum function of the new "FFT" extension to visualize the nulling result. It's best to put the spectrum/waterfall aperture mode on manual so the spectrum doesn't rescale on you when the signal is nulling. You can enable the peak detect ("Pk" button) on the WF tab to see the difference. Because the nulling is happening in the audio path the regular waterfall and spectrum signal levels are not effected. Same for the S-meter. And currently same for the FFT and integrate modes of the FFT extension, although this might change.

That README page is slightly confusing because the picture of the air-core coil and first schematic appear adjacent to each other. The two schematics refer to the second picture which shows an "AM loopstick" style ferrite coil which could easily be 700 uH I would imagine.

Brings back memories of when I ran a LOWFER beacon on 175 kHz back in the early '80s. 1W input using an IRF510. And an output coil wound on a 200x500 mm coil form using Litz wire. Heard all over the western US. Was it really that long ago? Am I really that old? What happened!

I just replied to your email before I saw this post. So I'll include my email reply here:

So it turns out the default dx.json is stored on every Kiwi in case it turns up missing during a software install. If you bring up the admin console try these commands to see the differences:

In my case it showed dx.json had a few new lines not present in the default file.

You can replace the "wc" (word count) with a "cp" to copy the default file to the current dx.json. You can use "diff" to see the actual text differences.

You should immediately restart (admin control tab) so the server doesn't overwrite the dx.json file you just restored.

If all channels are full you'd have to "kick" a channel via the button on the admin status page to create a free channel for you to connect.

Alternatively, you can reserve one of the channels by setting a user password on the admin security tab and then set "number of channels not requiring a password even if password is set" to 3 (assuming you're using 4-channel mode). Then that channel will always be available for your use. You won't have to actually give the password if you're connecting from the local network.

You could also use the "camp" interface to wait in queue for a free channel to become available if you don't want to permanently reserve a channel and don't want to kick someone. But you will be waiting an arbitrary amount of time in that case. The camp panel appears automatically when you attempt to connect when all channels are full.

It's fine to use the default serial number as the Kiwi name for a publicly listed Kiwi. Lots of people do that.

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.