APRS Packet Errors for EA5IEV (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
20190718093729EA5IEV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5IEV-DP!373722.73N/05915.6rRNG0034 IPSC2-EA-Hotspot MMDVM 435.0000 MHz
20190718095442EA5IEV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5IEV-DP!373722.73N/05915.6rRNG0034 IPSC2-EA-Hotspot MMDVM 435.0000 MHz
20190718101201EA5IEV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5IEV-DP!373722.73N/05915.6rRNG0034 IPSC2-EA-Hotspot MMDVM 435.0000 MHz
20190718102912EA5IEV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5IEV-DP!373722.73N/05915.6rRNG0034 IPSC2-EA-Hotspot MMDVM 435.0000 MHz
20190718104622EA5IEV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5IEV-DP!373722.73N/05915.6rRNG0034 IPSC2-EA-Hotspot MMDVM 435.0000 MHz
20190718110330EA5IEV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5IEV-DP!373722.73N/05915.6rRNG0034 IPSC2-EA-Hotspot MMDVM 435.0000 MHz
20190718112054EA5IEV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5IEV-DP!373722.73N/05915.6rRNG0034 IPSC2-EA-Hotspot MMDVM 435.0000 MHz
20190718113806EA5IEV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5IEV-DP!373722.73N/05915.6rRNG0034 IPSC2-EA-Hotspot MMDVM 435.0000 MHz
20190718115520EA5IEV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5IEV-DP!373722.73N/05915.6rRNG0034 IPSC2-EA-Hotspot MMDVM 435.0000 MHz
20190718121244EA5IEV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5IEV-DP!373722.73N/05915.6rRNG0034 IPSC2-EA-Hotspot MMDVM 435.0000 MHz
20190718122939EA5IEV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5IEV-DP!373722.73N/05915.6rRNG0034 IPSC2-EA-Hotspot MMDVM 435.0000 MHz
20190718124635EA5IEV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5IEV-DP!373722.73N/05915.6rRNG0034 IPSC2-EA-Hotspot MMDVM 435.0000 MHz
20190718130344EA5IEV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5IEV-DP!373722.73N/05915.6rRNG0034 IPSC2-EA-Hotspot MMDVM 435.0000 MHz
20190718132054EA5IEV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5IEV-DP!373722.73N/05915.6rRNG0034 IPSC2-EA-Hotspot MMDVM 435.0000 MHz
20190718133801EA5IEV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5IEV-DP!373722.73N/05915.6rRNG0034 IPSC2-EA-Hotspot MMDVM 435.0000 MHz
20190718135509EA5IEV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5IEV-DP!373722.73N/05915.6rRNG0034 IPSC2-EA-Hotspot MMDVM 435.0000 MHz
20190718141218EA5IEV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5IEV-DP!373722.73N/05915.6rRNG0034 IPSC2-EA-Hotspot MMDVM 435.0000 MHz
20190718142938EA5IEV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5IEV-DP!373722.73N/05915.6rRNG0034 IPSC2-EA-Hotspot MMDVM 435.0000 MHz
20190718144643EA5IEV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5IEV-DP!373722.73N/05915.6rRNG0034 IPSC2-EA-Hotspot MMDVM 435.0000 MHz
20190718150349EA5IEV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5IEV-DP!373722.73N/05915.6rRNG0034 IPSC2-EA-Hotspot MMDVM 435.0000 MHz
20190718152050EA5IEV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5IEV-DP!373722.73N/05915.6rRNG0034 IPSC2-EA-Hotspot MMDVM 435.0000 MHz