[aprssig] tactical call identifier packet

Curt, WE7U archer at eskimo.com
Mon Jul 28 04:43:08 EDT 2008

On Wed, 23 Jul 2008, Wes Johnston wrote:

> Could we create a new packet type that would force the display of
> a tactical callsign instead of an object's real callsign?
> For example... if I want to map ai4px-9 to "wes' car" on my
> display, I can do it on each client, but I have to program each
> client to know when it sees ai4px-9 to display wes car.  What if
> there was a packet that could "suggest" tactical calls.  I could
> program one client to send packets which the rest would see and
> they'd know which tactical calls to display w/o me having to
> program each one.  Yes, it's a little extra overhead on 144.39.

Just checked-in to Xastir CVS:

Update of /cvsroot/xastir/xastir/src
In directory sc8-pr-cvs10.sourceforge.net:/tmp/cvs-serv18726

Modified Files:
         db.c util.c util.h

Log Message:
The beginnings of being able to share Tactical Call data with others
over the air.  This code works, decoding messages sent to "TACTICAL"
which are in one of these four formats:

     My Home
     WE7U-3=My Home
     WE7U-3=My Home;WE7U-12=Curt's Jeep;WE7U-15=I Don't Know

In the first case it'll assign "My Home" as the tactical callsign
for the station that sent the message.  In the last case it'll
remove tactical callsigns for the listed stations.  For testing
remember that you can't send a new message to TACTICAL until the
previous message has either timed-out or been cancelled.

I just tried this code out between two Xastir stations running the
new code and it works.  Next is to find an APRS+SA station to test
against to see how they behave.

Curt, WE7U.				archer at eskimo dot com
   Lotto:  A tax on people who are bad at math. - unknown
Windows:  Microsoft's tax on computer illiterates. - WE7U.
The world DOES revolve around me:  I picked the coordinate system!"

More information about the aprssig mailing list