An FM pileup

Last night was a big drill night for us on the Heyworth fire department. We have a large gas terminal located in our fire district. A pipeline runs to a tank farm where fuel products are stored and then loaded onto semi-trailers for transportation to other storage areas, gas stations, or private tanks. We had the terminal owners and three other mutual aid departments participating in the drill.

Communications is almost always a problem when you get that many people on scene. Radio communications become clogged as 10 apparatus arrive on scene. "Where do you want us? Send me this....Can you go here?" These message repeat over and over, all the while the firefighters performing work are unable to get back to command. Why is this a problem? Because everyone wants to hear all traffic, we stay on ONE frequency. You've got 10 trucks and 25+ people all trying to talk on one VHF FM analog frequency.

If only more of our members were hams, maybe we wouldn't have to discuss why talking over other transmissions doesn't work. Or why putting 25 people on a single channel is not a good idea if we expect two-way communications between more than 5 of them! Nothing like a good 'ole FM pileup to make you want to smack your head against the wall. If nothing else, maybe the single command officer trying to work the pileup WHILE managing the event would realize that we need to work differently.

AREDN first site on the air

I've installed the first of what I hope are many AREDN (Amateur Radio Emergency Data Network) mesh nodes. This site is located on a large grain elevator in Heyworth, IL. It's at the 150 foot level, with two yagi antennas. One antenna is pointed north towards Bloomington, and the other is pointed northeast.

I'm still going some testing with the antenna configuration - with guidance from the AREDN group, it looks like I need point both antennas in the same direction to take advantage of how 802.11 works. I wanted to try to reach two distant locations with this node...the better way to do that is to have two nodes with directional antennas - at least that's what I'm going to try next.

The node is made up of a Ubiquiti Rocket M900 node, two RP-SMA to N jumpers, and two yagi antennas. The node is fed with a CAT5E cable that provides Power over Ethernet (POE) up to the node, and data in both directions. This arrangement results in very little loss - there's nearly no coax. 

This site also houses a UHF analog repeater and the KD9AKF D-STAR repeater. Using vlan capable switch, I am able to create a connection to the internet from this mesh node. It isn't meant to be a replacement for personal use internet - but having the ability to route to and from the internet means I can access services from either side of the mesh as allowed by amateur Part 97 rules.

What's next? I'm working on two more nodes - one is a portable setup that I'm still experimenting with. I'm going to try a 12 mile link to the top of a parking garage sometime. What's interesting to me is playing in the 900MHz ham allocation. So far, 900MHz for this application behaves much more like microwaves than UHF - it does penetrate some structures and obstructions. 

A getting started guide for AREDN

I'm enjoying experimentation with AREDN. Using off-the-shelf equipment, you can build a mesh IP network running in ham frequency allocations. Getting started is a bit tricky at the moment...I've joined the project team to help with some documentation and to do some release testing. Here's a link to a Getting Started guide I'm working on.

If you're interested in playing with mesh networks, take a look at the guide and let me know what you think!

Getting Started with AREDN

This is a work in progress....some pictures still need to be added. Let me know your feedback!

You've read enough of the documentation about AREDN that you're ready to give amateur radio mesh networking a shot! Well welcome aboard! This guide will give you some basic information about getting your first nodes up and running. There are a number of links in the contents below. Please read them all...they are all important!

Using COTS with AREDN

I've always been fascinated with wireless communications. I'm the kid that had all of the CB radio walkie-talkies torn apart on the toy room floor. Last year I really got hooked on QRP...I've made a number of 5W CW contacts, along with tons of 5W PSK31 QSOs. My latest adventure involves these two new acronyms - COTS and AREDN.

COTS stands for Commercial Off-the-Shelf equipment. And AREDN stands for Amateur Radio Emergency Data Network. I'm taking network equipment that was designed for commercial use in the 900MHz, 2.4GHz, and 5GHz bands and using it with a different firmware set on our US amateur radio frequency allocations. 

AREDN is the new kid on the block in this arena...a group of developers that had been working the the Broadband-Hamnet/HSMM-Mesh team started off on their own. They are developing some features that aimed at improving the manageability, stability, and flexibility of a mesh data network built using Ubiquity Networks COTS gear. 

My fellow Central IL ham friends and I have just completed a successful installation of the WX9WX Raspberry PI based D-STAR repeater. While doing this install, I found two very large 800-900MHZ antennas abandoned by Nextel. I have this disease...I can't let an antenna lay around unterminated. So I'm off on my next quest to build a data network using the AREDN firmware, focused initially on a 900MHz backbone. 

So far? So good. Flashing the first device was a piece of cake. Another ebay purchase yielded some nice 900MHz yagi antennas, and another has another device on the way. This should be fun! Stay tuned!