Hi Rob, There is to-be-debugged code in WD to use the Soapy API to communicate with the many SDRs (including the SDRPlay) for which there is a Soapy driver. Debugging the existing features of WD has

I have just increased the curl timeouts on my scrapers from 10 seconds to 120 seconds which seems to result in many more successful scrapes from the wsprnet.org server. Some successful API calls

All, Is anyone using Wsprdaemon with an Sdrplay RSP1A? If so, I would be interested in your configuration and if you managed to get it to work with more than one simultaneous receive? Having got my

Works for me as well - thank you Rob.

Thank you Rob, it seems to be uploading again after moving the cache. 73 Stefan

Since this morning's WD Users Zoom we uncovered one bug in WD spot uploading which is the result of the wsprnet.org overload problems. I think I can implement and check in a fix before tomorrow

At least in my case the spots are not uploaded: curl: (28) Operation timed out after 300000 milliseconds with 0 bytes received 73 Stefan

Since yesterday morning, no more spots are uploaded from me as well. (My spots on 2200m/630m/160m are from WSJT-X) But other WD users seem to be able to upload fine? For example OE9GHV, KD2OM,

Rob, just for info I confirm, that I upload the spots correctly to wsprnet.org - so the reason why there are no spots visible at Phil's site (wsprd.vk7jj) is NOT because there is nothing

I have no pending uploads here just now. For what it is worth I observed a time gap on VK7JJ last night from 18:12 to 18:20 ( that is 00:12 to 00:20 Z) but wspr.net had no such gap. 73 Rolf

Ulli, Mine has failed completely too. I see 1545 lines in "upload_spots_file_list.txt" and "uploads.log" has grown to 2601 lines with "broken Pipe" and "line 3420: echo: write error: Broken pipe". No

I have been told these lost spots are due to overloads at wsprnet.org and that is under investigation. -- Rob Robinett AI6VN rob@... mobile: +1 650 218 8896

No spots at all from my kiwis...for the last day or so... However all received at wsprdaemon servers, I think... So I leave everything running here and just wait... Just strange idea: Could it be one

Thanks Rolf, wsprnet.org is overloaded and we are trying to debug the interface between it and the wsprdaemon.org server. Rob-- Rob Robinett AI6VN rob@... mobile: +1 650 218 8896

Now it looks OK for the last 2 hours. At least no time gaps in reporting. Rolf

Have observed that VK7JJ is dropping spots. Just found 10 minutes missing whereas they are OK on WSPRnet. I suspect that there are more to this, but have not had time to dive into it. It appears

Thanks for explaining Rob.

The recent Wsprnet issues have coincided with me moving to using Wsprdaemon. I hope it wasn't me.... Good morning All, As a result of the recent Wsprnet disruption, it has been quite difficult to

That makes sense as it felt like wsprnet was there, but just too busy. I do wonder why people attack that sort of site, perhaps they are doing some atmospheric heating and would rather it not show up

Hi Rob, I have not implemented the proxy upload feature, so currently "proxy" is the same as "noise". Even when it get implemented, I worry about making WD responsible for delivery of spots to