[WT-support] More about $FREQnn

[Toni Lindén]

Hi!

I do use $FREQnn messages always, but there's some things I'd like to
be changed.

If doing SO2R, I normally try to find QSY frequency "on the fly". Now
if I have e.g. F7 message like "PSE QSY $FREQS" the QRG for $FREQS is
taken from the moment when I hit F7. In most of the cases I'm still
tuning the 2nd radio for finding the clear freq for QSY. So I'd like
it to go so that frequency of 2nd radio is read no earlier that when
$FREQS comes into sending turn. I don't know if I'd explain that
clearly, but I'll try to give an example.

Now it works like:
1) Hit F7
2) Read QRG from 2nd radio
3) Sends F7 message (NOW PSE QSY $FREQP)

How I'd like it to work:
1) Hit F7
2) Start sending F7 (NOW PSE QSY)
3) Read QRG from 2nd radio
4) Continue F7 message without delays with QRG ($FREQS)

I've tried also setting $FREQS in different message (e.g. MSG1) and
setting up messages like F7= NOW PSE QSY $MSG1 or with scenarios put
in scenario line F7=F7 $MSG1, but always the outcome is the same, the
QRG is read at the moment when I hit F7.


Also Bob's suggestion about having different resolution $FREQS message
is good. Maybe it could be set by operator in CW menu.
Option like QSY resolution:
- 1kHz
- 500Hz
- 100Hz
And WT would look the correct QRG for $FREQnn.

As an example now it works like:
QRG 14.023.96
$FREQnn sends 14023R9

How it should work with different resolutions:
QRG 14.023.74
- 1kHz $FREQnn sends 14024
- 500Hz $FREQnn sends 14023R5
- 100Hz $FREQnn sends 14023R7


73 de Toni, OH2UA


> Date: Mon, 13 Sep 2010 00:26:48 -0700
> From: "Bob Wilson, N6TV" <n6tv at arrl.net>
> Subject: Re: [WT-support] Feature Request for multi-ops: Send a "PSE
>        QSY" message to pass multipliers
> To: support at win-test.com
> Message-ID:
>        <AANLkTi=zR+dcfHQS2ispa1wzxx9OSpvBF_DoMez4EKHf at mail.gmail.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> On Sun, Sep 12, 2010 at 3:29 PM, Laurent HAAS - F6FVY <f6fvy at free.fr> wrote:
>
>> Check $FREQnn variables. That should already solve more or less what
>> you're looking for.
>>
>
> Thanks, I had completely overlooked these message variables, which were
> added in version 3.27 over a year ago.  I've just updated the Wiki
> page<http://docs.win-test.com/wiki/Message_variables#CW_.2F_RTTY_automation>because
> they were missing.
>
> Unfortunately, I think these variables may still be little used because they
> really do not send what a human operator would send.
>
> For example, if a networked radio is on 14021.99, and you hit a key
> programmed to send PSE QSY $FREQ20, the message comes out as "PSE QSY
> 14021R9" instead of just "PSE QSY 14022".
>
> Could you please change the message variable behavior so that they
> automatically round to the nearest *half kHz*, e.g. only send 14021,
> 14021R5, or 14022, and nothing in between?
>
> It's hard enough to get many rare DX stations to understand QSY requests as
> it is.  1/2 kHz should be close enough.  Only rarely would you need to be
> any more precise than that.
>
> 73,
> Bob, N6TV
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: http://www.f5mzn.org/pipermail/support/attachments/20100913/69aa26a8/attachment-0001.htm