Hi all,
During the operation, I contracted Steve Hauss, who is a Pilot for 3YOJ
concerning the issue. His response is below:
Hi Leslie, originally the group was having trouble adjusting their
fox/hound. Now they’ve got it working properly. So they would be TX even in
foxhound mode. If you are using.WSJT-X you don’t need to do anything other
than put the program into foxhound mode. That should work. 73, N2AJ
Les
W2LPL
Message: 1
Date: Wed, 15 Feb 2023 10:15:14 -0300
From: Fred Carvalho <fred.py2xb <fred.py...@gmail.com>
wsjt-devel@lists.sourceforge.net@gmail.com <fred.py...@gmail.com>>
To: WSJT software development <>, Joe
Taylor <j...@princeton.edu>
Subject: [wsjt-devel]
Message-ID:
<CALOHH3iY=amkusdqWvQ47P+ej5pgz=iro0npmjsguxuxx71...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
GM to all
*This concerns F/H operation in 3Y0J*
During the DXpedition the team announced multiple times that they were
using WSJT DXPedition Mode (F/H). However, FOX was most of the time in ODD
periods and accepted reports in any spot in the channel. QSY below 1000Hz
was not necessary. My QSOs with them were always like that. It took me some
time to understand how to work them, which I think was the same to most of
the callers. BTW, I have never seen FOX out of sync. The worst that I can
remember was 0.4s.
Many thought ? myself included- that they were not using WSJTx, but some
other multistream DXP mode application. However one of the operators
confirmed to me that they have used WSJT software.
After the expedition they have stated that : ? *We had issues with the FT8
due to we did not have any device to sync against, and our clock was 14
seconds off - which meant we at some time were TX odd, while we thought it
was even.*?
Well a simple GPS device connected to one of their notebooks would have
prevented the problem above.
So my questions to the developers are:
a) Is it really possible that lack of sync would lead them to TX in
ODD periods as FOX ?
b) How come QSY below 1000 HZ was not necessary for the Hound to
finalize the QSO with them?
This is very intriguing to many of us. Some clarification on what happened
is very much appreciated
Thanks Fred PY2XB
--
Fred - PY2XB
PY2FXH, PY2FXH/W2, PY2FXH/9, PY2XB/0, F/PY2XB, ZX2XB, PT7BXB, PY2XB/PY0F,
PQ0F <https://www.qrz.com/db/pq0f>, VP5/PY2XB, PW2IO
<https://www.qrz.com/db/pw2io>(SA-071), ZX8W
<https://www.qrz.com/db/zx8w> (SA-060),
PY2XB/1 (SA-029), 8P9XB <https://www.qrz.com/db/8p9xb>, PQ8XB
<http://www.qrz.com/db/pq8xb> (SA-045), ZX2S
<http://www.qrz.com/db/zx2s> (SA-028),
PR7XB W4/PY2XB, 3D2XB <http://www.qrz.com/db/3d2xb>, PY22XB
<http://www.qrz.com/db/py22xb>,PY0FX, W2/PY2XB, W9/PY2XB, VE3/PY2XB, PY2XB/5
*Team member** :* PW2M <https://www.qrz.com/db/pw2m> (SA-071), PX8J
<http://www.px8j.com/> (SA-041), T30PY - T30SIX <http://www.mdxc.org/t30py/>
, PT0S <http://www.pt0s.com/>, 9M0W <http://www.yt1ad.info/9m0w/>
-------------- next part --------------
An HTML attachment was scrubbed...
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
