I was recently out in a "quiet place" to make noise floor measurements of my active antenna system. I did indeed find such a place which could reach the noise floor limitations of my system and

WD installs the arm64 version wsprd, but WSJT-x builds that for the Pi. You will probably need to compile wsprd from sources to get it to run on your nano. See Joe Taylor's comments at:

the nano uses 64bit-ARMv8.... does wsprd (or wsjtx-x) support that? On 5/1/21 9:21 AM, John via groups.io wrote:

I never see the wsprd process listed in the TOP display. I went to the wsprdaemon/bin dir and did a wsprdaemon@wsprdaemon-desktop:~/wsprdaemon/bin$ ./wsprd -bash: ./wsprd: cannot execute binary file:

I forgot to add that I am running the smallest configuration for this test. One KIWIsdr and only one 20 meter channel. I do see the recorder process in the KIWI. John

Still working on the same problem to get wsprdaemon to run on the Nvidia Nano running UBUNTU 18.04. The problem I am seeing is no spots with the tail -F uploads.log command. I do see the message to

and how many bands are you trying to decode?

Try running these on your wd server 1) from a terminal session on the Pi type "cd ~/wsprdaemon/uploads.d/wsprnet.d/spots.d <ENTER>" 2) from that same terminal session on the Pi type

what OS are you running?

This error shouldn't appear in more recent Kiwi versions. When the non-NBFM squelch was implemented the API was changed slightly. But there was a period of time where the old API was not accepted as

(Sorry, only seeing this now as I don't check here very often.) The new (non-NBFM) squelch function only effects the browser. Like the mute button. But kiwirecorder connections are coming in on a

I have been working to get the daemon running on the 4GB nano. Most is looking well. The KIWIs are loading ok just no spot uploads. At decode time { 8 sec mark} I see a bump in CPU to 80% but it only

All fixed. Was ethernet switch problems./

I have found the update takes about 17 minutes. Try and do a full power cycle after 17 minutes

I think there is a topic on this problem in the forums.kiwisdr.com site. -- Rob Robinett AI6VN rob@... mobile: +1 650 218 8896

I have two Classic KIWI stuck in Update. One from 1.445 to 1.446 and the other is just sitting at 1442 with 1446 Available but with no action. Both are not accepting settings from wsprdaemon. Any

Hello All, I was going through their examples (on my local workstation), testing things out, and getting a feel the CLI / API. I decided to load one of their bigger datasets and play around some. I

Hello All, I should have looked a bit further before diving into a complex solution. Third Party UI Clients are Plentiful I already have a subscription to JetBrains DataGrip (and others), and it has

Disaster recovery / backups are never important until ya need them (been there, done that, lost the data). I've got a full copy of the WSPRnet dataset also, in multiple locations. Not that I really

We maintain 3 copies of the wsprdaemon.org site: 1) wsprdameon.org is a cloud server maintained by digitalocean.com on a Silicon Valley server 2) wd1.wsprdaemon.org is a Dell server located in a