APRS Packet Errors for EA3HXZ-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
20260208141524	EA3HXZ-10>APLRG1,TCPIP*,qAC,T2CAEAST:!L9G:fO,8r& GIGate Batt=4.22V
20260208151524	EA3HXZ-10>APLRG1,TCPIP*,qAC,T2CAEAST:!L9G:fO,8r& GIGate Batt=4.38V
20260208161524	EA3HXZ-10>APLRG1,TCPIP*,qAC,T2CAEAST:!L9G:fO,8r& GIGate Batt=4.35V
20260208171524	EA3HXZ-10>APLRG1,TCPIP*,qAC,T2CAEAST:!L9G:fO,8r& GIGate Batt=4.30V
20260208181524	EA3HXZ-10>APLRG1,TCPIP*,qAC,T2CAEAST:!L9G:fO,8r& GIGate Batt=4.36V
20260208191524	EA3HXZ-10>APLRG1,TCPIP*,qAC,T2CAEAST:!L9G:fO,8r& GIGate Batt=4.39V