APRS Packet Errors for IK2MLR-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
20260208164519	IK2MLR-10>APLRG1,TCPIP*,qAC,T2PANAMA:!L8)\_P[13a GLoRa APRS Igate IK2MLR/1 Batt=4.36V
20260208171519	IK2MLR-10>APLRG1,TCPIP*,qAC,T2PANAMA:!L8)\_P[13a GLoRa APRS Igate IK2MLR/1 Batt=4.31V
20260208174520	IK2MLR-10>APLRG1,TCPIP*,qAC,T2PANAMA:!L8)\_P[13a GLoRa APRS Igate IK2MLR/1 Batt=4.25V
20260208181519	IK2MLR-10>APLRG1,TCPIP*,qAC,T2PANAMA:!L8)\_P[13a GLoRa APRS Igate IK2MLR/1 Batt=4.28V
20260208184519	IK2MLR-10>APLRG1,TCPIP*,qAC,T2PANAMA:!L8)\_P[13a GLoRa APRS Igate IK2MLR/1 Batt=4.31V
20260208191520	IK2MLR-10>APLRG1,TCPIP*,qAC,T2PANAMA:!L8)\_P[13a GLoRa APRS Igate IK2MLR/1 Batt=4.29V
20260208194520	IK2MLR-10>APLRG1,TCPIP*,qAC,T2PANAMA:!L8)\_P[13a GLoRa APRS Igate IK2MLR/1 Batt=4.25V
20260208201520	IK2MLR-10>APLRG1,TCPIP*,qAC,T2PANAMA:!L8)\_P[13a GLoRa APRS Igate IK2MLR/1 Batt=4.34V
20260208204520	IK2MLR-10>APLRG1,TCPIP*,qAC,T2PANAMA:!L8)\_P[13a GLoRa APRS Igate IK2MLR/1 Batt=4.28V
20260208211520	IK2MLR-10>APLRG1,TCPIP*,qAC,T2PANAMA:!L8)\_P[13a GLoRa APRS Igate IK2MLR/1 Batt=4.36V
20260208214520	IK2MLR-10>APLRG1,TCPIP*,qAC,T2PANAMA:!L8)\_P[13a GLoRa APRS Igate IK2MLR/1 Batt=4.24V
20260208221520	IK2MLR-10>APLRG1,TCPIP*,qAC,T2PANAMA:!L8)\_P[13a GLoRa APRS Igate IK2MLR/1 Batt=4.28V