[RTTY] Suggestion for upcoming RTTY Roundup

[robert]

I did see that when I was using writelog and mmty programs, But never when
using rckrtty.
if a report is TOO it's converted to 599 and thes is as it should be.

I was in a qso with a station's in europe, but a station in USA came in and
was qsl'ing the report which I was getting,
it happened for about 20 minutes when the USA station got lost. I wonder if
he got all the point's hihi.
My report is "W7WHY 599 40 40 DE TF3TTY K"
It should not give any mistakes who is getting what.
73 de tf3tty
----- Original Message -----
From: "Tom Osborne" <w7why at verizon.net>
To: "RTTY" <rtty at contesting.com>
Sent: Saturday, December 31, 2005 8:55 PM
Subject: Re: [RTTY] Suggestion for upcoming RTTY Roundup


> Once you have unshifted, unless you send a figures shift character, you
will
> be getting the "too etu too etu" characters, then you have to look at the
> keyboard and figure what the heck number "etu" is or ask for a repeat.
This
> happens a lot in marginal conditions.  I like something to keep the
numbers,
> numbers till they are unshifted.  IMHO.  73
> Tom W7WHY
>
>
>
> > For slower paced contests that may be fine, but unless you send a new
> > shift
> > character before each character group, many of us will unshift.  If you
do
> > it properly by at least shifting (let alone unshifting each time) again,
> > it
> > takes 33 to 66 percent longer to send the same group of two characters
> > than
> > using dashes.  In addition, only 2 of 4 or 5 instead of 2 of 3
characters
> > hold the info you are after.  If copy is poor this can mean the
difference
> > between a QSL and an AGN AGN! Guess it depends on how smart your decoder
> > is
> > (both computer and human software) and whether you can type well which
way
> > works better.  My preference is for dashes...
> >
> > Ty K3MM
> >
> >
> > -----Original Message-----
> > From: rtty-bounces at contesting.com [mailto:rtty-bounces at contesting.com]
On
> > Behalf Of robert
> > Sent: Saturday, December 31, 2005 11:20 AM
> > To: RTTY at contesting.com; Shelby Summerville
> > Subject: Re: [RTTY] Suggestion for upcoming RTTY Roundup
> >
> > Hi
> >
> > I hope that everyone send a DE before there callsign and a 599 before
the
> > exchange.
> > All the programs I have seen needs those two worde so they know that a
> > callsign is comming and a exchange.
> > If this is not in there then I have to pt the callsign in the program
and
> > the exchange. It gave me a lot of trouble in pileups so I just ignore
> > those
> > who don't send it. at it's best it gives me a breake to get me a cup of
> > coffie and waitfor thse hams to move....
> >
> > guys please send DE before your callsign and 599 and the exchange.  i.e.
> > 599 14 14.. Don't send 599-14-14 thats just as bad as not sending 599..
> > regards guy's
> > see you tomorrow in sartg. Point your antennas to iceland.
> >
> > regards robert      TF3TTY
> >
> >
> > ----- Original Message -----
> > From: "Shelby Summerville" <k4ww at arrl.net>
> > To: "RTTY Reflector" <rtty at contesting.com>
> > Sent: Saturday, December 31, 2005 12:58 PM
> > Subject: [RTTY] Suggestion for upcoming RTTY Roundup
> >
> >
> >> Dick Thompson wrote: "I would like to put forth a suggestion to those
who
> >> are entering the ARRL RTTY Contest, especially the newer people.
> >>
> >> The report that you send is a signal report & State or Province or
> >> Country (S/P/C).  Please don't send 599 Mich if you are in Michigan.
> >> Send 599 MI.  There is no need to spell out your state/province.  Just
> >> use the standard 2 letter abbreviation.  I don't even know why a 599
> >> needs to be sent.  Everybody knows they will get a 599 even if they
have
> >> to repeat the exchange a dozen time.  Hi Hi.  It would be nice if the
> >> managers of a contest would do away with signal reports completely,
> >> since nobody ever gives anything other than 59(9).  Hi Hi.
> >>
> >> Good luck in the contest, guys.  Hope to see you there."
> >>
>
>> -------------------------------------------------------------------------
-
> > --
> >> ----------------------------------
> >>
> >> Dick, great suggestion, unfortunately you're "preaching to the choir"!
> > Most,
> >> if not all, subscribers to this reflector, are well acquainted with
RTTY
> >> contesting protocol? My suggestion, and I do this: keep a record,
during
> > the
> >> contest, of those that you may deem "not doing it correctly"! Post
> > contest,
> >> send those stations, a private email, gently advising them of the
> > "correct"
> >> way? Most, if not all, that you send an email, will welcome the advice,
> >> especially if it's written in a way, to encourage them, certainly not
> >> discourage them?
> >> I also keep a record of stations "never worked before on RTTY", and
send
> >> them a "welcome to RTTY contesting" email. Included in that email are
the
> >> URL's that will give them the necessary information, to continue to
> >> participate in future RTTY contests.
> >>
> >> Happy New Year to y'all
> >>
> >> C'Ya, Shelby - K4WW
> >>
> >> _______________________________________________
> >> RTTY mailing list
> >> RTTY at contesting.com
> >> http://lists.contesting.com/mailman/listinfo/rtty
> >
> > _______________________________________________
> > RTTY mailing list
> > RTTY at contesting.com
> > http://lists.contesting.com/mailman/listinfo/rtty
> >
> > _______________________________________________
> > RTTY mailing list
> > RTTY at contesting.com
> > http://lists.contesting.com/mailman/listinfo/rtty
> >
>
> _______________________________________________
> RTTY mailing list
> RTTY at contesting.com
> http://lists.contesting.com/mailman/listinfo/rtty