Joe Taylor wrote:
Hi John,
On 3/16/2018 3:04 PM, John Becker K9MM wrote:
I updated my installation of WSJT-X from v1.8.0 to v1.9.0 rc2 earlier
today.
I encountered some problems while trying to work TY7C on 17M using
DXpedition mode.
I don't know how we could make this advice any more clear:
*To use FT8 DXpedition Mode you must read and follow instructions in the
FT8 DXpedition Mode User Guide.*
Here's the Guide. It's available directly from the Help menu.
http://physics.princeton.edu/pulsar/k1jt/FT8_DXpedition_Mode.pdf
My bad! I had previously printed out this document and skimmed through
it, but that was several weeks ago. I usually avoid using release
candidates at all, but I wanted to try out DXpedition mode, and I had
missed the public test last week. The TY7 operation is winding down, and
when I found them using DXpedition mode today with a decent signal on
17M I decided to see if I could work them.
The TY7C Dxpedition talks about their planned use of FT8 DXpedition mode
here:
https://ty2018dx.wordpress.com/2018/03/01/hot-news-ft8-in-dxpedition/
"TY7C will be active in FT8 in DXpedition mode.
It will be possible to small stations to works us in this mode.
Caution : WSJT-X version 1.9 rc or higher is mandatory, please see link.
You need to be configured as Hound , we will be Fox.
If you don’t use these settings (aka no DXpedtion mode), we won’t decode
you in the waterfall.
As requested by the software authors, we will NOT use the standard FT8
frequencies, we may be found about 4kHz below the official frequency..
see you in the pile-up."
2. At one point, my transmit frequency had jumped to his frequency.
See bottom pf page 1: "Hounds acknowledge having been called and
send their “R+rpt” message at a randomly selected frequency between 300
and 900 Hz. These frequency conventions are enforced and orchestrated
automatically by WSJT-X."
OK, but isn't it a problem if this "randomly selected frequency" puts
the hound's transmit frequency so close to the fox's that they are
overlapping? That's what happened.
Also see item #12 in *Detailed Instructions for Hounds*.
3. After he acknowledged my report with K9MM TY7C RRR, and the log QSO
pop-up appeared, I was unable to select the TY7C K9MM 73 message. He
kept sending K9MM TY7C RRR every couple of minutes, obviously waiting
for me to send TY7C K9MM 73, but I was never able to do so. I do not
appear in the online log, which has been updated since my attempted QSO.
FT8 DXpedition mode does not use "73" messages at all. See top of page
2 for examples of the standard exchange sequence.
OK, then if they were expecting a 73 from me, that is a problem with
*their* understanding of the correct use of DXpedition mode.
It would be nice to have a distinct FT8 DXpedition selection in the
Mode drop down menu, rather than having to go into the settings menu
to turn DXpedition mode on and off.
FT8 DXpedition Mode is not for casual use.
Of course, but if the station I am trying to work is using it, I have no
other choice.
-- 73, Joe, K1JT
------------------------------------------------------------------------------
I wouldn't have bothered to post my comments except for the fact that
the v1.9.0 rc2 release notes states "Please report any anomalous behavior".
Thanks for all you have done for the ham radio community with the WSJT
and WSJT-X software programs. The FT8 mode has triggered a revolutionary
shift in HF operation. Sorry if my comments were an annoyance.
73,
John, K9MM
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
