understand the details of why it is
implemented this way. winkeyer doesn't. Which is correct? Who am I
to say? Understanding the root cause, now, I can modify the
pywinkeyerdaemon source to workaround this K3NG keyer bug. Better to
do that or to write a patch for K3NG or both? Workaroun
's problem should be fixed. Will
continue to follow up per his test report. I especially need to do
something about #2 above.
Besides +++ --- and a complete cwdaemon compatible prosign
implementation, I added tune capability as well to pywinkeyerdaemon,
so ALT-T works from tlf now. Looks li
setspeed first. (I didn't
> > find that function in the winkeyer interface.) In testing, I found
> > that tlf sends a setspeed command at startup, so no problems.
> >
> > https://github.com/drewarnett/pywinkeyerdaemon
> >
> > Best regards,
> >
> > Drew
> > n7da
> >
>
a setspeed first. (I didn't
find that function in the winkeyer interface.) In testing, I found
that tlf sends a setspeed command at startup, so no problems.
https://github.com/drewarnett/pywinkeyerdaemon
Best regards,
Drew
n7da
n the TODO list too long.)
+++TEST--- doesn't work unless there's a setspeed first. (I didn't
find that function in the winkeyer interface.) In testing, I found
that tlf sends a setspeed command at startup, so no problems.
https://github.com/drewarnett/pywinkeyerdaemon
Best regards,
Drew
n7da
