APRS Packet Errors for WB4YDL-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
20260208150252	WB4YDL-2>APIN21,TCPIP*,qAC,T2TEXAS:!3627.85N/08911.30W-Reelfoot Lake area Igate and digi
20260208153253	WB4YDL-2>APIN21,TCPIP*,qAC,T2TEXAS:!3627.85N/08911.30W-Reelfoot Lake area Igate and digi
20260208160254	WB4YDL-2>APIN21,TCPIP*,qAC,T2TEXAS:!3627.85N/08911.30W-Reelfoot Lake area Igate and digi
20260208163255	WB4YDL-2>APIN21,TCPIP*,qAC,T2TEXAS:!3627.85N/08911.30W-Reelfoot Lake area Igate and digi
20260208170256	WB4YDL-2>APIN21,TCPIP*,qAC,T2TEXAS:!3627.85N/08911.30W-Reelfoot Lake area Igate and digi
20260208173257	WB4YDL-2>APIN21,TCPIP*,qAC,T2TEXAS:!3627.85N/08911.30W-Reelfoot Lake area Igate and digi
20260208180259	WB4YDL-2>APIN21,TCPIP*,qAC,T2TEXAS:!3627.85N/08911.30W-Reelfoot Lake area Igate and digi
20260208183300	WB4YDL-2>APIN21,TCPIP*,qAC,T2TEXAS:!3627.85N/08911.30W-Reelfoot Lake area Igate and digi
20260208190301	WB4YDL-2>APIN21,TCPIP*,qAC,T2TEXAS:!3627.85N/08911.30W-Reelfoot Lake area Igate and digi
20260208193302	WB4YDL-2>APIN21,TCPIP*,qAC,T2TEXAS:!3627.85N/08911.30W-Reelfoot Lake area Igate and digi
20260208200304	WB4YDL-2>APIN21,TCPIP*,qAC,T2TEXAS:!3627.85N/08911.30W-Reelfoot Lake area Igate and digi
20260208203305	WB4YDL-2>APIN21,TCPIP*,qAC,T2TEXAS:!3627.85N/08911.30W-Reelfoot Lake area Igate and digi