Author Archive
Don’t forget — Straight Key Night 2018 is tomorrow !
December 30th, 2017 | 
Author: Straight Key Night -- 2018
Don't forget January 1st, 2018 starting 00:00 GMT (7pm EST Dec 31) is the start of Straight Key Night 2018. Bring your tired, old equipment on-air and mash your favorite mechanical key. This is not a contest, just an opportunity to make lots of fun QSOs.
ARRL has details on their website... http://www.arrl.org/straight-key-night
Video from 2018 SKN
If you hang in there until the 2:08 mark you'll see my new, spiffy, dual camera angle recording method that I plan to use in all my videos.
So, lower your power, and raise your expectations...
72/73
Richard AA4OO
Video recording woes
Getting the audio right shouldn't be this hard...
I've spent a considerable amount of time lately creating machine generated Morse code videos for copy practice.
I've created videos of the top 100 Words, 500 Words and today, the top 100 most common words in a QSO, at different speeds. I'm machine generating rather than keying them by hand because I would make too many mistakes. I do this through my memory keyer connected to the computer via a terminal application and capture the text being sent along with the audio.
I've created videos of the top 100 Words, 500 Words and today, the top 100 most common words in a QSO, at different speeds. I'm machine generating rather than keying them by hand because I would make too many mistakes. I do this through my memory keyer connected to the computer via a terminal application and capture the text being sent along with the audio.
Getting the audio right has been hard. When I record screen captures on my PC it wants the audio to be recorded at 44 kHz but when I transfer that to a Mac to use my video editing software, it expects the audio to be recorded it 48 kHz, and converting the audio in the video just doesn't work well. I use an H2 USB mic for the recording. If I set the mic and the PC screen capture software to 48 kHz I get no audio. So I have had to record at 44 kilohertz on the PC. I'm sure there's better screen capture software that could be used on the PC but I haven't been able to find it for free. I guess I'm too cheap.
This has caused my videos to have popping noises in the transferred audio. While I've tried to fix it during the editing process, it still sounds bad to me.
So, you may wonder why haven't I just recorded the videos on a Mac from the beginning rather than using a PC? Well, I haven't been able to get the OSX terminal application to talk to my 1990's MFJ Super Memory keyer via the serial cable. For some reason my Mac doesn't have a driver for the usb dongle I used to talk to the old memory keyer but my PC does. I searched a bit more and found a non-free terminal application that will let me connect to this serial cable. Now I connect from the Mac and capture the keyer output. I'll spend hundreds of dollars on ham gear but ask me to shell out $30 for computer software and I balk. And after all, I'm a software developer, shame on me.
So, starting today, my new videos should have improved audio and be at a higher resolution than previous videos recorded from the PC.
These practice Morse code videos seem to be popular with folks, so I hope they're helping people. They're a lot of work but I guess they're worth it.
That's all for now...
So lower your power, and raise your expectations
Richard AA4OO
http://www.hamradioqrp.com
No love for CW in ARES / RACES
CW - emergency communication ?
With the recent spate of natural disasters and dire warnings of impending doom, from terrorists and rogue nations alike, it got me to looking into my previous emergency ops participation.
When I was a newly minted amateur operator about a decade ago, I participated some in traffic nets and obtained FEMA certifications to participate in emergency operations. At the time I had built my go-kit, consisting of battery powered FM 2m/440 equipment and portable J-poles. It even had wheels and a pull handle, very spiffy. But I wasn't much concerned with CW.
With a re-kindled interest in QRP and CW operations, it got me to looking again at participation in emergency ops, and to my surprise there are few states that even list CW as a mode for emergency communication frequencies.
The following table lists the only pre-approved ARES frequencies I can find, designated for CW. There are 37 states missing from this list... If you live in a state other than those listed below; no CW emcomm for you buddy.
Excerpt from http://www.idahoares.info/resources_ares_frequencies.shtml I looked in a number of ARES/RACES sites listing nationwide frequencies and they appeared to have the same list
Why no love for CW?
I understand that CW is a slow mode of communication and not well represented by the amateur radio masses, but let's face it, CW has more efficiency at getting a signal through in marginal conditions than FM or SSB. When a disaster strikes and the electrical grid is down for hundreds of miles and gasoline for running generators is short, you won't be operating QRO stations or have power to run computers for digital modes. Powering a 12v battery with a solar panel may be your only option.
CW's power density is superior to any non-digital mode. A 5 watt CW signal packs as much punch as 100 watt SSB and let's not even discuss the inefficiency of FM or AM. In extended emergency conditions, using CW could mean the difference between getting a message through and not.
Operating CW in Emergencies
So if there were an extended emergency, shouldn't there be some fallback plan for use of low cost, easy to build and store XTAL controlled radios? Many home-built XTAL controlled CW radios use QRP watering hole frequencies for their center frequency; 3560, 7030 and 14060 kHz. Why not designate those frequencies using CW as standards for emergency communication?
Maybe CW is sinking so far into obscurity in amateur radio, this sort of thinking doesn't enter the consciousness of those in charge, but I don't think it should. Maybe CW clubs like FISTS and SKCC could partner with QRP clubs (who tend to be CW focused) to form a homespun group of emergency operators prepared to use CW when all else fails. It might be fun to organize, and who knows, it could save a life, or reunite separated family members.
That's all for now...
So lower your power and raise your expectations
72/73
Richard, AA4OO
Morse Chrome
Chrome browser extension for Morse Code
I'm always interested in finding new ways to practice my copy skills when away from the radio.
While there's a growing number of mobile device apps for sending and practicing Morse Code, as well as excellent websites like www.lcwo.net, it's always fun to stumble upon a new one.
While there's a growing number of mobile device apps for sending and practicing Morse Code, as well as excellent websites like www.lcwo.net, it's always fun to stumble upon a new one.
Morse Chrome is an extension for the Chrome web browser that allows you to select text on a web page, and send it as Morse Code.
After installing the extension, select text on a web site of your choice and right click (or in the case of a Macintosh, CTRL-click) and one of the options in the right-click dialog will be "Play Morse".
It will proceed to play the selected text as Morse Code.
The speed and pitch can be managed from your Chrome Extension options for Morse Chrome
The generated code sounds accurate to me but it is generated with a rather harsh ramp (possibly a pop) at the beginning of each element. I've heard other computer generated Morse sound similar so it may simply be a problem with the the audio API in the browser. I've played around with different pitch settings and can't reduce the pop. It may be better or worse on different computers.
The only real complaint I have is that I can't find a way to stop it from playing without closing the browser. So if you select a rather large block of text you'll have to wait for it to finish sending before being able to select another selection, unless you exit and restart your browser.
But it's another tool in the arsenal of practicing Morse Code practice so I'm glad to have it.
That's all for now...
So lower your power and raise your expectations
72/73
Richard AA4OO
CQ WW Contest
FT8 hasn't killed CW yet
I'm not a contester but I enjoy listening to some amazing contestants pulling in those weak signals flying by at 30 wpm during CW contests. Today is the last day of the...
CQ WW Contest
 |
| Lots of CW stations grabbing those final contacts of the contest |
I was listening via my SDRPlay connected to a short piece of wire in my garage. Even with this highly compromised "antenna" I was hearing wall-to-wall CW stations vying for a piece of the action. I listened to W4SO and other big-gun stations, pulling in DX contacts one after another.
I'm looking forward to the day when my brain can decode call signs at that rate. I need to spend more time with LCWO.net callsign trainer...
That's all for now...
So lower your power and raise your expectations
72/73
Richard AA4OO
This is not the wattage you’re looking for… move along
Getting hot under the collector/base junction
Where did my power go?
My Elecraft W1 power meter has been absent from the antenna chain for a while due to a jumper cable shortage when I last reconfigured my shack. But now the W1 meter is back in the chain and it revealed something a bit worrisome about the 1Watter transceiver...
My Elecraft W1 power meter has been absent from the antenna chain for a while due to a jumper cable shortage when I last reconfigured my shack. But now the W1 meter is back in the chain and it revealed something a bit worrisome about the 1Watter transceiver...
I've had a bunch of QSOs using the 1Watter both in the shack and in the great outdoors. The 1Watter is my first home built transceiver (albeit from a kit) and has been a great learning experience. It is called a 1Watter (or 1H2O as Diz calls it) because it nominally produces an output of 1 watt.
The Elecraft W1 power meter is a nice, inexpensive QRPp to QRO meter because it measures from 150 watts all the way down to 150mw.
The little 1Watter transceiver does indeed produce just a hair over 1 watt when it's first powered up. Tonight I tossed my call out on 7030 kHz and was promptly answered by N4DR up in Maryland. He was running a YOUKITS TJ5A at 5w. When we started the QSO my W1 meter showed that my 1Watter was outputting between 900mw and 1w to my mighty attic antenna.
Then by the second exchange in the QSO I noticed my output power dropping down to 700mw. By the end of our ragchew my 1Watter output had dropped to 500mw.
 |
| Power meter in background showing 500mw by the end of the first QSO |
As I ended that first QSO I was called by another station (AF4YF) who was running a 2 watt homebrew xcvr. And by the end of that QSO the 1Watter was producing less than 300mw. I felt that some investigation was in order.
Heat is the enemy
The 1Watter uses a 2N5109 NPN RF transistor for a final. Transistors really are not fans of heat.
The maximum power output available from a power transistor is closely linked to temperature, and above 25°C falls in a linear manner to zero power output as the maximum permissible temperature is reached.
My 1Watter kit included a friction fit heat sink, seen at the top of the photo below. But apparently this heat sink either saturates quickly or doesn't have sufficient surface to conduct away the heat. My enclosure is not vented but it is alumunium and I don't feel any appreciable temperature rise above ambient so I don't think venting is in order yet.
I allowed the 1Watter to rest for 30 minutes following the QSOs, still powered but not transmitting. That only resulted in the output power getting back into the 700mw range. I'm considering increasing the bias to start with a higher transmit power so that it will maintain 100mw but I'm afraid of destroying the transistor. I might also try some conductive paste but it's messy and I'm not sure it will help if it can't be pressed between two surfaces.
I'd appreciate any constructive suggestions. I'm still a noob at this electronics stuff.
But the real moral of the story is...
 |
| Band conditions on the evening of this QSO |
So as I sat here wondering why my 1 watt radio was only producing a 1/2 watt now, I reminded myself that I was having extended QSOs using a (now) 500mw radio with other QRP operators (5w and 2w). I was also using my attic antenna, not some multi-element beam on a tower. Band conditions on 40m were also a limiting factor tonight (see snapshot at right).
These were not simply swap 599 TU QSOs, we were exchanging information on multiple go-rounds with solid copy.
So if you're reading this blog you likely have some interest in QRP. Hopefully this is just yet another reminder that we often don't need as much power as we think we do for communications. I was getting discouraged this summer due to the decreasing sunspot cycle and thinking "I'm gonna need to operate QRO more and likely get a real antenna put up in my yard".
But it's times like this with my 1Watter that keeps reminding me to lower my power and raise my expectations.
But it's times like this with my 1Watter that keeps reminding me to lower my power and raise my expectations.
So lower your power and raise your expectations...
72 / 73
Richard, AA4OO
Head Copying CW
There's more to using Morse Code than Learning Morse Code
It's been about 18 months since I started learning Morse Code in order to use it for making CW contacts in amateur radio. Learning the code allows you to recognize the letters, numbers and punctuation but it's akin to when you learned your "letters" when you were a child. Knowing the alphabet is just the first step to "reading". So it is with learning Morse Code.
When I started making contacts using CW it was fairly formulaic. I even had my QSOs written out with regard to what I was planning to send and what I expected to hear during each exchange.
But then my copy and sending speed increased beyond 17-19 words per minute and I could no longer type or write down what I copied fast enough to comprehend and I began to head copy.
Head Copying
Head copying is when you stop transcribing what you hear and listen to it as you would a conversation and only take notes on salient points. This was a big step for me and it has been a difficult transition.
Using Morse Code to communicate at speeds faster than it can be written straddles the weird place between hearing and reading. We learn morse code by its sound but at slower speeds, say below 30wpm what we are "hearing" is letters, not words so we are having to buffer those letters in our head to spell words. When we "listen" to someone speak we are not hearing them speak letters but complete words, when we "read" our brains are not looking at individual letters but at complete words. When we hear Morse code at 20-25 wpm we are hearing very slowly pronounced words and it is a new skill that has to be learned.
This skill is necessary for ragchewing. A ragchew is a long QSO between two amateur radio operators. This is generally what amateur radio operators are doing on the radio when they're not contesting, ...
How to practice for a ragchew
So after you learn the code, how do you learn to use it in a conversation?
I struggled with copying ragchew QSOs at 20+ words per minute for most the spring and early summer of 2016. Just listening to QSOs alone wasn't cutting it for me. During my lunch time at work I began regularly using my CW training application on my phone to send the top 500 words at 25wpm and it has been a big help to me.
I had to learn the skill of not just recognizing letters but holding what I was hearing in my brain long enough to turn it into a word and just as importantly not to get hung up on a word that I couldn't immediately recognize but let it go and pay attention to the next. To me, this has been a bigger learning curve than recognizing the alphabet and numbers at speed.
In addition to learning to buffer the letters until they form a word I must also keep the slowly accumulating set of words in my head until it forms a sentence or makes sense as to what is being communicated.
THIS IS COMMUNICATION with Morse Code and it is different than anything else we are familiar with so treat it as learning a new skill.
Now if all you are trying to do with CW is contests, you don't need this skill. You just need to be able to copy a call and whatever designators are sent after it for the contest rules (state abbreviation or a contest number or grid square) and get it copied into your logging program. But if you want to communicate at speeds above 20wpm you will need this new skill.
Next steps
After you've practiced with machine sent top 100 or top 500 words you'll still need time copying actual QSOs because more often than not, most operators you will communicate with have lousy spacing and run their words together or use so many abbreviations that you'll have to learn to hear the abbreviations as new words. When I work an operator who runs things together I'll first try to really exaggerate my word spacing during my exchange to give them a hint and if that doesn't work I ask them put more space between their words. Some will comply, but some folks just don't seem to know how to leave space so I'll catch what I can, politely respond to what I could understand and then move on.So if you're getting discouraged when you reach a wall of comprehension, try the steps above and with time I think you'll find your comprehension during a ragchew improving and it will take you to a new place in the hobby.
That's all for now
So lower your power and raise your expectations... and put extra space between your words!
73
Richard AA4OO
