APRS Packet Errors for VK7DY (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
20260405120409VK7DY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK7DY-DP!42-0.00S/14731.05ErRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1750 MHz
20260405124011VK7DY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK7DY-DP!42-0.00S/14731.05ErRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1750 MHz
20260405131610VK7DY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK7DY-DP!42-0.00S/14731.05ErRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1750 MHz
20260405135207VK7DY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK7DY-DP!42-0.00S/14731.05ErRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1750 MHz
20260405142756VK7DY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK7DY-DP!42-0.00S/14731.05ErRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1750 MHz
20260405150354VK7DY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK7DY-DP!42-0.00S/14731.05ErRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1750 MHz
20260405153947VK7DY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK7DY-DP!42-0.00S/14731.05ErRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1750 MHz
20260405161550VK7DY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK7DY-DP!42-0.00S/14731.05ErRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1750 MHz
20260405165141VK7DY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK7DY-DP!42-0.00S/14731.05ErRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1750 MHz
20260405172723VK7DY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK7DY-DP!42-0.00S/14731.05ErRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1750 MHz