APRS Packet Errors for VE3KMN (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
20190717044249VE3KMN>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE3KMN-DP!4524.75N/-75-41.83rRNG0034 IPSC2-BRAZIL MMDVM 441.0250 MHz
20190717045944VE3KMN>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE3KMN-DP!4524.75N/-75-41.83rRNG0034 IPSC2-BRAZIL MMDVM 441.0250 MHz
20190717051645VE3KMN>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE3KMN-DP!4524.75N/-75-41.83rRNG0034 IPSC2-BRAZIL MMDVM 441.0250 MHz
20190717053334VE3KMN>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE3KMN-DP!4524.75N/-75-41.83rRNG0034 IPSC2-BRAZIL MMDVM 441.0250 MHz
20190717055032VE3KMN>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE3KMN-DP!4524.75N/-75-41.83rRNG0034 IPSC2-BRAZIL MMDVM 441.0250 MHz
20190717060734VE3KMN>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE3KMN-DP!4524.75N/-75-41.83rRNG0034 IPSC2-BRAZIL MMDVM 441.0250 MHz
20190717062438VE3KMN>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE3KMN-DP!4524.75N/-75-41.83rRNG0034 IPSC2-BRAZIL MMDVM 441.0250 MHz
20190717064138VE3KMN>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE3KMN-DP!4524.75N/-75-41.83rRNG0034 IPSC2-BRAZIL MMDVM 441.0250 MHz
20190717065846VE3KMN>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE3KMN-DP!4524.75N/-75-41.83rRNG0034 IPSC2-BRAZIL MMDVM 441.0250 MHz
20190717071544VE3KMN>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE3KMN-DP!4524.75N/-75-41.83rRNG0034 IPSC2-BRAZIL MMDVM 441.0250 MHz
20190717073301VE3KMN>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE3KMN-DP!4524.75N/-75-41.83rRNG0034 IPSC2-BRAZIL MMDVM 441.0250 MHz
20190717075000VE3KMN>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE3KMN-DP!4524.75N/-75-41.83rRNG0034 IPSC2-BRAZIL MMDVM 441.0250 MHz
20190717080700VE3KMN>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE3KMN-DP!4524.75N/-75-41.83rRNG0034 IPSC2-BRAZIL MMDVM 441.0250 MHz
20190717082409VE3KMN>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE3KMN-DP!4524.75N/-75-41.83rRNG0034 IPSC2-BRAZIL MMDVM 441.0250 MHz
20190717084130VE3KMN>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE3KMN-DP!4524.75N/-75-41.83rRNG0034 IPSC2-BRAZIL MMDVM 441.0250 MHz
20190717085901VE3KMN>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE3KMN-DP!4524.75N/-75-41.83rRNG0034 IPSC2-BRAZIL MMDVM 441.0250 MHz
20190717091610VE3KMN>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE3KMN-DP!4524.75N/-75-41.83rRNG0034 IPSC2-BRAZIL MMDVM 441.0250 MHz
20190717093323VE3KMN>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE3KMN-DP!4524.75N/-75-41.83rRNG0034 IPSC2-BRAZIL MMDVM 441.0250 MHz
20190717095037VE3KMN>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE3KMN-DP!4524.75N/-75-41.83rRNG0034 IPSC2-BRAZIL MMDVM 441.0250 MHz
20190717102420VE3KMN>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE3KMN-DP!4524.75N/-75-41.83rRNG0034 IPSC2-BRAZIL MMDVM 441.0250 MHz