APRS Packet Errors for EC5ZY (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
20190420102825EC5ZY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EC5ZY-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA4Master MMDVM 144.8250 MHz
20190420144358EC5ZY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EC5ZY-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA4Master MMDVM 144.8250 MHz
20190420150051EC5ZY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EC5ZY-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA4Master MMDVM 144.8250 MHz
20190420151742EC5ZY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EC5ZY-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA4Master MMDVM 144.8250 MHz
20190420153441EC5ZY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EC5ZY-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA4Master MMDVM 144.8250 MHz
20190420155148EC5ZY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EC5ZY-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA4Master MMDVM 144.8250 MHz
20190420160856EC5ZY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EC5ZY-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA4Master MMDVM 144.8250 MHz
20190420162603EC5ZY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EC5ZY-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA4Master MMDVM 144.8250 MHz