APRS Packet Errors for VK3CDE (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
20241222053419	VK3CDE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK3CDE-DP!27-0.00S/13300.00ErRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1750 MHz
20241222065015	VK3CDE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK3CDE-DP!27-0.00S/13300.00ErRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1750 MHz
20241222072839	VK3CDE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK3CDE-DP!27-0.00S/13300.00ErRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1750 MHz
20241222080713	VK3CDE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK3CDE-DP!27-0.00S/13300.00ErRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1750 MHz
20241222084636	VK3CDE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK3CDE-DP!27-0.00S/13300.00ErRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1750 MHz
20241222090155	VK3CDE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK3CDE-DP!27-0.00S/13300.00ErRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1750 MHz
20241222094221	VK3CDE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK3CDE-DP!27-0.00S/13300.00ErRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1750 MHz
20241222102102	VK3CDE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK3CDE-DP!27-0.00S/13300.00ErRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1750 MHz
20241222105930	VK3CDE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK3CDE-DP!27-0.00S/13300.00ErRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1750 MHz