APRS Packet Errors for EA4D-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
20260208164551EA4D-10>APLOX1,TCPIP*,qAC,T2UKRAINE:!L9z4(M`.M# XEA4D Lora iGate System P=4.32V
20260208171556EA4D-10>APLOX1,TCPIP*,qAC,T2UKRAINE:!L9z4(M`.M# XEA4D Lora iGate System P=4.26V
20260208174600EA4D-10>APLOX1,TCPIP*,qAC,T2UKRAINE:!L9z4(M`.M# XEA4D Lora iGate System P=4.37V
20260208181605EA4D-10>APLOX1,TCPIP*,qAC,T2UKRAINE:!L9z4(M`.M# XEA4D Lora iGate System P=4.29V
20260208184613EA4D-10>APLOX1,TCPIP*,qAC,T2UKRAINE:!L9z4(M`.M# XEA4D Lora iGate System P=4.31V
20260208191620EA4D-10>APLOX1,TCPIP*,qAC,T2UKRAINE:!L9z4(M`.M# XEA4D Lora iGate System P=4.48V
20260208194628EA4D-10>APLOX1,TCPIP*,qAC,T2UKRAINE:!L9z4(M`.M# XEA4D Lora iGate System P=4.26V
20260208201638EA4D-10>APLOX1,TCPIP*,qAC,T2UKRAINE:!L9z4(M`.M# XEA4D Lora iGate System P=4.43V
20260208204642EA4D-10>APLOX1,TCPIP*,qAC,T2UKRAINE:!L9z4(M`.M# XEA4D Lora iGate System P=4.44V
20260208211649EA4D-10>APLOX1,TCPIP*,qAC,T2UKRAINE:!L9z4(M`.M# XEA4D Lora iGate System P=4.32V
20260208214654EA4D-10>APLOX1,WIDE1-1,qAS,EA4LO-10:!L9z4(M`.M# XEA4D Lora iGate System P=4.49V
20260208221700EA4D-10>APLOX1,TCPIP*,qAC,T2UKRAINE:!L9z4(M`.M# XEA4D Lora iGate System P=4.30V