APRS Packet Errors for EA1EPD-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
20260208152231EA1EPD-10>APLRG1,TCPIP*,qAC,T2CHILE:!L8oTVL7GTa GLoRa APRS Noia Batt=4.29V
20260208155231EA1EPD-10>APLRG1,TCPIP*,qAC,T2CHILE:!L8oTVL7GTa GLoRa APRS Noia Batt=4.24V
20260208162231EA1EPD-10>APLRG1,TCPIP*,qAC,T2CHILE:!L8oTVL7GTa GLoRa APRS Noia Batt=4.32V
20260208165231EA1EPD-10>APLRG1,TCPIP*,qAC,T2CHILE:!L8oTVL7GTa GLoRa APRS Noia Batt=4.25V
20260208172231EA1EPD-10>APLRG1,TCPIP*,qAC,T2CHILE:!L8oTVL7GTa GLoRa APRS Noia Batt=4.28V
20260208175231EA1EPD-10>APLRG1,TCPIP*,qAC,T2CHILE:!L8oTVL7GTa GLoRa APRS Noia Batt=4.21V
20260208182231EA1EPD-10>APLRG1,TCPIP*,qAC,T2CHILE:!L8oTVL7GTa GLoRa APRS Noia Batt=4.25V
20260208185231EA1EPD-10>APLRG1,TCPIP*,qAC,T2CHILE:!L8oTVL7GTa GLoRa APRS Noia Batt=4.30V
20260208192231EA1EPD-10>APLRG1,TCPIP*,qAC,T2CHILE:!L8oTVL7GTa GLoRa APRS Noia Batt=4.23V
20260208195231EA1EPD-10>APLRG1,TCPIP*,qAC,T2CHILE:!L8oTVL7GTa GLoRa APRS Noia Batt=4.25V
20260208202232EA1EPD-10>APLRG1,TCPIP*,qAC,T2CHILE:!L8oTVL7GTa GLoRa APRS Noia Batt=4.29V
20260208205232EA1EPD-10>APLRG1,TCPIP*,qAC,T2CHILE:!L8oTVL7GTa GLoRa APRS Noia Batt=4.25V