APRS Packet Errors for SV3DVW-9 (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
20180221175745SV3DVW-9>APT311,WIDE2-2,qAR,SV3AQO-10:!0000.00N/00000.00E>000/000/A=000000/QRV 145225---RU84--RU85
20180221175844SV3DVW-9>APT311,WIDE2-2,qAR,SV3AQO-10:!0000.00N/00000.00E>000/000/A=000000
20180221180043SV3DVW-9>APT311,WIDE2-2,qAR,SV3AQO-10:!0000.00N/00000.00E>000/000/A=000000/QRV 145225---RU84--RU85
20180221180142SV3DVW-9>APT311,WIDE2-2,qAR,SV3AQO-10:!0000.00N/00000.00E>000/000/A=000000
20180221180341SV3DVW-9>APT311,WIDE2-2,qAR,SV3AQO-10:!0000.00N/00000.00E>000/000/A=000000/QRV 145225---RU84--RU85
20180221180440SV3DVW-9>APT311,WIDE2-2,qAR,SV3AQO-10:!0000.00N/00000.00E>000/000/A=000000
20180221180541SV3DVW-9>APT311,J43VAE*,WIDE2-1,qAR,SV3AQO-10:!0000.00N/00000.00E>000/000/A=000000
20180221180639SV3DVW-9>APT311,WIDE2-2,qAR,SV3AQO-10:!0000.00N/00000.00E>000/000/A=000000/QRV 145225---RU84--RU85
20180221180738SV3DVW-9>APT311,WIDE2-2,qAR,SV3AQO-10:!0000.00N/00000.00E>000/000/A=000000
20180221180839SV3DVW-9>APT311,J43VAE*,WIDE2-1,qAR,SV3AQO-10:!0000.00N/00000.00E>000/000/A=000000