APRS Packet Errors for EA7KRS-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
20260208152534EA7KRS-10>APLRG1,WIDE2-1,qAO,EA7KFV-10:=L;{YrM?k!a !GIgate LoRa APRS Batt=4.17V
20260208155536EA7KRS-10>APLRG1,WIDE2-1,qAO,EA7KFV-10:=L;{YrM?k!a !GIgate LoRa APRS Batt=4.10V
20260208162534EA7KRS-10>APLRG1,WIDE2-1,qAO,EA7KFV-10:=L;{YrM?k!a !GIgate LoRa APRS Batt=4.14V
20260208165535EA7KRS-10>APLRG1,WIDE2-1,qAO,EA7KFV-10:=L;{YrM?k!a !GIgate LoRa APRS Batt=4.17V
20260208172535EA7KRS-10>APLRG1,WIDE2-1,qAO,EA7KFV-10:=L;{YrM?k!a !GIgate LoRa APRS Batt=4.15V
20260208175536EA7KRS-10>APLRG1,WIDE2-1,qAO,EA7KFV-10:=L;{YrM?k!a !GIgate LoRa APRS Batt=4.11V
20260208182535EA7KRS-10>APLRG1,WIDE2-1,qAO,EA7KFV-10:=L;{YrM?k!a !GIgate LoRa APRS Batt=4.13V
20260208185535EA7KRS-10>APLRG1,WIDE2-1,qAO,EA7KFV-10:=L;{YrM?k!a !GIgate LoRa APRS Batt=4.11V
20260208192535EA7KRS-10>APLRG1,WIDE2-1,qAR,EA7KEL-10:=L;{YrM?k!a !GIgate LoRa APRS Batt=4.12V
20260208195535EA7KRS-10>APLRG1,WIDE2-1,qAR,EA7KEL-10:=L;{YrM?k!a !GIgate LoRa APRS Batt=4.10V
20260208202535EA7KRS-10>APLRG1,WIDE2-1,qAR,EA7KEL-10:=L;{YrM?k!a !GIgate LoRa APRS Batt=4.16V
20260208205535EA7KRS-10>APLRG1,WIDE2-1,qAR,EA7KEL-10:=L;{YrM?k!a !GIgate LoRa APRS Batt=4.12V