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 #370 — Secondary radio QSOs may be logged on wrong band after entering text commands there

Attached to Project— Win-Test
Opened by Robert A. Wilson (N6TV) - Monday, 22 Feb 2016, 4:29am
Bug Report
Secondary radio wnd
Current WT-4.x
0% complete

wt v4.20

  1. Set up for SO2R mode, Radio 1 and Radio 2 computer controlled, such as two Elecraft K3s
  2. Windows | Secondary Radio
  3. Radio 1 on 20m, Radio 2 on 15m
  4. Options | CapsLock Binds to the Secondary Radio
  5. Note correct band displayed in both primary and secondary radios
  6. Press CapsLock
  7. Type any text command or script shortcut in the secondary radio window, e.g., WORKDUPE, MOVEINMYLOGONLY, RUNSP, SPAN (calls my P3 script), etc.
  8. BUG: Band changes in Secondary radio window, on the logging line, to match the Primary radio band (?)
  9. Now, log a QSO on the secondary radio. It will be logged on the correct frequency, but wrong band.

Note: After typing the text command in the secondary radio window, if you move the Radio 2 VFO even a little, the band display will quickly correct itself. The bug only happens if you type a text command AND then log a QSO WITHOUT moving the VFO.

This task depends upon

This task blocks these from closing

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