Order Tray | Contact Us | Home | SIG Lists

[aprssig] APRS digi from the digi point of view

Tom Hayward tom at tomh.us
Fri Jun 15 01:25:56 UTC 2007


We plan to use SARn-N for search and rescue stuff. TEMPn-N has been
mentioned for certain situations. I'd say allow for ?????n-N to keep
options open.

ftp://ftp.tapr.org/aprssig/aprsspec/spec/aprs101/APRS101.pdf
Here's a link to the APRS spec. I couldn't find any section that
referred to or allowed for anything but WIDEn-N. It does have a
chapter on third-party digipeating, which you may want to support.

Tom KD7LXL

On 6/14/07, Jim Wagner <wagnerj at proaxis.com> wrote:
> OK, lets say someone is writing an application that COULD have APRS
> digi function. The question is what digi alias schemes should said
> application be prepared to support:
>
> (1) Simple name or call? Sure, all digis, APRS or not, need to do that
>
> (2) RELAY and WIDE? I know that they are deprecated, but should they be
> offered?
>
> (3) WIDEn-N? Yes?
>
> (4) What about TRACEn-N? If so, what are the rules used by TRACE digis?
> What do they substitute where?
>
> (5) Are there other NAMEn-N constructs in use? Do you allow an
> arbitrary 5 char name?
>
> (6) Other digi reference schemes?
>
> Thanks
> Jim, KA7EHK
>
>
> _______________________________________________
> aprssig mailing list
> aprssig at lists.tapr.org
> https://lists.tapr.org/cgi-bin/mailman/listinfo/aprssig
>




More information about the aprssig mailing list