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
20260208133651EA1AER-10>APLOX1-1,TCPIP*,qAC,T2SPAIN2:!L8xBKM(Zna HLora iGate P=4.34V
20260208140852EA1AER-10>APLOX1-1,TCPIP*,qAC,T2SPAIN2:!L8xBKM(Zna HLora iGate P=4.34V
20260208143652EA1AER-10>APLOX1-1,TCPIP*,qAC,T2SPAIN2:!L8xBKM(Zna HLora iGate P=4.23V
20260208150652EA1AER-10>APLOX1-1,TCPIP*,qAC,T2SPAIN2:!L8xBKM(Zna HLora iGate P=4.18V
20260208153652EA1AER-10>APLOX1-1,TCPIP*,qAC,T2SPAIN2:!L8xBKM(Zna HLora iGate P=4.17V
20260208160852EA1AER-10>APLOX1-1,TCPIP*,qAC,T2SPAIN2:!L8xBKM(Zna HLora iGate P=4.16V
20260208163002EA1AER-10>APLOX1-1,TCPIP*,qAC,T2SPAIN2:!L8xBKM(Zna HLora iGate P=4.18V
20260208170002EA1AER-10>APLOX1-1,TCPIP*,qAC,T2SPAIN2:!L8xBKM(Zna HLora iGate P=4.14V
20260208173002EA1AER-10>APLOX1-1,TCPIP*,qAC,T2SPAIN2:!L8xBKM(Zna HLora iGate P=4.14V
20260208180202EA1AER-10>APLOX1-1,TCPIP*,qAC,T2SPAIN2:!L8xBKM(Zna HLora iGate P=4.11V
20260208183002EA1AER-10>APLOX1-1,TCPIP*,qAC,T2SPAIN2:!L8xBKM(Zna HLora iGate P=4.12V
20260208190003EA1AER-10>APLOX1-1,TCPIP*,qAC,T2SPAIN2:!L8xBKM(Zna HLora iGate P=4.12V