There is a space at the end of that and all my messages. This is the first
I've heard of the zone not being copied.
73,
Ed W0YK
On Sep 27, 2016 07:21, John Barber <john@bordertech.co.uk> wrote:
>
> Agree .. the exchange needs to match conditions. Most of last weekend, the
> ideal report from the US was '599 state zone state zone ' when giving a
> report to a CQing station. It's vital to change the macro as signal levels
> change to get that balance between speed and avoiding repeats.
> My sent report when CQing was 'hiscall 599 14' but changed to 'hiscall 599
> 14 hiscall' when working a run of very weak JA stations. That maybe changed
> a 10% 1st time reply to 95% first time reply. It's not worth repeating 599
> 14 as they are known to all.
> When the report gets cut too short and too quick it can be really annoying.
> P49X was sending 'hiscall 599 09' with no space at the end or maybe cutting
> TX too quickly. 3 contacts and I didn't print the zone once! Sorry Ed.
> John GW4SKA
>
>
>
>
>
> -----Original Message-----
> From: RTTY [mailto:rtty-bounces@contesting.com] On Behalf Of Larry
> Sent: 27 September 2016 03:54
> To: rtty@contesting.com
> Subject: Re: [RTTY] Q Rate Killers
>
> NR4M's reply is the real answer I think. You need to be willing to adjust
> based on conditions and your station capabilities.
>
> I find that 'his_call rst exch state his_call' (for CQWW RTTY) can be
> helpful when running and a few stations are calling. The first 'his call'
> may get clobbered but the DX will usually hear the second and be certain
> your call is directed at him. If they need a repeat I may use F7 with the
> exch and state each sent twice. I use 'his_call TU my_call' for
> F3 which will hopefully finalize in the DX operator's mind what my call is.
> Don't forget that if you get spotted it often doesn't matter what you send
> for your call - "the cluster is always right"(?!) and so what is on the
> cluster is obviously your call.
>
> 73, Larry W6NWS
>
>
> On 9/26/2016 10:02 PM, Art (K5FNQ) wrote:
> > then what is the recommended minimum and maximum to send?
> >
> > N1MM default has "his call, sec, state, sec, state, mycall"
> >
> > At times with a strong station I would hit escape before "my call" was
> > sent. I had no problem with that.
> >
> > Cutting to "sec state sec state" scares me that the other station
> > might not have my call or I might have busted his?
> >
> > Art K5FNQ
> >
> >
> >
> > On 9/26/2016 20:56, Steve Bookout wrote:
> >>
> >> If you can be loud, then you can send less stuff. Unfortunately, not
> >> everyone can be loud all the time.
> >>
> >> I start with one of each exchange element and if it's noisy and I'm
> >> getting a bunch or requests for repeats, then I'll add additional
> >> exchange info.
> >>
> >> Steve
> >>
> >> On 9/26/2016 9:16:PM, Jeff AC0C wrote:
> >>> Tom,
> >>>
> >>> The exchange content for peak efficiency is just on the border where
> >>> you are infrequently asked for a fill. If you almost never get a
> >>> request, then I would say your content is too redundant. Keeping it
> >>> simple, on the next contest drop your exchange by one of each
> >>> element and see how it goes. In any event, do drop the "UR" out of
> >>> it in all cases.
> >>>
> >>> Have fun!
> >>>
> >>> 73/jeff/ac0c
> >>> www.ac0c.com
> >>> alpha-charlie-zero-charlie
> >>>
> >>> -----Original Message----- From: Tom Magarelli
> >>> Sent: Monday, September 26, 2016 7:37 PM
> >>> To: RTTY@contesting.com
> >>> Subject: Re: [RTTY] Q Rate Killers
> >>>
> >>>
> >>> I'm not sure if I'm one of the guilty parties
> >>>
> >>> My exchange was K4SBZ UR 599 NJ NJ NJ 05 05 05
> >>>
> >>> My thought was to send my state and zone 3 times, hopefully not
> >>> needing a repeat. That seemed to work I only had 1 station ask me
> >>> for a repeat of my State. My thinking was not having a lot of
> >>> repeats, I could make more contacts and move along quicker.
> >>>
> >>> Please tell me if my thinking is wrong. I'm not in the big league
> >>> either, just trying to have some fun.
> >>>
> >>>
> >>> -----Original Message-----
> >>> From: RTTY [mailto:rtty-bounces@contesting.com] On Behalf Of Stanley
> >>> Zawrotny
> >>> Sent: Monday, September 26, 2016 7:41 PM
> >>> To: RTTY@contesting.com
> >>> Subject: [RTTY] Q Rate Killers
> >>>
> >>> A while back, there was a discussion about how extra spaces and
> >>> characters
> >>> slow down an exchange. Those a nothing compared to the many ops that I
> >>> worked in the CQ WW DX RTTY Contest last weekend that took 15-20
> >>> seconds or
> >>> longer to reply. I'm not in the big leagues and worry about
> >>> milliseconds,
> >>> but when it takes almost a minute to complete a contact, that gets
> >>> to me.
> >>>
> >>> Stan, K4SBZ
> >>>
> >>> "Real radio bounces off the sky."
> >>> _______________________________________________
> >>> 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
>
> _______________________________________________
> 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
|