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
20260209150927	EA2AIV-10>APLOX1,TCPIP*,qAC,T2UKRAINE:!L9J#N8_m& XLora iGate P=4.03V
20260209153932	EA2AIV-10>APLOX1,TCPIP*,qAC,T2UKRAINE:!L9J#N8_m& XLora iGate P=4.27V
20260209160936	EA2AIV-10>APLOX1,WIDE1-1,Q,qAR,EA2DRO-10:!L9J#N8_m& XLora iGate P=4.03V
20260209163940	EA2AIV-10>APLOX1,WIDE1-1,Q,qAR,EA2DRO-10:!L9J#N8_m& XLora iGate P=4.15V
20260209170948	EA2AIV-10>APLOX1,WIDE1-1,Q,qAR,EA2DRO-10:!L9J#N8_m& XLora iGate P=4.21V
20260209173955	EA2AIV-10>APLOX1,WIDE1-1,Q,qAR,EA2DRO-10:!L9J#N8_m& XLora iGate P=4.20V
20260209181008	EA2AIV-10>APLOX1,TCPIP*,qAC,T2UKRAINE:!L9J#N8_m& XLora iGate P=4.12V
20260209184023	EA2AIV-10>APLOX1,WIDE1-1,Q,qAR,EA2DRO-10:!L9J#N8_m& XLora iGate P=4.07V
20260209191030	EA2AIV-10>APLOX1,TCPIP*,qAC,T2UKRAINE:!L9J#N8_m& XLora iGate P=4.15V
20260209194042	EA2AIV-10>APLOX1,WIDE1-1,Q,qAR,EA2DRO-10:!L9J#N8_m& XLora iGate P=4.25V
20260209201057	EA2AIV-10>APLOX1,WIDE1-1,Q,qAR,EA2DRO-10:!L9J#N8_m& XLora iGate P=4.20V
20260209204101	EA2AIV-10>APLOX1,TCPIP*,qAC,T2UKRAINE:!L9J#N8_m& XLora iGate P=4.20V