AmateurRadio.com

On Saturday I had several folks over for an antenna party.  My two element 10/12/15/17/20 meter quad lost the 10 meter driven element wire over the winter and I was wanting to take the quad out of service.  Quads are great antennas, perhaps magical, but from a maintenance and installation point they are a nightmare.  This quad went through two ice storms and survived, but that wasn't without much gnashing of teeth.  Quads are three-dimensional antennas, so one big disadvantage is they take up a lot of vertical real estate on a tower.  Since originally putting this tower and quad up, I got interested in six meters but I couldn't put a six meter beam up on the tower.

Rather than hinging down the 40' (12 m) Rohn tower as usual I rented a 45' (14 m) manlift locally.  This was a good decision.  This model had a 500 pound (227 kg) platform capacity, so two people plus gear could fit in it.  Once I figured out how to operate the controls, it was a very nimble piece of equipment.  We wore harnesses and clipped into the platform railing with lanyards for safety.



Anthony Good, K3NG, is a regular contributor to AmateurRadio.com and writes from Pennsylvania, USA. Contact him at [email protected].

As I mentioned in my posting from last week, I spent a few days in Florida recently. I was down there visiting family, but had free time in the afternoons and had planned on operating for a few hours each day from Lido Key, which is IOTA designator NA-034. Briefly, IOTA (Islands On The Air) is a program where hams operate from various islands all over the world and make contacts with other hams. There’s an awards program for contacting various numbers of islands. The rules (link goes to a PDF file) for what qualifies as an island for IOTA purposes are a bit complex, but Lido Key, just west of Sarasota, Florida, qualifies. I’ve made a couple of trips down there in the past and had a lot of fun operating from that location.

My plan was to head out to the parking lot of Lido Beach and set up there, as I’ve done in the past.This location is very easy to get to, and the parking lot has never been full when I’ve been there, so I can take up as much space as I need. For this portable operation, instead of using hamsticks (which are very straightforward to use but since they are nearly 2 meters long, are hard to ship), I decided to use my Buddistick vertical antenna. I’ve written about the Buddistick quite a bit here before, you can do a search from the search box on the right of the blog home page for “buddistick” to see all the references. Because Sharon and I didn’t want to have to check baggage, I shipped the radio (my trusty Icom 706MkIIG), feedline, power cables, and Buddistick down to a relative a couple of days before we left NJ.

I set up the radio and initially mounted the antenna on the rear of the rental car, a Mazda 5, which seemed to be a good way to get it up fairly high and also allowed me to toss the counterpoise wire over a low tree branch. (It’s a bit difficult to see, but you can view the counterpose wire just above the bottom of the picture, it’s the very thin wire.) I set up the antenna, configured it for 20m, and checked it with the antenna analyzer, where I found that I had excellent SWR at my intended operating frequency of 14.260Mhz (one of the standard IOTA frequencies). I connected the antenna to the feedline, and used the built-in SWR testing in the radio to ensure that the SWR was still good (it was), found that my intended frequency was unoccupied, and started to call CQ. That’s when I discovered that I had a pretty serious problem.

The problem was that when I keyed the radio and called CQ, I could hear a lot of what sounded like RF feedback in the headset. My assumption was that for some reason, the transmitted signal from the transmitted signal from the radio was being fed back into the radio, and causing the noise that I was hearing in my headset. As it turned out, I was wrong about the source of the problem, but I didn’t find that out for another 24 hours. Working on that initial assumption, I tried to move the antenna to a slightly different location on the car, and even tried to use the very small Buddistick tripod to place the antenna on the ground much farther away from the car, but had no success. (By the way, that’s a wonderful little tripod, but it’s really not designed to work on a concrete parking lot surface where you can neither dig the legs in nor secure it to anything. All it took was a tiny breeze to knock over the antenna. Fortunately, no damage was done to the whip antenna, but I’ll be a bit more careful about trying that again.)

At that point, I had to take a break from troubleshooting to join a conference call at work. (Yes, even though I was on vacation.) After the call and a follow-up call, about 90 minutes had passed. I tried a few more attempts to play with the radial height, move the location of the radio, and to create an RF choke by coiling some feedline at the feedpoint of the antenna, but was still having no success. I decided to try to find another operating location, hoping to find a park where I could mount the antenna on a picnic table much farther away from the radio, hoping that any RF problems coming from the antenna would be significantly reduced by the distance. I looked at the GPS I’d brought with me and it appear to show a park farther south on the island, so I put all the gear in the car, and headed south.

The saga continues in Part II.

David Kozinn, K2DBK, is a regular contributor to AmateurRadio.com and writes from New Jersey, USA. Contact him at [email protected].

Who owns the single operator all band low power record? Is 60 million points possible for a multi-multi station? Who will log 1,528 prefixes or more this weekend?

It’s aggro prefix time for high frequency airwaves and operators are transmitting unusual prefixes from their callsign quivers. Everyone is a multiplier. It is important to listen first after clicking that flash spot before pushing to talk.

No one likes a busted call when log adjudication rolls around. One pays a penalty in points, ouch, especially when operators are chasing records or looking to establish a personal best.

Rules (link).

Have fun, double check receiver filter settings, check audio, and listen first. Everyone likes a clean log.

Contest on!

Scot Morrison, KA3DRR, is a regular contributor to AmateurRadio.com and writes from California, USA.

We’ve managed to cobble together another round table discussion for Episode #034 of Linux in the HAM Shack. Thanks to Lord Drachenblut of Ten Buck Review and our party crasher, Jonathan, KB1KIX, for helping us out with this episode.

The format is a little bit different this time based on some feedback from listeners. If you like what you hear or would rather have us go back to the way things were, let us know. We’re interested in what you think. Our topic tonight is a thought provoking e-mail that we received before last episode from Jim, N2ENN. Hopefully we’ve given it an honest appraisal.

Please send us your feedback, your questions and your donations to obtain a noise gate for Richard. Also, enter our two contests for a chance to win real money! And stay tuned for our next recording. We have a very special guest interview coming up. You won’t want to miss it.

73 from the LHS Guys

Russ Woodman, K5TUX, co-hosts the Linux in the Ham Shack podcast which is available for download in both MP3 and OGG audio format. Contact him at [email protected].

This isn’t original, though I’ve edited it a bit. It was sent to me as one of those chain emails, so my apologies if you have already seen it. But I thought it was so true, I just had to share it. I think everyone should read it.

To all who were born in the 1930s, ’40s, ’50s and 60s!

We were born to mothers who smoked or drank while they carried us and lived in houses full of asbestos. They took aspirin, ate blue cheese, raw egg products, bacon and processed meat, tuna from a can, and didn’t get tested for diabetes or cervical cancer.

Our baby cots were covered with bright coloured lead-based paints. We had no childproof lids on medicine bottles, doors or cabinets. We rode in cars with no seat belts or air bags. We rode our bikes without helmets or shoes.

The shops closed at 5pm and didn’t open on Sundays, but we didn’t starve! Our only take away food was fish and chips – no pizza shops, Burger King or McDonald’s. We ate crisps with salt in them, white bread with real butter, drank full cream milk and soft drinks with sugar in them, but we weren’t overweight because we were always outside playing!

We rode bikes or walked to school and didn’t get abducted. Our teachers would hit us with canes and gym shoes and bullies ruled the playground. It didn’t harm us.

When we wanted our friends we would just walk or ride round there and yell for them. No one was able to reach us all day. We would leave home in the morning and play all day, as long as we were back when the streetlights came on.

We collected old drink bottles and cashed them in at the corner store to buy toffees, gobstoppers, bubblegum and bangers to blow up frogs with. We would spend hours building go-karts out of old prams and then ride down the hill, only to find out we had no brakes. We built tree houses and dens and played in river beds with matchbox cars. We were given air guns and catapults for our birthdays. We fell out of trees, got cut and dirty, broke bones and teeth and there were no lawsuits from these accidents.

We did not have Playstations, Nintendo Wii, X-boxes, no video games at all, no 999 channels on satellite TV, no video/dvd movies, no mobile phones, no personal computers, no Internet, no Internet chat rooms. When we wanted to make friends we went outside and found them!

We had freedom, failure, success and responsibility and we learned how to deal with it. And you are one of them. Congratulations for surviving despite so many difficulties!

Julian Moss, G4ILO, is a regular contributor to AmateurRadio.com and writes from Cumbria, England. Contact him at [email protected].

Multi Single.

• N5AW | 678 CW | 158 SSB | 197 DXCC | 76 Oblast | 22hr | 1,185,093 Points.

n = 1 score submitted in this category.

Single Operator.

• YT3M (YU2FG) | 1543 CW | 220 DXCC | 232 Oblast | 24hrs | 4,124,952 Points [SKY CC].
• US0HZ | 1270 CW | 174 DXCC | 206 Oblast | 20hrs | 2,967,800 Points.
• S56A | 817 CW | 216 DXCC | 185 Oblast | 18hrs | 2,286,502 Points.

n = 32 scores submitted in this category.

Single Operator Mixed.

• XU7ACY | 865 CW | 60 SSB | 130 DXCC | 157 Oblast | 10hrs | 1,910,846 Points [FRC].
• EI4CF | 296 CW | 449 SSB | 185 DXCC | 140 Oblast | 17hrs | 1,552,984 Points.
• PY2NY | 450 CW | 225 SSB | 130 DXCC | 81 Oblast | 14hrs | 844,844 Points [Araucaria DX].

n = 9 scores submitted in this category.

Congratulations YT3M for leading Club SKY to a first place finish while Team N5AW scored a top slot with heavy metal in the aire! An accomplishment well done from both sides of the Atlantic while XU7ACY rocked the Asian multiplier grid with his stellar CW effort.

Contest on!

Scot Morrison, KA3DRR, is a regular contributor to AmateurRadio.com and writes from California, USA.

Welcome to Handiham World!

Recently we talked a bit about how to put some logic into your decision making when you are comparing equipment or antenna performance. The topic was the venerable A-B test, using a two-way switch that could be connect first one antenna, then another. The idea behind this kind of testing is to eliminate as many variables as possible so that we are really just comparing the two things that we want to compare. After all, using separate transceivers (each one connected to its own antenna) puts into play the extra variable of radio performance when what we really want to do is compare one antenna to another one. It makes much more sense to use a single radio and an A-B switch with the common side connected to a single radio and the switched outputs each connected to separate antennas.

Now I would like to introduce you to another related concept to help you work your way through troubleshooting. It is called a “decision tree”. A decision tree gets its name because it branches out much like a tree. From the main trunk, let’s say there are two large branches. From each of those branches there are two more, and so on. At the base of the tree it is easy to see just the trunk, but high up in the air atop the tree there are thousands of branches. The concept of the branching tree can help us to solve problems with our electronic equipment. Decisions must be made logically and empirically, beginning at one point where the symptom of the problem presents itself and is easy to see, much like the trunk of the tree. Sometimes there may be many, many possible causes for that very same symptom — all of these possible causes are represented by the many branches at the top of the tree. If we look at the top of the tree, we will see a confusing collection of branches, or possible causes to our problem. The idea of the decision tree is to start at the trunk with the most obvious symptom and follow the branches outward and upward until we arrive at the single twig at the top of the tree that is the cause of our problem.

Now, let’s see how this works with a problem that most of us have encountered with our radios.

Let’s say that we go down to the ham shack in the basement and turn on the HF radio. Oddly enough, nothing seems to happen; no sound comes out of the speaker. Of course with a problem like this there can be many possible causes. Putting the idea of the decision tree to work for us can save time and effort as we work our way logically toward a solution to the problem.

1. Did the radio power up?

If the answer is yes, proceed to number two.

If the answer is no, we follow this branch:

Is the power switch in the on position?

If the answer is no, turn on the power switch and your problem is solved.

If the answer is yes, you now have another branch to follow:

Is the radio getting power from the power supply?

If the answer is no, you need to follow another branch:

Is the power supply is turned on?

If the answer is no, turn on the power supply and the power is now available to the radio and you may proceed to operate normally.

If the answer is yes, you are off to the next branch:

Is the power supply plugged into a live AC outlet?

If the answer is no, you need to plug it in or find another outlet that is live, then proceed to operate normally.

If the answer is yes, you need to check the fuse or circuit breaker in the power supply and proceed along a line of determining a problem with the supply rather than the radio.

2. Is the audio gain turned up high enough to hear sound?

If the answer is no, turn up the gain and proceed to operate normally.

If the answer is yes, you are off to the next branch:

Is there any sound at all when you listen closely, such as a weak hiss?

If the answer is no, you will want to follow a line of checking external speaker connections, whether headphones have been left plugged in by mistake, and so on. Several more branches can be followed here – you get the idea.

If the answer is yes, you will want to follow several other branches that will include checking the RF gain control, the antenna connection, any tuners or other accessories in the feedline, and so on.

As you can see, a decision tree can be quite long and branching, even for a simple problem. However, the idea is to begin logically with the things that are easiest to check and most likely to be the cause of the problem. It certainly wouldn’t do to immediately run outside and check the antenna if you didn’t hear sound from the radio. Audio gain controls that are turned down, squelch controls that are turned up too high, RF gain controls that have been turned way down, or an antenna switch that is in the wrong position are all more likely causes of the problem. Furthermore, you wouldn’t want to start working on repairing your transceiver if a circuit breaker in your house’s main breaker box has tripped, causing the outlet into which your power supply is plugged to be dead. It is all about following a logical, thoughtful path in problem solving.

Believe me, this is not something that new ham radio operators — and even some with extra class licenses — always know how to do. Logical troubleshooting is something that can be learned by experience. Sometimes equipment repair manuals include graphical decision trees to help technicians working at the service department proceed through the diagnostic process and a logical and efficient manner. These days, software can help us make decisions as well, but I would like to see our Handiham members be as independent and self-sufficient in troubleshooting basic problems as possible. At the upcoming Minnesota radio camp we will be considering how to solve basic problems in the ham shack. Practicing this skill makes us all more independent and ultimately better operators. After all, amateur radio is a technical activity, and we should be able to do some basic troubleshooting.

For Handiham World, I’m…

Patrick Tice, [email protected]

Pat Tice, WA0TDA, is the manager of HANDI-HAM and a regular contributor to AmateurRadio.com. Contact him at [email protected].