On Mon, 1 Feb 2010, Jason KG4WSV wrote:
On Mon, Feb 1, 2010 at 2:06 PM, Curt, WE7U <[email protected]> wrote:
Remember that there's the AEA format, the TAPR-2 format, and others
that are usually similar to TAPR-2 but perhaps with fewer commands
or just slightly different.
Isn't the APRS-IS format pretty much the TAPR format, with the
addition of path elements that may push the number over the AX.25
limit, and case incompatible? I'd thought to specify that the IS
parser code is sufficient for the cmd-mode TNC parser.
Nope, but it's a good start. If I receive a header from an AEA TNC
(which has a different order for the SRC/DEST/PATH elements than a
TAPR-2 TNC does), I just pass it on to the APRS-IS. Same for
wherever the TNC decides to place one or more asterisk characters, I
just pass them on. So... Anything receiving packets off the
APRS-IS has to be able to decode these variants.
--
Curt, WE7U. <http://www.eskimo.com/~archer>
APRS: Where it's at! <http://www.xastir.org>
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!"
_______________________________________________
Xastir-dev mailing list
[email protected]
http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir-dev
