APRS Packet Errors for EA1AV-15 (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
20260209091946EA1AV-15>APLRG1,TCPIP*,qAC,T2SPAIN2:!L8xX5M(F$a GLoRa APRS Batt=4.28V
20260209094946EA1AV-15>APLRG1,TCPIP*,qAC,T2SPAIN2:!L8xX5M(F$a GLoRa APRS Batt=4.24V
20260209101946EA1AV-15>APLRG1,TCPIP*,qAC,T2SPAIN2:!L8xX5M(F$a GLoRa APRS Batt=4.31V
20260209104946EA1AV-15>APLRG1,TCPIP*,qAC,T2SPAIN2:!L8xX5M(F$a GLoRa APRS Batt=4.21V
20260209111946EA1AV-15>APLRG1,TCPIP*,qAC,T2SPAIN2:!L8xX5M(F$a GLoRa APRS Batt=4.33V
20260209114947EA1AV-15>APLRG1,TCPIP*,qAC,T2SPAIN2:!L8xX5M(F$a GLoRa APRS Batt=4.32V
20260209121947EA1AV-15>APLRG1,TCPIP*,qAC,T2SPAIN2:!L8xX5M(F$a GLoRa APRS Batt=4.37V
20260209124947EA1AV-15>APLRG1,TCPIP*,qAC,T2SPAIN2:!L8xX5M(F$a GLoRa APRS Batt=4.28V
20260209131947EA1AV-15>APLRG1,TCPIP*,qAC,T2SPAIN2:!L8xX5M(F$a GLoRa APRS Batt=4.35V
20260209134947EA1AV-15>APLRG1,TCPIP*,qAC,T2SPAIN2:!L8xX5M(F$a GLoRa APRS Batt=4.30V
20260209141947EA1AV-15>APLRG1,TCPIP*,qAC,T2SPAIN2:!L8xX5M(F$a GLoRa APRS Batt=4.34V
20260209144947EA1AV-15>APLRG1,TCPIP*,qAC,T2SPAIN2:!L8xX5M(F$a GLoRa APRS Batt=4.28V