Tuesday, July 10, 2012

2012 MISSOULA MARATHON APRS WRAP UP


Hi Group,

Greetings from Missoula, Montana.

 The Missoula Marathon was held this past weekend. There were 5000+ runners/walkers/handicappers participating. The Hellgate Amateur Radio Club, led by Elmer WG7P, did a great job directing efforts of the 25+ volunteers who provided voice communications and APRS support to the race. We had communicators at most of the 17 AID Stations along the two routes, which included a Full Marathon (26.2 miles) and Half Marathon (13.1 miles). As the three lead male and female runners passed each AID Station the assigned communicator would radio in the bib numbers and time of crossing to Jerry N7GE (also an avid APRSr) at the finish line. I manned the APRS finish line station, monitoring the trackers we had following three lead males and female runners, and two "tail end charlie" trackers bringing up the rear of the races. Both Jerry and I took turns radio'ing the leader updates to Eric NZ7S at the FINISH line crossing where the announcers broadcast the info over their PA system.

The trackers consisted of two Byonics MT-AIO "yellow box" units mounted on bicycles, a Byonics MT-RTG mounted in the half-marathon pace car, three Kenwood D7/D72's, and an Arduino tracker neatly mounted on a bob-trailer behind the tail-end charlie bike. We ID'd the trackers with tactical callsigns (MSLA*) and entered owner callsigns at the end of the status text comment, set them for 30 second updates with various offsets to reduce packet collisions. Battery life well exceeded our needs on all the trackers. The finish line station ran UI-View with two area specific maps generated with Precision Maps v9, one showing the entire race routes, and the other focused on the final four AID stations. The AID stations were generated as objects on UI-View, and were periodically announced onto the APRS-IS as MSOAID*. As my TH-D72 was being used as a tracker, the UI-View station relied on APRS-IS input only. A projector and screen displayed the race picture for others to see from our location just below the finish line in Caras Park.

The trackers and FINISH line station worked great, although there were some gaps in coverage and other technical difficulties along for the ride. It was nothing we couldn't deal with, and overall a very successful mission. This was the first occasion for using APRS at the Missoula Marathon, and race officials were very impressed. I've done about a dozen or more races, marathons, triathons and Ironman events over the years, so bring some experience with me to the Hellgate club as I'm summering in Montana to escape the heat of Tucson. Makes sense, right?

We had a debrief last night at the monthly HARC meeting, and along with increasing the number of trackers to cover the three leading males and leading females of each race, we intend to place a tracker with the 5 hour PACER runner, and perhaps with one or more of the SAG vehicles. We also talked about coordinating some other communication updates including "tweeting" the BIB numbers when they pass the AID stations, so others can stay aware, and using several iPhones or Android smartphones to broadcast streaming video to UStream and link it with a map of the associated APRS tracker. I have that capability now, using my Android Bionic and mobile tracker to the web page at http://k7gps.weebly.com, but it could easily have been adapted to U2APRS or APRS OpenTracker running on a smartphone and the UStream video simultaneously. Oh the possibilities are limitless.

There's another communications-related activity I'd like to expand for next year, that is in the "lost and found" arena. We had several people wanting to drop off lost and found items, or in two cases looking for separated parties, one of which was a runner/walker in the event, who should have, but had not yet crossed the finish line. We took the bib number, name and description of those folks and radio'd an attempt to locate to our people along the course, but unfortunately never made contact with the other parties. On the TV news later that night I heard a report of one runner who collapsed mid-way between aid stations, where we didn't have any communicators, was administered CPR and rushed to the hospital. His age and physical description matched those of the person we were looking for. We'll try harder next time to get the bib number of those who are administered first-aid along the course, and get that info to communications-central, so when concerned parties come looking we can provide them with at least some information, or which hospital they were transported to.

Regards, Dave K7GPS

More information:

M-1, M-2, F-1, HF-2 trackers were all mounted on 10-speed bikes. We wrapped blue painters tape around the area where our tracker would be mounted, so as to not cause any scratches on some very expensive bikes. Dick W7XT fab'd a couple 19.5" metal mounting brackets to the bike to hold the mini-mag mount antenna and give some semblance of a ground plane. We also used:


  • H-1 tracker, the MT-RTG, was in a Subaru. Nothing fancy there.
  • TL-1 tracker, a D7 and Etrex GPS with 1/2 wave no-ground-plane antenna, was on Dick's BMW 1100R and worked just fine.
  • TL-2 on Dean's bicycle bob-trailer, the Arduino tracker, and a pole mounted Go-Pro HD camera. Perfect for the larger battery he had. Next year we may run a uStream-capable camera from it, and put him up front. This takes the limited tracker mounting options off the bike an onto a small, single-wheeled trailer that attaches to the rear. With as many biking events the HARC supports here in Missoula, perhaps the club will invest in a half-dozen of these to come up with a really-robust tracking capability. Think of the possibilities! 


It was a really fun event to support, and the race officials really appreciated the club's efforts. The club is moving forward to purchase several more MT-AIO trackers since they support a bunch of different events where APRS can supplement voice communications.

We're also recommending to the race officials to have the escort bike riders wear a brightly colored shirt with M-1, F-1 etc in big letters, so our AID station communicators can more-easily identify the leaders, and the riders call out the bib numbers of who they're escorting, as in some cases the bib numbers curl up or are tucked in, making them unseen to the AID stations as they come by.

Again, this was really a great event, and the people of Missoula and all involved are really super people. It's no wonder this smaller venue marathon was voted "most friendly marathon" in 2009. I think the trend continues today.

Dave K7GPS

Thursday, July 5, 2012

aprssig - APRS joins Operation ON-TARGET!

The annual Operation ON-TARGET consist of scouts and hams all over the country going to mountain tops and attempting to communicate by signal mirror (assisted by HAM contact to know where to point).  This is Saturday July 21st, 1100 to 1400 LOCAL TIME.

See www.ldsfacts.net/ontarget.htm

Take along an APRS HT or radio, since then everyone can see on their attached GPS where everyone else is and can globally text message in real time for coordination.  In addition, everyone back home can watch it all LIVE and see on maps where everyone is and what links are successful on http://aprs.fi

Operation on target has hundreds of participants out west because of the accessible mountains and clarity of distance.  The goal is mountain top connectivity across the entire US north to south.

Similarly, APRS has had an annual event (Golden Packet attempt) on the 3rd weekend in July to do the same thing but with APRS and packet.  We have been successful in linking 15 mountain tops from Georgia to Maine with APRS and will do it again this year.  But by joining with Operation On Target, at least out-west, the APRS folks out west get to leverage the many more hams that are involved already.  See all about the Golden Packet event:

http://aprs.org/at-golden-packet.html

At this time, we WILL plan on operating the APRS Golden Packet event out west on the 21st with the Operation on Target.  We are still trying to decide for the Appalachian trail group, originally planning on the 22nd, Sunday, to move to the 21st Saturday to match up our efforts with East coast Scouts that might be doing Operation On Target along the Appalachians.

So far, we have not found any east-coast OT plans.  So if anyone knows of any, please let us know.  We will carry mirrors if there are scouts watching...

Oh, and the CQ Worldwide VHF contest is that same weekend!  That starts at 1800z on Saturday (1400 EDT on the east coast).  The mountains will be crawling with hams! (and QRM)...

For the 4 hour event, APRS will use 144.34 MHz.  Please join the at-golden-packet@yahoogroups.com if you will participate so we can coordinate. And review APRS Details on the web page above.  We will all use the EYEBALL symbol to make it easy to identify participants.

Bob, Wb4APR
https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig

Wednesday, May 30, 2012

APRS to SOTA gateway


Stewart G0LGS has set up an excellent APRS2SOTA gateway to send your spots to sotawatch.org via aprs.

Tuesday, March 20, 2012

PNW Amateur Activities


PNW Amateur Radio Events
Comprehensive List by N7CFO - http://www.n7cfo.com/amradio/hf/hf.htm

Moving from wikidot.com to blog pages

Some NWAPRS notes have been gathered at the nwaprs.wikidot.com site.  That's not real convenient to edit and is extra trouble when we can put everything we need here on the blog.   So today we'll move the data and archive the old wiki pages.


Tuesday, March 13, 2012

Data Flow...

We're moving the static data from the nwaprs.info website to the 'pages' here...   The transistion has just started and much cleanup is still needed.   Stay tuned - and make packets.

Bill

Thursday, October 13, 2011

New ISS object flying

Greetings APRS users,

There's a new ISS object flying in APRS-IS, but this object is different than others that have flown. It is flying with a MultiLine (http://www.aprs-is.net/WX/MultilineProtocol.aspx) description of the approximate reception footprint. It moves every two minutes, so if you're using an APRS client that displays MultiLine information (APRSISCE/32 and xastir at a minimum), you'll be able to see the footprint coming and know to anticipate a pass (or realize that you just missed one).

The ISS object has a comment that says "Msg4Pass". That means to send an APRS message to "ISS" (without the quotes) from any message-capable APRS platform. This can be APRS radios (if you're in range of a message-gating IGate), any of the PC-based APRS messaging clients (like UI-View), or any of the new mobile APRS-IS clients, provided that they do messaging.

When "ISS" (not the real space station, but the APRS satellite server) will calculate the current or next pass of the ISS for an observer at your station's last beaconed position (it will say "Please Beacon Position" if it doesn't know where you are). The response will be one of the following:

Az: aaa El: lll LOS:xx:yyz - If you are in a pass
AOS: xx:yyz+aa:bbc - If you are not in a pass
AOS: NONE - If there are no passes for your location in the next two days.

aaa and lll are the azimuth and elevation for an observer at your location at the time the message was processed. LOS is Loss of Signal and xx:yyz is the time remaining in the pass and will vary to show sufficient time periods (hh:mmh, mm:ssm, sss).

AOS is Acquisition of Signal with xx:yyz being the delta time until the pass begins and +aa:bbc is the expected duration of the upcoming pass. The longer the pass, the higher you can expect the max elevation to be and the more chance of working it as it flies by.

But Wait! There's MORE! If the text you send to ISS is a known station identifier (say KJ4ERJ-12), the returned pass information will not be for your location, but for that station's last known location. To be clear, "@ call-SSID" is appended to the end of the response so you know which observer it is for. Of course, if the satellite server doesn't know where your specified station is locate, you will receive "Please Beacon Position" as a response.

And that's not all! This doesn't only work for the ISS, but for any of the other satellites found in the TLE set fromhttp://www.celestrak.com/NORAD/elements/amateur.txt You can send an APRS message to "AO-51" to find out when that satellite will pass within range. If you have any trouble figuring out which satellite name a message can be sent to, send an APRS message to KJ4ERJ-12 (or an e-mail to here) and I'll see if I can map the TLE entry to the responder station ID. And of course, you can also send any other known station ID to any of the satellites to get the current or next pass information for that station's location.

Give the service a try, and let me know how it works out. There's nothing to remember except the satellite name (including the dash in most cases) and the fact that you send a message to the satellite. Nothing like ANSRVR or CQSRVR or SATSRV, just send the message to the satellite by name and it will return the pass information.

Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32

PS. Don't look for ISS at aprs.fi as it flies too fast and is currently rejected by the speed limit filter. If you want to track the ISS object, add o/ISS* to your APRS-IS filter string. If you don't want to see it when it goes by, add -o/ISS* to your filter.

Here's a pair of chat transcripts with ISS and AO-51 (times are Eastern US):

21:35:39 New Chat Between KJ4ERJ-AP and ISS on 2011-10-13
21:35:41> foo (*2-21:35:41)
21:35:41< Az:325 El:12 LOS:4:19m
21:42:57> bar (*2-21:42:57)
21:42:57< AOS:4:44h+3:21m
21:48:41> WB4APR-15 (*2-21:48:41)
21:48:41< AOS:1:19h+8:23m @ WB4APR-15

21:43:09 New Chat Between KJ4ERJ-AP and AO-51 on 2011-10-13
21:43:11> FOO (*2-21:43:11)
21:43:11< AOS:5:45h+3:10m
21:43:26> ISS (*2-21:43:26)
21:43:26< AOS:5:45h+3:09m
21:43:37> N0GPS-3 (*2-21:43:37)
21:43:38< AOS:8:59h+12:24m @ N0GPS-3
21:48:58> WB4APR-15 (*2-21:48:58)
21:48:58< AOS:7:12h+13:23m @ WB4APR-15