Keyboard Shortcuts
ctrl + shift + ? :
Show all keyboard shortcuts
ctrl + g :
Navigate to a group
ctrl + shift + f :
Find
ctrl + / :
Quick actions
esc to dismiss
Likes
Search
QMX CW issue, omits dits
Meanwhile having some QCX mini, now also own a QMX. Unfortunately I experienced a mysterious issue while keying CW that I don't know from the QCX. Every once in a while the QMX keyer omits a dit or a dah. At first I thought of a contact problem of my morse key (BaMaTech) but on my WinKeyer it worked flawlessly. I tried several speeds but even at low speeds this issue was present. After some futher experimenting with some alternative configurations and with other morse keys I think this is a problem of the QMX. I have firmware 1_00_027.
?
Any ideas?
?
73 de Michael, DF9TZ
? |
Michael,
I would echo Russ's concern about RFI. I believe I've seen this issue on this forum before. You might want to do a search for "RFI". Does this behaviour change with different antennas / dummy loads? You might want to explore ways to keep RFI out of the QMX: a choke, a better counterpoise, a different feedline, or a different antenna configuration altogether. GL es 73 de Todd W2TEF |
开云体育Michael,Just put a common mode choke 10 feet from your rig in the antenna coax line. ?I have had RFI cause all kinds of strange interference with my experimenting with all my QRP rigs. ?I have found that a CMC at 10 feet has “cured” many strange problems I have had in the past 10 years.? Dave K8WPE On Apr 14, 2025, at 7:59?AM, Michael via groups.io <michael.wohlfarth@...> wrote:
|
Thanks for the ideas so far.
?
As I am used to Iambic A I also choose this option on the QMX.
?
Incoming RF obviously is not the problem as this issue also occurs in practice mode. To be shure I tried a dummy and got the same result.
?
Could it be that the processor is not fast enough by handling the paddle input? I found that the QMX occasionally even does not send single dits as for an 'e' letter. In one case after sending some text with medium speed (20) the QMX hang by sending a continuous tone so I had to switch off power.
?
None of my QCX showed this behaviour at any time.
?
I am puzzled...
?
73 de Michael DF9TZ |
I have the exact same issue with the cw keying on my QMX+.? I have changed all the variable parameters for the CW keyer to no avail, as it misses dits. I have resorted to using an external K1EL USB keyer, which, of course, works fine with no missing dots.? The key jack is set up for straight keying when using an external keyer.? It would seem that the auto keyer emulation in my radio is the culprit. I have a 9V version and run it using an external INIU Power Bank with a 9V PD cable.? A voltage sag could cause the problem, but it has not bothered me enough to consider looking into the real issue.
73's Joe K8FC |
On Tue, Apr 15, 2025 at 06:12 AM, Michael wrote:
Could it be that the processor is not fast enough by handling the paddle input?Highly unlikely. I have heard many others report excellent keyer performance, even at higher rates.
And while I'm far from a CW expert, I have never noticed any malfunction of the keyer.
?
So I'm wondering if your particular QMX has some internal issue, like a flaky jack or one of the components.? The dit line in particular is also shared with the mic input, and has an extra capacitor and resistors and the bias voltage for the mic.? If any of these is malfunctioning or 'noisy', it could cause a keyer problem. |
Yes as Stan said. There aren't any known issues with the CW keyer. As far as I'm aware the behavior accurately mimics the original Kurtis keyer chip.? In the early days of QCX there were some problems but these were all resolved early on, in the second half of 2017.? QMX uses the same keyer code as QCX. But QMX suffered some keyer problems in its early months! The reason in the end, was found to be a race condition in the code. The same code in QCX was also flawed. But the ATmega328 code was never fast enough to win the race against itself. The STM32F446 on the other bands is so fast it races itself occasionally and that caused the glitch. It was a one line code fix but a devil to find that one line! But that was all over a year ago now.? 73 Hans G0UPL On Tue, Apr 15, 2025, 19:22 Stan Dye via <standye=[email protected]> wrote:
|
Michael,
?
I don't know if this is your issue, but if you have used any of the "Iambic A" keyers with anticipation, then you will lose dits/dahs, as the Iambic A mode in the QMX has no dit (or dah) pre-stored memory (except when you actually squeeze, that is).? Many keyers implement a logic whereby what they call the "Iambic A" mode does have a way to store an element while composing the inter-element space (i.e., while the inter-element space is being issued), so that you can release the dit/dah paddle while the space is being issued, and still get the extra element at the end. This capability is called 'anticipation" in some keyers, and is meant to make Iambic A "more responsive". It is a matter of milliseconds, but if your fingers are muscle-trained to do that routinely with a given keyer, you will notice the difference when you don't have anticipation.
?
I have tried and used many different keyers, and can confirm that the QMX keyer does not have any specific issue. It just implements a pure Iambic A keying, with no pre-stored elements and no anticipation. This can make the keyer feel "tardy" when one comes from a keyer with anticipation, and this is something I notice when I come back to the QMX after having used another keyer. I have used the QMX up to more than 50wpm, both in Iambic A and in Iambic B, and it does not miss a dit, unless I do make a genuine keying mistake. It certainly does not miss dits at 20wpm. Provided that you don't expect it to "pre-store" your dits before the full inter-element space has been issued.
?
I can confirm that RF in the shack can actually interfere with the QMX keyer, and that can be a source of all sorts of headaches. But RFin the shack also wrecked almost any other keyer I was using, before I solved the issue.
?
Hope this helps
?
72/73 de Enzo M0KTZ |
Thanks a lot for your ideas, thanks Hans for your explanaition.
?
Sometimes the easiest solution is the most likely. After some further experimenting I found that in fact it was a contact problem at the paddle jack. After fixing this, the keying now works as it should.
?
Problem solved :-)
?
73 de Michael DF9TZ
? |
to navigate to use esc to dismiss