14 Minutes 59 Seconds

The Emcomm debate lives on at the 'zed with this article entitled "READ THE ARTICAL BY WB6NOA IN CQ PAGE 46". It's apparently a pro-Emcomm (and spelling challenged) article, but in this debate I've honestly been disappointed in both sides. ARRL to a large extent created this Emcomm monster and now they're trying to put it back in its cage. The FCC can't seem to send a consistent message and has made some unreasonable interpretations of the rules, like the "you can't do any Emcomm for your employer even if you're off the clock" message. Rational voices with valid points about the questionable usefulness of amateur radio Emcomm in today's world get drowned out by the anti-Emcomm crowd that merely opposes all Emcomm for the sake of opposing it or because it's another way to get a dig in on ARRL.

The Emcomm debate has had its 14 minutes and 59 seconds of fame. It's time to move on. FCC, who cares if someone makes a few bucks while eating donuts and talking on the radio? If someone wants to blow their savings on a Dodge Colt Emcomm mobile, let's laugh at it and move on. Let's acknowledge that there is a place for some Emcomm in amateur radio, but it's not the only or the prime reason for amateur radio today.

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

Handiham World for 27 January 2010

Welcome to Handiham World!

Drawing of guy in hardhat climbing ladder

Heard on the air this morning:

“Nothing like an emergency to find out what works and what doesn’t.”

I had turned on my 2 meter rig, which was tuned to my club’s repeater, and I soon learned that a widespread data outage had occurred in northeastern Minnesota when a fiber optic line was damaged. A bit of web research filled in the story a bit more. The outage began yesterday, January 26, when Qwest fiber optic cables were damaged at a site outside Duluth, Minnesota. A steam pipe in a manhole burst, and the hot gas damaged the fiber optic line. The stations I heard on the repeater were being ported into the Twin Cities via Echolink, thanks to our repeater’s continuous connection to a wide area repeater network serving the area around western Lake Superior, the LSAC, or Lake Superior Amateur Coalition, system of linked repeaters. The stations were discussing what areas might still not have data service, even though it was now Wednesday, January 27. Of course a data outage meant that internet and 9-11 phone service were down. What was the response of a local TV station in the area? Why, to proudly announce that they posted outages and service status reports… on the internet!

By gluing my ear to the radio, I learned from the repeater conversation that the LSAC repeaters kept working throughout the emergency. A fire at an auto body shop happened during the outage, but had been put out safely.

Well, all of this puts me in mind of some basic truths about emergencies:

  1. You never know when they will happen. They are by their nature unexpected in a given moment, even though we understand intellectually that emergencies will happen.
  2. You never know what kind of damage may result or what other problems may be set in motion because of the original failure. There is often collateral damage extending outward along unpredictable paths.
  3. You never know exactly where they will happen. Oh, we may be able to say with some feeling of confidence that our basement ham shack will not flood from a burst dam, because we are on a hill and there is no dam for hundreds of miles, but just as we turn the key in the lock and leave for a week’s vacation a water pipe bursts and we come home to a flood of our own.
  4. The media may not report the incident correctly.

The point is that we just never know. Understanding this does require some knowledge of probabilities, and that in turn helps us to manage the risk.

Take this communications outage, for example. Looking at the three basic truths, we see that it was completely unexpected, happening at a rather inconvenient time. It was the result of another infrastructure problem altogether, since the fiber optic cables would have been just fine if a steam pipe hadn’t burst nearby. Thus, the steam pipe failure constituted the first emergency, and collateral damage to wide area communications quickly followed. There are steam pipes and cables running underground all around the world. Since the underground conduits place these two systems together, and probably also close to high voltage electrical distribution wiring, you can see that a catastrophic failure might well spread to other systems.

Who knew that a steam pipe failure would kill the internet? And 9-11 emergency service? And who could predict exactly where the conjunction of these various types of infrastructure would experience the failure?

Then there is the media. How many times have you listened to a story that has turned out ultimately to have been reported incorrectly? We know when the weatherman is wrong because we can tell when the rain falls and the sun shines, but what about when the media say things that are just not true? The reporters are well-meaning but often no not understand the technology or infrastructure that they are reporting about. This can lead to some rather silly stories making it out onto the air.

Where does amateur radio fit into the picture?

It is obvious to those of us in amateur radio: We provide a communications system that is redundant and separated from other communications infrastructure. There is nothing like redundancy to overcome the first three basic truths of when and where emergencies will happen and what collateral damage may result. Repeater systems can be located at different sites with overlapping coverage. The failure of internet connectivity will not bring down any individual repeater. A repeater that does go down will leave the others up and running. Individual operators will still have their own mobile and fixed stations. Compare that to a system where stream pipes, high voltage power lines, and fiber optic data cables all run in close proximity!

One problem area remains media coverage and perception of amateur radio. In story after story, I keep reading about the “old technology” of amateur radio being pressed into service in one emergency or another. To me, this is like saying that the telephone is old technology. Everyone knows that the phone system incorporates new, cutting-edge technology. The same is true of amateur radio, but somehow the media never seem to understand this. Furthermore, once a perception gets out there, it is hard to erase it. We know that amateur radio is cutting-edge in its new technology, and incorporates digital systems throughout. My suggestion is that you never miss an opportunity to let people know how modern and up to date ham radio is. We have to chip away at the perception that our activity is old-fashioned, a pastime of yesteryear.

Even so, we will be out there – waiting and ready for the next communications emergency.

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].

LHS Episode #032: Screen-Doored Submarines

Well, January has pretty much come and gone. I sure hope the rest of the year sticks around a bit longer. Now that it's 2010, though, Linux in the HAM Shack has a lot of things planned for the future: contests, interviews with fascinating and influential people, trips to live events throughout the year and, as always, scintillating content about Linux and ham shacks.

As of Episode #029, we have achieved more than 50,000 downloads. Episode #029 also turned out to be one of our most popular. When Richard and I started this endeavor back in October 2008 we didn't really know what to expect out of the podcast, but I think it's safe to say that whatever expectations we may have had, we're certainly reaching or exceeding them. I only hope that we only have more room to go up from here. Thank you to everyone who listens to, participates in, or otherwise helps out with the podcast--especially Bill, KA9WKA, our beloved Show Notes compiler, and everyone who has made a donation to the program. We are only about $100 in donations away from our booth at the 2010 Dayton Hamvention and we hope that we'll be able to set up there and say hello to all of our fans, old, new and undiscovered, when it finally rolls around.

But for now, we wish you a speedy download and an enjoyable listen.

73 de Russ and Richard


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].

Old Magazines

As part of a downsizing exercise I'm trying to clean out my shed of most of the QST magazines I have collected over the past 15 years. I was hoping to buy all the QSTs on CD from perhaps 1950 or 1960 to present to replace the paper copies and get several more decades to peruse when I'm an old codger vegetating in one of those assisted dying homes. I figured ARRL would offer the whole kit and kaboodle for perhaps $150 or $200. Going to the website I was dismayed to learn to get just 1995 to present would cost $310. OK, maybe I was a bit unrealistic, but how much does it cost to have an intern burn CDs from the already existing QST PDF database? Looks like I'll continue to have a couple hundred pounds of magazines in my shed for the foreseeable future. Oh well. If I ever lose my job I can use them to heat the house.

I also have a bunch of 73 magazines. No chance of ever getting them CD. NEVER SAY DIE! Not. What CQ magazines I had left I tossed out. I always thought it was a somewhat quirky publication, though I was a 73 fan at the time, so perhaps it was just me that was quirky.

I also found several years of Popular Communications from the 1980s. I loved this magazine when I was a teenager. I was a big pirate radio fan at the time and really enjoyed the spy stories. I almost threw the box out but decided to keep it. It's a window back into a time that we'll never see again when shortwave broadcasting was actually interesting.

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

K3 Weirdness in AFSK-A Mode (SOLVED!)

During the BARTG test I had some weird moments after I QSY’d from 20m to 40m — DM780 would key the K3’s PTT (via HRD IP Server) but there would be no audio into the Line In port, and thus no RF output. Sometimes rebooting the K3 would work, other times quitting and re-launching DM780 did the trick. I’m not 100% certain of the cause but I’m leaning towards software rather than hardware.
Then I noticed low RF output at certain audio frequencies, and this only in AFSK-A reverse (USB) mode; no trouble in normal (LSB) AFSK-A mode, nor in DATA-A normal and reverse. The output power would be OK when the center frequency was set low on the waterfall (+/- 400 Hz, for example) but would drop off at higher Fc setings. And the cutoff point seemed to vary — sometimes I could get full 100W RF out at around 1500 Hz Fc (I typically use 1530 Hz as Fc for RTTY), other times the output would drop above 900 Hz and be effectively zero at 1300 Hz and above. After some messing around with soundcard and line input levels I seemed to have gotten it somewhat sorted out, but as I did all that in the middle of a contest while in semi-panic mode I didn’t take too many notes.
I did some basic tests today by transmitting RTTY diddles at 100W into the MFJ-267 dummy load/wattmeter while in AFSK-A REV mode; mic gain is adjusted for 3 flickering bars of ALC as per the advice of Elecraft. I got full 100W reading on the meter at 2200 Hz Fc, but it steadily decreased as I inched upwards — at 2300 Hz Fc the output was down around 60W, and by 2400 Hz the wattmeter needle barely moved. But when I switched from REV (USB) to NOR (LSB) I get full output right up to the top edge of the waterfall (2900 Hz Fc) — pretty much what I experienced yesterday during the RTTY test.
I then shut the whole system off for a while and repeated these tests an hour or so later to see if things changed from a “cold” state: starting out my output at 2200 Hz was down around 10 to 15W. The output then slowly rises as PA temperature (as measured by the K3’s built-in PA TEMP meter) reaching full 100W at 43 deg C. But after cooling off (PA: 35 deg C, front panel: 32 deg C) power output remains at full 100W! This is driving me absolutely bat-shit crazy.
I’m not really concerned that I won’t be able to transmit RTTY at high center frequencies as my operating style is to find and click on a signal in the waterfall, center it at 1530 Hz, then switch to a narrow filter setting; I’m more troubled by how the cutoff frequency changes, sometimes below 1530 Hz, and apparently is a function of temperature. It doesn’t appear to be a PA problem — the same power drops occur when bypassing the PA unit and running at 10W, and I’m getting full power in all other modes — so I’m going to guess it’s an issue with the DSP board and its handling of audio at the Line In port. More tests to follow, and when I have a better set of test results I’ll contact the boys in Aptos.
Update 26-Jan-2010: I believe it has been solved — the only things I didn’t check until today were the filter parameters in the CONFIG menu. Sure enough, I had FL3 set to 2.4 kHz even though the filter is actually a 2.1 kHz filter. Unsure how or why this caused the problem, but since setting it to the correct setting I am now able to get full output power at the mark frequencies indicated by the K3’s MARK-SH setting (2125, 1445, 1275 or 915 Hz). Not sure how the FL3 parameter got changed; perhaps inadvertently while running K3-EZ, or perhaps it was set improperly during my assembly and setup back in January ’08. In any case, all’s well that ends well. My apologies to Wayne, Eric, Lyle, Don, Greg, etc. for bothering them with what turned out to be user error. I will now sit in the corner wearing my “Dumb Ass” hat as penance.


BARTG Sprint 2010

Spent a few hours Saturday handing out QSO points on 20 and 40. No new ones for me, and I had a hard time working DX. Some weirdness with the K3 (see next post) has me scratching my increasingly balding head…

Summary:
  • QSOs: 65
  • US States: 35
  • VE Provinces: 3
  • Total Mults: 23
  • Total Continents: 3
  • Score: 4,485 pts.
Band-by Band Breakdown:
  • 20m: 40 QSOs, 18 states, 4 provinces, 5 DX
  • 40m: 25 QSOs, 15 states, 5 DX


SOS, XXX, and TTT

Last season while watching Deadliest Catch on Discover Channel, several times I heard the distress call "PON PON". Doing a little research (errr... a Google search) I learned that there are several distress signals beyond the venerable and familiar MAYDAY or SOS:

Distress signal: "MAYDAY" (CW: SOS)
Urgency signal: "PAN PAN" (CW: XXX)
Safety signal: "SECURITE" (CW: TTT)

I'm curious why we don't discuss or support the usage of PAN PAN (XXX) and SECURITE (TTT) in amateur radio?

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

Subscribe FREE to AmateurRadio.com's
Amateur Radio Newsletter

 
We never share your e-mail address.


Do you like to write?
Interesting project to share?
Helpful tips and ideas for other hams?

Submit an article and we will review it for publication on AmateurRadio.com!

Have a ham radio product or service?
Consider advertising on our site.

Are you a reporter covering ham radio?
Find ham radio experts for your story.

How to Set Up a Ham Radio Blog
Get started in less than 15 minutes!


  • Matt W1MST, Managing Editor