[aprssig] HF noise measuring campaign reports via APRS
hessu at hes.iki.fi
Sun Sep 16 22:54:41 CDT 2012
By the way, a noticeable number of stations do seem to transmit
floating-point values in telemetry. Our perl parser currently accepts
them, I wonder how others treat them?
The 0...255 requirement seems to be designed for 8-bit decoders, I wonder
if there are any of those around.
On Sun, 16 Sep 2012, Lynn W. Deffenbaugh (Mr) wrote:
> I agree that the standard APRS telemetry is definitely the preferable
> approach, but since your example packet (below) showed 8 floating point
> values of apparently some level of precision, I didn't suggest a format that
> only supports 5 values ranging from 0 to 255 (per spec, but some say 0..999)
> that can be scaled based on defined parametric equation coefficients.
> Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32
> On 9/14/2012 4:40 PM, Chris Moulding wrote:
>> Thanks for the information about the telemetry packets. That looks ideal
>> especially when it displays in aprs.fi so well without any software changes
>> at your end!
>> At the moment we are looking at three frequencies but with five telemetry
>> channels available it might make sense to go with five frequencies from the
>> Chris, G4HYG
>>> If there's at most 5 frequencies monitored by a given station, you could
>>> transmit it as standard APRS telemetry, and it would be graphed
>>> automatically by all APRS receiving stations without any code changes in
>>> the receiving end. Like this:
>>> You can also transmit channel names for each graph.
>>> - Hessu
>> aprssig mailing list
>> aprssig at tapr.org
> aprssig mailing list
> aprssig at tapr.org
More information about the aprssig