[WT-support] K3 SSB mode change bug

[Bob Wilson, N6TV]

Good find.  It does make more sense to change band first, then change mode.

As long as you only use Win-Test to change bands, or only use the radio's
buttons to change bands, there should be no problem.

But if you try to use both methods, it does seem quite possible that you
could end up on the wrong sideband the next time that you use the radio
buttons.

I assume you were using the native support for K3 built-in to Win-Test, not
OmniRig, but using OmniRig you may also have the same problem.

Personally I prefer to use the Radio's buttons to change bands, since
typing in a band or frequency tends to disable RIT, and I like to keep RIT
ON.

Be sure to use CONFIG:BAND MAP to make the band buttons skip over the
non-contest bands.

73,
Bob, N6TV

On Tue, Oct 30, 2012 at 5:27 PM, Robert Chipperfield <robert at syxis.co.uk>wrote:

>  Hi all,
>
> Something I spotted at ZD9UW (but couldn't work out exactly what was going
> on), then managed to reproduce at M4A over the weekend...
>
> When using the K3 with WT in SSB, if I QSY by typing "20" or "40" etc, WT
> appears to send the "change mode" command *before* the "change band".
> This means you can end up on the wrong sideband:
>
>    - Start on 20m USB.
>    - Type "40" in WT.
>    - WT sends LSB to the K3 - which is still on 20m at this point, and
>    stores that mode with the band - then QSYs to 40m. So far, the operator is
>    unaware of a problem (now on 40m LSB).
>    - Type "20" in WT.
>    - WT sends USB to the K3, thus setting the mode for 40m to USB,
>    followed by the QSY to 20m... which is set to LSB from the previous QSY 20m
>    -> 40m.
>    - At this point, both bands are set to the wrong sideband...
>
> If you then click on a spot on the same band, for example, the problem
> goes away, since it resets both the mode and frequency.
>
> I've seen this with two different K3s, and two different installations of
> WT on different machines, so I don't think it's anything I'm doing!
>
> (By way of a fix, I think it's just the set mode / set frequency commands
> that need to be sent the other way around, so it QSYs before setting the
> mode...)
>
> 73,
> Rob, M0VFC
>
> _______________________________________________
> Support mailing list
> support at win-test.com
> http://lists.f5mzn.org/cgi-bin/mailman/listinfo/support
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.f5mzn.org/pipermail/support/attachments/20121030/f0ca616a/attachment.html>