APRS Packet Errors for G6LTT-1 (last 24 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
20250508070432G6LTT-1>APLRG1,TCPIP*,qAC,T2CSNGRAD:!Ron now working
20250508080433G6LTT-1>APLRG1,TCPIP*,qAC,T2CSNGRAD:!Ron now working
20250508093437G6LTT-1>APLRG1,TCPIP*,qAC,T2CSNGRAD:!Ron now working
20250508103438G6LTT-1>APLRG1,TCPIP*,qAC,T2CSNGRAD:!Ron now working
20250508123441G6LTT-1>APLRG1,TCPIP*,qAC,T2CSNGRAD:!Ron now working
20250508143444G6LTT-1>APLRG1,TCPIP*,qAC,T2CSNGRAD:!Ron now working
20250508184612G6LTT-1>APLRG1,TCPIP*,qAC,T2CSNGRAD:!Ron now working
20250508190112G6LTT-1>APLRG1,TCPIP*,qAC,T2CSNGRAD:!Ron now working
20250508200113G6LTT-1>APLRG1,TCPIP*,qAC,T2CSNGRAD:!Ron now working
20250508211616G6LTT-1>APLRG1,TCPIP*,qAC,T2CSNGRAD:!Ron now working
20250508220118G6LTT-1>APLRG1,TCPIP*,qAC,T2CSNGRAD:!Ron now working
20250509020124G6LTT-1>APLRG1,TCPIP*,qAC,T2CSNGRAD:!Ron now working
20250509030126G6LTT-1>APLRG1,TCPIP*,qAC,T2CSNGRAD:!Ron now working
20250509040127G6LTT-1>APLRG1,TCPIP*,qAC,T2CSNGRAD:!Ron now working
20250509051629G6LTT-1>APLRG1,TCPIP*,qAC,T2CSNGRAD:!Ron now working
20250509061630G6LTT-1>APLRG1,TCPIP*,qAC,T2CSNGRAD:!Ron now working