APRS Packet Errors for EA7JV (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
20190221175903EA7JV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JV-DP!3727.77N/-03-28.36rRNG0034 IPSC2-EA-Hotspot MMDVM 439.9125 MHz
20190221181542EA7JV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JV-DP!3727.77N/-03-28.36rRNG0034 IPSC2-EA-Hotspot MMDVM 439.9125 MHz
20190221183222EA7JV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JV-DP!3727.77N/-03-28.36rRNG0034 IPSC2-EA-Hotspot MMDVM 439.9125 MHz
20190221184901EA7JV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JV-DP!3727.77N/-03-28.36rRNG0034 IPSC2-EA-Hotspot MMDVM 439.9125 MHz
20190221190539EA7JV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JV-DP!3727.77N/-03-28.36rRNG0034 IPSC2-EA-Hotspot MMDVM 439.9125 MHz
20190221192214EA7JV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JV-DP!3727.77N/-03-28.36rRNG0034 IPSC2-EA-Hotspot MMDVM 439.9125 MHz
20190221193853EA7JV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JV-DP!3727.77N/-03-28.36rRNG0034 IPSC2-EA-Hotspot MMDVM 439.9125 MHz
20190221195533EA7JV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JV-DP!3727.77N/-03-28.36rRNG0034 IPSC2-EA-Hotspot MMDVM 439.9125 MHz
20190221201214EA7JV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JV-DP!3727.77N/-03-28.36rRNG0034 IPSC2-EA-Hotspot MMDVM 439.9125 MHz
20190221202849EA7JV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JV-DP!3727.77N/-03-28.36rRNG0034 IPSC2-EA-Hotspot MMDVM 439.9125 MHz
20190221204535EA7JV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JV-DP!3727.77N/-03-28.36rRNG0034 IPSC2-EA-Hotspot MMDVM 439.9125 MHz
20190221210215EA7JV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JV-DP!3727.77N/-03-28.36rRNG0034 IPSC2-EA-Hotspot MMDVM 439.9125 MHz
20190221211851EA7JV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JV-DP!3727.77N/-03-28.36rRNG0034 IPSC2-EA-Hotspot MMDVM 439.9125 MHz
20190221213528EA7JV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JV-DP!3727.77N/-03-28.36rRNG0034 IPSC2-EA-Hotspot MMDVM 439.9125 MHz
20190221215210EA7JV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JV-DP!3727.77N/-03-28.36rRNG0034 IPSC2-EA-Hotspot MMDVM 439.9125 MHz
20190221220856EA7JV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JV-DP!3727.77N/-03-28.36rRNG0034 IPSC2-EA-Hotspot MMDVM 439.9125 MHz
20190221222545EA7JV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JV-DP!3727.77N/-03-28.36rRNG0034 IPSC2-EA-Hotspot MMDVM 439.9125 MHz
20190221224234EA7JV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JV-DP!3727.77N/-03-28.36rRNG0034 IPSC2-EA-Hotspot MMDVM 439.9125 MHz
20190221225929EA7JV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JV-DP!3727.77N/-03-28.36rRNG0034 IPSC2-EA-Hotspot MMDVM 439.9125 MHz
20190221231613EA7JV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JV-DP!3727.77N/-03-28.36rRNG0034 IPSC2-EA-Hotspot MMDVM 439.9125 MHz
20190221233255EA7JV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JV-DP!3727.77N/-03-28.36rRNG0034 IPSC2-EA-Hotspot MMDVM 439.9125 MHz