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
20260209134027	XE2NCH-4>APLRG1,TCPIP,qAC,T2PERTH:!LALwG5."a xGLoRa APRS iGATE NaCHo Batt=4.27V
20260209141027	XE2NCH-4>APLRG1,TCPIP,qAC,T2PERTH:!LALwG5."a xGLoRa APRS iGATE NaCHo Batt=4.26V
20260209144027	XE2NCH-4>APLRG1,TCPIP,qAC,T2PERTH:!LALwG5."a xGLoRa APRS iGATE NaCHo Batt=4.27V
20260209151027	XE2NCH-4>APLRG1,TCPIP,qAC,T2PERTH:!LALwG5."a xGLoRa APRS iGATE NaCHo Batt=4.27V
20260209154027	XE2NCH-4>APLRG1,TCPIP,qAC,T2PERTH:!LALwG5."a xGLoRa APRS iGATE NaCHo Batt=4.24V
20260209161027	XE2NCH-4>APLRG1,TCPIP,qAC,T2PERTH:!LALwG5."a xGLoRa APRS iGATE NaCHo Batt=4.31V
20260209164027	XE2NCH-4>APLRG1,TCPIP,qAC,T2PERTH:!LALwG5."a xGLoRa APRS iGATE NaCHo Batt=4.29V
20260209171027	XE2NCH-4>APLRG1,TCPIP,qAC,T2PERTH:!LALwG5."a xGLoRa APRS iGATE NaCHo Batt=4.24V
20260209174028	XE2NCH-4>APLRG1,TCPIP,qAC,T2PERTH:!LALwG5."a xGLoRa APRS iGATE NaCHo Batt=4.19V
20260209181028	XE2NCH-4>APLRG1,TCPIP,qAC,T2PERTH:!LALwG5."a xGLoRa APRS iGATE NaCHo Batt=4.30V
20260209184028	XE2NCH-4>APLRG1,TCPIP,qAC,T2PERTH:!LALwG5."a xGLoRa APRS iGATE NaCHo Batt=4.20V
20260209191028	XE2NCH-4>APLRG1,TCPIP,qAC,T2PERTH:!LALwG5."a xGLoRa APRS iGATE NaCHo Batt=4.25V