jks

@Jimo: Not so simple. Not because of the actual code issues, but because of the validation and deployment issues (as usual). Can you imagine the disruption? Especially if something goes wrong?

This is probably best handled when there is the eventual need to open a second proxy server (we're getting close and it will probably be in the EU). That way the migration can be done in a controlled way.

It has a --zoom (-z) option which defaults to zero meaning zoomed all the way out (0 - 30MHz). Setting the frequency only matters when you are zoomed further in (values 1-14). These zoom values match the zoom values seen on the Kiwi user interface (i.e. number 'n' after "WFn" tab on main control panel).

Yes! Right-click on your mouse to bring up the Kiwi utility menu. This is an often overlooked feature. If you have a laptop like a Mac there are different ways to configure the track pad for right-click in addition to the usual left-click (I use the two-finger tap method). One of the menu entries is "save waterfall as JPG". This feature was contributed by Peter, VE3SUN.

But this is a manual operation. You're probably interested in automatic waterfall recording.

The kiwiclient waterfall code is currently only for gathering statistics and not saving the waterfall image. But with some code changes it could probably be made to do that.

To be more precise about the kiwiclient waterfall tools. There are three facilities:

• The --wf option of kiwirecorder (note not kiwiwfrecorder) prints statistics.
  
• Kiwiwfrecorder (note not kiwirecorder) is a specialty program Christoph wrote that saves waterfall data together with GPS timestamps as Python Numpy array format file (.npy) which with some code changes could probably be an image file as well.
  
• microkiwi_waterfall.py is a simplified version of kiwirecorder --wf that Marco wrote. A version of which runs his Dynamic SNR Map website http://sibamanna.duckdns.org/sdr_map.html
  

I'm simply using SAM code from Warren Pratt's excellent wdsp package as pulled from the Teensy-ConvolutionSDR project. So I don't know too much about how it works. The code can be found on your Kiwi in the file /root/Beagle_SDR_GPS/rx/wdsp/SAM_demod.cpp

It has its own internal PLL code and does not use Christoph's C++ PLL code that is shared by the IQ and timecode extensions. Comments in the SAM code mention that the PLL zeta and bandwidth should probably be adjustable for varying conditions (e.g. dx, "medium", "fast"). Right now they default to a zeta of 0.65 and b/w of 200 Hz.

With the recent reorganization of the noise blanker/filter controls there is now some empty space on the audio tab of the main control panel. Perhaps some SAM PLL adjustment controls could be added there.