When I start calling station with TX2, station which have "/" in
call, happens weird thing.
072630 -10 0.4 553 ~ VK4JNA/5 RR73
072645 Tx 1047 ~ OH1MRR -12
072700 -8 0.4 553 ~ OH1MRR R-14
072715 Tx 1047 ~ VK4JNA/5 RR73
072730 -6 0.4 553 ~
Fri, 22 Nov 2019 20:21:47 -0800
Jim Brown kirjoitti:
> On 11/22/2019 2:33 PM, Grant VK5GR wrote:
> > and FOX mode is playing a big part in the success of that.
>
> I see FT8 and DXpedition mode to be the greatest thing to happen to
> the little pistol station since I learned CW 60 years ago.
>
On 11/22/2019 2:33 PM, Grant VK5GR wrote:
and FOX mode is playing a big part in the success of that.
I see FT8 and DXpedition mode to be the greatest thing to happen to the
little pistol station since I learned CW 60 years ago.
73, Jim K9YC
___
w
On 11/19/19 at 8:01 AM, iztok.s...@telekom.si (Iztok Saje) wrote:
Hi!
On band activity: how about ALL.TXT?
On linux:
tail -f ALL.TXT |grep -v A35JT
would give nice idea what is going on the band segment.
I assume ALL.TXT works in Fox mode, and there are similar
commands in Windows as well.
Joe,
Sorry, the on list response was in responses to Steve's question which was made
on this forum.
Other questions I have replied to you directly. However one I will reply to
here. A35JT's peak QSO rate was 340/hr to Japan on 12m from memory. We
regularly ran at 150-200+ an hour for expected
Grant --
You asked me to take our exchanges off-list, but then you seem to have
reverted to the list. So for the record, I'll respond here.
As I explained to you off-list, the ALL.TXT file in WSJT-X 2.1.0
provides the information you asked for, in real time.
Perhaps we can furnish this inf
Hi Grant,
I assume that the timestamps in the ALL.TXT are taken from the slot time
counter at the moment, when software has performed its reception decoding. If
the decoding happens to take place after the start of the next transmission,
then the time indicated is wrong. That may or may not bee
