APRS Packet Errors for EC2UW (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
20190216071432EC2UW>APZDMR,QTH,TCPIP*,qAU,T2EUSKADI:)EC2UW-DP!432686700.00N/-294rRNG0034 IPSC2-EA2Master MMDVM 431.0000 MHz
20190216073053EC2UW>APZDMR,QTH,TCPIP*,qAU,T2EUSKADI:)EC2UW-DP!432686700.00N/-294rRNG0034 IPSC2-EA2Master MMDVM 431.0000 MHz
20190216074712EC2UW>APZDMR,QTH,TCPIP*,qAU,T2EUSKADI:)EC2UW-DP!432686700.00N/-294rRNG0034 IPSC2-EA2Master MMDVM 431.0000 MHz
20190216080332EC2UW>APZDMR,QTH,TCPIP*,qAU,T2EUSKADI:)EC2UW-DP!432686700.00N/-294rRNG0034 IPSC2-EA2Master MMDVM 431.0000 MHz
20190216081950EC2UW>APZDMR,QTH,TCPIP*,qAU,T2EUSKADI:)EC2UW-DP!432686700.00N/-294rRNG0034 IPSC2-EA2Master MMDVM 431.0000 MHz
20190216083612EC2UW>APZDMR,QTH,TCPIP*,qAU,T2EUSKADI:)EC2UW-DP!432686700.00N/-294rRNG0034 IPSC2-EA2Master MMDVM 431.0000 MHz
20190216085232EC2UW>APZDMR,QTH,TCPIP*,qAU,T2EUSKADI:)EC2UW-DP!432686700.00N/-294rRNG0034 IPSC2-EA2Master MMDVM 431.0000 MHz
20190216090850EC2UW>APZDMR,QTH,TCPIP*,qAU,T2EUSKADI:)EC2UW-DP!432686700.00N/-294rRNG0034 IPSC2-EA2Master MMDVM 431.0000 MHz
20190216092510EC2UW>APZDMR,QTH,TCPIP*,qAU,T2EUSKADI:)EC2UW-DP!432686700.00N/-294rRNG0034 IPSC2-EA2Master MMDVM 431.0000 MHz
20190216094134EC2UW>APZDMR,QTH,TCPIP*,qAU,T2EUSKADI:)EC2UW-DP!432686700.00N/-294rRNG0034 IPSC2-EA2Master MMDVM 431.0000 MHz
20190216095755EC2UW>APZDMR,QTH,TCPIP*,qAU,T2EUSKADI:)EC2UW-DP!432686700.00N/-294rRNG0034 IPSC2-EA2Master MMDVM 431.0000 MHz
20190216101415EC2UW>APZDMR,QTH,TCPIP*,qAU,T2EUSKADI:)EC2UW-DP!432686700.00N/-294rRNG0034 IPSC2-EA2Master MMDVM 431.0000 MHz
20190216103034EC2UW>APZDMR,QTH,TCPIP*,qAU,T2EUSKADI:)EC2UW-DP!432686700.00N/-294rRNG0034 IPSC2-EA2Master MMDVM 431.0000 MHz
20190216104655EC2UW>APZDMR,QTH,TCPIP*,qAU,T2EUSKADI:)EC2UW-DP!432686700.00N/-294rRNG0034 IPSC2-EA2Master MMDVM 431.0000 MHz
20190216110315EC2UW>APZDMR,QTH,TCPIP*,qAU,T2EUSKADI:)EC2UW-DP!432686700.00N/-294rRNG0034 IPSC2-EA2Master MMDVM 431.0000 MHz
20190216111935EC2UW>APZDMR,QTH,TCPIP*,qAU,T2EUSKADI:)EC2UW-DP!432686700.00N/-294rRNG0034 IPSC2-EA2Master MMDVM 431.0000 MHz
20190216113554EC2UW>APZDMR,QTH,TCPIP*,qAU,T2EUSKADI:)EC2UW-DP!432686700.00N/-294rRNG0034 IPSC2-EA2Master MMDVM 431.0000 MHz
20190216115217EC2UW>APZDMR,QTH,TCPIP*,qAU,T2EUSKADI:)EC2UW-DP!432686700.00N/-294rRNG0034 IPSC2-EA2Master MMDVM 431.0000 MHz
20190216120838EC2UW>APZDMR,QTH,TCPIP*,qAU,T2EUSKADI:)EC2UW-DP!432686700.00N/-294rRNG0034 IPSC2-EA2Master MMDVM 431.0000 MHz
20190216122500EC2UW>APZDMR,QTH,TCPIP*,qAU,T2EUSKADI:)EC2UW-DP!432686700.00N/-294rRNG0034 IPSC2-EA2Master MMDVM 431.0000 MHz
20190216124123EC2UW>APZDMR,QTH,TCPIP*,qAU,T2EUSKADI:)EC2UW-DP!432686700.00N/-294rRNG0034 IPSC2-EA2Master MMDVM 431.0000 MHz
20190216125748EC2UW>APZDMR,QTH,TCPIP*,qAU,T2EUSKADI:)EC2UW-DP!432686700.00N/-294rRNG0034 IPSC2-EA2Master MMDVM 431.0000 MHz