[CQ-Contest] Precedence?

Jack Brindle jackbrindle at me.com
Fri Nov 8 19:08:36 EST 2019


Ah, my friend Ken. The fill request would be PREC?, while the actual fill is A.
Multiply that by the four different items that might need a fill (I sent all four fills last weekend at one time or another).
And, yes there is another key (commonly F2) that sends the entire exchange.

The most common request I made was for precedence, while on Sunday late with all the rapid QSB it became NR? For a three digit NR, it became common to hear the first two very well, and the third not at all.

Like you, I don’t like sending the whole thing again unless I really have to.

73 & hopefully see you at the NCCC meeting on Sunday!
Jack, W6FB


> On Nov 8, 2019, at 3:52 PM, Ken K6MR <k6mr at outlook.com> wrote:
> 
> “This means that we need eight keys (four for fill requests, the other four for the actually data”
>  
> OK, I’ll bite.  Why in the world do you need the same data twice?  Put the data in a key.  Once.  Your Exch key handles your normal exchange (all the data at once).  I’m not following.
>  
> “So, what I suspect what most folks do is to just send the whole thing whenever any fill request comes in.”
>  
> And thankfully, almost no one does this. And never do it yourself unless you get AGN?  It’s just wasted RF.
>  
>  
> Ken K6MR
>  
> From: Jack Brindle via CQ-Contest <mailto:cq-contest at contesting.com>
> Sent: Friday, November 8, 2019 13:50
> To: Contest <mailto:cq-contest at contesting.com>
> Subject: Re: [CQ-Contest] Precedence?
>  
> I think part of the problem is the number of F-Keys available for messages. Sweepstakes has four fields that may require fills (really five, but we usually have our callsign covered with a key already). This means that we need eight keys (four for fill requests, the other four for the actually data). Most loggers don’t really support this many keys, so we end up choosing what data we can assign to keys and hope for the best. With that in mind, many ops will simply append Prec to Nr and then send them together. Even still, that means six keys.
> 
> So, what I suspect what most folks do is to just send the whole thing whenever any fill request comes in. There is also the situation where we get tired and accidentally hit the wrong key. I found myself a time or two in CW SS accidentally hitting the CQ key (quickly followed by abort) when I really wanted to hit the NR key. I used SkookumLogger in Sweeps. I assigned the four fills to keys, then brought up the keyboard CW whenever I needed to request a fill. That also caused a few issues from forgetting to get out of keyboard mode, usually sending the received fill data at the end of my exchange. Yes, I did confuse a few folks. They were tired also…
> 
> So perhaps it might be a combination of them misunderstanding the request, hitting the wrong key, or not having all the fill data set up on their keyboard.
> 
> 73!
> Jack, W6FB
> 
> 
> > On Nov 8, 2019, at 12:39 PM, N4ZR <n4zr at comcast.net <mailto:n4zr at comcast.net>> wrote:
> > 
> > I think most folks use PREC? but if the guy on the other end says "?" I try "NR?" in hope that he will concatenate number and precedence, and if necessary, "AGN PSE". But I agree, not everyone gets it.
> > 
> > 73, Pete N4ZR
> > Check out the Reverse Beacon Network
> > at <http://reversebeacon.net <http://reversebeacon.net/>>, now
> > spotting RTTY activity worldwide.
> > For spots, please use your favorite
> > "retail" DX cluster.
> > 
> > On 11/8/2019 12:27 PM, john at kk9a.com <mailto:john at kk9a.com> wrote:
> >> 
> >> What it the best way to ask for a repeat of someone's precedence in SS CW? For me this is the most difficult part of the exchange to get sent again. Often I get the section is repeated instead and I have to ask again in a different way or sometimes the whole report is sent again which at least resolves the issue. In a few cases the calling station simply disappeared after my query and I had to wipe them from my log.
> >> 
> >> John W4AAA (KK9A,op)
> >> 
> >> 
> >> _______________________________________________
> >> CQ-Contest mailing list
> >> CQ-Contest at contesting.com <mailto:CQ-Contest at contesting.com>
> >> http://lists.contesting.com/mailman/listinfo/cq-contest <http://lists.contesting.com/mailman/listinfo/cq-contest>
> >> 
> > _______________________________________________
> > CQ-Contest mailing list
> > CQ-Contest at contesting.com <mailto:CQ-Contest at contesting.com>
> > http://lists.contesting.com/mailman/listinfo/cq-contest <http://lists.contesting.com/mailman/listinfo/cq-contest>
> 
> _______________________________________________
> CQ-Contest mailing list
> CQ-Contest at contesting.com <mailto:CQ-Contest at contesting.com>
> http://lists.contesting.com/mailman/listinfo/cq-contest <http://lists.contesting.com/mailman/listinfo/cq-contest>


More information about the CQ-Contest mailing list