APRS Packet Errors for EC5M-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
20260209120640EC5M-10>APLOX1,TCPIP*,qAC,T2CSNGRAD:!L:y:XN@]f& XLora iGate Ibi 433.775 MHz
20260209123645EC5M-10>APLOX1,TCPIP*,qAC,T2CSNGRAD:!L:y:XN@]f& XLora iGate Ibi 433.775 MHz
20260209130649EC5M-10>APLOX1,TCPIP*,qAC,T2CSNGRAD:!L:y:XN@]f& XLora iGate Ibi 433.775 MHz
20260209133655EC5M-10>APLOX1,TCPIP*,qAC,T2CSNGRAD:!L:y:XN@]f& XLora iGate Ibi 433.775 MHz
20260209140659EC5M-10>APLOX1,TCPIP*,qAC,T2CSNGRAD:!L:y:XN@]f& XLora iGate Ibi 433.775 MHz
20260209143704EC5M-10>APLOX1,TCPIP*,qAC,T2CSNGRAD:!L:y:XN@]f& XLora iGate Ibi 433.775 MHz
20260209150711EC5M-10>APLOX1,TCPIP*,qAC,T2CSNGRAD:!L:y:XN@]f& XLora iGate Ibi 433.775 MHz
20260209153717EC5M-10>APLOX1,TCPIP*,qAC,T2CSNGRAD:!L:y:XN@]f& XLora iGate Ibi 433.775 MHz
20260209160722EC5M-10>APLOX1,TCPIP*,qAC,T2CSNGRAD:!L:y:XN@]f& XLora iGate Ibi 433.775 MHz
20260209163729EC5M-10>APLOX1,TCPIP*,qAC,T2CSNGRAD:!L:y:XN@]f& XLora iGate Ibi 433.775 MHz
20260209170734EC5M-10>APLOX1,TCPIP*,qAC,T2CSNGRAD:!L:y:XN@]f& XLora iGate Ibi 433.775 MHz
20260209173738EC5M-10>APLOX1,TCPIP*,qAC,T2CSNGRAD:!L:y:XN@]f& XLora iGate Ibi 433.775 MHz