[SD-User] missing first dot - and more
Paul O'Kane
pokane at ei5di.com
Mon Nov 30 01:05:28 PST 2009
----- Original Message -----
From: "summers brian" <summersb at telus.net>
> Rather than change any parameters I decided to re-install V14.26.
> First thing I noticed was that the missing first dot problem no
> longer existed.
All I can say is that I used SD 14.29, with WinKey, for some
250 QSOs and had no problems. With WinKey enabled, SD sends
ASCII text to WinKey, and WinKey converts the text to CW.
In this context, for SD to be responsible for a missing first
dot, the implication is that SD is sending the ASCII character
U instead of V to WinKey. That is unlikely.
So, there must be another explanation. That's why I suggested
increasing the PTT lead time as a possible way of preventing
the first dot being clipped. I use WinKeyer's PTT output, and
enable PTT (with PTTON) in SD. This eliminates the possibility
of clipped dots because it switches the rig to transmit mode
before keying starts - with a delay corresponding to the PTTLEAD
setting (in milliseconds).
> For every contact made (all 685) I sent 5nn. The .ALL file
> starts at 599 then shows lots of Q's at 559, 579, 549, and 569.
This is normally the result of using SD's RANDOM command, but
I've not seen it in other circumstances. Please send me your
SD.INI file and the .ALL and .AUD files from the contest.
I accept that the problems disappeared when V14.26 was reloaded.
Was it reloaded into a separate folder? If so, the SD.INI
parameters may well be different - and I would like to see both
files.
73,
Paul EI5DI
More information about the SD-User
mailing list