APRS Packet Errors for GM4UPX-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
20260208162831GM4UPX-10>APLRG1,TCPIP*,qAC,T2CHILE:!L2CZZMhcda GLoRa APRS -Link Testing Batt=4.25V
20260208165831GM4UPX-10>APLRG1,TCPIP*,qAC,T2CHILE:!L2CZZMhcda GLoRa APRS -Link Testing Batt=4.27V
20260208172832GM4UPX-10>APLRG1,TCPIP*,qAC,T2CHILE:!L2CZZMhcda GLoRa APRS -Link Testing Batt=4.25V
20260208175833GM4UPX-10>APLRG1,TCPIP*,qAC,T2CHILE:!L2CZZMhcda GLoRa APRS -Link Testing Batt=4.21V
20260208182834GM4UPX-10>APLRG1,TCPIP*,qAC,T2CHILE:!L2CZZMhcda GLoRa APRS -Link Testing Batt=4.23V
20260208185834GM4UPX-10>APLRG1,TCPIP*,qAC,T2CHILE:!L2CZZMhcda GLoRa APRS -Link Testing Batt=4.25V
20260208192835GM4UPX-10>APLRG1,TCPIP*,qAC,T2CHILE:!L2CZZMhcda GLoRa APRS -Link Testing Batt=4.21V
20260208195836GM4UPX-10>APLRG1,TCPIP*,qAC,T2CHILE:!L2CZZMhcda GLoRa APRS -Link Testing Batt=4.23V
20260208202837GM4UPX-10>APLRG1,TCPIP*,qAC,T2CHILE:!L2CZZMhcda GLoRa APRS -Link Testing Batt=4.21V
20260208205837GM4UPX-10>APLRG1,TCPIP*,qAC,T2CHILE:!L2CZZMhcda GLoRa APRS -Link Testing Batt=4.20V
20260208212838GM4UPX-10>APLRG1,TCPIP*,qAC,T2CHILE:!L2CZZMhcda GLoRa APRS -Link Testing Batt=4.21V
20260208215839GM4UPX-10>APLRG1,TCPIP*,qAC,T2CHILE:!L2CZZMhcda GLoRa APRS -Link Testing Batt=4.23V