APRS Packet Errors for EA2AIV-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
20260208153349	EA2AIV-10>APLOX1,TCPIP*,qAC,T2UKRAINE:!L9J#N8_m& XLora iGate P=4.12V
20260208160354	EA2AIV-10>APLOX1,TCPIP*,qAC,T2UKRAINE:!L9J#N8_m& XLora iGate P=4.16V
20260208163400	EA2AIV-10>APLOX1,TCPIP*,qAC,T2UKRAINE:!L9J#N8_m& XLora iGate P=4.03V
20260208170405	EA2AIV-10>APLOX1,TCPIP*,qAC,T2UKRAINE:!L9J#N8_m& XLora iGate P=4.25V
20260208173409	EA2AIV-10>APLOX1,TCPIP*,qAC,T2UKRAINE:!L9J#N8_m& XLora iGate P=4.21V
20260208180414	EA2AIV-10>APLOX1,TCPIP*,qAC,T2UKRAINE:!L9J#N8_m& XLora iGate P=4.16V
20260208180446	EA2AIV-10>APLOX1,EB2EAS-10*,Q,qAR,EA2Z-10:!L9J#N8_m& XLora iGate P=4.16V
20260208183425	EA2AIV-10>APLOX1,TCPIP*,qAC,T2UKRAINE:!L9J#N8_m& XLora iGate P=4.23V
20260208190435	EA2AIV-10>APLOX1,TCPIP*,qAC,T2UKRAINE:!L9J#N8_m& XLora iGate P=4.23V
20260208193441	EA2AIV-10>APLOX1,TCPIP*,qAC,T2UKRAINE:!L9J#N8_m& XLora iGate P=4.15V
20260208200456	EA2AIV-10>APLOX1,TCPIP*,qAC,T2UKRAINE:!L9J#N8_m& XLora iGate P=4.08V
20260208203509	EA2AIV-10>APLOX1,TCPIP*,qAC,T2UKRAINE:!L9J#N8_m& XLora iGate P=4.25V
20260208210515	EA2AIV-10>APLOX1,TCPIP*,qAC,T2UKRAINE:!L9J#N8_m& XLora iGate P=4.07V
20260208210550	EA2AIV-10>APLOX1,EA2DRO-10*,Q,qAR,EA2CCQ-10:!L9J#N8_m& XLora iGate P=4.07V