APRS Packet Errors for XE3EA (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
20260209133500XE3EA>APDW17,TCPIP*,qAC,T2TEXAS:!2100.22N/08935.83WyAPRS MERIDA 144.390 MHz
20260209140500XE3EA>APDW17,TCPIP*,qAC,T2TEXAS:!2100.22N/08935.83WyAPRS MERIDA 144.390 MHz
20260209143500XE3EA>APDW17,TCPIP*,qAC,T2TEXAS:!2100.22N/08935.83WyAPRS MERIDA 144.390 MHz
20260209150500XE3EA>APDW17,TCPIP*,qAC,T2TEXAS:!2100.22N/08935.83WyAPRS MERIDA 144.390 MHz
20260209153500XE3EA>APDW17,TCPIP*,qAC,T2TEXAS:!2100.22N/08935.83WyAPRS MERIDA 144.390 MHz
20260209160500XE3EA>APDW17,TCPIP*,qAC,T2TEXAS:!2100.22N/08935.83WyAPRS MERIDA 144.390 MHz
20260209163500XE3EA>APDW17,TCPIP*,qAC,T2TEXAS:!2100.22N/08935.83WyAPRS MERIDA 144.390 MHz
20260209170500XE3EA>APDW17,TCPIP*,qAC,T2TEXAS:!2100.22N/08935.83WyAPRS MERIDA 144.390 MHz
20260209173500XE3EA>APDW17,TCPIP*,qAC,T2TEXAS:!2100.22N/08935.83WyAPRS MERIDA 144.390 MHz
20260209180500XE3EA>APDW17,TCPIP*,qAC,T2TEXAS:!2100.22N/08935.83WyAPRS MERIDA 144.390 MHz
20260209183500XE3EA>APDW17,TCPIP*,qAC,T2TEXAS:!2100.22N/08935.83WyAPRS MERIDA 144.390 MHz
20260209190500XE3EA>APDW17,TCPIP*,qAC,T2TEXAS:!2100.22N/08935.83WyAPRS MERIDA 144.390 MHz