¿ªÔÆÌåÓý

ctrl + shift + ? for shortcuts
© 2025 Groups.io
  1. QRPLabs
  2. Topics

Intermittent Dit on QMX

 

I built a QMX about 3 weeks ago. I had a short on the 5 volt PS board and had to wait for a replacement. QRP-Labs was very fast with a replacement. I just don¡¯t have the equipment to do surface mount repairs. With that problem repaired I have been using the QMX on FT8. Made a contact on my first CQ attempt with a good signal report from Canada.

I have been working on re-learning Morse Code. Using the QMX in Practice Mode and verifying what I send is displayed. I notice every few minutes of practice, the QMX will miss a Dit. I feel it on the paddle and paddle I am using I have also used on my QCX+ with no problems. I have set the keyer to 12 WPM. All other settings are factory and running version x.009. I know the software is still being updated with bug fixes and features.

Just wondering if anyone else has experienced this? Maybe the processor is busy for a split second.

I will probably switch the paddles back to the QCX+ and verify if I may have an intermittent cable/connection/paddle.
 

Albert, good on you for using the QRP Labs rigs for this. I suggested as much a couple of days ago in a LICW post where the OP was asking for ideas for a code oscillator. Why bother when you can build an entire rig for $55 and get a great practice oscillator in the bargain? I saw some weirdness early on with my QMX keyer, but not since, and I don't recall specifically what it was.

Regarding speed, though, I'd recommend trying to practice at 20 WPM. If you get good at 12, you will eventually hit the wall trying to get past it since slower speeds allow you to count dits and dahs, whereas 20WPM forces you to learn the rhythm of the characters, and eventually words. Just leave lots of spacing early on, and you'll start locking in the characters. It might seem impossible, but stepping from slower to faster speeds is actually far more difficult.
 

Farnsworth!

I'm in a Morse?class right now, and we're learning characters at 25 WPM timing, and 5 WPM spacing.? That timing is a little bewildering to me, because I learned code 30 years ago at 20 WPM timing / 5 WPM spacing for my Novice exam and was at 15 / 15 sending and receiving on-air at my best back then.? I'm a little limited now by having only straight keys (SKs) here, so my next buy/build project will likely be a paddle key. ?

But I'm trying!? Learning to send left-handed will be the hardest part for?me.

Occasionally I used to get compliments on my CW proficiency at 15 / 10, especially?when people learned I was?SK-ing it.? I think taking band in high school helped.

If you're truly desperate, you can get a code sender / reader and pick a Farnsworth?timing you like.? Eventually you'll pick up code well enough to read it in your head and send it with an SK. ?

Almost everybody can learn code and get proficient.? It's easier than most of us seem to think.? Even kids can learn it, once they know their alphabet well enough to read Dr. Seuss.? My oldest daughter could read that well before she was 3.

73
Jim N6OTQ


On Thu, Sep 14, 2023 at 7:02?AM K9NUD-Steve <k9nud@...> wrote:
Albert, good on you for using the QRP Labs rigs for this. I suggested as much a couple of days ago in a LICW post where the OP was asking for ideas for a code oscillator. Why bother when you can build an entire rig for $55 and get a great practice oscillator in the bargain? I saw some weirdness early on with my QMX keyer, but not since, and I don't recall specifically what it was.

Regarding speed, though, I'd recommend trying to practice at 20 WPM. If you get good at 12, you will eventually hit the wall trying to get past it since slower speeds allow you to count dits and dahs, whereas 20WPM forces you to learn the rhythm of the characters, and eventually words. Just leave lots of spacing early on, and you'll start locking in the characters. It might seem impossible, but stepping from slower to faster speeds is actually far more difficult.

 

Jim:

I'm trying to increase my CW speed, but I've fallen behind a little because of the T41 project. That said, using the Farnsworth method just proves that the way I learned Morse code for my Novice license back in 1953 was wrong! Counting dits and dahs will make any speed above 20wpm very difficult. Listening for patterns, or rhythms, is the way to go. I like the program by G4FON which has many options, including setting the Farnsworth spacing. W1AW uses Farnsworth for its practice sessions at speeds under 18wpm.

If you're trying to learn Morse, give the G4FON software a shot. It's free and quite good. Try starting at 25wpm with 10wpm spacing. Being able to copy 25wpm probably covers most CW operators.

Jack, W8TEE

On Thursday, September 14, 2023 at 09:52:15 AM EDT, Jim Strohm <jim.strohm@...> wrote:


Farnsworth!

I'm in a Morse?class right now, and we're learning characters at 25 WPM timing, and 5 WPM spacing.? That timing is a little bewildering to me, because I learned code 30 years ago at 20 WPM timing / 5 WPM spacing for my Novice exam and was at 15 / 15 sending and receiving on-air at my best back then.? I'm a little limited now by having only straight keys (SKs) here, so my next buy/build project will likely be a paddle key. ?

But I'm trying!? Learning to send left-handed will be the hardest part for?me.

Occasionally I used to get compliments on my CW proficiency at 15 / 10, especially?when people learned I was?SK-ing it.? I think taking band in high school helped.

If you're truly desperate, you can get a code sender / reader and pick a Farnsworth?timing you like.? Eventually you'll pick up code well enough to read it in your head and send it with an SK. ?

Almost everybody can learn code and get proficient.? It's easier than most of us seem to think.? Even kids can learn it, once they know their alphabet well enough to read Dr. Seuss.? My oldest daughter could read that well before she was 3.

73
Jim N6OTQ


On Thu, Sep 14, 2023 at 7:02?AM K9NUD-Steve <k9nud@...> wrote:
Albert, good on you for using the QRP Labs rigs for this. I suggested as much a couple of days ago in a LICW post where the OP was asking for ideas for a code oscillator. Why bother when you can build an entire rig for $55 and get a great practice oscillator in the bargain? I saw some weirdness early on with my QMX keyer, but not since, and I don't recall specifically what it was.

Regarding speed, though, I'd recommend trying to practice at 20 WPM. If you get good at 12, you will eventually hit the wall trying to get past it since slower speeds allow you to count dits and dahs, whereas 20WPM forces you to learn the rhythm of the characters, and eventually words. Just leave lots of spacing early on, and you'll start locking in the characters. It might seem impossible, but stepping from slower to faster speeds is actually far more difficult.

 

Not sure if it is related but there is a lag on sidetone implementation with keying in iambic mode much above 16wpm which causes errant keying. Hans is aware of that issue. Not saying it is the same just raising the possibility.

Cheers

Daimon. G4USI
 

Thank you for all your replies. After checking with my QCX+ I have the same issue.

In checking the MFJ-564B manual, I had not adjusted the mechanical settings correctly. I adjusted the contacts gap to make it feel good, not the rear set screws. This meant the contacts were not squarely touching, but touching. (Didn't think it would make a difference, touching is touching) After adjusting the paddles per the manual, the problem has gone away.

Steve, I will take your suggestion about a higher WPM setting. When I learned code as a novice, I learned Dot and Dash not the sound. As a novice, I only got up to about 12 WPM or so. During that time, life changed and I stepped away from ham radio for about 30 years. I still have my HW-8 I built.

I sure don't remember code being so hard to learn back then.

Thanks again all!
KE0PRX

1 - 6 of 6