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,250
Last Active
Roles
Member
Points
7
  • use of kiwirecorder, kiwiwspr etc

    I have just finished version 0.5d which adds support for a watchdog and scheduled band configuration changes.
    It also incorporates many command line changes which I hope make it easier to use.
    However it requires changes to the CAPTURE_JOBS[] array in the kwiconfig.conf file and you must add at least one WSPR_SCHEDULE[] entry.
    It is running well at 3 sites, but as always save your current kwiwspr.sh and kwiwspr.conf file in case this new version doesn't work for you.
    It is a very lightweight program and you can easily spot all 14 LF/MF/HF WSPR bands on a Raspberry Pi
    I welcome comments and bug reports
    G0LUJWA2ZKDGene
  • use of kiwirecorder, kiwiwspr etc

    The Kiwi runs an update task once a day to check for a new SW version and as part of that process terminates autowspr and kiwirecorder.py sessions for reasons only known to John. So that is one more reason for the need for a watchdog. My enhanced version with scheduled band changes is almost ready for testing
    WA2ZKDPowernumptyG0LUJ
  • use of kiwirecorder, kiwiwspr etc

    The Kiwi runs an update task once a day to check for a new SW version and as part of that process terminates autowspr and kiwirecorder.py sessions for reasons only known to John. So that is one more reason for the need for a watchdog. My enhanced version with scheduled band changes is almost ready for testing
    WA2ZKDPowernumptyG0LUJ
  • use of kiwirecorder, kiwiwspr etc

    The Kiwi runs an update task once a day to check for a new SW version and as part of that process terminates autowspr and kiwirecorder.py sessions for reasons only known to John. So that is one more reason for the need for a watchdog. My enhanced version with scheduled band changes is almost ready for testing
    WA2ZKDPowernumptyG0LUJ
  • What is the status of the WSPR background and autostart features? [added in v1.181]

    I didn't know there was any activity on 60M, but of course I'll add it.
    I too want to mmimic the "band Hopping' feature of WSJT-x. I won't have time to work on it for a few days.
    In the mean time, you could create a set of kiwiwspr.conf files and have the cron job run "-J z; mv replace kiwiwspr.conf; -J a"
    WA2ZKD