APRS Packet Errors for DB0LY-6 (last 24 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
20180818142803DB0LY-6>APRS,TCPIP*,qAC,T2POLNW:!5312.73N/01316.48E_225/g006t080r000p...P000b10092h83Arduino APRS Weather Current: dry
20180818151325DB0LY-6>APRS,TCPIP*,qAC,T2POLNW:!5312.73N/01316.48E_225/g006t081r000p...P000b10090h83Arduino APRS Weather Current: dry
20180818160851DB0LY-6>APRS,TCPIP*,qAC,T2POLNW:!5312.73N/01316.48E_225/g006t080r000p...P000b10087h88Arduino APRS Weather Current: dry
20180819094548DB0LY-6>APRS,TCPIP*,qAC,T2GYOR:!5312.73N/01316.48E_225/g006t078r000p...P000b10099h100Arduino APRS Weather Current: dry
20180819103111DB0LY-6>APRS,TCPIP*,qAC,T2GYOR:!5312.73N/01316.48E_225/g006t080r000p...P000b10095h100Arduino APRS Weather Current: dry
20180819104619DB0LY-6>APRS,TCPIP*,qAC,T2GYOR:!5312.73N/01316.48E_225/g006t081r000p...P000b10093h100Arduino APRS Weather Current: dry
20180819120156DB0LY-6>APRS,TCPIP*,qAC,T2GYOR:!5312.73N/01316.48E_225/g006t083r000p...P000b10087h100Arduino APRS Weather Current: dry
20180819131232DB0LY-6>APRS,TCPIP*,qAC,T2GYOR:!5312.73N/01316.48E_225/g006t084r000p...P000b10080h100Arduino APRS Weather Current: dry