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
20190716060705EA5IEV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5IEV-DP!373722.73N/05915.6rRNG0034 IPSC2-EA-Hotspot MMDVM 435.0000 MHz
20190716062400EA5IEV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5IEV-DP!373722.73N/05915.6rRNG0034 IPSC2-EA-Hotspot MMDVM 435.0000 MHz
20190716064103EA5IEV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5IEV-DP!373722.73N/05915.6rRNG0034 IPSC2-EA-Hotspot MMDVM 435.0000 MHz
20190716065755EA5IEV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5IEV-DP!373722.73N/05915.6rRNG0034 IPSC2-EA-Hotspot MMDVM 435.0000 MHz
20190716071446EA5IEV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5IEV-DP!373722.73N/05915.6rRNG0034 IPSC2-EA-Hotspot MMDVM 435.0000 MHz
20190716073142EA5IEV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5IEV-DP!373722.73N/05915.6rRNG0034 IPSC2-EA-Hotspot MMDVM 435.0000 MHz
20190716074837EA5IEV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5IEV-DP!373722.73N/05915.6rRNG0034 IPSC2-EA-Hotspot MMDVM 435.0000 MHz
20190716080529EA5IEV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5IEV-DP!373722.73N/05915.6rRNG0034 IPSC2-EA-Hotspot MMDVM 435.0000 MHz
20190716082224EA5IEV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5IEV-DP!373722.73N/05915.6rRNG0034 IPSC2-EA-Hotspot MMDVM 435.0000 MHz
20190716083921EA5IEV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5IEV-DP!373722.73N/05915.6rRNG0034 IPSC2-EA-Hotspot MMDVM 435.0000 MHz
20190716085620EA5IEV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5IEV-DP!373722.73N/05915.6rRNG0034 IPSC2-EA-Hotspot MMDVM 435.0000 MHz
20190716091315EA5IEV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5IEV-DP!373722.73N/05915.6rRNG0034 IPSC2-EA-Hotspot MMDVM 435.0000 MHz
20190716093013EA5IEV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5IEV-DP!373722.73N/05915.6rRNG0034 IPSC2-EA-Hotspot MMDVM 435.0000 MHz
20190716094724EA5IEV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5IEV-DP!373722.73N/05915.6rRNG0034 IPSC2-EA-Hotspot MMDVM 435.0000 MHz
20190716100430EA5IEV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5IEV-DP!373722.73N/05915.6rRNG0034 IPSC2-EA-Hotspot MMDVM 435.0000 MHz
20190716102125EA5IEV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5IEV-DP!373722.73N/05915.6rRNG0034 IPSC2-EA-Hotspot MMDVM 435.0000 MHz
20190716103825EA5IEV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5IEV-DP!373722.73N/05915.6rRNG0034 IPSC2-EA-Hotspot MMDVM 435.0000 MHz
20190716105525EA5IEV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5IEV-DP!373722.73N/05915.6rRNG0034 IPSC2-EA-Hotspot MMDVM 435.0000 MHz
20190716111236EA5IEV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5IEV-DP!373722.73N/05915.6rRNG0034 IPSC2-EA-Hotspot MMDVM 435.0000 MHz
20190716112939EA5IEV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5IEV-DP!373722.73N/05915.6rRNG0034 IPSC2-EA-Hotspot MMDVM 435.0000 MHz
20190716114633EA5IEV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5IEV-DP!373722.73N/05915.6rRNG0034 IPSC2-EA-Hotspot MMDVM 435.0000 MHz