Date
1 - 18 of 18
WD 3.0 beta testing
|
Thanks dear Rob,
OK all I'm looking forward to apply RTL-SDR. 73, Hidehiko JA9MAT |
|
|
|
Rob Robinett
I'm sorry but it is a completely untested feature and I was unable to find a driver which could tune the RTL with sufficient accuracy for WSPR decoding. On Fri, May 20, 2022 at 7:14 PM Hidehiko Komachi - JA9MAT <qrper72@...> wrote: Hello, --
|
|
|
|
Hello,
I'd like to test RTL-SDR on WD 3.0 beta version. Is this avairable now? Hidehiko JA9MAT |
|
|
|
Rob Robinett
I have just checked in some fixes to 3.0.2 to support installation of Pi 'buster' and 'bullseye' and Ubuntu 20.04.
Also, I added support for the 22M band: "KIWI_0,22" is an example of the conf file syntax. That code is running at KPH on a Pi4 buster which needed to be changed to '-o 3' or it runs out of CPU with the 15 rx channels) At KFS the code runs on a 28 channel Thinkcenter Ubuntu 20.04 which finishes decodes in about 70 seconds. Although I think they were working, in order to get log lines about scheduling I also reworked and tested the schedule's sunrise/sunset calculations. The schedule times are referenced to the time reported by the linux 'date' command. So if your server is set for UDT, then the schedule times are referenced to UDT. I don't have a server set for UDT, so I would appreciate any testing done on a UDT server. |
|
|
|
Running great on a Pi4 (Bullseye) with a little help from Rob. I'm really impressed with the capabilities and I've just scratched the surface. Update: very stable running and it loafs along on a 2gb Pi4. |
|
|
|
Rolf Ekstrand
Updated to 3.0.2 on my Raspi 4 running the old Buster last night. I am still only running 40 to 10 due to high noise in the area.
No problems yet as far as I can see. K9DZT - Rolf |
|
|
|
WA2TP - Tom
I too just updated to 3.0.
Unfortunately something went wrong.
I see connections on all kiwis with 3.0, however they drop after 20-30 seconds with no uploads.
On May 3, 2022, at 10:39 AM, Rob Robinett <rob@...> wrote:
|
|
|
|
Rob Robinett
Hi Cathal, Thanks for the report. I was wondering about who was reporting from that HB9 call. My WD 3.0 beta testing work has been centered for the last couple of days on getting WD to install on 'bullseye' the Python libraries needed to generate noise graphs and the sunrise/sunset times. It seems you have found the commands needed to do that faster than I did. I am working on the code in WD needed to detect when to run those commands instead of the installation using the legacy procedure. When that work is done I will check in what will be V 3.0.0 Rob On Tue, May 3, 2022 at 5:30 AM Cathal Ferris <groups.io@...> wrote: Solved my runtime errors at least, the graphs will take a bit of time to verify: --
|
|
|
|
Solved my runtime errors at least, the graphs will take a bit of time to verify:
sudo pip install numpy --upgrade ; sudo apt update ; sudo apt-get install libatlas3-base Unsure why numpy was multi-versioned for me, but it now works when the global version is up to date as per the installation via pip After that I was seeing errors related to a missing libcblas.so.3 library. Installing libatlas3-base provides the functionality that was needed there. v3 wsprdaemon script now executes as one would expect. |
|
|
|
I had to rebuild the Pi4 that I had been happily running wsprdeamon on in the past. The SD card had given up, and systemd login daemon self-corrupted. No time-efficient way to repair so a full reinstallation it was with limited backups performable. (I'm also updating my Kiwis to Buster and I may have a dead Kiwi cape to deal with separately. The fun never ends ;) ) The system is built from the raspianOS image bullseye-lite dated April 22, with a full "aptitude update ; aptitude upgrade" completed on install.
Installing wsprdaemon, I did run into the "qt5-default" problem with the 2.x tree. I didn't get an adequate resolution to that - but I did not spend a lot of time on that at that point; and I figured "why not try 3.x?" 3.x appears to Install fine(ish). I'm using the same config file I had backed up from the previous instance. I do get results that are seen on wspr.rocks, under the Swiss callsign I've been allocated since the QTH move (HB9HJF) ; One issue is the noise graph is not being generated locally, and there are other issues when executing the script. The noise graphs are being seen on http://wsprdaemon.org/graphs/HB9HJF/ happily enough, so I can see that the numbers are present from the daemon, but they are not being seen on the local server, likely due to python math libraries not present/working for the local graph generation. While I could probably beat at things and make it work, I figured it would be more proper to document here so that it could be seen clearly. The second oddity is that each script execution it does not see that matplotlib is available, then it does see it's satisfied. Happy to answer questions or to allow an SSH access/screen share at some point if needed. When I run as my normal pi user this is the output I see. matplotlib fail, then repeating sets of numpy errors/tracebacks. pi@piserver:~/wsprdaemon $ ./wsprdaemon.sh -a
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
WARNING: LC_NUMERIC 'en_IE.UTF-8' on your server is not the expected value 'en_US.UTF-8'.
If the spot frequencies reported by your server are not correct, you may need to change the 'locale' of your server
Tue 03 May 2022 09:35:08 UTC: install_python_package() Package matplotlib is not installed. Checking that pip3 is installed
Tue 03 May 2022 09:35:12 UTC: install_python_package() Having pip3 install package matplotlib
Looking in indexes: https://pypi.org/simple, https://www.piwheels.org/simple
Requirement already satisfied: matplotlib in /usr/local/lib/python3.9/dist-packages (3.5.1)
Requirement already satisfied: pillow>=6.2.0 in /usr/local/lib/python3.9/dist-packages (from matplotlib) (9.1.0)
Requirement already satisfied: numpy>=1.17 in /usr/lib/python3/dist-packages (from matplotlib) (1.19.5)
Requirement already satisfied: kiwisolver>=1.0.1 in /usr/local/lib/python3.9/dist-packages (from matplotlib) (1.4.2)
Requirement already satisfied: packaging>=20.0 in /usr/local/lib/python3.9/dist-packages (from matplotlib) (21.3)
Requirement already satisfied: cycler>=0.10 in /usr/local/lib/python3.9/dist-packages (from matplotlib) (0.11.0)
Requirement already satisfied: fonttools>=4.22.0 in /usr/local/lib/python3.9/dist-packages (from matplotlib) (4.33.3)
Requirement already satisfied: pyparsing>=2.2.1 in /usr/local/lib/python3.9/dist-packages (from matplotlib) (3.0.8)
Requirement already satisfied: python-dateutil>=2.7 in /usr/local/lib/python3.9/dist-packages (from matplotlib) (2.8.2)
Requirement already satisfied: six>=1.5 in /usr/lib/python3/dist-packages (from python-dateutil>=2.7->matplotlib) (1.16.0)
Tue 03 May 2022 09:35:17 UTC: install_python_package() Installed Python package matplotlib
pi@piserver:~/wsprdaemon $ Traceback (most recent call last):
File "/home/pi/wsprdaemon/suntimes.py", line 2, in <module>
from astral import Astral, Location
ImportError: cannot import name 'Astral' from 'astral' (/usr/local/lib/python3.9/dist-packages/astral/__init__.py)
/home/pi/wsprdaemon/config_utils.sh: line 278: astral_times[0]: unbound variable
Traceback (most recent call last):
File "/home/pi/wsprdaemon/suntimes.py", line 2, in <module>
from astral import Astral, Location
ImportError: cannot import name 'Astral' from 'astral' (/usr/local/lib/python3.9/dist-packages/astral/__init__.py)
/home/pi/wsprdaemon/config_utils.sh: line 278: astral_times[0]: unbound variable
RuntimeError: module compiled against API version 0xf but this version of numpy is 0xd
Traceback (most recent call last):
File "/home/pi/wsprdaemon/noise_plot.py", line 16, in <module>
import matplotlib as mpl
File "/usr/local/lib/python3.9/dist-packages/matplotlib/__init__.py", line 109, in <module>
from . import _api, _version, cbook, docstring, rcsetup
File "/usr/local/lib/python3.9/dist-packages/matplotlib/rcsetup.py", line 27, in <module>
from matplotlib.colors import Colormap, is_color_like
File "/usr/local/lib/python3.9/dist-packages/matplotlib/colors.py", line 56, in <module>
from matplotlib import _api, cbook, scale
File "/usr/local/lib/python3.9/dist-packages/matplotlib/scale.py", line 23, in <module>
from matplotlib.ticker import (
File "/usr/local/lib/python3.9/dist-packages/matplotlib/ticker.py", line 136, in <module>
from matplotlib import transforms as mtransforms
File "/usr/local/lib/python3.9/dist-packages/matplotlib/transforms.py", line 46, in <module>
from matplotlib._path import (
ImportError: numpy.core.multiarray failed to import
RuntimeError: module compiled against API version 0xf but this version of numpy is 0xd
Traceback (most recent call last):
File "/home/pi/wsprdaemon/noise_plot.py", line 16, in <module>
import matplotlib as mpl
File "/usr/local/lib/python3.9/dist-packages/matplotlib/__init__.py", line 109, in <module>
from . import _api, _version, cbook, docstring, rcsetup
File "/usr/local/lib/python3.9/dist-packages/matplotlib/rcsetup.py", line 27, in <module>
from matplotlib.colors import Colormap, is_color_like
File "/usr/local/lib/python3.9/dist-packages/matplotlib/colors.py", line 56, in <module>
from matplotlib import _api, cbook, scale
File "/usr/local/lib/python3.9/dist-packages/matplotlib/scale.py", line 23, in <module>
from matplotlib.ticker import (
File "/usr/local/lib/python3.9/dist-packages/matplotlib/ticker.py", line 136, in <module>
from matplotlib import transforms as mtransforms
File "/usr/local/lib/python3.9/dist-packages/matplotlib/transforms.py", line 46, in <module>
from matplotlib._path import (
ImportError: numpy.core.multiarray failed to import |
|
|
|
Ssh is installed as that is how I get in, remember you have access without the remote server. It is not the standard port and you had me set it up for you to log in without a password.
toggle quoted message
Show quoted text
. On Apr 28, 2022, at 15:12, Rob Robinett <rob@...> wrote:
|
|
|
|
Rob Robinett
It appears that the ssh service is not installed on your i7. A default installation of Ubuntu 20.04 LTS doesn't install the 'openssh-server' but I recently added code to WD 3.0 which should install that service if REMOTE_ACCESS_CHANNEL is defined in your conf file. It is hard for me to test that auto-installation of 'openssh-server' is working, so it would help if you could run" dpkg -l openssh-server If nothing is listed, then run: sudo apt install openssh-server and I should be able to log in. On Thu, Apr 28, 2022 at 11:30 AM KD2OM <steve@...> wrote:
--
|
|
|
|
Rob, I made the i7 KD2OM, APi-1 _1 and APi-2 _2
toggle quoted message
Show quoted text
You know the login details for the i7 Steve . On Apr 28, 2022, at 13:25, Rob Robinett <rob@...> wrote:
|
|
|
|
Rob Robinett
Obviously those specific values are for Steve.
If others want to offer me access to their WD servers, PM me and I'll offer you your own REMOTE_ACCESS_CHANNEL number. In addition to making those changes to your conf file and then running any WD command, you will need to PM me a login name and password on your WD server. That login will need to have sudo permissions for me to do useful debugging. For closer to realtime help, join my Telegram 'wsprdaemon' channel |
|
|
|
Rob Robinett
yes, add to your i7's conf file: REMOTE_ACCESS_CHANNEL="12" SIGNAL_LEVEL_UPLOAD_ID="KD2OM_1" The SIGNAL_LEVEL_UPLOAD_ID must be different from that on the APi, but that "KD2OM_1" will not affect your wsprnet.org reporter ID. "KD2OM_1" is used only to label your noise graphs and to ID your remote access connection. On Thu, Apr 28, 2022 at 8:57 AM KD2OM <steve@...> wrote:
--
|
|
|
|
Thanks Rob, I have updated all systems. BTW I am running the I7 system now most of the time. I don’t believe the APi can keep up. I also switched all my KiwiSDR to 14 channel again.
toggle quoted message
Show quoted text
Should I add the remote command to the i7? . On Apr 28, 2022, at 10:37, Rob Robinett <rob@...> wrote:
|
|
|
|
Rob Robinett
I have checked in a fix for the problem where MERGE would not select the best SNR.
'git pull' to get that fix. 'wd -V' will print "Version = 3.0.1" if you are running that fixed code. |
|
|
|
Rob Robinett
The WD 3.0 software has been running at my AI6VN/KH6, KPH and KFS sites for several months, and in the last two weeks I have helped bring it up on an additional 8 sites. In most of those installations it seems to run as stably as 2.10k and 3.0 includes many 'behind-the-scenes' enhancements to slightly improve the number of spots reported. I have also just created a Telegram 'Wsprdaemon' channel which I will monitor. WD 3.0 includes a remote support option which when enabled in your conf file will, with your permission, allow me to log on to your WD server to help with installation and debugging.
So I am inviting those who are interested in joining the 3.0 beta program to install it. For existing WD 2.10 users: cd ~/wsprdaemon ./wsprdaemon.sh -z git pull git checkout v3.0 ./wsprdaemon.sh -a The ./wsprdaemon.conf file formats are backwards compatible, and you can return to use 2.10 by executing 'git checkout main' in the above commands. |
|
|