wsprdaemon not uploading spots on just one band
|
Chris Wilson
Having had this great software running trouble free for ages, this evening I have noticed that out of LF, MF, 160, 80, 40, 17 and 10, the 40 meter band is no longer either decoding or uploading to the wspr net site.
If I set my Kiwi itself to decode wspr on 40 meters in the extensions it does so just fine and uploads spots. How might I debug this please? I have rebooted the Kiwi, Beaglebone and the Raspberry Pi running the daemon but no joy. Thanks. EDIT, it's now very spasmodically uploading a few spots on 40m, but far far less than what I would expect at this time. The fact that it hears and uploads dozens of spots operating wspr direct from the Kiwi's extensions suggests there may be a glitch in my daemon installation, to my simple mind, although I haven't interfered with it at all for weeks. I am anything but a confident user of Linux, so be gentle please :) -- Best Regards, Chris Wilson 2E0ILY |
|
|
|
Chris,
toggle quoted message
Show quoted text
What do you see if you run wd -s from the command line? 73 Steve KD2OM On Feb 27, 2022, at 16:55, Chris Wilson <chris@...> wrote: |
|
|
|
Chris Wilson
I am embarrassed to say I am not sure what you are asking me to do. I have used VNC to log on to the remote Pi and opened the Linux equivalent of a dos box command prompt. Typing wd -s gives a command not found, as it does if I enter the wspdaemon directory before typing that. But I don't think this is what you intend me to do at all, sorry.... I am really naive about Linux.
-- Best Regards, Chris Wilson 2E0ILY |
|
|
|
That is quite alright. You should be able to open the terminal
(dos command box), it would look something like this when you
enter wd -s <enter> On 2/27/22 22:34, Chris Wilson wrote:
I am embarrassed to say I am not sure what you are asking me to do. I have used VNC to log on to the remote Pi and opened the Linux equivalent of a dos box command prompt. Typing wd -s gives a command not found, as it does if I enter the wspdaemon directory before typing that. But I don't think this is what you intend me to do at all, sorry.... I am really naive about Linux. |
|
|
|
You might have to enter wsprdaemon.sh -s My system has a shortcut. Sorry I forgot that some users might not have that. If you are in the actual wsprdaemon directory you might need to enter it as ./wsprdaemon.sh -s
toggle quoted message
Show quoted text
Steve On 2/27/22 22:34, Chris Wilson wrote:
I am embarrassed to say I am not sure what you are asking me to do. I have used VNC to log on to the remote Pi and opened the Linux equivalent of a dos box command prompt. Typing wd -s gives a command not found, as it does if I enter the wspdaemon directory before typing that. But I don't think this is what you intend me to do at all, sorry.... I am really naive about Linux. |
|
|
|
It is likely that with the recent excellent 40M conditions your server can't decode all the signals on 40M in the 120 seconds of a WSPR cycle.
On the desktop of a Pi you can add a 'CPU usage' panel to the task bar at the top of the screen and then watch how busy the CPU is. It should jump to 100% usage at second 5 of each wspr cycle and then drop down to less than 50% for 10 second or more at the end of each cycle. If it's 100%,
You can also try adding this line to the top of your wsprdaemon.conf file:
CORRECTION: I found the Pi 4 at my Maui site was running 100% and so I needed to make this change and found I had mis-typed it. The correct line to add is: WSPRD_CMD_FLAGS="-C 500 -o 3 -d"
It causes WD to execute the 'wsrpd' decoder with '-o 3' instead of the default '-o 4'; it will find fewer spots but will run faster.
Most top spotting sites are now running WD on x86 servers in order to handle their decoding burdens which will only increase with improved propagation as sunspots increase.
On Sun, Feb 27, 2022 at 2:41 PM KD2OM <steve@...> wrote:
You might have to enter wsprdaemon.sh -s My system has a shortcut. |
|
|
|
Hans V alphen
Hello,
|
|
|
|
Chris Wilson
I'll run the WD command in a bit, when I have finished a couple of jobs. But the overloading sounds like it may well be the issue, however there are long gaps, an hour or more, where NOTHING decodes (or maybe uploads). Could that happen if it was simply overloading? I don't suppose the wsprdaemon will run on a Windows PC will it? If I dedicate a somewhat elderly PC to Linux what's the easiest distro to install and use please? Thanks for all the help, much appreciated.
-- Best Regards, Chris Wilson 2E0ILY |
|
|
|
Chris Wilson
Not having much luck with this command, here is what i have been trying, what am I doing wrong here please?
pi@raspberrypi:~ $ wsprdaemon.sh -s bash: wsprdaemon.sh: command not found pi@raspberrypi:~ $ sudo wsprdaemon.sh -s sudo: wsprdaemon.sh: command not found pi@raspberrypi:~ $ ./wsprdaemon.sh -s bash: ./wsprdaemon.sh: No such file or directory pi@raspberrypi:~ $ cd wsprdaemon pi@raspberrypi:~/wsprdaemon $ wsprdaemon.sh -s bash: wsprdaemon.sh: command not found pi@raspberrypi:~/wsprdaemon $ ./wsprdaemon -S bash: ./wsprdaemon: No such file or directory pi@raspberrypi:~/wsprdaemon $ CPU usage looks OK from the Pi's Task Manager, it can go 100% for about 8 seconds but comes back down. Spots are still pretty random with many time slots totally empty. As other bands seem OK I don't think it's my (slow) internet connection. Thanks again for the help. -- Best Regards, Chris Wilson 2E0ILY |
|
|
|
WA2TP - Tom
Hi Chris,
toggle quoted message
Show quoted text
I just did a two week search of your uploaded spots on wspr rocks, and the only spots that I see for any band, have been uploaded by kiwi decoder. I do not see any WD uploads from 2E0ILY. When did you say your WD setup stopped working? Tom WA2TP On Feb 28, 2022, at 6:16 AM, Chris Wilson <chris@...> wrote: |
|
|
|
Rob Robinett
Hi Chris. To execute WD from a terminal window run: ~/wsprdaemon/wsprdemon.sh Your logs include TIMEOUT lines, so that is definitely your problem. Almost any i-5 or i-7 computer will be far more powerful than a Pi. The WD V3.0 servers sun on Ubuntu 20.04 LTS and I test WD client installations on that OS. It is possible to run WD in an Ubuntu virtual machine on Windows, but part of my goal for WD is for it to run very, very reliably, like a refrigerator, and a virtual machine environment doesn't provide that. I am using some Lenovo Thinkcentre Tiny M93p at some sites which I purchased used on ebay for $100-200, for example: On Mon, Feb 28, 2022 at 3:16 AM Chris Wilson <chris@...> wrote: Not having much luck with this command, here is what i have been trying, what am I doing wrong here please? --
|
|
|
|
Chris Wilson
I use 2E0ILY/KIWI for the multi band wsprdaemon uploads from my Kiwi. Plain 2E0ILY is direct from another PC and receiver, as is 2E0ILY/RPIT and 2E0ILY/AFED occasionally, a Red Pitaya and an Afedri on LF only
Thanks for looking though, I should perhaps of made that clear, sorry. -- Best Regards, Chris Wilson 2E0ILY |
|
|
|
Chris Wilson
OK, thanks Rob, I know where to head now, I have a spare i5 machine, I will fire it up and see what version i5 is in it and how much RAM (probably only 4 gig, is that enough? Are there any SFF boards like a pepped up Pi that have enough oomph? Electric prices have gone absolutely crazy and the wife, probably quite rightly, blames "all that junk constantly humming away upstairs" for a lot of each quarterly bill.
I'll check out this spare PC and post the processor and RAM details, if I may, for your critiquing? -- Best Regards, Chris Wilson 2E0ILY also 2E0ILY/KIWI on wspr net |
|
|
|
WA2TP - Tom
Thank you for the clarification.
toggle quoted message
Show quoted text
Unfortunately, wspr rocks is limited to call signs of 9 characters or less. On Feb 28, 2022, at 10:02 AM, Chris Wilson <chris@...> wrote: |
|
|
|
Rob Robinett
I think Ubuntu will run fine on a i5 / 4G PC. The odroid is the next step up from a Pi, but I think it will cost you more than a used Thinkcentre class PC and have less performance although the odroid is almost certainly more power efficient. The Thinkcentre Tiny consumes 9W at idle and at most 33W when all CPU cores are busy, On Mon, Feb 28, 2022 at 7:02 AM Chris Wilson <chris@...> wrote: OK, thanks Rob, I know where to head now, I have a spare i5 machine, I will fire it up and see what version i5 is in it and how much RAM (probably only 4 gig, is that enough? Are there any SFF boards like a pepped up Pi that have enough oomph? Electric prices have gone absolutely crazy and the wife, probably quite rightly, blames "all that junk constantly humming away upstairs" for a lot of each quarterly bill. --
|
|
|
|
Chris Wilson
I am 99% sure the spare PC is the same as one I am running for something else, so it's an i5-3470 but not a t suffix. RAM is almost certainly also 4gig, would that do for now Rob? If it will do I am downloading the recommended Ubunto Desktop version as I type, is installing the daemon exactly the same as on a Pi, or different please? Can I run it headless after installing and setting up, using VNC to see it and do any jobs, over the LAN, as I do with the Pi? Thanks Rob.
-- Best Regards, Chris Wilson 2E0ILY |
|
|
|
Or run it from your wsprdaemon dir with the standard linux approach
./wsprdaemon.sh -a (or -s/ -z whatever you want to do) I tend to forget that ever so often... Yes headless would be no problem for that setup, also with Remote Desktop Connection accessible from a Windows machine or xrdp from a Raspberry Pi |
|
|
|
Rob Robinett
Hi Chris, Your i5 with 4 GB RAM is almost certainly an OK platform. After installing Ubuntu, you will need to enable sharing to support remote access using the realvnc viewer on your PC. If you want ssh access, install the openssh-server on your server. Use the Raspberry Pi imager program (or other program) running on your PC to copy to a USB stick or uses another program to write the Ubuntu image file to a CDROM. Boot your PC to the USB or CDROM and follow the instruction on your PC';s screen Rob On Mon, Feb 28, 2022 at 7:30 AM Chris Wilson <chris@...> wrote: I am 99% sure the spare PC is the same as one I am running for something else, so it's an i5-3470 but not a t suffix. RAM is almost certainly also 4gig, would that do for now Rob? If it will do I am downloading the recommended Ubunto Desktop version as I type, is installing the daemon exactly the same as on a Pi, or different please? Can I run it headless after installing and setting up, using VNC to see it and do any jobs, over the LAN, as I do with the Pi? Thanks Rob. --
|
|
|
|
Chris Wilson
OK, nearly there I hope, but maybe due to line wrapping issues copying my wsprdaemon.conf file from the Pi PC to the desktop has gone wrong. I get this error:
hris@wsprdaemon:~/wsprdaemon$ ./wsprdaemon.sh -s wsprdaemon.sh Copyright (C) 2020 Robert S. Robinett This program comes with ABSOLUTELY NO WARRANTY; for details type './wsprdaemon.sh -h' This is free software, and you are welcome to redistribute it under certain conditions. execute'./wsprdaemon.sh -h' for details. wsprdaemon depends heavily upon the 'wsprd' program and other technologies developed by Joe Taylor K1JT and others, to whom we are grateful. Goto https://physics.princeton.edu/pulsar/K1JT/wsjtx.html to learn more about WSJT-x ': not a valid identifierprdaemon.conf: line 3: declare: ` ERROR: configuration file '/home/chris/wsprdaemon/wsprdaemon.conf' contains 'RECEIVER_LIST' which has fewer than the required 5 fields chris@wsprdaemon:~/wsprdaemon$ This is the line it's complaining about but I cannot see my error, can someone put me straight there please? Thanks. declare RECEIVER_LIST=( "KIWI_0 192.168.178.29:8073 2E0ILY/KIWI IO82qv NULL" ) ### This table defines a schedule of configurations which will be applied by '-j a,all' and thus by the watchdog daemon when it runs '-j a,all' ev ery odd two minutes ### The first field of each entry in the start time for the configuration defined in the following fields ### Start time is in the format HH:MM (e.g 13:15) and by default is in the time zone of the host server unless ',UDT' is appended, e.g '01:30,UDT' ### Following the time are one or more fields of the format 'RECEIVER,BAND' ### If the time of the first entry is not 00:00, then the latest (not necessarily the last) entry will be applied at time 00:00 ### So the form of each line is "START_HH:MM[,UDT] RECEIVER,BAND... ". Here are some examples: declare WSPR_SCHEDULE_simple=( "00:00 KIWI_0,2200 KIWI_0,630 KIWI_0,160 KIWI_0,80 KIWI_0,40 KIWI_0,10 KIWI_0,17" ) ### This array WSPR_SCHEDULE defines the running configuration. Here we make the simple configuration defined above the active one: declare WSPR_SCHEDULE=( "${WSPR_SCHEDULE_simple[@]}" ) -- Best Regards, Chris Wilson 2E0ILY |
|
|
|
Rob Robinett
It is hard to tell from your email, but it appears that some spaces are missing between fields in your KIWI_0 line. As the error message says, WD expects 5 space-separated fields on each RECEIVER_LIST line Also, your ID is very long and some spot query sites might have problems with that. just put /K at the end. On Mon, Feb 28, 2022 at 3:04 PM Chris Wilson <chris@...> wrote: OK, nearly there I hope, but maybe due to line wrapping issues copying my wsprdaemon.conf file from the Pi PC to the desktop has gone wrong. I get this error: --
|
|
|
