APRS Packet Errors for K9MEV-10 (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
20260209110227K9MEV-10>APX210,TCPIP*,qAC,SECOND:=4150.42N/08818.10WIK9MEV IGate Xastir on Raspberry Pi
20260209113228K9MEV-10>APX210,TCPIP*,qAC,SECOND:=4150.42N/08818.10WIK9MEV IGate Xastir on Raspberry Pi
20260209120229K9MEV-10>APX210,TCPIP*,qAC,SECOND:=4150.42N/08818.10WIK9MEV IGate Xastir on Raspberry Pi
20260209123230K9MEV-10>APX210,TCPIP*,qAC,SECOND:=4150.42N/08818.10WIK9MEV IGate Xastir on Raspberry Pi
20260209130231K9MEV-10>APX210,TCPIP*,qAC,SECOND:=4150.42N/08818.10WIK9MEV IGate Xastir on Raspberry Pi
20260209133232K9MEV-10>APX210,TCPIP*,qAC,SECOND:=4150.42N/08818.10WIK9MEV IGate Xastir on Raspberry Pi
20260209140233K9MEV-10>APX210,TCPIP*,qAC,SECOND:=4150.42N/08818.10WIK9MEV IGate Xastir on Raspberry Pi
20260209143234K9MEV-10>APX210,TCPIP*,qAC,SECOND:=4150.42N/08818.10WIK9MEV IGate Xastir on Raspberry Pi
20260209150235K9MEV-10>APX210,TCPIP*,qAC,SECOND:=4150.42N/08818.10WIK9MEV IGate Xastir on Raspberry Pi
20260209153236K9MEV-10>APX210,TCPIP*,qAC,SECOND:=4150.42N/08818.10WIK9MEV IGate Xastir on Raspberry Pi
20260209160237K9MEV-10>APX210,TCPIP*,qAC,SECOND:=4150.42N/08818.10WIK9MEV IGate Xastir on Raspberry Pi
20260209163238K9MEV-10>APX210,TCPIP*,qAC,SECOND:=4150.42N/08818.10WIK9MEV IGate Xastir on Raspberry Pi