Here is what I have setup
WSJT-x 2.1.2 running on a linux (Ubuntu 20.04) Intel Nuc sending UDP data to the laptop on 2237
RumLogNG 5.2 running on my OSX BigSur Laptop
Here is what IS working
WSJT-X QSOs are logged in RumLogNG
WSJT-X is sending info to DXCluster to RumLogNG
RumLogNG is triggering transmit on WSJT-X when the "auto" button is checked in the network window
What isn't working
Once an auto transmit is sent, WSJT-X continues to transmit until the watchdog timer kicks in.
It appears RumLogNG is not sending the "stop Transmit" command after 3 transmits (per user manual)
RumLogNG doesn't add the callsign to the 20 minute block list and so even after hitting a watchdog timer (5 minutes) RumLogNG triggers another transmit to the same callsign.
Any Ideas?
WSJT-X Auto issue
Re: WSJT-X Auto issue
Pse note: The counter resets always when you receive the other station sending your callsign.
73 and best dx de Tom, DL2RUM
Re: WSJT-X Auto issue
In the scenario above, the station being called is not replying to my call at all. So it should not be resetting the counter
Re: WSJT-X Auto issue
So I grabbed a screen recording from both machines of the behavior I'm seeing.
Main window is OSX running RumLogNG, and inset window (purple outline is my linux box running wsjt-x.
https://youtu.be/mElzl7FAx-M:
Main window is OSX running RumLogNG, and inset window (purple outline is my linux box running wsjt-x.
https://youtu.be/mElzl7FAx-M:
Re: WSJT-X Auto issue
I've found the time now to confirm this misbehaviour. It will be fixed in the next update.
Tnx for the hint!
Tnx for the hint!
73 and best dx de Tom, DL2RUM
Re: WSJT-X Auto issue
Awesomesauce!
Thanks for the update.
Thanks for the update.
Re: WSJT-X Auto issue
Confirmed this issue is resolved in the latest release.
Thanks for fixing this!
Thanks for fixing this!