jks

About

Username
jks
Joined
Visits
31,838
Last Active
Roles
Member, Administrator, Moderator
Points
312

Reactions

579Helpful500Awesome

  • SSB Click Frequency

    jksjks
    This has been an open issue for almost a year now: https://github.com/jks-prv/Beagle_SDR_GPS/issues/5

    Basically it is waiting for a "user preferences" capability to be introduced so the tuning method can be varied to individual taste. I'm not going to change the default behavior until then. Otherwise I'll get pummeled with people who don't like the change..

    KQ6XA

  • Can dx.json be manually edited?

    jksjks
    Some important clarification about the directory locations.

    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.
    WA2ZKD

  • Is it possible to transform kiwi sdr on Xilinx Zynq FPGA a single chip solution [for GPS only]

    jksjks
    Hi. Yes, what you want to do is possible. But it is a lot of work. It is maybe easier to start with the GPS code that does not have the Kiwi SDR code parts: http://www.jks.com/sdgps/sdgps.html This code just runs a program on the Beagle that prints messages with no web interface and no complications of all the Kiwi SDR code.

    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?

    Navnath123

  • Interesting Signals

    jksjks
    This helps quite a bit: https://www.sigidwiki.com/wiki/Signal_Identification_Guide From our friends at http://rtl-sdr.com

    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.

    E, G: FSK/RTTY

    D: 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

    M0TAZ

  • CPU load is inversely proportional to the number of receivers?

    jksjks
    It's not that simple. The Kiwi is a very complicated realtime system. There is a careful balance of resources to minimize the cost of the device while maximizing the number of supported channels. This means there is sometimes a tradeoff between FPGA resources and Beagle cpu cycles.

    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:

    #recv %user %sys %idle %busy
    0 96 3 0 100
    1 60 18 20 80
    2 41 23 33 67
    3 41 22 33 67
    4 46 22 30 70

    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.

    dl2sba

  • IBP Button to track beacons

    jksjks
    Peter's IBP scanner is now a built-in extension in the v1.123 release.

    VE3SUN

  • Vote rigging on sdr.hu

    jksjks
    Martin: Done. I forgot you had multiple, switchable antennas.

    Ron: See comments #25 and 26 in this thread. It's an experiment and not many Kiwis have been "rated" yet (the GPS tag is automatic however).

    G8JNJ

  • v1.115: reduced audio latency, especially for local connections

    jksjks
    Okay, I'm going to try something different for today's release.

    G8JNJ

  • Config: v1.113 - Now unable to view Admin pages using iPad [fixed in v1.114]

    jksjks
    Fixed in v1.114 later today..

    G8JNJ

  • Noise at roughly 60 KHz intervals

    jksjks
    Probably not a Kiwi design issue, unless you've supplied your own, older Beagle that is known to have noise problems (see http://kiwisdr.com/quickstart/index.html#id-e14) What you describe is typical for one type of SMPS we've seen. 60 kHz is a common switching frequency.

    Switch off the other devices until you find the culprit. Try filtering the mains input to your Kiwi linear power supply and perhaps Ethernet and antenna feed line.

    There are plenty of Kiwis that are in very quiet noise environments with few system noise effects, e.g.

    wjniemi