APRS Packet Errors for CWAringo (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
20180316223534CWAringo>APRS,TCPXX*,qAX,CWOP-7:@162236z42 33.360N/13 15.982E_293/000g000t042r000p014h83b09953.wview_5_20_2
20180316224534CWAringo>APRS,TCPXX*,qAX,CWOP-5:@162246z42 33.360N/13 15.982E_293/001g002t041r000p014h85b09953.wview_5_20_2
20180316225037CWAringo>APRS,TCPXX*,qAX,CWOP-3:@162251z42 33.360N/13 15.982E_293/002g002t041r000p012h85b09951.wview_5_20_2
20180316225534CWAringo>APRS,TCPXX*,qAX,CWOP-7:@162256z42 33.360N/13 15.982E_293/000g003t041r000p012h86b09950.wview_5_20_2
20180316230034CWAringo>APRS,TCPXX*,qAX,CWOP-5:@162301z42 33.360N/13 15.982E_293/000g002t041r000p012h86b09950.wview_5_20_2
20180316232033CWAringo>APRS,TCPXX*,qAX,CWOP-5:@162321z42 33.360N/13 15.982E_338/000g002t041r000p010h86b09947.wview_5_20_2