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
20180323203103CWAringo>APRS,TCPXX*,qAX,CWOP-5:@232031z42 33.360N/13 15.982E_293/000g000t029r000p000h74b09903.wview_5_20_2
20180323204103CWAringo>APRS,TCPXX*,qAX,CWOP-7:@232041z42 33.360N/13 15.982E_293/000g001t029r000p000h74b09906.wview_5_20_2
20180323204606CWAringo>APRS,TCPXX*,qAX,CWOP-5:@232046z42 33.360N/13 15.982E_293/000g000t029r000p000h74b09906.wview_5_20_2
20180323205103CWAringo>APRS,TCPXX*,qAX,CWOP-7:@232051z42 33.360N/13 15.982E_293/000g000t029r000p000h74b09904.wview_5_20_2
20180323205603CWAringo>APRS,TCPXX*,qAX,CWOP-3:@232056z42 33.360N/13 15.982E_293/000g000t029r000p000h74b09906.wview_5_20_2
20180323210103CWAringo>APRS,TCPXX*,qAX,CWOP-3:@232101z42 33.360N/13 15.982E_293/000g001t029r000p000h74b09907.wview_5_20_2
20180323210606CWAringo>APRS,TCPXX*,qAX,CWOP-5:@232106z42 33.360N/13 15.982E_293/000g000t029r000p000h75b09907.wview_5_20_2
20180323211603CWAringo>APRS,TCPXX*,qAX,CWOP-7:@232116z42 33.360N/13 15.982E_293/000g000t029r000p000h75b09907.wview_5_20_2