#### Re: Telemetry EQNS oddity

Arnold Harding - KQ6DI

According to the APRS 101 specification
Page 70, the specification calls for a decimal point after EQNS.  Here's from the specification.
Example:N0QBF-11 :EQNS.0,5.2,0,0,.53,-32,3,4.39,49,-32,3,18,1,2,3

You made me look, so that's OK.  The fact that aprs.fi gets it one way ( as I intended) and APRSISCE doesn't makes me wonder if APRSISCE isn't getting it the way intended.  (I'm not suggesting APRSISCE is wrong, it just doesn't come out the same way.)
My guess is I need a leading zero after the negative sign before the decimal point on negative less than 1 calculations.
Arnold, KQ6DI

On 04/10/2021 4:24 PM Rob Giuliano via groups.io <kb8rco@...> wrote:

The format is    EQNS ,A1,B1,C1,A2,B2,C2,A3,B3,C3,etc.

You missed the comma (used a decimal)
should be :KQ6DI-1 :EQNS,0,-.644,150,0,-.5,-190,0,1,0,0,.625,0

Robert Giuliano
KB8RCO

On Saturday, April 10, 2021, 2:27:32 PM EDT, Arnold Harding - KQ6DI <kq6di@...> wrote:

I think I may have done something outside the specification, or there is an error somewhere.  I changed telemetry EQNS to remove some leading zeros, and APRSISCE doesn't pick the values out.  What I am sending is:
:KQ6DI-1 :EQNS.0,-.644,150,0,-.5,-190,0,1,0,0,.625,0

aprs.fi picks out the values correctly ( at least as I intended ), but APRSISCE doesn't pick up part of the equation.
Channel 1 b=0 should be -.644
Channel 2 b=0 and should be -.5

It worked before when I had leading zeros in the equation like -0.644 and -0.5.
But notice that channel 4 did pick up the correct number of .625.

So my guess is that negative values less than one must have a leading zero and become -0.644 and -0.5.  Do I need those leading zeros on negative values?

That site only sends telemetry parameters once a day at 09:03, IF the RF makes it out of this RF hole.  It's also 3 hours each way for me to change parameters, so I won't make a special trip for this.

Arnold, KQ6DI

Join APRSISCE@groups.io to automatically receive all group messages.