RTTY
[Top] [All Lists]

Re: [RTTY] Really

To: k3mm@verizon.net
Subject: Re: [RTTY] Really
From: Claude Du Berger <duberger.miousse81@globetrotter.net>
Date: Sun, 31 Jan 2010 21:01:04 -0500
List-post: <rtty@contesting.com">mailto:rtty@contesting.com>
Ty, we all understand the why to use or not to use dashes between numbers
alfter all comments about it last week. This text was done for the new one on
RTTY, and I prefered to suggest a simple way to do it.

About the TU, in fact I now have remove the (hiscall) when saying TU when
in RUN. I now send simply TU de VE2FK CQ
I have already sent hiscall twice with the exchange.
Many PRO prefer sending the TU first specially to let the S&P station quit the
frequency rapidly to find another station.

Remember this list of info is not for the expert as you.
Your info on AFSK is correct.
Thanks

Claude Du Berger VE2FK
ve2fk@arrl.net

http://www.contestgroupduquebec.com/
http://sites.google.com/site/va2upcontesting/Home

  ----- Original Message ----- 
  From: k3mm@verizon.net 
  To: duberger.miousse81@globetrotter.net 
  Cc: rtty@contesting.com 
  Sent: Sunday, January 31, 2010 8:10 PM
  Subject: Re: Re: [RTTY] Really



  >> In ur #3, there is logic to support the use of dashes between the 
numbers...it usually eliminates a Figures shift character before each "001", so 
in theory it's quicker.  When using advanced front-ends such as RITTY, repeated 
character patterns are used to make an educated guess as to the correct number 
when errors are received and it doesnt matter whether you use dashes or 
space+Figures...it will figure it out, so shorter is better.  However, I've 
found that most operators do not have this kind of sophistication and have a 
hard time even translating "QWERTYUIOP" into "1234567890" when the Shift 
character is missed or garbled.  So I've pretty much given up on using the 
dashes and put up with the slower space+Figures sequence.

  3:  Use spaces to seperate your numbers, ex: 599 001 001
      There is no real reason to use hyphens. Do not use
      periods, commas, slant bars. In RTTY it is preferable
      to send the 3 digits, it's easier to click on 001 than 1.
      In normal conditions the exchange is sent twice but the
      RST only once. In poor conditions exchange may be sent
      3 times,  ex: 599 001 001 001 
      Do not add more spaces between words to make line longer.
     
  >>  In the following example, you want to confirm with "Hiscall" TU "Urcall" 
CQ or just "Hiscall" TU .   If you send TU first, whoever it is that thinks 
they worked you will be gone, so it's a waste of time to send their call at 
that point.

  7:  If you are in RUN-CQ mode, reply with (Hiscall) exch.(Hiscall)
      If there are many callers, QRM, it is important to confirm to 
      whom you have sent the exchange. ex: Hiscall 599 001 001 Hiscall
      Then, confirm with (TU Hiscall de URCALL CQ)   to continue.
   
  >> Wouldnt it be great if we could get everyone to follow # 8 part one??  



  8:  In S&P mode never send your exchange to the CQ'ing station
      until he has acknowledged your call and sent his exchange first!

  >> This next part is only correct if your call is not busted.  If he gets the 
call wrong, you have the option of just sending your call again if it's highly 
questionable, or sending your call again a couple of times and then the 
exchange if you are sure it was for you.  Then it is up to the RUN station to 
acknowledge your correct call before he moves on.  If he doesnt, you must call 
him again until he acknowledges your correct call.  Otherwise, you will lose 
not only that QSO but another 1 or 2 in points during log checking.

      Dont send hiscall but only yours,  ex: DE CALL CALL
      then reply with only your exchange, ex:  TU 599 002 002
      (TU say it all, QSL, TU, 73)  Again, the DE is optional.

  >> ...and wouldnt it be great if we could everyone to use the actual Mark 
frequency as the spot/pass frequency, rather than reading their LSB or USB dial?

  >>  ...and one more tip about running AFSK:  Please use only "high tones" and 
170hz shift.  The standard Mark tone is 2125 hz.  The center of your passband 
should be 2210 hz.  If you use low tones, you run the risk of transmitting 
audio harmonics since they will end up within your transmit passband.  Help 
keep the bands clean by keeping your tones high in the passband and watching 
your mic and ALC levels.  Also note that a lot of the radio-based FSK is 
actually AFSK in disguise, so it is not immune.  Sure, run AFC and NET while 
S&P, but tune for high tones so your tones will also be high on the return.

  73, Ty K3MM
  _______________________________________________
  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>