APRS Packet Errors for PD2APD-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
20260208143254PD2APD-10>APLRG1,TCPIP*,qAC,T2SYDNEY:!L4+9OP!i:a GLoRa APRS Batt=4.31V
20260208150809PD2APD-10>APLRG1,TCPIP*,qAC,T2PERTH:!L4+9OP!i:a GLoRa APRS Batt=4.27V
20260208155539PD2APD-10>APLRG1,TCPIP*,qAC,T2PERTH:!L4+9OP!i:a GLoRa APRS Batt=4.29V
20260208165539PD2APD-10>APLRG1,TCPIP*,qAC,T2PERTH:!L4+9OP!i:a GLoRa APRS Batt=4.31V
20260208165928PD2APD-10>APLRG1,TCPIP*,qAC,T2LUBLIN:!L4+9OP!i:a GLoRa APRS Batt=4.28V
20260208175928PD2APD-10>APLRG1,TCPIP*,qAC,T2LUBLIN:!L4+9OP!i:a GLoRa APRS Batt=4.25V
20260208185928PD2APD-10>APLRG1,TCPIP*,qAC,T2LUBLIN:!L4+9OP!i:a GLoRa APRS Batt=4.23V
20260208195929PD2APD-10>APLRG1,TCPIP*,qAC,T2LUBLIN:!L4+9OP!i:a GLoRa APRS Batt=4.30V