APRS Packet Errors for OE3LDV-2 (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
20260208144919	OE3LDV-2>APRSMC,TCPIP*,qAR,OE3LDV-1:!4839.54N/01631.10E-#TLORA2/B=100/A=000840
20260208151934	OE3LDV-2>APRSMC,TCPIP*,qAR,OE3LDV-1:!4839.54N/01631.10E-#TLORA2/B=100/A=000840
20260208154949	OE3LDV-2>APRSMC,TCPIP*,qAR,OE3LDV-1:!4839.54N/01631.10E-#TLORA2/B=100/A=000840
20260208162004	OE3LDV-2>APRSMC,TCPIP*,qAR,OE3LDV-1:!4839.54N/01631.10E-#TLORA2/B=100/A=000840
20260208165023	OE3LDV-2>APRSMC,TCPIP*,qAR,OE3LDV-1:!4839.54N/01631.10E-#TLORA2/B=100/A=000840
20260208172038	OE3LDV-2>APRSMC,TCPIP*,qAR,OE3LDV-1:!4839.54N/01631.10E-#TLORA2/B=100/A=000840
20260208175052	OE3LDV-2>APRSMC,TCPIP*,qAR,OE3LDV-1:!4839.54N/01631.10E-#TLORA2/B=100/A=000840
20260208182103	OE3LDV-2>APRSMC,TCPIP*,qAR,OE3LDV-1:!4839.54N/01631.10E-#TLORA2/B=100/A=000840
20260208185116	OE3LDV-2>APRSMC,TCPIP*,qAR,OE3LDV-1:!4839.54N/01631.10E-#TLORA2/B=100/A=000840
20260208192129	OE3LDV-2>APRSMC,TCPIP*,qAR,OE3LDV-1:!4839.54N/01631.10E-#TLORA2/B=100/A=000840
20260208195144	OE3LDV-2>APRSMC,TCPIP*,qAR,OE3LDV-1:!4839.54N/01631.10E-#TLORA2/B=100/A=000840
20260208202159	OE3LDV-2>APRSMC,TCPIP*,qAR,OE3LDV-1:!4839.54N/01631.10E-#TLORA2/B=100/A=000840