APRS Packet Errors for 9W4GAW-2 (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
20260208150706	9W4GAW-2>APLRG1,TCPIP*,qAC,T2PERTH:!LM"%vh2T+a GLoRa APRS (I-GATE) Batt=4.17V
20260208153706	9W4GAW-2>APLRG1,TCPIP*,qAC,T2PERTH:!LM"%vh2T+a GLoRa APRS (I-GATE) Batt=4.17V
20260208160706	9W4GAW-2>APLRG1,TCPIP*,qAC,T2PERTH:!LM"%vh2T+a GLoRa APRS (I-GATE) Batt=4.20V
20260208163706	9W4GAW-2>APLRG1,TCPIP*,qAC,T2PERTH:!LM"%vh2T+a GLoRa APRS (I-GATE) Batt=4.17V
20260208170706	9W4GAW-2>APLRG1,TCPIP*,qAC,T2PERTH:!LM"%vh2T+a GLoRa APRS (I-GATE) Batt=4.21V
20260208173706	9W4GAW-2>APLRG1,TCPIP*,qAC,T2PERTH:!LM"%vh2T+a GLoRa APRS (I-GATE) Batt=4.19V
20260208180706	9W4GAW-2>APLRG1,TCPIP*,qAC,T2CHILE:!LM"%vh2T+a GLoRa APRS (I-GATE) Batt=4.27V
20260208183707	9W4GAW-2>APLRG1,TCPIP*,qAC,T2CHILE:!LM"%vh2T+a GLoRa APRS (I-GATE) Batt=4.28V
20260208190707	9W4GAW-2>APLRG1,TCPIP*,qAC,T2CHILE:!LM"%vh2T+a GLoRa APRS (I-GATE) Batt=4.18V
20260208193707	9W4GAW-2>APLRG1,TCPIP*,qAC,T2CHILE:!LM"%vh2T+a GLoRa APRS (I-GATE) Batt=4.23V
20260208200709	9W4GAW-2>APLRG1,TCPIP*,qAC,T2CHILE:!LM"%vh2T+a GLoRa APRS (I-GATE) Batt=4.23V
20260208203707	9W4GAW-2>APLRG1,TCPIP*,qAC,T2CHILE:!LM"%vh2T+a GLoRa APRS (I-GATE) Batt=4.24V