APRS Packet Errors for EA1IPG (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
20190717165035EA1IPG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1IPG-DP!12500.00N/15000.00rRNG0034 IPSC2-EA-Hotspot MMDVM 144.8750 MHz
20190717170752EA1IPG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1IPG-DP!12500.00N/15000.00rRNG0034 IPSC2-EA-Hotspot MMDVM 144.8750 MHz
20190717172518EA1IPG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1IPG-DP!12500.00N/15000.00rRNG0034 IPSC2-EA-Hotspot MMDVM 144.8750 MHz
20190717174238EA1IPG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1IPG-DP!12500.00N/15000.00rRNG0034 IPSC2-EA-Hotspot MMDVM 144.8750 MHz
20190717175953EA1IPG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1IPG-DP!12500.00N/15000.00rRNG0034 IPSC2-EA-Hotspot MMDVM 144.8750 MHz
20190717181657EA1IPG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1IPG-DP!12500.00N/15000.00rRNG0034 IPSC2-EA-Hotspot MMDVM 144.8750 MHz
20190717183410EA1IPG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1IPG-DP!12500.00N/15000.00rRNG0034 IPSC2-EA-Hotspot MMDVM 144.8750 MHz
20190717185116EA1IPG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1IPG-DP!12500.00N/15000.00rRNG0034 IPSC2-EA-Hotspot MMDVM 144.8750 MHz
20190717190824EA1IPG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1IPG-DP!12500.00N/15000.00rRNG0034 IPSC2-EA-Hotspot MMDVM 144.8750 MHz
20190717192540EA1IPG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1IPG-DP!12500.00N/15000.00rRNG0034 IPSC2-EA-Hotspot MMDVM 144.8750 MHz
20190717194257EA1IPG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1IPG-DP!12500.00N/15000.00rRNG0034 IPSC2-EA-Hotspot MMDVM 144.8750 MHz
20190717200016EA1IPG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1IPG-DP!12500.00N/15000.00rRNG0034 IPSC2-EA-Hotspot MMDVM 144.8750 MHz
20190717201742EA1IPG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1IPG-DP!12500.00N/15000.00rRNG0034 IPSC2-EA-Hotspot MMDVM 144.8750 MHz
20190717203504EA1IPG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1IPG-DP!12500.00N/15000.00rRNG0034 IPSC2-EA-Hotspot MMDVM 144.8750 MHz
20190717205204EA1IPG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1IPG-DP!12500.00N/15000.00rRNG0034 IPSC2-EA-Hotspot MMDVM 144.8750 MHz
20190717210909EA1IPG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1IPG-DP!12500.00N/15000.00rRNG0034 IPSC2-EA-Hotspot MMDVM 144.8750 MHz
20190717212624EA1IPG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1IPG-DP!12500.00N/15000.00rRNG0034 IPSC2-EA-Hotspot MMDVM 144.8750 MHz
20190717214344EA1IPG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1IPG-DP!12500.00N/15000.00rRNG0034 IPSC2-EA-Hotspot MMDVM 144.8750 MHz
20190717220047EA1IPG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1IPG-DP!12500.00N/15000.00rRNG0034 IPSC2-EA-Hotspot MMDVM 144.8750 MHz
20190717221750EA1IPG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1IPG-DP!12500.00N/15000.00rRNG0034 IPSC2-EA-Hotspot MMDVM 144.8750 MHz
20190717223447EA1IPG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1IPG-DP!12500.00N/15000.00rRNG0034 IPSC2-EA-Hotspot MMDVM 144.8750 MHz