APRS Packet Errors for OK2MNL-19 (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
20260129103124OK2MNL-19>APLRG1,TCPIP*,qAC,T2PERTH:!LoRa APRS Batt=3.88V
20260129110125OK2MNL-19>APLRG1,TCPIP*,qAC,T2PERTH:!LoRa APRS Batt=3.85V
20260129111625OK2MNL-19>APLRG1,TCPIP*,qAC,T2PERTH:!LoRa APRS Batt=3.84V
20260129120126OK2MNL-19>APLRG1,TCPIP*,qAC,T2PERTH:!LoRa APRS Batt=3.82V
20260129121627OK2MNL-19>APLRG1,TCPIP*,qAC,T2PERTH:!LoRa APRS Batt=3.82V
20260129130128OK2MNL-19>APLRG1,TCPIP*,qAC,T2PERTH:!LoRa APRS Batt=3.79V
20260129131628OK2MNL-19>APLRG1,TCPIP*,qAC,T2PERTH:!LoRa APRS Batt=3.78V
20260129140129OK2MNL-19>APLRG1,TCPIP*,qAC,T2PERTH:!LoRa APRS Batt=3.76V
20260129150130OK2MNL-19>APLRG1,TCPIP*,qAC,T2PERTH:!LoRa APRS Batt=3.71V
20260129151630OK2MNL-19>APLRG1,TCPIP*,qAC,T2PERTH:!LoRa APRS Batt=3.70V
20260129153131OK2MNL-19>APLRG1,TCPIP*,qAC,T2PERTH:!LoRa APRS Batt=3.70V
20260129154631OK2MNL-19>APLRG1,TCPIP*,qAC,T2PERTH:!LoRa APRS Batt=3.69V
20260129160131OK2MNL-19>APLRG1,TCPIP*,qAC,T2PERTH:!LoRa APRS Batt=3.68V
20260129161632OK2MNL-19>APLRG1,TCPIP*,qAC,T2PERTH:!LoRa APRS Batt=3.67V