jks

It would be best if you try making the sd card first and see if you can get through that procedure. We don't sell the BBG-only pre-loaded with software. I'd have to get our logistics guy to make one up. Then there's the shipping from here (DHL US$40).

Well, no.

First, this file is filled with dozens of illegal UTF-8 sequences. You can see the decoding failures in the browser's javascript console. They are mostly of the form e1 byte1 byte2, where the trailing two bytes are not valid UTF-8 continuation bytes beginning with the high-order bits 11. This is a symptom of improperly downloading files from eibispace.de. I had to learn this the hard way many years ago. You can't download files from there with the browser download function. You have to use wget plus some additional magic.

Second, I don't understand why you'd want to do this. We already have an integrated EiBi database. Yes, it's A25. I've been waiting for B25 to be released. I don't think this csv file is the official B25 release as eibispace.de only shows a 27 Sept update to A25 as being current.

The integrated EiBi database has a special filtering control panel that you don't get by uploading EiBi entries into the stored database. You lose that functionality which is important given that there are so many overlapping labels (more than 10 thousand).

But whatever I suppose..

Okay, but now G4SDG has faded up to -18 dB according to WSJT-X. And the Kiwi WSPR autorun decode count went from 12 to 13 during that time slot. So it worked at that signal strength. I think this confirms what's going on.

All I got out of that thread was "82 year old codger" and "AI hallucinations", both of which I can relate to (lol).

Actually I think I know what the problem is (amplitude imbalance). But I can't test until tomorrow.

I should also mention, re your earlier query about VHF/UHF Kiwi, that a reason to detect and respond to dynamic changes in the offset is because it is possible for this to be set in the antenna switch configuration. So that a user connection could select an antenna that also switches a downconverter in/out-of-line. On the Kiwi UI this causes a page reload to correct the frequency scale and all the other places the new offset needs to be taken into account.

But in practice I don't think many Kiwi are setup this way. VHF/UHF operation seems to be a static setup rather than associated with an antenna configuration.

First of all I did not write the squelch code, so I can't say exactly how it works. But it was originally designed for the NBFM modes. So using it outside that context is perhaps a bit problematic. I think it tries to compare energy at and above typical voice frequencies and use that as a basis for squelching. So it probably isn't going to work at all on AM BCB signals where there are very few periods of silence.

It works well however on things like the digital bursts in the UK on e.g. 4037.5 kHz. In either USB or AM modes.

The first one you mention is not a true Kiwi, but a clone that runs very old software (v1.690). So it probably has API compatibility issues. I do not provide support for clones. And, sadly, they don't seem to either (the clone forums are full of people who can't get support).

The VHF/UHF ones require detecting the offset via API and adjusting the frequency scale. But the API will still be baseband referenced, i.e. 0 - 30/32 MHz. It's a bit complicated. I will have to go through the code and identify all the places you need to consider applying the offset.

All of these air band signals will be AM mode. The Switzerland one worked for me, but has a huge number of spurious signals. Look for intermittent signals representing the short AM transmissions. The Russian one is another clone running v1.690 so probably won't work for that reason. You can identify these by connecting using the Kiwi web interface and checking the v1.xxx version number of the user control panel "Stat" tab.

In the next release I am changing the default of "acquire if busy" to be checked (enabled). This change will only affect new software installations, i.e. not change an existing configuration in case someone has explicitly set the value.

Okay, I think I have this fixed. Will be in the next release.

It a corner case: When two bands abut each other, and you're tuned to the exact frequency in common with the bands (e.g. 7200 as mentioned here), the - - - buttons should use the lower band's tuning step. And the + + + buttons should use the upper band's tuning step.

The story is slightly more complicated for overlapping bands. Which right now occurs for ITU R3 (Asia/Pacific) with the 40m amateur and 41m broadcast bands. Basically 41m has priority because it's first in the admin DX tab "band bars" list (unless you've changed it).

He mentioned in his email to me (but not in the post above) that it was set in continuous mode.