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
20180524233009PI1VLD>APRS,TCPIP*,qAS,PI1DMR-14:@242330z5132.100N/00412.60ErPHG2160MMDVM 438.2125/430.6125 CC1
20180525000008PI1VLD>APRS,TCPIP*,qAS,PI1DMR-14:@250000z5132.100N/00412.60ErPHG2160MMDVM 438.2125/430.6125 CC1
20180525003008PI1VLD>APRS,TCPIP*,qAS,PI1DMR-14:@250030z5132.100N/00412.60ErPHG2160MMDVM 438.2125/430.6125 CC1
20180525010009PI1VLD>APRS,TCPIP*,qAS,PI1DMR-14:@250100z5132.100N/00412.60ErPHG2160MMDVM 438.2125/430.6125 CC1
20180525013003PI1VLD>APRS,TCPIP*,qAS,PI1DMR-14:@250130z5132.100N/00412.60ErPHG2160MMDVM 438.2125/430.6125 CC1
20180525020013PI1VLD>APRS,TCPIP*,qAS,PI1DMR-14:@250200z5132.100N/00412.60ErPHG2160MMDVM 438.2125/430.6125 CC1
20180525023015PI1VLD>APRS,TCPIP*,qAS,PI1DMR-14:@250230z5132.100N/00412.60ErPHG2160MMDVM 438.2125/430.6125 CC1
20180525033016PI1VLD>APRS,TCPIP*,qAS,PI1DMR-14:@250330z5132.100N/00412.60ErPHG2160MMDVM 438.2125/430.6125 CC1
20180525040017PI1VLD>APRS,TCPIP*,qAS,PI1DMR-14:@250400z5132.100N/00412.60ErPHG2160MMDVM 438.2125/430.6125 CC1
20180525043020PI1VLD>APRS,TCPIP*,qAS,PI1DMR-14:@250430z5132.100N/00412.60ErPHG2160MMDVM 438.2125/430.6125 CC1
20180525050018PI1VLD>APRS,TCPIP*,qAS,PI1DMR-14:@250500z5132.100N/00412.60ErPHG2160MMDVM 438.2125/430.6125 CC1