APRS Packet Errors for YO9ION-2 (last 6 hours)

This table contains packets in which findU has detected an error. This is an automated system, no manual checking of these packets has been done. Most common cause of this is mistakes in entering the latitude/longitude into hard-coded digis, or positions of 0/0. If packets of yours appear here, and you have looked at it carefully and cannot find the error, look again. I've been watching these error messages in my log, and believe my parser is reasonably correct. Go get the APRS spec to be sure. If you have done that, and are CERTAIN the packet is a legal APRS packet, then it is possible that there is an error in my my parser. Only email me if you are absolutely, positively certain...ask yourself, would I bet $100!

time (UTC)Packet
20260901081633YO9ION-2>APBM1D,TETRA*,qAR,BM2002-10:=0000.00N/00000.00E[MTP6650
20260901081810YO9ION-2>APBM1D,TETRA*,qAR,BM2002-10:=0000.00N/00000.00E[MTP6650
20260901081842YO9ION-2>APBM1D,TETRA*,qAR,BM2002-10:=0000.00N/00000.00E[MTP6650
20260901083257YO9ION-2>APBM1D,TETRA*,qAR,BM2002-10:=0000.00N/00000.00E[MTP6650
20260901084245YO9ION-2>APBM1D,TETRA*,qAR,BM2002-10:=0000.00N/00000.00E[MTP6650
20260901084345YO9ION-2>APBM1D,TETRA*,qAR,BM2002-10:=0000.00N/00000.00E[MTP6650
20260901094704YO9ION-2>APBM1D,TETRA*,qAR,BM2002-10:=0000.00N/00000.00E[MTP6650
20260901094804YO9ION-2>APBM1D,TETRA*,qAR,BM2002-10:=0000.00N/00000.00E[MTP6650
20260901095048YO9ION-2>APBM1D,TETRA*,qAR,BM2002-10:=0000.00N/00000.00E[MTP6650
20260901101810YO9ION-2>APBM1D,TETRA*,qAR,BM2002-10:=0000.00N/00000.00E[MTP6650
20260901102656YO9ION-2>APBM1D,TETRA*,qAR,BM2002-10:=0000.00N/00000.00E[MTP6650
20260901102738YO9ION-2>APBM1D,TETRA*,qAR,BM2002-10:=0000.00N/00000.00E[MTP6650