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
20260209132904GM4UPX-10>APLRG1,TCPIP*,qAC,T2CHILE:!L2CZZMhcda GLoRa APRS -Link Testing Batt=4.25V
20260209135904GM4UPX-10>APLRG1,TCPIP*,qAC,T2CHILE:!L2CZZMhcda GLoRa APRS -Link Testing Batt=4.21V
20260209142905GM4UPX-10>APLRG1,TCPIP*,qAC,T2CHILE:!L2CZZMhcda GLoRa APRS -Link Testing Batt=4.21V
20260209145906GM4UPX-10>APLRG1,TCPIP*,qAC,T2CHILE:!L2CZZMhcda GLoRa APRS -Link Testing Batt=4.21V
20260209152907GM4UPX-10>APLRG1,TCPIP*,qAC,T2CHILE:!L2CZZMhcda GLoRa APRS -Link Testing Batt=4.24V
20260209155907GM4UPX-10>APLRG1,TCPIP*,qAC,T2CHILE:!L2CZZMhcda GLoRa APRS -Link Testing Batt=4.22V
20260209162908GM4UPX-10>APLRG1,TCPIP*,qAC,T2CHILE:!L2CZZMhcda GLoRa APRS -Link Testing Batt=4.23V
20260209165909GM4UPX-10>APLRG1,TCPIP*,qAC,T2CHILE:!L2CZZMhcda GLoRa APRS -Link Testing Batt=4.23V
20260209172910GM4UPX-10>APLRG1,TCPIP*,qAC,T2CHILE:!L2CZZMhcda GLoRa APRS -Link Testing Batt=4.25V
20260209175911GM4UPX-10>APLRG1,TCPIP*,qAC,T2CHILE:!L2CZZMhcda GLoRa APRS -Link Testing Batt=4.23V
20260209182912GM4UPX-10>APLRG1,TCPIP*,qAC,T2CHILE:!L2CZZMhcda GLoRa APRS -Link Testing Batt=4.22V
20260209185913GM4UPX-10>APLRG1,TCPIP*,qAC,T2CHILE:!L2CZZMhcda GLoRa APRS -Link Testing Batt=4.24V