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
20260704024754	VK7DY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK7DY-DP!42-0.00S/14731.05ErRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1750 MHz
20260704032353	VK7DY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK7DY-DP!42-0.00S/14731.05ErRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1750 MHz
20260704035952	VK7DY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK7DY-DP!42-0.00S/14731.05ErRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1750 MHz
20260704043601	VK7DY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK7DY-DP!42-0.00S/14731.05ErRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1750 MHz
20260704051201	VK7DY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK7DY-DP!42-0.00S/14731.05ErRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1750 MHz
20260704054801	VK7DY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK7DY-DP!42-0.00S/14731.05ErRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1750 MHz
20260704062402	VK7DY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK7DY-DP!42-0.00S/14731.05ErRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1750 MHz
20260704070007	VK7DY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK7DY-DP!42-0.00S/14731.05ErRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1750 MHz
20260704073618	VK7DY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK7DY-DP!42-0.00S/14731.05ErRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1750 MHz
20260704081237	VK7DY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK7DY-DP!42-0.00S/14731.05ErRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1750 MHz