APRS Packet Errors for 9W4GAW-3 (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
20260209132327	9W4GAW-3>APLRG1,WIDE1-1,qAR,9M2OCX-M:!LM!j?h2N`# GLoRa APRS (Digipeater) Batt=3.91V
20260209135327	9W4GAW-3>APLRG1,WIDE1-1,qAO,9W4GAW-2:!LM!j?h2N`# GLoRa APRS (Digipeater) Batt=3.88V
20260209142328	9W4GAW-3>APLRG1,WIDE1-1,qAR,9M2OCX-M:!LM!j?h2N`# GLoRa APRS (Digipeater) Batt=3.90V
20260209145328	9W4GAW-3>APLRG1,WIDE1-1,qAR,9M2OCX-M:!LM!j?h2N`# GLoRa APRS (Digipeater) Batt=3.89V
20260209152328	9W4GAW-3>APLRG1,WIDE1-1,qAO,9W4GAW-2:!LM!j?h2N`# GLoRa APRS (Digipeater) Batt=3.88V
20260209155328	9W4GAW-3>APLRG1,WIDE1-1,qAR,9M2OCX-M:!LM!j?h2N`# GLoRa APRS (Digipeater) Batt=3.87V
20260209162328	9W4GAW-3>APLRG1,WIDE1-1,qAR,9M2OCX-M:!LM!j?h2N`# GLoRa APRS (Digipeater) Batt=3.87V
20260209165328	9W4GAW-3>APLRG1,WIDE1-1,qAR,9W2DYA-L:!LM!j?h2N`# GLoRa APRS (Digipeater) Batt=3.87V
20260209172327	9W4GAW-3>APLRG1,WIDE1-1,qAR,9W2DYA-L:!LM!j?h2N`# GLoRa APRS (Digipeater) Batt=3.87V
20260209175327	9W4GAW-3>APLRG1,WIDE1-1,qAR,9M2OCX-M:!LM!j?h2N`# GLoRa APRS (Digipeater) Batt=3.85V
20260209182327	9W4GAW-3>APLRG1,WIDE1-1,qAR,9W2DYA-L:!LM!j?h2N`# GLoRa APRS (Digipeater) Batt=3.85V
20260209185327	9W4GAW-3>APLRG1,WIDE1-1,qAR,9W2DYA-L:!LM!j?h2N`# GLoRa APRS (Digipeater) Batt=3.85V