APRS Packet Errors for DL6PI-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
20260208131934DL6PI-10>APRSGW,TCPIP*,qAR,DL6PI-10:!5125.04N/00720.05E##Meshcom Gateway/B=100/A=000614
20260208134949DL6PI-10>APRSGW,TCPIP*,qAR,DL6PI-10:!5125.04N/00720.05E##Meshcom Gateway/B=100/A=000614
20260208142004DL6PI-10>APRSGW,TCPIP*,qAR,DL6PI-10:!5125.04N/00720.05E##Meshcom Gateway/B=100/A=000614
20260208145019DL6PI-10>APRSGW,TCPIP*,qAR,DL6PI-10:!5125.04N/00720.05E##Meshcom Gateway/B=100/A=000614
20260208152031DL6PI-10>APRSGW,TCPIP*,qAR,DL6PI-10:!5125.04N/00720.05E##Meshcom Gateway/B=100/A=000614
20260208155046DL6PI-10>APRSGW,TCPIP*,qAR,DL6PI-10:!5125.04N/00720.05E##Meshcom Gateway/B=100/A=000614
20260208162101DL6PI-10>APRSGW,TCPIP*,qAR,DL6PI-10:!5125.04N/00720.05E##Meshcom Gateway/B=100/A=000614
20260208165116DL6PI-10>APRSGW,TCPIP*,qAR,DL6PI-10:!5125.04N/00720.05E##Meshcom Gateway/B=100/A=000614
20260208172131DL6PI-10>APRSGW,TCPIP*,qAR,DL6PI-10:!5125.04N/00720.05E##Meshcom Gateway/B=100/A=000614
20260208175146DL6PI-10>APRSGW,TCPIP*,qAR,DL6PI-10:!5125.04N/00720.05E##Meshcom Gateway/B=100/A=000614
20260208182201DL6PI-10>APRSGW,TCPIP*,qAR,DL6PI-10:!5125.04N/00720.05E##Meshcom Gateway/B=100/A=000614
20260208185219DL6PI-10>APRSGW,TCPIP*,qAR,DL6PI-10:!5125.04N/00720.05E##Meshcom Gateway/B=100/A=000614