APRS Packet Errors for EB5AYE (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
20200920083021	EB5AYE>APRS,TCPIP*,qAS,BM2142POS:@201030z3943.100N/00027.59WQMMDVM DMO 433.3400/433.3400 CC1
20200920090022	EB5AYE>APRS,TCPIP*,qAS,BM2142POS:@201100z3943.100N/00027.59WQMMDVM DMO 433.3400/433.3400 CC1
20200920093037	EB5AYE>APRS,TCPIP*,qAS,BM2142POS:@201130z3943.100N/00027.59WQMMDVM DMO 433.3400/433.3400 CC1
20200920100055	EB5AYE>APRS,TCPIP*,qAS,BM2142POS:@201200z3943.100N/00027.59WQMMDVM DMO 433.3400/433.3400 CC1
20200920103052	EB5AYE>APRS,TCPIP*,qAS,BM2142POS:@201230z3943.100N/00027.59WQMMDVM DMO 433.3400/433.3400 CC1
20200920110050	EB5AYE>APRS,TCPIP*,qAS,BM2142POS:@201300z3943.100N/00027.59WQMMDVM DMO 433.3400/433.3400 CC1
20200920113100	EB5AYE>APRS,TCPIP*,qAS,BM2142POS:@201330z3943.100N/00027.59WQMMDVM DMO 433.3400/433.3400 CC1
20200920120053	EB5AYE>APRS,TCPIP*,qAS,BM2142POS:@201400z3943.100N/00027.59WQMMDVM DMO 433.3400/433.3400 CC1
20200920123117	EB5AYE>APRS,TCPIP*,qAS,BM2142POS:@201431z3943.100N/00027.59WQMMDVM DMO 433.3400/433.3400 CC1
20200920130059	EB5AYE>APRS,TCPIP*,qAS,BM2142POS:@201500z3943.100N/00027.59WQMMDVM DMO 433.3400/433.3400 CC1