RTTY
[Top] [All Lists]

Re: [RTTY] (no subject)

To: "Dick Flanagan" <dick@k7vc.com>, "Jeff Blaine" <keepwalking188@yahoo.com>, "RTTY Reflector" <rtty@contesting.com>
Subject: Re: [RTTY] (no subject)
From: "Jim W7RY" <jimw7ry@gmail.com>
Reply-to: Jim W7RY <jimw7ry@gmail.com>
Date: Mon, 16 Jan 2012 17:42:32 -0800
List-post: <rtty@contesting.com">mailto:rtty@contesting.com>
Agreed!
73
Jim W7RY


--------------------------------------------------
From: "Dick Flanagan" <dick@k7vc.com>
Sent: Monday, January 16, 2012 4:07 PM
To: "Jeff Blaine" <keepwalking188@yahoo.com>; "RTTY Reflector" 
<rtty@contesting.com>
Subject: Re: [RTTY] (no subject)

> Writelog scrolls down (not up) so you don't have to chase call signs.
> The call sign stays in one place until the window fills and starts to
> fill from the top again. It is too bad that N1MM doesn't have that 
> feature.
>
> Dick
>
> --
> Dick Flanagan K7VC
> dick@k7vc.com
>
>
> On 1/16/2012 3:41 PM, Jeff Blaine wrote:
>> Mike,
>>
>> I’m saying get rid of that last CR/LF.  A guy will be trying to get his 
>> mouse over your exchange and then that CR/LF will come along and bump 
>> everything up.  Not a help.  N1MM has a feature to kill off some of these 
>> CR/LF but I don’t think it will filter that case.
>>
>> 73/jeff/ac0c
>> www.ac0c.com
>> alpha-charlie-zero-charlie
>>
>>
>>
>> From: Mike
>> Sent: Monday, January 16, 2012 5:27 PM
>> To: Jeff Blaine
>> Cc: rtty@contesting.com ; k0rc@citlink.net
>> Subject: Re: [RTTY] (no subject)
>>
>> Your right Jeff.  There should be a space before the last "(CR/LF)". 
>> Just got lost in the e-mail line wrap-around.
>>
>>
>> On Mon, Jan 16, 2012 at 6:04 PM, Jeff Blaine<keepwalking188@yahoo.com> 
>> wrote:
>>
>>    Mike,
>>
>>    You may also want to drop that last CR/LF in favor of a space. 
>> Otherwise you make the guy on the other end chase you up the page 
>> unnecessarily.
>>
>>    73/jeff/ac0c
>>    www.ac0c.com
>>    alpha-charlie-zero-charlie
>>
>>
>>
>>    From: Mike
>>    Sent: Monday, January 16, 2012 4:59 PM
>>    To: rtty@contesting.com
>>    Cc: k0rc@citlink.net ; Jeff Blaine
>>    Subject: Re: [RTTY] (no subject)
>>
>>
>>    Regarding the sending of the call at the end of the exchange:
>>
>>      a.. If I am running I'll only send the call of the station I'm 
>> answering at the end of the exchange (the call is always sent at the 
>> beginning of the exchange) when: a. Several stations answered my CQ and 
>> are still calling when start sending my exchange, or; b. When I think I 
>> may have started sending the exchange when he may still be transmitting, 
>> or; c. At the end of the "K1XXX TU(CR/LF)Now K2XX 599 VA VA K2XX (CR/LF)" 
>> exchange.
>>
>>      b.. I don't send the other station's call, or my call, at the end of 
>> my S&P exchange.
>>
>>    Regarding "a." above, I sometimes still don't send the call at the end 
>> of the exchange if I know my signal is strong into his location or the 
>> other stations stop sending their calls about the same time the station I 
>> am answering did, or the other stations calling were not as loud as the 
>> station I answer.
>>
>>    You have to get a feel for when to send the call at the end of the 
>> exchange.  Suspect I send the other station's call at the end of the 
>> exchange about 50% of the time.
>>
>>
>>    On Mon, Jan 16, 2012 at 2:52 PM, Jeff Blaine<keepwalking188@yahoo.com> 
>> wrote:
>>
>>      Robert you are right.
>>
>>      The place to get the run station's call is off his CQ.  Not off the
>>      exchange.
>>
>>      73/jeff/ac0c
>>      www.ac0c.com
>>      alpha-charlie-zero-charlie
>>
>>
>>      -----Original Message-----
>>      From: Robert Chudek - K0RC
>>      Sent: Monday, January 16, 2012 1:26 PM
>>      To: rtty@contesting.com
>>      Subject: Re: [RTTY] (no subject)
>>
>>      "Think about it.
>>      I am doing S/P tuning across his frequency and I see:
>>      k1xx 599<exch>   <exch>   k1xx"
>>
>>      When I am in S&P and I come across this exchange, all I know is the
>>      station transmitting is not K1XX. The exchange is configured for the
>>      benefit of two stations trying to make a QSO as efficiently as 
>> possible.
>>      It is not configured to give a S&P station some advantage.
>>
>>      "Who is the calling station?"
>>      As a S&P station, you will just have to wait and see.
>>
>>      "Who is the station running the frequency?
>>      As a S&P station, you will just have to wait and see.
>>
>>      "So who should I call?"
>>      As a S&P station, you will just have to wait and see.
>>
>>      "Are you saying I should just send out my call without knowing who I 
>> am
>>      trying to contact."
>>      Absolutely NOT! You should never call blind! As a S&P station, you 
>> will just
>>      have to wait and see.
>>
>>      "How about this:
>>      k1xx 599<exch>   <exch>   k1xx de w6wrt"
>>      That's just a waste of the transmitting stations time (and the 
>> receiving
>>      station as well).
>>
>>      73 de Bob - KØRC in MN
>>
>>
>>      ------------------------------------------------------------------------
>>
>>      On 1/16/2012 12:57 PM, Richard Cariello wrote:
>>      >  Bob,
>>      >  That's what makes this a horse race. As the person who is running 
>> the
>>      >  frequency the more time he gets his call out the better will be 
>> his rate.
>>      >
>>      >  Think about it.
>>      >  I am doing S/P tuning across his frequency and I see:
>>      >  k1xx 599<exch>   <exch>   k1xx
>>      >
>>      >  Who is the calling station?
>>      >  Who is the station running the frequency?
>>      >  So who should I call?
>>      >  Are you saying I should just send out my call without knowing who 
>> I am
>>      >  trying to contact. I see this allot but that station never gets 
>> called
>>      >  because he has already been worked, just adding QRM to the 
>> frequency.
>>      >
>>      >  You come across this type of operation allot during SSB contests. 
>> The
>>      >  station will run signing as "QRZ". After a while I simply call 
>> the station
>>      >  as "QRZ" but at least the next time I tune across this station I 
>> can at
>>      >  least ID his voice.
>>      >
>>      >  How about this:
>>      >  k1xx 599<exch>   <exch>   k1xx de w6wrt
>>      >
>>      >  As the station doing S/P this would let me see who is running the
>>      >  frequency and give the station he is working the second chance to 
>> know it
>>      >  is his report. Now I will know as the S/P station if I need him 
>> or not.
>>      >
>>      >  Rich AA2MF
>>      >
>>      >
>>      >
>>      >
>>      >
>>      >
>>      >  On Jan 16, 2012, at 12:33 PM, Robert Chudek - K0RC wrote:
>>      >
>>      >>  He is not signing as the other station. The other station 
>> already knows
>>      >>  he is working W6WRT. It's a waste of time sending W6WRT again.
>>      >>
>>      >>  Bill also knows his call sign, so there's no benefit for him 
>> seeing it
>>      >>  again either.
>>      >>
>>      >>  There is a benefit. That is when the first K1XX gets covered up 
>> by "tail
>>      >>  enders" and "long callers". Nobody knows who the report is being 
>> sent to
>>      >>  (other than W6WRT). Having the call sign on the end ensures the 
>> intended
>>      >>  station knows he is being worked.
>>      >>
>>      >>  I lost count of the number of times I received "4:XC-ALU4C 599 
>> CA CA BK"
>>      >>  on my screen. Then I simply WAIT until the station resends his 
>> report
>>      >>  and I can tell whether he is working me or someone else.
>>      >>
>>      >>  73 de Bob - KØRC in MN
>>      >>
>> 
>>     >>  
>> ------------------------------------------------------------------------
>>      >>
>>      >>
>>      >>  On 1/16/2012 8:13 AM, Richard Cariello wrote:
>>      >>>  Bill W6WRT,
>>      >>>  I am just getting back into RTTY myself and greatly enjoying 
>> the mode.
>>      >>>
>>      >>>  I am wondering why you are signing as the other station:
>>      >>>
>>      >>>  ME:    K1XX 599<EXCH>    <EXCH>    K1XX
>>      >>>
>>      >>>  I would use:
>>      >>>
>>      >>>  ME:    k1xx 599<exch>    <exch>    w6wrt (your callsign)
>>      >>>
>>      >>>  If conditions are bad then double the callsigns as needed to 
>> make the
>>      >>>  QSO.
>>      >>>
>>      >>>  Rich AA2MF
>>      >>>
>>      >>>
>>      >>>  On Jan 16, 2012, at 7:39 AM, Duane Budd wrote:
>>      >>>
>>      >>>>  Bill said:
>>      >>>>
>>      >>>>  "When I'm running, I want to verify two things from the 
>> calling
>>      >>>>  station:
>>      >>>>
>>      >>>>  1. He's working me and not another station on the frequency 
>> that I
>>      >>>>  can't
>>      >>>>  hear.
>>      >>>>
>>      >>>>  and
>>      >>>>
>>      >>>>  2. That he has my callsign correct.
>>      >>>>
>>      >>>>  Unless the calling station sends my call at some point, how 
>> would I
>>      >>>>  verify
>>      >>>>  the above?
>>      >>>>
>>      >>>>  Here's how I like it when I'm running:
>>      >>>>
>>      >>>>  ME:    CQ TEST W6WRT W6WRT CQ
>>      >>>>  HIM:    K1XX K1XX K1XX (or only twice if condx good, never 
>> just once)
>>      >>>>  ME:    K1XX 599<EXCH>    <EXCH>    K1XX
>>      >>>>  HIM:    W6WRT 599<EXCH>    <EXCH>    K1XX
>>      >>>>  ME:    K1XX TU W6WRT CQ
>>      >>>>
>>      >>>>  There is some redundancy in the above, but during a busy 
>> contest when
>>      >>>>  often
>>      >>>>  there are several stations on the same frequency, some 
>> redundancy is a
>>      >>>>  necessity, IMO. Otherwise you are likely to log the wrong 
>> station.
>>      >>>>
>>      >>>>  73, Bill W6WRT"
>>      >>>>
>>      >>>>  And that is exactly the way I do it and for the same reasons.
>>      >>>>
>>      >>>>  While I am not a pro like AA5AU, I enjoy RTTY contesting and 
>> it has
>>      >>>>  become
>>      >>>>  my favorite operating joy...
>>      >>>>
>>      >>>>  Budd, W5BEN
>>      >>>>  dcbudd@embarqmail.com
>>      >>>>  Johnson City, TN
>>      >>>>
>>      >>>>
>>      >>>>
>>      >>>>  _______________________________________________
>>      >>>>  RTTY mailing list
>>      >>>>  RTTY@contesting.com
>>      >>>>  http://lists.contesting.com/mailman/listinfo/rtty
>>      >>>  _______________________________________________
>>      >>>  RTTY mailing list
>>      >>>  RTTY@contesting.com
>>      >>>  http://lists.contesting.com/mailman/listinfo/rtty
>>      >>>
>>      >>  _______________________________________________
>>      >>  RTTY mailing list
>>      >>  RTTY@contesting.com
>>      >>  http://lists.contesting.com/mailman/listinfo/rtty
>>      >
>>      _______________________________________________
>>      RTTY mailing list
>>      RTTY@contesting.com
>>      http://lists.contesting.com/mailman/listinfo/rtty
>>
>>      _______________________________________________
>>      RTTY mailing list
>>      RTTY@contesting.com
>>      http://lists.contesting.com/mailman/listinfo/rtty
>>
>>
>>
>>
>>    --
>>       73,
>>       Mike, K4GMH
>>
>>
>>
>>
>>
>>
> _______________________________________________
> RTTY mailing list
> RTTY@contesting.com
> http://lists.contesting.com/mailman/listinfo/rtty
> 
_______________________________________________
RTTY mailing list
RTTY@contesting.com
http://lists.contesting.com/mailman/listinfo/rtty

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