[aprssig] Is floating point telemetry allowed in APRS?

[Andrew P.]

Whoops. I take that back. Here's a local guy near my house doing it.

WA3NOA-RI>RXTLM-2,TCPIP,qAR,WA3NOA-5:T#043,0.2,0.0,1.0,0.0,0.0,00000000

By the way, what's the RXTLM destination code for? I'll have to ask him (he's in my local ARES group).

Andrew Pavlin, KA2DDO
------Original Message------
From: Steve Dimse
To: aprssig at tapr.org
Sent: Mar 27, 2013 4:09 PM
Subject: Re: [aprssig] Is floating point telemetry allowed in APRS?


The spec is not fluid that way. If it says telemetry should look like 

T#005,199,000,255,073,123,01101001

sending

T#005,199.1,000,255,073,123,01101001

is not within the spec, and many parsers will reject the packet outright, others might truncate, still others might crash. The results are undefined and therefore should not be used. The whole point of the spec was to have data that everyone could understand in the same way. 

People that have non-standard needs are supposed to use the user-defined part of the spec which allows for any data one might need without causing problems in other parsers. 

Can you give an example of such a packet?

Steve K4HG



On Mar 27, 2013, at 4:01 PM, Charles Blackburn wrote:

> that is a good question, although i would assume that you could just drop the fraction and be done with it.
> 
> charlie
> _______________________________________________
> aprssig mailing list
> aprssig at tapr.org
> http://www.tapr.org/mailman/listinfo/aprssig
> 

_______________________________________________
aprssig mailing list
aprssig at tapr.org
http://www.tapr.org/mailman/listinfo/aprssig


Sent from my Verizon Wireless BlackBerry