APRS Packet Errors for WA5WRL-10 (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
20260209120238WA5WRL-10>BEACON,TCPIP*,qAC,FIRST:!3250.31N/09642.79WnIGATE - White Rock Lake
20260209123239WA5WRL-10>BEACON,TCPIP*,qAC,FIRST:!3250.31N/09642.79WnIGATE - White Rock Lake
20260209130237WA5WRL-10>BEACON,TCPIP*,qAC,FIRST:!3250.31N/09642.79WnIGATE - White Rock Lake
20260209133238WA5WRL-10>BEACON,TCPIP*,qAC,FIRST:!3250.31N/09642.79WnIGATE - White Rock Lake
20260209140239WA5WRL-10>BEACON,TCPIP*,qAC,FIRST:!3250.31N/09642.79WnIGATE - White Rock Lake
20260209143240WA5WRL-10>BEACON,TCPIP*,qAC,FIRST:!3250.31N/09642.79WnIGATE - White Rock Lake
20260209150241WA5WRL-10>BEACON,TCPIP*,qAC,FIRST:!3250.31N/09642.79WnIGATE - White Rock Lake
20260209153242WA5WRL-10>BEACON,TCPIP*,qAC,FIRST:!3250.31N/09642.79WnIGATE - White Rock Lake
20260209160243WA5WRL-10>BEACON,TCPIP*,qAC,FIRST:!3250.31N/09642.79WnIGATE - White Rock Lake
20260209163244WA5WRL-10>BEACON,TCPIP*,qAC,FIRST:!3250.31N/09642.79WnIGATE - White Rock Lake
20260209170244WA5WRL-10>BEACON,TCPIP*,qAC,FIRST:!3250.31N/09642.79WnIGATE - White Rock Lake
20260209173245WA5WRL-10>BEACON,TCPIP*,qAC,FIRST:!3250.31N/09642.79WnIGATE - White Rock Lake