Morning all, I was only able to participate in the last 20 minutes of the 20m 
test and most of the 30m test. Due to propagation, l was not able to decode the 
fox on either band although I saw many hounds calling and providing their 
signal reports. 

I had set up wsjtx the night before in hound mode so it would be ready once I 
got on the air for the test. Once I started it up last night, I noticed a 
couple of weird things:

The program locked up when ran my auto tuner. Resolved by closing and 
restarting. Never happened before. 

The program got “stuck” in the decode phase several times requiring close and 

The program would not pass CQs (I.e. the Mexican station) to JT bridge.  
Usually passes CQs without fail. 

Frustrated, I changed back to non DXpedition mode and closed the program. 
Restarted in regular FT8 mode then switched back to hound and everything worked 

So I’m not sure whether this is the way the software is supposed to work or not 
but if it is, a stronger admonition in the user manual about not starting the 
program in fox or hound mode may be warranted. 

For the record, I’m running the OSX version on a MacBook Pro with JTBridge and 

Hope this useful. Gary KO3F 

Sent from my iPad

> On Mar 7, 2018, at 6:40 AM, Jay Hainline <> wrote:
> My observations.
> I was only able to participate during the first 20 minutes of the 20 meter
> test at 2300z. Joe was decoding around -18 during the time and I was calling
> using barefoot power. According to pskreporter, Joe heard me but I was never
> called.
> So my question is why I was never called? Does my callsign get pushed down
> the list when new calls are decoded? What sort order was Joe using at the
> time? Is there a "first come, first serve" sort order to the queue of hounds
> to be called?
> Judging by comments I have seen, the lack of RR73 message being sent causing
> hounds to send R-report over and over, there is still work to be done before
> it is dxpedition ready. I hope there are more tests and I will be able to
> participate fully.
> Thank you to the developers for putting this all together. It is very
> interesting!
> 73 Jay KA9CFD
> -----Original Message-----
> From: Joe Taylor <> 
> Sent: March 4, 2018 23:44
> To: WSJT software development <>
> Subject: [wsjt-devel] Public test of FT8 DXpedition mode March 6-7
> Hi all,
> I write to remind you of the public test of *FT8 DXpedition Mode* scheduled
> for March 6-7.  The more participants, the better!
> The main goal is to simulate pileups in which many "Hounds" call and attempt
> to work a desirable rare DX station, the  "Fox", and to maximize the
> resulting QSO rate.  We hope you can be there and work each of our Foxes on
> each band.
> All participating stations must use program version WSJT-X v1.9.0-rc2. 
> If you don't yet have it, download links are available here:
> Detailed instructions for Fox and Hound stations are posted here:
> It's important to read and follow these instructions carefully!  Don't just
> try to wing it.
> Each hour during the test has a designated frequency and Fox callsign,
> "Fox_A" in the following table.
> Date   UTC    Freq  Fox_A    Fox_B   NSlots
> -------------------------------------------
> Mar 6 2300  14.080  K1JT     W7/KH7Z    3
> Mar 7 0000  10.141  W1/KH7Z  K9AN       5
> Mar 7 0100   7.080  W7/KH7Z  K1JT       4
> Mar 7 0200   3.585  K9AN     W1/KH7Z    3
> As you will know after reading the FT8 DXpedition Mode User Guide, Fox can
> conduct up to "NSlots" QSOs simultaneously.  W7/KH7Z will be operated by
> AA7A, and W1/KH7Z by N1DG.
> Fox_A will operate for the full hour if plenty of Hounds keep calling. 
> Fox_B is on standby reserve.  If the QSO rate for Fox_A approaches zero at
> the half-hour mark, Fox_A will stop transmitting and Fox_B will call CQ.
> If you (as a Hound) can legitimately use more than one callsign -- your
> spouse's call, club call, etc. -- please try to work each Fox multiple
> times.  No dupe QSOs with the same call and same band, though.
> Real-time liaison will be available via the "Ping Jockey Relief" chat page
> (PJB), .  Everyone should
> monitor this page for possible announcements of frequency changes or
> switch-overs from Fox_A to Fox_B.  To ensure that announcements from Fox
> stations are easily visible, Hounds should monitor PJB but not post messages
> there during the test.
> The deepest pileups will help us to tune the final-release software version
> for optimum performance on both Fox and Hound sides.  After the test, please
> post any comments you feel will be helpful to one of our two email forums,
> or .  You will
> need to be subscribed to the list in order to post there.
> We sincerely hope you can join us for this test, working each Fox on each
> band!
>     -- 73, Joe, K1JT (for the WSJT Development Group)
> ----------------------------------------------------------------------------
> --
> Check out the vibrant tech community on one of the world's most engaging
> tech sites,!
> _______________________________________________
> wsjt-devel mailing list
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites,!
> _______________________________________________
> wsjt-devel mailing list

Check out the vibrant tech community on one of the world's most
engaging tech sites,!
wsjt-devel mailing list

Reply via email to