[Xastir] Thanks for helping us have a successful event!

[Bob Donnell]

One of the things that came to mind, reading Mike's post is that IF the VM
installation can be set up to do soundmodem packet, then all that's needed
is the right stuff for operating the rig dedicated to packet.  No TNC
needed.  At one time I had a Pentium 150 laptop with a Baycom modem set up -
which uses a lot of the same pieces as the soundmodem - and it handled
Xastir OK, other than it took a very long time to pan and zoom topo maps.
Local Tiger vector maps would likely be a lot faster.  

If the ham involved has any interest in using digital modes, a USB sound
card device designed for radio interface, like a TigerTronics SignalLink
USB, could be set up with the radio in question, providing packet operations
with the virtual machine, or when used with the native operating system, to
do HF digital modes, like PSK-31 - basicly a not-too-expensive way to get a
"two-fer" - APRS support via Xastir and the VM, and the many digital modes
via the native operating system and software available for it.

Receive-only stations could also be set up to use the computer's soundcard
as the audio source.  Transmit might be managed, but the trick with most
laptops becomes how to key the radio.  Most soundmodem software and hardware
uses one of the hardware handshake lines from a serial port to key the rig.
That's where the SignalLink USB is sneaky.  It uses a fast-acting VOX
circuit to key the radio.  The only down side is that any sound sent to that
port will key the rig - but since it's going into the system as a secondary
audio device, that's somewhat less risky - though careful configuration
might be needed.

By the way, Curt, WE7U, and I have used Xastir for several years in
dispatching SAG drivers, all APRS tracker equipped, to pick up runners
unable to complete the run.  Curt works behind the scenes in the main net
control, taking reports from the nets that communicate with hams at each
mile marker and rest stop, then sending them to me.  I operate the SAG net,
on a different frequency, from across the Seattle Center, which gives us
enough seperation to not interfere with eachother, and I'm located just
outside the recovery area (which being built to Cold War standards, is
difficult to get RF in and out of) so when there's a runner being delivered,
as their SAG driver arrives, the hams in the medical area can send a wheel
chair, if needed, to meet the runner at the street, and get he or she
delivered to the medicos helping the mildly injured.  We have successfully
used instant messaging to pass this info back and forth, but have also
planned on using Xastir for APRS one-liner's if our IM circuit fails.  

Placing objects for each stopped runner is a good idea, and one I'll see if
I can remember to adopt.  It seems like a good idea, and provides a
graphical status board.  Editing the object also allows those watching to
see which SAG unit is enroute to pick up each participant.  And rather than
having each SAG driver reconfigure their tracker (always risky), we use the
tactical call sign assignment capability to make each SAG show up with the
tactical identifier that was assigned.  The area of the event is small
enough that it's not usually necessary to limit the display to only tactical
calls - anyone going by on the freeway isn't in the picture long enough to
be of concern.

One the other things I did some time ago was to take the race map, clean all
of the extraneous text out of it, rotate it to north-up orientation, and
generate a .geo file for it.  That places the rest stops and mile markers on
the map.  If I need to find a specific non-identified intersection, then I
turn on the Tiger Map layer, with labels, to find the street.  And it sounds
like I can improve on that this fall, too.

73, Bob, KD7NM

-----Original Message-----
From: xastir-bounces at lists.xastir.org
[mailto:xastir-bounces at lists.xastir.org] On Behalf Of Mike Benonis
Sent: Tuesday, June 16, 2009 9:16 AM
To: Xastir - APRS client software discussion
Subject: Re: [Xastir] Thanks for helping us have a successful event!

Hi Peter,

We too used Xastir this past weekend for our MS-150 Bike Tour in central
Virginia.  It worked quite well, though we did not deploy it nearly as
extensively as you did.  I primarily used it as a vehicle tracking system,
though I did create objects for each rest stop.  Next year, I think I will
take many of your suggestions and use APRS to track fallen riders and other
situations on the course - and perhaps we can convince our club members to
get a TNC and a laptop setup for their rest stops.

Thanks to the Xastir team for a great program!

Best regards,

Mike Benonis
Heritage Theatre Festival Sound Engineer Elec. Engr. '09, The University of
Virginia mjb8h at virginia.edu KI4RIX

On Jun 16, 2009, at 08:20, peter+aprs at duonet.net wrote:

> Hello, this is KC0TFB, Peter Gamache.  I coordinated APRS operations 
> for the Minnesota Multiple Sclerosis Society's MS-150 fundraising 
> bicycle tour this year, last Friday, Saturday and Sunday.  As part of 
> the safety team (dozens of dedicated and skilled ham operators), we 
> ensured the safety of thousands of event participants during their 
> 150-mile ride from Duluth, Minnesota to the Twin Cities.  It was an 
> exciting event and I'm glad that Xastir helped make it happen.  Here's 
> how it worked:
>
> Planning and preparation for APRS use during the event started about
> 5-6
> weeks ago. In Sun VirtualBox (http://virtualbox.org/), I installed 
> Xubuntu GNU/Linux 9.04, then stripped out the non-essential packages.  
> I then added the Xastir package and the TigerLine 2006 maps (from 
> ftp://aprs.tamu.edu
> )
> for all the MN counties that the event passed through.  This laid the 
> foundation for our APRS operations.
>
> Since this VM image would be used by all the Rest Stop operators on 
> whatever laptop they provided, I wanted an easy-to-use interface.  On 
> the desktop, I added a icon for my "Get Updates" script.  This script 
> "phoned home"
> to a
> server that could run commands on each system to cover my tracks, had 
> I forgot anything.
>
> Jason, N0RPM (also our Net Control APRS op), contributed an excellent 
> tool, in the form of the other desktop script.  It configured Xastir 
> for each station, inserting the appropriate callsign, coordinates, 
> comment and symbol for each rest stop in the configuration file, then 
> launched Xastir.
>
> Prior to the event, we distributed the VM image to all the Rest Stop 
> radio operators.  In VirtualBox, you can "Export" a VM.  This 
> compresses the filesystem and gives you two files as output: one that 
> describes the VM settings and another that represents the disk image.  
> For us, this totalled about 600Mb, which fit perfectly on a CD-R.
>
> Several revisions occurred after the CD-Rs were distributed, however 
> the "Get Update" script took care of this.  Various updates added the 
> GNIS file for MN (ftp://aprs.tamu.edu) to support street address 
> location searches, re-configured the map selector and removed the 
> .xastir/config/ object.log, so all our stations wouldn't try to beacon 
> the same objects.
>
> Most importantly, we had a training meeting for all the Rest Stop APRS 
> operators.  In training, we discussed the important features we'd need 
> to
> use: Messaging, locating map features, the basics of zooming, panning 
> and how to configure Xastir for whatever TNC each operator had 
> available.
>
> At the event, cyclists had each been issued a wristband which 
> identified their rider number, as well as listed a "Rider Helpline" 
> telephone number.
> That number went to our net control telephone op, the person 
> responsible for providing the "end-user interface" to our support 
> radio network.
>
> If a rider needed assistance, the telephone op would pass the message 
> to our APRS operator, who would place an object (using the rider 
> number as an object name) on the map.  The Net Control voice operator 
> would then contact the nearest rest stop, "Rest Stop X, pick up rider 
> #1234 at Fourth Ave and Main Street."
>
> The voice operator at the specified rest stop would confirm receipt of 
> the request, and the rest stop APRS operator would adopt the rider 
> object on the map.  The rest stop communicators would then dispatch 
> the nearest SAG (support and gear) van to pick up the rider along the 
> route.  The SAGs all had tracking beacons installed (see 
> http://map.findu.com/mssag*) prior to the event, so finding the 
> nearest one was easy.
>
> When the SAG reported back via 2m simplex to the rest stop, informing 
> them that the rider was picked up, the rest stop would then delete the 
> object for the rider, removing it from everyone's map.  The rest stop 
> would then inform Net Control via either our 70cm repeater or APRS 
> messaging that "Rider #1234 was picked up".
>
> The event ended with all the thousands (around 4000, if my estimates 
> are
> correct) of riders making it safely home.  Once again, Xastir helped 
> make this possible.  Thanks to all the developers and users who make 
> up the Xastir community - we couldn't have done this without you!
>
> 73,
> Peter / KC0TFB
> _______________________________________________
> Xastir mailing list
> Xastir at lists.xastir.org
> http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir

_______________________________________________
Xastir mailing list
Xastir at lists.xastir.org
http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir