AmateurRadio.com

It's been a while since I really made an effort to use the ol' Vibroplex.  I gave the contacts a decent cleaning today and gave it a whirl in a QSO with Art K8CIT. I don't think I sounded terrible - and I hope Art didn't think so either. I could use some more practise, though, and I will continue to use it more often.

I haven't run this piece in a long time. It's from my old webpage on how to adjust a bug:

Using a bug is a real fun part of using Morse Code.  Adjusting one properly so that it works right for you and doesn't frustrate the heck out of you is easy; if you take your time and work methodically. Refer to the photo below for reference.


The first thing you do is to back off all the adjusting screws quite a bit.  Not all the way; but far enough out so that everything is nowhere near being set.  Once that's done you want to adjust the action of the pendulum.  Unscrew "A" - this is the pivot point for the pendulum.  Slowly tighten it. You'll know you have it adjusted correctly when the pendulum moves from side to side freely with no binding; but, at the same time, you can move the finger pieces up and down with your fingers and feel very little or no play.

The next thing you want to do is to adjust screw "B".  Allow the pendulum to hit the damper.  Screw in "B" to the point where you can either see or just perceive the pendulum has touched the damper.  Stop there and secure the screw with the knurled lock nut.  It is important not to move the pendulum too far away from the damper or else you will not be able to reliably stop your "dits".

The next thing you want to do is adjust the  left trunnion screw -  D.  This will control the amount of side to side travel of the pendulum.  For smooth code this gap should be very small.  I take a piece of ordinary printer paper, fold it in half to double it and adjust the spacing so that the paper will just slip between the point of the screw and the pendulum.  This results in a very small amount of side to side travel.  The end result is a nice and clean transition between "dits" and "dahs".  I do the same thing for the amount of spacing for the "dah" contact at C.  I turn that trunnion screw in so that the paper slips in the gap easily with no binding, then I lock the set screw in place to keep the setting.

The next thing you want to do is adjust the "dits" making part of your bug.  This is done by adjusting "E".  When "E" is adjusted correctly, you should be able to swing the pendulum to make "dits"; and get 10 to 15 "dits" before the pendulum dampens out and comes to a rest.

"F" controls the tension of the "dit" action.  I find it best to tension the spring about half way.  Hopefully, if you follow this guide and play around a little bit and experiment, you will find the "sweet spot" that will allow you to send really glassy smooth Morse Code.

Sending with a Bug is just as much fun as sending with a keyer and paddles.  However, sending with a Bug allows you to add a little personality.  Listening to CW sent with a keyer sounds sterile compared to that sent with a Bug.

If you need to slow down the speed of your Bug to a point that's even slower than what you can get with the weight(s) positioned all the way to the end of the pendulum, then clip a clothes pin or a few alligator clips to the end of the pendulum.  This will slow down a Bug to an effective speed as low as 13 words per minute or so.

In my opinion, you know that your bug is adjusted properly when you can send characters like X, Y, Q, C, F and L with little effort, and they sound good - or at least recognizable in my case!

Here's a great video that shows you how to do it, also:


72 de Larry W2LJ
QRP - When you care to send the very least!

And I'm not talking about changing AC to DC.

As predicted, I have received some comments over at AmateurRadio.com, regarding the immediately preceding "Bug Fist" post.  As I've stated there, and will state here again (for the record) that post was NOT intended to be about folks who are learning how to send Morse Code as a beginner.  That post was supposed to be about people who know how to send good code - but don't, because they don't use a bug correctly.

But to answer a question posed over there. How does one learn to send good code in the first place?

Good question.

Back in the day - back in my day, the FCC had a very nice program in place. It was called the United States Amateur Radio Novice License.  It was our gateway.  We learned to receive Morse Code at 5 WPM.  We were restricted to "Novice sub bands".  You say that sounds like a curse?  Heck no! It was heaven!  Imagine trying to learn how to ride a bike with other kids on the playground zooming around on ten-speeds, mountain bikes, scooters and what have you.  We had a little area, set aside for us, where we could zip around on our training wheels.  As we rode and rode (made QSOs) we built up our confidence and eventually shed our training wheels, and we upgraded. Oh, in the process, we fell off our bikes, and got our knees and elbows bloodied along the way. But we learned!

But as they say, "Them days are gone forever." So what's a new Ham who wants to get on HF CW supposed to do?

Several things, actually.

I am going to assume you have learned the basic Morse Code character set and that you can receive at a speed of about 5 WPM.  If you haven't, you need to do that.  But here's an important point - if you've learned CW, whether it be from W1AW or whatever software program - you already know what good code sounds like!  You will also know, conversely, what bad code sounds like. Your assignment is to send good code.

This is where code practice oscillators come in to play.  They weren't invented just to teach people how to learn to receive Morse Code, they were also invented to teach people how to send Morse Code. If you have one, fine. If you don't - get one. Or ..... you can go to your rig, and turn off the VOX while in the CW mode. This should give you a nice, big, fancy and expensive code practice oscillator. Use it. Use it a lot until you are comfortable and can send Morse Code without really have to think about forming the characters too much. As I stated over at AmateurRadio.com - use a tape recorder, or the voice recorder on your cell phone and record your sending.  If you can decode what you are sending, then other people will be able to, also.  If you listen to your fist and find yourself going, "What?!?", then you probably aren't ready and need to practice more. It's OK to send slowly, but accurately. Personally, I would rather listen to someone sending slowly, but correctly, rather than listening someone trying way too hard, too fast, too soon, who leaves me scratching my head. (Pssst! This is why the FISTS motto is "Accuracy transcends speed.")

Once you are reasonably confident in your sending skills, you can get on the air.  The Novice subbands don't really exist anymore, but you can find some slower folks hanging around together around 7.125 MHz. The FISTS and SKCC frequencies also good places to hang - from around .050 to .058.  You can ply your newly discovered skills there among friends. Don't be intimidated!  Relax, take a deep breath and enjoy the ride. Remember, we're not looking for a cure for cancer or cardiovascular disease here. We're supposed to be having fun. Don't obsess and don't put yourself down. We were all beginners once, and we all had to start somewhere.

I'm going to warn you. Your first half dozen or so QSOs will be a bit nerve wracking. Best thing to do is write down ahead of time a "canned QSO".  Just follow the script and before you know it, you'll feel more and more comfortable and will no longer need the script.  If you try to make a QSO every day, before you know it, you'll come to recognize the experience you have gained.  Your speed will increase and you will really come to enjoy this new mode you have set out to learn.

Another word of caution. There will be jerks! Sorry ..... there's nothing I can do about that. Just as on the highway, there's always that idiot that has to zoom in and out of lanes at 75 MPH, you're also going to run into jerks that think 40 WPM is beneath them and will not slow down for anyone - God included. If I may get Biblical here without offending anyone ...."Just shake their dust from your feet and go onto the next village."  The speed demons who won't QRS for anyone are not worth your time or effort. I've been in this game for 36 years now, and I run into my share, too.  To this day, I have to ask myself why guys send at around 55 WPM in contests only to have to repeat their exchanges multiple times, because we mere mortals can't copy their "buzz saw" CW.

Conversely ..... should you answer a CQ, do not, under any circumstances, start sending faster than you are comfortable receiving!  I know, we all have a tendency to do this, but it is going to get you into trouble.  You are going to get yourself into a terrible experience that will make you want to run away from Morse Code forever.  Any dedicated CW op worth his salt will slow down (QRS) for a newbie. Do not be afraid to ask someone to "QRS PSE?", either. We don't know for sure that your uncomfortable unless you tell us.  Sometimes, we more experienced CW ops assume too much, too.

I think I covered everything and I hope this helps those of you who are newer out there and are struggling to learn the CW ropes. If you have any questions, pop something into the comments box or send me an e-mail. I will try to help in any way I can.

There's an old joke where a stranger asks a cabbie in NY how to get to Carnegie Hall. The cabbie replies "Practice!".  If you want to get good at the Morse Code game, it's going to take lots of practice. No way around it, but it doesn't have to be a chore or unpleasant. Have fun and enjoy yourself!

72 de Larry W2LJ
QRP - When you care to send the very least!

John KK4ITN left a comment on my post "Conditions" over at AmateurRadio.com. Here's a line from it:

"Seems when the bands are down every person with a ‘bug’ is out calling cq. Wish they would put code oscillators and dummie loads on sale. Dits at 20 wpm and dahs at 5 wpm."

I guess it's not directly related to band conditions, and I'm not sure that John's claim is 1,000,000% accurate, however - he makes an excellent point.

Not to dump on bug users, because I have a bug. I like using a bug. Using a straight key makes the arthritis in my hands go "Hey! Stop that!" But unless I've practiced with my bug (off the air) for a while .... my sending can be pretty bad.  So I try to make it a point to take the KX3 "off the air" and practice sending with my bug on a regular basis.  Not as regularly as I should, but I try to keep in decent practice.

I agree with John and I would posit that listening to someone use a bug (or even a straight key or paddles, for that matter), who doesn't know how to use it properly, is akin to listening to nails being scratched across a blackboard. NB: For any younger readers, a blackboard is what we used in school before the advent of whiteboards and smartboards.  If you scrape your fingernails across the surface of a blackboard, it makes a sound unlike anything you've ever heard. It literally hurts to listen to it.  It will make your teeth ache. There's something about human fingernails and slate that just don't mix. Listening to someone scratch a balloon is almost as bad. But .... I digress.

The phrase, "Dits at 20 wpm and dahs at 5 wpm" resonated with me.  Morse Code sent like that is not only unreadable - even worse, it's unbearable.  No one is asking that all Morse be sent so that it sounds like it's coming from a keyer or a computer - but for Pete's sake - at least make sure your sending is copyable!

I would suggest that anyone who is inclined to use a bug perform this little exercise.  Send some Morse and record it, either with a tape recorder (do they still make those?), or, I believe most smartphones have a voice recorder feature. Do it off the air. Either send your RF into a dummy load or turn off your "VOX" - that usually will put your rig into code practice oscillator mode.

Send some Morse, listen to it, and copy what you sent. Be honest and critical with yourself. If you can honestly copy what you've sent, then you're probably good enough to go live. It might even be a good idea to wait a day or two between the sending part and the listening to yourself part - just in order to make it a bit more objective.

I can tell you for a fact, that I have done this - I have listened to my own bug fist - and have said, "Oh my!".  It was a rude, but necessary awakening. I am totally glad that I did not subject my fellow Hams to what I had thought was decent sending.

72 de Larry W2LJ
QRP - When you care to send the very least!