APRS Packet Errors for ED4YAD-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
20260208132536ED4YAD-10>APLOX1,TCPIP*,qAC,T2SPAIN:!L:,!lMRQB& XLora iGate by EA4URA P=4.39V
20260208135537ED4YAD-10>APLOX1,TCPIP*,qAC,T2SPAIN:!L:,!lMRQB& XLora iGate by EA4URA P=4.25V
20260208142737ED4YAD-10>APLOX1,TCPIP*,qAC,T2SPAIN:!L:,!lMRQB& XLora iGate by EA4URA P=4.45V
20260208145537ED4YAD-10>APLOX1,TCPIP*,qAC,T2SPAIN:!L:,!lMRQB& XLora iGate by EA4URA P=4.20V
20260208152537ED4YAD-10>APLOX1,TCPIP*,qAC,T2SPAIN:!L:,!lMRQB& XLora iGate by EA4URA P=4.28V
20260208155537ED4YAD-10>APLOX1,TCPIP*,qAC,T2SPAIN:!L:,!lMRQB& XLora iGate by EA4URA P=4.22V
20260208162738ED4YAD-10>APLOX1,TCPIP*,qAC,T2SPAIN:!L:,!lMRQB& XLora iGate by EA4URA P=4.35V
20260208165538ED4YAD-10>APLOX1,TCPIP*,qAC,T2SPAIN:!L:,!lMRQB& XLora iGate by EA4URA P=4.36V
20260208172538ED4YAD-10>APLOX1,TCPIP*,qAC,T2SPAIN:!L:,!lMRQB& XLora iGate by EA4URA P=4.37V
20260208175538ED4YAD-10>APLOX1,TCPIP*,qAC,T2SPAIN:!L:,!lMRQB& XLora iGate by EA4URA P=4.43V
20260208182738ED4YAD-10>APLOX1,TCPIP*,qAC,T2SPAIN:!L:,!lMRQB& XLora iGate by EA4URA P=4.42V
20260208185538ED4YAD-10>APLOX1,TCPIP*,qAC,T2SPAIN:!L:,!lMRQB& XLora iGate by EA4URA P=4.21V