[WT-support] Macro $CORRECT

[Franta Bendl]

Hi Tonno, Iain, Marcelo,

you are right, using of F5 is also a way. An automatic solution would be nice, 
particularly because the half way is already done - the Macro $CORRECT called 
within INS-string notices correctly the change of the call. It needs merely 
to send the changed call instead of the old one.

73 de Franta/DJ0ZY



On Wednesday 03 June 2009 20:21:11 Tõnno Vähk wrote:
> It's a good idea Franta, I have been in situation many times and had to
> actually press ESC and send exchange again.
>
> But actually it is probably easiest to press F5 or wheverer $LOGGEDCALL is
> stored during exchange and it gets queued to the end of the exchange? That
> is almost automatical:)
>
> 73
> tonno
>
> -----Original Message-----
> From: support-bounces at win-test.com [mailto:support-bounces at win-test.com] On
> Behalf Of Franta Bendl Sent: Wednesday, June 03, 2009 9:15 PM
> To: support at win-test.com
> Subject: Re: [WT-support] Macro $CORRECT
>
> Hi Iain,
>
> yes I know the standard procedure - I made abt. 1500 QSOs last weekend ;-)
>
> I don't see a danger of misunderstanding:
>
> CQ DJ0ZY DJ0ZY TEST
> N6ML
> (typo: N6MK and I see (hear) it at the time of send and make correction to
> N6ML)
> N6MK 5NN 1234 N6ML
> 5NN 678
> TU DJ0ZY
>
> What do you mean could be the problem? I heard such corrections last
> weekend one or two times made manually and I found it as good idea. And I
> had never doubt to understand what the station mean. So I am looking for
> possibility how to realize it automatically with Wintest.
>
> My idea is to have $CORRECT in both "INS" and "+". So if I was enough fast
> the correction will be send after report and in the other case (I was too
> late) than it will be send before "TU" as usual.
>
> 73 de Franta/DJ0ZY
>
> On Wednesday 03 June 2009 19:21:12 Iain MacDonnell - N6ML wrote:
> > Franta Bendl wrote:
> > > I mean it's good idea to send the logged (correct) call again after
> > > sending of the RST and report in case it was corrected since then. It
> > > can save time spent by the other station repeating its call.
> > >
> > > E.g. DJ1ZY 599 123 DJ0ZY when I corrected the call during the sending
> > > of the RST and report. So I tried to set the INSERT string in "Standard
> > > CW messages" to
> > >
> > > $LOGGEDCALL $GUESSEXCH $F2 $CORRECT
> > >
> > > But it doesn't work properly. Wintest checks OK that the call was
> > > changed and sends it again but it doesn't send the new (corrected) call
> > > but the old one. Is it a bug as at this moment an other call is sent
> > > than the one in the call-field? Or is there any other solution for
> > > this?
> >
> > I think you may be misunderstanding how it works. The $CORRECT symbol
> > will send the call if it has been corrected since you sent the exchange.
> > If you include it in your exchange (INSERT) message, the other station
> > wouldn't have been able to correct your error yet! It's usually used in
> > the 'TU' (PLUS) message, to confirm the corrected call...
> >
> > CQ N6ML N6ML TEST
> > W1ABC
> > W1ABC 5NN 001
> > R 5NN 003
> > TU N6ML
> > K1XYZ
> > N1XYZ 5NN 002
> > K1XYZ K1XYZ 5NN 001
> > K1XYZ TU N6ML
> > ...
> >
> >
> > So your 'PLUS' message might look like:
> >
> > $CORRECT ++TU-- $MYCALL $CR
> >
> >
> > HTH,
> >
> >      ~Iain / N6ML
> >
> > _______________________________________________
> > Support mailing list
> > Support at win-test.com
> > http://www.f5mzn.org/cgi-bin/mailman/listinfo/support
>
> _______________________________________________
> Support mailing list
> Support at win-test.com
> http://www.f5mzn.org/cgi-bin/mailman/listinfo/support
> _______________________________________________
> Support mailing list
> Support at win-test.com
> http://www.f5mzn.org/cgi-bin/mailman/listinfo/support