APRS Packet Errors for EA7HU (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
20180817190301EA7HU>APRS,TCPIP*,qAS,BM214:@172102z3750.100N/00442.00WQMMDVM DVMega 430.4375/430.4375 CC1
20180817193316EA7HU>APRS,TCPIP*,qAS,BM214:@172133z3750.100N/00442.00WQMMDVM DVMega 430.4375/430.4375 CC1
20180817200246EA7HU>APRS,TCPIP*,qAS,BM214:@172202z3750.100N/00442.00WQMMDVM DVMega 430.4375/430.4375 CC1
20180817203243EA7HU>APRS,TCPIP*,qAS,BM214:@172232z3750.100N/00442.00WQMMDVM DVMega 430.4375/430.4375 CC1
20180817210245EA7HU>APRS,TCPIP*,qAS,BM214:@172302z3750.100N/00442.00WQMMDVM DVMega 430.4375/430.4375 CC1
20180817213244EA7HU>APRS,TCPIP*,qAS,BM214:@172332z3750.100N/00442.00WQMMDVM DVMega 430.4375/430.4375 CC1
20180817220233EA7HU>APRS,TCPIP*,qAS,BM214:@180002z3750.100N/00442.00WQMMDVM DVMega 430.4375/430.4375 CC1
20180817223227EA7HU>APRS,TCPIP*,qAS,BM214:@180032z3750.100N/00442.00WQMMDVM DVMega 430.4375/430.4375 CC1
20180817230239EA7HU>APRS,TCPIP*,qAS,BM214:@180102z3750.100N/00442.00WQMMDVM DVMega 430.4375/430.4375 CC1
20180817233214EA7HU>APRS,TCPIP*,qAS,BM214:@180132z3750.100N/00442.00WQMMDVM DVMega 430.4375/430.4375 CC1
20180818000215EA7HU>APRS,TCPIP*,qAS,BM214:@180202z3750.100N/00442.00WQMMDVM DVMega 430.4375/430.4375 CC1
20180818003209EA7HU>APRS,TCPIP*,qAS,BM214:@180232z3750.100N/00442.00WQMMDVM DVMega 430.4375/430.4375 CC1