jks

Note that passbands are specified in a way that might not seem obvious for LSB reception. While you would say "-L 300 -H 3300" for a 3000 Hz wide USB passband the equivalent for LSB is "-L -3300 -H -300". The easiest way to understand this is to zoom in and mouse over the yellow passband graphic in the Kiwi UI and look at the values displayed for passband low, high, center frequency, bandwidth and carrier point as you mouse over different parts of the passband. The passband low/high points are always read left-to-right.

Of course the passband can be whatever you want. So you could have an asymmetrical AM passband where the low side was -5000 and high side 2500.

In fact it is a fiction to have the modes USB, LSB and CW. Internally to the Kiwi it is really only mode SSB with USB/LSB/CW defined only by the passband shape. For example, you can get DSB simply by setting a passband that resembles an AM passband while in any of the SSB modes.

Okay, I just did this on a Ubuntu 17.10 distro and it seemed to work:

sudo apt install python
python --version (confirms python 2.7, not 3.x, was installed)
sudo apt install python-numpy
sudo apt install git
git clone https://github.com/jks-prv/kiwiclient.git
cd kiwiclient
make help
(kiwirecorder.py help will print)
ping kiwi-ip-address (make sure Ubuntu can see your Kiwi)
^C (to stop ping)
export KIWI_HOST=kiwi-ip-address (for Bash, different for other shells)
make real (record a real mode [i.e. non-IQ] file)
^C (to stop recording)
ls -lt (recorded .wav file should be at top of list)

Look at the "Makefile" file to see examples of how kiwirecorder.py is invoked to do different things.

@K7JFC Thanks, that's a very good idea. I'll update the docs to indicate the delivered v1.2 software will have audio problems because of the new browser autoplay restrictions.

[update: I have done this]

I looked at your Kiwi. The transverter was inline so I couldn't evaluate HF. But even that looked much worse than before. Lots of small carriers everywhere.

I fixed the config.js file so it says "Air Band" now instead of "Amateur".

Also the software update to v1.282 was perfectly fine.

From the CHANGE_LOG file:

v1.281  April 12, 2019
    Add URL parameter "peak" to set spectrum peak hold mode (overrides last value saved in cookie)
        e.g. "&peak", or redundantly "&peak=1", but more usefully "&peak=0"

    Audio FFT:
        Allow URL parameter "no_wf" to be used in 4 and 3-channel modes, not just 8-channel mode.
            This is useful e.g. if you want to use the audio FFT to study the frequency response of
            the new de-emphasis filter in 20 kHz mode (3-channel mode) where you would otherwise
            never be given the audio FFT because there is no shortage of waterfall channels.
        Added missing window function to FFT.
        Fixed scale/waterfall click frequency in non-IQ modes.

    Added signal generator extension. When enabled replaces ADC input to audio/waterfall DDCs
        with a tunable RF signal source using the same FPGA DDS IP block used by the DDC mixers.

        WARNING: Be careful about drawing conclusions re Kiwi performance and possible bugs
        when using the sig gen. It reveals spurious responses in the waterfall/spectrum to a greater
        degree than if you just tune around with an antenna connected. But without detailed
        experimentation it can be difficult to know where the limitations are. Remember that the
        Kiwi is a carefully balanced compromise to get 4-channel mode to work (i.e. fit in the FPGA
        and have enough Beagle CPU cycles). So the DDSs, mixers, DDCs and FFTs are not perfect.
        Speaking of compromise, when considering FFTs it's important to understand this:
        https://en.wikipedia.org/wiki/Spectral_leakage

Okay, to kiwirecorder.py in https://github.com/jks-prv/kiwiclient I have added an option "--S_meter=S_METER", where S_METER is the number of S-meter averages you want (e.g. 1, 10 etc.) After the averaging it prints a single line with the RSSI value in dBm.

See the Makefile target "s_meter" for an example of how to run it from the command line.

Okay, to kiwirecorder.py in https://github.com/jks-prv/kiwiclient I have added an option "--S_meter=S_METER", where S_METER is the number of S-meter averages you want (e.g. 1, 10 etc.) After the averaging it prints a single line with the RSSI value in dBm.

See the Makefile target "s_meter" for an example of how to run it from the command line.

From the CHANGE_LOG file:

v1.281  April 12, 2019
    Add URL parameter "peak" to set spectrum peak hold mode (overrides last value saved in cookie)
        e.g. "&peak", or redundantly "&peak=1", but more usefully "&peak=0"

    Audio FFT:
        Allow URL parameter "no_wf" to be used in 4 and 3-channel modes, not just 8-channel mode.
            This is useful e.g. if you want to use the audio FFT to study the frequency response of
            the new de-emphasis filter in 20 kHz mode (3-channel mode) where you would otherwise
            never be given the audio FFT because there is no shortage of waterfall channels.
        Added missing window function to FFT.
        Fixed scale/waterfall click frequency in non-IQ modes.

    Added signal generator extension. When enabled replaces ADC input to audio/waterfall DDCs
        with a tunable RF signal source using the same FPGA DDS IP block used by the DDC mixers.

        WARNING: Be careful about drawing conclusions re Kiwi performance and possible bugs
        when using the sig gen. It reveals spurious responses in the waterfall/spectrum to a greater
        degree than if you just tune around with an antenna connected. But without detailed
        experimentation it can be difficult to know where the limitations are. Remember that the
        Kiwi is a carefully balanced compromise to get 4-channel mode to work (i.e. fit in the FPGA
        and have enough Beagle CPU cycles). So the DDSs, mixers, DDCs and FFTs are not perfect.
        Speaking of compromise, when considering FFTs it's important to understand this:
        https://en.wikipedia.org/wiki/Spectral_leakage

From the CHANGE_LOG file:

v1.281  April 12, 2019
    Add URL parameter "peak" to set spectrum peak hold mode (overrides last value saved in cookie)
        e.g. "&peak", or redundantly "&peak=1", but more usefully "&peak=0"

    Audio FFT:
        Allow URL parameter "no_wf" to be used in 4 and 3-channel modes, not just 8-channel mode.
            This is useful e.g. if you want to use the audio FFT to study the frequency response of
            the new de-emphasis filter in 20 kHz mode (3-channel mode) where you would otherwise
            never be given the audio FFT because there is no shortage of waterfall channels.
        Added missing window function to FFT.
        Fixed scale/waterfall click frequency in non-IQ modes.

    Added signal generator extension. When enabled replaces ADC input to audio/waterfall DDCs
        with a tunable RF signal source using the same FPGA DDS IP block used by the DDC mixers.

        WARNING: Be careful about drawing conclusions re Kiwi performance and possible bugs
        when using the sig gen. It reveals spurious responses in the waterfall/spectrum to a greater
        degree than if you just tune around with an antenna connected. But without detailed
        experimentation it can be difficult to know where the limitations are. Remember that the
        Kiwi is a carefully balanced compromise to get 4-channel mode to work (i.e. fit in the FPGA
        and have enough Beagle CPU cycles). So the DDSs, mixers, DDCs and FFTs are not perfect.
        Speaking of compromise, when considering FFTs it's important to understand this:
        https://en.wikipedia.org/wiki/Spectral_leakage

Jim, let me know if you get kiwi_nc working. I got it running to the point of producing output but haven't tested it beyond that.

For Mac people, I just found this work by Chris yesterday: https://www.blackcatsystems.com/software/kiwiSdr-sound-client-virtual-audio-device.html