31 May 2018

The Russians Are Watching

And so are the Chinese, the Iranians, the North Koreans, and very likely the eeevil Canadians (just joking about the Canadians).


A few days ago the ARRL posted a news item about how Army MARS will require their operators to use computers that are completely disconnected from the internet while running the Data Modem Terminal software during MARS operations. This comment is telling:
"Despite a stand-alone environment, we assume that all computer systems in private citizens' hands are infected with hostile software code of some sort and are not secured," he said. "No amount of virus and malware scanning software changes that assumption. We can, however, isolate computers by disconnecting them from the intentional network in which hostile software will report and receive instruction."
We are in an era where real-time monitoring of your digital radio communications activity is not just possible, but probable given the software you are using and the activity you are supporting.

Think it can't happen to you? Did you ever wonder why the Geek Squad at Best Buy was all but giving Kaspersky anti-virus software away?

We're watching, Comrade!

 W8BYH out

28 May 2018

On Prepping

'Prepping', or preparing for the next disaster or the ultimate apocalypse, is an activity that a lot of Amateur Radio operators (gleefully) participate in. Actually, it's more like the Preppers are participating in Amateur Radio. Either way, there's a huge overlap between ham radio and prepping. I hang out on the margins of this activity because I understand the importance of being prepared for likely disaster situations (note the emphasis on likely). Also, if 23 years in the Army teaches you anything it's to be prepared. And there's no organization better at prepping than the United States Army. It's an obsession with them. Lastly, there's a bit of perverse pleasure that comes from facing a disaster, even a small one like a power outage, with all the supplies and systems in place that allows you to look around your small castle and say, "I've got this".

I read a lot about prepping, follow a few forums devoted to prepping, watch a lot of YouTube videos on prepping and even participate in disaster prepping exercises through my local ARES group. Too much of what you read or see on-line is focused in the wrong direction for the average citizen. It seems most of the 'fantasy' preppers talk about bugging out to some remote retreat where they've tunneled into the side of a mountain, installed biological and radiological filters and blast-proof doors, laid in a 20 year supply of food and water, run hydroponic gardens and have a wonderful time riding out the apocalypse. They actually made a how-to movie about it:


But let's get real. Most of the likely disasters we face will be triggered by Mother Nature - either weather or earthquake. Hurricanes, tornadoes, wildfires, lightning strikes, snow storms or just run-of-the-mill flooding routinely impacts millions each year. Those of you (un)lucky enough to live in southern California face annual wildfire risks, plus every time San Andreas burps you're running into the streets hoping it isn't The Big One.

And then there's the impact of poorly maintained infrastructure. In August 2003 drooping power lines on a residential street in Ohio shorted out on tree branches, causing a generating station in East Lake, Ohio, to go off-line. A cascading series of events ended up shutting down power to huge sections of  New York, Pennsylvania, Ohio, Michigan, New Jersey, Connecticut, Rhode Island and the province of Ontario. Think about it. Some poorly maintained power lines on a residential street ended up cutting power to millions of people across the northeastern US and Canada.

While these are not full apocalypse situations, it shows that the S*** does Hit The Fan more than most people realize, and that it can happen without warning.

So how do you prepare for the most likely scenario you may face? Well rather than blather on and on I'm just going to let Scott Conover, AC2FV from Long Island tell you how it should be done. In May 2016 Scott posted an excellent, easy to watch and easy to follow video on just what it takes to survive a 'likely scenario' event. Using Super Storm Sandy as the defining example, Scott goes through the impact the storm had on Long Island, the survival scenarios it generated and how he mitigated them.

I strongly recommend this video to everyone concerned about prepping, even if you have zero interest in communications or ham radio. It is the most level-headed discussion of the topic of real-world prepping and response that I've seen. Watch and learn:



W8BYH out

26 May 2018

2018 Hurricane Season

Mother Nature's getting an early start. Better batten down the hatches.


To open this interactive web map in a new tab you can click here. The developer, ESRI, is the leading provider of geospatial-based web mapping and they provide this map as a part of their emergency and situational awareness services. It's good stuff. I'd bookmark it... just saying.

W8BYH out

Ham Radio Deluxe

For the past 4 months I've been 'struggling' to figure out Ham Radio Deluxe (HRD). I put 'struggling' into quotes because the struggle always came in 15 or 30 minute blocks when I had time to play with it. But inevitably I'd get frustrated because I always thought that HRD was getting in the way of my operating. I'd rather be on the radio than fiddling with the radio.

But in the past week I found myself with a lot of extra time off from work as I was playing nursemaid to my lovely XYL who had knee replacement surgery (she's doing fine, thank you). I became determined to figure out this program and make a decision to either keep using it or turn to something else.

Ham Radio Deluxe logging window

My motivation for learning HRD ended up being digital modes. I've been an SSB guy since I first got my General ticket over 15 years ago, but I really wanted to give digital modes a try. This was spurred by my interest in emergency communications. As much as I like voice communications I realize that passing messages by voice is a highly error prone process. Some level of expertise in digital communications is necessary if you expect to communicate effectively in times of emergency.

So, I thought I'd start with PSK31 and work up from there. PSK31 is extremely popular, allows keyboard-to-keyboard chats and there's usually someone hanging around the pre-determined frequencies on 80, 40 and 20 meters looking for a contact.

There's a lot of good digital mode software out there, the most famous being Fldigi (for 'fast, light digital'). Fldigi is free software that is maintained by a very talented development group and is something of the standard in digital communications. It is excellent software and is my #1 recommendation for someone looking for a digital mode package. But because Fldigi's focus is just on digital it leaves out a lot of features to support other modes of operation like SSB. I was looking for something more broad-based, something that could support all the modes I was interested in using - SSB, AM, digital and, perhaps some day, CW. I was also looking for an integrated logging program.

By process of elimination I settled on HRD and ponied up the money for an annual subscription. I manage application development for a living so I'm not afraid to pay for good software. I understand the costs involved in the development and maintenance of good software. But on the flip side I also expect a certain level of development and maintenance activity that you don't often find with 'freeware'. The management team at HRD seem to understand this, and they maintain steady progress on bug fixes, feature requests and bringing on new capabilities.

(Time for an aside here, because I know someone is going to bring this up. Several years ago HRD got a bad rap for how it was treating its paying customers. Things came to a head when, out of spite, one of its support staff turned off  several customers access to the software in retaliation for bad reviews. Soon after HRD management was reorganized and the new management team has been working hard at both improving the HRD software and doing damage control. The new HRD is not the old HRD, both from a software and management perspective. Yet reviewers on forums like eHam and QRZ.com continue to bitch about this incident as though it happened yesterday, using it as a tool to bludgeon HRD. To those I say, give it up. It's unwarranted and grossly unfair to the current management team, who are bending over backwards to provide a quality product and support.)

HRD is a program so chock full of variables that it can take days to get it all figured out. But the #1 variable, the one that seems to bedevil most users, is making the proper connection to the radio. This is where HRD excels compared to other programs. The guys who built the rig interface module knew what they were doing. After a few frustrating tries at manually configuring the connection parameters I threw up my hands and tried the 'auto-connect' feature. BINGO - instant connection. The module polls the radio, grabs the necessary connection settings and does the software configuration for you. But this is just to get the radio to talk to the software to control things like frequency and mode settings. Further configurations for digital modes can be a whole other level of frustration, even if your radio (like my IC-7300) has an integrated sound card. This is because proper configuration is a balancing act between your radio, the software and your computer hardware settings. If you use an external soundcard interface like the excellent Signalink things can be even more painfully complex. Only Rube Goldberg could have dreamed up something more twisted.

Why design something simple when it's far more fun to make it overly complex?

But things are not all peachy-keen on the HRD side. The HRD suite reflects its development origins where new modules were 'bolted-on' to a core product. This type of development is very common and is used across the software industry, but if the modules are not integrated from both a function and look and feel perspective the performance and user experience can be a bit rough. We see this in HRD with things like inconsistent menu structures, differences in icon & type styles, etc. as you move from module to module. We also see this as different modules try to compete for the same computer resources like serial ports. It can take developers several software versions to get new functionality fully integrated and matured and the hiccups smoothed out. Here's a hint - it took Microsoft well over a decade to get all the bits and pieces of what we know as Microsoft Office to work together seamlessly and share the same look and feel. The Microsoft Office development team members can be counted in the hundreds. HRD likely has less than a dozen. Given the overall complexity of HRD, the clean-up effort required to bring legacy code up to snuff and the work needed to develop, test and integrate new features I'm willing to give the HRD team time to smooth things out.

OK, back to PSK31. After several hours of tweaking I was finally rewarded with settings on both the radio side and the HRD side that allowed me to transmit a clean PSK31 signal. I happened to get it running just before a busy digital mode contest weekend, so I had lots of opportunities to hone my settings and set up my macros. Once I got things figured out it was like shooting fish in a barrel - see a PSK31 CQ call signal stream in the waterfall, click on it, throw your callsign back and the odds were better than 50/50 that the other station would acknowledge you. Easy peasy. The log filled up fast. But I'm sure for most of you reading this, PSK31 is old news.

A bit of  keyboard chat with KG4ZQY in Brunswick, GA.
I find that the PSK31 baud rate closely matches my touch typing speed, so keyboard-to-keyboard
is actually a lot of fun

But it was while playing with PSK31 that I found perhaps the biggest benefits of HRD:
  • The data mode module talks to the radio configuration module which talks to the rig control module which talks to the logbook module which talks to the callsign lookup module which talks to the DX cluster module which... well, you get it. Everything talks to everything else, fairly seamlessly and quickly. The developers have done a good job integrating the various modules that make up HRD.
  • HRD is stable. It has not frozen or hiccuped even once on the three Windows 10 laptops I've tested it on. Now that's an accomplishment. In the software world stability trumps features every time. I'm glad HRD has focused on stability, even if it's at the expense of bringing on new features.
I now have HRD running on a Panasonic Toughbook with an i5 dual core processor, 16 GB of system memory and plain-jane Intel graphics - good but not great specs for a laptop today. The software just loafs along, gobbling up less than 2% of system resources and plays well with other software packages like Winlink 2000 that demand access to serial ports and other resources.

I can't say if HRD is the best thing going for an integrated ham radio software package. I can say that it works and works well for me. I'll continue to train up on Fldigi simply because that's the standard within the ARES groups I support, but for general use, HRD - and the IC-7300 - makes for a crackerjack setup.

W8BYH out

04 May 2018

Ground Mounted Vertical

For the past two years or so I've been using a vertical HF antenna set manufactured by Chameleon Antenna out of Sparks, Nevada. Chameleon is known for producing well made portable antennas and components and the customer service is outstanding.

The HF antenna I use isn't a single product. Chameleon sells a variety of components that you can use to build an antenna 'system', and what I've cobbled together consists of the the Chameleon Hybrid base - a 5:1 matching transformer - and two vertical whip sections. I normally use a jaw clamp to secure the antenna to a tripod supported mast. This arrangement requires counterpoise wires, and I run three or four counterpoises set out between 40 & 60 feet to help tuning on the lower bands. Chameleon is honest in its literature by stating that most antenna setups will require a tuner or matching unit, but the 5:1 matching transformer should provide a low enough VSWR on all bands that your tuner should have no trouble finding a match. I also find it helpful to place a common mode choke right at the feedpoint to help tame the SWR.

When clamped to the tripod mast and hoisted 8' or so in the air the antenna is a great performer. Chameleon will tell you that with a vertical antenna, height is everything, so the higher you get it in the air the better the performance. As long as the bands cooperate I've had no trouble making contacts all over the eastern US and into the Caribbean. It's not a DX antenna, but for regional communications it works just fine.

The Chameleon in its normal setup, clamped to a tripod mounted mast

Setup can take a little time, and if there's any wind the antenna needs to be guyed for support, but once it's up it is a great performer

The Chameleon vertical makes for a great 'tailgate portable' setup

Recently I was operating at a local park and broke my tripod center pole. This is simply an inexpensive painters pole that slides into the tripod center socket so I wasn't too upset. But I didn't have a spare so it left me without a way to stand up the antenna.

Then I remember that I had a Chameleon ground spike with me. The Chameleon spike is a simple stainless steel spike with a socket threaded to accept the standard 3/8 x 24 mounting bolts used on most portable ham radio antenna bases. The spike is designed specifically to support Chameleon's vertical antenna components but in reality can be used with just about any vertical antenna with a 3/8 x 24 base.



I had purchased the spike over a year ago, looked it over and tossed it into my antenna bag thinking it might come in handy one day. Well, that day had arrived. With a broken tripod there was no other way for me to support this vertical antenna. A few whacks with a mallet and the spike was in the ground. I screwed in the antenna sections, attached the counterpoises, hooked up the coax and hoped for the best.

The spike supporting the Chameleon 5:1 matching unit and vertical sections

I need not have worried - even in this era of lousy band conditions this setup got me in to NW Ohio and Maryland up near Baltimore on 40 meters. In fact, it was 'Ohio NVIS Test Day' and I was talking to folks around Columbus and Dayton on their NVIS setups with no problem - from well south of Atlanta.

The antenna setup using the Chameleon capacitance hat, which isn't a true 'cap-hat',
but it makes the antenna a little more broad-banded on the lower frequencies

I was also able to make connections to Winlink nodes on 40 meters up to 490 miles away. Overall I was quite pleased with the setup. Yes, I'm sure it would have performed better mounted to the tripod and hoisted up 8 feet or so, but you have to work with what you have, and this was all I had, and it worked!


Making connections to Winlink nodes as far away as Pennsylvania was no problem. Notice the vertical antenna
peeking up just over the Signalink unit


Chameleon vertical on the right, radio on the left. A beautiful, cool day. A great location. Radios.
What more can you ask for?

Would I ever deliberately choose this ground spike setup over a tripod mounted setup? No, but it does provide a means to get on the air quickly. With practice I'm sure I could have this antenna combination set up and and on the air in under 10 minutes. If you are working an emergency communications scenario where you need to get a minimal communications capability on the air fast to buy time to set up a more robust antenna configuration, this spike/vertical combo is ideal.

W8BYH out

29 April 2018

Can It Take A Licking and Keep On Ticking?

Or, is it possible to find a laptop that can take a bit of real-world abuse in the rugged outdoors but not break the bank?

Ever break a laptop? Ask most heavy users of laptops and the answer will be yes (if they are honest). I'm in that august group, with no less than four broken units in my 25 years of laptop use. I know that's not a record. I've worked with folks who averaged one broken laptop every two years. At some point you begin to suspect it's intentional.

Not mine, but you get the idea

There's a reason organizations like the US military and police and fire departments spend big bucks for ruggedized laptops like Panasonic Toughbooks. These laptops get used and abused in ways most folks can't even imagine. Like being used as a coffee cup stand in a HMMWV somewhere in Afghanistan.

Most American taxpayers can't afford the entry price for a Panasonic Toughbook or its Dell equivalent (about $3,000, with middling performance specs). To be honest, very few need what a Toughbook offers, like the ability to keep working while being dragged around behind an ATV. But many users do need something in the middle - a laptop that is built into a rugged chassis that can take some real world knocks, bumps and a light shower without begging for mercy or just giving up the ghost without bothering to say goodbye.

Two very capable laptops that wouldn't survive a weekend trip to the mountains.
The Surface Pro 4 (left) is a replacement for one that suffered a shattered screen after a fall from 2.5 feet
 while in a heavily padded case.
The Acer (right) is a very capable laptop and a PC Magazine award winner, but the case is so flimsy that the trackpad
has gone 'wonky' and one of the USB ports has died.

But what does 'in the middle' mean? Well as interpreted by both Panasonic and Dell that means a laptop that has a rugged build but lacks the full MILSPEC rating for shock, dust and water resistance. These 'middle ground' laptops are built around a magnesium chassis, offer covered (but not necessary fully sealed) ports, sealed keyboards and rugged displays that are readable in full sunlight. Generally they are rated at the IP 51 or 53 levels for splash and dust resistance. An additional important consideration is that users can actually use them for day-to-day computing tasks. If you've ever tried to type on something like a Panasonic Toughbook CF-31 you'll quickly understand. It's like trying to type on a brick. These 'middle ground' laptops have keyboards and trackpads that are actually comfortable to use.

A number of manufacturers besides Panasonic and Dell offer beefed-up laptops. Lenovo and Dell offer units that are designed to survive a little rough handling in office or school environments. (My wife's school just bought a load of Dell Chromebooks for student use that seem to be built to the higher end Precision specs. Good idea, given how little regard most kids today seem to have for other people's property). But these laptops are not really designed for use out-of-doors in the elements, or to survive repeated rough handling.

A few years back I needed a new work laptop and after some searching settled on an Acer Aspire. This laptop has great specs and was a 2016 PC Magazine award winner in the low cost laptop category. What made it 'low cost' is the build quality. While not cheaply made, it's clear Acer reached the price point by sacrificing a sturdier build. The laptop is, to be generous, flimsy. For the first 18 months of use this wasn't a problem. But over time, with being schlepped back and forth to work, taken in and out of meetings, being used for demos and presentations, etc. the wear and tear began to take a toll. Now the trackpad suffers from the classic 'randomly wandering pointer' syndrome, one of the USB ports is intermittent and the keys have developed a mushy feel.

One day last year I took it on a mini DX-pedition to a local park to use it to drive my radio on digital modes. While operating at the outdoor site and watching all the spring pollen, dust and grass being kicked up by the wind I concluded that the time had come to replace the Acer and look for something that could spend a day outdoors without worrying about whether or not it would survive. My requirements weren't too stiff; Amateur radio software really doesn't put much of a strain on a modern system (can you say 'legacy 32 bit code'?). Any new computer would need to run Windows10, sport at least an i5 dual core processor, 8 GB of RAM, a 500 GB hard drive, a sunlight readable screen, have at least an IP51 rating for dust and water protection and be MIL-STD-810 compliant for shock and vibration resistance.

Two companies lead the market in building laptops that meet these standards. As discussed earlier, they are Panasonic with their iconic Toughbook line, and Dell with their 'Rugged' (5414) and 'Tough Rugged' (7414) lines. The Panasonic Toughbooks have been an industry standard for over 20 years. They are the 'go-to' laptops for most federal, state and local emergency response agencies and they have been so dominant in the market that I think they are reflexive purchases for most agency buyers  - you need a rugged laptop just put in an order for a Toughbook. Dell is a johnny-come-lately to the rugged laptop market, but I understand they are gaining traction fast, especially with IT managers who already have corporate accounts with Dell.

Panasonic CF-31 Toughbook.
When you say 'rugged laptop' this is what most people think of

A quick review of both manufacturer's offerings leads to the immediate conclusion that buying one would cause a process server to appear on my porch to hand me divorce papers. Apparently rugged laptops are not cheap to build. The entry point for a new Toughbook with the specs I outline above is somewhere north of $3,000. The same holds true for the Dell line. But there's also a huge market in refurbished models. While factory refurbished Toughbooks can be hard to find (most are third party refurbs), Dell actually does a lot of in-house refurbishments and those units (with full factory warranties) end up on third party vendor sites. In fact, eBay is full of Dell refurbished laptops of all varieties. But which one to buy? As I said before, I don't need a high end gaming machine, just a basic unit with good performance specs. Well it turns out Dell has pulled a Goldilocks on me, offering something 'in the middle' that is just right. Dell's 5414 series laptops sit just below their top-of-the-line military grade rugged laptops (7414 series), but offer just the right amount of performance and protection I'm looking for at a refurbished price level that won't cause divorce papers to magically appear.

The Dell 5414. Just rugged enough.

After haunting eBay for a few weeks I finally found a Dell 5414 that fit my needs. Actually, I did a little better than planned. It seems the rugged laptop market is rapidly moving beyond conventional hard drives and adopting SSD hard drives (it only makes sense - with no moving parts an SSD is inherently more rugged). So I managed to snag a  256 GB SSD model with 16 GB of RAM and a high resolution touchscreen. One of the interesting features of both this Dell and Panasonic Toughbooks is the number of legacy ports these units sport. Apparently the main customer base - emergency response agencies - are still hooking up to some pretty old devices. This Dell 5414 comes with a 9-pin serial port (DB-9), a VGA video port and a CAT5 LAN port. The 9 pin serial port will actually get some use, since there are radios being made (Kenwood TM-D710G for example) that still use a standard 9 pin serial connector. But the laptop also sports a plethora of up-to-date connection ports - USB-2, USB-3, HDMI, SD - lacking only the relatively new USB-C port.

The Dell is festooned with a wide variety of ports. On the opposite side
is another covered bay with two USB-3 ports and an SD card slot

All ports except the charging port and the docking stations connector on the bottom sit in bays with snap open covers. The integrated carrying handle may look goofy, but it's actually quite useful. This is not a light device (about 6.3 lbs!), so having a secure carry handle is critical, and the design does not interfere with typing.

But how about performance? Well, it's got an i5 dual core processor and uses Intel integrated graphics, so its no barn burner. But it's way more than capable enough to handle the ham radio software I run - Winlink, Ham Radio Deluxe, Fldigi, VOACAP, Chirp, RT Systems programming software. And it runs Microsoft Office just fine. With 16 GB of RAM and an SSD hard drive performance is actually quite snappy. The high resolution touch screen works great in full sunlight.

More than enough 'oomph' to run any current Amateur Radio software

So how does it work in the real world? After limited testing I can say, "just great!" Remember, one of this Dell's primary missions is to control radios and associated devices in the field. A quick test run to a local park for some HF & VHF operations showed the laptop fits the role perfectly. The plethora of USB ports makes it possible to simultaneously hook up the CAT control cabling for my Yaesu FT-857 and Signalink sound card modem and connect via USB to a Kenwood TH-D72 radio with a built-in TNC for Winlink operations. This was impossible to do with my old Acer unless I had an external USB hub available. Additionally the legacy DB-9 serial port will allow me to connect to my Kenwood TM-D710 without having to use a USB port as a surrogate serial port.

Operations in the field without having to worry too much about dust, dirt or heavy humidity. Yeah!

Some day I expect most of this connectivity will be handled by Bluetooth, but for now it takes cables and cables need ports, and the Dell 5414 excels in this area.

About half of this spaghetti mess has to connect to a computer

So the Dell becomes the system 'hub' and seems to handle the multiple USB connections with aplomb. Actually, Windows 10 handles the connections, and does it very well. I've rarely had 'connection drama' with the Windows 10 operating system like I used to have with Windows 7 or XP. It just works.

The Dell is slated to become my core laptop for daily Amateur Radio use, replacing the old Acer. But because of its rugged construction I suspect it will also end up being something of a daily work laptop, getting taken into environments that the Surface Pro might not do well in (like construction sites). So I'll report back occasionally to keep the readers updated on how the Dell is performing in the real world running Amateur Radio apps.

73!

W8BYH out

22 April 2018

A Hurricane Post-Mortem

The 2017 hurricane season is on the books as the most extensive, and the most expensive, season on record for the Atlantic and Caribbean basins. Mother Nature cut loose with a series of storms that hit just the right land areas at just the right angle and at just the right intensity to cause catastrophic damage from the Caribbean to well up into the southeastern United States. Two storms in particular, Hurricanes Harvey and Maria, caused widespread damage across the Gulf Coast states and Puerto Rico.

How bad was it? This satellite photo taken on 8 September 2017 shows three storms racked and stacked
 to do damage. Left to right they are Hurricanes Katia, Irma and Jose. The middle storm, Irma, ended up
 stomping up the Florida peninsula and then working its way up into Georgia, clobbering south and western
Georgia (including the Atlanta area) before finally running out of steam somewhere up in Tennessee 

Today we'll talk about one particular storm - Hurricane Maria - and the impact is had on the island of Puerto Rico and the emergency communications lessons learned in the aftermath of the storm. There is a lot of talk in the Amateur Radio community about the desperate calls for Amateur Radio operators, both on the island and here on the mainland, to handle emergency and health and welfare traffic. Amateur Radio operators from across the US ended up deploying to support a wide variety of relief agencies like the American Red Cross, the Salvation Army, FEMA and even the Dept. of Homeland Security. In some cases Amateur Radio operators deployed with just the shirts on their backs and 'fell in' on equipment already in-place, other times they deployed with donated gear. In one well known instance the ARRL partnered with Icom to put together 'package sets' of HF and VHF radios that volunteers organized by the ARRL took on the plane with them into Puerto Rico to support the Red Cross. And in some instances, like the SHARES volunteers that deployed to support the Dept. of Homeland Security, Amateur Radio operators hauled their own personal radio gear down into the disaster area to provide communications interoperability between government and non-government agencies.

Most of the glowing reports of Amateur Radio support are third party and have been filtered through the public relations arms of the various organizations involved - the ARRL, the Red Cross, etc. So of course the stories are positive. But I come from the military, where no holds barred AARs are the norm. The Army dislikes repeating past mistakes, so AARs, particularly small unit AARs, can be brutally honest. So what bothers me is that I've seen only one AAR of any value come out of a communications agency directly involved in relief efforts. This is the after-action report done by the ARRL, and it's quite good in its honesty and recommendations for improvement.

This post was inspired by the fact that the 2018 hurricane season opens in just a month (1 June) and by a very interesting real-time forum discussion between an Amateur Radio operator named Planemaker who deployed to Puerto Rico in October 2017 to support the DHS under the SHARES program, and fellow Amateur Radio operators back on the mainland who were trying to maintain communications with him. The discussion was hosted on the ham radio section of the AR15.com forum - one of the busiest firearms, survival and disaster preparedness forums on the internet. The thread is titled 'Heading to Puerto Rico With My Radio. Wish Me Luck' and runs for seven pages, starting with the Planemaker's announcement that he's been activated and closing with a very comprehensive one-man AAR. You may have some political qualms about reading a forum thread on a pro-gun site, but all the discussions are actually very professional and tightly focused on the conditions and communications challenges on the ground in Puerto Rico, in real time. The AAR comments start on page 6, but the entire thread is worth reading through as it gives a great overview of the daily communications challenges that Planemaker faced. His observations and evaluations all ring true, and they ring true not just for Amatuer Radio operators deploying to austere environments, but for those of us who just need to hunker down and shelter in-place yet keep communications up and running.

I've summarized both Planemaker's comments and some inferences I gleaned from reading through the forum posts. I think these are observations and lessons any emergency communicator can learn from:

1. Digital Modes
  • Winlink proved to be somewhat fragile, mainly because it does not have a weak signal mode. When band conditions were poor, which was about all the time, Winmor (the soundcard interface for Winlink) had a lot of trouble making and maintaining connections. Agencies using PACTOR modems had much greater success utilizing Winlink
  • Fldigi was the standard digital comms software suite, so familiarity with Fldigi was deemed essential
  • Weak signal modes like FT8 and Olivia seemed to be the most reliable way to go for passing short messages, but even those were iffy depending on the time of day and antennas used
  • Unattended digital modes were important. The ability to park the radio on a coordinated frequency and mode and log all activity for off-line review was a huge time and effort saver
2. Antennas
  • No one antenna setup or design worked 100% of the time. Planemaker's team used dipoles, verticals and end-fed wires. All had their pluses and minuses depending on band conditions, location and local RFI (which was a huge problem). In general, vertical antennas were worse, tuned dipoles were best
  • The ability to re-rig and improvise antenna setups was one of the keys to success. If something doesn't work reconfigure and try again, and keep trying until the signal gets through
  • A simple MJF manual tuner became one of the 'hero' pieces of equipment because it could tune just about any antenna it was hooked up to and could be used with any radio
  • An antenna analyzer proved to be a critical piece of gear as it allowed the team to create home-brew antennas and test for resonance before deploying them to communications sites that didn't have tuners available
  • In many cases horizontal NVIS HF setups were the only thing that got the signal from village to village. Puerto Rico has very dissected terrain, so VHF point-to-point without the use of repeaters is virtually impossible. Most repeaters/towers were either heavily damaged or destroyed during the hurricane, and those few that survived where quickly over-saturated with traffic. For many remote towns & villages HF comms via NVIS was the only reliable 'reach-back' system
3. Computers & Software:
  • Arriving on-site to support a disaster is a lousy time to start loading software (like Fldigi), getting it configured and then trying to learn to run it. Make sure your computers have the necessary software installed and configured for the radios you will be using, and make sure you have at least basic knowledge of how the software works before the disaster strikes
  • If you are 'falling in' on an agency-provided computer be aware that the agency may not want your software on their computers, regardless of how mission critical it is. Also, IT personnel or local computer administrators (they guy with the admin password and the authority to make configuration changes on your computer) will likely be hard to find and badly over-worked. Good computer skills are a must
4. Power
  • Power is a precious commodity in disaster situations, and radios (and computers) are useless without power. Planemaker ended up relying on his LIon battery pack and solar charger far more than he thought he would, and he didn't plan for enough solar panel capacity to account for the cloudy conditions in Puerto Rico. Even the response agency sites with 'reliable' generator systems experienced frequent outages due to gas shortages, poor generator maintenance or, in one case, the generator simply disappeared into the island interior
  • There's power, and then there's power. Poorly maintained generators, brownouts, spikes, overloads, shorts and ground faults and unexpected outages played havoc with electrical systems and ended up frying a number of items. If your systems (radio or laptop) can run on DC then use that as much as possible. Otherwise, make sure your critical equipment is shielded from RFI, well grounded and connected to a surge suppressor. Unplug when not in use!
5. Supported Agencies
  • Planemaker was frankly shocked at how 'unready for HF' most federal agencies are, particularly the US military. It seems that federal agencies have moved wholesale to VHF for local comms and SATCOM systems for long haul communications. If there is an HF capability left in the US military force structure, it wasn't to be found in Puerto Rico. This became a critical issue as the available satellite communications circuits were quickly overloaded. The stopgap remedy of putting commercial satellite phones in the hands of elected officials, administrators and other key people also had drawbacks since nobody had phone lists (mayor A couldn't call mayor B for assistance because A didn't have B's phone number). Plus, to make or receive a call the user had to be standing outside with a clear view of the sky. 
  • The Puerto Rico Army National Guard dug out some old HF radios but had no idea how to use them, meaning they had no way to operate on the MARS or SHARES nets that were handling traffic. Planemaker ended up giving classes on HF theory and helping them get these radios back on the air. The bottom line here is, I think, don't expect the US military to have any deep or extensive expertise in HF communications
  • Don't assume a supported agency knows what to do with you once you arrive. Part of your job may be figuring out for yourself where your skills and talent best fit the need
  • Frequency coordination between agencies was virtually non-existent. This left the Amateur Radio operators to figure it out for themselves. Again, don't assume the supported agencies understand their responsibility in this
6. Equipment

We'll leave aside any discussion of specific radio systems. Everything seemed to work from that perspective. Instead we'll focus on specific issues that Planemaker brought up.
  • PACTOR vs. Signalink. The clear winner here was the PACTOR modem. It offered far greater reliability and throughput than the Signalink being driven by Winmor. The downside? Cost - and it's a huge downside
  • Coax. You can never have enough coax, and it needs to be the lightest and thinnest needed to get the job done. And it needs to be pre-made lengths with connectors
  • Connectors and adapters. Like coax, you can never have enough connectors or adapters. In the Amateur Radio world we generally stick with PL-259/SO-239 setups, but if you need to support military or government systems you'll be dealing with NMO, BNC, and a whole soup-sandwich of connector types. Bring lots and lots of connectors. And don't forget about adapters - barrel connectors, BNC-to-PL-259, SMA-to-BNC, 'gender benders', etc. The golden rule is, even if you don't think you'll need it, you will
  • Anderson Power Poles. If your power connections are via Anderson Power Poles then you'll need a way to make new connectors, patch cables, etc. Bring along a bag of connectors and a crimping tool
  • Ferrite and common mode chokes. Most of the field offices Planemaker worked from suffered from crippling RFI, often traced to generator or wiring issues. This will be a common problem in any disaster scenario as most consumer grade generators are poorly grounded/shielded. To get any communications out he ended up having to 'choke' just about all of his power and feed lines.
  • MARS mods. It sounds like Planemaker was a licensed MARS operator or otherwise had authorization to operate on the MARS frequencies (via SHARES perhaps?), but his HF rig did not have the MARS modification installed. If you are going to operate on the MARS frequencies get the mod done before heading out to the disaster zone
  • Corrosion. The high, salty humidity in Puerto Rico played havoc on any unprotected metal in just a matter of weeks. This meant constant maintenance on antenna setups and the near mandatory use of stainless components. While we don't have the high salt issue here in Atlanta, we do have the humidity issue. Check your connectors for corrosion and water intrusion every few months
I think the biggest point I take away from this review is the importance of good digital communications skills. But it also leaves open the question - just what digital modes and software will your supported agency be using (if any)? What this means is, as Planemaker says, you'll need to be 'semper gumby' (always flexible) 😄

So just who is 'Planemaker'? Turns out he's Mike Logan, KM4WUO from Chesapeake, VA. In December 2017 he gave a talk on his experience to the Chesapeake Amateur Radio Emergency Service group. Here's the video. Highly recommended:




W8BYH out