APRS Packet Errors for EA5HXT-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
20260208133637EA5HXT-10>APLRG1,TCPIP*,qAC,T2CHILE:!L:uH=NC6Da GLoRa APRS iGate 433.775 Mhz Batt=4.26V
20260208140637EA5HXT-10>APLRG1,TCPIP*,qAC,T2CHILE:!L:uH=NC6Da GLoRa APRS iGate 433.775 Mhz Batt=4.23V
20260208143637EA5HXT-10>APLRG1,TCPIP*,qAC,T2CHILE:!L:uH=NC6Da GLoRa APRS iGate 433.775 Mhz Batt=4.29V
20260208150637EA5HXT-10>APLRG1,TCPIP*,qAC,T2CHILE:!L:uH=NC6Da GLoRa APRS iGate 433.775 Mhz Batt=4.29V
20260208153638EA5HXT-10>APLRG1,TCPIP*,qAC,T2CHILE:!L:uH=NC6Da GLoRa APRS iGate 433.775 Mhz Batt=4.29V
20260208160638EA5HXT-10>APLRG1,TCPIP*,qAC,T2CHILE:!L:uH=NC6Da GLoRa APRS iGate 433.775 Mhz Batt=4.22V
20260208163638EA5HXT-10>APLRG1,TCPIP*,qAC,T2CHILE:!L:uH=NC6Da GLoRa APRS iGate 433.775 Mhz Batt=4.25V
20260208170638EA5HXT-10>APLRG1,TCPIP*,qAC,T2CHILE:!L:uH=NC6Da GLoRa APRS iGate 433.775 Mhz Batt=4.25V
20260208173638EA5HXT-10>APLRG1,TCPIP*,qAC,T2CHILE:!L:uH=NC6Da GLoRa APRS iGate 433.775 Mhz Batt=4.27V
20260208180638EA5HXT-10>APLRG1,TCPIP*,qAC,T2CHILE:!L:uH=NC6Da GLoRa APRS iGate 433.775 Mhz Batt=4.23V
20260208183638EA5HXT-10>APLRG1,TCPIP*,qAC,T2CHILE:!L:uH=NC6Da GLoRa APRS iGate 433.775 Mhz Batt=4.24V
20260208190638EA5HXT-10>APLRG1,TCPIP*,qAC,T2CHILE:!L:uH=NC6Da GLoRa APRS iGate 433.775 Mhz Batt=4.28V