Emergency Minnesota

 Amateur Radio Disaster Data Network

Just after 9/11/01, some of the 11,000 FCC licensed volunteer Amateur Radio operators in Minnesota decided they could build a radio based data network covering our region.  This network would provide a reliable backup email and data capability to support them in the event of an emergency that disabled or overloaded normal communications channels.  We passed the hat and collected enough funds and donated equipment to complete the first phase of the network using AX.25 packet radio technology, which has been running to commercial reliability standards since 2002.  See the packet network maps and news section at the bottom of the site. 

In order to provide high capacity, easy to use volunteer emergency communications services, we have built with our own funds and are now making available for general Amateur use the second phase of our new D-Star 90+ kilobit TCP/IP data network.  This technology, which supports web based emergency computer applications, moves Amateur Radio back to where the FCC Part 97 rules say we belong- advancing the state of the radio art. 

Our organization is dedicated to improving emergency communications and helping agencies and volunteer groups around the world be the best they can be using start of the art technology and dedicated, experienced volunteers from the Amateur Radio Service. 

Our latest talk is available here: http://www.slideshare.net/ny9d/network1j

D-Star Amateur Radio Repeater List Twin Cities Metro 12/15/09

1. KC0TQI  East Ramsey County, 250' AGL 1.2 DD   1299.000 - MNSTP - Sponsored by Twinslan/Mining ARC etc   - 172.16.0.20/24 is the web/Citadel server- DV 1285.100-    (DHCP)

2. WD0HWT Minneapolis South/MSP Airport/MOA  - 200'AGL - - 1298.000   DD only 172.16.1.1 is the repeater, 172.16.1.20 is the Citadel server (255.255.255.0)     *Note this system is not owned or financially supported by the MARA.  (+ DHCP)

3. KE8TX 1251.000 DD 172.16.2.1 Minneapolis Downtown East - 400' AGL - Excellent range so far - thanks Roger and Peter and folks from HC Mobile Corps + Dan Skripka and Doug Reed+ Max - web server on .20 (Mask 255.255.255.0) Emergency power + DHCP.   Citadel on .20- the router is offline 10/4/09- the repeater is up

4. 1299.300 DD WB0ZKB3-  Minneapolis Downtown NE - Sponsored by Greg K and Alan + DV which we tested 6/22/08 - DHCP

5. NY9D 1249.000 New DD/packet Gateway STPONE - Downtown St. Paul #1 Site - *UP* 9/19/08  172.16.4.1 and 172.16.4.20 (255.255.255.0) + DHCP Packet on 145.01.  Citadel users on packet can leave messages for D-Star users and visa versa.   Max is about to deploy a packet command line interface for D-Star ID1 users.  

6. K0FVF West Metro/Golden Valley  (note:  440 voice is pretty active).   *440 Net now Sundays 9PM local time...use CQCQCQ in your radio for "your" call and K0FVF for Rptr1
145.150 K0FVF  On the air *shared pair- switches to space shuttle audio when that is up
442.900  K0FVF- DV
Sponsored by Greg Kitchak N0GEF

7. U of M- Moos Tower Minneapolis

443.425 +  W0YC   DV  -Run by the Gopher ARC.  Has a Gateway.   Reported to be having some 440 input issues. 

8. Anoka Radio Club/Bakken Club

On the air 443.775 as of 12/11/09 at the Bakken site- Mounds View.  W0ANA  B   (two spaces)

Good coverage North and West

9. 12??.?? DD Portable repeater owned by Alan

10. 12??.?? DD Portable repeater owned by Greg

Minnesota D-Star Emergency Data Network News

3/13/10:  There are rumblings of radio spectrum re-allocations in the works.  The only good news here is most of what we are doing technology and process wise here can be moved if we have to.  One email newsletter report of FCC activities suggested that "inefficiently used government spectrum might be made available" - hmmm one wonders who might have lightly used UHF and up spectrum and be running a lot of old technology. 

3/13/10:  Well we learned the used first generation D-Star repeater we thought was available has been sold- it's in Florida.  We need a new plan- such as the purchase of a controller to start a new repeater or the 440 module for STPONE. 

The D-Star meeting morphed into a discussion of the new Minneapolis Marathon. This event has already been successful for us- we have been advised to attend the FEMA 200 and 700 ICS classes online and the 300 and 400 classes in person, in order to develop an incident action plan.  One of these is being used for the MN State Fair as an example. 

The plan for the Minneapolis Marathon is looking like:

1. One Amateur tactical radio net for operators in yellow shirts every mile and at aid aid stations

2. (New) a net at area hospitals for tracking the location of our runners (mostly a practice for the stations there)

3. A rented radio medical network for all the various agencies and volunteer groups (i.e. bike medics)

We have been requested to provide support and mentors for new hams who might be out for the first time in a real event. 

3/5/10: Tomorrow (3/6/10) @12 Noon we have a D-Star User's Group meeting at Radio City in Mounds View. All are welcome.

2/25/10: Amateur Radio has been requested to support Team Ortho and the Minneapolis Marathon by the Race Director and Medical Director.  This race will include 8000 runners in a 5K, 1/2 and full Marathon on June 6, 2010.  The course starts in the area of the Guthrie Theater and goes down to the Airport and back along the river.  We will likely deploy operators in yellow shirts every mile and at aid stations.  One voice repeater and backup would be used.  We will offer to set up a multi agency dispatch and command center.  We are in range of three of our high speed data systems and will try to deploy some of the large medical vans. 

http://www.teamortho.us/

2/21/10: There was a significant fiber optic cable cut in the Duluth, MN area 1/26- it lasted up to 12 hours. 

 http://minnesota.publicradio.org/display/web/2010/02/19/duluth-communications/

We do have a dual, redundant packet radio data link Twin Cities to Duluth on 145.01 MHz and 145.67 MHz which does not by design use any common carrier facilities.  This work was done after 9/11/01 with support from the MN Department of Health and MN DNR.  We also continue to resist strident calls to use the Internet as backup to the Internet ( Internet services were down in the area as I understand it)  and would be open to upgrading any of our long haul links to 100 kilobit speeds. 

Our advice for cable cut/phone outages:

1. Get on your local repeater and figure out the size of the outage.

2. Small ones can be reported locally

3. County wide and larger outages can be reported to your ARES/RACES county level emergency officials

4. Large outages should probably be reported to the State Duty Officer.  You do not have to reach them via the shortest path.  A message can be relayed.  We need to develop a protocol to minimize hoax messages here.  One idea is a pre-arranged set of message sequence numbers that can be delivered with the message.  This would be used to authenticate the sender. 

1/20/10: The folks in charge of the renamed US Military Auxiliary Radio System (MARS) seem to share our view on the complete folly of using the Internet as a backup to the Internet.  In the ARRL Letter it is reported that the document renaming the service includes the following instruction: "MARS must also be capable of operation in "radio only" modes -- without landlines or the Internet" 

1/9/10: We are working on our Network Strategic Plan.  Some highlights:

- Good, overlapping high speed data coverage inside the 494/694 ring is in place now

- Plan to add more repeaters in Washington and Dakota counties as well as down by the National Weather Service

- 440 at St Paul #1

- TwinsLAN might invest in a used Generation One repeater- we have a little funding ($500) left over we just discovered

- Get a 2 meter D-Star machine up - we have a frequency pair available

- We are re-focusing on repeater controller linking, via some newer 802.11 equipment + dishes

- We might decide to only keep two core repeaters off the linked backbone - one for each side of the Metro Area

- There is strong interest by served agencies in ICS/HICS message formats which our equipment supports

- Our strategic open source mail, messaging and conferencing package, Citadel, supports a wiki, which is ideal for ad-hoc incident support

- We got a report of a large Amateur Radio supported event that was expecting VoIP /SIP expertise, which we have

12/22/09:  The new Anoka /Bakken D-Star repeater in Mounds View, MN reinforces our Statewide Network Strategic Plan.  The idea is there is an inner core network of seven powerful, non linked, non Internet D-Star DD nodes that is secure and resistant to remote hacking and jamming.  An outer ring of linked, Internet connected nodes can be used for routine operations and is fun to chat on, work DX etc.  The existing AX.25 packet network (also non Internet connected) would be used for long haul data traffic such as Twin Cities-Duluth and Twin Cities-Fargo until we can get a technology upgrade. 

12/19/09: We heard the newest  argument against D-Star.  The idea is that when the current generation of VHF/UHF digital commercial equipment becomes surplus in a few years D-Star would not be compatible with it.  Huh?

11/21/09: We have been offered the exclusive use of two 180 foot commercial towers - one in Hampton, south of St. Paul on the way to Rochester, and one midway between Rochester and Mankato in Medford.   These could be used for a nice packet, D-Star or voice radio link Twin Cites/Rochester and Rochester/Mankato, which does not exist today.  We are not interested in funding any more corridor projects ourselves, as this one would would involve one time costs of $1000/tower and about $680/tower in annual operating costs.  So if a funding/sponsorship source came forward we could project manage the installation.

10/24/09: As the long time organizers of a major all-volunteer Amateur Radio led emergency services event here in Minnesota, we are not impressed by any of the arguments being made recently to allow paid employees to use amateur radio services on behalf of their employers. 

10/22/09: We want to congratulate Illinois Amateur Operators who have established a brand new relationship with the Chicago Marathon.  75 Hams helped out at the 2009 race.  We gave a talk in Chicago in 2008 describing how good a fit there can be between volunteer race medical teams and volunteer radio operators.    A Race Director we know says there is widespread recognition in his community of the training and experience and dedication we bring to the events. 

10/21/09: We were saddened to read of the deaths of 3 half-marathon runners at the Detroit Marathon.  Detroit is about a 2000 runner Marathon not 19,000 as reported in the press. 

10/4/2009: The 2009 Medtronic Twin Cities Marathon was another big success.  We had more than 120 Amateur Radio volunteers participating, supporting medical communications.  The weather was good for running- in the 50s, which is ideal for a low injury rate.  We ran on 100% D-star DD mode for the data for 2009, (+ some FCC Part 15/802.11G) and had the usual 7 concurrent FM VHF/UHF voice nets.   All event medical assets were on directed nets on a range of radio services run by trained volunteer radio operators from the Twin Cities Amateur Radio Service. 

On the Shakopee Mdewakanton Sioux Community Mobile Unit we used a 1.2G NMO antenna and 70 feet of RG58 feedline on the 50 foot tower here for D-Star 100kbps data access as our STPONE repeater site was about a mile away @270 feet.  Even in this low lying location the van could hit three of our data repeaters.  This illustrates the value of a decent tower on these types of vehicles.  Rooftop only VHF/UHF radio antennas in a "lights out" or rural emergency situation have a limited range. 

Alan in the mobile - note the 4-screen course video (3 + a TV feed in this shot) - above is the new IC-7000 and ID-1

A status screen from KD8GBLs TRIVNETDB V2.1 from the Family Medical Information Tent during the race.  Zero end user training is required.  At the finish line, the 100 yard link from the laptops to the data trailer is via 802.11G (FCC part 15) so unlicensed community volunteers can be used for data entry and query operations without control operator supervision.  Note we are not using text messaging per se - the application is based on Mysql, php and Apache

The word "Mass" in a Mass Casualty Incident refers to scale.  Our use of D-Star and 802.11G allows the rapid expansion of capacity.  Kelly Black, KB0GBJ, (yellow shirt) led the Family Medical Information Tent team in 2009.  Each operator has access to our web based runner information system, that tracks the location of dropped out or possibly injured runners to assist family members.  One of the laptops has a commercial "aircard" to access the Internet for Marathon Web Site access.  We have learned that mixing Internet and Ham Radio traffic on the same radio data network is not ideal.

We have retired AX.25 from even a backup role in the event- note the two 10 watt D-Star ID-1 uplinks in the data trailer- we had four remote ID-1 stations coming in via two of our rooftop RP-1D "repeaters"  to the server.  We did test the use of multiple laptops on a single remote ID-1 via the RP-1D.   You need a dedicated LAN segment- do not share traffic with other services- the ID-1 will attempt to put all Ethernet frames it hears on the RF link.  All data traffic is monitored and supervised in the trailer.

We are using all Cisco (mostly borrowed) commercial 802.11G/Part 15 gear.  We have seen a 100% failure rate under real outdoor and high data traffic/ambient RF conditions of consumer grade 802.11 access points and dislike low budget/low power notebook adapters.  We have a firm policy to only allow FCC Type Accepted equipment + legal power levels in our networks. 

 

Note the donated former microwave link trailer in the foreground is back to all microwave for data.  2x 802.11g antennas and 2x D-Star L-Band antennas are on the 65 foot tower.  In the background is the antenna array for the Medical Communications Center.  Given what is at stake we have extensive redundancy in all systems. 

Paul, K0LAV manages the finish line assets, the Inter-Agency Medical Comm Center and has carried the primary event /course emergency phone for the last four years. 

We use our in place, redundant repeater/data nodes on race day.  Having five-way sparing allows multiple concurrent failure survivability and significant surge capacity.  Our policy is to have minimum three-way redundancy. 

 

9/20/09:  From Randy Donahue – WB0ZSO:  We purchased a new D-Star repeater to put up in place of the analog system we have now in Slayton, MN (146.79).   It's on the air from his latest report. 

News: 9/9/09: A new mobile asset is being tested for a finish line medical command and control role at the Marathon in our organization.  We are adding a D-Star ID-1, IC-7000, 802.11g links and using the impressive onboard array of 7 video cameras, including two wireless remote cameras. 

 

Jim from Shakopee Mdewakanton gives our team the briefing on the various systems aboard - right before we started rewiring his vehicle.

We have spread the word that a well equipped Emergency Communications Van in Minnesota needs an ID-1 for high speed data network support. 

News: 9/7/09: We are getting ready for a final meeting to test some new software releases before the Marathon.  And we are working on our long delayed site linking project.  An article has been accepted on the Mining ARC DD mode scoring demonstration described below.

News: 9/6/09: One of the largest hospitals in our area, and a leading trauma center, HCMC, will be ordering equipment for our network. 

News: 8/31/09

Wayne Green, W2NSD, who ran the magazine "73 Amateur Radio Today" used to publish an annual report card on the American Radio Relay League. We talked to Wayne about carrying on some of his traditions and ideas- he said we should strike out on our own.  This is one we are going to revive.  The high percentage of uncontested board elections lately indicates any pressure for change needs to come from external sources. 

Our 2008 ARRL Board of Directors Report Card

FCC - A

Mr. Hollingsworth was fabulous and things seem to be off to a good start under the new leadership.  The BPL battle is going well. 

Historical Preservation - A

Every past word and deed has been lovingly captured in print, and from the looks of our basements, so has every piece of equipment ever used as well.

Technology - F

There is not a word in FCC Part 97 encouraging the use of legacy operating modes- they are permitted, but right in the preamble it says we are supposed to "advance the state of the radio art" - this problem, if not fixed, is very serious.

Emergency Communications - D

We are not named in the National Disaster Plan - why not?   Are we getting in the game enough on ICS/NIMS?  Is there a role for legacy technology in modern EmComm?  Are we regularly impressing served agencies with our advanced capabilities and training as FCC Part 97 says we are supposed to? 

Youth – C-

Lots of effort here, but how cool is 30-50 year old radio technology really?

Member Services - A

Given limited resources, could some energy be redirected to other areas?

Public Relations - D

The unaided awareness of the concept of Amateur Radio is falling in the general population. 

 

News: 8/23/09: The Mining ARC used two ID-1 radios and laptops to report rowing race results from the middle of a lake to shore.  You set up static IP addresses in the same subnet (and the same mask) on two laptops, and set the radios up with dis-similar callsigns in DD (simplex) mode.  The ID1s make powerful, stable long range Ethernet bridges.  The software used was the free NetMeeting that is packaged with Windows XP.  Note the ID-1 does not have an IP address. 

 

News: 8/13/09: At the request of the Mining ARC, we tested Microsoft NetMeeting on Windows XP Professional laptops connected by Icom ID-1s.  The microphones must be muted as the audio traffic (lots of small packets) works poorly in DD mode (which is half duplex) and saturates the RF link.  The white board and chat worked well.  NetMeeting is included free with some versions of Microsoft Windows(r) like XP Professional.  The other benefit of this software is not having to train operators, as many people use it at work.  Thanks to Ed, WB0VHF for the idea and equipment. 

News: 8/13/09:  Those interested in volunteering for the Medtronic Twin Cities Marathon as part of our communications operation can sign up online now.  We have our own volunteer category, "Amateur Radio Communications" and should not be part of an "organization" which they ask about. 

http://www.mtcmarathon.org/volunteers/volunteerregistration.cfm

News: 8/1/09:

Packet & Radio Workshop Sunday, Aug 2, 2009 at 9am to 5pm:

1710 N Douglas Dr, Suite 285

Golden Valley, MN 55422

Call on 146.520 for entry or the phone number on the door.

 

We will be working on D-STAR and packet. We'll be willing to help on whatever other projects you have. We're getting fairly late in the year and have a lot to get done before the Marathon in October.

 

If you are planning to bring a project and may need tools or RF test equipment, send me an email Friday or early Saturday and I'll see what I can do.....

 

My favorite route to get to the location is Hwy 100 to the Duluth St exit. West on Duluth till it ends at Douglas Dr in front of Honeywell.

South on Douglas a little more than a block. Enter the parking lot using the last driveway on the east side before you hit the railroad tracks.

The entrance door is usually locked and we are half the building away, so plan to give a call on 146.520 when you arrive. Kelly hangs a note with the phone number in the door so you can call on your cell phone instead.

 

Doug.

 

News: 7/24/09: We are going to be adding yet another large medical/communications asset for the 2009 Medtronic Twin Cities Marathon.  We are going to integrate D-Star DD mode and our area wide network of four DD mode repeaters into the very high end communications suite they already have installed.   This rig is 84 feet long and has four treatment rooms and a comms center. 

Mobile Unit Photo

News: 7/23/09: John Leeper came through with a number of surplus Compaq N800V laptops to supplement our rapidly aging laptop fleet.  We can now show up with a good number of decent laptops and we have now finished getting rid of all 802.11b cards.   

News: 7/21/09: A DVD of our talk from the 2008 TAPR Conference (almost identical to) Dayton 2009 is on Disk-1 of this set:

http://www.arvideonews.com/dcc2008/

News: 7/11/09: There are reports of a possible sponsor for a new D-Star repeater in the direction of St. Cloud.

News: 6/22/09: We are getting ramped up for the 2009 Medtronic Twin Cities Marathon.  Our team had a meeting today and started in on our project list:

1. We have a new version of our trivnetdb database for down /injured runner tracking - 3.0.  Peter is making some adjustments and we will test it next meeting and also clone it off onto a thin client for demo and training purposes.

2. We need a lead data operator for Net 2.  Kelly is moving to the Finish Line.

3. We need to work on repeater linking- one more try with the Ricochet equipment.  If that does not work we are moving up to Canopy equipment.

4. There is some interest by our Medical team in remote, tower mounted  video cameras to track and locate down runners at the finish line and in the last mile or so.  These are used extensively at the Marine Corps Marathon. 

5. We are working on plan to better integrate personal health records supplied by runners with the medical records in the Medical Tent. The idea is if we see a runner in the tent, we are able to print out the medical record form pre-populated with any available history information. 

6. We are looking for a mobile command center to use for Net 1 - the Hennepin County part of the race. 

News: 5/17/09: We had a chance to speak at the D-Star User's Group in Dayton.  The talk is available (very similar to the one from the DCC/TAPR show this summer) from Amateur Radio Video News www.arvideonews.com

The show was well attended.  There is a lot of interest in the repeater linking feature of D-Star.  More than 420 gateways exist world wide, and there are in excess of 8000 registered gateway users not including Japan, who are running on an older version of the gateway.  We shared a booth with Ed Woodrick WA4YIH from Georgia D-Star Inc.  They have an excellent newsletter. 

http://www.dstarinfo.com/

We talked to the Wisconsin folks, KB9MMA in particular.  We were wondering what happened to the big statewide packet network they had.  It has all moved to RMS, which is a Linux variant of the Winlink2000 program supported by the ARRL  They are still on 145.61.  We have an idea to link our two statewide systems together.

http://www.winlink.org/SysopSoftware

Several areas are deploying large scale high speed data systems, similar to ours.  These area include New Jersey and Houston.  We are going to release our DNAT and other code in an easy to use distribution soon.  We have not wanted to get into the Linux support business. 

News: 5/10/09: We are in the process of establishing friendly relations with yet another State Agency who owns some water towers.  These, as we have written before, are excellent sites for packet nodes, D-Star equipment,  voice repeaters, etc.  We are practicing our "elevator pitch" - a short, pithy mission statement of why we need to put our equipment on their sites.  I think listing the agencies you are supporting and the services you provide (we are a backup for the Pandemic Flu response as an example) is very good.  You need to provide names of references, and the heads of State Agencies are a good start.  You need to be a team player in a larger effort here. 

We own a commercial tower site and were approached by some nice and responsible railroad scanning enthusiasts.  They said they were hobbyists, and wanted tower space for free.  I was completely unmoved and all I could think of were the words "rent" and "insurance."  Just saying you are ham radio operators is no longer enough.   

News: 5/9/09.  Max had completed our demo for Dayton.  He has built web forms you can fill out for essentially all of the ICS templates.  These are picked up and mailed via Citadel behind our D-Star repeaters from Outlook Express (r) on the workstations in the emergency scene.      

News: 5/1/09: It is looking like this strain of H1N1 is "looking like a normal seasonal flu" in the words of one Public Health MD on the radio today.  We need to pat our Public Health Planners on the back here for a good solid response, do a bit of fine tuning of procedures and get ready for the next one, or the next version of this virus.  I think we do not need to go out and borrow more money and increase government funding here, as the next new strain will be as this one is -random and unpredictable, and spending more money now won't change that fact.  We actually need to fund pandemic response a few years from now, when the current stockpile of equipment and medications gets out of date.  

News: 4/26/09: Swine Influenza A (H1N1) has been identified in several US states by the CDC, and there was discussion of the SNS antiviral supply on a press conference today.  

News: 4/24/09: There is a novel type of swine flu in Mexico, that appears to be transmitted between humans. 

http://www.msnbc.msn.com/id/30389150/

News: 4/24/09: We may be expanding into Washington County on an excellent site.  We would add a new repeater stack there, to extend the high speed data coverage to the border with Wisconsin, and also provide East Metro digital voice coverage on 440, and possibly use the site as a hub for a more reliable Twin Cities-Rochester link on packet.  This will require fund raising, as we have a repair reserve only in the bank. 

We have located a water tank in Moorhead for a 145.67 packet node near the State University that would be good also for a temporary 800 MHZ antenna site for visiting mutual aid units in the area.  This was a big issue during the recent floods.  The idea is if a Comm Van from the Twin Cites came up they could "plug in" to a tall water tank antenna for better range.  For some reason, the million dollar emergency communications vans that are being ordered by counties here do not have decent (i.e. tall) antenna masts. 

News: 4/16/09: We are presenting "D-Star and Real World MCI" at the Dayton Hamvention D-Star Forum Friday night, and will be in the Icom booth Friday. 

News: 4/11/09: If you are using Windows Vista (r) or Windows 7 and need an async terminal program, the Airmail (from www.winlink.org) package has one that works great.  Thanks KE6RK. 

News: 4/9/09: We have been invited to staff the Icom booth in Dayton and to work on a program for the D-Star night Friday down there in Dayton

News: 4/5/09: We had four stations on the Sunday D-Star net- 9:00 PM on the K0FVF machine- 442.900.  The next D-Star User's Group is at 11:00 AM Saturday May 2 at Radio City in Mounds View. 

News: 4/5/09: We've changed our minds about D-Star DV mode.  Using the CQCQCQ "your" call, it is about the same amount of work to look up a repeater call sign and enter it in the RPTR memory as it is to put in a PL tone.  So the "extra effort" argument is gone.  Our experience lately with the mode has been very positive.  So we are raising funds to add the 440 modules to more of our site.  We got a new (to us) IC-91A this weekend at Radio City, and added in the DV module.  It works fine. 

News: 3/29/09: Paul, K0LAV our Network Engineering Director is suggesting we put in packet nodes in Staples and Detroit Lakes in order to get our backbone extended to Moorhead.  We are working on the Staples location now.  Packet equipment and an antenna was installed at a hospital in Staples by Jack, W0MBD. 

News: 3/28/09: K0LAV reported four check-ins to the D-Star 440 voice net a week ago Sunday. 

News: 3/24/09: We are calling in our markers to try to get a packet node installed up in the Red River area- the primary users would be the Red Cross, MN DEM and MN Department of Health.  We need a site for a small node cabinet and antenna at 80 feet or more.  We have a few pre staged node packages ready.

News: 3/23/09: There are reports of flooding in the Red River area.  It might be time to push some more links up that way via packet that can be built out to higher speeds later.

News: 3/22/09: Max is reporting progress on putting an ICS 213 message form in Citadel.  He is working on the rest of the ICS forms.  The ARRL Radiogram is important for historical reasons but that is about it, by a reading of FCC Part 97. 

News: 3/12/09: Paul, K0LAV has joined the ranks of 440 D- Star voice users tonight.  We also discovered that my little IC-U82 was not reaching the repeater over in Golden Valley from indoors so I had a high priced scanner.  If you are having D-Star issues, the first place to check is your RF connection and paths.   We again need to get a 440 machine in Ramsey County. 

News: 3/12/09:

After the TwinsLAN meeting is the next

Packet & Radio Workshop Saturday, March 14, 2009 at Noon to 5pm:

1710 N Douglas Dr, Suite 285

Golden Valley, MN 55422

Call on 146.520 for entry.

 

We will be working on D-STAR, linking, IP telephones, and project planning for the year. May even get some packet work done....

 

I'm be bringing an RF analyzer and sig gen to this work party in case you have a packet station to test. There will be plenty of other stuff to work on.....

 

If you are planning to bring a project and may need tools or equipment, send me an email Friday or early Saturday and I'll see what I can do.....

 

My favorite route to get to the location is Hwy 100 to the Duluth St exit. West on Duluth till it ends at Douglas Dr in front of Honeywell.

South on Douglas a little more than a block. Enter the parking lot using the last driveway on the east side before you hit the railroad tracks.

The entrance door is usually locked and we are half the building away, so plan to give a call on 146.520 when you arrive.

 

Doug. (N0NAS)

 

News: 3/10/2009: The next Hamfest in MN is 3/28/09

 

Midwinter Madness Hobby Electronics Show
Robbinsdale ARC
http://www.k0ltc.org
Talk-In: 147.000 +600
 
Contact: Jerry Dorf, N0FWG
PO Box 22613
Robbinsdale, MN 55422
Phone: 763-537-1722
Email: k0ltc@k0ltc.org
 
Buffalo, MN
Buffalo Civic Center
1306 Calder Avenue NE
Div: Dakota
Sect: Minnesota

News: 3/10/2009: The next ARRL/TAPR Digital Communications Conference is in Chicago 9/25-2/09 again.  We have to see if we have some updates to write about

http://www.tapr.org/dcc.html

News: 2/22/09: Our talk on the Minnesota Packet/D-Star network & strategy from the 2008 Chicago TAPR Conference is commercially available on DVD

 http://arvideonews.com/dcc2008/index.html

News: 2/21/2009: Our work session list is growing.  One is in the making soon.  (3/22?)

Build a full time D-Star application gateway to "Safe and Sound" for the Red Cross

Test IP Phone system #1

Test IP Phone system #2 (PBX in a Flash 1.3)

Build a hard disk based Linux appliance running our database + Internet /Intranet gateway -uplink for home /served agency use.  These can have a disk drive vs. flash as you can get to them easily for repairs.  A 17 watt 110V AC appliance is a lot more electric bill friendly than a 65-150 watt desktop computer. 

There are reports from K0LAV who is our Site Engineering Consultant of a linking microwave system being available for $200/end.  The idea is to link Minneapolis South, STPONE and Mining.  One idea is to set up a microwave relay site at the MNMPLS rooftop packet site @300 feet.  The Minneapolis East site would be standalone, as it has a main job of supporting County /State mobile command centers and the Red Cross. 

We need to investigate a new patient care/PHR/bed tracking system for the hospital tent.  This needs to be standalone and HIPAA aware.  It would then feed person location information to the non secure Amateur Radio system.  The Doctors want to have a runner wheeled into the admissions area, have their runner bib barcode scanned and be able to hand back  a sheet of paper with the medical record form pre-populated with personal health record data.   Ideally this would be available on a handheld wireless computer.  This is how the US DoD does battlefield triage. 

Somebody needs to start documenting our operations plans and frequencies in IC 205 format.  John Dooley (MN EOC) gets credit for a way forward here- we were wrapped around the axle on needing forty pages of stuff in a binder but the forms are pretty simple/one page. 

There is a patch or two needed for the 2008 Production Linux/Sun System on the packet side

Need to test live streaming video ("on scene assessment" per one of our agencies) on one of our repeaters.  This *should* work.

Need to test multiple laptops on a switch/hub behind a single ID-1 to a repeater- we do this all day long on 802.11

Test the barcode scanner for patient admissions.

Need to record our systems as "repeaters" with the Minnesota Repeater Council.  Each has a 1.2 DV module.  We can record those to get "in the book"

News: 2/20/09: John Leeper, who is our expert on computer equipment that is otherwise headed to the recycling plant, has hinted we may see a dozen "new to us" laptops.  Our old fleet is severely dragging.  The 146.85 MARA repeater, clearly the crown jewel of Minnesota amateur radio assets, reportedly has no UPS on it right now.  John located a pair of late model, modular UPS systems we should deploy there.  Our best gear needs to be used on our key systems.   

News 2/19/09: We applaud the developers of the new Twin Cities APCO-25 ARMER interoperable public safety radio system.  It worked well during the RNC and 35W bridge collapse.  We are going to disagree professionally with some advice we are getting though from system backers.  There is interest in creating radio caches and handing out the radios to various support and volunteer groups.  In a real emergency, especially a large disaster, this is incorrect practice.  The big trunked systems have a finite number (16, 24, 32 etc) of *shared* radio channels and backbone channels.  If you have an all hands on deck situation, with every police and fire and public works unit out rescuing people, you may have all the channels tied up with that.  Adding a few hundred volunteers will tie up channel/trunk capacity that could be used to save lives.  We use about 3-4 full time Amateur radio channels at the Marathon, with only 120 radio operators and highly experienced control operators on directed nets.   The Marathon also uses five shared/rented commercial UHF repeaters for race operations, and have had trouble with channel capacity on those, (even on a Sunday morning) which has interfered with transportation and logistics work.  The symptom of a full shared repeater is the blocking of transmissions. 

Ad-hoc volunteer activities need to be directed to Amateur Radio, as we have 40 "channels" of UHF/VHF repeaters (and simplex) in the Twin Cities alone.   We are all in favor of training, but the notion of big trunked radio systems and "surge capacity" needs to be looked at from an engineering perspective.

News: 2/18/09: We had a chance to present the system and see a live demo (thanks Don Heppleman) of the STPONE D-Star data machine from the State of Minnesota Emergency Operations Center.  It was interesting to hear from some of the staff there on what they are interested in seeing.  One requested feature is the ability to print out messages.  The idea is if you need 25 sheets of plywood for boarding up storm damage, it is helpful to have on paper the exact size and thickness of the plywood.   We are investigating the notion of adding a form to Citadel to let you enter and print messages is ICS 213 or ARRL Radiogram format.  We got some strong coaching to use ICS forms, like IC 205 to document our plans and frequencies used for events.  This is good advice.  The IC 205 form is pretty easy to use.  We think the State EOC Team in various capacities will be joining us in 2009 for the Marathon. 

We discussed our idea of using phone numbers as the key field for missing persons tracking.  The apparent Federal standard is first name /last name which is fine too.  We are not fond of using Social Security numbers. 

Our local school district last week had 3500 computers and 41 servers infected with the Conflicker virus/worm.  These machines have been offline for more than eight days.  I told our hosts at the State EOC that they would never be getting a call from us that our system (providing backup, when all else fails volunteer emergency communications) had been hacked from the Internet as we do not connect to the Internet or use Windows.    This is what the old computer security orange books called an "air gap."  Those who have been pleading with us to connect to or link to the Internet- we do support very controlled served agency gateways/uplinks that could be used in a dire emergency but that is it.  There are a zillion ways to commercially reach the Internet- we are not one of them. 

Other groups with different mission statements are encouraged to put up Internet linked D-Star systems as that technology is pretty cool.  A ham from Iowa drove up to attend our D-Star User's Group meeting, and is hoping we can get a linked system (using the Icom gateway software) up soon.  Any takers?

News: 2/16/09: We have requested County grant funding for a 440 UHF voice/data D-Star module for our STPONE site.  And we need to start adding more UPS power to several of the sites.  Our primary Minneapolis site has been up more than a year - that is 100% uptime in 2008 for those who are counting. 

News: 2/15/09: There is still some mystery on getting ID-1 radios to talk to our repeaters.  The problems can be traced to RF paths and settings.  Here is a screen shot from this morning, about ten air miles from each of three repeaters.  The beam is pointed at the Mining ARC system, and two other repeaters can be reached off the side lobes of a 24 element beam at 20 feet on 100 feet of LMR-400.  The antenna used is low tech these days- very similar to that used by the 802.11 folks for long hauls. At the top is an MFJ tri band antenna ($99)  (2M/440/1.2) and below that is the beam.  Two systems can be reached from the omni antenna. 

 

 

Note the settings on the bottom screen.  If you don't have multiple connected repeaters via Icom software/gateways/assist ports, RPT2 has to be deselected.  The A/S suffix on RPT1 seems to not matter.  The "Caller" callsign suffix issue bears some investigation.  If you are getting flashes of the *repeater* call sign on your ID-1 screen that is a good sign on the RF path.  172.16.0.20 is the address of the little web server- .20 is our standard for the web/Citadel servers.  Note that address is non routable across the Internet :-). 

  

 

News: 2/14/09: News Flash to Amateur Radio Manufacturers: Direct OEM and retail sales of Microsoft Windows XP ceased on 30 June 2008.  Most new  laptop and desktop computers are equipped with 64 bit microprocessors and do not have serial ports standard.  Windows Vista Beta 1 (5112) was released to TechNet/MSDN users on 7/29/2005.  The final RTM version of Windows Vista was released to MSDN/TechNet subscribers (6000)  on 11/16/2006.  If you still can't get your Windows Vista (64 bit) USB or other drivers to work, you need to hire smarter engineers or go into the wind up toy or t-shirt business. 

News: 2/7/09: We will be starting a Twin Cities D-Star User's Group.  The first meeting is 2/7 at 2PM at Radio City in Mounds View. 

News: 2/1/09: We have a dozen IP/SIP phones on hand, so will be deploying an IP phone system to support the 2009 Marathon.  Ideally, we can use an appliance sized computer, to avoid the space and power drain of a desktop.  We have two flavors of phones- Cisco 7905G (SIP, 48V DC power/POE) and more of the Sipura / Linksys SPA-841 (5 volt DC) units.  It might be easier to come up with 5V DC power vs. 48V DC in our trailers, via solar panels, etc.  One new challenge - an ad-hoc power over Ethernet strategy.  POE is used extensively for IP phones and wireless access points. 

News: 1/14/09: The final, detailed report on the performance of the new digital Motorola Apco 25 /ARMER public safety voice radio system at the 35W Bridge Collapse incident was published in December 2008.  Anecdotal indications right after the incident were quite positive, and these findings were confirmed in the report.  The radios performed well in the challenging conditions at the river disaster scene, which was well below average grade level. 

There was a fair amount of discussion of who was assigned to what trunk/talk groups etc.  One interesting finding was just that listening to a given talk group used up system capacity.  So if you hear of an incident and "tune in" you use up scarce resources across the system when your radio registers to that talk group.  This was a fairly small incident as disasters go, so a renewed focus on training and channel discipline seems to be in order.  The mass issuance of these radios to volunteer groups, given the fairly high cost and finite nature of the channel capacity, does not seem prudent.  Another strategy is for systems to restrict talk groups to local "membership" - you can have wide area ones, but you need to limit far away users from joining local talk groups. 

News: 1/10/09: The New York Times is reporting today that the $2B contract in New York State to build a statewide data network in that State for public safety purposes is close to cancellation.  According to the copyrighted story, after $52m in work in two counties, the system was unsatisfactory.  The winning bidder, M/A Com, apparently underbid Motorola by $1B.  We built our Statewide Packet Network here in Minnesota in 2002-2005 for about $8000, which covers 75% of the population.

A guess would be they underestimated the number of sites/towers they would need.  New York State has a lot of hills.  These very effectively block radio signals.  The larger cell phone companies have an average of 1000 cell sites per state.  $2B does not buy a lot of sites, and sites are hard to get, etc.   

News: 1/3/09: Our donated and surplus laptop computer "fleet" did not fare well during the 2008 MTCM.  Out of a dozen units, perhaps three were working at 100% capacity.  So for 2008 we are upgrading.  All units will be running legal copies of Windows 2000 Professional at least, and all 802.11b wireless cards have been retired.  Just one 802.11b card takes the whole network from 54 mbps down to 11.  All new 802.11g cards will support 100mw output power and WPA.  We are going to support Family Medical with diversity receive antennas on the data trailer in 2009 as well.    Windows Update is a two edged sword- good for security, bad for "thin" temporary networks. 

News: 12/18/08: There are reports of two new Marathon races being established in the Twin Cities in 2009.  

http://www.individual.com/story.php?story=93628335

News: 11/29/08: We are happy to welcome members of the Metropolitan Hospital Compact to the D-Star system in the Twin Cities.  Amateur operators supporting member hospitals can set up accounts on the STPONE system, overlooking the Minnesota Department of Health in St. Paul.  It can be reached via packet radio on 145.01, and on D-star on 1249.000 - DHCP is enabled.  You can use your Amateur callsign for an ID.  On packet, we are working on a way so passwords are not sent in the clear.  If you use your callsign as an ID, it is Federal Crime to transmit with a fake callsign, so there is some protection.    Note this system is not on the Internet, and should present a low risk for common Internet security exploits.   

News: 11/24/08: Our highest priority radio project right now is the purchase of a UHF /440 D-Star RP-4000 module for the STPONE site.  There is a controller port and antenna ready there.    Digital voice technology is more challenging to jam, and should be more dependable under emergency conditions than FM technology. 

News: 11/24/08: We are grappling with how to handle runner supplied Personal Health Records during the Marathon.  The idea is if runners provide basic information on pre-existing conditions and medications being taken and allergies, medical treatment during the event would be safer and more effective.  The issue is we (volunteers) are nervous trying to secure that data.  Ideally, runners would enter it once, and for a given race, healthcare professionals (i.e. MDs) could securely access that information if needed.  We are looking at two widely available platforms - Google Health and Microsoft Health Vault.  This would also further the cause of national adoption of electronic health record technology, as runners (and the Sports Medicine Community) are very leading edge in healthcare technology adoption and research.     

News: 11/17/08: Here is a link to the new Minnesota Mobile Medical Unit - we need to see what associated communications volunteers it has.

  http://www.health.state.mn.us/news/mmu.html

News: 11/17/08: The Minnesota Hospital Compact is looking for some help and we have offered to nose into that space.  Our big data networks are done, and getting served agencies on them is a good next step. 

News: 11/15/08: Dan reminded us that the ID-1s do not have an IP address, and we are using them as bridges to networks behind them, so a larger address block might be better- say a /28 or larger.  And there was more discussion that routing protocol overhead is not good.   The notion of a fixed /24 per repeater /ARAP system seems to still have merit.   

News: 11/9/08: Peter has come up with an idea to use DHCP and /29 subnets.  The idea is all ID-1 attached networks connecting to the repeaters would get assigned a /29 address, and we would use OSPF to ensure the IDs could talk to each other via the Ethernet on the Linux appliance.  This would replace DNAT.  We would retain the .1 to .20 addresses on each repeater for fixed services, like .1 for the repeater and .20 for the web server.  We made good progress on a design for our new Field Hospital Management System, based on a locked down version of our current database server.   We are going to make extensive use of handheld devices for triage, admissions, bedside care and remote secure inquiry.  Handheld device triage input is used by the US DoD. 

News: 11/9/08: We have a request to get some uplinks going to test the Red Cross Safe and Well system on our network. 

News: 10/24/08: The underlying D-Star DD protocol does not seem to support error correction.  So the overall system relies on the upper layer protocols to handle retransmission.  Web browsers don't seem to care much- they get slow on poor RF paths with lots of packet loss.  FTP on the Linux appliances is not as happy, and Max is reporting some corrupted tar files.  It might be time to dredge up some of the bulletproof file transfer packages like Xmodem - maybe we need one of our own- "Dmodem" for D-Star. 

News: 10/22/08: We are resisting the call to pile more applications on our NeoWare Linux appliance computers.  I think we are going to call these "Amateur Radio Routers" since they have all the services we use- AX.25, TCP/IP, D-Star services, etc.  Faster ones could support VoIP/SIP, repeater control, IRLP, etc.    Then there is mesh networking.  If you want an actual database or email server, that needs to be on a regular computer we think. 

News: 10/21/08:  Max is reporting he has upgraded all four of our D-Star systems to support DHCP.   Alan's has for some time.  We are retaining our separate subnets to facilitate linking.  

News: 10/20/08: Programming D-star radios can seem complicated.  There are just three things you need to program for basic voice repeater operations.  The Icom manuals, likely translated from Japanese, are inscrutable:

Mycall (the U82 book on P. 11 says this is "your" call sign - see below)  - This is the call sign of the radio owner - i.e. you

Yourcall (not to be confused with "your call" above) what Icom calls the "desired station" - i.e. somebody else - use CQCQCQ - lets you talk to anybody 

RPT1 - use the call of your local repeater.  You can get confused with a second repeater and remote repeaters and suffixes.  Just put in the call of your local machine to start. 

If this is right, you will hear local operators talking.  If it sounds like Donald Duck, that means the RF signal is weak- use a better antenna. 

News: 10/18/08: We are looking for tower climbers.  No experience needed- we have a ton of expertise and equipment - (belts, etc) and can train -but we are getting some projects that we need a larger crew for.  The latest one, the link build-out at Monticello, needs almost 1000 feet of hardline pulled and seven antennas, all at the 110+ foot level.    

News: 10/16/08:  We have been calling in all of our markers in trying to develop a Northwest receive site for the 146.85 repeater.  This machine is, and had been for almost 30 years the primary repeater for Metro Skywarn volunteers, and has several new jobs, such as supporting the Area Hospital Compact.  Storms come from the Northwest as a rule, and we want our spotters to be there looking for rotating wall clouds, etc.  The .85 system can be heard out there, but can't hear the spotters.  After three in person meetings with area elected government officials, we have identified a candidate site.  More to follow. 

News: 10/14/08: There was some drive time activity on the 442.90 D-Star voice repeater here - I think the FM machines are not very lively and some folks might have moved here.  We are going to set up a voice ID-1 machine in Ramsey County this winter.

News: 10/10/08: Several of us are going up to our site in Monticello, MN on Saturday, 10/18 to install seven antennas and several repeater systems, to finish the long planned voice radio link from the Twin Cities to Brainerd, and get the Superlink going again.  Anyone interested in helping can send a note to Paul, K0LAV.  

News: 10/6/08:  The over 100 Amateur Radio volunteers (we were a few of thousands of community volunteers at the event) had a cool, damp but fun day at the 2008 Medtronic Twin Cities Marathon.  Our new D-Star data repeaters performed flawlessly.  Everything went well- it was great practice all the way around.  The level of runner injuries was very low.  That made us all happy.  We ran six formal voice nets, and trained in some new operators.  The level of cooperation across the various public safety and medical organizations was flawless.  Life is good.

Above is the 2008 Medical Tent the day before.  Don brought his tower trailer (center) with 2x UHF business band antennas and our 440 Net 4 antennas.  To the right is the data trailer - 1.2G antenna for Minneapolis East, (10 miles away), packet antenna (145.67) and 802.11b for the finish area.  On the front of the trailer is a mobile whip for STPONE on 1.2G.  Running two D-Star data 100 kilobit repeater uplinks 2 MHz apart was no problem.  We can scale up for massive events this way. 

A picture of Net 1 (Golden Valley Public Center) from K0BUD.  Max from our Data Team is on the left.

Net 3 (St. Paul Fire Department Communications Center) from Bill Hughes.  Doug Reed installed an ID-1 the week before the race and they got into the system via STPONE.

 

A surprise visit from an alumni- Tim Neu, our first Linux Systems Manager- he did the first install of Trivnet (our database and packet radio /TCP-IP interface) for us.  He volunteered in Medical Records/Admissions. 

It was soggy but cool - decent running weather for us in 2008.

Our Medical tent at 5:00 AM race morning- all set. 

Peter in the data trailer -  behind him is the new (to us) Sun Netra server- and Trivnetdb 2.0 which he re-wrote for 2008, also the MPLSE uplink, the packet radio, and the STPONE uplink.   There is a new (to us) ID-800 as well.  We are going to try to run the 2009 event 100% on D-Star data, and trying to further phase in digital voice.  Net 3 was on APCO-25 again this year.  We are currently about half digital. - 2/3 of the data and 1/3 of the voice. 

An unknown Medical volunteer, Dr. Roberts (c) and Dr. Morrison (r) working triage outside of the tent.  Dr. Morrison keeps explaining triage - it sounds simple- "chest pain- into a rig to the ER; ice pack or blister- self help table; everybody else goes in the tent" I think that is Ryan in the doorway in a yellow shirt doing check in.

Three of around eight electric carts failed in the wet conditions and impacted all kinds of logistics activities.  It has been popular in recent years to have ham operators and MDs team up on carts and zoom around taking care of down runners- they can maneuver around barricades and crowds and even across lawns, taking care to not hit underground sprinkler heads ($$$). 

A steady supply of rigs (and places to send patients) is the key in mass casualty incidents- St. Paul Fire and HCMC EMS did their usual outstanding job.  We used MNTRAC to track hospital capacity and transports. 

News: 10/5/08: Here is the 2008 Post Race Letter from Dr. Roberts: 

Thanks to all of you who spent the day helping the runners.

You did a great job in challenging conditions for both the runners and many of you who were stationed outside in the rain.

This is the first time we have had any significant rain during the race and it increased our early encounters.

Once the rain stopped, we saw a significant decrease in encounters and it was almost "boring".

Thanks again and I hope to see all of you again next year.

 As always, if you have suggestions to improve the medical team, email me with your thoughts so we can discuss them in the steering committee.  We made several changes on the fly today that improved care and outcomes.

 Cheers,

Bill Roberts

Medical director

News: 10/4/08: It's Marathon Weekend in the Twin Cities.  We are currently running multiple D-Star DD mode data uplinks this year from our data trailer on the State Capitol Grounds, to our repeater systems in Ramsey and Hennepin counties.  We discovered late last week our new microwave antenna on the St. Paul Fire Department Communications Center (Net 3) is blocked by a building from line of sight to Minneapolis.  We are running Net 3 on our new STPONE site, and Net 2 on MPLSE.  Last year we ran a single feed from the data trailer to one repeater.  There are several other ways to make this work- the key is the DNAT software Max put our four thin client repeater controllers.  We are testing an iPhone as a medical admissions client system in the Hospital Tent.  We have been requested to integrate the databases for 2009.  The Marine Corps Marathon does this- we have been hesitant on the HIPAA front here, but a secure database and network design should make this possible.  The idea is the Ham Radio (Part 97) side of things gets a "public" view, and the inside of the Medical Tent (now 40X80 feet) gets a secure, encrypted view over 802.11 with a VPN running. 

News: 10/1/08: If you are having trouble getting connected with ID-1s in DD mode, remember the end computer IP address masks *must* be compatible.  The easiest way to accomplish this is to have them be an exact match.  So ours are 255.255.255.0.  ID1s do not seem to be aware of IP addresses- they just move Ethernet packets around but care about callsigns.  See our directions below. 

News: 9/28/08:  We had a sighting of the actual Dennis Boone, KB8ZQZ, (L below) who wrote Trivnetdb for us a few years back.  I was telling the audience at the TARP/DCC Conference in Chicago how grateful we were for his work and there he was.  Pictured with him on the right in the photo is Jeff Goeke-Smith, who in working with him on a Ricochet project.  It is being reported that large quantities of remaining hardware have found their way into friendly hands via an asset purchase.  Dennis is showing a 900 MHz spectrum analyzer that uses the Ricochet USB hardware platform.  Talk about a small world...

dennis boone

News: 9/19/08:  Our fourth Twin Cities D-Star high speed data repeater and newest full time 145.01 packet gateway, STPONE, is operational on an excellent downtown St. Paul commercial site @260' AGL.  Many thanks to all those who helped out over the last few months.  We now have two systems serving Ramsey County and two serving Hennepin County and one on air spare.  The new system overlooks the MN Department of Health, State Emergency Operations Center and St. Paul Fire Department.   It is in clear view of the State Capitol and will also serve the 2008 Medtronic Twin Cities Marathon. 

News: 9/17/08: Alan is reporting quality control problems with Comet base station antennas - improperly soldered internal parts on GP95s and GP3s.  You need to test SWR before installation.  We have ourselves had in service failures on GP21s due to wobbling and the base set screw popping out. 

News: 9/17/08: K0LAV, Paul, has developed a voice radio setup for the Marathon Operations Center that we manage.  It consists of two Motorola Maxtrac 2 channel radios in a metal case with power supply.  With the channels pre-programmed to the main and backup repeater for each radio net, we cannot have race day radio programming issues.  We'll see :-)

News: 9/16/08: Our newest repeater was delivered to the site today.  We expect it to be on the air this week.

News: 9/16/08:  We need voice operators for Net 1 on the Marathon - contact K0BUD     via N0OEL@aol.com  

News: 9/15/08: We will be presenting on Saturday 9/27 at the annual TAPR Conference in Chicago right after lunch.  Our talk, on the future of volunteer emergency communications, is called "It's the Network"- rumor has it magazine editors are down there "trolling for articles" :-)

News: 9/11/08: There is a an interesting article in a trade magazine, Network World, on 8/25/08 about a concept called disruption tolerant networks.  These are used in field deployments and are designed to withstand outages.  The idea is packets keep trying to find a way to the destination. 

http://www.networkworld.com/news/2008/082208-dtn-networks.html

News: 9/10/08: The St. Paul Downtown site project is back rolling again.  We plan to install it in the next two weeks.  We have some more ideas for projects, now that the D-Star Phase 1 is nearly done.

1. A packet /voice link to Mankato.  This is needed for the Health Department.  One action item- find a nice water tank about half way and get a tri band antenna on it.  Then a nice cabinet at the base, and some feed line.  Then we can install packet, voice links etc as needed.

2. The Twin Cities to Rochester corridor needs an intermediate hop someplace.

News: 9/4/08:

Just an early reminder that next weekend, Saturday Sept 13, is the next

TwinsLAN member meeting. The usual time and usual place, 9:30AM at Pavek.

As usual, feel free to join us for breakfast at Byerly's behind Target,

south from Pavek. Max & I are usually there sometime around 8AM.

 

We haven't yet planned a speaker for after the meeting. Who has

suggestions to fix that? I'm out of ideas, so please pass them along.

What would you like to hear about? What have you been doing recently?

Did you use packet or digital modes during Field Day or on the

DXpedition to Lake Wobegon? Found any good tricks to pass along? Got

your APRS tracker working in the RV? Been using WinLink 2000 at all? We

could certainly use a Program Director for the TwinsLAN meetings.....

 

And we'll be doing another Packet Workshop after the meeting. The

scheduled time is Noon to 6PM. The location is Kelly Black's work place

over on Douglas Drive just south of Duluth Ave west of the Hwy 100 exit.

Better directions in the Workshop email or probably on the TwinsLAN web

page.

 

This will probably be the last workshop before the Twin Cities Marathon,

so we'll be trying to do final check-out of computers and D-STAR stuff

we'll use for the event. Hopefully by then we'll have the next D-STAR

digital repeater installed. This one is planned for downtown St Paul so

it will hopefully be easy to hit from the finish line.

 

73, Doug Reed, N0NAS.

News: 8/30/08: There were some folks from the Federal Government at Radio City - they were in town for the RNC and getting parts for their radio truck.  I was bragging about our data networks, and they asked about our provisions for emergency i.e. solar power.  Good question.  We have a little grant money left, and getting one or more systems up on 100% solar power is a priority.  

News: 8/21/08: Given that the R.N.C. will be in town shortly, we are going to declare a network freeze and stick to repairs only between now and then. That is a new policy for us- try to lock down the configurations a week before the events.  

News: 8/17/2008: There is an interesting article in the September issue of QST on Project 25 radio technology.  This is another open standard for digital radios.  We have so far been underwhelmed by the digital voice aspects of D-Star - at the user interface level it seems to be too complex, counter-intuitive and not plug and play when used with repeaters. Our extensive mass casualty incident experience here indicates that systems that require a lot of user training and configuration are not helpful in the press of events with ad-hoc volunteer resources.  Our Marathon systems at the user interface (i.e. laptop) do not require any training, and telephones and well designed voice radio systems should not either.  If the Project 25 voice radio gear was easy to use we might like it.  The idea would be a box of radios would be issued- "Select Channel 1" is about the limit of user training that seems reasonable.  Further proof of this is in the level of difficulty some still have with "CTSS" tones on 30 year old voice radios. One could pre-build and clone radios but what to do about callsigns. 

One idea for somebody like Icom is to come out with some D-Star radios that are cheap, but require pre-programming the way Motorola radios do.  So the radios are $150 or $200 and you mass-program and issue them.  They could be digital only for that matter.  Groups could buy them in bulk and pre-program them for large scale go-kits the way governments do with Project 25 radios. 

News: 8/17/2008:  After a series of meetings with the Marathon Medical and Race Operations leadership, we have our plan in place.  A little testing is in order, and we have a new capability in the plan.  We are going to try to have on-site access to MNTRAC for logging and monitoring hospital transports and capacity.  And we need to system test our new Sun server.  We are out of space at the finish line in the secured area for any new large medical assets like tractor-trailer based mobile hospitals- we have been offered two of them so far. 

We need more Amateur Radio volunteers as we have a role in keeping track of golf carts and small "gator" type mini medical vehicles which can run in a crowded area with the roads blocked off.  Several of these are available to the Minneapolis Fire Department, etc.  We are also integrating runner supplied personal health information with our medical record form on a secure system to provide history information to the medical staff when someone arrives for treatment.   

News: 8/10/08: The talk down in Rochester went well.  After we left there were reports of "outstate grant money" being available.  This is interesting, but we long ago learned that it takes four or five in person meetings to get big infrastructure projects off the ground, and that local political leaders like to only deal with local folks.  Fast talking outsiders are not often helpful, and the smaller the city/county the more this is true.   After at least five less than productive 120 mile round trips in the last few years, we are convinced we are right here.  

 

News: 7/29/08: We will be speaking for the first part of the ARES Forum (around 9:30-10:30 AM) on 8/9 (Saturday) at the ARRL Dakota Division Convention in Rochester, MN.

 

 Complete Information at http://www.rarexpo.org/

 

News: 7/28/08: Dan Skripka is reporting the last installment of our matching grant has been approved.  Thanks Dan!  We need to buy some more antennas and may be investing in an electrician for a site install. The antenna we like best is the Comet GP-95.  The one at the Mining ARC works great. 

News: 7/27/07: The final system test is complete on the hardware for our St. Paul #1 site.  There is a Bloomington tower site available @160 feet - we do not need it for 145.67 and we do not have any D-Star repeater equipment in stock.  The two priorities we can see is for one of the "backyard" systems to move there,

News: 7/25/08:

The next workshop is tomorrow at the Golden Valley location, 9AM till around 5PM. Main project is to try and get the next D-STAR data repeater ready for install in St Paul and whatever else we can do in our preparations for the RNC and the MTC Marathon.

 

News: 720/08: All the parts needed for the St. Paul Downtown #1 Site are in hand, thanks to the grant for Dan Skripka and the support from Metro Skywarn.  The machine is now running in test mode- the D-Star is up we need to add on the packet.  We got a new radio for that. 

News: 7/16/08: At our "East" repeater/node site we are having stray RF issues (?) which are causing our Linux Thin Client system to crash.  So Max added in the capability to reboot if there is a kernel panic.  This seems sensible as we are all about reliability.  The very long (50 foot) stock Ethernet cable on the RP-1D might be a factor. 

Max:     "This is the command I put in rc.local to get the kernel to reboot after a panic:

 

  echo "5" > /proc/sys/kernel/panic

 

Normally, that value is 0 - don't reboot automatically, changing it to a non-zero value causes the system to reboot after that many seconds. A good thing for remote or hard to get at servers. There are other ways to do the same thing, sysctl being another."

 

News: 7/3/08: Our new St. Paul Downtown #1 repeater/node site has been approved by the site owner.  So we have a cabinet and are building up the equipment as we speak.  The plan is to have it installed by 8/15 at the latest.  It will support D-Star DD mode and have a packet gateway. 

News: 7/1/08: It is being reported there is a new State Van under construction that will be used for emergency medical response.  We would like to get that van set up with D-Star equipment as well, and test it this fall at the Marathon.

News: 6/30/08: We got copied on a note today from the Minnesota Department of Homeland Security and Emergency Management, who had the following advice on which ICS/NIMS courses to take:

"Simply, if you are an active participant in an event you need (ICS) 700,100, and 200. If you are making decisions about how the resources are used, requesting or sending, or leading resources, you need the additional training of the (ICS) 800, 300, and 400 courses"

News: 6/23/08:  Alan has made some homebrew 1.2G cavities.  These go along with the homebrew 1.2G beams.  We are going to pester him to make a duplexer next. 

News: 6/23/08: Dennis Boone, KB8ZQZ. who wrote Trivnetdb for us way back when,  has fixed the Trivnetdb source distribution site

http://www.kb8zqz.org/trivnetdb/

News: 6/22/08: We can report the RP-1D units do support DHCP pass-thru.  We tested it this morning.  Doug Reed, N0NAS was supervising, so there was no funny business.  By the way the Icom manual says to use uppercase letters only for the repeater call sign- the manual is right.  Peter, KD8GBL, also had the idea to test PPPoE - that works as well.  The idea is that can be used for many to many ID-1 connections via the repeater.  We do that today with DNAT, but it has to be set up in advance.  We tested two ID-1s talking to our newest repeater via PPPoE- thanks Radio City. 

News: 6/21/08:  The ARRL-ARES 6/20 E-Letter is reporting the following, which is encouraging - he is viewing the Icom ID-1 as yet another tool in our toolbox.

There is new software entitled JNOS for passing e-mail messages over Amateur Radio during emergencies:

<http://ronhashiro.htohananet.com/am-radio/packet/jnos.html>

 

Readers can download the program, and try it as noted in the documentation. Configuration is simple: it takes only ten to fifteen minutes editing in your call sign, password, and log-on banners to get started. The beauty of JNOS is the sending and receiving of e-mail messages over the Internet as well as Amateur Radio seamlessly. It can print incoming e-mail messages on a printer unattended, one message to a sheet, just like a fax machine.

 

JNOS will also take advantage of the ICOM ID-1 in digital data mode, and I'm in the process of testing and documenting that configuration.

At some point, I'd like to implement this at Hawaii State CD and Oahu DEM, when a sufficient critical mass has been implemented. -- Ron Hashiro, AH6RH, Honolulu, Hawaii State Civil Defense RACES

 

News: 6/17/08: 

The next packet & radio workshop will be Sunday June 22. The location for this workshop is Golden Valley. The workshop will run from 9AM until 5 or 6 pm

 

The focus of this workshop will again be on various D-STAR projects. We have a lot of work to do getting ready for some installations this summer. I am NOT going to have much in the way of test equipment and tools available. But if you have small projects we'll still be trying to help you complete them. If you tell me ahead of time you need something special, maybe I can bring it.....

 

The location is 1710 N Douglas Dr, Suite 285, Golden Valley, 55422.

 From Hwy 100, north of I-394, exit on Duluth St. Go west of Hwy 100 about 1/2 mile to Douglas Drive. You will go south from Duluth St and watch for the railroad tracks. Immediately on the north side of the tracks is a long, low, 2 story office building on the east side of the road. We'll be in Suite 285 but you will need to knock on the outside door or ask on 146.520 simplex for entry. If on Hwy 55, go north on Douglas Dr and it should be the second railroad crossing.

 

If you want a map, Google search for:

   1710 North Douglas Drive, 55422

 

If you are worried about getting lost, the Duluth Street exit from Hwy 100 is the best. You go west on Duluth St and it ends at a T intersection. Turn left, go south a few blocks and you will come to the railroad tracks, the building on the left is the one you want. Very hard to miss this way....

 

I hope to see you there! The next workshop will be in July. Come this Sunday and help choose some dates.

 

73, Doug Reed, N0NAS.

News: 5/28/08:  There is a list of projects building for our next open work session. 

Formally test and document DCHP pass-thru on RP-1Ds.  Does it work?  The jury is out.  We are reading reports both ways. 

Build D-Star system #4.  We need power, a cabinet, Linux system, etc.  System #4 will include a Packet gateway.  For the moment, System #4 is our lab repeater, though Alan might bring his portable repeater.  We are assigning 172.16.4.1 and .20 (/24) to the new system and might use 1249.000.   

System test the new 2008 server that Peter built.  The existing one then goes into hot standby backup status.  We could also test multiple ID-1 to ID-1 connectivity  to see if two server uplinks could be used at once.    In production in a disaster, we might have ten remote stations, each accessing two remote servers as an example at once.  This would let us support multiple served agencies. We will run two live ID-1 to repeater uplinks in 2008.  We should have six repeaters to choose from. 

System test the two new vans.  Antennas in these as well as the internal Ethernet and 802.11 capability will need to be verified. 

News: 5/25/08: We are getting offers to borrow more high end mobile communications vans for the Marathon.  As of right now, a new 50 foot mobile fire command center may be joining our "fleet", and we are also working on the MN State Mobile EOC van.  If both had D-Star ID-1s, they could tie into our database trailer at the finish line via our repeater systems.  We can loan them equipment out of our radio pool for the event.  It might be nice to have say five ID-1s going back to one ID-1 at the database end.  We have DNAT on our repeater back end systems set up to support multiple uplinks from multiple remote databases.  We continue to not be fans of the databases co-located with repeaters model. 

News: 5/17/08: The American Radio Relay League has announced a change in direction for the organization.  There is a new "Fifth Pillar" - technology.  This is a timely move, as this heads off a very strong movement in the organization to become largely an historical society.  As someone who owns more than 75 history books this is OK, but was causing trouble in several key areas.  One is with the recruiting of young people who expect us to teach them current technical skills, the FCC rules, which reference "the state of the radio art," and served agencies, who are tired of hearing about the limitations of 30-80 year old radio operating modes, given the other choices  they have.

ARRLWeb: ARRL NEWS: ARRL Introduces "Fifth Pillar" at Dayton Hamvention®

News: 5/16/08: We have seen a 15% failure rate on the little five dollar RJ45 F-F adapters that go on the Ethernet pigtails on new out of the box Icom ID-1s.  If the Ethernet seems "dead" on yours, try a different adapter.  Spare ones of these are a handy item to have if you need to extend RJ45 cables anyhow.  These cables are used for other applications, such as microphones and serial cables.  It is helpful to own an RJ45 crimper as well.   

News: 5/15/08:  At the last work session we issued an ID-1 radio to Max, who is able to now drive around and test the systems.  We have at least 10 D-Star repeaters in Minneapolis/St. Paul.  One issue- can we get these listed in the ARRL Repeater Directory?  The issue for us is the DD machines by themselves are not technically repeaters and also do not do well on shared frequencies.  So our systems need to be coordinated, even though they are simplex.  

News: 5/11/08:  We have long suspected there is not a lot of spare emergency room capacity in major US cities, based on our experience at the Marathon here.  A story in USA Today on 5/6/08, while having limited scientific validity (one random sample was taken) showed that Minneapolis had five empty emergency room beds.  Other cities in the sample were in about the same shape.  Washington DC had zero, and Chicago had eight.  The notion of improvised facilities that would somehow be set up to handle a big flood of cases was discussed.  Those who are skeptical about the role of Amateur Radio in disaster recovery need to read that - there is no other group that has this level of experience in ad-hoc communications. 

http://www.usatoday.com/news/nation/2008-05-05-citiesready_N.htm

News: 5/10/08: Peter built us a new production server for the 2008 Marathon on a rack mounted 1U Sun Netra server.  These have several advantages, and they are compact and cheap enough ($50) to install permanently places like in trailers.  Hauling desktop computers around is not much fun.  The one he found has two Ethernets and two serial ports- just enough, (one D-Star uplink, one 802.11, one packet TNC and the server console) and built in RAID.  We also have a new release of our web server code and more database fields.  We are upgrading our IP phone system as well.  We think the last $2000 of our current grant will go to one more ID-1, and then some antennas and power supplies and lightning arrestors. 

Prediction:  IP Phone systems will be as important to ham radio post 9/11/01 as war surplus prop pitch motors were after WWII. 

News: 4/24/08:  The final US Fire Administration report on the 35W Bridge Collapse was issued and is interesting reading.  The strong and effective event response was marked by good communications practices, a solid following of Incident Command System (aka NIMS) procedures and the fact that the agencies involved in relief efforts had trained together.  The number of EMS runs (50) was very similar to that from the 2007 Medtronic Twin Cities Marathon. 

The concept of "freelancing" - self dispatching of emergency resources without orders from the Incident Commander was mentioned.  This is one thing volunteer groups like ours need to be vigilant on.  Volunteers who show up at a disaster scene without being requested may have good intentions, but add to the burden of the Incident Commander, as they then have to be looked after from a safety and logistics perspective. 

http://www.usfa.dhs.gov/downloads/pdf/publications/tr_166.pdf

News: 4/23/08: We have been given approval to proceed with our new Minneapolis Downtown #2 site.  We just picked up our fourth RP-1D D-Star DD mode repeater- thanks Radio City.  Exactly where this machine will go depends- one good choice is St. Paul #1 depending how the paperwork goes there, or the Minneapolis #2 site.   We are expecting one more grant shortly- the question is- do we ask Dan to order Repeater #5, or do we add 440 capability on to one of the machines we have?    Icom is reported to be out of first generation D-Star repeaters as part of the "Buy Five" promotion. 

News 4/23/08: We are pestering the ARRL to do something about callsign authentication.  Right now it is trivial to spoof a callsign in an email message.  When we get a message from W0XYZ, is it really from W0XYZ or someone pretending to be W0XYZ?  So using off the shelf digital signature /public key infrastructure software would fix this.  There are those (we are in that camp) who oppose encryption of amateur radio traffic - this is not encryption it's authentication.  The FCC rules require it actually "97.219...(1) Authenticate the identity of the station from which it accepts communication on behalf of the system."   If the ARRL does not take the torch here we might try it ourselves.  The other thing you can do with this technology is to sign/authenticate message content- this is like a checksum to prevent/detect tampering with the content.  This is part of what is called in the security business "non repudiation" - did you really send that message. 

News 4/14/08: We need to think about upgrading our 802.11 facilities and to get our mesh networking research project moving again.  We are meeting with the Medical and EMS teams for the Marathon soon, and will get our summer work plan in order.  We got a little busy last fall on infrastructure work and need to see what they are asking for.  One idea they liked was a "bed dashboard" application for the hospital tent - to show who was where and provide a live view of capacity - one key requirement is deciding where incoming patients need to go, and to keep the ER section open for new critical cases. 

News 4/14/08:  We are getting calls and notes about the new "RMS" /Winlink software.  We are mostly network builders here, and these networks should be an ideal platform for this software.  Jerry, N0MR,  is a leading expert in MN on this topic.  One interesting issue - we are seeing more packet activity in Wisconsin on 145.61 and will need to build some bridging stations.  Our practice would be to install two or three gateways if we decide to go ahead. 

News 4/11/08: We may be getting two new repeater/node sites, including possible one in St. Cloud.   Work is underway on the packet gateway at MNSTP and we are experimenting with DHCP on that machine.  DHCP is not looking good at the moment.  One hunch is it is a broadcast based protocol and D-Star DD mode (via repeaters) does not seem fond of broadcast protocols (for good reason). 

News 4/2/08: We are again putting the Medical Communications Team together to support the 2008 Medtronic Twin Cities Marathon.  We are looking for volunteers, and have openings out on the race course and at the finish line.  It should be possible this time to run the data side of the medical support operation all on D-Star DD with packet radio as backup.  We need to get an ID-1 to the Twin City FM Club and one in the Ramsey County EOC.  The Ramsey County one is on order. 

The team is organized as follows:

Chair

Asst. Chair /Finish Line/ Operations Center

Net Control Net One /Volunteer Check in

Net Control Net Two

Net Control Net Three

Are the main leaders, and then we have departments at the Hospital Tent, Family Medical Tent, and the Remote Bus Drop off/EMS staging area, and then for the Data Trailer and database servers and for Net Four and various medical radio channels.   All operations are decentralized and the Net Controls are spread out across the geographic area.  This is helpful if there are problems- if you can't reach higher authority you just keep going, and too many radios in one place leads to RF interference and general confusion.

News: 3/26/08:  We got a new (to us) Icom ID-800H D-Star radio, which we are experimenting with.  Thanks Ed, WB0VHF.  This is for the trailer and will be used for all kinds of duties.  The setup complexity (programming all the call signs) here is a little bit of a barrier- there is of course software available for the radio which makes it easier.   It is being reported the MNSTP upgrade and packet gateway work was successful.  We'll post some screen shots. 

News: 3/22/08: A team from Twinslan and the Mining ARC are upgrading the MNSTP site to include a full time D-Star DD mode to AX.25 packet gateway.  We run one for the Marathon but have not had one online all the time.  We are also experimenting with some ideas we have for linking.  We have a new appreciation for the work that AMSAT does, as they do not get to rework anything once launched.  

News: 3/19/08: The talk down at Mankato went well.  The club there is running late model commercial equipment for their repeaters, and uses all diverse Government sites.  Some clubs run the oldest possible, often fussy repeater and data equipment for some reason. 

The question came up in Mankato: "how can we get more involved in operations and exercises?" and answer is pretty simple for them.  We have an ongoing mission to support the MN Health Department.  The club down there can meet with their local Public Health Officer (who they already know) and set up a drill/exercise- a "what if all the phones/Internet are out" kind of drill.  And move some messages around.  One group in Northern MN ran a drill last year where they distributed colored M&Ms(r) as a test of vaccine delivery.  There are outlying counties down that way that need to be engaged here as well. 

They also need to get some links built to the Twin Cities (about 66 miles and some big 1000 foot ridges away as they are at about 800' ASL).  They also need a second path to be built on packet to the Statewide Network that does not go via the Twin Cities.  Then they could become a remote hub and even a operations center/hub with a BBS system etc.  We hatched an idea for a big Statewide drill where they would be in charge.  Our thought was, if something really bad happens in the Twin Cities, do we want that event managed from the Twin Cities, or with Twin Cities based operators- no.  One idea as well- if there is a School of Public Safety at Mankato State University, they could learn exercise planning and use us as the persons to run the drills. 

Long term they can get some sites along the way to the Twin Cities on a link via packet and then upgrade that link to Microwave.  And then they can put a D-Star system in and link that in.  The National Weather Service is down their way and might a good connection point. 

News: 3/19/08: We think the MNSTP System was down for a day. Ed reset the power and are back up.  That one is borrowing 12V power from someplace and needs a dedicated late model switching power supply.  These, like the SEC 1223 units we get at Radio City, have been highly reliable and have low standby current draw.  We say "we think" as you need four things to reach a DD mode system- a good RF path, the right frequency, the right repeater callsign and the right IP address.  If you have just the IP address wrong as I did this morning the ID-1 gives you this ?KC0TQI message back from the repeater which is a version of "I'm here" which is good.   

News: 3/18/08: We are promoting Dan Skripka, KE8TX  to CFO of our organization. 

News: 3/16/08: There will be a talk sponsored by the Mankato Radio Club on 3/18/08. 

“Digital Communications in Emergency Response”

Erik Westgard, NY9D will provide a presentation on the following topics...

The need for digital communications in response situations.

History of the current digital network in MN. (Packet 145.01, 145.67, APRS)

The future need for a faster digital network.

Do D-Star digital data repeaters have a place in MN?

 

Background Information:

Current Packet Network http://www.14567.org/

D-STAR at the 2007 Medtronic Twin Cities Marathon By Erik Westgard, NY9D

http://www.arrl.org/news/features/2008/03/01/2/?nc=1

 

March 18th, 2008 @ 7:00 PM

Red Cross, 105 Homestead Road Mankato, MN

Map to Red Cross

 

RSVP to k0yr@arrl.net

 

News: 3/16/08: Dan Skripka, KE8TX, donated some money to our project, and has managed to get that matched by one of the area foundations- so we have the funding in hand today for the equipment for our St. Paul Downtown #1 site.  Thanks also to Doug Reed and to Metro Skywarn for handling the behind the scenes processing on these grants and donations.   Dan from Radio City is used to us as he knows when we call to ask him to order $3000 repeater/radio packages we never have any money at the time but it shows up from someplace at the last second like clockwork.

By the way the key to getting new sites and funding for Amateur Radio infrastructure is the proper handling of paperwork.  The days of handshake-only arrangements are long gone.  Relationships and trust are important, but all your agreements need to be in writing to protect all parties.  

News: 3/16/08:  Do weather maps work on the D-Star DD mode system- yes.  This one is a 250KB JPEG viewed on our Minneapolis Downtown #1 system- the download time was pretty good this morning- a few seconds

News: 3/15/08:  It is being reported the new rooftop antennas at the MN Health Department HQ (Freeman Building in St. Paul) are installed.  Radios of all kinds (except, interestingly, our Packet Network) and cell phones worked poorly inside that building likely due to metal film tinted windows.  There was a long struggle with the architects over outside antennas- we won :-) 

News: 3/8/08: We have a new location in progress for our workshops.  Many thanks to the Maplewood Fire Department for helping us over the years.  They are remodeling their station there and needed the space back. 

News: 3/8/08: The paperwork on our new St. Paul Downtown #1 Site is moving along.  We contacted Dan Fish up at Radio City in Mounds View about equipment for the site.    The plan is to have that on the air in <60 days.  The site is at >250' AGL and will require minimal site preparations.   We are slated (based on a conversation with Max on our Software Team) to have Packet (145.67) to D-Star linking there.

News: 3/1/08: Our 2007 Medtronic Twin Cities Marathon story is on the ARRL Web Site today

 http://www.arrl.org/news/features/2008/03/01/2/?nc=1

 

News: 3/1/08: Here is a note from Tom Azlin, who runs the digital aspects of the Marine Corps Marathon in Washington, DC.  They started using L-Band D-Star a year before we did, and have a much larger race in terms of runners. 

 

3/1/08

Very cool Erik!

 

It is indeed a really good D-Star public service application.  Here in the Washington DC area we are about to kick off the third year of using the ID-RP2C/2D and multiple ID-1s for the Marine Corps Marathon (MCM).

Our Operational Readiness Demonstration in 2006 was switched part way through that race to the primary comms for the four demonstration aid stations.

 

We have a different back end set up as we plug the controller into the existing Marine Corps network at the finish line which simplified our role to the communications between the MCM finish line servers out to the seven aid stations supporting over 20,000 runners. This allowed direct access to the MCM runner databases by the officials at the aid stations using the MCM created web applications. BTW, the selection of D-Star was made by the amateur radio team and is not Marine Corps endorsement. What they see is simply using their existing applications via amateur radio.

 

The past two years of success with D-Star at the MCM has led to discussion of the 23cm DD system in one of the local counties to connect to emergency shelters with the EOC. This will be tested over this next year in exercises as we now have our Tysons Corner D-Star repeater up an running.

 

Again, great story and application Erik. We have learned a lot over the past years from how you are supporting the marathon there.

 

73, Tom n4zpt

MCM digital coordinator

 

News: 3/1/08: We are making progress on our new St. Paul Downtown #1 site.  The idea is to have our fourth D-Star DD machine there. 

News: 3/1/08: We attended a huge Healthcare Information Technology show called HIMMS 2008 in Orlando.  Avaya was there and had an emergency response truck, which is similar to the one Cisco has.  The Cisco one is called the NERV and I have toured it as well.  These have routers, and an IP PBX in there.  (So do we in our trailer- see below). They have a satellite dish and a bank of VHF/UHF public service radios.  They each also have an Icom IC7000 UHF/VHF/HF amateur radio.  One of the things they can do is interconnect the audio from the various radios and the phone system and the satellite.  This is a high tech version of the old ham radio "phone patch" in a way. Video is a big part of the system.  And they support teleconferencing.  Our ancient donated trailer has a much better antenna tower (65') than any of these state of the art money is no object vans - and big towers give you range when you are trying to access or provide emergency radio coverage. 

http://blogs.cisco.com/news/2007/11/video_ciscos_network_emergency.html

There was a nice presentation from the IT folks who run the Palomar Pomerado Health and Scripps Health hospitals during the recent San Diego wildfires.  They gave a talk on how they dealt with the wildfires, which were expected at one point by a senior fire official "to burn all the way to the ocean (the entire San Diego County)" and included the evacuation of an entire hospital.  The utilities stayed up, and they did a good job on the evacuation- around 200 patients moved in 2.5 hours.  They had a lot of problems with smoke and ash getting into ventilation systems and into buildings.  There were lots of times when they did not have good information on the unfolding crisis, but they practiced and practiced before hand.  Employees developed an interesting technique to see if their house burned down while they were at work- if their old fashioned answering machine answered, their house was still standing.  They also ran an emergency day care center as schools were closed- this helped key employees report to work. 

At the show we learned there is a priority over-ride system officials can use for cell phones to get a line in a period of overload (though this would not work if the overload was caused by too many officials who also had priority) and this can be combined with another priority system to get access to long distance services as well.

News: 2/17/08: Based on a conversation with Ed, WB0VHF who has been a big supporter of our project, and some of our served agencies, we are ready to discuss our plans for high speed data infrastructure for the RNC event on September.  We will add one more system to our network between now and then and possibly two.  The goal is to go from three to five DD Mode D-Star machines ("repeaters/ARAPs") on line by 9/1/08 under our jurisdiction.  The idea is these will be on wide area, secure, commercial/government sites and will be available for volunteer Amateur Operators supporting the agencies when they are required.  We are down to needing about $1500 to get the first new machine going.  The second one will be about $3500.  Hennepin and Ramsey Counties are both purchasing user radios for the system. 

Current Sites:

Minneapolis Downtown #1- Up

Minneapolis South/MofA/MSP Airport- Up

Mining ARC /Oakdale/St. Paul - Up

New Sites:

St. Paul Downtown #1 - site candidate in discussions

Minneapolis Downtown #2- site candidate in mind

News: 2/14/08:  Kelly helped us build a field deployable IP PBX with six phones.  The idea is if we have to build an ad-hoc Emergency Operations Center we would have telephones, which do not require control operators, and when you are running a large field hospital (as we do every year) phones are just easier.   We can tie into any existing Internet network, and bought some SIP VoIP service from an outfit way out of town.  We are using the Internet to provide ad-hoc phone service in case other types of phone services are unavailable.  We also have an analog trunk card if we do find a real phone jack. The Red Cross uses this type of technology over satellite.

News: 2/9/08: There is a work party at the Maplewood Fire Station tomorrow, 2/10- 9A to at least mid afternoon.  I am not sure on the agenda. 

News: 2/3/08: We happened to rent a copy of the movie "Live Free Die Hard" with Bruce Willis.  This movie accurately characterizes the current wild enthusiasm for putting critical SCADA utility and infrastructure control systems on the Internet.  And it should be considered the last word on why modern Internet based communications systems need a backup that is not also based on the Internet. 

News: 1/28/08: A question came up today if our system was open to general Amateur use.  The answer is yes.  We think credible backup communications systems have to be regularly tested and exercised.  This includes hands-on operator training and general use.  We also have a ton of experimentation to perform.  FM Voice was pioneered back in the 1970's.  D-Star technology is brand new, and we are helping to develop it.  This band, L-band, is unknown to most folks in Minnesota.  Actually, data over L-Band (aka DD mode) is new to almost everyone. 

News: 1/23/08:  There is an article by Craig Kuhl in the 1/15/08 issue of Wireless Week Magazine  http://www.wirelessweek.com/Article-8-Hours-Long-Time.aspx that states there was an FCC order issued after Katrina that all 210,000 US cell sites must have at least eight hours of backup power available.  The article goes on to say this requirement came about after a "stinging" post event report from the FCC: "...a lack of adequate backup power for communications facilities was a critical problem after Katrina that caused communications network interruptions and hampered recovery efforts."    The article goes on to provide a quote from Caterpillar the engine people to suggest that "more players on cell towers...(including) ham operators..." were driving an increased demand for backup power.  As we have the backup communications mission from the FCC and world wide we need to very gently remind our agencies they still need a backup communications system of some kind- and preferably more that one "layer" of backup.

News: 1/18/08: We got a donation yesterday of some surplus flat panel monitors and a big 24 port LAN switch.  We were short of both items at the last workshop.  Thanks, John Leeper.  Max is working on the routing architecture between the Linux appliances behind our repeaters that are not repeaters.  We think RIP will be fine for us.  A network convergence time of say ten minutes might be fine- the last thing you want on a fairly slow network when you have important traffic to pass is a lot of automatically generated routing chatter and flapping.   We talked to the Minnesota Department of Health - they are updating their web based emergency health information system and want the new one ready for the big Republican Convention.  Note the term "web based"  - we tested the old one on our network.  

News: 1/12/08: We got an email from the folks in Rochester, MN interested in D-Star.  Other than Internet linking to say the system at the U of M, they could also link to us up here by email.  The idea would be to set up a TCP over Packet (AX.25) VHF link between the Linux back end systems on the repeaters.  So mail could be forwarded and folks could participate in live conferences.  These is even a way to set up "linked" conference rooms under Citadel.  This could be done on 145.01.  The 145.67 network was designed to not support TCP/IP and automatic mail forwarding.  If there needed to be a faster radio channel over the 70 miles we can build one.

News: 12/30/07: We spent most of our workshop session today loading up an Asterisk VoIP system on Debian 4.0.  After a while we started pestering Doug Reed, N0NAS to let us test this over D-Star, so he set up two ID-1 radios for us in the lab.   We tried a Cisco 7905 (SIP firmware) phone on one ID-1, and the Asterisk server (+ Sipura 941 SIP phone) on the other ID-1.  We had a known good simplex DD path.  The phones could call each other but the voice quality was very very choppy.   We did not have time to research which CODEC we were using in the phones.  DD mode is simplex, and does not seem to like a full duplex stream of small packets.  We think a more "half duplex/push to talk" type voice mode would work over DD.  This was a research project, and we plan to spend some more time on it.  Phones of all kinds sometimes don't work in disasters, and the ability to make a VoIP call has been requested.  Having a phone system in our trailers seems like a good idea.  There are legal restrictions on the use of Part 97 frequencies for routine phone service.  It might work just fine and be regulation-free as another emergency communications tool for us if we use WiFi or our Ricochet network backbone.  

News: 12/29/07: We are out on the ARRL Web Site today:    http://www.arrl.org/news/features/2007/12/29/1/?nc=1 and on the front page of QRZ.COM. 

News: 12/29/07:  On re-reading the ITU G.114 spec for Voice over IP, it says one way delays of <150ms are acceptable for most applications.  We can hit this easily - this may be a good test project.  So that is why those surplus IP phones have been sitting there. 

News: 12/19/07:  Our next open workshop is at the Maplewood Fire Station on Century Avenue 12/30/07.  9:00AM-5PM.  The US Coast Guard Auxiliary is discussing starting a Ham Radio Club locally and they are asking about some advice on radio modifications.  I asked Doug to please bring the microscope and fine tip soldering iron. 

News: 12/18/07: We got a call from the folks in Mankato, MN who are interested in our new project.  They have been running a powerful 145.67 packet node down there for years, using our standard naming convention and on a tall government site.  They want to get in the high speed data game.  I think we'll go down there with our slides.  We might try to contact the TCRC or SMARTS clubs down that direction and do a "Southeast Metro" session as well.  

Our advice to them is to start saving their nickels for a D-Star controller ($1200 or so) and some RF modules, at $1400 each.  They have two good sites.  The next big project is to build a high speed data link back to the Twin Cities.  This will take several hops.  We can use Motorola Canopy equipment if we have some water tower sites.  We are building links right now on four corridors- Twin Cities to Duluth, Brainerd and Rochester plus Mankato.  It would be helpful if some of our grants were to arrive. 

News: 12/15/07: The next open workshop looks like the end of December.  It is a busy month at the Fire Station.  We also want to get back at our Mesh Networking via Open Source project. 

News: 12/15/07: It is being reported there is a new U of M DV repeater on the air on 443.425 from Moos Tower - U of M West Bank.

News:  12/1/07:  There was a note on the Minneapolis East Citadel Server from WB0ZKB, who indicated he was getting into the machine from Maple Plain, 22 air miles away, on a 900 MHz paging antenna.  So much for the "short range" argument.  A friend, Kent, KC0DGY, works for a local TV station, and their video remote truck needs to "see" the IDS Tower in Downtown Minneapolis to allow their microwave video feed to work.  He has many stories of various places around town that he knows will work and places that do not.  This reinforces the notion that mobile emergency communications vehicles need towers. 

News: 11/30/07:  We are getting emails from Metro Skywarn who wants to test live streaming video.  It should work.  We have a test repeater...or four or five.

News: 11/25/07: This morning brought a note from Kelly, KB0GBJ asking about our priority list for 2008.  Other than adding some more sites for data machines, we do need to solve the repeater/access point linking challenge using radio, as we are radio people.    Max has installed Ricochet USB (900 MHz Part 15) modems with some of the Linux repeater controllers, and these can "see" light pole mounted legacy Ricochet modems two miles away just on the little folding antennas.  We think putting an actual pole-top unit at each repeater site with a decent antenna might be enough to link the systems that are not very far (2-5 miles) apart.   We are calling this effort "Poor Man's D-Star" as the little modems are $15.00 used, and the data rate @100kbps is similar. 

In the Site Department,  our Mining site covers Downtown St. Paul well enough but we do need coverage South.  We might need to round up another water tank site.   I have another site idea which will be amusing if it happens.   We will be meeting with the MN Department of Health on the 30th, with whom our organization has a separate signed memorandum of understanding.  We gave a talk at the Twin City FM Club last week and a person in the audience slipped us a business card for another good site. 

News: 11/24/07: Our Minneapolis South site is fine, and we suspect has been the whole time.  It was full scale this morning in the Mall of America approach roads, parking lot and by the MSP Airport on a small magnet mount mobile antenna.  The notion of needing to link our machines is key, as they do not have great non LOS range- this is not LA, or Phoenix, with mountains overlooking our cites. 

It was interesting Windows Server 2008 RC1 gives you a "limited connectivity" message on the Ethernet-ID-1 connection, until the ID-1 "sees" the repeater and then the little message goes away. 

News: 11/21/07: Hennepin County is looking for us to come up another 1.2 data machine for a site they have @400 feet.    They have an idea for multiple machines linked via dedicated land lines which has considerable merit. 

News: 11/14/07: The next open workshop is November 18th in Maplewood at the East County Line Fire Station on Century- 9:00 on. 

News: 11/9/07: We are requesting that the rest of the State and Metro Area County Communications Vans and EOCs install ID-1s.  Ramsey County is working on theirs.  If we buy enough ID-1s we might be able to pull in another ARAP aka Repeater from Radio City.  We have lots of sites for another machine.  Metro Skywarn has taken title to the machine now called Minneapolis East based on a second donation from Dan Skripka- thanks Dan.  TwinsLAN is going to try to put some nice block diagrams and code samples on their web site to help others.  We need another work party to do some more development.  

News: 11/8/07: We have received a donation from the Brainerd Motorola dealer of four truckloads of late model FM VHF/UHF repeaters and duplexers and cavities.  We think there are some broken repeaters around Minnesota that need help- talk to K0LAV. 

News: 10/27/07:  We are struggling with what to call our 1.2 GHz data repeaters.  They are not repeaters.  They are not "nodes" as they don't behave like packet nodes.  So since we are a leading user of these devices we are going to come up with a name "Amateur Radio Access Points" - they look more like a $39 wireless router than anything else, and they are simplex, and not taking up two frequencies.  We would like to have the ARRL Repeater Directory list these. 

News: 10/24/2007: I have an idea for fundraising for our D-Star network.  Every Amateur who calls or writes and says we (Amateur Radio) should use the Internet instead of Amateur Radio for backup disaster communications and inter-site linking I charge $1 via PayPal.   If a served agency calls and says they have no possible other way to reach critical data in an emergency I'm OK with providing access to them- but as a routine matter using D-Star for normal ISP Services is on the list of prohibited communications under FCC Part 97.113:. 

(5) Communications, on a regular basis, which could reasonably be furnished alternatively through other radio services.

And there is the tired argument that 30 and 40 year old technology- like 1200 bps packet-  is "all we need"- is interesting in the face of the evacuation of almost one million people from the LA /San Diego fires today. 

http://www.latimes.com/business/printedition/la-fi-cell24oct24,1,68147.story?coll=la-headlines-pe-business

News: 10/21/07:  Max has identified the uplink /DNAT issue with FTP.  He was missing some kernel modules.  This was overlooked during the rush to get the machines built and installed. 

News: 10/19/07: We are looking for signal reports on our Minneapolis South node, which seems under the weather. 

News: 10/12/07: We are getting some mail.  So far in the last two weeks some folks wrote from Sacramento, who are trying to do some modern stuff and getting taken to task for not using packet.  That sounds familiar somehow.  The South Carolina National Guard was next, and then some folks from Virginia working on some aspect of the Republican National Convention.  I want to get a list out of who works on what on our team here so you can go to the right person directly. 

News 10/7/07: It worked!  We operated Medtronic Twin Cities Marathon/TC10 Net Two (Mile 19-22.5) on one of our three new L-Band D-Star-DD repeaters in Downtown Minneapolis to the database server at the finish line in Downtown St. Paul all day today, helping get medical aid to and tracking the locations of several hundred runners who needed medical attention.  More than 16,000 runners were in our database, and there were hundreds of thousands of spectators.   We had hot, challenging weather.  We had 140 licensed volunteers and ran seven voice nets as well as the data system.  Most of the load was on our three main on-course radio nets today, led by Mike, K0BUD, John, N0YR and Bill, N0QHP.   

The Chicago Marathon was today, and in even warmer temperatures had to halt their race after four hours.   Based on reliable sources they ran out of community medical resources- i.e. rigs for hospital transport.  The MTCM is the 8th largest marathon in the USA, and the argument that D-Star is "unproven" in large scale, multi agency planned mass casualty events is now incorrect.  Thanks everyone!!

MTCM Family Medical Information Tent 10/7/2007- six laptops running on 802.11b to our database at the race finish line fed by packet and D-Star DD Mode via our four new L-Band  repeaters.  More than a dozen computers were required to run the medical system- more than can be supported via packet radio, but easy for D-Star.   Pat, KB0OLI,(l) runs the tent.  Note the Yellow Shirts are Hams, the other operators are community medical volunteers.  The use of unlicensed 802.11b allows the integration of available staff into emergency operations. 

KD8GBL was the "Maytag Repairman" today in the data trailer- no troubles were reported on the data system.  Note the ID-1 repeater database uplink transmitter on top of the database server.  145.67 packet radio and TNC is to the right, and 802.11b access point to the upper left. 

A hot day for a road race 10/7/07

News: 10/6/07: A special thanks to Barry Altman who spent most of today testing our system.  At about 5:30PM, after the last route statement was added by KD8GBL  to our production server (with Max on the phone) he reported success.  He could go up to the repeater from 10 miles away in Minneapolis, and down to the remote database server in our trailer at the finish line in front of the State Capitol in St. Paul.   So the notion of the ad-hoc deployment of Amateur Radio assets- users and servers- under D-Star DD repeaters allowing the use of easy to use web applications comes true.  We'll let you know how it works in production after we care for 15,000 Marathon and 10 Mile runners about 3PM tomorrow :-)

News: 10/4/07:  So far for the Marathon, we can report that both the Mining ARC and Minneapolis East D-Star DD repeaters are full scale with no packet loss at the finish line in the exact spot where the MARA radio/database server trailer will go from a mobile Comet antenna on my vehicle hatchback.   The spot for the Hennepin County Van is full scale into Minneapolis East, so we are ready to go.  The South Repeater was not reachable from either site and may have issues.    Dual "Have you Tested Your RF Paths rather than Rely on Luck" awards go to Greg Kitchak, who did some testing a few weeks back and warned me about the issue with South, and to Dan Skripka, who had me do some testing this evening..  One more repeater as a backup would not hurt.  If you have ever wondered why we install data repeaters in threes (the 145.67 packet network is this way) to cover a given area when we are making commitments to people now you know. 

News: 10/3/07: Minneapolis Downtown East is up.  1251.000 /DD 172.16.2.1 /24 the web site is on 172.16.2.20 /24.  This one is at a 33 story downtown rooftop.  The range looks great.  I get one bar (maybe 10% packet loss on beam that was aimed only roughly) on my radio in Shoreview.  Many thanks to a large team who helped here, esp Dan Skripka and Doug Reed who sponsored the system.  We are expecting one more system to go in this week.. 

News: 10/2/07: We will be installing our newest  ID-RP1VS   + Linux controller at a certain Downtown Minneapolis site @30 stories.  This has provided some clarity on our plans- as the Marathon is Sunday.  Dan is making progress on our other Downtown site, and we are asking Erik (the other one) to loan us his machine for that site.  The idea there is we would have also 440 voice/data in addition to 1.2 DD mode.   Note a "DIN" RF connector in the foreground on a cable. 

 

News: 9/29/07: The Icom ID-1 setup software works fine under Windows Server 2008(r) Beta 3- formerly known as Longhorn.  The software works great as a user you just have to turn off all the misc "stuff" on the Ethernet Interface- all the other stacks except IPV4 and all the extra authentication stuff should be disabled.    Broadcast traffic on the Ethernet with IP addresses will be transmitted by the radio... Make sure you have automatic configuration checked on Explorer under LAN options. 

News: 9/28/07:  In the "deadlines are good" department, we have three independent teams working on final prep for two more repeaters on good Minneapolis >300' rooftop sites in the next week.  This would bring the total number of D-Star repeaters in the Twin Cities to Eight, with one more on order, and one in stock up at Radio City.    The goal is to reach the both Net 2 van and the finish line on a challenging RF path.  Greg and Alan have built another 1.2 DD repeater- they have four between them.

News: 9/27/07: We picked up another RP1D / RP1V repeater today from Radio City.  It will go on the first available downtown Minneapolis site in the next week.  We told Dan Fish up there to order another repeater under the"buy five get one free" program. 

News: 9/23/07:  The Hennepin County Communications van stopped by our work session today for the final integration testing of D-Star equipment including an ID-1.  This means three of our best mobile communications assets are now D-Star high speed data capable.  We were able to reach the Mining ARC high speed repeater from the van.  We found a bad Ethernet coupler on a new radio which took a while to troubleshoot.  We are going to try to install two more D-Star repeaters in the next two weeks in Downtown Minneapolis to improve finish line coverage. 

News: 9/20/07: We are going to try to get Minneapolis Downtown East on the air in time...and various other ideas...

News: 9/15/07: We may not be able to reach the Mpls-S repeater/node from the State Capitol.  So the pressure is on to get another good site going in less than three weeks.  Can we do it? 

News: 9/14/07: We are postponing the move to DHCP- it will go in the next release of our Linux appliance code.  The final Marathon dress rehearsal is on 9/23 at the Maplewood Fire Station. 

News: 9/10/07: We sent notes to our served agencies for the D-Star project telling them we were operational.  Whew.  Now to get ready for our 9/16 Hamfest at the Shoreview Village Mall from 8 to 11. 

News: 9/9/07:  We are declaring the first two nodes of our Twin Cities High Speed Data Backbone operational.  Max and Ed just installed the new version of the Linux control computer on the Mining site.  We can cover both cities with the two sites.  They were able to reach both systems from the parking lot of the Maplewood Fire Station today on a portable antenna from Greg's trailer. 

News: 9/8/07: We might switch to DHCP on our systems.  We'll let everybody know.  

News: 9/5/07: The next work party is at the Maplewood Fire Station this Sunday.  We will try for a dress rehearsal on the complete system for the Marathon.  I need to leave early again.

News 9/5/07: We are scrambling to get the Minneapolis Downtown East digital node installed in time for the Marathon.   We are more comfortable with a three node core system rather than just two nodes. 

News: 8/30/07: According to the Anoka Radio Club Newsletter, they are slated to get a D-Star repeater soon courtesy of Radio City.  This one would support 23cm voice/data and 440.  We think 440 is the way to go for digital voice repeaters and low speed data.  2 meters is full and will stay that way in our view. 

News 8/29/07: We have been informed there is today no working "9600 bps high speed packet" infrastructure capability in the Twin Cities any more - there is some revival of it outstate- we have some new maps on the way. 

News: 8/25/07.  Max has tested our new Minneapolis South system from his truck- it's operational.  We can ping it 12 miles out. 

 

News: 8/24/07: Our new L-Band simplex data repeater/node, Minneapolis South, is now operational.  We are at 1298.000, with a new version of the Linux appliance software.  This one supports multiple remote users and uplinks to the repeater from served agencies and trailers, (including Internet and Intranet as requested by agencies), and Citadel, our conferencing/mail/collaboration system, and will allow TCP/IP repeater linking without having to use the as yet undocumented D-Star native linking protocol or linking radios.  Thanks to Max and Kelly for their software support here. 

News: 8/23/07: Note we are going to be using D-Star as a high speed data only backbone for the Medtronic Twin Cities Marathon medical communications.  No digital voice is planned by us for the moment, and we are focusing on Net 2 and Net 3, to replace a "high speed packet" backbone, which has not met our reliability requirements for at least the last four years- it's out of service right now.  No changes of any kind to current voice operations are contemplated for 2007.   The use of L-band also means there is less RF on 2 meters and 440 at the finish line.   We are tired of trying to run lots of updates/queries over 1200 bps packet, which has been 100% reliable but is not designed for this much data volume. The 26 mile course covers a lot of area, and we have to use fixed infrastructure.  No L band is available at Net 1 so they will still use packet.   

News 8/20/07: We were reading the situation reports from the State Emergency Operations Center last night and noticed some possible communications issues in places like Winona, MN due to the serious rain/flooding.  Towns in fact are isolated by road closures.  This is a nice reminder of why we spent the last five summers driving around the State putting up shared infrastructure, and the fact that an end point is in the State EOC says when people need it it's there and does not involve people getting out of bed and driving to set up portable equipment.  We offered one group down in that direction some used equipment to put up a replacement city packet.   We also need some more regional bulletin board systems to be able to post stuff.  Any takers down there?  Note we want to use .67 to access BBS systems but please not to automatically forward mail.  Some of the best nodes in the packet system were put up locally- and can be serviced locally. 

News: 8/19/07:  As we can now document there are more than 12 ID-1 radios alone in amateur operator hands in the Twin Cites, the argument put forth that we should oppose the introduction of D-Star as "more users" are on packet is now incorrect.  (This does not include the 2M/440 radios that have been purchased- perhaps several times that number).  We reviewed the heard lists on our wide area packet digipeaters this weekend - they are few/no actual packet end users evident- there are plenty of node beacons going which is a good thing.   Packet is obsolete from an engineering standpoint any more but is useful when there is nothing else.  We have had a dozen people show up for our D-Star work sessions in the last few weeks. 

News: 8/18/08:  Max has uncovered a mystery involving one of our fleet of RP-1Ds - that it stops responding to pings on the back end Ethernet interface only for ten seconds every minute.  Data traffic seems to still flow- is this housekeeping?   I want to get my test bed going to validate this but re-did my 1.2 beam here and it is pointed in the wrong direction.  And it's raining and there is no rotator.  

News 8/15/07:  We would encourage everyone to read the editorial in the September 2007 QST Magazine. 

News 8/12/07: We are all done testing the Minneapolis South system, and yet another D-Star repeater has been purchased here by Alan.  We plan to install next week.

News: 8/11/07: Next open workshops at Maplewood Fire Station #1 - 8/12 and 8/26.  We are doing final systems integration work on the repeater for Minneapolis South and our uplink system and back-end Linux boxes.  I would like to get an early start (9am) these two days as I need to leave early- 12:30. 

News: 8/8/07:  The electrical and antenna work for the new Minneapolis South D-Star repeater site is now done. 

News: 8/7/07: Served agencies are talking about new high speed radio data networks - one on 700 MHz "Frontline" that works at about 100 kilobits.  This would be similar to what we can get with D-Star.  We could provide a useful backup.  It is being reported commercial cell data air cards (which in some/all cases share cell site bandwidth with cell voice) worked slowly during the recent Minneapolis bridge collapse. 

News: 7/18/07.  We have discovered that you sometimes need plenum rated coax/hardline cable, if run inside of buildings anywhere near air ducts or elevator shafts at least in Minneapolis.  We also learned that you cannot have radio equipment installed in elevator rooms in Minneapolis.

News: 7/15/07:  We are back in contact with the folks doing communications for the Marine Corps Marathon.  This one, with 35,000 runners, is about three times the size of ours.  They are also apparently using a version of trivnetdb, and used D-Star DD mode last year in a secondary role.  They will be using D-Star as primary in 2007 a few weeks after us. 

News: 7/8/07.  Kelly Black KB0GBJ and Max Klingert KB0RSQ from Twinslan solved our "uplink" puzzle.  The Icom D-Star DD mode does not allow one to many connections between ID-1 users.  But DD mode is not IP address aware (it routes only via callsign headers) so does allow us to have a server behind the repeater that all stations can reach, and using destination NAT, (Linux IPtables command with DNAT) many stations can reach that server, and be NAT redirected to a remote server coming in on an ID-1 link to the repeater in another IP address block.  We tested it with 3 ID-1s today.  This will allow a group of system users to access remote databases, servers, or remote Internet or Intranet servers on ID-1s on the repeater.  This was our design goal and we had a few tense moments when it did not at first appear to work.  We do not want to have database servers co-located on repeater sites that are hard to get to.  We can have a small, flash-programmed Linux appliance there instead. 

News 7/4/07:  The 2nd Annual MARA Tailgate Flea Market will be held again in at the Shoreview Village Mall on Sunday 9/16/07 at 8:00AM.  It started last year at 7:30AM but it was still dark.  A lot of amateur radio gear changed hands.  This is at Highway 96 and Lexington Avenue, about a mile E of 35W, and a mile N of 694.

News: 7/3/07: The next open work party is at Maplewood Fire Station #1 on 7/8.  We are going to try to test a full time packet to D-Star gateway.  This would then be deployed.  We also want to test repeater to repeater routing.  Our main issue so far- we want to have our databases in trailers and "uplink" them to our RP1D repeaters.  This does not look possible right now.  One (untested) idea is to have an RP-1D in the trailer, and make the uplink a repeater-repeater hop.  It would work if we uplinked to the back end of the repeater, but that would require another pair of ID-1s, Icom link radios or something like an 802.11 bridge. 

News: 7/1/07: It is being reported that Kenwood in Japan is marketing a D-Star radio  http://www.kenwood.co.jp/newsrelease/2007/20070628.html

News: 6/20/07:  Dan at Radio City has ordered a fourth D-Star data repeater.  This one is for Anoka.  The Icom 10G repeater-repeater link radio pricing is out- $4995 per end. 

News: 6/18/07.  We are telling our served agencies to start ordering ID-1 for their EOCs, vans, etc.  Icom is apparently starting to market the 10G link radios. 

News: 6/6/07.  We are in the final funding negotiations for our third RP-1D repeater.  I think this will give us a very large concentration of data hardware, and puts our main goal, a triple redundant Twin Cities core network like we have today with packet, in sight.  The rooftop site arrangements are going well. 

News: 6/3/07.  We had a big day of testing on our second (WD0HWT) D-Star repeater - there are now five in the Twin Cities.  We (Kelly) got a D-Star to packet radio gateway tested out and accessed the Red Cross Public Website over our repeater.  We had three ID-1 radios there so we could work out routing issues.  We are seeing good round trip delay figures (100ms) to the repeater.  Below the pic (l to r) is one of our RP-1Ds, a packet node, and a laptop running Trivnetdb, really just debian and the AX.25 node software.  The ethernet cable (blue) goes to the port on the back of the repeater and to the laptop.  We made an Internet gateway for by bringing up wireless Internet on the Linux machine. 

 

Kelly Black had a good idea yesterday, repeated today by KC9JIK and KD0ASG - why not set up kids with a "Ham Radio Chat/IM Client" that works over digital radio.  It would be free.  Jabber or another type of server was suggested. 

News: 6/3/07: See us in the Pioneer Press Sunday Paper   http://www.twincities.com/localnews/ci_6048442#recent_comm   Thanks Matt and Sherri.  I was going to suggest in the US we can talk about sports and politics on the air but for international traffic Matt and his Editor did read FCC Part 97- it's in there:

§97.117 International communications.

Transmissions to a different country, where permitted, shall be shall be limited to communications incidental to the purposes of the amateur service and to remarks of a personal character.

News: 6/1/07:  We think there is another donation coming next week to help cover a repeater for Minneapolis Downtown East.  This would give us the required three systems in the core Metro.  Linking them would be useful.  One plan discussed today is to move Erik's machine below from his back yard to a hospital rooftop in the SW Metro for coverage there- say Burnsville.  More discussions planned at the Mining Radio Club /TwinsLAN Swapmeet at 3M Center Sat 6/2/07 7AM-Noon.

News: 5/31/07:  The 14567.org group now has our own D-Star RP-1D repeater,  thanks to Dan Fish at Radio City.  It will be tested with the MN Department of Health Workspace application and installed shortly in  Downtown Minneapolis.  We bought another ID-1 radio, which will go in our trailer, and will be used as the high speed data uplink for the Medtronic Twin Cities Marathon database.   We have yet another rooftop site in negotiations for our systems in Minneapolis.  

News 5/22/07: We are establishing a buying consortium to get a few more ID-1 radios.  We just need one more radio to be purchased from Radio City and Dan will hand over another repeater.  This will go on our new Minneapolis /South site and would cover both downtowns and wide circle of the Metro

News: 5/14/07: A D-Star 1.2 GHz high speed data/digital  repeater was successfully installed by the Mining ARC + TwinsLAN on a good 230' site in East Ramsey County.  The digital voice repeater is on 1285.100 (output), data is on 1299.000 KC0TQI.  We bought an ID-1 - it's plug and play. 

News: 5/9/07: There is apparently some confusion about codecs (which do compression and translation- such as analog to digital voice over IP in D-Star) and codes, which are intended to obscure meaning and are not allowed under FCC Part 97 rules.  We have received written, formal confirmation from N1ND at the ARRL Regulatory Affairs Department that the codecs in D-Star are legal per the FCC.    Note high speed data does not apparently use this codec.  Our plans do not call for the use of voice on L-Band, as the radios we have cannot do voice and high speed data at the same time.  To have a $1000 data radio act like a $130 voice radio is needed only in Japan where there are too many operators and not enough voice repeaters, but not here. 

News: 5/8/07:  We got our first D-Star related grant today.  The grant is from a corporate sponsor, and includes a new 500 foot rooftop site in Eastern Downtown Minneapolis.  This site, and the site at 3M will cover much of the Twin Cities Metro Area for high speed data access. 

News 5/6/07:  Doug Reed N0NAS of TwinsLAN / MN Skywarn helped conduct a successful  test of our web based injured runner applications over a new D-Star data repeater which was donated to MN Skywarn (the NWS affiliated tornado spotters who are all hams BTW) by Radio City of Mounds View.  This machine will be installed in a few weeks on a good site.   On the picture below, left is the Linux server, the ID-1, then the "user" laptop then the donated repeater which is now on the air. 

 

News 5/5/07: At the American Red Cross sponsored Digital Symposium, the ARC representatives announced they have had a strategy change for initial and ongoing disaster response- "we don't use voice radios much any more- our priority is to get high speed data connections to our computer systems we use for taking care of our clients (disaster victims)"     This is in line with our strategy and advice here.  Note they also use IP phones which are an interesting technical challenge to consider for Amateur Radio.

News: 5/3/07: Dan up at Radio City is reporting he has one of the D-Star data repeater sets spoken for, and has a deal open on the second one- any group that buys 3 (now two)  ID1 radios gets the second repeater. 

News 5/1/07:  The next Packet Workshop is at Maplewood Fire Station #1 on 5/6.  We hope to start to integrate D-Star with our Trivnet Linux systems, and to build a packet to D-Star digital gateway.  Doug Reed has one of the Radio City D-Star repeaters in hand.   There is also a Digital Symposium being run by the Red Cross folks in Minneapolis at Red Cross HQ on 5/5 starting at 10:00 AM.  We will be giving the first talk. 

News 3/30/07: Dan at Radio City up in Mounds View has purchased 10 Icom ID-1 radios for stock.  For that under the current promotion he got two complete D-Star repeaters which he is making available for local clubs.  One will be used for software development by TwinsLAN.  He does though need folks to buy the remaining ID-1s so they are not still in his inventory.  Several of us are going to pick one up shortly.  Four or five have already been sold.   If we can get one of the 1.2 G data machines installed we'd like to use it for the 2007 Medtronic Twin Cities Marathon to be "primary" course/metro wide, with packet as backup. 

News 3/28/07: Greg Kitchak, N0GEF has installed another D-Star repeater in the West Metro.  Call is K0FVF

145.150

442.900

News 3/16/07: We had a successful test of a D-Star repeater at our packet workshop.  It is reported there are now four D-Star repeaters on order or in hand in MN so far.  We decided to deploy Citadel systems statewide using solar power and Linux appliance computers.  We will be having a Statewide drill on SET weekend in October.  Stay tuned.  Several new packet nodes have been added to the map. 

News: 3/1/07: Radio City in Mounds View has ordered five Icom ID-1 radios, and got the "free D-Star repeater" with that.  We are talking to Dan about where that should go.  Anyone who wants to buy an in-stock ID-1 from Dan to help him out would be appreciated.  Why do Minnesota people buy radios from South Dakota/Wisconsin  again?  We had a great show at the Washington, DC public health event- lots of interest across the 1300 attendees in Amateur Radio as a backup system.

News: 2/19/07: We have decided to use Citadel as our back end mail and conferencing system.  We still have not heard back on our two/three outstanding D-Star proposals.   We are eagerly following the test results for the first few systems.  Kelly and Max from our Development Team are reworking the command line/tty interface to get rid of every-character echo and going to line by line (cr) echo who is more radio-friendly.

News 2/15/07:  It is being reported as of Sunday there are three complete D-Star repeater systems in the Twin Cities that are in the process of being put on the air by various individuals.

News Flash: 1/22/07: Erik, N0SVX, has ordered a complete D-Star repeater system.  This will include 2M, 440, and 1.2 both voice and data.  More to follow.  First site- Bloomington on 440 - it's on the air.  443.450 (correction)

New 1/7/2007: We are evaluating a Linux BBS/conferencing package called Citadel.  Kelly Black is studying it and has built us an AX.25 interface for it

News: 1/1/2007: John N0YR has donated three 2 meter radios.  These will be used on our new Rochester link.  Thanks, John!! 

News 11/30/2006: We will be presenting our packet/D-Star network and partnership with the MN Department of Health at the 2007 Public Health Preparedness Summit in Washington DC.  http://www.phprep.org/index.shtml - We are building a demo laptop to take with us to the show

News 11/25/2006: From Jerry, N0MR:  The (new 145.01) path to Duluth is running nice and all TheNet, k net, or X1J. Connect to MNSTP then MNHRIS then HINK then WISS. Then you can go to MNDUL, DULBBS, or my mailbox, N0MR-1. Several places along the way you can branch to a cross to 145.67.

News 11/3/2006: The Lakes Area Repeater Association, (one of the sponsoring organizations behind the Statewide Packet Network) now has now co-signed an MOU with the Minnesota Department of Health along with the American Radio Relay League. 

News 10/30/06:  We made a run up to Pequot lakes and now have a APRS station there.  We want to build an Internet APRS gateway using a Linux appliance (Neoware 3000 + Slackware) box in Little Falls.  Little Falls and Pequot now have dual port TNCs- 145.67/145.01.  There is more D-Star interest- the U of M Club is raising funds for one (440 band?) as well.  Our primary interest is high speed emergency data access and supporting our served agencies.  This is "Amateur Radio the Service" in action. 

News 9/19/06: We are announcing our plans to buy an Icom  D-Star digital data repeater.  The first one will go in to one of several secure commercial/governmental sites we have in Ramsey County.  Future repeater stacks will go in Hennepin County, and in Bloomington/Savage.  The systems will be linked via a dedicated microwave radio backbone.  The idea is to support 128kbps digital data and web software based public service applications on Amateur Radio frequencies, and not depend on commercial network services to back themselves up.  Each high speed node site costs $3000.  

 We are big fans of radio based backup systems.  Many have suggested we use the Internet as a backup system in case the Internet fails.  This does not seem to be a sound engineering practice.  We are not planning to become an ISP, which on a routine basis is prohibited under FCC rules anyway. 

Users of Icom ID-1 radios (10 watts, the fastest and most powerful data radio on the market in any service) will be able to use the system to access public service applications, mail, and our two Statewide packet radio networks as well as the TwinsLAN Metro Area network.   145.67/145.01 packet users can also reach the same applications and the D-Star users via a Trivnetdb Linux gateway. 

News 5/15/06:  We have decided to deploy regional mail server/BBS systems on the 145.67 network.  (Thanks Jerry, N0MR).  In the event of a disaster or incident, amateur radio packet  users can go to the nearest BBS system, for updates and instructions.  Bulletin messages to "all" (SB is the command) ) can direct people to which callsigns are in use for an incident.   We are also using Trivnetdb on Linux as an application for delivering services on the 145.67 network.  Multiple users can connect to these servers  and access databases for missing persons, and also build new databases (!) such as for Pan Flu work and use the conference services.  The KC0LQL node and Trivnet have a conference service- sign in with your call or tactical call (such as the first six letters of the County name for Public Health Officers).   A grant request is in for an Icom D-Star system to provide high speed web access between 145.67 locations, 145.01 locations and critical medical locations.    

Icom ID-1, RP-1D and D-Star L-Band General Advice

RP-1Ds are very easy to set up.  Plug it in, set the callsign, frequency and IP address/mask via the USB connector and Windows software.  Set the Ethernet to "on" and turn off the gateway and links (unless you have some).  Then you are good to go.  Computers and ID1s in the same IP subnet as the repeater can now talk to the repeater, and the Ethernet on the back.  We are not fans of DHCP at this point.  If your radio does not talk the repeater assume you have RF path problems - the repeaters and protocols seem bulletproof to us.  Do not put an ID-1 or a repeater controller on a busy Ethernet hub.  They can act like bridges and will bridge all kinds of trash onto the RF path

This frequency band does not provide the "bonus propagation" we have seen on 2 meters.  On 2 meters, in our experience, if you put a radio and an 18 inch piece of coat hanger in the air you are good to go. On microwave bands you need line of sight coverage and good antennas and connectors and feed lines. 

We have not had good luck with NMO mobile antenna mounts on 1.2G-Alan says they do not look good on his analyzer.  The Comet N base mobile antenna systems work great.  Radio City stocks them.   I have used the Comet 1.2 mobile antennas for years- they are rated to 2.4Ghz.    

Invest in an SWR bridge for this band.  The Comet CM-120 was about $70.00.  You put your ID-1 into FM mode, and press the Push to talk button and ID and you get 10 watts of RF to test your antenna.  The lack of obvious adjustments on the repeater (none) is good news and bad news.  The bad news is you can't tweak anything.  The good news is these are plug and play RF wise and you don't need to tweak them. 

The ID-1 settings are a little mysterious.  For one to work you need to set it up, and have a good signal to the repeater.  On the left is the signal going up then the right is the signal coming down.  If you are not seeing displays like this it is likely you have an RF problem.  You can test SWR- get an SWR bridge (Comet makes one) and put the rig into FM simplex, tune to a proper FM simplex frequency, key the mic and ID.  It's tricky to test SWR on the digital signals.  In the case here, KE8TX is the repeater. 

 

1. Computer set with an Ethernet interface on the right fixed IP address and subnet.  We do not use DHCP currently (other groups might be)....   So for the Mining ARC system you might use 172.16.0.56 as an address for your PC (2-254 are legal, skip .20) and 255.255.255.0 as the subnet mask. We have tended to set the default gateway to the base address of the repeater or the Ethernet on the repeater 172.16.0.20 - no data here on what is best-  you can set a DNS server- use the Ethernet address 172.16.0.20    Turn off all the other services on the interface- Netbios, 802.1x, etc.  For starters, turn off your other Ethernet interfaces, Internet, etc just until it works the first time.  This seems to work both with and without a default gateway set. 

2. Use an Ethernet cable not a crossover.  And not a switch or hub unless you are the only station(s) on it. 

3. Turn on the ID-1 and put in your settings - you need to set your personal callsign "my"   TwinsLAN/3M repeater: Your: KC0TQI A  RPTR1: KC0TQI G    GW: checked  - the gateway symbol tells the repeater to direct traffic to the Ethernet interface on the repeater, which is either off, running the Icom Gateway Software or in our case, a Linux appliance running our web server and DNAT etc.

4. The Ethernet should come up (layer 1/2) on the computer, and the lights on the radio should flash when you ping the repeater, and you should see a little boxed lightning bolt flash (xmit) and a little three bar s-meter symbol flash (rx data).  The callsign of the repeater should flash on the radio display. 

5. If that works you can try the repeater web site - 172.16.0.20 - if that works you are good to go. 

I have this working on Windows Server 2008 RC0 in my lab here, and it works with XP and Linux.  The ID-1 programming software does not yet support Linux.  I have the Internet going on one computer interface and D-Star on the other today - that is pretty cool. 

----------

Don't even think of antennas with less than about 11-14 dbi of gain - losses are everywhere on this band- discones are rated for 1.2 but are useless

Long cable runs are not your friend.  This equipment will not work on towers with the gear at the base unless you have top end hardline  (1 5/8" like the cell phone folks use)

We think remote mounting of the ID-1 base unit is a good idea.  It draws 7 amps and is rated for 14f to 140f - not bad.

A PL259 connector is dummy load at this band- use only N/SMA/BNC/DIN connectors (there in an N plug out that is like a PL259 and easy to solder on)

RG8 coax (and RG8X and RG58) works very well as a dummy load on this band. 

Excess coax adapters and jumpers cause a lot of loss

Make sure lightning arrestors you use are rated for this band

Beams are good- very good in fact - we are trying some corner reflectors next

Slight antenna movement /adjustment might help - we aim antennas with ping- fire up "ping -t" under Windows(r)  to your repeater, and aim the antenna until you get the fewest lost packets.  The inventors of ping might be surprised by the use of their software for aiming antennas. 

Our experience is the general behavior of radios, repeater range, etc of 1.2 is like 440 - NY9D designed and built a 1.2 FM voice repeater years ago from scratch and ran it for years - even published an article in 73 Magazine on it.  Accept no "advice" on this band from people who do not own/use/build equipment for it.  There are many myths around.  That analog machine might reappear on the air. 

ID-1s do not seem to have IP addresses - they just use callsigns - your data goes encapsulated in callsign headers .  We are not using DHCP- your computer on the ID-1 needs a fixed address in the same range as the address on the repeater/gateway you wish to reach or other station you wish to reach.   Other repeater owners may be using different systems.   We are using fixed IP subnets, a different one per repeater.  The idea is then we can use a router to link the back end Linux systems. 

We see around 100ms of per hop RT latency on ID-1s

L-Band DD mode is not duplex- it's simplex, so excess broadcast packets, unattended data streams, linking on the same channel are not good.  These are called "repeaters" but are not in the FCC sense of the word.

We have had good luck with two multiband antennas here- the Comet GP95 *** ($160) and MFJ 1532N ** ($99)- 4.5db (2m), 8.3db (440) and 11.7 db (1.2)  - both are one piece and suited for building tops and tall places

Doug Reed N0NAS (9/9/07) thinks ID-1's don't mind having home type routers attached to them- you can support multiple TCP/IP sessions through one radio-radio (callsign to callsign) "tunnel" in essence- not a hub/switch with a lot of devices on it...The radio otherwise takes all it hears with an IP address on the Ethernet wire and sends it out the RF end. 

Windows Update is a good thing but not with D-Star + Internet gateways.  If your computer wants to check for updates and it thinks there is Internet someplace on your D-Star system it will fire up and go- the Marine Corps Marathon folks found this out during their race.

 

D-Star Project Phases

D-Star equipment, like packet equipment, can be purchased and installed by anyone, and operated by a person with a valid FCC license.  The whole digital voice with Internet linking aspect of D-Star is interesting but out of scope for our purposes, based on the requests we have from our served agencies.  Their focus is high speed data. 

Phase 0 - The planning phase- complete

Phase 1- Initial single site repeater purchase and installation - Complete 5/14/07

Phase 2- Minneapolis  South site installation - Complete 8/24/07

Phase 2A- Minneapolis Downtown East site installation and Live test at the Medtronic Twin Cities Marathon 10/07

Phase 3- Link testing between "repeaters" i.e. Motorola Canopy or Ricochet or ?? Underway

Phase 4- Five Node System deployment in the Twin Cities by 9/1/08

Phase 5- High density corridor deployment- Twin Cities to Duluth, Rochester and Brainerd - this will be tricky as 15 mile hops will need lots of sites/towers and gear

 

Prioritized Project list 9/09 and targeted dates and owner:

These projects are managed jointly by the 14567.org team and Twinslan.  We hold monthly open workshops- new location is in Golden Valley.  
 

1. Raise $1400 to get a D-Star 440/UHF repeater radio module for the STPONE site.  There is a critical mass of voice activity and we want to encourage that and get some testing in on the low speed data mode.

 

2. Buy a D-Star repeater controller and 1.2 data radio for a new, 600 foot site in Washington County that has been made available to us.  This is $3000.

 

__________________________________________________________________

D-Star Digital Voice Etc

We are not for the moment in charge of area D-Star digital voice deployments, Internet linking, Icom Internet gateways, etc. 

We are not big fans of 1.2G digital voice- why use a $1000 microwave ID-1 radio for voice (and it can't run high speed data at the same time) when a $120 VHF-FM radio will do? 

We are rolling out 440 voice and low speed data if we can get some gear/funding.  You can loan us gear- we'll give it back.

The 2 meter D-Star voice repeater channel pair situation is looking better nationally as of 2/19/08- one of the repeater councils is refarming the band.  There is a thick "preserve legacy modes at all costs" fog around here -we were getting a little cynical. 

   

------------------------------------------------------------------------------------------------------------------------------------------------

D-Star DD Mode FAQ 2/15/08

1. Why are you using separate IP subnets for each repeater?  This makes us reconfigure the Ethernet on our computer when we change repeaters.  We don't understand the linking protocol Icom uses, and can't afford to buy the official link radios @$5000 per end.  So we will have to link the Linux appliance computers themselves.  You can't IP route easily between the same subnets.  So we are setting up separate subnets per repeater.  You just pick an IP address ( not .1 or .20) and go. 

2. What about Kenwood and Yaesu?  Kenwood has announced a D-Star radio in Japan.  My take is they are doing everything they can to fight D-Star.  They have plenty of support in this battle.  The full page "Packet is the Future" ads from Kenwood. are a hoot.  We'll see who wins :-)

3. What is the range on 1.2?  It's about like UHF.  Line of sight - so 10-12 miles from a big rooftop for tower-tower.  It is whatever the RF Path Study says.  There is no magic. 

4. What do you mean by Internet?  We use "The Internet" to refer to the commercial information service.  We use TCP/IP over Amateur Radio to refer to our plans for linking, and is the underlying protocol at some level for DD Mode.   We use TCP/IP over 802.11 (Part 15) as a linking and short range option as well.  The use of Part 15 off the shelf technology and frequencies allows encryption, Internet access and does not require licensed control operators.

5. The cost of ID-1s is a big impediment for home stations and casual user adoption.    Yes that this true but we want to build credible shared infrastructure and deployable assets.  You can get on AX.25 packet radio for $50- but almost no one does.   The role of casual home users in tactical, large scale emergency services is not clear to me.  In Pandemic Influenza under quarantine type conditions, this is of course different, but home users would not need high bandwidth?  So existing packet, low speed data, Airmail, Winlink 2000 would seem fine. 

6. Can you use D-Star DD for routine public Internet access?  No - it's not legal.   Other/commercial radio services (Satellite, 2G/3G, 802.11 etc) offer commercial Internet over essentially the entire USA. 

FCC Part 97.113:.  (prohibited Part 97 operations)

(5) Communications, on a regular basis, which could reasonably be furnished alternatively through other radio services.

7. Is the D-Star portion of this project being done with the support and or endorsement of the ARRL Dakota Division or MN Section.  No. 

8. Do you support encryption?  No.  You don't need encryption to provide many forms of backup emergency communications.  All forms of commercial communications support encryption, and if they are calling us (Ham Radio) things are bad.  You can creatively solve some short term message authentication problems with one time pads of unique message sequence numbers, and tactical names for sites, etc.  Operators of digital message forwarding systems on the other hand are required by the FCC to authenticate users to limit their liability on illegal traffic.  For that we think a digital signature aka "digital callsign" is a good idea.  A digital callsign does not obscure anything.  And we can see an agency wanting to use an SSL protected website.  This is fully legal in an emergency, and  not legal on a routine basis so we are covered. 

9. What do you tell served agencies?  We say we are the fifth tier emergency communications network for them.  "If all else fails" as the ARRL bumper sticker says.  

Normal commercial data services > Normal commercial voice services incl. Fax > Normal commercial wireless services > Sat phones > US

10. Do you worry about having a single platform vendor.  No.  80+% of the routers in the world are from one vendor (Cisco) so it has not been an issue there either.  

11.  Is this network a "Common Carrier" that competes with other Common Carriers?  No.  A Common Carrier (see Wikipedia) serves the public.  This network only serves FCC licensed Amateur Operators on Part 97 frequencies.  

------------------------------------------------------------------------------------------------------------------------------------------------------

Packet Radio Section

As the owners and long time operators of more Amateur Radio AX.25 packet radio equipment than anyone else in at least five states, we have been big fans of AX.25.  It is just is too slow for modern applications.   And it's hard to find and train operators on the character mode interface.  400+ Million people can use a web interface without training.    So we'll keep our old network going as long as we can get parts and there is not anything newer and better.  And it works when there is nothing else.  This is a hobby, and we follow the letter of the FCC rules - if you are interested in advancing the state of the radio art, AX.25 packet radio is not the place to do it.  Running big networks counts a little I suppose. 

---------------------------------------------------------------------------------------------------------------------------------------------------------

Minnesota Packet /APRS News: 

News 11/14/08: MNMONT is back on the air on 145.67, and has a good signal south and a little east from Monticello.  Ideally, it would go more north east to help out the Central Minnesota Hospital Project, which is roughly on a line from St. Cloud to Duluth.   

News: 8/5/08: We have a new 145.67 backbone packet node- MNMLR- located near Garrison, MN.  Thanks Jerry and Al for the report here.   Jerry, N0MR is reporting they are building a bit of a 440 packet radio backbone mid-state. 

News: 6/29/08: We are burning in the newest solar packet node.  The charge controller is working fine and it should be ready to install in a week or two.  The priority project seems to us to be the Rochester/Twin Cities link.  The idea is to get that working with a primary path, and then add a second/third path. 

News: 4/12/08:  We got some notes and calls this week.  Jerry says the work on MNSTP has disrupted the Twin Cities end of the 145.01 packet network.  MNWBL has an ancient radio on the 145.01 side which has failed.  This is true.  We need to find another NE metro site for 145.01 to get some more redundancy in place.  The Hospital Compact folks are asking about packet/FM voice radios and drills and training.  We sent them on to those in charge of that project. 

News: 2/20/08: Two of the KAM units we got yesterday upon closer inspection turned out to be "Enhanced" units in disguise.  So these could be used for Airmail, which is a Pactor based HF email system.  Some of the mail BBS systems set up to accept Airmail connects over HF radio still take connections from slow legacy Pactor 1 systems.  So these TNCs are useful- you pretty much need to pair them with an HF radio with a digital frequency readout in my experience to get to these BBS systems.  The latest gear for this is Pactor II I think, but the modems are $1000. 

News: 2/19/08: We got short of repair parts for our packet network and stopped into the Amateur Radio Consignment Center on 632 Prior N (just North of University Ave) in St. Paul.  They are open Tu/Th 4-7PM and Sat 9-Noon.  651-644-3102.  Paul the owner has been a huge supporter over the years, and he had three Kantronics KAMs waiting for us tonight at the right price- about $20 each.  He has supplied about 20 TNCs to us and some radios since 2001.  His stock of vintage parts such as large variable capacitors has never been better.  ARCC is our "other" ham radio dealer in the Twin Cities, and along with Radio City have been invaluable. 

News: 2/19/08: MNCLK is back online.  We waited a day for the holiday and got in there today over lunch and replaced the TNC.  The last site visit was in 2003.  

News: 2/17/08: Jerry is reporting MNCLK is offline.  He says the TNC is spewing "A"s - these lose their minds about every five years and have to be rebooted.  We'll get up there this week.  MNMONT - our backup to MNCLK is offline- long story- so we'll make fixing it a priority.    

News: 1/23/08: We was curious if cold weather impacts our packet network- it's four degrees F out -and the answer is no- all of the links are fine.  These path were over-engineered in the first place. 

News: 12/15/07: We got an email asking us to increase the Twin Cities APRS backbone coverage.  We are not fans of home made repeater/node equipment on our commercial/government sites, so if someone were to hand over a late model type accepted radio, attached to a late model Kantronics TNC (MTBF of six + years) and a switching power supply, we might find a home for it.  Fussy equipment you have to go and tinker with every few months is unprofessional and annoys our site owners.  This is 1980's technology...long since perfected. 

News: 11/25/07:  There is not much on the air in the Twin Cities on 145.01.  I was trying to test some old Kantronics DVR2-2 crystal controlled radios on that frequency.  These are good for solar power.  

News: 11/20/07:  The parts to make another solar packet node are in stock, so we are going to tackle the Minneapolis/Rochester link situation.  We have a site in mind in River Falls, Wisc.  The new link as is is not very solid.

News: 10/1/07:  From W0STV: We have the MNROCH 145.670 node up and running. We are running an Icom V8000 running a KPC + at 25 watts since the power supply is not big enough to run at full power. We will have it at 75 watts by this weekend. We have already made contact with the Maple node. Please inform Austin and Winona to try the node.  

Nodes heard 10-01-2007 by MNROCH

MNRUSH

MNISLE

MAPLE

MNMSU

HINKMN

 News: 9/26/07: New maps, including some for the 444.125 development are coming from Jerry and Kelly


 

-----------------------------------------------------------------------------------------------------------------------------------------------------

Legacy 145.67 1200 BPS Packet Wide Area Node Status as of 8/1/2009:  These are mostly government/commercial grade nodes or others with unique capabilities and is not a complete list- we are not listing home stations for the most part.  Note if a given path seems to be not working, try a longer one- long range propagation is common on this band, and disrupts short range paths.  Bold indicates these are critical backbone nodes that we strive to keep on the air to a high degree of reliability. 

MNMLR - Garrison, MN (*** New*** 8/08)

MNWBL White Bear- - Not dual band but both channels are on the air.  (4/08). 

MNBRD Brainerd - Brainerd ARC 

MNWBS - Wobasso (Redwood County) NEW*****  KB0CGJ

MNCCC7 Matowah/Duluth (c to MNCCC to reach MNDUL and FWD in Duluth on 145.01)

MNLF2 Little Falls- 244' HAAT.  Good RF path to MNBRD, WILMAR, MNCLK!  We have an APRS node in Little Falls also on the top of the tower at 213'!- N0NAS-11 - try it via http://www.findu.com/  *Now dual port 145.67/145.01 10/14/06.  If we had some money this would make a nice anchor for a high speed backbone Minneapolis-BRD. 

MNBLM Bloomington

MNFRBL-  Fairbault - nice node/BBS -W0NKA - Might be a big help on rebuilding our Rochester link

MAPLE Maplewood- 280' - Best route to most places...- Please in a declared communications emergency, this node should be reserved for high priority official traffic  

MNRUSH- Rush City -  Now has APRS node (for MS150) on backup antenna .   Works MNCCC7 (Duluth) direct

MNPEQ Pequot Lakes - 145.67 node up, New* 145.01 crosslink and APRS  - 

MNMSU Mankato - powerful node and BBS

MNSAND- Sandstone- good path to MNCCC7 and to MNRUSH

MNMPLS Minneapolis #1 400'-  Has nice path direct to MNCLK, WILMAR

MPLSDN Minneapolis Downtown 400' 

MNCLK- Clear Lake-  140' - works MNLF2 and all Twin Cities backbone nodes direct. 

KC0LQL - St. Paul- Test node for our LINUX version of ARES-Data trivnetdb by Dennis Boone, KB8ZQZ- See us in February, 2004 QST Magazine.  Connect to the node then to db to use the Trivnet interface.  Has a conferencing system.  Near MAPLE for easy access.  We are running Debian 2.6 on our production systems. 

WILMAR- 400' in Willmar, MN.  Very good coverage to Wobasso, Mankato, etc. 

MNAUS- !

MNWCEM - Minnesota State Emergency Operations Center, St. Paul 

MNDSN - Dawson, Minnesota   ***NEW

MNROCH- is back 10/1/07 !!! We need to develop a new range circle for the site. 

MN/WI Packet BBS List- Thanks Jerry, N0MR (Statewide Packet Network Operations Manager for these)  - Plan is for one BBS per State EM Area.  These came from donated laptops.

Minnesota Area Packet BBS's Updated 8/09

 

Following are the major packet BBS's in the area along with the frequencies.

STPONE    St. Paul, Citadel on 145.01

STPBBS      St Paul                 145.63, 145.01

STCBBS      St Cloud          145.67

HUTCH Hutchinson        145.67

BRDBBS      Brainerd          145.67, 446.125

ISLBBS      Isle              145.67, 446.125

DULBBS      Duluth                  145.01, 446.125

BALBBS      Balsam Lake,      WI   145.01

 

Jerry, N0MR

 

145.01 1200 BPS Node Status as of 8/13/09

STPONE - Our Packet/D-Star node on a nice downtown St Paul site @260 feet or so. 

MNGPZ - Grand Rapids

MNWBL - White Bear Lake

MNLF1- Little Falls- Dual port 10/24/06

HINK- Hinkley

MNHRIS- Harris

MNISLE- Crosslink .67/01 + new Telpac node w0kgw-10

MNNWD - Norwood Young America

MNDUL- Duluth .-01 gateway, reached on .67 via MNCCC7 then MNCCC

MPSTP- Twinslan link - Woodbury location- now (4/08)  linked to MNSTP D-Star repeater for Citadel etc- has various issues 6/09

WISS- Duluth area

446.125 Maps and Status - thanks Jerry N0MR - stay tuned

 

Solar Powered Stations

NY9D - Near MNWBL - 2x 15 watt panels ($80 each from Northern Tool) and a charge controller and a deep cycle Group 24 battery are enough to power a Kantronics KPC-3 (turn off the LEDS) and mini-mailbox, NY9D-1 and a Kantronics DVR2-2 3 watt radio.  You could also use an HT here for your radio.  The idea is this is a fully survivable BBS that would work in a prolonged regional power outage, as has happened. 

Disaster Plan

In a declared emergency, an activation message will go out over the National Traffic System (NTS) and other methods (i.e. local repeaters).  Most likely, one or more BBS systems on the network will be designated as the dissemination point for official bulletins and message traffic for our served agencies, primarily hospitals and MDH.  Please stay off of the main backbone nodes and 145.67 in this situation unless you have official served agency traffic as the Statewide Network (we share just one 1200 bps radio channel) has very limited long distance surge capacity.  There are many other designated packet radio channels -145.01, 145.03, 145.05 etc. (including the Twinslan backbone) where non-essential /H&W/supporting/local  traffic can go during such an event. 

Links

  • http://training.fema.gov/IS/NIMS.asp The FEMA Emergency Management courses (IS-100 etc) are very good.  These are mandatory these days for emergency responders.  It pays for anyone involved in disaster response to get to know the lingo at least. 
  • Twinslan- Twin Cities Amateur Radio Data  - They are the sponsors of the monthly open workshops 
  • http://home.att.net/~lakesarearptr/index.html   The official site for the Little Falls #2 tower
  • http://www.packetradio.com/- The place for radio-TNC cabling diagrams
  • http://www.kb8zqz.org/trivnetdb/  - KB8ZQZ's trivnetdb page- a modern TCP/IP + Packet + D-Star capable LINUX replacement for ARES-Data !  We are using Linux systems as D-Star back ends as the Icom D-Star gateway software is a little mysterious
  • The American Radio Relay League - the National organization of Amateur Radio www.arrl.org  Look up clubs, hamfests, info. 
  • The Magic Repeater Site- good local info  http://www.magicrepeater.net/
  • DstarPeter's D-Star site - he is one of our software architects

General Notes

More nodes and antenna sites are always needed... Send us email on this. 

For those interested in high speed packet / Internet / TCP-IP / APRS /D-Star see www.twinslan.org.

We are already at Phase III of the D-Star core data network.  We have four repeaters up of ours, and a an on-air spare.  Linking repeaters is the next project, as we solved the remote database/uplink issue. We are looking at Motorola Canopy(r) or Ricochet(r) equipment for linking. 

High speed amateur radio data is here, and older analog/FM/packet radio technology won't support data rates much about 9600 bps reliably.    All of our served agencies expect us to be able to support web based applications, which won't work on legacy packet radio.  All new radios we purchase for the network backbone with donations or grants will be D-Star capable. 

Most/all Winlink 2000 / Telpac / Internet based work sponsored by the ARRL is going on mostly on 145.01 and on 440 packet.  This application layer technology should work just fine over the 145.67 and D-Star backbones.  Twinslan is supporting this effort as well.  We are providing sites and equipment as we have it surplus for this effort.  

To keep the long-haul links open for emergencies, please no 1980's type BBS-BBS automatic mail forwarding, APRS or DX spotting on the .67 network.  Manual, human driven access (Telpac etc) to mail, databases, BBSs etc is perfect!   The old packet BBS mail forwarding system, yourcall@anothercall, seems pretty obsolete to us. 

Beacons are encouraged out-state, please set "beacon every 250"- Note some Twin Cites stations are beaconing too often please....

How you can help:  The MARA (our sister organization) is a MN nonprofit, (not a full 5013C though) and we are always seeking radios, antennas, certain computers, TNCs, etc.  Any surplus for the core network is redeployed to supporting projects.  Our older radios and TNCs have gone to the 145.01 backbone as an example, and we redeployed donated older laptops to build BBS systems.    A nonprofit organization called 14567.org drives the overall network design and operations. 

It is being reported that 145.67 MHz is being proposed as a simplex calling frequency for D-Star nationally.  We got to this channel in the first place by escaping from tight "guidelines" on the use of the normal packet radio frequencies back in the 1980s.  We think frequency sharing will work, but changing all these nodes over would be a pain. 

Basic directions from any PC terminal program to any TNC:

Turn on station.  Usually radio volume set to 2 O'clock.  Set squelch to normal, unless you have the TNC set for software squelch, then you can have the squelch open.  The TNC should hear a beacon from nearby nodes or other stations.  You should see a command prompt from your TNC or hit control C to get one. 

MH     will list stations recently heard by your TNC

Our you can use the map and try a node.  From the command prompt (control C will get you to command prompt if you are not there)

C nodename   (like C MNHUGO)

If you are successful, the node will say *connecting* or *connected* or the like, and give you a little header back and command line.

J

Will give you a list of recently heard stations at that node. 

N

will list nodes heard

From the node command prompt, you can C to stations the node has heard.

B will disconnect you from the node.  Or, you can hit control C, get back to a local command prompt, and enter D to disconnect. 

The basic idea is to listen for a station (hopefully a powerful node), connect to that node, and use the node function (KA-Node) in the network to hop to stations you need to visit.  Normally, you can start a keyboard-to-keyboard with another ham by connecting to their callsign either directly from your TNC if they are nearby, or through a node if they are distant.   You can connect to a regional BBS system (like DULBBS) to get mail and bulletins and send notes to other stations in your area. 

__________________________________________________________________________

Build a Packet Node Directions:

We suggest later-model (KPC-3 or newer) Kantronics TNCs unless you have experience with "Node" type firmware. Very early Kantronics units (KPC1/2/2400) do not have a transmit timeout timer, and can/do lock up....

A hardware reset is always a good idea.  Take all defaults. 

You need to turn on the KA-Node:

Numnodes=4    is one we pick

Mynode=MNLLLL   where LLLL is something useful like an airport code

We do not suggest using myalias- if your alias is the same name as your node, the node won't work

Antennas and radios and TNCs need to be grounded on a common ground system.  A small UPS is nice and it might take the brunt of a AC power hit. 

Note: ANY terminal node controller (even computer sound cards) you find will work for a "user station" - try it!

------------------------------------------------------------------------------------------------------

Advice for Minnesota Hospitals and Hams working with hospitals 3/08

Jack Maus, W0MBD has been spearheading a project out of St. Cloud to get hospitals in Minnesota to develop reliable backup radio communications capabilities.  Amateur Radio is a good way to get this job done.  This supplements phones, faxes, sat phones, etc.  Think about what you do when the systems you use every day stop working.  What they are doing:

1. Find licensed Amateur Radio operations in the area of the hospital- www.qrz.com   has a lookup function- you can search by zip code to find local operators.  (Note: - Amateur Radio operators are individually licensed by the FCC.  You are not required to work with any specific groups or organizations.  You can pick and choose individuals or groups that best meet your needs as an organization).

2.  Decide on your plan- most hospitals (40%+ of all hospitals in MN so far) are putting in FM VHF/UHF voice and data capable radio systems to start.  These are called "dual band 2M/440 FM" radios in ham lingo.   We are now (9/06) advising hospitals to purchase only D-Star capable equipment.  This equipment was not available until recently but is fast and modern.  We will be installing more D-Star "repeater" systems over time as we get grant funding and donations.     The main D-Star data system is 90k bits/second using the Icom ID-1 radios, which is fast enough in production here for web based applications like the Minnesota Department of Health Workspace and the Red Cross Missing Persons database.  The Icom ID-800 (and newer models) radio will work with current FM voice, current packet (via an external TNC like the KPC-3) and is ready for low speed D-Star. 

D-Star and the ID-1s have been plug and play for web based applications and Internet access in our testing (5/7/2007).  You can use D-Star for hospital-hospital use as well. 

3. Put up a permanent outside antenna (or two).  Hospitals are often heavily built with lots of metal framing/rebar and are well shielded against  radio signals getting in or out.  A well-grounded 8 foot fiberglass whip "Tri-Band" like a Comet GP95 is ideal on the roof, with a 1/2 inch diameter coax cable like LMR-400 run to the emergency communications location inside.  Better coax cable (like 1/2 inch hardline or 7/8 hardline- Andrew etc) is a good investment.  A source of reliable 12 volt DC power at >10 amps is required.  The two/three piece inexpensive fiberglass ham antennas with black plastic center couplings do not hold up well on tall commercial roofs due to wind flexing in our extensive experience. 

We visited a corporate Security Operations Center recently.  It was very well done and very cool.  But it was indoors away from windows and hand held radios and cell phones were well shielded.  One idea mentioned by Greg Kitchak was to have an antenna on the roof, and a piece of feedline to the operations center, and another antenna of the same type inside the room, which would act as a passive repeater of radio signals.  One would be tempted to do this for whatever public safety radios were used, so when the Fire Captain or Police Chief shows up to help you in an emergency, his/her radio would work.  Just having an antenna on the roof and feedline and the right connector might also work, so they would plug in their radio if the built-in antenna could be detached. 

4. For voice, you are all set to talk to the 11,000 licensed hams and the 200 amateur radio owned and operated FM analog voice repeaters in Minnesota for a 10-30 mile range.  For packet radio, connect to your nearest "node" above.  You can then connect to the station you are asked to connect to for the drill, etc.  Conferencing is available at the BBS locations on the map above.  Regional bulletin board/mail servers are being deployed in all areas for mail use. 

5. The MN State Warning Officer (3/06) suggests that Hams do not rush to hospitals if a Pandemic Influenza outbreak is reported, as they would be subject to quarantine.  Stand by at home for instructions.  

6. Get to know your local MN Public Health Officers (one per MN County) as they have a critical /leadership role in health emergency management.

7. Putting in Amateur HF equipment and antennas gives you advanced capability including Statewide/National/Global range and access to HF Airmail, a radio based email system.

8. There is a strong interest by some groups in building new 2 meter legacy analog FM voice repeater systems.  There are almost 200 amateur owned FM voice repeaters operating in Minnesota, and no more open frequency pairs for new ones on 2 meters.  Use/support/upgrade the ones we have.  

9. Given the investments that our Minnesota Amateur Radio dealer, Radio City of Mounds View, has made in emergency communications ($60,000 worth of D-Star inventory in 2007 and six donated repeater systems) we are baffled why so many hospitals are buying their amateur radio gear from out of State.

10.  Hospital employees can get an Amateur Radio license, but need to be careful of the legal restrictions on being paid to use Amateur Radio.  So you can supervise and coordinate the work of volunteers.  But you can't send messages while being paid.  You can use the equipment in a real emergency, to help protect life and property.  Just not on a routine basis. 

11. Beware of the need in some cases to run (costly- $10/foot) plenum fire rated coax cable for radio signals inside of buildings.  Read the electrical code carefully.  Ground everything.  In our experience with >20 sites over 20 years, we have never ever had properly grounded radio equipment or antennas hit by lightning.

12. The Amateur Radio Service is not allowed to use encryption on our radio frequencies.  We can help you build encrypted databases, and encryption is allowed on commercial equipment and frequencies, but not on our radios.  So moving patient specific condition information is not in the rules.  There are lots of things we can do as community volunteers to keep your facility up and running and taking care of patients in a disaster without transmitting medical records information on our radios.  We can handle logistics and assignment of people and track the location of patients.  We are an ideal link to the outside world, but if it's a HIPAA issue, we will turn to a commercial device or service.    For the Marathon, one of our folks does handle and safeguard sensitive health records on a computer but it's one on one, in our role as backup IT staff in field medical facility - a role we might play in a real emergency.  So in an emergency, you have five doctors, six nurses - do you take someone with patient care skills and have them run a computer, find a printer with paper in it, and repair the diesel generator, or do you call us? 

Advice for new or prospective Hams  7/26/06

Get yourself a scanner or 2 meter handheld radio.  Find a local repeater serving your area (146.85 Mhz FM or 147.21 or 444.100 are good ones in the Twin Cities).  Listen in.  Find out what is going on in your area.  Repeaters are listed in the ARRL Repeater Handbook - in Minnesota it's the Minnesota Repeater Council.  Buy a copy of a license book "Now You're Talking" is a good one- there are others.  Study up or take a class.  Find a local volunteer (VEC) exam team (www.arrl.org or W5YI or other sources for that) .  Once you have your license, please do not just rely on people you meet on local voice repeaters for your exposure to the hobby.  Repeaters are privately owned, and may or not be hospitable to newcomers and only represent a subset (small) of the 11,000 licensed operators and amateur radio modes and frequencies in Minnesota as an example.  HF is usually the best place to meet fun hams.  Local clubs can be as well- choose carefully based on your interests and how you like the folks.  Hamfests are a great place to meet other hams and to socialize.  The www.arrl.org website has lists of clubs, hamfests, etc. 

Advice for current Amateur Operators 5/5/07:

When is the last time you sent $20 to your local club, earmarked for investment in shared infrastructure?  Amateur Radio The Service depends on shared equipment and networks, like repeaters.  Money is tight in most clubs.   Beware of club who carefully save their money for a rainy day, while their repeaters fall apart.  They wonder why members drift away, and why the IRS is calling- nonprofits are not supposed to hoard money beyond their operating needs. 

We have a new digital networks talk and a D-Star grant application.  Write if you need it. 

Getting Started in High Speed Digital   1/1/08

 

There was this interesting e-mail thread I was in on recently that involved the US Coast Guard Auxiliary and their efforts to establish a volunteer, Ham Radio communications capability.  We ran into this when we first started building our Packet Network.  We talked to many local radio clubs, all of whom were interested, and even offered financial support and or endorsement for the project.  But an established radio club usually has a charter and bylaws and a mission/direction.  Having some outsiders or even insiders come and and try to change things or to re-focus on a new mission seems to be very difficult. 

So the solution we came up with was to start our own radio club.  This is easy, it takes one or more people making up a name.  If you get a little more organized, you can round up a few more people and start applying for a club callsign, and even get affiliated with the ARRL.  This takes quite a while but has some benefits.  The one lesson we learned was not to try to have your new club do too much.  You don't need to teach classes (other clubs already do, you don't need to form a VEC (there already are several), and you don't need your own 2 meter FM repeater (as this is impossible).  So the idea is to form a club, and focus just on your new mission, and not try to duplicate already existing functions already done elsewhere.  One thing to avoid, and that is an excessive focus on internal meetings and processes and paperwork.  These days, people are busy, and if most of your volunteer hours are devoted to internal meetings and travel, you will not be successful- except at meetings and travel.

 

------------------------------------------------------------------------------------------------

Who's In Charge

The primary sponsor for the Minnesota Statewide Network and D-Star development is a nonprofit radio club called the Lakes Area Repeater Association, which is the lead organization representing advanced Amateur Radio emergency services and technical capabilities to served agencies in Minnesota. 

Some core team members:

Paul Emeott, K0LAV - Site Engineering Dir.

Max Klingert, KB0RSQ- Linux Appliance code and DNAT

Kelly Black, KB0GBJ- Linux Systems Integration, Servers /Trivnet Support and Citadel

Doug Reed, N0NAS- Lab Manager + RF Engineering

Mike Baillargeon, K0BRG, Trivnet Web Interface

Dennis Boone, KB8ZQZ, Trivnet Development

Tim Neu, KC0LQL, Linux Systems Integration

Peter Corbett, KD8GBL, Linux Support + Trivnet Development

John Leeper, K0ZMR, Infrastructure Team

Dan Skyrpka, KE8TX, CFO

Jerad Hoff, Web Hosting

 

 

 

Erik Westgard  NY9D@arrl.net  Paul Emeott , K0LAV Pemeott@comcast.net

 

 


 
qu