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
20190418111001PY1JHG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1JHG-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 439.5500@-5.0 MHz
20190418112659PY1JHG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1JHG-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 439.5500@-5.0 MHz
20190418114342PY1JHG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1JHG-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 439.5500@-5.0 MHz
20190418120033PY1JHG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1JHG-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 439.5500@-5.0 MHz
20190418121714PY1JHG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1JHG-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 439.5500@-5.0 MHz
20190418123408PY1JHG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1JHG-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 439.5500@-5.0 MHz
20190418125049PY1JHG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1JHG-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 439.5500@-5.0 MHz
20190418130734PY1JHG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1JHG-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 439.5500@-5.0 MHz
20190418132415PY1JHG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1JHG-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 439.5500@-5.0 MHz
20190418134111PY1JHG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1JHG-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 439.5500@-5.0 MHz
20190418135756PY1JHG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1JHG-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 439.5500@-5.0 MHz
20190418141440PY1JHG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1JHG-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 439.5500@-5.0 MHz
20190418143128PY1JHG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1JHG-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 439.5500@-5.0 MHz
20190418144821PY1JHG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1JHG-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 439.5500@-5.0 MHz
20190418150503PY1JHG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1JHG-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 439.5500@-5.0 MHz
20190418152144PY1JHG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1JHG-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 439.5500@-5.0 MHz
20190418153828PY1JHG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1JHG-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 439.5500@-5.0 MHz
20190418155524PY1JHG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1JHG-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 439.5500@-5.0 MHz
20190418161206PY1JHG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1JHG-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 439.5500@-5.0 MHz
20190418162848PY1JHG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1JHG-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 439.5500@-5.0 MHz
20190418164532PY1JHG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1JHG-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 439.5500@-5.0 MHz
20190418170228PY1JHG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1JHG-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 439.5500@-5.0 MHz