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
20171211131718JJ2YQH-P>APDVAP,TCPIP*,qAC,JJ2YQH-PS:!0000.00ND00000.00E&DV_AP D-PRS -> APRS
20171211134718JJ2YQH-P>APDVAP,TCPIP*,qAC,JJ2YQH-PS:!0000.00ND00000.00E&DV_AP D-PRS -> APRS
20171211141718JJ2YQH-P>APDVAP,TCPIP*,qAC,JJ2YQH-PS:!0000.00ND00000.00E&DV_AP D-PRS -> APRS
20171211144718JJ2YQH-P>APDVAP,TCPIP*,qAC,JJ2YQH-PS:!0000.00ND00000.00E&DV_AP D-PRS -> APRS
20171211151718JJ2YQH-P>APDVAP,TCPIP*,qAC,JJ2YQH-PS:!0000.00ND00000.00E&DV_AP D-PRS -> APRS
20171211154718JJ2YQH-P>APDVAP,TCPIP*,qAC,JJ2YQH-PS:!0000.00ND00000.00E&DV_AP D-PRS -> APRS
20171211161718JJ2YQH-P>APDVAP,TCPIP*,qAC,JJ2YQH-PS:!0000.00ND00000.00E&DV_AP D-PRS -> APRS
20171211164718JJ2YQH-P>APDVAP,TCPIP*,qAC,JJ2YQH-PS:!0000.00ND00000.00E&DV_AP D-PRS -> APRS
20171211171718JJ2YQH-P>APDVAP,TCPIP*,qAC,JJ2YQH-PS:!0000.00ND00000.00E&DV_AP D-PRS -> APRS
20171211174718JJ2YQH-P>APDVAP,TCPIP*,qAC,JJ2YQH-PS:!0000.00ND00000.00E&DV_AP D-PRS -> APRS
20171211181718JJ2YQH-P>APDVAP,TCPIP*,qAC,JJ2YQH-PS:!0000.00ND00000.00E&DV_AP D-PRS -> APRS
20171211184718JJ2YQH-P>APDVAP,TCPIP*,qAC,JJ2YQH-PS:!0000.00ND00000.00E&DV_AP D-PRS -> APRS