Michelle,
My logging program is Log4OM ver2. I routinely import my WSJT-x adi files into
Log4OM with no problems. Most logging programs import only current loggings.
Ensure you click something like “do not import duplicates” in your logging
program as you download and you should have no prob
I'm new to FT8 and WSJT software. Is a way to export from the log only the
recent contacts? This way I don't make duplicates in my logging programs but
still keep contacts in the WSJT log for notifications of new (preventing
duplicate contacts in FT8). ThanksMichelle N3YRZ___
On Wed, May 20, 2020 at 2:05 PM Gary McDuffie wrote:
>
> If you call letting him know that you got his acknowledgement of your
> report a courtesy, I guess so. I call it a necessity in order to allow him
> to move on. If I don’t send the 73, it means I didn’t get his RR73. If he
> doesn’t fini
Ed,
There is a strange anomaly that makes no sense yet many of us that (especially)
work weak DX observe frequently ... Sometimes when you end up in a R -XX/RR73
loop ("RR/73 loop" or "ACK dance" as you term it) with a station anecdotally
and observationally sometimes sending 73 sequences back
There will always be uncertainty about what the other guy is thinking and
doing, whether our messages have been received and understood etc. Exchanging
RR73, 73 and free text messages at the end of a QSO extends the QSO sequence so
reducing any remaining uncertainty with each additional message
Ps: The JPEG's supplied show changes in Tx frequency when the "Tx spinner-box"
widget has its "up" control selected while transmitting !
-Original Message-
From: Stephen VK3SIR
Sent: Thursday, 21 May 2020 7:24 AM
To: WSJT software development
Subject: Re: [wsjt-devel] 2.2.0 rc1 - Allow
Joe and the Core Development Team,
Test environ: The Main FT-991 connected to a 80m Doublet (v2.2 rc1); Second
environ is a FT-897D with SCU-17 into a dummy load (v2.1.2). Test band is 20m.
I can confirm as that on FT8 transmissions that frequency changes on Tx are
blocked.
But...
Yet the T
> On May 20, 2020, at 10:28, Neil Zampella wrote:
>
> The 73 from you is a courtesy ... the RR73 is saying "Roger Roger -
> BYE'"basically ... we're good.This is why the program then
> switches to the Tx6 to send the next CQ call.
If you call letting him know that you got his acknowle
Both stations should log the QSO when RR73 is sent. At that point in the
message sequence both QSO partners have exchanged call signs, reports and
acknowledgements (R -04 and RR73). No further messages need to be exchanged.
Rather than sending a third ACK, e.g., 73, to confirm receipt of the s
Gary ...
The 73 from you is a courtesy ... the RR73 is saying "Roger Roger -
BYE'" basically ... we're good. This is why the program then
switches to the Tx6 to send the next CQ call.
If you didn't get the RR73, the program will resend the Tx3 R-xx message.
Neil, KN3ILZ
On 5/19/2020 11
Joe,
Sorry, I copied the wrong (already modified) line. Here is the original line
5736 from WSJT-Xs mainwindow.cpp:
5735 if(i==14) ui->cbHoldTxFreq->setVisible(b);
5736 if(i==14 and (!b)) ui->cbHoldTxFreq-> setChecked(false);
5737 if(i==15) ui->sbSubmode->setVisible(b);
Joe,
FYI: The error that Hold TX Frequency button is always unchecked after some
mode changes, results from line 5736 in mainwindow.cpp. If that line is
disabled (//), the error disappears and the Hold TX Frequency button remains
enabled.
5735 if(i==14) ui->cbHoldTxFreq->setVisible(b);
12 matches
Mail list logo
