[Invalid uncompressed location] for packets from my libaprs tracker

[Mikael Andersson]

Hi!

Thanks for a great APRS.fi!

I've built and am testing a tracker using libaprs for arduino. 

I've sent a few packages that have reached APRS.fi (http://aprs.fi/?c=raw&call=sa0mik*&limit=50&view=normal):

2016-02-25 10:08:01 CET: SA0MIK-5>APZMDM,WIDE1-1,WIDE2-2,qAR,SM0YGE:=5931.50N/01798.43EnI:9831564 T1:19.75 Vi:4.87 Vb:3.99 [Invalid uncompressed location]
2016-02-25 10:09:22 CET: SA0MIK-5>APZMDM,WIDE1-1,WIDE2-2,qAR,SK0BJ-10:=5931.49N/01798.44EnI:9831570 T1:26.25 Vi:4.98 Vb:3.96 [Invalid uncompressed location]
2016-02-25 10:22:34 CET: SA0MIK-5>APZMDM,WIDE1-1,WIDE2-2,qAR,SM0YGE:=5931.48N/01799.06EnI:9831615 T1:40.00 Vi:5.00 Vb:3.90 [Invalid uncompressed location]

When I look through the APRS protocol reference (http://www.aprs.org/doc/APRS101.PDF) I can't understand why these packages have an invalid location.

Could someone please help me understand why these packages are not valid?

Thanks!

Best,

Mikael

[Lynn W Deffenbaugh (Mr)]

Coordinates are expressed in degrees and decimal minutes (ddmm.mm or dddmm.mm).  There is no such places as 17 degrees 98.43 minutes.  Minutes must be <60.00.

Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32

--
You received this message because you are subscribed to the Google Groups "aprs.fi" group.
To unsubscribe from this group and stop receiving emails from it, send an email to aprsfi+un...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Mikael Andersson]

Thx! Can confirm I was using decimal degrees and not minutes and seconds. My bad! Will change and see what happens :)

[Mikael Andersson]

And now packets are valid:

2016-02-25 17:01:06 CET: SA0MIK-5>APZMDM,WIDE1-1,WIDE2-2,qAR,SM0YGE:=5918.53N/01759.11EnI:5 T1:14.00 Vi:4.96 Vb:4.00
2016-02-25 17:02:07 CET: SA0MIK-5>APZMDM,WIDE1-1,WIDE2-2,qAR,SM0YGE:=5918.53N/01759.11EnI:6 T1:10.50 Vi:4.96 Vb:3.95
2016-02-25 17:03:09 CET: SA0MIK-5>APZMDM,WIDE1-1,WIDE2-2,qAR,SM0YGE:=5918.53N/01759.11EnI:7 T1:7.75 Vi:4.96 Vb:4.02
2016-02-25 17:04:11 CET: SA0MIK-5>APZMDM,WIDE1-1,WIDE2-2,qAR,SM0YGE:=5918.53N/01759.12EnI:8 T1:5.50 Vi:4.96 Vb:4.00

Thank you! 

[Lynn W Deffenbaugh (Mr)]

May I ask why the telemetry-looking values in your packet comment?  If you put those into true telemetry packets and provide telemetry definitions for them periodically, aprs.fi will automatically generate graphs over time for you!

You will need to scale them to a 0-255 integer value (per spec, but aprs.fi supports 0-999, possibly more) but that's why the definitions are supported to put them back into more usable units.

Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32

--

[Heikki Hannikainen]

On Thu, 25 Feb 2016, Lynn W Deffenbaugh (Mr) wrote:

> May I ask why the telemetry-looking values in your packet comment?  If you put those into true telemetry packets and provide telemetry
> definitions for them periodically, aprs.fi will automatically generate graphs over time for you!

Alternatively, aprs.fi (and a couple other apps) accept base91 comment
telemetry embedded in the position packet, with quite a bit more
resolution than 8 bits:

http://he.fi/doc/aprs-base91-comment-telemetry.txt

That's being used by quite a lot of trackers nowadays.

- Hessu