APRS Packet Errors for SP9BOT-10 (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
20260220142001SP9BOT-10>APSVX1,TCPIP*,qAC,T2POLAND:=50.0639/20.0074nHS Sp9bot
20260220142002SP9BOT-10>APSVX1,TCPIP*,qAC,T2POLAND:=50.0639/20.0074nPHG1010
20260220144001SP9BOT-10>APSVX1,TCPIP*,qAC,T2POLAND:=50.0639/20.0074nHS Sp9bot
20260220144002SP9BOT-10>APSVX1,TCPIP*,qAC,T2POLAND:=50.0639/20.0074nPHG1010
20260220150001SP9BOT-10>APSVX1,TCPIP*,qAC,T2POLAND:=50.0639/20.0074nHS Sp9bot
20260220150002SP9BOT-10>APSVX1,TCPIP*,qAC,T2POLAND:=50.0639/20.0074nPHG1010
20260220153002SP9BOT-10>APSVX1,TCPIP*,qAC,T2POLAND:=50.0639/20.0074nHS Sp9bot
20260220153003SP9BOT-10>APSVX1,TCPIP*,qAC,T2POLAND:=50.0639/20.0074nPHG1010
20260220155002SP9BOT-10>APSVX1,TCPIP*,qAC,T2POLAND:=50.0639/20.0074nHS Sp9bot
20260220155003SP9BOT-10>APSVX1,TCPIP*,qAC,T2POLAND:=50.0639/20.0074nPHG1010
20260220161002SP9BOT-10>APSVX1,TCPIP*,qAC,T2POLAND:=50.0639/20.0074nHS Sp9bot
20260220161003SP9BOT-10>APSVX1,TCPIP*,qAC,T2POLAND:=50.0639/20.0074nPHG1010