APRS Packet Errors for DF4FW-02 (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
20260209142953DF4FW-02>APRSMC,TCPIP*,qAR,DF4FW-12:!5331.36N/00802.04E-MeshCom Gateway#DF4FW-02/B=040
20260209150019DF4FW-02>APRSMC,TCPIP*,qAR,DF4FW-12:!5331.36N/00802.04E-MeshCom Gateway#DF4FW-02/B=040
20260209153045DF4FW-02>APRSMC,TCPIP*,qAR,DF4FW-12:!5331.36N/00802.04E-MeshCom Gateway#DF4FW-02/B=035
20260209160115DF4FW-02>APRSMC,TCPIP*,qAR,DF4FW-12:!5331.36N/00802.04E-MeshCom Gateway#DF4FW-02/B=028
20260209163142DF4FW-02>APRSMC,TCPIP*,qAR,DF4FW-12:!5331.36N/00802.04E-MeshCom Gateway#DF4FW-02/B=019
20260209170203DF4FW-02>APRSMC,TCPIP*,qAR,DF4FW-12:!5331.36N/00802.04E-MeshCom Gateway#DF4FW-02/B=016
20260209173228DF4FW-02>APRSMC,TCPIP*,qAR,DF4FW-12:!5331.36N/00802.04E-MeshCom Gateway#DF4FW-02/B=011
20260209180254DF4FW-02>APRSMC,TCPIP*,qAR,DF4FW-12:!5331.36N/00802.04E-MeshCom Gateway#DF4FW-02/B=009
20260209183320DF4FW-02>APRSMC,TCPIP*,qAR,DF4FW-12:!5331.36N/00802.04E-MeshCom Gateway#DF4FW-02/B=006
20260209190346DF4FW-02>APRSMC,TCPIP*,qAR,DF4FW-12:!5331.36N/00802.04E-MeshCom Gateway#DF4FW-02/B=002
20260209193411DF4FW-02>APRSMC,TCPIP*,qAR,DF4FW-12:!5331.36N/00802.04E-MeshCom Gateway#DF4FW-02
20260209200437DF4FW-02>APRSMC,TCPIP*,qAR,DF4FW-12:!5331.36N/00802.04E-MeshCom Gateway#DF4FW-02