I don¡¯t know the answer, but it would seem fairly simple to create a little timer inside the code that (once the key has been closed )?would keep it in transmit mode for a variable length of time, but transmitting only when the key closes again ,?somewhat like
semi break-in. ? Likely someone has already done that. ?
toggle quoted message
Show quoted text
Is anyone running a uBitx (with OEM version 5.1 firmware) on CW? I tried, but the initial element (dot or dash) is so badly truncated by the TR and mode-switching delays that it comes out as a shortened dot (or less). This was in hand-key mode,
using an external keyer for actual code generation. The effect is lessened at very slow speeds because the overall length of all of the elements is greater, but seems to preclude operation at even moderate speeds.
It's pretty disappointing to have a QRP rig that doesn't do CW. Is there a work-around? Is CW operation possible with other firmware (KD8CEC)?
Thanks,
Neil KX2Y
