I passed a milestone this week. Somewhere in my NAQP Phone log upload, I passed 20,000 QSLs in the Logbook of the World(LotW). I have nearly 57,000 QSOs upload into LotW.
I can't imagine collecting 20,000 QSLs by conventional cards. It would take an enormous amount of work. Granted, most of the confirmations I have are for pretty routine contest QSOs that would likely not have bothered with the formality of a paper cards.
In any case, all those confirmations have gone a long way toward earning awards. I've already discussed getting 6-band Worked All States. I've also gotten DXCC, Mixed, CW, Phone, 20m and 15m. I have enough confirmations to get 40m and 10m as well -- I just tend to get one certificate each year.
I was intrigued when the WPX award came on-line in LotW. I found that I have enough confirmations for dozens of awards. I decided I'd hold out for the WPX Award of Excellence.
If you are interested in these operating awards, there's no better way to get the needed confirmations than Logbook of the World. Sure, it's a hassle to get on the system, but once you do, uploading submissions is relatively easy. And then the confirmations just keep on coming.
I wonder how long it will take to get to 30,000?
Sunday, January 20, 2013
Saturday, January 12, 2013
USB to Serial
Re-arranged a few things in the Micro-Shack just before the RTTY Roundup.
For years, I have been using an ancient Toshiba 4000-series laptop. My wife bought this monstrosity back in the late 90's in order to work with custom embroidery software. I'd upgraded it to Windows 98 SE, and it managed to do OK running various Windows contest logging software. While I'd rather run stuff on the Mac anyway, writing some good contest software for the Mac has been one of my Great Unfinished Projects (GUP) for many years now. That's far too long a story to go into right now.
The old Toshiba 4000 wasn't much, 400 MHz Pentium, 800x600 screen. One serial, one parallel and one USB port. It didn't even have networking (much less wireless networking). Old.
When I purchased my MacBook, I set it up through BootCamp to boot in Windows 7. I had tried to run the Windows contest software using it, but I ran into a weird problem. Randomly, after a few minutes to an hour, the machine would flash the screen blue, then reboot. Certainly you could use this in a contest -- at least, not one you were serious about.
About the same time, I attended PDC 09 and came home with an Acer 1420P. Every attendee got one. Although Acer built it, Microsoft had specced this machine. The idea was pretty simple. Microsoft had been tired of evangelizing technologies such as Tablet PC, or 3G networking, Windows 7, etc. Only to have developers say "Well, I don't have a machine that does that." Instead, they seeded the 4000 or so attendees of the conference with these machines. Sweet.
I tried to use the Acer to run contest software, but ran into the same weird problem. Since I couldn't see what flashed up on the blue screen before the reboot, it was hard to tell what was going on. So, I went back to the old Toshiba, and the Acer found some utility at work. Until about a year ago, when the Acer took a tumble off a desk and cracked the screen. It still worked, but the two jagged cracks across the screen made it difficult to use.
My XYL wanted the Toshiba back to do some embroidery, so I went about fixing the Acer. I found a replacement screen for $70, which seemed a reasonable investment. The replacement didn't have the touch interface -- so no Tablet PC. Considering I have an iPad anyway, and Microsoft has moved beyond the Tablet PC with the Surface, it seemed to be a small loss.
As I was setting up for the RTTY Roundup, I ran into the same problem as before -- random BSOD and reboot. However, I'd learned more about Windows 7 in the intervening years. Turns out the automatic reboot is a "feature" you can turn off. Now I can read that blue screen.
After a couple of trials, the culprit appeared to be the driver for the Keyspan USA-19HS. You see, the one thing that the MacBook and Acer have in common (other than running Windows 7), is they have no serial ports. In order to talk with the K3/100, you need a serial port. So I used this Keyspan device that I bought several years ago. Updated drivers were no help. Same problem.
This surprise me somewhat. I really like the Keyspan. It works great on Mac OS X. I was a big fan of Keyspan products -- a decade or so ago, I even met a couple of their developers at Apple's WWDC. At least, I was a fan until Tripp-Lite bought them out. Now, I'm not so sure.
While I suffered through the RTTY Roundup with the occasional BSOD, this seemed like an easy problem to fix. Elecraft sells the KUSB device which would be sure to work, but it's a little expensive at $40. I found a Plugable 2303 USB to Serial converter on Amazon for $13. I was encouraged when I read the driver release notes for this device had the same BSOD problem on Windows 7, but it had been fixed in the latest release.
I got a chance to try it earlier this week. Getting the drivers and setting the thing up was an experience, but not atypical for Windows. Once configured, I cranked up N1MM, put the K3 in TEST mode, and set it up to repeat CQ in CW after 1 second and left it for a few hours. All the DTR access should give the serial port a work-out. Six hours and no BSOD. Seems like it works.
The Plugable 2303 appears to be a good solution. I also tried it on MacOS X. Works fine there. It appears I can retire the Keyspan USA-19HS to MacOS X-only use.
For years, I have been using an ancient Toshiba 4000-series laptop. My wife bought this monstrosity back in the late 90's in order to work with custom embroidery software. I'd upgraded it to Windows 98 SE, and it managed to do OK running various Windows contest logging software. While I'd rather run stuff on the Mac anyway, writing some good contest software for the Mac has been one of my Great Unfinished Projects (GUP) for many years now. That's far too long a story to go into right now.
The old Toshiba 4000 wasn't much, 400 MHz Pentium, 800x600 screen. One serial, one parallel and one USB port. It didn't even have networking (much less wireless networking). Old.
When I purchased my MacBook, I set it up through BootCamp to boot in Windows 7. I had tried to run the Windows contest software using it, but I ran into a weird problem. Randomly, after a few minutes to an hour, the machine would flash the screen blue, then reboot. Certainly you could use this in a contest -- at least, not one you were serious about.
About the same time, I attended PDC 09 and came home with an Acer 1420P. Every attendee got one. Although Acer built it, Microsoft had specced this machine. The idea was pretty simple. Microsoft had been tired of evangelizing technologies such as Tablet PC, or 3G networking, Windows 7, etc. Only to have developers say "Well, I don't have a machine that does that." Instead, they seeded the 4000 or so attendees of the conference with these machines. Sweet.
I tried to use the Acer to run contest software, but ran into the same weird problem. Since I couldn't see what flashed up on the blue screen before the reboot, it was hard to tell what was going on. So, I went back to the old Toshiba, and the Acer found some utility at work. Until about a year ago, when the Acer took a tumble off a desk and cracked the screen. It still worked, but the two jagged cracks across the screen made it difficult to use.
My XYL wanted the Toshiba back to do some embroidery, so I went about fixing the Acer. I found a replacement screen for $70, which seemed a reasonable investment. The replacement didn't have the touch interface -- so no Tablet PC. Considering I have an iPad anyway, and Microsoft has moved beyond the Tablet PC with the Surface, it seemed to be a small loss.
As I was setting up for the RTTY Roundup, I ran into the same problem as before -- random BSOD and reboot. However, I'd learned more about Windows 7 in the intervening years. Turns out the automatic reboot is a "feature" you can turn off. Now I can read that blue screen.
After a couple of trials, the culprit appeared to be the driver for the Keyspan USA-19HS. You see, the one thing that the MacBook and Acer have in common (other than running Windows 7), is they have no serial ports. In order to talk with the K3/100, you need a serial port. So I used this Keyspan device that I bought several years ago. Updated drivers were no help. Same problem.
This surprise me somewhat. I really like the Keyspan. It works great on Mac OS X. I was a big fan of Keyspan products -- a decade or so ago, I even met a couple of their developers at Apple's WWDC. At least, I was a fan until Tripp-Lite bought them out. Now, I'm not so sure.
While I suffered through the RTTY Roundup with the occasional BSOD, this seemed like an easy problem to fix. Elecraft sells the KUSB device which would be sure to work, but it's a little expensive at $40. I found a Plugable 2303 USB to Serial converter on Amazon for $13. I was encouraged when I read the driver release notes for this device had the same BSOD problem on Windows 7, but it had been fixed in the latest release.
I got a chance to try it earlier this week. Getting the drivers and setting the thing up was an experience, but not atypical for Windows. Once configured, I cranked up N1MM, put the K3 in TEST mode, and set it up to repeat CQ in CW after 1 second and left it for a few hours. All the DTR access should give the serial port a work-out. Six hours and no BSOD. Seems like it works.
The Plugable 2303 appears to be a good solution. I also tried it on MacOS X. Works fine there. It appears I can retire the Keyspan USA-19HS to MacOS X-only use.
Wednesday, January 9, 2013
Straight Key NOT!
Since I was thinking about Straight Key Night before, you might anticipate I would have an extensive operating report of the Homebrew 40m Transmitter and Receiver. Well, not exactly....
I did go and review the rules. There are no prohibitions against using electronic keyers. Indeed, the guidelines state "This 24-hour event is not a contest; rather it is a day dedicated to celebrating our CW heritage." I certainly consider my nearly 34-year-old Mini-MOS keyer part of my CW heritage.
So, that was my plan -- to cheat on Straight Key Night and use my keyer.
I was busy during New Year's Eve, so I went out on the morning of New Year's Day and hooked up the keyer to the 40m Transmitter. With the spotting function, it appeared to work. The keying was a little soft, but I was able to find my transmitting frequency with ease. I tried two or three crystals, and then I noticed the oscillator wasn't stopping. If I unplugged the keyer and plugged it back in, I could send one element, and then it would stick on. Then it stopped working altogether.
At this point, I was sort of in a panic. I pulled the cover off the keyer and looked inside. What I saw next set me back a moment -- there was no battery in the keyer! I had been using the keyer solely on the stored power in the electrolytic capacitor for about five minutes. Now that is a low-power station accessory!
I scrounged up a 9 volt battery and verified that I had not fried the 30+ year old CMOS chips. However, it appeared that the CMOS gates had enough leakage that it would not reliably cut off the 6CL6 oscillator.
The original Mini-MOS design keyed through a PNP transistor in order to work with grid-block keyed rigs -- with a negative keying voltage. That worked great with my SB-401 and later with a DX-60B and the FT-101E that I borrowed. When I bought a Kenwood TS-430S in 1985, it had a positive keying voltage. I simply removed the PNP transistor and connected the keying line directly to the CMOS 74C02. Since it worked, I kept using it.
I think the original problem was there are no free gates in the seven chips that make up the keyer. In order to drive a NPN transistor or enhancement-mode FET to key the transmitter, the keying sense has to be reversed -- instead of bringing a positive voltage to ground, we need to go from ground to a positive voltage for the base / gate of the transistor. In retrospect, it would have been easier to have left the PNP transistor in place, use it to drive an NPN transistor or FET.
A quick look in the junk box revealed some 2N7000s -- an excellent enhancement-mode FET to key the transmitter. (The K1EL keyers use this same device) I just need to dig up a PNP and some resistors. Ah, a project for another day.
Oh, and what about Straight Key Night? Well, since I had just gotten the K3 going, I decided to play with it instead of SKN. I ended up working DX spots on 12 and 17m, including working VP2MRV on RTTY using the K3's FSK D CW to RTTY mode. Cool.
SKN? Maybe next year....
Saturday, December 29, 2012
K3!
![]() |
| K3/100 build and under the Christmas tree. |
When it came time to make our Christmas lists this year, I had mentioned that it had been ten years since I bought my last ham transceiver -- I finished the KPA100 for the K2 in the fall of 2002. And while it might be time to look at something new, modern transceivers are not cheap. In the end, I decided to ask for contributions toward the "K3" fund -- money I would use to buy an Elecraft K3 at some point in the future.
Before Christmas, my wife had hinted she had gotten me something expensive. She would tease me that she had purchased a Cessna 140 or a Harley-Davidson. She did it often enough I wasn't sure what to believe.
![]() |
| Inside these boxes is a bit of joy. |
Needless to say, I was surprised to open the box find a stock K3/100!
She had the presence of mind to get me the unassembled version, instead of the factory-built. While it's a bit more work, I really enjoyed assembling my K2/100, so I figured I'd get some enjoyment out of this.
Biggest problem, though, was where to build. The Micro-Shack is, well, micro. The entire desk surface is barely 5 by 2 1/2 feet. Most of my tools are still down at the QTH in Gwinnett county. Nevertheless, I figured I'd do what I could with what I had, rather than wait a week or so until I could get to my big workbench.
![]() |
| K3/100 goes together on the world's smallest workbench. |
It was already late in the day when I got started, so I decided to forgo the Elecraft-recommended inventory. I've built a number of their kits, and I can't say I've ever been shorted a part. Indeed, they always seemed to ship me extras. In retrospect, this wasn't such a bad idea. If you've never built a kit before, inventorying the kit is a great idea.
Since all the boards are pre-assembled, there's no need to warm up a soldering iron. However, there's plenty of mechanical assembly. I thought it was weird that Elecraft has one put the left and right side panels on, only to have you remove them a few steps later.
I had never really seen the insides of a K3 before, and the pictures don't do it justice. In some ways, it really is like an over-sized K2, with the mechanical rigidity coming from the main board. Once you get the casing on, it's really pretty rugged.
![]() |
| Initial power-on successful. |
I did have one item I did mess up during assembly. It was the KREF3 board. The instructions indicate you are to cut off any leads that might be longer than certain components on the board. I found a through-hole connector lead that I thought was a bit long, and when I tried to trim it, I also managed to bust capacitor C2 off the board. Fortunately, this component isn't used for anything critical. My guess is that it is used for FM only, but there's not really any documentation as to what the TXMIXFIL signal does. I've already contacted Elecraft support as to how they suggest we fix this.
After about six hours of work, my K3/100 was all assembled and calibrated. I only ran into one issue -- I had no dummy load to perform the Transmitter Gain Calibration. I ended up doing the calibration manually using the antennas I have on hand. Not perfect perhaps, but it will do until I can get my hands on a dummy load.
![]() |
| K3/100 assembled and operational. |
Now, I need to sit back and read this thick operating manual so I know how to use my new rig! See you on the bands.
Thursday, December 27, 2012
Six Knots Every Ham Should Know
In working with wire antennas, I'm thankful my parents enlisted me in the boy scouts. How else would I have learned all these useful knots? Every amateur radio operator should know how to tie these six knots:
- Bowline - an extraordinarily useful knot. Anywhere you need a knot that won't slip, won't tighten down and is very strong. I use this one everywhere -- when tying ropes off to insulators, bringing wires through insulators, tying ropes to carabeaners, etc. If you learn no other knot, learn this one.
- Square Knot - Got two hanks of rope, neither of them long enough for the job, join them with a square knot. While it won't go though pulleys, it will go over branches with a tug our two. best way to join ropes of roughly the same size.
- Sheet Bend - so, how do you tie your hauling line to the fishing line you've managed to get over that tree? Square knot doesn't work so well when one end is a lot smaller than the other. The Sheet Bend is the answer. Just remember that the larger line gets the "U" and the smaller line is the "X".
- Taut-Line Hitch - need to adjust a rope to a modest tension, but don't want to keep re-tying? The Taunt-Line Hitch is perfect. You can slide this knot considerably to adjust tension. Just don't use it for anything structural, like guy wires, since it can slip down under enough tension.
- Two Half-Hitches - Have a free end of a rope you don't want to flap around loose? Two half-hitches is the choice. I often use it to secure the free end after a Sheet Bend.
- Clove Hitch - Be careful with this one. It works well if you tie to a fixed post that can't rotate. Don't try to use it to raise a mast or left a boom -- with a smooth rope it may turn and then come loose.
Learn these knots inside, you'll want to have them memorized for when you are ready to use them out in the field or woods. Enjoy.
Tuesday, December 25, 2012
Thinking Ahead to Straight Key Night
Practically speaking, the transmitter isn't terribly useful. Being crystal controlled, you can't hunt around the band and answer someone -- you must call CQ. And it only covers 40m. 40m is a great band, but not everything happens there.
The receiver would be more practical to use -- it's a pretty nice superhet, with a narrow CW filter. But, really, it's designed for use with the transmitter, so it too, sits idle on the shelf.
2013 will be the seventh year I've operated Straight Key Night with this transmitter. Frankly, I'm considering cheating. Instead of using my old Japanese J-38-style clone, I'm thinking of using the Mini-MOS keyer. The whole idea of Straight Key Night is to return to our roots. Why not use this over venerable equipment? I also wonder how the transmitter will sound being keyed electronically, instead of mechanically.
If I do end up using the keyer, I'll have to disqualify myself.
Wednesday, December 5, 2012
160m Inverted L
Back in 2001, when Gary Breed, K9AY, helped me to put up my tower, he suggested that I operate the ARRL 160m contest. My excuse at the time was that I had no antenna for 160m. His suggestion was simply to load up whatever I had, that this contest was an opportunity to make a lot of contacts without much of an antenna -- and, besides, it was a lot of fun.
That year, I threw together an inverted L. It wasn't much more than 140 feet of THHN house wire, mounted to a simple particle board frame that could house a series variable capacitor. I ended up removing the series capacitor and just feeding it straight through.
I only had wire and room for two 100 foot elevated radials that were about 40 degrees to each other.
The inverted L never did work right that year, and I ended up using an 80m doublet about 10m off the ground for over 200 contacts.
I never forgot that experience, and I have enjoyed the ARRL 160m contest many, many times since then. I eventually shunt-fed the tower. Over the years, I managed to work all states and over 25 countries on 160m.
Out in Floyd county, I figured I had plenty of space to try out the inverted L again. It's taken a year, but I finally put it up, as you can see from the picture above. Or not. You see, it's about 200 feet up the hill going up about 60 feet into a red oak tree. The remaining 80 or so feet goes east through the woods to another tree. Even if you know where to look, it's hard to spot. Impossible, really.
Putting down radials is more an exercise in finding wire. Copper has gotten very expensive. I bought a spool of 500 feet of 14 gauge THHN wire and cut it into quarters. ($45 at Home Depot! ouch) Then I drug the four wires into the woods. Bad idea. They ended up looking hopelessly tangled.
No matter. I've been untangling wire and rope since I was 10 years old -- I have decades of experience. It took a while, but I rolled out the four radials roughly ninety degrees to each other. I fed the antenna with over 200 feet of the Wireman's best RG-8X, Certified 118. With only four radials, I did not expect much.
I was pleasantly surprised.
The antenna isn't quite resonant in-band. My initial readings showed an SWR valley around 1860 kHz. A little high, but useable. Subsequent measurements from the shack show the low SWR is below 1750 kHz. All the coax makes the antenna broad -- just because of the line losses. (This stuff is rated at 1.5 dB loss per 100 feet at 30 MHz -- losses at 2 MHz can't be much more than 1 dB) For this years ARRL 160m, I just ignored the losses and used a tuner.
My schedule only permitted me to operate for about four hours on the second night. This antenna was extremely effective. I could work just about anyone I could year, and calling CQ was reasonably effective.
The most amazing thing about this antenna is how quiet it is. At first, I thought it might be due to all the coax and ground losses. But, since the antenna was so effective -- at least as effective as the shunt-fed tower, I've changed my mind. It's just really quiet out here in the country in Floyd county.
My plan is to add more radials -- four more 125 footers ($45!) and eight of half that length ($45!) -- for a total of sixteen radials. I also want to add a trap for 80m, and I'll worry about trimming the antenna to resonance at that time.
That year, I threw together an inverted L. It wasn't much more than 140 feet of THHN house wire, mounted to a simple particle board frame that could house a series variable capacitor. I ended up removing the series capacitor and just feeding it straight through.
I only had wire and room for two 100 foot elevated radials that were about 40 degrees to each other.
The inverted L never did work right that year, and I ended up using an 80m doublet about 10m off the ground for over 200 contacts.
I never forgot that experience, and I have enjoyed the ARRL 160m contest many, many times since then. I eventually shunt-fed the tower. Over the years, I managed to work all states and over 25 countries on 160m.
Out in Floyd county, I figured I had plenty of space to try out the inverted L again. It's taken a year, but I finally put it up, as you can see from the picture above. Or not. You see, it's about 200 feet up the hill going up about 60 feet into a red oak tree. The remaining 80 or so feet goes east through the woods to another tree. Even if you know where to look, it's hard to spot. Impossible, really.
Putting down radials is more an exercise in finding wire. Copper has gotten very expensive. I bought a spool of 500 feet of 14 gauge THHN wire and cut it into quarters. ($45 at Home Depot! ouch) Then I drug the four wires into the woods. Bad idea. They ended up looking hopelessly tangled.
No matter. I've been untangling wire and rope since I was 10 years old -- I have decades of experience. It took a while, but I rolled out the four radials roughly ninety degrees to each other. I fed the antenna with over 200 feet of the Wireman's best RG-8X, Certified 118. With only four radials, I did not expect much.
I was pleasantly surprised.
The antenna isn't quite resonant in-band. My initial readings showed an SWR valley around 1860 kHz. A little high, but useable. Subsequent measurements from the shack show the low SWR is below 1750 kHz. All the coax makes the antenna broad -- just because of the line losses. (This stuff is rated at 1.5 dB loss per 100 feet at 30 MHz -- losses at 2 MHz can't be much more than 1 dB) For this years ARRL 160m, I just ignored the losses and used a tuner.
My schedule only permitted me to operate for about four hours on the second night. This antenna was extremely effective. I could work just about anyone I could year, and calling CQ was reasonably effective.
The most amazing thing about this antenna is how quiet it is. At first, I thought it might be due to all the coax and ground losses. But, since the antenna was so effective -- at least as effective as the shunt-fed tower, I've changed my mind. It's just really quiet out here in the country in Floyd county.
My plan is to add more radials -- four more 125 footers ($45!) and eight of half that length ($45!) -- for a total of sixteen radials. I also want to add a trap for 80m, and I'll worry about trimming the antenna to resonance at that time.
Subscribe to:
Posts (Atom)







