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
20190116190720EA7DMP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DMP-DP!3753.18N/-04-48.41rRNG0034 IPSC2-EA4Master MMDVM 438.1750 MHz
20190116192355EA7DMP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DMP-DP!3753.18N/-04-48.41rRNG0034 IPSC2-EA4Master MMDVM 438.1750 MHz
20190116194013EA7DMP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DMP-DP!3753.18N/-04-48.41rRNG0034 IPSC2-EA4Master MMDVM 438.1750 MHz
20190116195637EA7DMP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DMP-DP!3753.18N/-04-48.41rRNG0034 IPSC2-EA4Master MMDVM 438.1750 MHz
20190116201325EA7DMP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DMP-DP!3753.18N/-04-48.41rRNG0034 IPSC2-EA4Master MMDVM 438.1750 MHz
20190116202942EA7DMP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DMP-DP!3753.18N/-04-48.41rRNG0034 IPSC2-EA4Master MMDVM 438.1750 MHz
20190116204554EA7DMP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DMP-DP!3753.18N/-04-48.41rRNG0034 IPSC2-EA4Master MMDVM 438.1750 MHz
20190116210202EA7DMP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DMP-DP!3753.18N/-04-48.41rRNG0034 IPSC2-EA4Master MMDVM 438.1750 MHz