Вставка
- Опубліковано 17 жов 2024
- This video shows how I measured the morse code keyer speed in my Penntek TR-45L and Elecraft KX2 QRP rigs. The Reverse Beacon Network spots always seemed to indicate a WPM (word per minute) speed that was faster than the speed setting on these rigs - so I wanted to measure them to see which was right. The basic timing calculations can be found in this web resource:
morsecode.worl...
The RF Sampler that I used is similar to this:
www.rfparts.co...
Notes from this video can be found here:
www.qsl.net/w2a...
![Lp. Сердце Вселенной #30 ДВА В ОДНОМ [Один человек]• Майнкрафт](http://i.ytimg.com/vi/nrXy15orKhY/mqdefault.jpg)
I never thought of testing the actual speed. You did a very nice analysis and thank you.
Nice! Thanks for walking us through the theory & math as well as the links and notes!
Very interesting indeed. I really like the thinking behind your analysis of a problem or observation
I found this very interestind. I had never tought about it but it fun to know.
Interesting experiment Alan. I had never given this any thought. I find my ability to estimate WPM by ear has never been all that great. Fortunately my estimates by ear are usually slower than reality so I am delighted when I copy something thinking it’s X and it turns out to be X+!
Alan, Thanks for the interesting video topic.
In my POTA activations, I've found that the frequency I am using also comes into play as another dimension. I use the KX2 and the FT-891 the most during POTA activations and set the keyer speed to 24 wpm on both radios. When I activate POTA on the 40-meter band (affects both rigs) I perceive the Keyer to be slower than what I've set. However, when I QSY to 17 or 20 Meters the keyer speed becomes a little faster. I would say the difference in speed is about 1/2 wpm. This behavior is very consistent. Maybe there are some other factors at play here but I didn't look into it in any depth. I just adjust the keyer speed to compensate. I find the RBN consistently gives a faster WPM rate than from what I have set on the radios about 1 wpm faster. So if I set 24 wpm RBN reports me at 25wpm.
If time allows, you may want to redo the testing and use 40 and 17 and see if there are any differences you notice. As mentioned, I can hear a difference but I didn't do any actual measuring. 73, Jerry AC4BT
Interesting - I wouldn't expect the keyer speed to be dependent on the band being used. The 1 wpm difference between your setting and the RBN report is similar to what I observed on the KX2 in my testing. I never tested an FT-891 to see how its setting vs actual speed behaves.
I’ve noticed both my TR-35 and TR-45 are slightly faster than stated. I set it 1-2 WPM slower than I actually want. The IC-718 at my mom’s desk I did a test using the RBN because it sounded so slow. It was 2-3 WPM slower than you set it to. Very interesting. N7CCD
Interesting. I did learn that the RBN reported speed is pretty accurate. While the TR-45L and faster than it's set for, and the KX2 is also (but not at much), the FX-4CR was pretty spot on, as is my old Icom IC-703. I'm surprised that the IC-718 is slower than set.
Always great to see how something we simply take for granted can be a bit off! TNX Alan! 73 - Dino KLØS
...and it turns out that the RBN reading is *right*
I have noticed the same thing with most of my radios. They generally show slightly faster on the RBN than the key speed set on the radio. The exception to that is my FTDX10, which is usually one wpm lower on the RBN than I have the key speed set. I don't stress it too much. One or two WPM isn't a huge deal, but it's certainly interesting to see it tested and verified.
Hi Evan - It was an interesting experiment. The FX-4CR and my old Icom IC-703 are both spot on.
Does the KX2 have a weight adjustment in the menu system? I seem to remember seeing such a setting in the manual for the KX3 and the K3. You might be able to adjust the keyer speed.
Well done and well explained. 73 de AG7TX
I believe it does have the weighting control, but I think that will just adjust the relative dit/space/dah ratio. I had adjusted mine to be as close to the 1:1:3 as possible.
Maybe ask the reverse beacon folks what their algo is? Great vid as always. 👍
Hi Alan,
I like your methodology to determine the actual keying speed. 73 WJ3U
It also showed me that the RBN reported speed is pretty accurate.
You could have created a CW-memory in the KX2 with the word PARIS (up to 250 characters) and play that back. That would take out your "fist" all together.
Hi Alan, are going to contact wa3rnc to report this issue? They might correct this in firmware.
It may already be addressed - I have a pretty early unit so my firmware might not be the latest available.
RBN = Right Briskness Number
👍Thank you for the video.
Interesting... The mathematics and rational seem sound. The test seems more than adequate. Using the oscilloscope to measure and test is cool. But how would you calibrate either radio? 72 de W7UDT
Neither give you a means to adjust the displayed WPM vs. actual - so you're left with remembering how far off (percentage) your radio is, or simply adjust to a comfortable speed for you and ignore the numbers.
In the calculation for wpm with the word 'PARIS' there is a 3-unit trailing space included, whereas in your phrase 'CW' there isn't. That would be another source of error.
The calculation with the word 'PARIS' includes the standard 7-unit trailing space used between words (not 3-unit). This makes up the 50-unit length of the PARIS_ "word", and is what is used to derive the calculation of the unit length:
unit_length = (60 sec/min) / [50 *(x word/min)] = 1.2/WPM.
This calculation gives you the unit length for any WPM. Thus, when using my 'CW', all I need to do calculate the WPM for the 21-unit sequence of the 'CW' pattern. There is no need for a trailing space, and thus no source of error.
@@w2aew As soon as I wrote my message I thought, 'surely he would have thought of that', haha.. Wonderful. Great video as always! :-)
Gave me an Idea to use Arduino to generate Morse code and Detect Morse code.
For generating Morse code one would use keyboard and Arduino to look up the table and generates Morse code.
For the detector first we do envelop detection, then if the code was generated by machine we could use clock recovery PLL, but if it is generated by humans we detect the long time ( ie. _ ) and then divide them by two any signal that is shorter than this time is "." and any thing longer is "_" . Then based on this we could look up a table and print the character on LCD or send it though USB to computer.
It would be a fun project.
There is a bunch of ready-made code and such projects and ready-made devices for this. You’re late.
@@segrus Thanks, good to know.
But still is a fun project.
@@aduedc Okay) try it
i can verify (anecdotally) that i have experienced higher speeds than dialed on all my penntek rigs... so i turn the speed down a tad compared to my other qrp rigs
This experiment has also shown me that the speed reported by the reverse beacon network is pretty accurate.
👍❤
The problem is Devil runs the world. He is lier and murderer. That's why we've got the Gospel about the God's kingdom.
Jehovah would put everything in order. :-)
i thibk a small error is measurements were committed, which is known as the "fencepost error" (en.m.wikipedia.org/wiki/Off-by-one_error):
"cw" was measured as 7 symbols and 6 gaps long. i think the measurement would be more accurate if/when the length of 7 symbols and 7 gaps would be considered
The problem is that there is no way to force an _extra_ space in the keyer operation.