APRS Packet Errors for VE3UUU (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
20200807033147VE3UUU>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE3UUU-DP!0000.00N/00000.00ErRNG0034 IPSC2-CAN-RPTR Motorola 444.4000@+5.0 MHz
20200807040237VE3UUU>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE3UUU-DP!0000.00N/00000.00ErRNG0034 IPSC2-CAN-RPTR Motorola 444.4000@+5.0 MHz
20200807043337VE3UUU>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE3UUU-DP!0000.00N/00000.00ErRNG0034 IPSC2-CAN-RPTR Motorola 444.4000@+5.0 MHz
20200807050357VE3UUU>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE3UUU-DP!0000.00N/00000.00ErRNG0034 IPSC2-CAN-RPTR Motorola 444.4000@+5.0 MHz
20200807053456VE3UUU>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE3UUU-DP!0000.00N/00000.00ErRNG0034 IPSC2-CAN-RPTR Motorola 444.4000@+5.0 MHz
20200807060553VE3UUU>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE3UUU-DP!0000.00N/00000.00ErRNG0034 IPSC2-CAN-RPTR Motorola 444.4000@+5.0 MHz
20200807063634VE3UUU>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE3UUU-DP!0000.00N/00000.00ErRNG0034 IPSC2-CAN-RPTR Motorola 444.4000@+5.0 MHz
20200807080953VE3UUU>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE3UUU-DP!0000.00N/00000.00ErRNG0034 IPSC2-CAN-RPTR Motorola 444.4000@+5.0 MHz
20200807084050VE3UUU>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE3UUU-DP!0000.00N/00000.00ErRNG0034 IPSC2-CAN-RPTR Motorola 444.4000@+5.0 MHz