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
20190520153547EA1DZR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1DZR-DP!4331.48N/-05-40.00rRNG0034 IPSC2-EA1Master MMDVM 432.0000 MHz
20190520155229EA1DZR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1DZR-DP!4331.48N/-05-40.00rRNG0034 IPSC2-EA1Master MMDVM 432.0000 MHz
20190520160915EA1DZR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1DZR-DP!4331.48N/-05-40.00rRNG0034 IPSC2-EA1Master MMDVM 432.0000 MHz
20190520162600EA1DZR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1DZR-DP!4331.48N/-05-40.00rRNG0034 IPSC2-EA1Master MMDVM 432.0000 MHz
20190520164248EA1DZR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1DZR-DP!4331.48N/-05-40.00rRNG0034 IPSC2-EA1Master MMDVM 432.0000 MHz
20190520165933EA1DZR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1DZR-DP!4331.48N/-05-40.00rRNG0034 IPSC2-EA1Master MMDVM 432.0000 MHz
20190520171615EA1DZR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1DZR-DP!4331.48N/-05-40.00rRNG0034 IPSC2-EA1Master MMDVM 432.0000 MHz
20190520173309EA1DZR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1DZR-DP!4331.48N/-05-40.00rRNG0034 IPSC2-EA1Master MMDVM 432.0000 MHz
20190520175000EA1DZR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1DZR-DP!4331.48N/-05-40.00rRNG0034 IPSC2-EA1Master MMDVM 432.0000 MHz
20190520180650EA1DZR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1DZR-DP!4331.48N/-05-40.00rRNG0034 IPSC2-EA1Master MMDVM 432.0000 MHz
20190520182337EA1DZR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1DZR-DP!4331.48N/-05-40.00rRNG0034 IPSC2-EA1Master MMDVM 432.0000 MHz
20190520184030EA1DZR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1DZR-DP!4331.48N/-05-40.00rRNG0034 IPSC2-EA1Master MMDVM 432.0000 MHz
20190520185720EA1DZR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1DZR-DP!4331.48N/-05-40.00rRNG0034 IPSC2-EA1Master MMDVM 432.0000 MHz
20190520191409EA1DZR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1DZR-DP!4331.48N/-05-40.00rRNG0034 IPSC2-EA1Master MMDVM 432.0000 MHz
20190520193056EA1DZR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1DZR-DP!4331.48N/-05-40.00rRNG0034 IPSC2-EA1Master MMDVM 432.0000 MHz
20190520194743EA1DZR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1DZR-DP!4331.48N/-05-40.00rRNG0034 IPSC2-EA1Master MMDVM 432.0000 MHz
20190520200431EA1DZR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1DZR-DP!4331.48N/-05-40.00rRNG0034 IPSC2-EA1Master MMDVM 432.0000 MHz
20190520202114EA1DZR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1DZR-DP!4331.48N/-05-40.00rRNG0034 IPSC2-EA1Master MMDVM 432.0000 MHz
20190520203800EA1DZR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1DZR-DP!4331.48N/-05-40.00rRNG0034 IPSC2-EA1Master MMDVM 432.0000 MHz