and what's to stop mshv from adapting the same call method?
73
Sam W2JDB
On Sunday, November 5, 2023 at 04:27:38 PM EST, Reino Talarmo via
wsjt-devel <[email protected]> wrote:
Just a minor point, I assume. If that is programmed into wsjt-x, then the
change will not be backwards compatible. The CQ part of the message is actually
a specific pretty long bit string (28 bits, ‘c28’). There could be another bit
string for the CQF, but none of the current versions would present it as the
CQF and the protocol machine would not work. If you feel a need to study it
further, see https://wsjt.sourceforge.io/FT4_FT8_QEX.pdf.
73, Reino OH3mA
From: Scott Armstrong via wsjt-devel [mailto:[email protected]]
Sent: Sunday, November 5, 2023 10:53 PM
To: WSJT software development <[email protected]>
Cc: Scott Armstrong <[email protected]>
Subject: Re: [wsjt-devel] CQ Hound mode
I believe he meant Fox.
CQF <call> <grid>
I like that idea. It would differentiate between F/H and MSHV. But this all
assumes the DX stops and calls CQ ever once in a while.
-Scott AA5AM
On Sun, Nov 5, 2023 at 2:38 PM Gary McDuffie via wsjt-devel
<[email protected]> wrote:
> On Nov 5, 2023, at 13:08, Pino Zollo via wsjt-devel
> <[email protected]> wrote:
>
> Just an idea:
>
> When in Hound mode the DX station should call as:
>
> CQH DX0CALL GRID
>
> or
>
> CH DX0CALL GRID
But why? He should only be hound if he is on his published frequency (which
you can determine yourself), and he should never be in hound mode if he is in
the normal FT frequency segment.
Gary - AG0N
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
