APRS Packet Errors for EA1RCG-14 (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
20260209163413EA1RCG-14>APLRG1,WIDE1-1,qAR,EA1L-10:=L8Y=(L{n%# !GGRG LoRa APRS Batt=4.16V
20260209170413EA1RCG-14>APLRG1,WIDE1-1,qAR,EA1L-10:=L8Y=(L{n%# !GGRG LoRa APRS Batt=4.11V
20260209173413EA1RCG-14>APLRG1,WIDE1-1,qAR,EA1L-10:=L8Y=(L{n%# !GGRG LoRa APRS Batt=4.15V
20260209180413EA1RCG-14>APLRG1,WIDE1-1,qAR,EA1L-10:=L8Y=(L{n%# !GGRG LoRa APRS Batt=4.10V
20260209183414EA1RCG-14>APLRG1,WIDE1-1,qAR,EA1L-10:=L8Y=(L{n%# !GGRG LoRa APRS Batt=4.17V
20260209190412EA1RCG-14>APLRG1,WIDE1-1,QA4M6,qAR,EA1HI-10:=L8Y=(L{n%# !GGRG LoRa APRS Batt=4.14V
20260209193412EA1RCG-14>APLRG1,WIDE1-1,qAR,EA1L-10:=L8Y=(L{n%# !GGRG LoRa APRS Batt=4.12V
20260209200413EA1RCG-14>APLRG1,WIDE1-1,qAR,EA1L-10:=L8Y=(L{n%# !GGRG LoRa APRS Batt=4.15V
20260209210413EA1RCG-14>APLRG1,WIDE1-1,qAR,EA1L-10:=L8Y=(L{n%# !GGRG LoRa APRS Batt=4.15V
20260209213413EA1RCG-14>APLRG1,WIDE1-1,qAR,EA1L-10:=L8Y=(L{n%# !GGRG LoRa APRS Batt=4.13V
20260209220413EA1RCG-14>APLRG1,WIDE1-1,qAR,EA1RCG-10:=L8Y=(L{n%# !GGRG LoRa APRS Batt=4.12V