APRS Packet Errors for PI1VLD (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
20180218220011PI1VLD>APRS,TCPIP*,qAS,PI1DMR-14:@182200z5132.100N/00412.60ErMMDVM 438.2125/430.6125 CC1
20180218223010PI1VLD>APRS,TCPIP*,qAS,PI1DMR-14:@182230z5132.100N/00412.60ErMMDVM 438.2125/430.6125 CC1
20180218230010PI1VLD>APRS,TCPIP*,qAS,PI1DMR-14:@182300z5132.100N/00412.60ErMMDVM 438.2125/430.6125 CC1
20180218233010PI1VLD>APRS,TCPIP*,qAS,PI1DMR-14:@182330z5132.100N/00412.60ErMMDVM 438.2125/430.6125 CC1
20180219000011PI1VLD>APRS,TCPIP*,qAS,PI1DMR-14:@190000z5132.100N/00412.60ErMMDVM 438.2125/430.6125 CC1
20180219003010PI1VLD>APRS,TCPIP*,qAS,PI1DMR-14:@190030z5132.100N/00412.60ErMMDVM 438.2125/430.6125 CC1
20180219010015PI1VLD>APRS,TCPIP*,qAS,PI1DMR-14:@190100z5132.100N/00412.60ErMMDVM 438.2125/430.6125 CC1
20180219013010PI1VLD>APRS,TCPIP*,qAS,PI1DMR-14:@190130z5132.100N/00412.60ErMMDVM 438.2125/430.6125 CC1
20180219020010PI1VLD>APRS,TCPIP*,qAS,PI1DMR-14:@190200z5132.100N/00412.60ErMMDVM 438.2125/430.6125 CC1
20180219023011PI1VLD>APRS,TCPIP*,qAS,PI1DMR-14:@190230z5132.100N/00412.60ErMMDVM 438.2125/430.6125 CC1
20180219030005PI1VLD>APRS,TCPIP*,qAS,PI1DMR-14:@190300z5132.100N/00412.60ErMMDVM 438.2125/430.6125 CC1
20180219033005PI1VLD>APRS,TCPIP*,qAS,PI1DMR-14:@190330z5132.100N/00412.60ErMMDVM 438.2125/430.6125 CC1