Closed n4af closed 2 years ago
A trace of uWinKey procedure wkAddCWMessageToInternalBuffer indicates it loads the winkey speed changes ok. The problem is either a timing problerm or WinKey cannot handle the more complex speed changes.
The proposed solution, integrated into 4.106.1, is to force code speed to the displayed code speed before invoking SendCrypticMessage in MainUnit.
To amplify on this, a more complex speed command to Wkey works ok, the problem is that ,over time, the ambient WKey speed can deviate from the displayed code speed.
TR4W will now, on each new WKbuffer force the starting CW speed to the displayed code speed.
one other note: Wkey does not do 'speed up/down' increments. TR4W does the calculation and sends the 'new' speeds to Wkey from procedure CheckSpeedChange;
Programming an Fkey for sending at speedup/speed down in a simple scenario works ok 'ctrl-p ctrl-f 5NN ctrl-p ctrl-s VA' gives a speed up of the RST, where the speedup can be repeated to increment the speed up.
However, a problem can slowly arrive with more complex speed up: [speed up 10wpm]'5NN'[speed down 16]'VA'[speed up 6] should/does send the RST faster and the QTH slower.
Unfortunately, over time, the sending speed can start to creep away from the displayed code speed- observed as slower.