APRS Packet Errors for EA7JIB (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
20201020113331EA7JIB>APRS,TCPIP*,qAS,BM2142POS:@201333z4116.100N/00134.100ErMMDVM DMO 224.9400/222.3400 CC1
20201020120451EA7JIB>APRS,TCPIP*,qAS,BM2142POS:@201404z4116.100N/00134.100ErMMDVM DMO 224.9400/222.3400 CC1
20201020123344EA7JIB>APRS,TCPIP*,qAS,BM2142POS:@201433z4116.100N/00134.100ErMMDVM DMO 224.9400/222.3400 CC1
20201020130410EA7JIB>APRS,TCPIP*,qAS,BM2142POS:@201504z4116.100N/00134.100ErMMDVM DMO 224.9400/222.3400 CC1
20201020133512EA7JIB>APRS,TCPIP*,qAS,BM2142POS:@201535z4116.100N/00134.100ErMMDVM DMO 224.9400/222.3400 CC1
20201020140358EA7JIB>APRS,TCPIP*,qAS,BM2142POS:@201603z4116.100N/00134.100ErMMDVM DMO 224.9400/222.3400 CC1
20201020143335EA7JIB>APRS,TCPIP*,qAS,BM2142POS:@201633z4116.100N/00134.100ErMMDVM DMO 224.9400/222.3400 CC1
20201020150429EA7JIB>APRS,TCPIP*,qAS,BM2142POS:@201704z4116.100N/00134.100ErMMDVM DMO 224.9400/222.3400 CC1
20201020153341EA7JIB>APRS,TCPIP*,qAS,BM2142POS:@201733z4116.100N/00134.100ErMMDVM DMO 224.9400/222.3400 CC1
20201020163444EA7JIB>APRS,TCPIP*,qAS,BM2142POS:@201834z4116.100N/00134.100ErMMDVM DMO 224.9400/222.3400 CC1
20201020170441EA7JIB>APRS,TCPIP*,qAS,BM2142POS:@201904z4116.100N/00134.100ErMMDVM DMO 224.9400/222.3400 CC1