-
Notifications
You must be signed in to change notification settings - Fork 59
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Poor CW sending from key - nearly unusable #27
Comments
I can confirm that issue. Keying from iambic paddle tested > several elements missed / cut by internal interruption (audible snapping can be heard during the keying) The minimum CW timeout available setting (50ms > not 5ms) slightly helped and managed few QSOs but it is almost useless. Fix is needed. |
Latest release a little better but still not right, but no issues with a straight key - implying the paddle keyer code? |
Same here... not useable at present. Need to use straight key. |
You could also try to use iambic paddle connected through external elbug if you have one. |
Can you try the new keyer implemented in may 4th update? Read the instructions on sbitx.net |
Ok, will text when possible. Thanks for your work👍Martin W Smith M0MWSOn 6 May 2023, at 01:32, Ashhar Farhan ***@***.***> wrote:
Can you try the new keyer implemented in may 4th update? Read the instructions on sbitx.net
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: ***@***.***>
|
Minor hamlib additions
Very poor CW sending from a key. I am not sure if the code is just missing dits and dahs or if it is because of a small delay in the sidetone that is causing me to miskey. By dialling down the CW timeout (QSK delay???) from 1000mS to 5mS, things improve slightly but my sending still sounds awful with missing characters. This is a major issue - CW is my only mode and I want the pleasure of sending with a key not a keyboard or macros, which actually appear to work properly. Plesae can we get this sorted or my radio becomes useless. Thanks.
The text was updated successfully, but these errors were encountered: