[WT-support] Little help with LUA-stuff

[Bob Wilson, N6TV]

Laurent,

Thanks, this sounds like an excellent enhancement that will definitely
simplify things.  QRX for Version 3 of the PSE QSY scripts after some
testing.

Is there a wtKeyer:Play API that works the same way (synchronously)?
Ideally it wouldn't return until the message completed, or Escape halted the
CW.  It could then return "true" if the CW message completed, or "false" if
it was interrupted.

Why would I need this?  The $QSOB4 message variable is unusable in Advanced
SO2R mode today, because it can put both ears on the wrong radio (see Task
#205 <http://flyspray.win-test.com/index.php?do=details&id=205> opened over
two years ago and still not addressed).  There is also a similar Advanced
SO2R bug with the Escape key, which can also leave you listening to the
wrong radio (see Task
#289<http://flyspray.win-test.com/index.php?do=details&id=289>opened a
few days ago).  I wrote a simple script to work around the latter
problem, but it only works on CW.  I can't write my own #QSOB4 script to
work around the first problem until a synchronous playback API is provided.

Of course both bugs should be fixed in the Win-Test code, but since the
developers don't have any time to work on certain areas of the code these
days, I'm trying to figure out some way to get around these issues.

Finally, I see in the wt_dev Release.txt that you have also added the
wtStatus API to make it possible to automate PSE QSY messages at a multi-op:

- wtStatus:GetFreq(strBand[, strMode]) returns the "best" pass freq for a
given band and mode.

How is "best" defined?  Same search priority as $FREQnn (R, R+, M,  and
M+)?  If it always goes to the PASSFREQ, that is not what I would want it to
do.  Most often one would pass stations to the Run frequency of the Primary
Run radio on that band.  Also, I don't remember how to delete a PASSFREQ
once it gets set.  Typing PASSFREQ and deleting the frequency and press OK
doesn't seem to have any effect in manual mode (which is what you do when
you don't have an RS-232 line available to control a rig).

73,
Bob, N6TV

On Wed, Sep 15, 2010 at 2:40 AM, Laurent HAAS - F6FVY <f6fvy at free.fr> wrote:

> Hi Bob et al.
>
> Bob Wilson, N6TV a écrit :
>
> > Ok here is version 2 (attached).  You should be able to spin the
> > Secondary Radio dial while the PSE QSY is sending.
>
> (snip)
>
> > Unfortunately
> > the "?" can't be placed after the call to #FREQS(0) as Laurent already
> > mentioned.
>
> To make life easier, I modified the way the scripts are handled in the
> CW and RTTY messages. From rev. 412, they are now called *synchronously*
> by default.
>
> It means that if you have
>
> AAA #SCRIPT BBB
>
> the keyer now sends AAA, launches the script script.wts, idles and
> *waits* the script to be fully executed and returning, and once done,
> continues, and sends BBB. If for some reason, you want to revert to the
> previous behavior, you use the #@SCRIPT notation : In this later case,
> the script is called asynchronously (the keyer doesn't idle nor waits).
>
> I also introduced a new API wtKeyer:Insert(strMessage) to insert a
> string in the CW/RTTY message when used in the synchroneous mode. The
> string is inserted right in the place where the keyer idles.
>
> It means that PSE QSY-- #FREQS(x) ++ ? can now work easily.
>
> Note : ONLY textual data can be inserted : It is not parsed, and thus
> _no_ variable (or script call) can be used. The +/- speed bursts are
> allowed (in CW).
>
> Hope this helps.
>
> 73
>
> Larry - F6FVY
> _______________________________________________
> Support mailing list
> Support at win-test.com
> http://www.f5mzn.org/cgi-bin/mailman/listinfo/support
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.f5mzn.org/pipermail/support/attachments/20100915/9e488ebf/attachment.htm