WriteLog
[Top] [All Lists]

Re: [WriteLog] Fwd: Fwd: [cwops] Packet spots

To: Hal Kennedy <halken@comcast.net>, "writelog@contesting.com" <writelog@contesting.com>
Subject: Re: [WriteLog] Fwd: Fwd: [cwops] Packet spots
From: Randy Thompson <k5zd@outlook.com>
Date: Tue, 10 Nov 2020 16:06:24 +0000
List-post: <mailto:writelog@contesting.com>
In this regard, I have to congratulate Wayne W5XD and the WriteLog development 
team.  They seem to produce release after release that just work.  No 
contesting ending failures.  Compare that to some other logging software!

-----Original Message-----
From: WriteLog <writelog-bounces@contesting.com> On Behalf Of Hal Kennedy
Sent: Tuesday, November 10, 2020 9:58 AM
To: writelog@contesting.com
Subject: [WriteLog] Fwd: Fwd: [cwops] Packet spots

Agree with Randy and others.  I ran the largest system engineering department 
in the US.  Maybe the world.  One of the top five rules:  NEVER intentionally 
introduce errors to "fix" something.  The rule of unintended consequences can 
be brutal.

73
Hal N4GG


Agree!  I want to control this myself rather than have the software do it.
If implemented, it should be an optional setting.


K5ZD

-----Original Message-----
From: WriteLog <writelog-bounces@contesting.com> On Behalf Of Kevin Rowett
Sent: Monday, November 9, 2020 11:17 PM
To: Alan Maenchen <ad6e@arrl.net>
Cc: WriteLog Reflector <writelog@contesting.com>
Subject: Re: [WriteLog] Fwd: [cwops] Packet spots

yes!  I find XIT, or slight adjustment of the big knob to help tremendously in 
getting to the top (bottom?) of a pileup, in a contest.

But, I’d NOT like the SW to do that for me.

In fact, we had a bit of discussion about that on the internal K4 eng list.  
Someone was advocating the K4 do that, as part of the radio.
Nooooooo.

73, K6TD


> On Nov 9, 2020, at 8:11 PM, Alan Maenchen <ad6e@arrl.net> wrote:
>
> I posted the note below on the CWops reflector about XIT offset for 
> the "click n shoot" crowd.
> N4ZR then said that N1MM has such a feature built in (option). I'm not 
> pushing for it, but wondering if WL does something similar. I haven't 
> looked for it but then there's a lot that I don't know. Just curious.
>
> Personally, I think part of effective operating in a pileup situation 
> is choosing your TX frequency such that you stand out in a crowd.
> That's something you learn. Personally, I move the main VFO manually 
> to offset myself from others rather than use the XIT knob. But, that 
> knob is there and having some automatic offset might be a good 
> thing... only for jumping on a packet spot.
>
> 73, Alan  AD6E / KH6TU
>
>
>
> ---------- Forwarded message ---------
> From: Pete Smith <n4zr@comcast.net>
> Date: Mon, Nov 9, 2020 at 5:27 PM
> Subject: Re: [cwops] Packet spots
> To: <main@cwops.groups.io>
>
>
> Many N1MM+ users are aware of this, but there is an option in the 
> Telnet window to automatically offset your transmission from the spot 
> frequency by a random small amount - should help.
>
> 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/9/2020 5:59 PM, Alan AD6E wrote:
>
> Need to get this off my chest - I apologize in advance for this complaint.
> It was a great SS but ...
>
> I love getting spotted and the resulting pileup. BUT there is a 
> serious problem with the "click and shoot" crowd where they don't 
> think about what it's like on the other end. Even a small pile of two 
> or three on exactly the same frequency is near impossible to copy 
> anyone. Signal strength alone is sometimes good enough to copy the 
> loud one, but usually they stack up at close enough strength that it's 
> impossible to copy. Yes, I do ride the RF gain control when I can and 
> that helps but my hearing isn't what it used to be.
>
> PLEASE!  Set your XIT to some random offset .. plus or minus. The easy 
> copy signals are the ones as far from the crowd as possible and still 
> within my bandwidth (400-500 Hz).  Unfortunately, not many of those. I 
> know some like to use really narrow filters so deciding what offset to 
> use is a crap shoot.  See what works. An offset of zero does NOT work.
>
> That said, I caught myself a few times zero beating. Some 
> self-flagellation is in order.
>
> Aloha, Alan  AD6E / KH6TU
>
>
>
>
> _._,_._,_
> ------------------------------
> Groups.io Links:
>
> You receive all messages sent to this group.
>
> View/Reply Online (#41943)
> <https://cwops.groups.io/g/main/message/41943> | Reply To Sender 
> <n4zr@comcast.net?subject=Private:%20Re:%20Re%3A%20%5Bcwops%5D%20Packe
> t%20spots>
> | Reply To Group
> <main@cwops.groups.io?subject=Re:%20Re%3A%20%5Bcwops%5D%20Packet%20spo
> ts>
> | Mute
> This Topic <https://groups.io/mt/78148355/722609> | New Topic 
> <https://cwops.groups.io/g/main/post>
> Your Subscription <https://cwops.groups.io/g/main/editsub/722609> | 
> Contact Group Owner <main+owner@cwops.groups.io> | Unsubscribe 
> <https://cwops.groups.io/g/main/unsub> [ad6e@arrl.net] _._,_._,_ 
> _______________________________________________
> WriteLog mailing list
> WriteLog@contesting.com
> http://lists.contesting.com/mailman/listinfo/writelog
> WriteLog on the web:  http://www.writelog.com/

_______________________________________________
WriteLog mailing list
WriteLog@contesting.com
http://lists.contesting.com/mailman/listinfo/writelog
WriteLog on the web:  http://www.writelog.com/ 
_______________________________________________
WriteLog mailing list
WriteLog@contesting.com
http://lists.contesting.com/mailman/listinfo/writelog
WriteLog on the web:  http://www.writelog.com/ 
_______________________________________________
WriteLog mailing list
WriteLog@contesting.com
http://lists.contesting.com/mailman/listinfo/writelog
WriteLog on the web:  http://www.writelog.com/
_______________________________________________
WriteLog mailing list
WriteLog@contesting.com
http://lists.contesting.com/mailman/listinfo/writelog
WriteLog on the web:  http://www.writelog.com/
<Prev in Thread] Current Thread [Next in Thread>