APRS Packet Errors for 9W2VAV (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
202602091309269W2VAV>AESPG4,TCPIP*,qAC,T2CHILE:=0252.43N/10139.21E#VPdigi STM32 V5.6 iGate
202602091339549W2VAV>AESPG4,TCPIP*,qAC,T2CHILE:=0252.43N/10139.21E#VPdigi STM32 V5.6 iGate
202602091410169W2VAV>AESPG4,TCPIP*,qAC,T2CHILE:=0252.43N/10139.21E#VPdigi STM32 V5.6 iGate
202602091440419W2VAV>AESPG4,TCPIP*,qAC,T2CHILE:=0252.43N/10139.21E#VPdigi STM32 V5.6 iGate
202602091511079W2VAV>AESPG4,TCPIP*,qAC,T2CHILE:=0252.43N/10139.21E#VPdigi STM32 V5.6 iGate
202602091541339W2VAV>AESPG4,TCPIP*,qAC,T2CHILE:=0252.43N/10139.21E#VPdigi STM32 V5.6 iGate
202602091611589W2VAV>AESPG4,TCPIP*,qAC,T2CHILE:=0252.43N/10139.21E#VPdigi STM32 V5.6 iGate
202602091642249W2VAV>AESPG4,TCPIP*,qAC,T2CHILE:=0252.43N/10139.21E#VPdigi STM32 V5.6 iGate
202602091712509W2VAV>AESPG4,TCPIP*,qAC,T2CHILE:=0252.43N/10139.21E#VPdigi STM32 V5.6 iGate
202602091743169W2VAV>AESPG4,TCPIP*,qAC,T2CHILE:=0252.43N/10139.21E#VPdigi STM32 V5.6 iGate
202602091813419W2VAV>AESPG4,TCPIP*,qAC,T2CHILE:=0252.43N/10139.21E#VPdigi STM32 V5.6 iGate
202602091844069W2VAV>AESPG4,TCPIP*,qAC,T2CHILE:=0252.43N/10139.21E#VPdigi STM32 V5.6 iGate