Greetings y'all HB9VQQ is presently performing a test of Kiwi with Rpi4 running WD against an Airspy HF Discovery running Wsjtx with Rpi4 on the same antenna through a splitter https://groups.io/g/wsp

Using this link: https://wspr.live/gui/d/ereVvgn7z/station-noise-stats?orgId=1&refresh=1m the ONLY noise plots I can see are from KFS. No other station, including mine, has any data. Am I missing some

Hello all, I´ve been trying to run a single band wspr monitor with the audio input feature, but with no success. My present setup consists on a Funcube dongle, playong on the PC´s own soundcard. Since

This issue is more for Arne, but I do not have his e-mail adres. Perhaps someone can forward to him ? -------------- so: For Arne ---------------- Problem: Page: WSPR Daemon/ Station Noise stats This

My kiwis are all offline, as latest kiwi version 1.464 upgrade don't work Has someone a backup of Vers. 1.461 and can offer this for download ? I have older backups, but not 1.461 Version 1.461 was la

I have started to debug FST4W decoding in the WD 3.0 alpha but so far I can't find any signals at KPH on 630, and WSJT-x doesn't seem to identify such signals, if they exist, on other bands I am using

I have an eight channel installation running with great success. My local noise plot shows only a very few points however even though I have run the installation for several hours. Is there a way to t

Great, that kph is receiving again with the kiwi's... I thought I use the Japanese CW contest to make a screenshot of kfs (NWest antenna) and compare it with the TCI 530 at kph I know that this is not

Hi Yuri, I am adding this to the WD forum so others see the issue. I will be testing WD 3.0 installation on Ubuntu 20.04 and will address all such problems thanks for the report. Rob -- Rob Robinett A

I do not see new WSPR spots on wspr.rocks since 2230 UTC this afternoon (8/27/2021). Carol KP4MD

Hi Rolf, I resumed daily work on WD 3.0 about 2 weeks ago and have just about finished the very extensive software restructuring work. Wspr.rocks queries show my WD_3.0a alpha code running reliably at

Hi Rob, I know Murphy was an optimist and that even the best plans do not last through the battle. How well do I know from years in the trenches. Just curious here how you are doing as I am working on

I just noticed that JKS has made the forum available again, though read only for now. http://forum.kiwisdr.com/index.php?p=/categories/kiwisdr-discussion

I will be carrying out maintenance and a change to the wsprdaemon_spots table on logs1.wsprdaemon.org today. The table may stop updating while the work is underway and you are advised to use logs2.wsp

The work on the noise table on logs1 is now complete. The work was to add an automatically generated incrementing sequence number to each noise line uploaded. The noise table on logs1 that is now bein

Please be aware that I am testing out some changes to the wsprdaemon_noise table on logs1.wsprdaemon.org today. The wsprdaemon_noise table will stop updating at times and there will be gaps in the dat

This version adds WD's SW version number to the spots it uploads to wsprnet.org. That site doesn't display those version numbers, but wspr.rocks will print that version number field. Also, version 2.1

Thanks to an observation by Clint KA7OEI, I found and fixed a problem in the WD server which caused noise graph files to not be displayed. The WD server wakes up every 5 seconds, gets a list of .png f

Has anyone looked at DigiSkimmer? https://github.com/lazywalker/DigiSkimmer Seems to be using a similar approach to Wsprdaemon to deliver the basic WSPR spotting functionality (none of the clever nois

Despite my vow last night to not work on the FD until its serious RF input problems are solved, this morning I decided that I had spent so much time setting up access to Tom NH6Y's FD that I would spe