APRS Packet Errors for EA4RO (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
20190217141235EA4RO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4RO-DP!4022.80N/-03-44.12rRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20190217142907EA4RO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4RO-DP!4022.80N/-03-44.12rRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20190217144539EA4RO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4RO-DP!4022.80N/-03-44.12rRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20190217150218EA4RO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4RO-DP!4022.80N/-03-44.12rRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20190217151850EA4RO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4RO-DP!4022.80N/-03-44.12rRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20190217153524EA4RO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4RO-DP!4022.80N/-03-44.12rRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20190217155207EA4RO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4RO-DP!4022.80N/-03-44.12rRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20190217160854EA4RO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4RO-DP!4022.80N/-03-44.12rRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20190217162540EA4RO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4RO-DP!4022.80N/-03-44.12rRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20190217164217EA4RO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4RO-DP!4022.80N/-03-44.12rRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20190217165856EA4RO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4RO-DP!4022.80N/-03-44.12rRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20190217171556EA4RO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4RO-DP!4022.80N/-03-44.12rRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20190217173242EA4RO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4RO-DP!4022.80N/-03-44.12rRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20190217174940EA4RO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4RO-DP!4022.80N/-03-44.12rRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20190217180620EA4RO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4RO-DP!4022.80N/-03-44.12rRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20190217182253EA4RO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4RO-DP!4022.80N/-03-44.12rRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20190217183954EA4RO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4RO-DP!4022.80N/-03-44.12rRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20190217185655EA4RO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4RO-DP!4022.80N/-03-44.12rRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20190217191339EA4RO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4RO-DP!4022.80N/-03-44.12rRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20190217193014EA4RO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4RO-DP!4022.80N/-03-44.12rRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20190217194654EA4RO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4RO-DP!4022.80N/-03-44.12rRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20190217200345EA4RO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4RO-DP!4022.80N/-03-44.12rRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz