APRS Packet Errors for EA4CZ-4 (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
20260208152912EA4CZ-4>APLOX1,TCPIP*,qAC,T2CZECH:!L:VN5M-*!a XLoRa iGate by Daniboy P=4.16V
20260208155912EA4CZ-4>APLOX1,TCPIP*,qAC,T2CZECH:!L:VN5M-*!a XLoRa iGate by Daniboy P=4.12V
20260208163112EA4CZ-4>APLOX1,TCPIP*,qAC,T2CZECH:!L:VN5M-*!a XLoRa iGate by Daniboy P=4.03V
20260208165913EA4CZ-4>APLOX1,TCPIP*,qAC,T2CZECH:!L:VN5M-*!a XLoRa iGate by Daniboy P=4.26V
20260208172913EA4CZ-4>APLOX1,TCPIP*,qAC,T2CZECH:!L:VN5M-*!a XLoRa iGate by Daniboy P=4.22V
20260208175913EA4CZ-4>APLOX1,TCPIP*,qAC,T2CZECH:!L:VN5M-*!a XLoRa iGate by Daniboy P=4.05V
20260208183113EA4CZ-4>APLOX1,TCPIP*,qAC,T2CZECH:!L:VN5M-*!a XLoRa iGate by Daniboy P=4.16V
20260208185913EA4CZ-4>APLOX1,TCPIP*,qAC,T2CZECH:!L:VN5M-*!a XLoRa iGate by Daniboy P=4.34V
20260208192914EA4CZ-4>APLOX1,TCPIP*,qAC,T2CZECH:!L:VN5M-*!a XLoRa iGate by Daniboy P=4.25V
20260208195914EA4CZ-4>APLOX1,TCPIP*,qAC,T2CZECH:!L:VN5M-*!a XLoRa iGate by Daniboy P=3.97V
20260208203114EA4CZ-4>APLOX1,TCPIP*,qAC,T2CZECH:!L:VN5M-*!a XLoRa iGate by Daniboy P=4.15V
20260208205914EA4CZ-4>APLOX1,TCPIP*,qAC,T2CZECH:!L:VN5M-*!a XLoRa iGate by Daniboy P=4.11V