[aprssig] APRS Telemetry Question
Steve Noskowicz noskosteve at yahoo.comSun Oct 14 22:04:58 UTC 2012
- Previous message: [aprssig] APRS Telemetry Question
- Next message: [aprssig] Next build of YAAC (Yet Another APRS Client) now available
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
I'll be more explicit. My intent was not to argue the spec, but simply to point out that unfortunately, an answer of "read the 101 spec" doesn't answer all questions (read: 'specify the protocol') fully, so follow up questions are to be expected. It also "says" the Telemetry starts with a "T" when, from comments here, it must start with "T#". The answers did get me a better understanding of what I wanted that was difficult to get from the spec alone and I thank the responders for that. In addition, since my local digi is somehow crippled, it is difficult getting real off-air packets right now. This level is not where I spent most of my time gaining an understanding of APRS. 73, Steve, K9DCI USN (Vet) MOT (Ret) Ham (Yet) --- On Sun, 10/14/12, Jason KG4WSV <kg4wsv at gmail.com> wrote: > Steve Noskowicz <noskosteve at yahoo.com> wrote: > >> ... Every single character ... is part of the > specification, > > > > Not quite, as I pointed out. > > If you note the field length it says 5. Not 2-5, 0-5, > etc (as it does > in other places for variable length fields). This is > clearly a > fixed-width field, the T, #, 3 digits, and the comma are > required. > > Even if some parsers accept mal-formed packets, the spec is > pretty > clear in this area, IMO. > > -Jason > kg4wsv
- Previous message: [aprssig] APRS Telemetry Question
- Next message: [aprssig] Next build of YAAC (Yet Another APRS Client) now available
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the aprssig mailing list
