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
20181022084008DB0LY-6>APRS,TCPIP*,qAC,T2EUSKADI:!5312.73N/01316.48E_180/g006t051r001p...P000b10146h100Arduino APRS Weather Current: dry
20181022120644DB0LY-6>APRS,TCPIP*,qAC,T2EUSKADI:!5312.73N/01316.48E_000/g006t055r000p...P000b10156h100Arduino APRS Weather Current: dry
20181023001107DB0LY-6>APRS,TCPIP*,qAC,T2EUSKADI:!5312.73N/01316.48E_180/g006t045r000p...P000b10127h100Arduino APRS Weather Current: dry
20181023001609DB0LY-6>APRS,TCPIP*,qAC,T2EUSKADI:!5312.73N/01316.48E_180/g006t045r000p...P000b10126h100Arduino APRS Weather Current: dry
20181023014150DB0LY-6>APRS,TCPIP*,qAC,T2EUSKADI:!5312.73N/01316.48E_180/g006t047r000p...P000b10107h100Arduino APRS Weather Current: dry
20181023023717DB0LY-6>APRS,TCPIP*,qAC,T2EUSKADI:!5312.73N/01316.48E_180/g006t045r000p...P000b10095h100Arduino APRS Weather Current: dry
20181023025727DB0LY-6>APRS,TCPIP*,qAC,T2EUSKADI:!5312.73N/01316.48E_180/g006t045r000p...P000b10088h100Arduino APRS Weather Current: dry
20181023030731DB0LY-6>APRS,TCPIP*,qAC,T2EUSKADI:!5312.73N/01316.48E_180/g006t045r000p...P000b10082h100Arduino APRS Weather Current: dry
20181023032741DB0LY-6>APRS,TCPIP*,qAC,T2EUSKADI:!5312.73N/01316.48E_180/g006t044r000p...P000b10075h100Arduino APRS Weather Current: dry