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 via wsjt-devel <wsjt-devel@lists.sourceforge.net> wrote:

    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 <fred.py...@gmail.com>
        To: WSJT software development
        <wsjt-devel@lists.sourceforge.net>, Joe
                Taylor <j...@princeton.edu>
        Subject: [wsjt-devel] 3Y0J strange F/H operation
        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

    _______________________________________________
    wsjt-devel mailing list
    wsjt-devel@lists.sourceforge.net
    https://lists.sourceforge.net/lists/listinfo/wsjt-devel



_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

--
Dave WB5NHL
8 band DXCC, 317 countries confirmed (Mixed , current)
Hamshack Hotline 5555
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Reply via email to