APRS Packet Errors for G4DDG-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
20260209122011G4DDG-10>APLRG1,TCPIP*,qAC,T2SYDNEY:=L4bIsMAyc# !GDevon Data Group Batt=4.02V
20260209125011G4DDG-10>APLRG1,TCPIP*,qAC,T2SYDNEY:=L4bIsMAyc# !GDevon Data Group Batt=4.03V
20260209132011G4DDG-10>APLRG1,TCPIP*,qAC,T2SYDNEY:=L4bIsMAyc# !GDevon Data Group Batt=4.01V
20260209135011G4DDG-10>APLRG1,TCPIP*,qAC,T2SYDNEY:=L4bIsMAyc# !GDevon Data Group Batt=4.04V
20260209142011G4DDG-10>APLRG1,TCPIP*,qAC,T2SYDNEY:=L4bIsMAyc# !GDevon Data Group Batt=4.03V
20260209145011G4DDG-10>APLRG1,TCPIP*,qAC,T2SYDNEY:=L4bIsMAyc# !GDevon Data Group Batt=4.02V
20260209152011G4DDG-10>APLRG1,TCPIP*,qAC,T2SYDNEY:=L4bIsMAyc# !GDevon Data Group Batt=4.02V
20260209155012G4DDG-10>APLRG1,TCPIP*,qAC,T2SYDNEY:=L4bIsMAyc# !GDevon Data Group Batt=4.03V
20260209162012G4DDG-10>APLRG1,TCPIP*,qAC,T2SYDNEY:=L4bIsMAyc# !GDevon Data Group Batt=4.03V
20260209165012G4DDG-10>APLRG1,TCPIP*,qAC,T2SYDNEY:=L4bIsMAyc# !GDevon Data Group Batt=4.02V
20260209172012G4DDG-10>APLRG1,TCPIP*,qAC,T2SYDNEY:=L4bIsMAyc# !GDevon Data Group Batt=4.00V
20260209175012G4DDG-10>APLRG1,TCPIP*,qAC,T2SYDNEY:=L4bIsMAyc# !GDevon Data Group Batt=4.01V