Could this be as simple as debouncing the keying circuit? I have a 0.1 uf disc ceramic across the output of my J-36 paddles to prevent this.
Lee KX4TT
toggle quoted message
Show quoted text
On Tuesday, April 1, 2025 at 11:00:00 AM EDT, Gerald via groups.io <hb9cey@...> wrote:
The new firmware v1.05 / v3.051 is slightly better than before, but since CW still doesn't work properly for me even with the new firmware, I compared it with the QCX-Mini. Both transceivers were keyed and monitored in parallel, at the same speed, using a paddle. I also tried unsuccessfully with another paddle.
?
While the QCX-Mini didn't lose any characters, the zBITX repeatedly produced errors, dots and dashes were lost or appended. This happened at slow and also faster speeds. This reminds me of my simple diy touch paddle where I always had to wet my fingers otherwise exactly such errors occurred.
?
It seems strange to me that everything works fine for other users.
?
If I use a macro from the zBITX to transmit, the zBITX keys everything flawlessly up to 50 wpm. No lost dots or dashes. How can this be, and where is the difference between keying by macro and the paddle input? I'm neither an IT nor an electronics engineer, but I would first look for the problem with the key input. Perhaps someone can explain this to me.
?
73, Gerald