APRS Packet Errors for HS2EBX-1 (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
20260209103412HS2EBX-1>APRX20,TCPIP*,qAC,APRSTH:!1615.31NI10357.16E&XGatE ReV.1.0 FinaL EditioN
20260209110244HS2EBX-1>APRX20,TCPIP*,qAC,APRSTH:!1615.31NI10357.16E&XGatE ReV.1.0 FinaL EditioN
20260209112907HS2EBX-1>APRX20,TCPIP*,qAC,APRSTH:!1615.31NI10357.16E&XGatE ReV.1.0 FinaL EditioN
20260209115409HS2EBX-1>APRX20,TCPIP*,qAC,APRSTH:!1615.31NI10357.16E&XGatE ReV.1.0 FinaL EditioN
20260209121928HS2EBX-1>APRX20,TCPIP*,qAC,APRSTH:!1615.31NI10357.16E&XGatE ReV.1.0 FinaL EditioN
20260209124631HS2EBX-1>APRX20,TCPIP*,qAC,APRSTH:!1615.31NI10357.16E&XGatE ReV.1.0 FinaL EditioN
20260209131445HS2EBX-1>APRX20,TCPIP*,qAC,APRSTH:!1615.31NI10357.16E&XGatE ReV.1.0 FinaL EditioN
20260209134127HS2EBX-1>APRX20,TCPIP*,qAC,APRSTH:!1615.31NI10357.16E&XGatE ReV.1.0 FinaL EditioN
20260209140823HS2EBX-1>APRX20,TCPIP*,qAC,APRSTH:!1615.31NI10357.16E&XGatE ReV.1.0 FinaL EditioN
20260209143504HS2EBX-1>APRX20,TCPIP*,qAC,APRSTH:!1615.31NI10357.16E&XGatE ReV.1.0 FinaL EditioN
20260209150412HS2EBX-1>APRX20,TCPIP*,qAC,APRSTH:!1615.31NI10357.16E&XGatE ReV.1.0 FinaL EditioN
20260209153109HS2EBX-1>APRX20,TCPIP*,qAC,APRSTH:!1615.31NI10357.16E&XGatE ReV.1.0 FinaL EditioN
20260209155847HS2EBX-1>APRX20,TCPIP*,qAC,APRSTH:!1615.31NI10357.16E&XGatE ReV.1.0 FinaL EditioN