APRS Packet Errors for E22DXH-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
20260209144509	E22DXH-1>AESPG4,TCPIP*,qAC,T2YANTAI:!1439.01N/10101.02E;APRS
20260209151554	E22DXH-1>AESPG4,TCPIP*,qAC,T2YANTAI:!1439.01N/10101.02E;APRS
20260209154613	E22DXH-1>AESPG4,TCPIP*,qAC,T2YANTAI:!1439.01N/10101.02E;APRS
20260209161624	E22DXH-1>AESPG4,TCPIP*,qAC,T2YANTAI:!1439.01N/10101.02E;APRS
20260209164650	E22DXH-1>AESPG4,TCPIP*,qAC,T2YANTAI:!1439.01N/10101.02E;APRS
20260209171747	E22DXH-1>AESPG4,TCPIP*,qAC,T2YANTAI:!1439.01N/10101.02E;APRS
20260209174740	E22DXH-1>AESPG4,TCPIP*,qAC,T2YANTAI:!1439.01N/10101.02E;APRS
20260209181807	E22DXH-1>AESPG4,TCPIP*,qAC,T2YANTAI:!1439.01N/10101.02E;APRS
20260209184831	E22DXH-1>AESPG4,TCPIP*,qAC,T2YANTAI:!1439.01N/10101.02E;APRS
20260209191856	E22DXH-1>AESPG4,TCPIP*,qAC,T2YANTAI:!1439.01N/10101.02E;APRS
20260209194921	E22DXH-1>AESPG4,TCPIP*,qAC,T2YANTAI:!1439.01N/10101.02E;APRS
20260209201946	E22DXH-1>AESPG4,TCPIP*,qAC,T2YANTAI:!1439.01N/10101.02E;APRS