On Wed, Jan 11, 2012 at 8:48 AM, Jim Hargrave <w5ifp@gvtc.com> wrote:
> > What I did see was people not putting a space at the end of
> > your messages so someone would send CQ and I couldn't get their
> > callsign:
> >
> > CQ RU W1XYZRUVMXOONFEONB
>
> Hi Don,
>
> This has been one of my complaints for a long time. I have
> adopted a policy of not even responding to them.
> Some folks just don't get the message.
How do you expect someone to get a message if you don't send one??
If it bothers you that much, program a macro to send a quick hint "PSE
INCLUDE A SPACE BEFORE AND AFTER YOUR CALLSIGN" .. or make a note of
the call, and email them later ... but ignoring them doesn't seem
useful to anyone....
~iain / N6ML
> Same applies for name, QTH and Gridsquares. They
> all need spaces before/after. Completely negates auto capture.
>
> 73s de Jim
> W5IFP
>
>
> > -----Original Message-----
> > From: rtty-bounces@contesting.com [mailto:rtty-bounces@contesting.com]On
> > Behalf Of Don AA5AU
> > Sent: Wednesday, January 11, 2012 10:26 AM
> > To: RTTY Reflector
> > Subject: Re: [RTTY] Dropped last character in transmission during
> > RTTYRoundup
> >
> >
> > I didn't notice this at all, but there could be at least one
> > explanation for some of this.
> >
> > SO2R operators will purposely cut off their transmission in
> > order to transmit on the other radio. I do this constantly.
> > If you watch me CQ, you might find me dropping my signal at any
> > time during the message because I don't believe it making
> > anyone wait on the other radio for my report. Well, someone
> > always has to wait a second or two if there are QSOs occurring
> > on both radios at the same time, but I try to keep the delay at
> > a bare minimum. RTTY SO2R is at an all-time high right now.
> >
> >
> > What I did see was people not putting a space at the end of
> > your messages so someone would send CQ and I couldn't get their
> > callsign:
> >
> > CQ RU W1XYZRUVMXOONFEONB
> >
> > So I didn't know if it was W1XY or W1XYZ if they weren't in the
> > SCP file. Overall, I thought everyone was pretty good and the
> > quality of operators is at an all-time high. Probably saw a lot
> > of other stuff too but don't remember them.
> >
> > 73, Don AA5AU
> >
> >
> > >________________________________
> > > From: David Levine <david@levinecentral.com>
> > >To: RTTY Reflector <rtty@contesting.com>
> > >Sent: Wednesday, January 11, 2012 9:50 AM
> > >Subject: [RTTY] Dropped last character in transmission during
> > RTTY Roundup
> > >
> > >Didn't notice this mentioned this week, but in my few hours
> > operating the
> > >RTTY Roundup on Sat & Sun I noticed what seemed to be a few
> > operators that
> > >were plenty loud, but the last character of each line of their
> > macro they
> > >were sending was dropped. When I noticed it, I listened
> > (watched) a couple
> > >of exchanges and it was every single line that the operator
> > would send. I
> > >then noticed it a few more times with different operators over
> > the course
> > >of the weekend. It wasn't that their amp cut out so the last
> > character was
> > >sent "barefoot" but it just wasn't sending.
> > >
> > >With it being noticeable to me in the short time I operated, I was
> > >wondering if anyone else noticed? And was there some systemic
> > problem in a
> > >recently updated version of some popular logging program that
> > was causing
> > >it? I never noticed it before this weekend.
> > >
> > >73,
> > >K2DSL - David
> > >_______________________________________________
> > >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
|