Date
1 - 4 of 4
WD 3.0.3.4 - Command not found error
|
Duncan GM5JET
Hi,
Since upgrading to the latest WD version spots are no longer being uploaded and I am seeing the following error at the command line. |
|
|
|
Rob Robinett
Hi Duncan, Did you name your receiver 'SDR..."'? If so, then WD thinks it is talking with an SDRPlay and as a result it is exercising untested parts of WD 3.0. For current and future compatibility, it is clearest and best to name KiwiSDRs 'KIWI_xxx' Did that help? Rob On Tue, Aug 23, 2022 at 8:11 AM Duncan GM5JET <gm5jet@...> wrote: Hi, --
|
|
|
|
Hi Rob,
Thanks for such a quick reply. I had XXXX_SDR declared in the .conf and so I'll change that now and check the results. Regards, Duncan EDITED: The error seems to have resolved but WD is still not uploading spots. Have checked both WSPRnet and WSPR Rocks UPDATE: The uploads seemed to be delayed. Now reporting ok and will keep an eye on it all. |
|
|
|
Rob Robinett
After WD starts it can take up to 6 minutes before the first spots are decoded and uploaded to wsprnet.org. In order to minimize the burden on the wsprnet.org server, WD waits until second 100 of the WSPR cycle to upload spots: i.e spots from the cycle which starts a minute 2 are decoded starting at minute 4 and uploaded at minute 4 + 110 seconds == just before minute 6.\ Since WD is started at a random second, in almost all cases the first wav file is not a complete 2 minute wav file. So if in this example WD was started at minute 0 + 10 seconds, the first spot would be delivered to wsprnet.org almost 6 minutes later. I could modify WD to upload a few seconds sooner, but since WD clients contribute about 25% of the total spots uploaded to wsprnet.org it would add additional congestion to their already overburdened server. . On Tue, Aug 23, 2022 at 8:35 AM Duncan GM5JET <gm5jet@...> wrote:
--
|
|
|