for Project:

Welcome to the Bug Tracking System for the Win-Test contest logger. Things to note :

Feel free to report any bugs, however minor. To improve efficiency, please try to be as accurate as possible.

Please don't ask for feature requests here but on the mailing list.

Thanks for your help. Olivier F5MZN and Laurent F6FVY

Task #326 — Elecraft K3 gets set to wrong sideband after Alt-F1 cycle through bands

Attached to Project— Win-Test
Opened by Robert A. Wilson (N6TV) - Friday, 2 Nov 2012, 9:17am
Bug Report
Current WT-4.x
0% complete

Reported by M0VFC with WT 4.9.1:

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:

  1. Start on 20m USB.
  2. Type "40" in WT.
  3. 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).
  4. Type "20" in WT.
  5. 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.
  6. 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...)

Note: Kenwood radios have requirement (?) to change mode before frequency. No such requirement in K3.

This task depends upon

This task blocks these from closing

Comments (0) | Attachments (0) | Related Tasks (0/0) | Notifications (3) | Reminders (0) | History |