APRS Packet Errors for EA2SPS-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
20260209093628	EA2SPS-10>APLOX1,TCPIP*,qAC,T2SPAIN:!L8ViPN$97a XLora iGate P=4.48V
20260209100628	EA2SPS-10>APLOX1,TCPIP*,qAC,T2SPAIN:!L8ViPN$97a XLora iGate P=4.48V
20260209103628	EA2SPS-10>APLOX1,TCPIP*,qAC,T2SPAIN:!L8ViPN$97a XLora iGate P=4.48V
20260209110628	EA2SPS-10>APLOX1,TCPIP*,qAC,T2SPAIN:!L8ViPN$97a XLora iGate P=4.34V
20260209113629	EA2SPS-10>APLOX1,TCPIP*,qAC,T2SPAIN:!L8ViPN$97a XLora iGate P=4.36V
20260209120629	EA2SPS-10>APLOX1,TCPIP*,qAC,T2SPAIN:!L8ViPN$97a XLora iGate P=4.41V
20260209123629	EA2SPS-10>APLOX1,TCPIP*,qAC,T2SPAIN:!L8ViPN$97a XLora iGate P=4.35V
20260209130629	EA2SPS-10>APLOX1,TCPIP*,qAC,T2SPAIN:!L8ViPN$97a XLora iGate P=4.40V
20260209133629	EA2SPS-10>APLOX1,TCPIP*,qAC,T2SPAIN:!L8ViPN$97a XLora iGate P=4.37V
20260209140630	EA2SPS-10>APLOX1,TCPIP*,qAC,T2SPAIN:!L8ViPN$97a XLora iGate P=4.51V
20260209143630	EA2SPS-10>APLOX1,TCPIP*,qAC,T2SPAIN:!L8ViPN$97a XLora iGate P=4.43V
20260209150630	EA2SPS-10>APLOX1,TCPIP*,qAC,T2SPAIN:!L8ViPN$97a XLora iGate P=4.38V