APRS Packet Errors for DL1HCI-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
20260208181723DL1HCI-99>APRSMC,TCPIP*,qAR,DL1HCI-12:!5326.96NM01004.08E#MeshComNode/B=100/A=000026
20260208184743DL1HCI-99>APRSMC,TCPIP*,qAR,DL1HCI-12:!5326.96NM01004.08E#MeshComNode/B=100
20260208191806DL1HCI-99>APRSMC,TCPIP*,qAR,DL1HCI-12:!5326.96NM01004.08E#MeshComNode/B=100
20260208194823DL1HCI-99>APRSMC,TCPIP*,qAR,DL1HCI-12:!5326.96NM01004.08E#MeshComNode/B=100
20260208202034DL1HCI-99>APLT00-1,WIDE1-1,qAO,DL1HCI-10:=M3L?Q$TQ# P[
20260208211223DL1HCI-99>APRSMC,TCPIP*,qAR,DL1HCI-12:!5326.98NM01004.09E#MeshComNode/B=100/A=000121
20260208214244DL1HCI-99>APRSMC,TCPIP*,qAR,DL1HCI-12:!5326.96NM01004.08E#MeshComNode/B=100
20260208221303DL1HCI-99>APRSMC,TCPIP*,qAR,DL1HCI-12:!5326.96NM01004.08E#MeshComNode/B=100
20260208222034DL1HCI-99>APLT00-1,WIDE1-1,qAO,DL1HCI-10:=M3LA>Q$TQ# P[
20260208225057DL1HCI-99>APRSMC,TCPIP*,qAR,DL1HCI-12:!5326.96NM01004.08E#MeshComNode/B=100
20260208232117DL1HCI-99>APRSMC,TCPIP*,qAR,DL1HCI-12:!5326.96NM01004.08E#MeshComNode/B=100
20260208235142DL1HCI-99>APRSMC,TCPIP*,qAR,DL1HCI-12:!5326.97NM01004.08E#MeshComNode/B=100/A=000016