APRS Packet Errors for YO9ION-1 (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
20260914143012YO9ION-1>APBM1D,TETRA*,qAR,BM2002-10:=0000.00N/00000.00EeMXP600
20260914143643YO9ION-1>APBM1D,TETRA*,qAR,BM2002-10:=0000.00N/00000.00EeMXP600
20260914143837YO9ION-1>APBM1D,TETRA*,qAR,BM2002-10:=0000.00N/00000.00EeMXP600
20260914144318YO9ION-1>APBM1D,TETRA*,qAR,BM2002-10:=0000.00N/00000.00EeMXP600
20260914144357YO9ION-1>APBM1D,TETRA*,qAR,BM2002-10:=0000.00N/00000.00EeMXP600
20260914150414YO9ION-1>APBM1D,TETRA*,qAR,BM2002-10:=0000.00N/00000.00EeMXP600
20260914150450YO9ION-1>APBM1D,TETRA*,qAR,BM2002-10:=0000.00N/00000.00EeMXP600
20260914151650YO9ION-1>APBM1D,TETRA*,qAR,BM2002-10:=0000.00N/00000.00EeMXP600
20260914151746YO9ION-1>APBM1D,TETRA*,qAR,BM2002-10:=0000.00N/00000.00EeMXP600
20260914152248YO9ION-1>APBM1D,TETRA*,qAR,BM2002-10:=0000.00N/00000.00EeMXP600
20260914153719YO9ION-1>APBM1D,TETRA*,qAR,BM2002-10:=0000.00N/00000.00EeMXP600
20260914153847YO9ION-1>APBM1D,TETRA*,qAR,BM2002-10:=0000.00N/00000.00EeMXP600