Beacon Timing List Not Honored #57
Comments
|
Like this:
|
|
Perfect! I didn't realize this could be entered into the web GUI. Thank you! |
|
Yer welcome ... I'm glad to be abe to close one :) |
|
Well I hate to ruin a celebration, but unfortunately the zeros I just tried in the frequency field aren't being honored. I tried both "30m 0 0 0" and "10140200 0 0 0" and in both cases my Pi continued to transmit during every 2 minute window. :( |
lbussy
changed the title
|
When I tested, it treated all frequencies in the list as ... which is still an issue but not exactly what you had. |
|
Ah the nasty ol' interrupt signal. By chance did you navigate away from the terminal window (say changed focus to another window on your PC) then come back to it? I often experience this interrupt signal when using the original WsprryPi program when going back to a terminal session. I avoid this problem by running it (WsprryPi) in a tmux session which I then “detach” away from leaving WsprryPi running. Even then, whenever I go back to the tmux session (i.e.: “reattach” to it), doing that usually kills WsprryPi with an interrupt signal. In short, it’s annoying but not new. It's been complained about over the years in WsprryPi issues. |
|
Nah that was me hitting ctrl-c to exit. The issue there was when it got a non-zero frequency, it skipped transmission. The first try there should have been 20m but it was skipped - that's the bug as I see it. |
|
This is still on my list - work actually expects me to work so I am slower than I want to be. |
|
Still scratching my head, interspersed with bricking a few SD cards while testing. |
|
Well, it freaking works now. This is a newly compiled version so I am not sure if a library difference is at play here. There is a remaining issue where I need to test the same from the web UI, then maybe I'll release an Alpha version later today. The question about |
|
@AA7US please try this:
As always, this is idempotent, and you can run it over and over. This is an Alpha branch and will go away (just in case someone sees this later on.) Theoretically, this works with a frequency list at the command line (not web GUI yet), with the above caveats. |
|
Hi Lee, Thanks for all your hard work on this. I just ran the alpha install script, rebooted, but unfortunately the wspr daemon is failing to load again. Presumably this is the same problem we covered in Issue #56. John L. |
|
Have you rebooted? I added another "known issue" for that. |
Yes. |
|
Can you give me the last few lines of Was this a new install or a clean flash? |
All of the entries in wspr.error.log are:
I installed the alpha over existing wsprrypi release v1.1.0, which was working fine except for the tx timing problem. Full history in case it matters: Back in February I started with a clean install of Bullseye (Legacy) Lite downloaded from the Raspberry Pi Foundation. I configured a few things for my network and installed chrony in place of the standard ntp client. I run OS updates. I then installed wsprrypi. Since then, I've only run and rerun your wsprrypi install script. If you want me to try a new Bullseye install followed by an alpha wsprrypi install, I can certainly do that. John L. |
|
Interesting - let me look at that a bit. If you hit it, others will. |
|
Can you give me the results of Also |
Compared to you, it looks like I'm missing some versions? |
|
Okay please see if this addresses it. If so I can add these to the install script:
|
|
Unfortunately, no joy. 🙁 |
|
If it helps any... Downloaded from Raspberry Pi Foundation on 12/5/23. |
|
That's just ... weird. It says it has them and doesn't show the latest.
|
|
Strange indeed. 🤔 |
|
I'll try a fresh OS download and install later tonight, then I'll run the alpha script again. It can't hurt to try. John L. |
|
I think I can go back to the image you have and try as well. |
|
One last thing to try: |
|
|
Grr! Well, I know what's needed, not how to get it (yet). |
|
Okay, wanna give it another go? I statically linked the compiler libs. If this doesn't work, I need to try a different path. |
|
Good morning Lee, I reran the alpha script. Unfortunately the problem is still there. Below are the entries from install.log followed by a wspr daemon status (failure exit). There are GLIBC not found entries in the install log now that didn't appear during previous installs. John L. |
|
Maybe I should take up skydiving. The errors now are because it executes wspr if it is there to get the version. That failed as expected. The new one not running is a mystery for now. More digging. |
Or bungee jumping. Either might be more enjoyable for you. 🙂 |
|
I love bungee jumping! Skydiving too. Maybe this explains ... |
|
I finally have some good news Lee! I downloaded a copy of 32 bit Raspberry Pi OS Bookworm this morning (recall that I've been using 32 bit Bullseye), installed it on an SD card, run OS updates, rebooted, then ran the WsprryPi alpha script. I rebooted and found the wspr daemon was running! Now everything is almost functioning perfectly with WsprryPi except: Beacon timing IS being honored when run from the command line but not when setup using the web GUI. I think you already knew about this and are working on it. FYI: Immediately after installing Bookworm, I ran So I guess this means WsppryPi isn't supported running under Raspberry Pi OS Bullseye (Legacy) but is fine when running under Raspberry Pi OS Bookworm? 73, John L. |
|
Well, it all depends on whether I can figure out why it's not working. Right now, I'm pissed at it, but not given up yet. I'm VERY glad to hear you got it working, at least to where it's working here. The app is small and I have always intended that it could be dropped onto any Pi, but maybe that's not practical with the low-level memory and GPIO control. Also, 10M is dead today, so I have been fighting with this thing... :) |
|
So it "looks like" we will have to live with "Bookworm or better" for the glibc errors. I'm gonna just tell myself that's fine; maybe I'll come back to it, maybe not. I will now go back to the original issue: the web UI freq list is not being honored. |
|
Hi Lee, I've been using WsprryPi exclusively from the command line to get beacon timing control since timing control wasn’t working for me from the web interface. Today I decided to revisit the web interface just out of curiosity. I setup the configuration to transmit a beacon every 8 minutes using “30m 0 0 0” and now it’s working perfectly! IOW, the timing IS being honored from the web interface. I don’t what’s changed since February when I couldn’t get it to work, but it’s fine now. Come to think of it, there IS one thing I did… I recently reinstalled the software to enable the shutdown button option that I'd previously had disabled. Maybe it's just coincidence or maybe that fixed something . Anyway, I'm still using the alpha release version that you'd provided in one of these threads. Thanks for software. I use it all the time. |
|
Dear Lee, '2024-10-15 13:51:52 GMT Notice: INI file changed, reloading parameters. Which was as expected. When the WSPR transmission window opened the transmission started and the log was appended with: '2024-10-15 13:52:01 GMT Obtained new ppm value: -3.658569 As one can see, the first three transmissions happened as expected but then a further one occurred on 6m. After the completion of this transmission the cycle started again with a 2m transmission. It appears to me that the original frequency string (6m 6m 6m 6m) was overwritten with the new one (2m 6m 6m) but did NOT use the proper string length of 8 characters but the old one of 11 characters. Hence another 6m transmission was performed before it recycled with a 2m transmission. Could it be that the pointer to the end of the frequency string is not properly updated when the new configuration was saved? Please let me know if you need some clarification or further tests. 73s, Lothar (DK9FQ) |
|
Grüß Lothar! Thank you for those observations. I have to admit, and I am ashamed to do so, that I have not even been able to install my dev environment on my new systems, let alone look at this. The idea of grinding through this to find a place to start feeding my inner procrastination gene means I have not gotten anywhere on this. You may have given me the foothold I need. |
Please consider adding the ability to control how often WSPR beacons are transmitted using the web GUI as can be done from the command line.
For example, to transmit one WSPR beacon on the 30M band every 8 minutes (repeating indefinitely), a sample command is:
wspr -r -s N9NNN EM10 20 1014020 0 0 0
It sure would be convenient to accomplish the same thing using the web GUI. :)
73,
AA7US
The text was updated successfully, but these errors were encountered: