[aprssig] Is the APRS Spec for APRS Data Type Identifier just randomly ignored? Should it be?
Henk de Groot henk.de.groot at hetnet.nlThu Aug 18 19:08:44 UTC 2005
- Previous message: [aprssig] Is the APRS Spec for APRS Data Type Identifier just randomly ignored? Should it be?
- Next message: [aprssig] Is the APRS Spec for APRS Data Type Identifier just randomly ignored? Should it be?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Curt, WE7U schreef: > On Wed, 17 Aug 2005, James Washer wrote: > > >>Curt, the APRS Spec includes BEACON as well as many other non AP* destinations. Further, the spec goes on to say "any other destination NOT include in the generic ..." are ALTNET, >> >>Wouldn't this imply a BEACON destination is indeed an APRS packet? > > > Yep. Forgot about those exceptions. Also keep in mind that MIC-E packets also do not use AP* destinations, but are not ALTNET packets. In fact.. you cannot use MIC-E on ALTNETs since there is no way to indicate the ALTNET... So before looking at the destination address to detect an ALTNET, first look if it is not a MIC-E packet. Kind regards, Henk.
- Previous message: [aprssig] Is the APRS Spec for APRS Data Type Identifier just randomly ignored? Should it be?
- Next message: [aprssig] Is the APRS Spec for APRS Data Type Identifier just randomly ignored? Should it be?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the aprssig mailing list
