APRS Packet Errors for IR3UDB (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
20220630054551IR3UDB>APRS,TCPIP*,qAC,IQ3XQ-11:!4696.30N/0138.340ErARI-RCE FVG RX: 432.8625 TX: 431.2625
20220630060051IR3UDB>APRS,TCPIP*,qAC,IQ3XQ-11:!4696.30N/0138.340ErARI-RCE FVG RX: 432.8625 TX: 431.2625
20220630061551IR3UDB>APRS,TCPIP*,qAC,IQ3XQ-11:!4696.30N/0138.340ErARI-RCE FVG RX: 432.8625 TX: 431.2625
20220630063051IR3UDB>APRS,TCPIP*,qAC,IQ3XQ-11:!4696.30N/0138.340ErARI-RCE FVG RX: 432.8625 TX: 431.2625
20220630064551IR3UDB>APRS,TCPIP*,qAC,IQ3XQ-11:!4696.30N/0138.340ErARI-RCE FVG RX: 432.8625 TX: 431.2625
20220630070051IR3UDB>APRS,TCPIP*,qAC,IQ3XQ-11:!4696.30N/0138.340ErARI-RCE FVG RX: 432.8625 TX: 431.2625
20220630071551IR3UDB>APRS,TCPIP*,qAC,IQ3XQ-11:!4696.30N/0138.340ErARI-RCE FVG RX: 432.8625 TX: 431.2625
20220630073051IR3UDB>APRS,TCPIP*,qAC,IQ3XQ-11:!4696.30N/0138.340ErARI-RCE FVG RX: 432.8625 TX: 431.2625
20220630074551IR3UDB>APRS,TCPIP*,qAC,IQ3XQ-11:!4696.30N/0138.340ErARI-RCE FVG RX: 432.8625 TX: 431.2625
20220630080051IR3UDB>APRS,TCPIP*,qAC,IQ3XQ-11:!4696.30N/0138.340ErARI-RCE FVG RX: 432.8625 TX: 431.2625
20220630081551IR3UDB>APRS,TCPIP*,qAC,IQ3XQ-11:!4696.30N/0138.340ErARI-RCE FVG RX: 432.8625 TX: 431.2625
20220630083051IR3UDB>APRS,TCPIP*,qAC,IQ3XQ-11:!4696.30N/0138.340ErARI-RCE FVG RX: 432.8625 TX: 431.2625
20220630084551IR3UDB>APRS,TCPIP*,qAC,IQ3XQ-11:!4696.30N/0138.340ErARI-RCE FVG RX: 432.8625 TX: 431.2625
20220630090051IR3UDB>APRS,TCPIP*,qAC,IQ3XQ-11:!4696.30N/0138.340ErARI-RCE FVG RX: 432.8625 TX: 431.2625
20220630091551IR3UDB>APRS,TCPIP*,qAC,IQ3XQ-11:!4696.30N/0138.340ErARI-RCE FVG RX: 432.8625 TX: 431.2625
20220630093051IR3UDB>APRS,TCPIP*,qAC,IQ3XQ-11:!4696.30N/0138.340ErARI-RCE FVG RX: 432.8625 TX: 431.2625
20220630094551IR3UDB>APRS,TCPIP*,qAC,IQ3XQ-11:!4696.30N/0138.340ErARI-RCE FVG RX: 432.8625 TX: 431.2625
20220630100051IR3UDB>APRS,TCPIP*,qAC,IQ3XQ-11:!4696.30N/0138.340ErARI-RCE FVG RX: 432.8625 TX: 431.2625
20220630101551IR3UDB>APRS,TCPIP*,qAC,IQ3XQ-11:!4696.30N/0138.340ErARI-RCE FVG RX: 432.8625 TX: 431.2625
20220630103051IR3UDB>APRS,TCPIP*,qAC,IQ3XQ-11:!4696.30N/0138.340ErARI-RCE FVG RX: 432.8625 TX: 431.2625
20220630104551IR3UDB>APRS,TCPIP*,qAC,IQ3XQ-11:!4696.30N/0138.340ErARI-RCE FVG RX: 432.8625 TX: 431.2625
20220630110051IR3UDB>APRS,TCPIP*,qAC,IQ3XQ-11:!4696.30N/0138.340ErARI-RCE FVG RX: 432.8625 TX: 431.2625
20220630111551IR3UDB>APRS,TCPIP*,qAC,IQ3XQ-11:!4696.30N/0138.340ErARI-RCE FVG RX: 432.8625 TX: 431.2625
20220630113051IR3UDB>APRS,TCPIP*,qAC,IQ3XQ-11:!4696.30N/0138.340ErARI-RCE FVG RX: 432.8625 TX: 431.2625