CT-User
[Top] [All Lists]

[ct-user] CT9.84 CRTL F1/F2, MODE SELECT problem for VHF SS TST

To: <ct-user@contesting.com>
Subject: [ct-user] CT9.84 CRTL F1/F2, MODE SELECT problem for VHF SS TST
From: frankp at gcq.net (Frank Potts)
Date: Thu Jan 23 20:23:58 2003
Yes, this was exactly my point.

Frank Potts   NC1I

-----Original Message-----
From: Ed Parish K1EP <k1ep@arrl.net>
To: Bob Naumann - N5NJ <n5nj@gte.net>; CT-User@contesting.com
<CT-User@contesting.com>
To: <ct-user@contesting.com>
Date: Thursday, January 23, 2003 06:43
Subject: Re: [ct-user] CT9.84 CRTL F1/F2, MODE SELECT problem for VHF SS TST


>At 05:16 AM 1/23/03 -0600, Bob Naumann - N5NJ wrote:
>>>From the rules:  " Stations may be worked for credit only once per band
from
>>any given grid square, regardless of mode. "
>>
>>According to this, there's no reason to have mode at all in ARRL VHF
>>contests as part of the log - nevermind whether it's FM or SSB.
>>
>>I don't have any problem with logging FM, CW or SSB.  The point is that
it's
>>not required.
>
>It is not required by the rules but to be accurate I would like to know
what type of Q it is.  My reasons include, knowing what the distribution of
FM vs. SSB vs. CW Q's in the contest.  I think someone also pointed this
out.  It's nice to know that the extra effort to put up that FM antenna
yields you some points.  Or to make sure you check some of the lower
frequencies for CW.  Or to know that you could only complete the Q on CW as
the path margin didn't allow SSB.  Another reason is for accurate log
keeping and QSL'ing.  I would like to know the mode so that when I send a
card, it can reflect the proper mode.  The FCC doesn't require you to log
anymore, but I still log just about everything, especially transferring my
contest logs to my station log.  That requires emission type.
>
>
>
>>N5NJ
>>
>>----- Original Message -----
>>From: "R Johnson" <k1vu@tmlp.com>
>>To: <don@hfradio.com>; "Jim Reisert AD1C" <jjreisert@alum.mit.edu>;
>><CT-User@contesting.com>
>>Sent: Wednesday, January 22, 2003 7:29 PM
>>Subject: RE: [ct-user] CT9.84 CRTL F1/F2, MODE SELECT problem for VHF SS
TST
>>
>>
>>> Yes, Don your right after a fashion !!!  They are both Phone vs. CW !!!
>>>
>>> The ARRL VHF Contests broke the "Phone" category down into SSB and FM
>>Simplex
>>> in order to attract the some of the new "No-Code" licensees into VHF
>>CONTESTING.
>>>
>>> If you bring up anyone of the vhf contests you will see that the summary
>>window
>>> shows CW SSB FM as viable categories.
>>>
>>> Check it out.
>>>
>>> 73
>>> Bob, K1VU
>>>
>>>
>>> into  At 19:14 1/22/2003 , Don Melcher wrote:
>>> >Maybe I am missing something here - but isn't, for the purpose of a
>>contest,
>>> >FM & SSB considered the same "mode" - Phone (and digital RTTY)? What
mode
>>> >does CT THINK you're in when you select FM on the radio???
>>> >
>>> >Don Melcher
>>> >Owner - HF Radio On Board
>>> >www.hfradio.com
>>> >
>>> >-----Original Message-----
>>> >From: ct-user-bounces@contesting.com
>>> >[mailto:ct-user-bounces@contesting.com]On Behalf Of R Johnson
>>> >Sent: Wednesday, January 22, 2003 3:37 PM
>>> >To: Jim Reisert AD1C; CT-User@contesting.com
>>> >Subject: Re: [ct-user] CT9.84 CRTL F1/F2, MODE SELECT problem for VHF
SS
>>> >TST
>>> >
>>> >
>>> >Hi Jim: I tried CT 9.85.001. CRTL F1/F2 still broken. No FM.
>>> >
>>> >73 Bob, K1VU
>>> >
>>> > >
>>>
>>> _______________________________________________
>>> CT-User mailing list
>>> CT-User@contesting.com
>>> CT-User-request@contesting.com Subject=unsubscribe to unsubscribe
>>> http://lists.contesting.com/mailman/listinfo/ct-user
>>>
>>
>>_______________________________________________
>>CT-User mailing list
>>CT-User@contesting.com
>>CT-User-request@contesting.com Subject=unsubscribe to unsubscribe
>>http://lists.contesting.com/mailman/listinfo/ct-user
>
>
>_______________________________________________
>CT-User mailing list
>CT-User@contesting.com
>CT-User-request@contesting.com Subject=unsubscribe to unsubscribe
>http://lists.contesting.com/mailman/listinfo/ct-user

<Prev in Thread] Current Thread [Next in Thread>