APRS Packet Errors for EA1AER-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
20260209110008	EA1AER-10>APLOX1-1,TCPIP*,qAC,T2SPAIN2:!L8xBKM(Zna HLora iGate P=3.56V
20260209113008	EA1AER-10>APLOX1-1,TCPIP*,qAC,T2SPAIN2:!L8xBKM(Zna HLora iGate P=3.57V
20260209120208	EA1AER-10>APLOX1-1,TCPIP*,qAC,T2SPAIN2:!L8xBKM(Zna HLora iGate P=3.64V
20260209123008	EA1AER-10>APLOX1-1,TCPIP*,qAC,T2SPAIN2:!L8xBKM(Zna HLora iGate P=3.59V
20260209130008	EA1AER-10>APLOX1-1,TCPIP*,qAC,T2SPAIN2:!L8xBKM(Zna HLora iGate P=3.53V
20260209133008	EA1AER-10>APLOX1-1,TCPIP*,qAC,T2SPAIN2:!L8xBKM(Zna HLora iGate P=3.50V
20260209140209	EA1AER-10>APLOX1-1,TCPIP*,qAC,T2SPAIN2:!L8xBKM(Zna HLora iGate P=3.59V
20260209143009	EA1AER-10>APLOX1-1,TCPIP*,qAC,T2SPAIN2:!L8xBKM(Zna HLora iGate P=3.53V
20260209150009	EA1AER-10>APLOX1-1,TCPIP*,qAC,T2SPAIN2:!L8xBKM(Zna HLora iGate P=3.53V
20260209153009	EA1AER-10>APLOX1-1,TCPIP*,qAC,T2SPAIN2:!L8xBKM(Zna HLora iGate P=3.47V
20260209160209	EA1AER-10>APLOX1-1,TCPIP*,qAC,T2SPAIN2:!L8xBKM(Zna HLora iGate P=3.44V
20260209163009	EA1AER-10>APLOX1-1,TCPIP*,qAC,T2SPAIN2:!L8xBKM(Zna HLora iGate P=3.43V