APRS Packet Errors for DG1FDV-10 (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
20260209144641DG1FDV-10>APLRG1,TCPIP*,qAC,T2POLC:!L5*=PQA]_ G.../...g...t085h..b10125LoRa APRS GW
20260209151641DG1FDV-10>APLRG1,TCPIP*,qAC,T2POLC:!L5*=PQA]_ G.../...g...t078h..b10125LoRa APRS GW
20260209154641DG1FDV-10>APLRG1,TCPIP*,qAC,T2POLC:!L5*=PQA]_ G.../...g...t070h..b10126LoRa APRS GW
20260209161642DG1FDV-10>APLRG1,TCPIP*,qAC,T2POLC:!L5*=PQA]_ G.../...g...t065h..b10125LoRa APRS GW
20260209164642DG1FDV-10>APLRG1,TCPIP*,qAC,T2POLC:!L5*=PQA]_ G.../...g...t069h..b10121LoRa APRS GW
20260209171642DG1FDV-10>APLRG1,TCPIP*,qAC,T2POLC:!L5*=PQA]_ G.../...g...t082h..b10116LoRa APRS GW
20260209174642DG1FDV-10>APLRG1,TCPIP*,qAC,T2POLC:!L5*=PQA]_ G.../...g...t071h..b10117LoRa APRS GW
20260209181642DG1FDV-10>APLRG1,TCPIP*,qAC,T2POLC:!L5*=PQA]_ G.../...g...t066h..b10117LoRa APRS GW
20260209184642DG1FDV-10>APLRG1,TCPIP*,qAC,T2POLC:!L5*=PQA]_ G.../...g...t064h..b10117LoRa APRS GW
20260209191642DG1FDV-10>APLRG1,TCPIP*,qAC,T2POLC:!L5*=PQA]_ G.../...g...t075h..b10113LoRa APRS GW
20260209194642DG1FDV-10>APLRG1,TCPIP*,qAC,T2POLC:!L5*=PQA]_ G.../...g...t087h..b10111LoRa APRS GW
20260209201643DG1FDV-10>APLRG1,TCPIP*,qAC,T2POLC:!L5*=PQA]_ G.../...g...t075h..b10111LoRa APRS GW