[RTTY] RU macros - my views
iw1ayd - Salvatore Irato
iw1ayd at gmail.com
Mon Jan 5 15:52:41 EST 2015
Right David,
it could be an operator error under N1MM Classic and N1MM+ with ESM
enabled ... but I am stuck one step before when S&P. In my DI windows
macros there is the one in the leftmost and highest rank that is MYC2.
It is the same text as the F4 when S&P > F4 SP Call,{TX}{ENTER} {MYCALL}
{MYCALL} {RX}{ENTERLF}. So it is {TX}{ENTER} {MYCALL} {MYCALL}
{RX}{ENTERLF}. I know myself and I know that following ESM I could make
it wrong. Sometimes I place the incoming caller callsign into to main
input window and this fire up the ESM. First step it go to F4, so Right
Mouse = Not Menu will fire
"
IW1AYD IW1AYD "
But often I would check for beaming or, more easy it it is really a
multiplier - I see a RED callsign, but when into the main input window
it become blue. So I have to decide/known if I could call him or I have
to go away.
At this time, here you right David if I understand what U wrote, ESM
isn't anymore aimed to give a call. ESM is aiming the answer to that
pounce-able station callsign. That's it. The Cursor in the main input
windows of N1MM moved from the end of the callsign into the first filed
to the last, usually, field for data input: the exchange.
It will fire
ZZ#WWW 599-070-070
That's the wrong macro. Well, as I also suffer from this syndrome as you
David I'd prepared the DI macros as I sad.
At this time, almost any time I am in S&P just to remember, I call him
with the DI macro MYC2. I don't use ESM ... or I have to get it back one
step and this action is unclear for me.
As I made this cure for myself I wasn't thinking to the step you wrote
about. So definetivelyl you right it could be a program behavior -
operator error more than a malicious spoiling habit.
Admittedly I have some of those program behavior - operator error that
I am unable to cure. When not focused I see that I make mistakes like
this. The easiest is - with all the cooperation from the N1MM ESM code -
I send back AGN AGN even if I have already placed the right exchange
well into the right field. I still have to discover why. Also even even
I am faulting or not. This doesn't usually happen when I am focused by
high rates. Well, I will find it ...
So I would leave my example but just with a 1% of probability for
spoilers on track - 99% of operation errors - mistakes - program
behavior ... sorry to have forced it too high before.
73 de iw1ayd Salvo
PS now I am pretty sure my cure for myself work HI! I have had also a
MYC3 nearby some time ago, but I removed it <:-)
On 05/01/2015 20:31, David Levine wrote:
> This particular exchange can happen by mistake (operator error) when
> using N1MM. I haven't used other contest programs to determine if it's
> possible that this error could occur in other programs.
>
> TEST IW1AYD IW1AYD CQ
> .....))) IW1AYD 599 070 070 XX#YYY (((....
> XX#YYY 599 102 102
> .....))) IW1AYD TU HNY DE XX#YYY QRZ (((...
>
> Not to say someone couldn't do it on purpose, but it's possible it's
> an accident. The same can occur, again because of operator error...
>
> TEST IW1AYD IW1AYD CQ
> .....))) XX#YYY XX#YYY(((....
> .....))) IW1AYD 599 070 070 XX#YYY (((....
> .....))) XX#YYY XX#YYY(((.... <----- Mistake when I should have
> sent the next line.
> XX#YYY 599 102 102
> .....))) IW1AYD TU HNY DE XX#YYY QRZ (((...
>
> I usually take the initial example above as operator error and not
> malicious behavior. I've made the mistake enough that to me it's an
> accident.
>
> K2DSL - David
>
>
>
> On Mon, Jan 5, 2015 at 2:16 PM, iw1ayd - Salvatore Irato
> <iw1ayd at gmail.com <mailto:iw1ayd at gmail.com>> wrote:
>
> HI Jeff,
> you wrote down somewhat I couldn't have written in my already log
> mail, well done.
> What I could say Jef. Us TAIL END CQ are here to suffer the same
> inflictions from very one other in the world ... :-)
> It's a pity that some times this is happening. I need a positive
> recognition of UR call.
> UR call is the one just at the left of CQ ... even if you forget
> the space after ...
>
> W7RN TU IW1AYD CQIUTYWWSOMENOISE
>
> I wouldn't not be a multiplier for anybody, I know, but it's
> clever to me - listen: the moon, the sun, the mom.
>
> This same kind of "theft attempt" could be seen here here, not so
> often, and it's coming from the nearby East usually.
>
> But often also who come with the call in and the exchange in the
> same first step make the wrong end.
> As they jump a step over and when I answer they have no more to
> say ... usually what they transmit is what I should have transmitted
>
> TEST IW1AYD IW1AYD CQ
> .....))) IW1AYD 599 070 070 XX#YYY (((....
> XX#YYY 599 102 102
> .....))) IW1AYD TU HNY DE XX#YYY QRZ (((...
>
> Unbelievable: him is stooling not my correnpondant but the QRG
> where I was CQing on.
> Usually I think him understand this his false step, but just to be
> sure better to fire quickly a:
>
> TEST IW1AYD IW1AYD CQ
>
> We had born to suffer ... <:-) ... not only our two Jeff. But also
> your KB# and my XX# are in tribulations, you know.
>
> 73 de iw1ayd Salvo
>
> On 05/01/2015 19:23, Jeff Stai wrote:
>
>
> On Mon, Jan 5, 2015 at 9:43 AM, David Levine
> <david at levinecentral.com <mailto:david at levinecentral.com>
> <mailto:david at levinecentral.com
> <mailto:david at levinecentral.com>>> wrote:
>
> So I (S&P'er) and they
> (RUN) stations need to wait or, as the contest runs on, I just
> send my call
> anyway.
>
>
> Well, OK, but as a religious applier of the CQ at the end, I'd
> really appreciate it if people would pay attention to it:
>
> ...
> P5ABC 599 NV NV
> W7RN 599 123 123 P5ABC
> P5ABC TU W7RN CQ
> P5ABC P5ABC DE KB0XXX KB0XXX KB0XXX!!!!!
>
> Exclamation marks added by me for emphasis. "KB0" prefix shown
> because of a particular KB0 exhibiting this behavior who would
> NOT stand by while I was trying to get a fill from a
> multiplier station who called me. Actually, that particular
> exchange was more like:
>
> ...
> P5ABC 599 NV NV
> W7RN 599 $^&*^(*&)
> P5ABC 599 NV NV
> P5ABC P5ABC DE KB0XXX KB0XXX KB0XXX!!!!!
> KB0 PSE STAND BY P5ABC 599 NV NV NR? NR?
> P5ABC P5ABC DE KB0XXX KB0XXX KB0XXX!!!!!
> ...and so on...
>
> Someone who threw tantrums to get his way as a child no doubt...
>
> No intention to cast aspersions on all of the honest law
> abiding KB0s out there, either. End of rant.
>
> 73 jeff wk6i
>
> --
> Jeff Stai ~ wk6i.jeff at gmail.com <mailto:wk6i.jeff at gmail.com>
> <mailto:wk6i.jeff at gmail.com <mailto:wk6i.jeff at gmail.com>>
> Twisted Oak Winery ~ http://www.twistedoak.com/
> Facebook ~ http://www.facebook.com/twistedoak
>
>
> _______________________________________________
> RTTY mailing list
> RTTY at contesting.com <mailto:RTTY at contesting.com>
> http://lists.contesting.com/mailman/listinfo/rtty
>
>
More information about the RTTY
mailing list