ess may be testing enough!
73
Gary ZL2iFB
-Original Message-
From: Alex, VE3NEA
Sent: Thursday, 8 March 2018 10:11 a.m.
To: wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] DXpedition Mode Test Results
> - Of course, some Hounds did not operate as intended. Several k
> On Mar 7, 2018, at 1:27 PM, Joe Taylor wrote:
>
> I'm sure there is more to be said, but that will do for now. Depending on
> programming progress and on my own travel schedule, we may schedule another
> public test within a few weeks.
Thanks for the great job, Joe. It’s clear that lots
Hi Alex,
On 3/7/2018 4:10 PM, Alex, VE3NEA wrote:
- Of course, some Hounds did not operate as intended. Several kept
trying to raise Fox by calling below 1000 Hz.
Perhaps the software should block attempts to send Tx1 below 1000 Hz if
Hound mode is enabled, and show a popup message explaini
- Of course, some Hounds did not operate as intended. Several kept trying to raise Fox by calling below 1000 Hz.
Perhaps the software should block attempts to send Tx1 below 1000 Hz if Hound mode is enabled, and show a popup message
explaining why transmission did not start.
73 Alex VE3NE
Magnificent summary. Bravo!
-Original Message-
From: Joe Taylor [mailto:j...@princeton.edu]
Sent: Wednesday, March 7, 2018 12:28 PM
To: WSJT software development
Subject: [wsjt-devel] DXpedition Mode Test Results
Hi all,
Here are a few highlights of results from last night's p
Hi all,
Here are a few highlights of results from last night's public test of
FT8 DXpedition Mode:
- The overwhelming majority of participating Hounds operated as
intended, and according to instructions. I copied 190 unique Hound
callsigns during the 2300 hour (when I was acting as Fox on
There was no propagation on 20m and 30m, but on 40m and 80m I worked DX quickly and without problems. There were a few glitches
that are hopefully not difficult to fix.
1. When the Fox answered my call at 01:02:00 (see the attached screenshot), his message appeared on the left panel but not on
As expected, propagation from K1JT in NJ to K1HTV in VA on 20M was marginal. It
took a skewed path beam heading towards SA to produce a report from Joe, but no
complete QSO was made on 20M. QRM from XE1GK on 14080.250 didn't help. On 30
Meters, signals from Don, N1DG, as W1/KH7Z, started OK but
