APRS Packet Errors for EA7JDR (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
20190917194217EA7JDR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JDR-DP!3742.08N/-05-17.08rRNG0034 IPSC2-EA4Master MMDVM 438.8000 MHz
20190917195728EA7JDR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JDR-DP!3742.08N/-05-17.08rRNG0034 IPSC2-EA4Master MMDVM 438.8000 MHz
20190917201240EA7JDR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JDR-DP!3742.08N/-05-17.08rRNG0034 IPSC2-EA4Master MMDVM 438.8000 MHz
20190917202755EA7JDR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JDR-DP!3742.08N/-05-17.08rRNG0034 IPSC2-EA4Master MMDVM 438.8000 MHz
20190917204307EA7JDR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JDR-DP!3742.08N/-05-17.08rRNG0034 IPSC2-EA4Master MMDVM 438.8000 MHz
20190917205818EA7JDR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JDR-DP!3742.08N/-05-17.08rRNG0034 IPSC2-EA4Master MMDVM 438.8000 MHz
20190917211330EA7JDR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JDR-DP!3742.08N/-05-17.08rRNG0034 IPSC2-EA4Master MMDVM 438.8000 MHz
20190917212844EA7JDR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JDR-DP!3742.08N/-05-17.08rRNG0034 IPSC2-EA4Master MMDVM 438.8000 MHz
20190917214355EA7JDR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JDR-DP!3742.08N/-05-17.08rRNG0034 IPSC2-EA4Master MMDVM 438.8000 MHz
20190917215912EA7JDR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JDR-DP!3742.08N/-05-17.08rRNG0034 IPSC2-EA4Master MMDVM 438.8000 MHz
20190917221428EA7JDR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JDR-DP!3742.08N/-05-17.08rRNG0034 IPSC2-EA4Master MMDVM 438.8000 MHz
20190917222941EA7JDR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JDR-DP!3742.08N/-05-17.08rRNG0034 IPSC2-EA4Master MMDVM 438.8000 MHz
20190917224450EA7JDR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JDR-DP!3742.08N/-05-17.08rRNG0034 IPSC2-EA4Master MMDVM 438.8000 MHz
20190917230000EA7JDR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JDR-DP!3742.08N/-05-17.08rRNG0034 IPSC2-EA4Master MMDVM 438.8000 MHz
20190917231509EA7JDR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JDR-DP!3742.08N/-05-17.08rRNG0034 IPSC2-EA4Master MMDVM 438.8000 MHz
20190917233022EA7JDR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JDR-DP!3742.08N/-05-17.08rRNG0034 IPSC2-EA4Master MMDVM 438.8000 MHz
20190917234532EA7JDR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JDR-DP!3742.08N/-05-17.08rRNG0034 IPSC2-EA4Master MMDVM 438.8000 MHz
20190918000042EA7JDR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JDR-DP!3742.08N/-05-17.08rRNG0034 IPSC2-EA4Master MMDVM 438.8000 MHz
20190918001552EA7JDR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JDR-DP!3742.08N/-05-17.08rRNG0034 IPSC2-EA4Master MMDVM 438.8000 MHz
20190918003104EA7JDR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JDR-DP!3742.08N/-05-17.08rRNG0034 IPSC2-EA4Master MMDVM 438.8000 MHz
20190918004613EA7JDR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JDR-DP!3742.08N/-05-17.08rRNG0034 IPSC2-EA4Master MMDVM 438.8000 MHz
20190918010122EA7JDR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JDR-DP!3742.08N/-05-17.08rRNG0034 IPSC2-EA4Master MMDVM 438.8000 MHz
20190918011631EA7JDR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JDR-DP!3742.08N/-05-17.08rRNG0034 IPSC2-EA4Master MMDVM 438.8000 MHz
20190918013143EA7JDR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JDR-DP!3742.08N/-05-17.08rRNG0034 IPSC2-EA4Master MMDVM 438.8000 MHz