jks

If it's really only two characters it might be that operating at 9600 baud will be okay. You'd just have to try it and see what happens as far as any realtime impact.

I have the web server log and that's all I need. tcpdump when anything more specific required.

I'm not going to continue talking about this since we don't know who's reading the forum.

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.

rx.kiwisdr.com (aka kiwisdr.com/public) is now subject to a simple click/tap captcha to help evade recent DDoS attacks on kiwisdr.com.

Apologies, but this is the sorry state of the world we live in..