APRS Packet Errors for DK3ACH-12 (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
20260208132934DK3ACH-12>APRSMC,TCPIP*,qAR,DK3ACH-11:!5026.18N/00810.30E##DK3ACH-8/B=070/A=000512
20260208135959DK3ACH-12>APRSMC,TCPIP*,qAR,DK3ACH-11:!5026.18N/00810.30E##DK3ACH-8/B=075/A=000512
20260208150020DK3ACH-12>APRSMC,TCPIP*,qAR,DK3ACH-11:!5026.18N/00810.30E##DK3ACH-8/B=082/A=000512
20260208153035DK3ACH-12>APRSMC,TCPIP*,qAR,DK3ACH-11:!5026.18N/00810.30E##DK3ACH-8/B=070/A=000512
20260208160053DK3ACH-12>APRSMC,TCPIP*,qAR,DK3ACH-11:!5026.18N/00810.30E##DK3ACH-8/B=089/A=000512
20260208163109DK3ACH-12>APRSMC,TCPIP*,qAR,DK3ACH-11:!5026.18N/00810.30E##DK3ACH-8/B=090/A=000512
20260208170122DK3ACH-12>APRSMC,TCPIP*,qAR,DK3ACH-11:!5026.18N/00810.30E##DK3ACH-8/B=078/A=000512
20260208173135DK3ACH-12>APRSMC,TCPIP*,qAR,DK3ACH-11:!5026.18N/00810.30E##DK3ACH-8/B=074/A=000512
20260208180151DK3ACH-12>APRSMC,TCPIP*,qAR,DK3ACH-11:!5026.18N/00810.30E##DK3ACH-8/B=076/A=000512
20260208183208DK3ACH-12>APRSMC,TCPIP*,qAR,DK3ACH-11:!5026.18N/00810.30E##DK3ACH-8/B=079/A=000512
20260208190223DK3ACH-12>APRSMC,TCPIP*,qAR,DK3ACH-11:!5026.18N/00810.30E##DK3ACH-8/B=090/A=000512