APRS Packet Errors for JJ2YQH-P (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
20171218144711JJ2YQH-P>APDVAP,TCPIP*,qAC,JJ2YQH-PS:!0000.00ND00000.00E&DV_AP D-PRS -> APRS
20171218151711JJ2YQH-P>APDVAP,TCPIP*,qAC,JJ2YQH-PS:!0000.00ND00000.00E&DV_AP D-PRS -> APRS
20171218154711JJ2YQH-P>APDVAP,TCPIP*,qAC,JJ2YQH-PS:!0000.00ND00000.00E&DV_AP D-PRS -> APRS
20171218161711JJ2YQH-P>APDVAP,TCPIP*,qAC,JJ2YQH-PS:!0000.00ND00000.00E&DV_AP D-PRS -> APRS
20171218164711JJ2YQH-P>APDVAP,TCPIP*,qAC,JJ2YQH-PS:!0000.00ND00000.00E&DV_AP D-PRS -> APRS
20171218171711JJ2YQH-P>APDVAP,TCPIP*,qAC,JJ2YQH-PS:!0000.00ND00000.00E&DV_AP D-PRS -> APRS
20171218174711JJ2YQH-P>APDVAP,TCPIP*,qAC,JJ2YQH-PS:!0000.00ND00000.00E&DV_AP D-PRS -> APRS
20171218181711JJ2YQH-P>APDVAP,TCPIP*,qAC,JJ2YQH-PS:!0000.00ND00000.00E&DV_AP D-PRS -> APRS
20171218184711JJ2YQH-P>APDVAP,TCPIP*,qAC,JJ2YQH-PS:!0000.00ND00000.00E&DV_AP D-PRS -> APRS
20171218191711JJ2YQH-P>APDVAP,TCPIP*,qAC,JJ2YQH-PS:!0000.00ND00000.00E&DV_AP D-PRS -> APRS
20171218194711JJ2YQH-P>APDVAP,TCPIP*,qAC,JJ2YQH-PS:!0000.00ND00000.00E&DV_AP D-PRS -> APRS
20171218201711JJ2YQH-P>APDVAP,TCPIP*,qAC,JJ2YQH-PS:!0000.00ND00000.00E&DV_AP D-PRS -> APRS