APRS Packet Errors for W4JDH-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
20260208145941W4JDH-1>APRX29,TCPIP*,qAC,T2PERTH:!4735.99NI12218.49W&Hyper-local iGate - RPi3 w/Aprx on Debian 12
20260208155205W4JDH-1>APRX29,TCPIP*,qAC,T2PERTH:!4735.99NI12218.49W&Hyper-local iGate - RPi3 w/Aprx on Debian 12
20260208164251W4JDH-1>APRX29,TCPIP*,qAC,T2PERTH:!4735.99NI12218.49W&Hyper-local iGate - RPi3 w/Aprx on Debian 12
20260208173516W4JDH-1>APRX29,TCPIP*,qAC,T2PERTH:!4735.99NI12218.49W&Hyper-local iGate - RPi3 w/Aprx on Debian 12
20260208183351W4JDH-1>APRX29,TCPIP*,qAC,T2PERTH:!4735.99NI12218.49W&Hyper-local iGate - RPi3 w/Aprx on Debian 12
20260208192256W4JDH-1>APRX29,TCPIP*,qAC,T2PERTH:!4735.99NI12218.49W&Hyper-local iGate - RPi3 w/Aprx on Debian 12
20260208202236W4JDH-1>APRX29,TCPIP*,qAC,T2PERTH:!4735.99NI12218.49W&Hyper-local iGate - RPi3 w/Aprx on Debian 12