APRS Packet Errors for EA1IAM-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
20260208183408EA1IAM-10>APLOX1,TCPIP*,qAC,T2PRT:!L8`+XL2.q& XLoRa iGate IN53kd Batt=3.48V/4%+ P=4.75V
20260208190209EA1IAM-10>APLOX1,TCPIP*,qAC,T2PRT:!L8`+XL2.q& XLoRa iGate IN53kd Batt=3.48V/4% P=4.85V
20260208193210EA1IAM-10>APLOX1,TCPIP*,qAC,T2CZECH:!L8`+XL2.q& XLoRa iGate IN53kd Batt=3.47V/4% P=4.71V
20260208200212EA1IAM-10>APLOX1,TCPIP*,qAC,T2CZECH:!L8`+XL2.q& XLoRa iGate IN53kd Batt=3.47V/4% P=4.85V
20260208203413EA1IAM-10>APLOX1,TCPIP*,qAC,T2CZECH:!L8`+XL2.q& XLoRa iGate IN53kd Batt=3.47V/4% P=4.70V
20260208210214EA1IAM-10>APLOX1,TCPIP*,qAC,T2SPAIN:!L8`+XL2.q& XLoRa iGate IN53kd Batt=3.44V/4%-
20260208213216EA1IAM-10>APLOX1,TCPIP*,qAC,T2SPAIN:!L8`+XL2.q& XLoRa iGate IN53kd Batt=3.40V/2%-
20260208220218EA1IAM-10>APLOX1,TCPIP*,qAC,T2CSNGRAD:!L8`+XL2.q& XLoRa iGate IN53kd Batt=3.34V/1%-
20260208223420EA1IAM-10>APLOX1,TCPIP*,qAC,T2CSNGRAD:!L8`+XL2.q& XLoRa iGate IN53kd Batt=3.06V/0%-