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
20260208133726DO1PIT-99>APRSMC,TCPIP*,qAR,DO1PIT-11:!4808.62N1129.39ESAPRS MeshCom#Pit/B=100/A=001768
20260208140731DO1PIT-99>APRSMC,TCPIP*,qAR,DO1PIT-11:!4808.62N1129.39ESAPRS MeshCom#Pit/B=100/A=001762
20260208143816DO1PIT-99>APRSMC,TCPIP*,qAR,DO1PIT-11:!4808.62N1129.38ESAPRS MeshCom#Pit/B=100/A=001788
20260208150819DO1PIT-99>APRSMC,TCPIP*,qAR,DO1PIT-11:!4808.63N1129.39ESAPRS MeshCom#Pit/B=100/A=001683
20260208153838DO1PIT-99>APRSMC,TCPIP*,qAR,DO1PIT-11:!4808.63N1129.39ESAPRS MeshCom#Pit/B=100/A=001755
20260208160904DO1PIT-99>APRSMC,TCPIP*,qAR,DO1PIT-11:!4808.62N1129.38ESAPRS MeshCom#Pit/B=100/A=001821
20260208170918DO1PIT-99>APRSMC,TCPIP*,qAR,DO1PIT-11:!4808.63N1129.38ESAPRS MeshCom#Pit/B=100/A=001772
20260208174003DO1PIT-99>APRSMC,TCPIP*,qAR,DO1PIT-11:!4808.62N1129.39ESAPRS MeshCom#Pit/B=100/A=001716
20260208174019DO1PIT-99>APLT00-1,WIDE1-1,qAO,DM6CS-10:=6/DKQE9.S P[
20260208174146DO1PIT-99>APLT00-1,WIDE1-1,qAO,DM6CS-10:=6/BiQE9AS P[
20260208174224DO1PIT-99>APLT00-1,WIDE1-1,qAO,DM6CS-10:=6/GEQE:FS P[
20260208174829DO1PIT-99>APLT00-1,WIDE1-1,qAO,DM6CS-10:=6/BCQE9AS P[
20260208184942DO1PIT-99>APRSMC,TCPIP*,qAR,DO1PIT-11:!4808.62N1129.39ESAPRS MeshCom#Pit/B=100/A=001663