APRS Packet Errors for EA4LO (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
20180721040211EA4LO>APRS,TCPIP*,qAS,BM214:@210602z4034.100N/03310.00WQPHG0800MMDVM DVMega 438.4000/438.4000 CC1
20180721043203EA4LO>APRS,TCPIP*,qAS,BM214:@210632z4034.100N/03310.00WQPHG0800MMDVM DVMega 438.4000/438.4000 CC1
20180721050210EA4LO>APRS,TCPIP*,qAS,BM214:@210702z4034.100N/03310.00WQPHG0800MMDVM DVMega 438.4000/438.4000 CC1
20180721053207EA4LO>APRS,TCPIP*,qAS,BM214:@210732z4034.100N/03310.00WQPHG0800MMDVM DVMega 438.4000/438.4000 CC1
20180721060224EA4LO>APRS,TCPIP*,qAS,BM214:@210802z4034.100N/03310.00WQPHG0800MMDVM DVMega 438.4000/438.4000 CC1
20180721063208EA4LO>APRS,TCPIP*,qAS,BM214:@210832z4034.100N/03310.00WQPHG0800MMDVM DVMega 438.4000/438.4000 CC1
20180721070218EA4LO>APRS,TCPIP*,qAS,BM214:@210902z4034.100N/03310.00WQPHG0800MMDVM DVMega 438.4000/438.4000 CC1
20180721080050EA4LO>APRS,TCPIP*,qAS,BM214:@211000z4034.100N/03310.00WQPHG0800MMDVM DVMega 438.4000/438.4000 CC1
20180721083055EA4LO>APRS,TCPIP*,qAS,BM214:@211030z4034.100N/03310.00WQPHG0800MMDVM DVMega 438.4000/438.4000 CC1
20180721090108EA4LO>APRS,TCPIP*,qAS,BM214:@211101z4034.100N/03310.00WQPHG0800MMDVM DVMega 438.4000/438.4000 CC1
20180721093120EA4LO>APRS,TCPIP*,qAS,BM214:@211131z4034.100N/03310.00WQPHG0800MMDVM DVMega 438.4000/438.4000 CC1