VHFcontesting
[Top] [All Lists]

Re: [VHFcontesting] Ft8 qsy proposal

To: VHF Contesting Reflector <vhfcontesting@contesting.com>
Subject: Re: [VHFcontesting] Ft8 qsy proposal
From: Buck Calabro <kc2hiz@gmail.com>
Date: Wed, 20 Jul 2022 07:45:06 -0400
List-post: <mailto:vhfcontesting@contesting.com>
I'm not sure if Jim is looking for the convention that the Pack Rats
are proposing.
That's in the Nov 2021 Cheese Bits newsletter.

http://www.packratvhf.com/attachments/article/1012/Cheese%20Bits%20November%202021.pdf
73 de kc2hiz
  --buck

On Tue, 19 Jul 2022 at 22:06, Terry Price <terry@directivesystems.com> wrote:
>
> Yes, in the latest version of WSJT-X you can pre-configure a QSY message - 
> but no one uses it and how many folks really know the band to letter. The 
> WSJT folks should have taken that letter and through the GUI had it say, "QSY 
> TO 144 or 432 or whatever. There has always been an open form text in TX5. We 
> have used it to some success but giving the call and QSY frequency.
>
> Terry
>
> -----Original Message-----
> From: VHFcontesting 
> [mailto:vhfcontesting-bounces+terry=directivesystems.com@contesting.com] On 
> Behalf Of n2jmh@frontiernet.net
> Sent: Tuesday, July 19, 2022 9:09 PM
> To: VHF Contesting Reflector <vhfcontesting@contesting.com>
> Subject: [VHFcontesting] Ft8 qsy proposal
>
> Gang,
> Within the last year there was a proposal sent out for qsying on ft8 using 
> message 5. It was a basic plan but I didn’t save it. Thought for sure it was 
> going to be implemented into an update but I haven’t seen it.
> If anyone remembers the proposal can you point me in the direction? If I 
> remember right it used the abcd9e designations and I thought it included ph, 
> ft8 and cw. We are trying some experiments in The Rochester VHF Group to 
> increase activity, no other motives involved.
> 73 Jim n2jmh
_______________________________________________
VHFcontesting mailing list
VHFcontesting@contesting.com
http://lists.contesting.com/mailman/listinfo/vhfcontesting
<Prev in Thread] Current Thread [Next in Thread>