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
20191023084221DL1MA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DL1MA-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 432.0000 MHz
20191023085743DL1MA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DL1MA-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 432.0000 MHz
20191023091307DL1MA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DL1MA-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 432.0000 MHz
20191023092829DL1MA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DL1MA-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 432.0000 MHz
20191023094351DL1MA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DL1MA-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 432.0000 MHz
20191023095913DL1MA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DL1MA-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 432.0000 MHz
20191023101440DL1MA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DL1MA-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 432.0000 MHz
20191023103043DL1MA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DL1MA-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 432.0000 MHz
20191023104605DL1MA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DL1MA-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 432.0000 MHz
20191023110128DL1MA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DL1MA-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 432.0000 MHz
20191023111652DL1MA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DL1MA-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 432.0000 MHz
20191023113214DL1MA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DL1MA-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 432.0000 MHz
20191023114734DL1MA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DL1MA-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 432.0000 MHz
20191023120255DL1MA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DL1MA-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 432.0000 MHz
20191023121819DL1MA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DL1MA-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 432.0000 MHz
20191023123341DL1MA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DL1MA-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 432.0000 MHz
20191023124903DL1MA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DL1MA-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 432.0000 MHz
20191023130429DL1MA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DL1MA-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 432.0000 MHz
20191023131958DL1MA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DL1MA-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 432.0000 MHz
20191023133521DL1MA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DL1MA-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 432.0000 MHz
20191023135045DL1MA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DL1MA-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 432.0000 MHz
20191023140608DL1MA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DL1MA-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 432.0000 MHz
20191023142134DL1MA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DL1MA-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 432.0000 MHz
20191023143659DL1MA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DL1MA-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 432.0000 MHz