APRS Packet Errors for DG5YIM-7 (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
20260208182540DG5YIM-7>APRSMC,TCPIP*,qAR,DG5YIM-12:!5330.34N/00829.60E[MeshCom-Tracker#DG5YIM-7/B=100/A=000010
20260208185550DG5YIM-7>APRSMC,TCPIP*,qAR,DG5YIM-12:!5330.34N/00829.60E[MeshCom-Tracker#DG5YIM-7/B=100/A=000010
20260208192538DG5YIM-7>APRSMC,TCPIP*,qAR,DG5YIM-12:!5330.34N/00829.60E[MeshCom-Tracker#DG5YIM-7/B=100/A=000010
20260208195544DG5YIM-7>APRSMC,TCPIP*,qAR,DG5YIM-12:!5330.34N/00829.60E[MeshCom-Tracker#DG5YIM-7/B=100/A=000010
20260208202538DG5YIM-7>APRSMC,TCPIP*,qAR,DG5YIM-12:!5330.34N/00829.60E[MeshCom-Tracker#DG5YIM-7/B=100/A=000010
20260208205538DG5YIM-7>APRSMC,TCPIP*,qAR,DG5YIM-12:!5330.34N/00829.60E[MeshCom-Tracker#DG5YIM-7/B=100/A=000010
20260208215538DG5YIM-7>APRSMC,TCPIP*,qAR,DG5YIM-12:!5330.34N/00829.60E[MeshCom-Tracker#DG5YIM-7/B=100/A=000010
20260208222538DG5YIM-7>APRSMC,TCPIP*,qAR,DG5YIM-12:!5330.34N/00829.60E[MeshCom-Tracker#DG5YIM-7/B=100/A=000010
20260208225538DG5YIM-7>APRSMC,TCPIP*,qAR,DG5YIM-12:!5330.34N/00829.60E[MeshCom-Tracker#DG5YIM-7/B=100/A=000010
20260208232538DG5YIM-7>APRSMC,TCPIP*,qAR,DG5YIM-12:!5330.34N/00829.60E[MeshCom-Tracker#DG5YIM-7/B=100/A=000010
20260208235539DG5YIM-7>APRSMC,TCPIP*,qAR,DG5YIM-12:!5330.34N/00829.60E[MeshCom-Tracker#DG5YIM-7/B=100/A=000010