APRS Packet Errors for DJ4MC-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
20260209122044DJ4MC-10>APRSMC,TCPIP*,qAR,DG5DBY-1:!5121.90N/00722.20E-HELTEC V3 MeshCom/B=051/A=000807
20260209125103DJ4MC-10>APRSMC,TCPIP*,qAR,DG5DBY-1:!5121.90N/00722.20E-HELTEC V3 MeshCom/B=052/A=000807
20260209132122DJ4MC-10>APRSMC,TCPIP*,qAR,DG5DBY-1:!5121.90N/00722.20E-HELTEC V3 MeshCom/B=045/A=000807
20260209135139DJ4MC-10>APRSMC,TCPIP*,qAR,DG5DBY-1:!5121.90N/00722.20E-HELTEC V3 MeshCom/B=056/A=000807
20260209142147DJ4MC-10>APRSMC,TCPIP*,qAR,DG5DBY-1:!5121.90N/00722.20E-HELTEC V3 MeshCom/B=055/A=000807
20260209145203DJ4MC-10>APRSMC,TCPIP*,qAR,DG5DBY-1:!5121.90N/00722.20E-HELTEC V3 MeshCom/B=059/A=000807
20260209152218DJ4MC-10>APRSMC,TCPIP*,qAR,DG5DBY-1:!5121.90N/00722.20E-HELTEC V3 MeshCom/B=051/A=000807
20260209162244DJ4MC-10>APRSMC,TCPIP*,qAR,DG5DBY-1:!5121.90N/00722.20E-HELTEC V3 MeshCom/B=052/A=000807
20260209165259DJ4MC-10>APRSMC,TCPIP*,qAR,DG5DBY-1:!5121.90N/00722.20E-HELTEC V3 MeshCom/B=047/A=000807
20260209172314DJ4MC-10>APRSMC,TCPIP*,qAR,DG5DBY-1:!5121.90N/00722.20E-HELTEC V3 MeshCom/B=058/A=000807