[RTTY] [WriteLog] RTTY FKey Memory line for "W8XXX NOW W9AAA"

[Vilnis YL2KF]

Hi,

In N1MM using exactly the same idea as Don  do in WriteLog.
  <Autograb and pop>  or similar automation is source
for RX errors  due to missing space after call or qrm and so on.
   Run message :
F11 NEXT,{TX} QSL {LASTCALL} {ENTERLF} NOW {CALL}  {EXCH}  {MYCALL} {RX}

HNY & 73
de YL2KF
Vilnis

On 03.01.2015 02:46, Don Hill AA5AU wrote:
> I use WriteLog but I don't do this the traditional way of using a call stack and PUSH command or whatever it is. I tried it that way
> a couple times and it seemed awkward so I do it this way:
>
> I have only one extra message buffer and I call it my "NEXT" message and the message is programmed as follows:
>
> %R%P1 TU NOW %C 599 LA %E
>
> WriteLog users will be familiar with %R (sends CR/LF), %C is the callsign in the entry window and %E ends the message and drops the
> transmitter, so the key to this is %P1. %P1 is simply the last callsign logged.
>
> When I see two stations that I can work in succession, I decide which one I want to work first, let's say I see both P49X and K4GMH
> on my screen after a CQ. I decide to work P49X first because he's a new multiplier. So I put P49X in the call entry window and work
> him as I would any other station. As soon as I see P49X's report, I log the contact, then put the next station's callsign in the
> entry window (either by clicking on it or typing it in manually) and send him my "NEXT" message. If the other station is K4GMH, then
> it comes out as:
>
> P49X TU NOW K4GMH 599 LA
>
> Also notice that I only sent my State once in this report when I would normally send it twice. Hopefully K4GMH is paying attention
> and copied my state when I was working P49X. I suppose I could pluck K4GMH off a call stack and still use my NEXT message but I
> don't.
>
> I have been doing it this way since I first used WriteLog over 14 years ago. To me it's second nature and easier than messing with a
> call stack and using the PUSH command, or whatever it is.
>
> 73, Don AA5AU
>
> -----Original Message-----
> From: RTTY [mailto:rtty-bounces at contesting.com] On Behalf Of Ed Muns
> Sent: Friday, January 02, 2015 2:06 PM
> To: 'Dave Greig'
> Cc: 'RTTY Reflector'
> Subject: Re: [RTTY] [WriteLog] RTTY FKey Memory line for "W8XXX NOW W9AAA"
>
> I recommend subscribing to the NCJ if you enjoy radio sport.  Sent directly to you 6 times a year.
>
> To the point of the original post, an adequate response requires more than a simple reflector posting in order for someone to gain
> proficiency in what's behind the "W8XXX NOW W9AAA" transmission.
>
> Hence, reference to a two part column in the next two issues of the NCJ.
> The basics of call sign queuing are addressed along with specific details on how to implement it in WriteLog, N1MM Logger Plus and
> Win-Test.
>
> Ed W0YK
>
> ___________________________________________________________
>
> Dave N3BUO wrote:
>
> Thanks Ed, we will just run out and buy one at our local magazine store. Oh that's right no one carries this magazine any more at
> the news stands.
>
>
> On Fri, Jan 2, 2015 at 1:39 PM, Ed Muns <ed at w0yk.com> wrote:
>
>> Read the RTTY Contesting column in the Jan/Feb 2015 issue of the NCJ
>> and see if that answers your question(s).
>>
>> Ed W0YK
>>
>> __________________________________________________________
>>
>> Clay N9IO wrote:
>>
>> I have only seen a couple of RTTY ops while working a pileup transmit
>> "W8XXX NOW W9AAA" I have not figured out how to be that proficient
>> during an rtty run.
>>
>> Anyone care to share the "trick memory line code" what am I not getting?
>> Probably simple, right?
>> I use Writelog currently for rtty with my Flex6300.
>>
>> Thanks, looking for the fast track before RTTY RU.
>>
>> Clay Melhorn N9IO Bonfield, IL
>> Webmaster: KARS - Kankakee Area Radio Society - W9AZ
>> http://www.w9az.com/
>>
>> _______________________________________________
>> WriteLog mailing list
>> WriteLog at contesting.com
>> http://lists.contesting.com/mailman/listinfo/writelog
>> WriteLog on the web:  http://www.writelog.com/
>>
>> _______________________________________________
>> RTTY mailing list
>> RTTY at contesting.com
>> http://lists.contesting.com/mailman/listinfo/rtty
>>
> _______________________________________________
> RTTY mailing list
> RTTY at contesting.com
> http://lists.contesting.com/mailman/listinfo/rtty
>
> _______________________________________________
> RTTY mailing list
> RTTY at contesting.com
> http://lists.contesting.com/mailman/listinfo/rtty
> -----
> No virus found in this message.
> Checked by AVG - www.avg.com
> Version: 2015.0.5577 / Virus Database: 4257/8858 - Release Date: 01/02/15
>
> _______________________________________________
> RTTY mailing list
> RTTY at contesting.com
> http://lists.contesting.com/mailman/listinfo/rtty
>