APRS Packet Errors for EA4D-11 (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
20260208151849EA4D-11>APLOX1,WIDE1-1,qAO,EA4BX-10:!L:&sjMX!N# XEA4D Lora iGate System P=4.26V
20260208154856EA4D-11>APLOX1,TCPIP*,qAC,T2SPAIN:!L:&sjMX!N# XEA4D Lora iGate System P=4.17V
20260208161915EA4D-11>APLOX1,TCPIP*,qAC,T2SPAIN:!L:&sjMX!N# XEA4D Lora iGate System P=4.40V
20260208164921EA4D-11>APLOX1,TCPIP*,qAC,T2SPAIN:!L:&sjMX!N# XEA4D Lora iGate System P=4.17V
20260208171927EA4D-11>APLOX1,TCPIP*,qAC,T2SPAIN:!L:&sjMX!N# XEA4D Lora iGate System P=4.43V
20260208174932EA4D-11>APLOX1,TCPIP*,qAC,T2SPAIN:!L:&sjMX!N# XEA4D Lora iGate System P=4.35V
20260208181940EA4D-11>APLOX1,TCPIP*,qAC,T2SPAIN:!L:&sjMX!N# XEA4D Lora iGate System P=4.37V
20260208184944EA4D-11>APLOX1,TCPIP*,qAC,T2SPAIN:!L:&sjMX!N# XEA4D Lora iGate System P=4.29V
20260208191951EA4D-11>APLOX1,TCPIP*,qAC,T2SPAIN:!L:&sjMX!N# XEA4D Lora iGate System P=4.23V
20260208195001EA4D-11>APLOX1,TCPIP*,qAC,T2SPAIN:!L:&sjMX!N# XEA4D Lora iGate System P=4.30V
20260208202010EA4D-11>APLOX1,TCPIP*,qAC,T2SPAIN:!L:&sjMX!N# XEA4D Lora iGate System P=4.34V
20260208205014EA4D-11>APLOX1,TCPIP*,qAC,T2SPAIN:!L:&sjMX!N# XEA4D Lora iGate System P=4.42V