RE: [tracker2] New telemetry format - request for comments
Sent: Monday, July 02, 2007 7:39 AM
Subject: Re: [tracker2] New telemetry format - request for comments
In general, I like it. I'm not following on the APRSSPEC sig, but
here are some thoughts:
IMO, field separator/identifie r characters should not be letters a-f;
stay away from hex digits to avoid confusion.
should there be field number identifiers? I don't know what you have
in mind for 1-wire sensor chains, but what would happen, for
instance, if sensor #2 in a 5 sensor chain dropped out? How would I
know what my data meant? That may not be likely or even worth
"interpretation reference". Maybe some of these should be reserved
for "well known" and others user-defined? e.g. high bit = 0, well
known issued by some working group; high bit - 1, user defined.