APRS Packet Errors for DC2ML-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
20260208145121DC2ML-10>APLRG1,TCPIP*,qAC,T2PERTH:!L4MEOP1T>_ xG.../...g...t055r...p...P...h51b10104LoRa APRS iGATE
20260208154621DC2ML-10>APLRG1,TCPIP*,qAC,T2PERTH:!L4MEOP1T>_ xG.../...g...t055r...p...P...h51b10104LoRa APRS iGATE
20260208164121DC2ML-10>APLRG1,TCPIP*,qAC,T2PERTH:!L4MEOP1T>_ xG.../...g...t055r...p...P...h51b10104LoRa APRS iGATE
20260208173621DC2ML-10>APLRG1,TCPIP*,qAC,T2PERTH:!L4MEOP1T>_ xG.../...g...t055r...p...P...h51b10107LoRa APRS iGATE
20260208183121DC2ML-10>APLRG1,TCPIP*,qAC,T2PERTH:!L4MEOP1T>_ xG.../...g...t055r...p...P...h51b10106LoRa APRS iGATE
20260208192621DC2ML-10>APLRG1,TCPIP*,qAC,T2PERTH:!L4MEOP1T>_ xG.../...g...t055r...p...P...h51b10107LoRa APRS iGATE
20260208202121DC2ML-10>APLRG1,TCPIP*,qAC,T2PERTH:!L4MEOP1T>_ xG.../...g...t055r...p...P...h51b10109LoRa APRS iGATE