APRS Packet Errors for EA7DMP (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
20190420122751EA7DMP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DMP-DP!3753.18N/-04-21.98rRNG0034 IPSC2-EA4Master MMDVM 439.9750 MHz
20190420124458EA7DMP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DMP-DP!3753.18N/-04-21.98rRNG0034 IPSC2-EA4Master MMDVM 439.9750 MHz
20190420130158EA7DMP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DMP-DP!3753.18N/-04-21.98rRNG0034 IPSC2-EA4Master MMDVM 439.9750 MHz
20190420131853EA7DMP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DMP-DP!3753.18N/-04-21.98rRNG0034 IPSC2-EA4Master MMDVM 439.9750 MHz
20190420133554EA7DMP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DMP-DP!3753.18N/-04-21.98rRNG0034 IPSC2-EA4Master MMDVM 439.9750 MHz
20190420135253EA7DMP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DMP-DP!3753.18N/-04-21.98rRNG0034 IPSC2-EA4Master MMDVM 439.9750 MHz
20190420140951EA7DMP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DMP-DP!3753.18N/-04-21.98rRNG0034 IPSC2-EA4Master MMDVM 439.9750 MHz
20190420142650EA7DMP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DMP-DP!3753.18N/-04-21.98rRNG0034 IPSC2-EA4Master MMDVM 439.9750 MHz
20190420155148EA7DMP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DMP-DP!3753.18N/-04-21.98rRNG0034 IPSC2-EA4Master MMDVM 439.9750 MHz
20190420160856EA7DMP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DMP-DP!3753.18N/-04-21.98rRNG0034 IPSC2-EA4Master MMDVM 439.9750 MHz
20190420162603EA7DMP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DMP-DP!3753.18N/-04-21.98rRNG0034 IPSC2-EA4Master MMDVM 439.9750 MHz
20190420163710EA7DMP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DMP-DP!3753.18N/-04-48.41rRNG0034 IPSC2-DL-HOTSPOT MMDVM 438.1750 MHz
20190420164311EA7DMP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DMP-DP!3753.18N/-04-21.98rRNG0034 IPSC2-EA4Master MMDVM 439.9750 MHz
20190420165623EA7DMP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DMP-DP!3753.18N/-04-48.41rRNG0034 IPSC2-DL-HOTSPOT MMDVM 438.1750 MHz
20190420170004EA7DMP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DMP-DP!3753.18N/-04-21.98rRNG0034 IPSC2-EA4Master MMDVM 439.9750 MHz
20190420171656EA7DMP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DMP-DP!3753.18N/-04-21.98rRNG0034 IPSC2-EA4Master MMDVM 439.9750 MHz
20190420173404EA7DMP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DMP-DP!3753.18N/-04-21.98rRNG0034 IPSC2-EA4Master MMDVM 439.9750 MHz
20190420175121EA7DMP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DMP-DP!3753.18N/-04-21.98rRNG0034 IPSC2-EA4Master MMDVM 439.9750 MHz
20190420180845EA7DMP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DMP-DP!3753.18N/-04-21.98rRNG0034 IPSC2-EA4Master MMDVM 439.9750 MHz