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
20260209091505DL6PI-10>APRSGW,TCPIP*,qAR,DL6PI-10:!5125.04N/00720.05E##Meshcom Gateway/B=100/A=000614
20260209094520DL6PI-10>APRSGW,TCPIP*,qAR,DL6PI-10:!5125.04N/00720.05E##Meshcom Gateway/B=100/A=000614
20260209101533DL6PI-10>APRSGW,TCPIP*,qAR,DL6PI-10:!5125.04N/00720.05E##Meshcom Gateway/B=100/A=000614
20260209104548DL6PI-10>APRSGW,TCPIP*,qAR,DL6PI-10:!5125.04N/00720.05E##Meshcom Gateway/B=100/A=000614
20260209111603DL6PI-10>APRSGW,TCPIP*,qAR,DL6PI-10:!5125.04N/00720.05E##Meshcom Gateway/B=100/A=000614
20260209114618DL6PI-10>APRSGW,TCPIP*,qAR,DL6PI-10:!5125.04N/00720.05E##Meshcom Gateway/B=100/A=000614
20260209121633DL6PI-10>APRSGW,TCPIP*,qAR,DL6PI-10:!5125.04N/00720.05E##Meshcom Gateway/B=100/A=000614
20260209124648DL6PI-10>APRSGW,TCPIP*,qAR,DL6PI-10:!5125.04N/00720.05E##Meshcom Gateway/B=100/A=000614
20260209131703DL6PI-10>APRSGW,TCPIP*,qAR,DL6PI-10:!5125.04N/00720.05E##Meshcom Gateway/B=100/A=000614
20260209134718DL6PI-10>APRSGW,TCPIP*,qAR,DL6PI-10:!5125.04N/00720.05E##Meshcom Gateway/B=100/A=000614
20260209141733DL6PI-10>APRSGW,TCPIP*,qAR,DL6PI-10:!5125.04N/00720.05E##Meshcom Gateway/B=100/A=000614
20260209144748DL6PI-10>APRSGW,TCPIP*,qAR,DL6PI-10:!5125.04N/00720.05E##Meshcom Gateway/B=100/A=000614