APRS Packet Errors for XE2NCH-4 (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
20260208134027	XE2NCH-4>APLRG1,TCPIP,qAC,T2CHILE:!LALwG5."a xGLoRa APRS iGATE NaCHo Batt=4.20V
20260208141027	XE2NCH-4>APLRG1,TCPIP,qAC,T2CHILE:!LALwG5."a xGLoRa APRS iGATE NaCHo Batt=4.20V
20260208144027	XE2NCH-4>APLRG1,TCPIP,qAC,T2CHILE:!LALwG5."a xGLoRa APRS iGATE NaCHo Batt=4.21V
20260208151027	XE2NCH-4>APLRG1,TCPIP,qAC,T2CHILE:!LALwG5."a xGLoRa APRS iGATE NaCHo Batt=4.21V
20260208154027	XE2NCH-4>APLRG1,TCPIP,qAC,T2CHILE:!LALwG5."a xGLoRa APRS iGATE NaCHo Batt=4.26V
20260208161027	XE2NCH-4>APLRG1,TCPIP,qAC,T2CHILE:!LALwG5."a xGLoRa APRS iGATE NaCHo Batt=4.26V
20260208164027	XE2NCH-4>APLRG1,TCPIP,qAC,T2CHILE:!LALwG5."a xGLoRa APRS iGATE NaCHo Batt=4.21V
20260208171027	XE2NCH-4>APLRG1,TCPIP,qAC,T2CHILE:!LALwG5."a xGLoRa APRS iGATE NaCHo Batt=4.20V
20260208174027	XE2NCH-4>APLRG1,TCPIP,qAC,T2CHILE:!LALwG5."a xGLoRa APRS iGATE NaCHo Batt=4.32V
20260208181027	XE2NCH-4>APLRG1,TCPIP,qAC,T2CHILE:!LALwG5."a xGLoRa APRS iGATE NaCHo Batt=4.20V
20260208184028	XE2NCH-4>APLRG1,TCPIP,qAC,T2CHILE:!LALwG5."a xGLoRa APRS iGATE NaCHo Batt=4.22V
20260208191028	XE2NCH-4>APLRG1,TCPIP,qAC,T2CHILE:!LALwG5."a xGLoRa APRS iGATE NaCHo Batt=4.24V