Hi, Jarmo.
Does that mean that "CQ: Max Dist" is setup to work *only* with the ARRL
International Digital Contest?
Neither the Release Notes nor the -rc4 User Guide say anything about "CQ:
Max Dist", so it is difficult to say. "CQ: Max Dist" looks like the FT8
version of the "Best S+P"
Hi, Dennis.
I will try the Hamlib dll from v2.5.4, a version where I had no problems
with sudden closing.
I cannot say whether the sudden closings apply to FT4, but I cannot
remember noticing the sudden closing in FT4, whilst it happens now and then
with FT8, as described.
Re the "CQ: Max Dist"
For those having problems please provide some debug to see if we can figure
this out.
Please place this file as described
belowhttps://www.dropbox.com/s/t52ngcalsgnpm8m/wsjtx_log_config.ini?dl=0
C:\Users\[username]\AppData\Local\WSJT-X The WSJT-X_Rigcontrol.log file will
be in the same
Thu, 13 Oct 2022 08:34:37 -0400
Dennis W1UE via wsjt-devel kirjoitti:
Problem2 in not a problem, hover mouse over text, you can see, that
shoud wor with ARRL contest.
jarmo, oh1mrr
> I can also confirm problem #1. It is the same problem that existed in
> version 2.6.0 RC1,2,3 and 4.
>
> Since
I can also confirm problem #1. It is the same problem that existed in
version 2.6.0 RC1,2,3 and 4.
Since I use WSJT in combination with N1MM+ for logging, I get a "TCP Error"
when the program closes.
If I'm not using the combo, WSJT just closes. I have not noticed that the
closing occurs when
I can confirm problem 1, as it happened to me less than an hour ago, including
the orphaned JT9 decoding application. Running Win 10 on a Lenovo X1 Carbon
laptop. I had been on FT8 for about an hour when it happened.
Ed N4II.
From: Frode Igland via wsjt-devel
Sent: Thursday, October
I have used -rc4 since it was released and have found it quite stable with
three notable exceptions:
*1. Sudden closing in FT8 after extended periods of operation*
After an extended period of use in FT8 mode (normally more than two hours),
WSJT-X may close down abruptly. The closing happens at
