APRS Packet Errors for DL9TPA-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
20260209092751DL9TPA-10>APRS,TCPIP*,qAC,T2PERTH:=5050.23N/01256.07E&Python iGate
20260209095751DL9TPA-10>APRS,TCPIP*,qAC,T2PERTH:=5050.23N/01256.07E&Python iGate
20260209102751DL9TPA-10>APRS,TCPIP*,qAC,T2PERTH:=5050.23N/01256.07E&Python iGate
20260209105751DL9TPA-10>APRS,TCPIP*,qAC,T2PERTH:=5050.23N/01256.07E&Python iGate
20260209112751DL9TPA-10>APRS,TCPIP*,qAC,T2PERTH:=5050.23N/01256.07E&Python iGate
20260209115751DL9TPA-10>APRS,TCPIP*,qAC,T2PERTH:=5050.23N/01256.07E&Python iGate
20260209122751DL9TPA-10>APRS,TCPIP*,qAC,T2PERTH:=5050.23N/01256.07E&Python iGate
20260209125751DL9TPA-10>APRS,TCPIP*,qAC,T2PERTH:=5050.23N/01256.07E&Python iGate
20260209132751DL9TPA-10>APRS,TCPIP*,qAC,T2PERTH:=5050.23N/01256.07E&Python iGate
20260209135751DL9TPA-10>APRS,TCPIP*,qAC,T2PERTH:=5050.23N/01256.07E&Python iGate
20260209143144DL9TPA-10>APRS,TCPIP*,qAC,T2SYDNEY:=5050.23N/01256.07E&Python iGate
20260209150144DL9TPA-10>APRS,TCPIP*,qAC,T2SYDNEY:=5050.23N/01256.07E&Python iGate