APRS Packet Errors for EA8EE-5 (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
20251013090727EA8EE-5>APLRG1,TCPIP*,qAC,T2SPAIN:!LoRa APRS Batt=3.65V
20251013092228EA8EE-5>APLRG1,TCPIP*,qAC,T2SPAIN:!LoRa APRS Batt=3.58V
20251013100729EA8EE-5>APLRG1,TCPIP*,qAC,T2SPAIN:!LoRa APRS Batt=3.59V
20251013102229EA8EE-5>APLRG1,TCPIP*,qAC,T2SPAIN:!LoRa APRS Batt=3.60V
20251013120732EA8EE-5>APLRG1,TCPIP*,qAC,T2SPAIN:!LoRa APRS Batt=3.58V
20251013122232EA8EE-5>APLRG1,TCPIP*,qAC,T2SPAIN:!LoRa APRS Batt=3.61V
20251013123732EA8EE-5>APLRG1,TCPIP*,qAC,T2SPAIN:!LoRa APRS Batt=3.55V
20251013125233EA8EE-5>APLRG1,TCPIP*,qAC,T2SPAIN:!LoRa APRS Batt=3.57V
20251013130733EA8EE-5>APLRG1,TCPIP*,qAC,T2SPAIN:!LoRa APRS Batt=3.60V