APRS Packet Errors for R2AJV-4 (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
20260209092840R2AJV-3>APDW18,TCPIP*,qAC,R2AJV-2:;R2AJV-4 *010000z5705.33N/03755.40ErFM-DMR-DSTAR NODE
20260209095840R2AJV-3>APDW18,TCPIP*,qAC,R2AJV-2:;R2AJV-4 *010000z5705.33N/03755.40ErFM-DMR-DSTAR NODE
20260209102840R2AJV-3>APDW18,TCPIP*,qAC,R2AJV-2:;R2AJV-4 *010000z5705.33N/03755.40ErFM-DMR-DSTAR NODE
20260209105840R2AJV-3>APDW18,TCPIP*,qAC,R2AJV-2:;R2AJV-4 *010000z5705.33N/03755.40ErFM-DMR-DSTAR NODE
20260209112840R2AJV-3>APDW18,TCPIP*,qAC,R2AJV-2:;R2AJV-4 *010000z5705.33N/03755.40ErFM-DMR-DSTAR NODE
20260209115840R2AJV-3>APDW18,TCPIP*,qAC,R2AJV-2:;R2AJV-4 *010000z5705.33N/03755.40ErFM-DMR-DSTAR NODE
20260209122840R2AJV-3>APDW18,TCPIP*,qAC,R2AJV-2:;R2AJV-4 *010000z5705.33N/03755.40ErFM-DMR-DSTAR NODE
20260209125840R2AJV-3>APDW18,TCPIP*,qAC,R2AJV-2:;R2AJV-4 *010000z5705.33N/03755.40ErFM-DMR-DSTAR NODE
20260209132840R2AJV-3>APDW18,TCPIP*,qAC,R2AJV-2:;R2AJV-4 *010000z5705.33N/03755.40ErFM-DMR-DSTAR NODE
20260209135840R2AJV-3>APDW18,TCPIP*,qAC,R2AJV-2:;R2AJV-4 *010000z5705.33N/03755.40ErFM-DMR-DSTAR NODE
20260209142840R2AJV-3>APDW18,TCPIP*,qAC,R2AJV-2:;R2AJV-4 *010000z5705.33N/03755.40ErFM-DMR-DSTAR NODE
20260209145840R2AJV-3>APDW18,TCPIP*,qAC,R2AJV-2:;R2AJV-4 *010000z5705.33N/03755.40ErFM-DMR-DSTAR NODE