jks

Not following this in detail because I'm so busy. But try and run this at 115k baud at least to avoid impacting the Kiwi realtime performance (i.e. causing the audio to break). That was my experience when I added the CAT output option that also used /dev/ttyUSB0 (and /dev/ttyASB0 if necessary).

There was a discussion about this recently over on the wsprdaemon forum: groups.io/g/wsprdaemon/topic/vlsl_telecom_network/112581272?dir=asc

I've told this story before but will repeat it in case anyone has self-interference problems.

Before my apartment building was wired for fiber (FTTP) all we had was VDSL2 from a pedestal on the street over the crappy building CAT3 telephone cable. I had some noise, even after adding some toroids, around -95 to -100 dBm (uncalibrated) as shown in the first image. Not too bad.

One day one of the VDSL band segments jumped up almost 15 dB in signal strength. I looked at the VDSL statistics page on the modem and the "downstream" transmit power from the line card in the pedestal was at +14 dBm compared to the usual +3 dBm, which is what the statistics page said my modem was transmitting in the "upstream" direction. They were always about equal in the past.

After resetting the modem there was of course a VDSL retrain cycle and the downstream power dropped again to +3 dBm. I happened to catch this on the waterfall in the last image. Not quite as good as what I had before. But a big improvement.

As mentioned in that post, I quickly implemented the simplest, dirtiest server that followed the minimum SpyServer protocol just to get SDR++ to work (barely). My goal was to see if this concept was even possible. SDR++ was the fastest route to that goal.

I don't know anything about soapy or ka9q-radio or how difficult it might be to write a driver for them.

More importantly, this work was paused until other "pieces of tech" become available to make sending a more significant amount of spectrum possible. Like MHz instead of hundreds of kHz. That work is still ongoing..

Thanks! I forgot that the URL scan list is also entered as the first entry in the local menu.

Someone was kind enough to make a review entry for the Kiwi over on eham.net

If anyone wants to contribute a review to the entry that would be very much appreciated.

Thanks

@dl7awl Sorry, there was some missing text on that page describing that the new button on the admin backup tab must be used. I've fixed that now.

@ww6d I'm surprised you thought some sort of formatting of the sd card was necessary. That should not be the case. The procedure writes the new Debian 11 image to the raw sd card device (no formatting required). Then afterwards mounts the created partition on the card to write the Kiwi configuration information.

Also, the documentation section you mention "Re-flashing once you have the SD card" is referenced directly at the end of the upgrade instructions (even including a link!) So there should not have been any confusion about this.

I think this is a conflict between who controls the LEDs during the sd card backup script running. I believe it's on my list of things to fix.

Update: Okay, fixed for the next release.

Yep, a typo made in the Verilog code last July if you can believe that. Didn't show itself until I built v1.807. Fixed in v1.808..

It's not automatic. I have to do it by hand. It's published every six months at eibispace.de

I see A25 is out, so I'll try and get that in the next Kiwi release.

Nice. Well, it's all about the field strength. Very likely you can build something useful that will not be detectable outside of your immediate location.

And, you can use your Kiwi to test it -- the timecode extension!