v1.500: better indication of WF-only connections

From the CHANGE_LOG file:

v1.500 March 17, 2022

  Better indication of waterfall-only connections on the various connection status panels, 

    logs and the /users URL. See Kiwi forum for details.

As an example see below for a regular connection on channel rx0 and kiwirecorder with option --wf waterfall-only mode on rx1.

So "WF" will be shown in place of the mode (because there is no mode for a connection with no sound channel). The frequency shown is the center frequency of the waterfall for the particular zoom level. In this case 9650 kHz and z4 frames the 31m SWBC band. Running kiwirecorder with the --log_level info option prints a line describing the waterfall parameters in more detail.

wf samples: start|center|stop 8712.5|9650.0|10587.5 kHz, span 1875 kHz, rbw 1.831 kHz, cal -13 dB

So a connection showing 15000 kHz and z0 means the entire 0 - 30 MHz span is being sampled.

The admin page, log tab, contains additional log entries for WF-only connections to aid in bot analysis. Note that these new entries are not recorded in the system log. Only on the log tab. In addition to the existing "arrived" and "leaving" messages an additional message will be generated every 10 seconds if the cf or zoom changes. That way the log will give a rough idea if the connection is actively tuning around as opposed to passively sampling the entire spectrum.


Thu Mar 17 00:37:04 01:28:04.533 01.. 1 L 9650.00 kHz WF z4 "kiwirecorder.py" (ARRIVED)
Thu Mar 17 00:37:14 01:28:14.801 01.. 1   5600.00 kHz WF z10 "kiwirecorder.py" 0:00:10
Thu Mar 17 00:37:19 01:28:19.427 0... 1 L 19000.00 kHz WF z12 "kiwirecorder.py" (LEAVING after 0:00:15)

From a local network, accessing the /users URL returns a JSON object with a new field. wf: 0|1 indicates whether this connection is WF-only or not.


  • This will be interesting, thanks for all of these enhancements.

  • jksjks
    edited March 17

    There was a bug fixed (reported on Github) where if the volume slider was moved to zero it would jump to the default value. I fixed this, but it seems introduced a bug making a missing volume cookie cause a volume of zero instead of the default.

    Sorry about that. I forgot to include this fix in the change log. Will go out in a release today..

  • Don´t you worry John. We all know that you are doing your best and you have done amazing job with KiwiSDR. 👍️

  • Thanks @jks!

  • edited March 18

    @jks When I connected to one of my KiwiSDR (v.1.501) I see TDoA label on my connection info: 

  • jksjks
    edited March 18

    @rz3dvp Why is that a problem? It just means they have the TDoA extension open. When an extension is in use it is always shown in the connection list.

  • edited March 18

    @jks But I don't open this extension... And didn't use it for a long time...

  • jksjks
    edited March 18

    @rz3dvp Is that you though on rx0 connecting from Amsterdam? Is this a public Kiwi?

  • edited March 18

    @jks Yes, I was test my msk.swl.su:8073 after update from my home IP and from VPN (tried only connected to KiwiSDR and received on 80m HAM band, don't open any extensions), but saw TDoA from both IP (sorry, but don't save second screenshot)... May be it was temporarily problem, - I can't repeat this situation again.

Sign In or Register to comment.