jks

v1.809 April 5, 2025

  The output from my.kiwisdr.com has been expanded to include additional information:

    Proxy links in addition to local IP links if proxy mode is setup and running.

    Connection type & status (i.e. settings on admin page "connect" tab).

    Kiwi and Debian software versions.

    Kiwi product model and Beagle type.

    The Debian hostname is shown after the serial number if it has been customized from the

      default "kiwisdr". Useful if you have multiple Kiwi on your network and you want to

      distinguish them by name instead of solely by serial number.

  Admin network tab has new field "Debian hostname" to complement the my.kiwisdr.com change above.

    This changes the actual Linux hostname and is not just a Kiwi configuration parameter.

  DX label fixes (desktop):

    When an extension is open, and you click on a dx label specified to open the same named

    extension, the extension won't get closed and re-opened. Instead, any new extension

    parameters contained in the dx label are sent directly to the open extension for

    further processing. Example: clicking on a different LF time station causes the

    timecode extension to change its decoding setup.

    Label only turns magenta (indicting extension will be opened on click) when mousing over

    label _without_ a modifier key pressed (shift etc). For example shift-clicking a label

    opens the label edit panel. So it doesn't make sense to be turning the label magenta

    because an extension isn't going to be opened when you click it.

    The DX help panel is opened if the cursor is in the label area and "h" or "?" pressed.

    The stored DX database can now have a custom name, 15 chars max. (thanks Mauno WRTH)

    Change the first line of the dx.json file from:

      {"dx":[

    to:

      {"my-custom-name":[

    If this is of interest you presumably already have a custom dx.json file you're loading

    via the admin DX tab "import JSON" button. If not, just use the "export JSON" button

    to download a copy of dx.json and use a text editor to make your changes.

    The custom name will appear in all the usual places: The left end of the frequency

    scale, the various database selection menus, etc.

  When frequency scale offset is in use (i.e. using a downconverter) fixed broken behavior of:

    "VFO A/B" button. (thanks F5AFY)

    "Zoom-to-band" button.

    "--- +++" buttons when frequency scale offset was not a multiple of 1 kHz.

  S-meter URL query: Allow optional mode e.g. my_kiwi:8073/s-meter?14200usb (thanks F5AFY)

  Prevent Beagle LED control conflict when admin backup function running. (thanks F5AFY)

  Save/restore waterfall timestamp parameters in browser storage. (thanks nitroengine)

  Removed debugging print causing lots of "AJAX_STATUS ..." messages in admin log when

    wsprdaemon or similar application are in use. (thanks DL4ZBE)

  Admin local blacklist now disallows entry of subnets which would otherwise exclude local

    network addresses or the loopback IP address. (thanks G2YT)

  When the "device preset" menu of the "Mouse wheel / trackpad setup" section of the user tab

    is set to anything except "custom" the three fields below are disabled for input.

    Although they still show what the preset values are. (thanks ZL2P)

What would it take for this device in order to extend its range down to 1 kHz or even DC? I'm trying to monitor dirty electricity coming off my house's electrical wiring.

One question: if using on my home network, would there be the same latency as with online KiwiSDRs? I find that any I've used online have a delay of about a second or more between clicking on/selecting something and it actually happening. I'd find this annoying if using locally.

Question from a user: if I listen via PC everything works fine. If I go to the link with my Android smartphone this appears: Unable to reach the site. Why? Other.. KIWI sdr app is not available for my device

ET ships aka UFOs seem to be standing wave EM energized on the hull, the small 10-15m scout craft likely have a main tone around 10MHz and complex harmonics up and down, all the way down to audio range and at least up to GHz. GHz might even be a dominant component. Try looking for it. Sightings suggest at least 200 sorties around the world every day and they might put out considerable power levels so should be detectable from 1000km+. Larger craft will have deeper tone presumably. It will be a strong signal that has no data. When close they sometimes emit a sound like an agitated bell, a bit like meditation vessels. Similar sound might be recognizable in RF as a beat frequency or something. No FM modulation of course since it's a side effect of the propulsion.

It is a certainty that ET ships frequent our skies and there is strong evidence of EM and RF, only a question of how easy are they to detect. Coastal areas might be the most frequent as the regulars seem to have bases on earth, specifically in the continental shelf sea floor.

Ok I'm not shore this question is sensible, but what is the point of the clock input? I would have thought that with both gps and ntp you would have plenty of clock sources.

What external clock frequency is needed?

Hmm, the price is right, but i wonder... is the kiwi tweakable over SSH ?

I have an Airspy HF+ Discovery for VLF, HF and VHF, and an RTL-SDR for higher frequencies, accessible anywhere in the world via OpenWebRx+. Can anyone tell me how the KiwiSDR 2 is better? Serious question.