APRS Packet Errors for PY4HF (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
20260209090511PY4HF>APDR16,TCPIP*,qAC,T2BRAZIL:=2054.28S/04516.62Wd000/000/439450.000MHz/A=002855 Rodrigo Di
20260209093816PY4HF>APDR16,TCPIP*,qAC,T2BRAZIL:=2054.28S/04516.62Wd062/000/439450.000MHz/A=002794 Rodrigo Di
20260209100821PY4HF>APDR16,TCPIP*,qAC,T2BRAZIL:=2054.28S/04516.62Wd000/000/439450.000MHz/A=002818 Rodrigo Di
20260209105611PY4HF>APDR16,TCPIP*,qAC,T2BRAZIL:=2054.28S/04516.62Wd000/000/439450.000MHz/A=002772 Rodrigo Di
20260209112617PY4HF>APDR16,TCPIP*,qAC,T2BRAZIL:=2054.28S/04516.62Wd000/000/439450.000MHz/A=002731 Rodrigo Di
20260209115627PY4HF>APDR16,TCPIP*,qAC,T2BRAZIL:=2054.28S/04516.62Wd000/000/439450.000MHz/A=002752 Rodrigo Di
20260209124602PY4HF>APDR16,TCPIP*,qAC,T2BRAZIL:=2054.28S/04516.61Wd092/000/439450.000MHz/A=002775 Rodrigo Di
20260209132310PY4HF>APDR16,TCPIP*,qAC,T2BRAZIL:=2054.28S/04516.62Wd322/000/439450.000MHz/A=002741 Rodrigo Di
20260209135327PY4HF>APDR16,TCPIP*,qAC,T2BRAZIL:=2054.28S/04516.62Wd000/000/439450.000MHz/A=002849 Rodrigo Di
20260209142338PY4HF>APDR16,TCPIP*,qAC,T2BRAZIL:=2054.28S/04516.62Wd000/000/439450.000MHz/A=002769 Rodrigo Di
20260209145347PY4HF>APDR16,TCPIP*,qAC,T2BRAZIL:=2054.27S/04516.62Wd291/000/439450.000MHz/A=002875 Rodrigo Di