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 w
On Tue, 14 Feb 2023 23:17:19 -0300
Marco Calistri via wsjt-devel wrote:
> Il 14/02/23 11:44, Brian Morrison via wsjt-devel ha scritto:
> > On Tue, 14 Feb 2023 08:39:54 -0300
> > Marco Calistri via wsjt-devel
> > wrote:
> >
> >> Hello,
> >>
> >> I'm using CQRLOG as the default QSO logging software
Hi Brian,
Yes, i know Saku, he helped me in many occasions.
Since this is not a blocking issue for me but just a random and not important
one, occuring only under particular usage of the FT8 QSO (trying to complete 2
QSO almost at the same time) I don't feel me comfortable to asking Saku to
re
Fred, there were many 3Y0J pirates on, maybe you worked one of them?
73, Palle, OZ1RH.
> Message: 1
> Date: Wed, 15 Feb 2023 10:15:14 -0300
> From: Fred Carvalho
> To: WSJT software development , Joe
> Taylor
> Subject: [wsjt-devel] 3Y0J strange F/H operation
> Message-ID:
> i
Lots of the people that got Clublog confirmations worked them in the Wrong
time Slot. So the issue was real.
Ron, WV4P
On Wed, Feb 15, 2023 at 9:42 AM Palle Preben-Hansen, OZ1RH via wsjt-devel <
wsjt-devel@lists.sourceforge.net> wrote:
> Fred, there were many 3Y0J pirates on, maybe you worked on
Hi Fred
The software "TimeFudge" by Mike W9MDB fixed such a problem.
This is time synchronisation to other stations (they have accurate time).
The DX expedition does not need GPS or the internet to do time
synchronisation.
73
Henryk SP3E
śr., 15 lut 2023 o 13:22 Fred Carvalho via wsjt-devel <
w
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 us
TimeFudge will not correct a 15-second error.
Their clock was apparently 15 seconds off and nobody had a GPS time sync (which
I find almost unbelievable).
Heck...my watch I've had for 50 years is more accurate than that and TimeFudge
would have fine-tuned it.
Mike W9MDB
On Wednesday, Fe
> nobody had a GPS time sync (which I find almost unbelievable).
Boggles the mind.
On Wed, Feb 15, 2023 at 10:20 AM Black Michael via wsjt-devel <
wsjt-devel@lists.sourceforge.net> wrote:
> TimeFudge will not correct a 15-second error.
>
> Their clock was apparently 15 seconds off and nobody had
Unlike WSJT-X, JTDX software allows F&H on either odd or even
On 2/15/2023 10:44 AM, Ron WV4P via wsjt-devel wrote:
Lots of the people that got Clublog confirmations worked them in the
Wrong time Slot. So the issue was real.
Ron, WV4P
On Wed, Feb 15, 2023 at 9:42 AM Palle Preben-Hansen, OZ1RH
On Wed, 15 Feb 2023 14:26:07 +
Marco Calistri via wsjt-devel wrote:
> Hi Brian,
>
> Yes, i know Saku, he helped me in many occasions.
>
> Since this is not a blocking issue for me but just a random and not
> important one, occuring only under particular usage of the FT8 QSO
> (trying to com
There is no question the Expedition messed up with F&H. Simple as that. Add it
to the list of lessons learned for subsequent expeditions.
Regards Dwayne AB6A
> On Feb 15, 2023, at 8:04 AM, David Kjellquist via wsjt-devel
> wrote:
>
> Unlike WSJT-X, JTDX software allows F&H on either odd or ev
Hi All
If a station that looks like F/H calls 15/45 it ain't no Fox/Hound
station. It's a MSHV Multislot/channel. Because a station is TXing on
more than one channel at the same time doesn't make it a Fox/Hound station.
73 de 5p1kzx Michael
Den 15-02-2023 kl. 17:04 skrev David Kjellquist via
I agree with you 100% but that does not take away the fact there was abundant
confusion for many ops. Just watching this play out, you would see almost the
same amount of ops transmitting odd as well as even attempting to respond.
In my humble opinion, they should have been using F&H and even.
> “ 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
I have read the answers. Thanks to all.
Commenting posts and/or answering questions: No I have not worked Pirate,
although I have seen them. I have always looked at antenna direction and
FOX behavior before calling. So my QSOs were confirmed correctly.
To 5p1kzx Michael: We all assumed that they w
Wed, 15 Feb 2023 11:04:03 -0500
David Kjellquist via wsjt-devel
kirjoitti:
> Unlike WSJT-X, JTDX software allows F&H on either odd or even
I gor answer from pilot Steve...
"Hi Jarmo,
Sorry I could not answer your email sooner. Too many emails and text
messages. They say they were using WSJT-X
Perhaps there "needs to be" some world wide FT8 beacon stations on 24/7,
where the beacons are known to have accurate time. WSJT-X, upon the
operator tuning to the beacon(s), can report a time difference error, or
perhaps even resync the local clock to the beacon in lieu of WWV's or
CHU's etc.
JT Sync will get you close: http://www.dxshell.com/jtsync.html
On Wed, Feb 15, 2023 at 12:38 PM Glenn Williams via wsjt-devel <
wsjt-devel@lists.sourceforge.net> wrote:
> Perhaps there "needs to be" some world wide FT8 beacon stations on 24/7,
> where the beacons are known to have accurate time.
Hi All,
I use Meinberg NTP with Windows 10. About two weeks ago with V2.6.1, I
do NOT remember if it was with 3Y0J, I found that my FT8 RX DECODE
matched the required time line position, about 13-14.9 seconds after the
beginning of the correct period (I believe it was EVEN). But at the
same
Hi Reino
+I think your answer is the closest to the target +
We agree that if the computer clock is close to 15seconds time
difference EVEN and ODD would be crossed. If that happened with 2 computers
and for 10+ days, it is explained, but it is a big coincidence. I would
expect a variable clock d
Yeah!
Undoubtedly he is one of (if not the the) most active contributor for the
CQRLOG development code.
On Wndows platform I use Log4Om, jointly with WSJT-X and I think that if CQRLOG
would have a Microsoft Windows version too, probably could get a more frequent
updates since I think there ar
They clearly did not realize they had a problem. Even without GPS, manually
setting the clock via WWV/CHU/JJY is more than sufficient. I am pretty sure
they brought HF receivers with them.
de KM1P Joe
___
wsjt-devel mailing list
wsjt-devel@lists.s
23 matches
Mail list logo
