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
20260208145326	9W4GAW-3>APLRG1,WIDE1-1,qAR,9W2DYA-L:!LM!j?h2N`# GLoRa APRS (Digipeater) Batt=3.85V
20260208152326	9W4GAW-3>APLRG1,WIDE1-1,qAO,9W4GAW-2:!LM!j?h2N`# GLoRa APRS (Digipeater) Batt=3.85V
20260208155327	9W4GAW-3>APLRG1,WIDE1-1,qAO,9W4GAW-2:!LM!j?h2N`# GLoRa APRS (Digipeater) Batt=3.76V
20260208162327	9W4GAW-3>APLRG1,WIDE1-1,qAO,9W4GAW-2:!LM!j?h2N`# GLoRa APRS (Digipeater) Batt=3.84V
20260208165326	9W4GAW-3>APLRG1,WIDE1-1,qAO,9W4GAW-2:!LM!j?h2N`# GLoRa APRS (Digipeater) Batt=3.83V
20260208172325	9W4GAW-3>APLRG1,WIDE1-1,qAR,9W2DYA-L:!LM!j?h2N`# GLoRa APRS (Digipeater) Batt=3.82V
20260208175325	9W4GAW-3>APLRG1,WIDE1-1,qAO,9W4GAW-2:!LM!j?h2N`# GLoRa APRS (Digipeater) Batt=3.79V
20260208182325	9W4GAW-3>APLRG1,WIDE1-1,qAR,9W2DYA-L:!LM!j?h2N`# GLoRa APRS (Digipeater) Batt=3.82V
20260208185326	9W4GAW-3>APLRG1,WIDE1-1,qAR,9M2OCX-M:!LM!j?h2N`# GLoRa APRS (Digipeater) Batt=3.82V
20260208192326	9W4GAW-3>APLRG1,WIDE1-1,qAR,9W2DYA-L:!LM!j?h2N`# GLoRa APRS (Digipeater) Batt=3.81V
20260208195326	9W4GAW-3>APLRG1,WIDE1-1,qAR,9W2DYA-L:!LM!j?h2N`# GLoRa APRS (Digipeater) Batt=3.81V
20260208202326	9W4GAW-3>APLRG1,WIDE1-1,qAR,9M2OCX-M:!LM!j?h2N`# GLoRa APRS (Digipeater) Batt=3.80V