Thanks a lot, Joe. Looking forward to try it. The User Guide translation is
in progress. 73, Frode LA6VQ
man. 1. juli 2024, 21:11 skrev Joe Taylor :
> Hi Frode,
>
> On 7/1/2024 2:25 PM, Frode Igland LA6VQ wrote:
> > Thanks for the new and exciting version.
> > How do we get to practice SuperHound
Thanks a lot, Joe. Looking forward to try it.
The User Guide translation is in progress,
73, Frode LA6VQ
man. 1. juli 2024, 22:19 skrev Charles Suckling via wsjt-devel <
wsjt-devel@lists.sourceforge.net>:
> Hi Lloyd
>
> Here's a quick start guide for setting up SDRC to support QMAP.
>
>
> https:/
Thanks for the new and exciting version.
How do we get to practice SuperHound operation? Will there practice
sessions with a designated SuperFox, or will we have wait for N5J to be
able to test for bugs and improvement proposals?
73, Frode LA6VQ
man. 1. juli 2024, 20:19 skrev Joe Taylor via wsjt-d
Using WSJT-X 2.7.0-rc2imp I experience this as a new "feature":
When a counterpart responds to my CQ, or he/she tailends a QSO I am
finishing, both start time and end time are logged with TIME_OFF only, i.e
a duration of 0 seconds.
However, when I respond to stations calling CQ, or I tail-end a Q
Regarding logged time in cabrillo. Let's reason backwards:
1. Cabrillo is a file format used for submitting contest logs only.
2. Cabrillo is a file format normally created from an ADIF file that is
created by specialized logging software, say N1MM Logger+, WinTest or some
other contest software.
3
Forgive me for asking, but why would you need to highlight Fox messages in
addition to the easily observable characteristics of Fox/Hound mode?
As this is the WSJT-X dev forum, I assume that you are talking about the
WSJT-X software and "real" Fox/Hound, not any multi-stream operation. When
you are
I have nothing against getting WD reporting in the UDP Status message, but
I guess the most important part of the WD in Hound mode is that the "Enable
Tx" button is deactivated, and that the operator must be able to maintain
an attention span of two minutes to reactivate the "Enable Tx" button. Tha
The User Manual for FT8 DX-pedition mode, "Detailed Instruction for Hounds"
# 11 at the top of page 5, says:
> You will need to re-activate Enable Tx (or hit
> Enter on the keyboard) at least once every two minutes. (This restriction
> is to
> ensure that an operator is present and paying attentio
To permanently fix this issue and prevent further
> similar problems in combination with other software I would therefore
> welcome it if the WSJT-X software could be adapted such that the generated
> ADIF file always complies with the specifications.
>
> Regards
> Roman HB9HDN
&g
Q
tor. 20. okt. 2022 kl. 00:25 skrev Laurie, VK3AMA via wsjt-devel <
wsjt-devel@lists.sourceforge.net>:
>
>
> On 20/10/2022 12:05 am, Frode Igland via wsjt-devel wrote:
> > I have used the "Tx power" field in the WSJT-X logging window for most
> > of my tens of th
Hi, Roman.
My experience is that the ADIF format accepts more than the ADIF
specifications may indicate. I have used the "Tx power" field in the WSJT-X
logging window for most of my tens of thousands of WSJT-X QSOs. Whether I
enter "40 W", "40W" or "40", it hits my HRD Logbook as "40", i.e. a clean
WSJT will
> > select the DL station to call.
> >
> > Dennis W1UE
> >
> >
> > On Thu, Oct 13, 2022 at 8:21 AM jan0--- via wsjt-devel <
> > wsjt-devel@lists.sourceforge.net> wrote:
> >
> > > I can confirm problem 1, as it happened to
ect the DL station to call.
>
> Dennis W1UE
>
>
> On Thu, Oct 13, 2022 at 8:21 AM jan0--- via wsjt-devel <
> wsjt-devel@lists.sourceforge.net> wrote:
>
>> I can confirm problem 1, as it happened to me less than an hour ago,
>> including the orphaned JT9 decoding ap
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 the
14 matches
Mail list logo
