APRS Packet Errors for DO1PIT-99 (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
20260209092817DO1PIT-99>APRSMC,TCPIP*,qAR,DO1PIT-11:!4808.62N1129.38ESAPRS MeshCom#Pit/B=100/A=001713
20260209095901DO1PIT-99>APRSMC,TCPIP*,qAR,DO1PIT-11:!4808.62N1129.38ESAPRS MeshCom#Pit/B=100/A=001762
20260209102907DO1PIT-99>APRSMC,TCPIP*,qAR,DO1PIT-11:!4808.62N1129.39ESAPRS MeshCom#Pit/B=100/A=001785
20260209105912DO1PIT-99>APRSMC,TCPIP*,qAR,DO1PIT-11:!4808.62N1129.39ESAPRS MeshCom#Pit/B=100/A=001755
20260209112956DO1PIT-99>APRSMC,TCPIP*,qAR,DO1PIT-11:!4808.62N1129.38ESAPRS MeshCom#Pit/B=100/A=001759
20260209120002DO1PIT-99>APRSMC,TCPIP*,qAR,DO1PIT-11:!4808.62N1129.38ESAPRS MeshCom#Pit/B=100/A=001781
20260209123007DO1PIT-99>APRSMC,TCPIP*,qAR,DO1PIT-11:!4808.62N1129.38ESAPRS MeshCom#Pit/B=100/A=001677
20260209130051DO1PIT-99>APRSMC,TCPIP*,qAR,DO1PIT-11:!4808.62N1129.38ESAPRS MeshCom#Pit/B=100/A=001732
20260209133036DO1PIT-99>APLT00-1,WIDE1-1,qAO,DM6CS-10:=6/DrQE9.S P[
20260209133137DO1PIT-99>APRSMC,TCPIP*,qAR,DO1PIT-11:!4808.62N1129.39ESAPRS MeshCom#Pit/B=100/A=001788