I have hit the wrong macro key a number of time....actually many number
of times.
When I see a message like that; I just assume that the other stations
did that also.
I have a keyboard with big paddles keys on either end. All those paddle
type keys are assigned a macro.
Left side for 'Run', right side for S&P.
Nice bright characters on each paddle-key
I still hit the wrong one ....frequently!
On 2/14/12 10:12 AM, Alejandro V. XE1EE wrote:
> I don't know what some operarators think, but I have seen this many, many
> times.
>
> I'm calling CQ TEST and the normal answer is like:
>
> CQ TEST de XE1EE XE1EE
> DE XX1XXX
> I answer: XX1XX 599 001 001 TU
> .. that's the normal behavior, but often I see this:
>
> CQ TEST de XE1EE XE1EE
> de XX1XX 599 123 123 123 tu 73
>
> This guy is sending his report before I confirmed I have listened and sent
> my report. Have anyone experienced this?
>
> *********************
> XE1EE
> Alejandro Valdez O.
> DXCC RTTY, SSB& CW
> Mixed, 10, 15, 20& 40
> WAS, TPA& WAC
> www.dxxe.org
> www.qsl.net/xe1ee
> Twiter: @xe1ee
> ***********************
>
> +++++ No mas SPAM ++++++
> No me envíes cadenitas, oraciones y demás correos sin mi autorización.
> Do not send me prays, chain letters and others without my permission.
> ** No trees were killed in the sending of this message but a large number of
> electrons were terribly inconvenienced**
>
>
> --------------------------------------------------
> From: "Jim Hargrave"<w5ifp@gvtc.com>
> Sent: Tuesday, February 14, 2012 8:51 AM
> To: "Ron Kolarik"<rkolarik@neb.rr.com>; "RTTY"<rtty@contesting.com>
> Subject: Re: [RTTY] WPX funnies
>
>> Ron,
>>
>> This could be most any software and a product of a user defined Macro.
>>
>> As example, I use Logger32 with the MMTTY and MMVARI engines.
>> All the macros, up to 36 per mode for each engine, are user programmable.
>> I have a response macro for each contest.
>>
>> My WPX response macro is:
>> ---------------------
>> $transmit$
>> QSL $call$ 599 $serialnum$ $serialnum$ de $mycall$ TU
>> $receive$
>> $log$
>> ---------------------
>> As you will note this macros keys the transmitter, sends the response and
>> reverts back to receive. It also Logs the QSO.
>> I use this macro after I have already received an ack with the QSO
>> partner's
>> number.
>>
>> Now to address your question. If I get a request for NBR repeat, I use
>> this
>> Macro:
>> ------------------------
>> $transmit$
>> QSL $call$ $serialnum-1$ $serialnum-1$ de $mycall$ TU
>> $receive$
>> -------------------------
>> Note that this macro is in the same format and includes the QSO partner's
>> call, however since I have already logged the QSO the call has disappeared
>> and the serial number advanced. So the $call$ macro will be blank. IE:
>> "QSL
>> 100 100 de W5IFP TU" This should be sufficient because the QSO Partner
>> already knows who he/she is requesting a repeat from.
>> In this case I will only provide mycall at the end and the system will
>> subtract 1 from the last number logged ($serialnum-1$). I can repeat this
>> macro as many times as necessary. If necessary I can add the call back
>> into
>> the log entry field and it will then send his/her callsign again. I rarely
>> ever need to do this.
>>
>> My macro system is setup so I can work an entire contest with mouse clicks
>> and hardly ever touch the keyboard. I can optionally use the "F" keys as
>> each macro is assigned to a F, CTRL F, or ALT F hot key.
>>
>> Excuse the long winded explanation. Perhaps I got carried away and told
>> you
>> more than you wanted to know...(:->
>>
>> 73s de Jim
>> W5IFP
>>
>>
>> > -----Original Message-----
>> > From: rtty-bounces@contesting.com
>> [mailto:rtty-bounces@contesting.com]On
>> > Behalf Of Ron Kolarik
>> > Sent: Monday, February 13, 2012 10:41 PM
>> > To: RTTY
>> > Subject: [RTTY] WPX funnies
>> >
>> >
>> > Okay the usual lack of spaces, linefeeds, and your choice
>> > of hypen or space but this was a new one:
>> > YOUR CALL 599 001 001 KXXX
>> > On the repeat "YOUR CALL" was replaced with my call???
>> > I couldn't tell if the other side needed my call but sent
>> > his exchange anyway or if this was some sort of macro malfunction.
>> > Then it happened 2 or 3 more times so my vote is for the macro.
>> > Anyone know which software could have caused this?
>> >
>> > Ron
>> > K0IDT
>> > _______________________________________________
>> > 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
>
--
After I cook the vegetables, what do I do with the wheelchairs
---------------------------
Doing my best to annoy as many people as I can!
W9OL-Bill H. in Chicagoland
webcams at http://w9ol-towercam.webhop.org:8080
weather at http://hhweather.webhop.org:8080
_______________________________________________
RTTY mailing list
RTTY@contesting.com
http://lists.contesting.com/mailman/listinfo/rtty
|