APRS Packet Errors for PY1JHG (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
20190222005624PY1JHG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1JHG-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 439.5500@-5.0 MHz
20190222011259PY1JHG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1JHG-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 439.5500@-5.0 MHz
20190222012934PY1JHG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1JHG-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 439.5500@-5.0 MHz
20190222014609PY1JHG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1JHG-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 439.5500@-5.0 MHz
20190222020254PY1JHG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1JHG-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 439.5500@-5.0 MHz
20190222021936PY1JHG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1JHG-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 439.5500@-5.0 MHz
20190222023618PY1JHG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1JHG-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 439.5500@-5.0 MHz
20190222025253PY1JHG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1JHG-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 439.5500@-5.0 MHz
20190222030935PY1JHG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1JHG-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 439.5500@-5.0 MHz
20190222032612PY1JHG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1JHG-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 439.5500@-5.0 MHz
20190222034413PY1JHG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1JHG-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 439.5500@-5.0 MHz
20190222040047PY1JHG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1JHG-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 439.5500@-5.0 MHz
20190222041737PY1JHG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1JHG-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 439.5500@-5.0 MHz
20190222043416PY1JHG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1JHG-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 439.5500@-5.0 MHz
20190222045052PY1JHG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1JHG-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 439.5500@-5.0 MHz
20190222050727PY1JHG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1JHG-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 439.5500@-5.0 MHz
20190222052412PY1JHG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1JHG-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 439.5500@-5.0 MHz
20190222054046PY1JHG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1JHG-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 439.5500@-5.0 MHz
20190222055720PY1JHG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1JHG-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 439.5500@-5.0 MHz
20190222061355PY1JHG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1JHG-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 439.5500@-5.0 MHz
20190222063043PY1JHG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1JHG-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 439.5500@-5.0 MHz
20190222064718PY1JHG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1JHG-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 439.5500@-5.0 MHz