APRS Packet Errors for SR3WXA (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
20180520140300SR3WXA>APTT4,WIDE2-2,qAR,SP3WBX:=5224.78N/0165
20180520140711SR3WXA>APTT4,SR3DPN*,WIDE2-1,qAR,SP3WBX:@201402z5224.78N/01653.52E_049/00
20180520144208SR3WXA>APTT4,WIDE2-2,qAR,SP3WBX:@2014P000h33b10253L506.DsVP
20180520155406SR3WXA>APTT4,WIDE2-2,qAR,SP3WBX:@201549z5224.78N/01653.520248L339.DsVP
20180520161908SR3WXA>APTT4,SR3DPN,SR3NPB,WIDE2*,qAR,SP3WBX:@201614z5224p000P000h34b10247L278.DsVP
20180520161913SR3WXA>APTT4,WIDE2-2,qAR,SP3WBX:@201614z5224.7.78N/01653.52E_023/005g012t069r000
20180520162707SR3WXA>APTT4,WIDE2-2,qAR,SP3WBX:=5224.p. SP3LYR A=279
20180520164910SR3WXA>APTT4,SR3DPN,SR3NPB,WIDE2*,qAR,SP3WBX:@201644z5224.78N/01653
20180520175345SR3WXA>APTT4,WIDE2-2,qAR,SP3WBX:@201749z5224.78N/01653.5
20180520175408SR3WXA>APTT4,SR3NWY*,WIDE2-1,qAR,SP3WBX:@201749z5224.78N/01
20180520182826SR3WXA>APTT4,WIDE2-2,qAR,SP3WBX:@2018@e>Davis Vantage Pro2 Plus & TT4 Alpha 13.8V
20180520194226SR3WXA>APTT4,SR3NWY*,WIDE2-1,qAR,SP3WBX:@201937z5000p000P000h48b10252L000.DsVP