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
20190720185323EA5IEV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5IEV-DP!373722.73N/05915.6rRNG0034 IPSC2-EA-Hotspot MMDVM 435.0000 MHz
20190720191043EA5IEV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5IEV-DP!373722.73N/05915.6rRNG0034 IPSC2-EA-Hotspot MMDVM 435.0000 MHz
20190720192748EA5IEV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5IEV-DP!373722.73N/05915.6rRNG0034 IPSC2-EA-Hotspot MMDVM 435.0000 MHz
20190720194448EA5IEV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5IEV-DP!373722.73N/05915.6rRNG0034 IPSC2-EA-Hotspot MMDVM 435.0000 MHz
20190720200153EA5IEV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5IEV-DP!373722.73N/05915.6rRNG0034 IPSC2-EA-Hotspot MMDVM 435.0000 MHz
20190720201854EA5IEV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5IEV-DP!373722.73N/05915.6rRNG0034 IPSC2-EA-Hotspot MMDVM 435.0000 MHz
20190720203601EA5IEV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5IEV-DP!373722.73N/05915.6rRNG0034 IPSC2-EA-Hotspot MMDVM 435.0000 MHz
20190720205331EA5IEV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5IEV-DP!373722.73N/05915.6rRNG0034 IPSC2-EA-Hotspot MMDVM 435.0000 MHz
20190720211030EA5IEV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5IEV-DP!373722.73N/05915.6rRNG0034 IPSC2-EA-Hotspot MMDVM 435.0000 MHz
20190720212728EA5IEV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5IEV-DP!373722.73N/05915.6rRNG0034 IPSC2-EA-Hotspot MMDVM 435.0000 MHz
20190720214429EA5IEV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5IEV-DP!373722.73N/05915.6rRNG0034 IPSC2-EA-Hotspot MMDVM 435.0000 MHz
20190720220125EA5IEV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5IEV-DP!373722.73N/05915.6rRNG0034 IPSC2-EA-Hotspot MMDVM 435.0000 MHz
20190720221826EA5IEV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5IEV-DP!373722.73N/05915.6rRNG0034 IPSC2-EA-Hotspot MMDVM 435.0000 MHz
20190720223536EA5IEV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5IEV-DP!373722.73N/05915.6rRNG0034 IPSC2-EA-Hotspot MMDVM 435.0000 MHz
20190720225233EA5IEV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5IEV-DP!373722.73N/05915.6rRNG0034 IPSC2-EA-Hotspot MMDVM 435.0000 MHz
20190720230929EA5IEV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5IEV-DP!373722.73N/05915.6rRNG0034 IPSC2-EA-Hotspot MMDVM 435.0000 MHz
20190720234323EA5IEV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5IEV-DP!373722.73N/05915.6rRNG0034 IPSC2-EA-Hotspot MMDVM 435.0000 MHz
20190721000019EA5IEV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5IEV-DP!373722.73N/05915.6rRNG0034 IPSC2-EA-Hotspot MMDVM 435.0000 MHz
20190721001719EA5IEV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5IEV-DP!373722.73N/05915.6rRNG0034 IPSC2-EA-Hotspot MMDVM 435.0000 MHz
20190721003416EA5IEV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5IEV-DP!373722.73N/05915.6rRNG0034 IPSC2-EA-Hotspot MMDVM 435.0000 MHz