APRS Packet Errors for XE2RCS-31 (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
20260208200709	XE2RCS-31>APLRG1,WIDE1-1,qAR,XE2RCS-21:!LA_%=4{I`# xGLoRa APRS PENITENTE Batt=5.05V
20260208203709	XE2RCS-31>APLRG1,WIDE1-1,qAR,XE2RCS-21:!LA_%=4{I`# xGLoRa APRS PENITENTE Batt=5.05V
20260208210709	XE2RCS-31>APLRG1,WIDE1-1,qAR,XE2RCS-21:!LA_%=4{I`# xGLoRa APRS PENITENTE Batt=5.05V
20260208213709	XE2RCS-31>APLRG1,WIDE1-1,qAR,XE2RCS-21:!LA_%=4{I`# xGLoRa APRS PENITENTE Batt=5.05V
20260208220709	XE2RCS-31>APLRG1,WIDE1-1,qAR,XE2RCS-21:!LA_%=4{I`# xGLoRa APRS PENITENTE Batt=5.05V
20260208223709	XE2RCS-31>APLRG1,WIDE1-1,qAR,XE2RCS-21:!LA_%=4{I`# xGLoRa APRS PENITENTE Batt=5.05V
20260208230709	XE2RCS-31>APLRG1,WIDE1-1,qAR,XE2RCS-21:!LA_%=4{I`# xGLoRa APRS PENITENTE Batt=5.07V
20260208233710	XE2RCS-31>APLRG1,WIDE1-1,qAR,XE2RCS-21:!LA_%=4{I`# xGLoRa APRS PENITENTE Batt=5.04V
20260209000709	XE2RCS-31>APLRG1,WIDE1-1,qAR,XE2RCS-21:!LA_%=4{I`# xGLoRa APRS PENITENTE Batt=5.06V
20260209003707	XE2RCS-31>APLRG1,WIDE1-1,qAR,XE2RCS-21:!LA_%=4{I`# xGLoRa APRS PENITENTE Batt=5.03V
20260209010707	XE2RCS-31>APLRG1,WIDE1-1,qAR,XE2RCS-21:!LA_%=4{I`# xGLoRa APRS PENITENTE Batt=5.04V
20260209013707	XE2RCS-31>APLRG1,WIDE1-1,qAR,XE2RCS-21:!LA_%=4{I`# xGLoRa APRS PENITENTE Batt=5.04V