[aprssig] Is the APRS Spec for APRS Data Type Identifier just randomly ignored? Should it be?
Steve Dimse steve at dimse.comThu Aug 18 16:16:07 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 ]
On Aug 18, 2005, at 11:56 AM, James Washer wrote: > 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. > BEACON is a destination callsign defined in the APRS spec, which simply means it is included in the default ALTNET. Giving something a destination of BEACON does not make it either an APRS packet or a non- APRS packet. In fact, it specifically is in the spec so that non-APRS station on an APRSS network can be seen. Steve K4HG
- 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
