APRS Packet Errors for LU9EV-2 (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
20171017000622LU9EV-2>BEACON,WIDE2-2,qAR,LW1DXP-10:!3832.88S/05907.840SI05829.00W& U=11.4V. Igate APRS UHF Celina 430930KHz
20171017002131LU9EV-2>BEACON,WIDE2-2,qAR,LW1DXP-10:!3832.88S/05907.840P000b09998h47eMB34
20171017010208LU9EV-2>APN383,WIDE2-2,qAR,LW1DXP-10:!3832Digipiter 144.930 Mhz Radio Club Necochea
20171017012122LU9EV-2>APN383,WIDE2-1,qAR,LW1DXP-10:!3832.88S/059127.90W-San Carlos de Bariloche
20171017015243LU9EV-2>APN383,WIDE2-2,qAR,LW1DXP-10:!38370152z3405.68S/06137.72W_000/004g007t065r000p000P000b10075h64eMB34