APRS Packet Errors for CE3TMM-1 (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
20260208125817	CE3TMM-1>APLRG1,TCPIP*,qAC,T2ROMANIA:!L_B/-<[02a Gff46qp Huechuraba Santiago Batt=4.34V
20260208135817	CE3TMM-1>APLRG1,TCPIP*,qAC,T2ROMANIA:!L_B/-<[02a Gff46qp Huechuraba Santiago Batt=4.29V
20260208145817	CE3TMM-1>APLRG1,TCPIP*,qAC,T2ROMANIA:!L_B/-<[02a Gff46qp Huechuraba Santiago Batt=4.36V
20260208155818	CE3TMM-1>APLRG1,TCPIP*,qAC,T2ROMANIA:!L_B/-<[02a Gff46qp Huechuraba Santiago Batt=4.35V
20260208165817	CE3TMM-1>APLRG1,TCPIP*,qAC,T2PERTH:!L_B/-<[02a Gff46qp Huechuraba Santiago Batt=4.30V
20260208175817	CE3TMM-1>APLRG1,TCPIP*,qAC,T2PERTH:!L_B/-<[02a Gff46qp Huechuraba Santiago Batt=4.37V