APRS Packet Errors for EA1DZR (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
20190717065009EA1DZR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1DZR-DP!4331.56N/-05-40.00rRNG0034 IPSC2-EA1Master MMDVM 433.0000 MHz
20190717070655EA1DZR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1DZR-DP!4331.56N/-05-40.00rRNG0034 IPSC2-EA1Master MMDVM 433.0000 MHz
20190717072342EA1DZR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1DZR-DP!4331.56N/-05-40.00rRNG0034 IPSC2-EA1Master MMDVM 433.0000 MHz
20190717074028EA1DZR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1DZR-DP!4331.56N/-05-40.00rRNG0034 IPSC2-EA1Master MMDVM 433.0000 MHz
20190717075716EA1DZR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1DZR-DP!4331.56N/-05-40.00rRNG0034 IPSC2-EA1Master MMDVM 433.0000 MHz
20190717081404EA1DZR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1DZR-DP!4331.56N/-05-40.00rRNG0034 IPSC2-EA1Master MMDVM 433.0000 MHz
20190717092121EA1DZR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1DZR-DP!4331.56N/-05-40.00rRNG0034 IPSC2-EA1Master MMDVM 433.0000 MHz
20190717093806EA1DZR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1DZR-DP!4331.56N/-05-40.00rRNG0034 IPSC2-EA1Master MMDVM 433.0000 MHz
20190717095455EA1DZR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1DZR-DP!4331.56N/-05-40.00rRNG0034 IPSC2-EA1Master MMDVM 433.0000 MHz
20190717101145EA1DZR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1DZR-DP!4331.56N/-05-40.00rRNG0034 IPSC2-EA1Master MMDVM 433.0000 MHz