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
20260209103951PD2APD-10>APLRG1,TCPIP*,qAC,T2UKRAINE:!L4+9OP!i:a GLoRa APRS Batt=4.32V
20260209113951PD2APD-10>APLRG1,TCPIP*,qAC,T2UKRAINE:!L4+9OP!i:a GLoRa APRS Batt=4.33V
20260209114643PD2APD-10>APLRG1,TCPIP*,qAC,T2SYDNEY:!L4+9OP!i:a GLoRa APRS Batt=4.24V
20260209120325PD2APD-10>APLRG1,TCPIP*,qAC,T2SYDNEY:!L4+9OP!i:a GLoRa APRS Batt=4.31V
20260209122355PD2APD-10>APLRG1,TCPIP*,qAC,T2TAS:!L4+9OP!i:a GLoRa APRS Batt=4.28V
20260209130133PD2APD-10>APLRG1,TCPIP*,qAC,T2SYDNEY:!L4+9OP!i:a GLoRa APRS Batt=4.27V
20260209131654PD2APD-10>APLRG1,TCPIP*,qAC,T2ROMANIA:!L4+9OP!i:a GLoRa APRS Batt=4.29V
20260209132105PD2APD-10>APLRG1,TCPIP*,qAC,T2SYDNEY:!L4+9OP!i:a GLoRa APRS Batt=4.27V
20260209135604PD2APD-10>APLRG1,TCPIP*,qAC,T2UKRAINE:!L4+9OP!i:a GLoRa APRS Batt=4.32V
20260209142431PD2APD-10>APLRG1,TCPIP*,qAC,T2CSNGRAD:!L4+9OP!i:a GLoRa APRS Batt=4.29V
20260209152432PD2APD-10>APLRG1,TCPIP*,qAC,T2CSNGRAD:!L4+9OP!i:a GLoRa APRS Batt=4.31V
20260209153421PD2APD-10>APLRG1,TCPIP*,qAC,T2GB:!L4+9OP!i:a GLoRa APRS Batt=4.28V