nitroengine

@Yogicat Have a look here: https://forum.kiwisdr.com/index.php?p=/discussion/2444/christmas-kiwi/p1. The logo doesn't get replaced, just overlaid with another image. In my case as shown above, with a pair of Sony headphones. In the past, I've also stuck a set of New Years glasses on the Kiwi as well as that Santa hat.

Just fun stuff. I wouldn't attempt to replace the logo entirely.

If you want to add your own "logo", you could insert a small image in the "Owner info" box under the "Web page" tab using HTML. That will show up in the center of the top bar.

I've chatted with the owner of another Kiwi through his Kiwi before using the name callsign box.

I know there are a few guys who have configured chat boxes on their Kiwis. I believe most of them use this: https://www.chatango.com/ Pretty straightforward to add to the Kiwi in the "Additional HTML/Javascript for HTML" text box under the Webpage tab.

I don't mind the current Kiwi logo. It has brand recognition now.

I did stick a pair of Sony studio cans on the Kiwi on mine...just because, why not...

Somewhere it was mentioned you want a MicroSDHC card of 8-32GB. John or someone can correct me if I'm wrong, but from my understanding, MicroSDXC cards are not supported on the Beagle.

I know some MicroSDXC cards do have backwards compatibility with MicroSDHC devices.

I know the majority of Kiwi owners are only interested in HF, but there are many of us who do a lot of MW DX. The network of public Kiwis are highly useful for trying to track down a weak MW station, especially one that doesn't have an online stream. Using my own Kiwi and comparing to another Kiwi, you can often hear the 1:1 echo of a station between the two SDRs. So its unfortunate to see once really good Kiwis in desirable areas suddenly go "deaf"...or so you think until you zoom the waterfall out and see VLF and HF are as alive as can be and it's only the AM band that is deaf 😖...

So instead of implementing an MW BCB filter, I'd encourage trying a few dB of attenuation or try constructing notch filters for those specific problem frequencies.

A couple more once good Kiwis, including one out in California I often used, just tossed MW filters on them within the past month or so.

I know a lot of Kiwi owners are most interested in HF and SWLing, but the public Kiwis are also very useful to AM/MW DXers for targeting or identifying signals that may be local or within range to those Kiwis. Unfortunately, there's many Kiwis in desirable locations that have been fitted with steep BCB filters, rendering their use for MW DX limited to useless.

An ideal solution would be an add-on external attenuation module that works with the attenuator slider control in the Kiwi control panel. Sold as an accessory alongside the Kiwi. With a disclaimer on the attenuator accessory module that it is susceptible to damage if exposed to strong signals.

Another external Kiwi accessory to look into would be to offer a range of tunable notch filters that could allow one or more strong problem signals to be attenuated without affecting the entire spectrum or resorting to filtering out an entire band.

OpenWebRX+ has a long ways to go before it's as user friendly and as feature packed as the Kiwi's heavily modified version of OpenWebRX.

OpenWebRX+ is a good option for those who want to set up a remote SDR that can be set to cover frequencies beyond 30MHz and do broadcast FM. That is until a KiwiSDR 3 is released 😉.

I was just going to set an Admin password and send you a link, but decided to force an update to v1.688 first.

Guess what? Now the WSPR extension is reporting to wsprnet.org! I'll play around with it and see if it gives any trouble.

I let the non-autorun extension run for a good 20-30 minutes earlier today (on v1.686) and it wasn't reporting at that time, as it hasn't each time I tested it since I started this thread. I let the WSPR autorun go for a couple of days last week and that was reporting as normal.

So far it's working now (on v1.688). My reporter callsign is SWL/EN35.

Bikedork (located in Minneapolis, MN, running v1.680 in 4 channel mode) also isn't reporting to the WSPR database using the extension.

Running v1.678 in 3 channel mode. I'm playing around with the (non-autorun) WSPR extension this evening, and it doesn't appear to be uploading spots to the WSPR database at http://www.wsprnet.org. I've had it going for the past 30 minutes with a good number of decodes shown on the extension. I tested the WSPR autorun, and it does upload spots with that.