[aprssig] Is the APRS Spec for APRS Data Type Identifier just randomly ignored? Should it be?
James Washer washer at trlp.comThu Aug 18 15:56:18 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 ]
The reason I asked this, is that destination=BEACON is explicitly included in the APRS spec, hence, it's not correct to say a destination=BEACON packet is NOT an APRS packet. On Thu, 18 Aug 2005 11:48:45 -0400 Steve Dimse <steve at dimse.com> wrote: > > On Aug 18, 2005, at 11:40 AM, James Washer wrote: > > > What do you mean by a "BEACON packet below? > > > > BEACON packets are what are used in non-APRS packet networks to > announce presence. Often, but not always, they have a destination of > BEACON. They are the reason TNCs have a beacon parameter in the first > place! > > Steve K4HG > > _______________________________________________ > aprssig mailing list > aprssig at lists.tapr.org > https://lists.tapr.org/cgi-bin/mailman/listinfo/aprssig
- 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
