[WT-support] WT + Microham +WinKey

[G3SJJ]

Olivier, thanks for looking at this. Here is what I have just done :

- Expand mH Router, select Win-Test Preset
- Speed range set at 15-40, speed indicated is 27wpm with pot set at 12 
o'clock position
- Minimise Router
- Open WT at AFS log
- Bottom line of rate window says CW 28/39wpm.
- F1 message sent at the lower speed, so must be 28wpm
- Paddle sending at same speed !!
- Send a couple of CQs then send on paddle whose speed is NOW the HIGHER one
- Rate window still indicates 28/39
- Press ALT F10, left number now says 30 and F key speed has increased.
- Paddle speed now at same speed, so it has reduced from 39 to 30
- Turn speed control knob back until indicated speed is 30, knob now at 
10 o'clock position
- Press Alt F10 to increase F key speed to 39 and paddle speed also went 
to same speed but indicated 31

- Pressed F1, and no message sent !!!!
Sent something on paddle then pressed F1 and message sent. This is 
definitely repeatable

Will stop now as I am getting confused!!!!  73 Chris G3SJJ


Olivier Le Cam wrote:
> G3SJJ a écrit :
>> Just completed RSGB AFS Contest, 250 Qs over 4 hours, (which isn't 
>> bad for inter-UK!) and had some problems. I have raised this 
>> before.Win-Test is weird with WinKey/Microham.
>>
>> - The speed between external paddle and F Keys is all over the place. 
>> You choose independent speed pots and you can't change paddle speed, 
>> or speed control toggles between the two numbers in the rate window.
>
> Can you try to find a way to always repeat this behaviour?
>
>> - If you send anything on the paddle before hitting Ins/Fx etc, they 
>> don't work. For example, I recognise someone and send FB on the 
>> paddle, then hit Ins key. Nothing happens. So, send something again 
>> on the paddle and it unlocks Fn/Ins.
>
> I cannot repeat this here, but I have done various bugfixes on WinKey. 
> The next version would be available soon.
>
>> - This also show up using DVK. I have to hit Escape before sending an 
>> F Key message. This will cause me problems in next weekend's SSB leg.
>
> This would be fixed in next version.
>
> 73,