APRS Packet Errors for DL1MA (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
20190616090935DL1MA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DL1MA-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 432.0000 MHz
20190616092729DL1MA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DL1MA-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 432.0000 MHz
20190616094509DL1MA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DL1MA-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 432.0000 MHz
20190616100255DL1MA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DL1MA-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 432.0000 MHz
20190616102111DL1MA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DL1MA-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 432.0000 MHz
20190616103827DL1MA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DL1MA-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 432.0000 MHz
20190616105607DL1MA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DL1MA-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 432.0000 MHz
20190616111359DL1MA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DL1MA-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 432.0000 MHz
20190616113145DL1MA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DL1MA-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 432.0000 MHz
20190616114946DL1MA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DL1MA-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 432.0000 MHz
20190616120806DL1MA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DL1MA-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 432.0000 MHz
20190616122612DL1MA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DL1MA-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 432.0000 MHz
20190616124420DL1MA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DL1MA-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 432.0000 MHz
20190616130200DL1MA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DL1MA-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 432.0000 MHz
20190616132010DL1MA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DL1MA-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 432.0000 MHz
20190616133843DL1MA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DL1MA-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 432.0000 MHz
20190616135658DL1MA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DL1MA-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 432.0000 MHz
20190616141557DL1MA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DL1MA-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 432.0000 MHz
20190616143458DL1MA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DL1MA-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 432.0000 MHz
20190616145244DL1MA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DL1MA-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 432.0000 MHz