APRS Packet Errors for LU2WBA (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
20170820094255LU2WBA>APU25N,TCPIP*,qAC,CX2SA-S1:=4554.84S/06733.17WS!4554.0000S/06730.17Wy/Fran UiNew
20170820101254LU2WBA>APU25N,TCPIP*,qAC,CX2SA-S1:=4554.84S/06733.17WS!4554.0000S/06730.17Wy/Fran UiNew
20170820104255LU2WBA>APU25N,TCPIP*,qAC,CX2SA-S1:=4554.84S/06733.17WS!4554.0000S/06730.17Wy/Fran UiNew
20170820111254LU2WBA>APU25N,TCPIP*,qAC,CX2SA-S1:=4554.84S/06733.17WS!4554.0000S/06730.17Wy/Fran UiNew
20170820114254LU2WBA>APU25N,TCPIP*,qAC,CX2SA-S1:=4554.84S/06733.17WS!4554.0000S/06730.17Wy/Fran UiNew
20170820121255LU2WBA>APU25N,TCPIP*,qAC,CX2SA-S1:=4554.84S/06733.17WS!4554.0000S/06730.17Wy/Fran UiNew
20170820124255LU2WBA>APU25N,TCPIP*,qAC,CX2SA-S1:=4554.84S/06733.17WS!4554.0000S/06730.17Wy/Fran UiNew
20170820131255LU2WBA>APU25N,TCPIP*,qAC,CX2SA-S1:=4554.84S/06733.17WS!4554.0000S/06730.17Wy/Fran UiNew
20170820134254LU2WBA>APU25N,TCPIP*,qAC,CX2SA-S1:=4554.84S/06733.17WS!4554.0000S/06730.17Wy/Fran UiNew
20170820141253LU2WBA>APU25N,TCPIP*,qAC,CX2SA-S1:=4554.84S/06733.17WS!4554.0000S/06730.17Wy/Fran UiNew
20170820144255LU2WBA>APU25N,TCPIP*,qAC,CX2SA-S1:=4554.84S/06733.17WS!4554.0000S/06730.17Wy/Fran UiNew
20170820151254LU2WBA>APU25N,TCPIP*,qAC,CX2SA-S1:=4554.84S/06733.17WS!4554.0000S/06730.17Wy/Fran UiNew