Have you tried running WireShark on another machine and watching the traffic?
Perhaps all the traffic dies and not just WSPRnet?
alex
K6LOT
> On Jun 1, 2023, at 10:03 PM, Peter Sumner via wsjt-devel
> wrote:
>
> Hello,
> while WSJT-X is a small part of this puzzle, it is a key one so hence I
Hello,
while WSJT-X is a small part of this puzzle, it is a key one so hence I am
posting this here. I have for a long time now been using WSJT-X (v1.8 right
through to the current release for ARM v2.61 ) on a Raspberry Pi for a
dedicated WSPR station with two Icom rigs on VHF. Over time both the P
I have seen this twice before, all while switching configurations.
However, not
every time I switch configurations do I see it. It only happens once in a
while.
Using 2.7.0RC1 Improved, Win 10/11.
Dennis W1UE
On Thu, Jun 1, 2023 at 2:36 PM Rick via wsjt-devel <
wsjt-devel@lists.sourceforge.net
Hi
I have the same situation.
Running Linux Mint 20.3 and wsjtx2.7.0-rc1 built from source.
The Optimising Decoder FFT dialog only pops up (intentionally) if the
fail to mem_qmap dialog is on the screen for some time although it's
less than the 15 seconds stated in the code comments, more lik
Dear developers,
When switching to a predefined configuration, an information dialog pops up
with the message 'Unable to create shared memory segment mem-qmap',
followed by another modal message a few secs later 'Optimizing FFTs for your
CPU. Please be patient ...'
After that, the program does n
