APRS Packet Errors for KM4DC-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
20260208145424KM4DC-2>APIN21,TCPIP*,qAC,T2BC:!3851.76N/07706.87W-/A=000267PinPoint v2.1
20260208150424KM4DC-2>APIN21,TCPIP*,qAC,T2BC:!3851.76N/07706.86W-/A=000248PinPoint v2.1
20260208151424KM4DC-2>APIN21,TCPIP*,qAC,T2BC:!3851.77N/07706.87W-/A=000263PinPoint v2.1
20260208152424KM4DC-2>APIN21,TCPIP*,qAC,T2BC:!3851.75N/07706.86W-/A=000307PinPoint v2.1
20260208153424KM4DC-2>APIN21,TCPIP*,qAC,T2BC:!3851.76N/07706.86W-/A=000271PinPoint v2.1
20260208154424KM4DC-2>APIN21,TCPIP*,qAC,T2BC:!3851.75N/07706.87W-/A=000351PinPoint v2.1
20260208155424KM4DC-2>APIN21,TCPIP*,qAC,T2BC:!3851.74N/07706.85W-/A=000532PinPoint v2.1
20260208160424KM4DC-2>APIN21,TCPIP*,qAC,T2BC:!3851.74N/07706.88W-/A=000515PinPoint v2.1
20260208161424KM4DC-2>APIN21,TCPIP*,qAC,T2BC:!3851.76N/07706.85W-/A=000385PinPoint v2.1