rrobinet

I have configured several Kiwis for wifi access by attaching an inexpensive router configured as a Wifi client to the ethernet port of the Kiwi. This $25 TP Link has worked well for me: https://smile.amazon.com/TP-Link-Wireless-Portable-Travel-Router/dp/B00TQEX8BO/ref=sr_1_14?keywords=tplink+wifi+router&qid=1548188019&sr=8-14 In principle one could enable the internal BB Wifi or attach a USB wifi adapter, but I am reluctant to fiddle with the Kiwi's OS.

About

Username
rrobinet
Joined
Visits
1,300
Last Active
Roles
Member
Points
9

Reactions

44Helpful42Awesome

  • wsprdaemon problem

    rrobinetrrobinet
    There is a bug in v2.7a in which WD fails to install the Linux 'sox' utility problem. Legacy sites will have sox already installed, so they are not affected by this bug.
    'git pull' will download v2.7b which fixes this problem
    cathalferris

  • wsprdaemon - A Raspberry Pi WSPR decoding service

    rrobinetrrobinet
    wsprdaemon -z
    kill $(ps aux | awk '/wsprdaemon/{print $2}')
    rm -rf /tmp/wspr-captures/*
    wsprdaemon -a
    Huub

  • wsprdaemon - A Raspberry Pi WSPR decoding service

    rrobinetrrobinet
    Thanks for the feedback. I will clarify the use of 'wd' and alias and add further cleanup to the installation instructions.

    As for the plotting problems, here is more information than may interest you on the cause.

    v2.7 adds c2_fft data to each line of the signal-levels.log file which is used to create the noise graphs.

    In 2.6 the 13th column was the source of fft data which was created by running the sox fft command

    In 2.7 there are 14 column in each line and by default sox fft is not run, so that column is set to -999.9. The the newly implemented c2_fft value is always calculated and put in to the newly populated column 14 (the last one of each line).

    In v2.7 the python plotting program /tmp/wsprdaemon/noise_plot.py has been modified to use the values in column 14. I think I regenerate that program when the plotting is done each odd 2 minutes, but if a 2.6 noise_plot.py is run it will plot column 13 which is now -999.9 and thus off the bottom of the graph.

    In addition, legacy lines in /home/pi/wsprdaemon/signal_levels/*/*/signal-levels.log files might not contain 14 columns and crash the new noise_plot.py

    So the safest way to upgrade probably involves:
    1) flushing your old signal-level.logs files with: 'rm -rf /home/pi/wsprdaemon/signal_levels/*'
    then
    2) rebooting your server which will recreate /tmp/wsprdaemon/....

    Of course it will then be several WSPR cycles before there are enough measurements for the noise graphs to show visible points.
    cathalferris

  • wsprdaemon - A Raspberry Pi WSPR decoding service

    rrobinetrrobinet
    WD -V (capital V) will print the version number of yoru WDS
    "sudo systemctl status wsprdaemon" will show info about status
    "sudo systemctl enable wsprdaemon" will ensure that WD is started at server boot time.
    I will add a command flag to v2.7x check/enable/disable startup
    WA2ZKD

  • Could there be a user accessible setting of the default audio buffering time?

    rrobinetrrobinet
    This is really a feature request, not a problem
    CW and SSB users of KPH reported very few audio problems were introduced even when set to the minimum 0.25 seconds, and at those settings the Kiwis are far more friendly when used in two way conversations.
    So I think it would be great if users could select the audio buffer size and if there were an admin page setting for the default size.
    WA2ZKD