jks

I need to do a little more cleanup before releasing v1.139 with the new IQ mode. The changes are on the Kiwi at kiwisdr.sk3w.se:8073 if anyone wants to try it. I'd like to know if the Windows version of Dream works.

That reminds me that I've been meaning to create a "gallery" of waterfall / spectrum screen caps of common interference sources. Lots of situations have been identified now: BPL, xDSL, electric fences, different SMPSs, the Ethernet problem, ADC overload, ...

It might be ADSL or broadband-over-powerline (BPL). Note how the spectrum is obviously "notched" around the 30m, 20m, 17m and 15m ham bands (purple segments in band display). That's the service provider trying to keep hams happy, but failing dreadfully in this case. If you rotate the loop does the noise null at all?

I think it might also be several independent noise sources. I've seen those strong 0 - 30 MHz lines that look like static crashes before. I think they come from seriously defective switch mode power supplies.

Anything in /root/Beagle_SDR_GPS will be overwritten with a software update. So do not edit the files in /root/Beagle_SDR_GPS/unix_env/kiwi.config Files here are templates that are copied to /root/kiwi.config exactly once if they don't exist. Because the /root/kiwi.config directory is outside of the /root/Beagle_SDR_GPS directory structure it will not be effected by an update, and it is safe to edit them (and making a backup copy is a good idea).

Bonnie, I edited your post slightly to reflect this.

1) How are you wiring the Beagle SPI to the Zedboard? Are you using the same SPI pins as go from Beagle to Kiwi FPGA? This is tricky because those same pins are used to download/program the Kiwi FPGA. Did you somehow electrically isolate the Kiwi FPGA from those SPI pins? Otherwise you have to depend on the Kiwi FPGA power-up state to leave those pins in high-impedance mode. It is possible this is okay even if you did not isolate the pins.

2) Did you disable the code in the Kiwi server that programs the Kiwi FPGA?

3) Admin page not connecting: In the browser open the "javascript console window" and look for error messages. Each browser has a different way of doing this. On Firefox from the top menu bar select: Tools > Web Developer > Web Console and then make sure the Console tab is selected.

4) Do you get any error messages on the Beagle console when you run the Kiwi server?

A: JORN, Over-the-horizon-radar (OTHR) from Australia. Note the short intro tone in the middle of the passband. This distinguishes it from similar sounding signals like (for me) the Tiger radars of the SuperDARN network etc.

http://www.iarums-r1.org/iarums/radar-2013.pdf [10MB file]

E, G: FSK/RTTY

Would need to hear it or see zoomed in. But you're probably right.

Others: Correct I believe. The best blog I know discussing HF digital modes: http://i56578-swl.blogspot.com

What you're seeing at first is the GPS acquisition process (very Beagle FFT intensive) being paused when the first connection occurs. And with no connections the audio data pump between FPGA and Beagle is shut off causing a big reduction in system time due to fewer SPI transfers.

The %load number you show looks like user time only. You have to consider system (kernel) time as well. I see numbers like this:

This is about optimal. For no connections you want to spend all available cycles acquiring new GPS sats for maintaining ADC clock calibration. When there are corrections you want to have some cycles leftover for the portion of extension code that runs on the Beagle.