APRS Packet Errors for JL3ZEO (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
20180620040142JL3ZEO>APRS,TCPIP*,qAS,PI1DMR-14:@200401z3432.100S/13542.60WQWindows:BlueDV 438.5000/438.5000 CC1
20180620043143JL3ZEO>APRS,TCPIP*,qAS,PI1DMR-14:@200431z3432.100S/13542.60WQWindows:BlueDV 438.5000/438.5000 CC1
20180620050147JL3ZEO>APRS,TCPIP*,qAS,PI1DMR-14:@200501z3432.100S/13542.60WQWindows:BlueDV 438.5000/438.5000 CC1
20180620053156JL3ZEO>APRS,TCPIP*,qAS,PI1DMR-14:@200531z3432.100S/13542.60WQWindows:BlueDV 438.5000/438.5000 CC1
20180620060145JL3ZEO>APRS,TCPIP*,qAS,PI1DMR-14:@200601z3432.100S/13542.60WQWindows:BlueDV 438.5000/438.5000 CC1
20180620063152JL3ZEO>APRS,TCPIP*,qAS,PI1DMR-14:@200631z3432.100S/13542.60WQWindows:BlueDV 438.5000/438.5000 CC1
20180620070150JL3ZEO>APRS,TCPIP*,qAS,PI1DMR-14:@200701z3432.100S/13542.60WQWindows:BlueDV 438.5000/438.5000 CC1
20180620073147JL3ZEO>APRS,TCPIP*,qAS,PI1DMR-14:@200731z3432.100S/13542.60WQWindows:BlueDV 438.5000/438.5000 CC1
20180620083159JL3ZEO>APRS,TCPIP*,qAS,PI1DMR-14:@200831z3432.100S/13542.60WQWindows:BlueDV 438.5000/438.5000 CC1
20180620090158JL3ZEO>APRS,TCPIP*,qAS,PI1DMR-14:@200901z3432.100S/13542.60WQWindows:BlueDV 438.5000/438.5000 CC1
20180620093150JL3ZEO>APRS,TCPIP*,qAS,PI1DMR-14:@200931z3432.100S/13542.60WQWindows:BlueDV 438.5000/438.5000 CC1