The KiwiSDR 2 online store is open for orders! Please visit
Today's v1.694 update is hopefully a working version of the failed v1.691,692 release of a few days ago.
See the first post of the "v1.694" thread below for the CHANGE_LOG notes.
Please visit (documentation) and (online store)



Last Active
Member, Administrator, Moderator
  • Is there a howto for getting a kiwi on

    What's the error message? Is it from the " registration status" field on the tab of the admin page? Or the "status" field of the DUC section on the network tab?

    Since you're using DUC on, on the tab selection menu at bottom left, do you have "DUC Domain" selected? And does it show ""?

    On the network tab what yes/no answers do you get when you push the "check port open" button?

  • does ipv6 prevent registration? [fixed in v1.100]

    Alright, v1.100 should fix this problem. Thanks for giving me the info about the failure. That was a big help.

  • does ipv6 prevent registration? [fixed in v1.100]

    Could you please restart your Kiwi? (pull and replug the power, or login and type "cdp", "ku").
    I used the wrong command to restart the server after making a change and now I can't get back in.. Thanks.

  • ADC Clock Frequency Correction via GPS Timing

    The ADC clock counting occurs before the DDS and is unaffected by any tuning compensation. You're correct, the "slightly off" sample rate derived from the division of the ADC clock is not corrected. But it doesn't matter. You just want to fix the downstream effects of the sample rate being slightly off. Namely getting the waterfall to look "on frequency" and the audio to produce the exactly correct tones. If you can determine what the exact, slightly off, constantly changing sample rate is using the GPS then this should be similar to having used a very expensive TCXO/VCTCXO with no GPS involved at all. Fixing the tuning completely compensates for the sample rate being off.

    The 48-bit counter in the FPGA, clocked by the ADC clock and sampled by the GPS, is very similar to a traditional frequency counter. If the gate time of the counter is known to be accurate then the ratio of the counter to the gate time gives you the frequency: ADC_clk (Hz) = ADC_count / GPS_gate_time, where Hz is "counts" per second and GPS_gate_time is the difference between two GPS time samples measured in seconds. Another way:

    ADC_clk (counts)   ADC_count (counts)             1
    ---------------- = ------------------- X -------------------
            (sec)                            GPS_gate_time (sec)

    The software GPS in the Kiwi doesn't even have a 1 PPS. It produces a new GPS position/time solution every 4 seconds or so and GPS_time is simply the difference between two successive solutions. Since both solutions are accurate to roughly a microsecond the "gate time" is accurately known. There is one more thing required. In the FPGA the ADC clock counter is sampled simultaneously when the GPS hardware that determines a solution is sampled. So the sampling is synchronized.

  • v1.95 release: new admin page features

    v1.95 adds two new features to the admin page (e.g. kiwisdr.local:8073/admin)

    The tab has a new multi-choice menu for entering the domain name or ip address of the Kiwi. There continues to be some confusion about what exactly is required for this entry. Hopefully the new UI will give a little more guidance.


    The network tab has a new dialog to help check that the Kiwi can be reached by the URL setup in the previous step. This also checks that the external port in your router has been successfully opened to let Internet users contact the Kiwi. This can be used to help debug problems with incorrect setting of the router NAT entry or port blocking by the ISP.