Rather good way to get qso one period faster. Important with VHF ES
DXing (mostly 6m). Conditions change so fast.
There are not so many 4 character grids in Japan. And if callsign's QRZ
or HamQTH entry is up to date external logger adds the locator, usually
6 characters, or even more precise.
ct during the JA run, but correct both before and after it.
Ed N4II.
-Original Message-
From: Jim Brown via wsjt-devel
Sent: Saturday, July 17, 2021 6:29 AM
To: jan0--- via wsjt-devel
Cc: Jim Brown
Subject: Re: [wsjt-devel] WSJT-X 2.5.0-rc3 RST_RCVD logging issue
On 7/17/2021 2:59
On 7/17/2021 2:59 AM, jan0--- via wsjt-devel wrote:
It is characteristic of this propagation phenomenon between NA and AS on
6m that the opening between any given pair of stations is brief: One or
two minutes is not uncommon.
That depends a LOT on which part of the US and which DX country. He
believe it to be coincidental to the RST_RCVD logging issue.
Ed N4II.
From: Derek Turner
Sent: Saturday, July 17, 2021 2:33 AM
To: WSJT software development
Cc: j...@comcast.net
Subject: Re: [wsjt-devel] WSJT-X 2.5.0-rc3 RST_RCVD logging issue
Hi
Is it just coincidental that of the 33
On 7/16/2021 11:33 PM, Derek Turner via wsjt-devel wrote:
Is it just coincidental that of the 33 log records only two contain
Maidenhead locators.
Nope. I've probably worked close a hundred JAs, and I count count the
ones who call with their grid without taking my shoes off. But JA hams
are n
Hi
Is it just coincidental that of the 33 log records only two contain Maidenhead
locators.
And why do JAs en mass ignore locators which are fundamental in FT8 exchanges
for the rest of us ?
73 de G4SWY Del +++
Sent from Yahoo Mail on Android
On Sat, 17 Jul 2021 at 3:49, jan0--- via
wsjt
I had a 6m FT8 JA run using WSJT-X 2.5.0-rc3 today. After the event, I
copied the wsjt_log.adi file and uploaded the copy to my logging program,
where I noticed a curious, deterministic pattern in the RST_RCVD column
[Capture.PNG attached].
These incorrect RST_RCVD values were also in the wsjt
