APRS Packet Errors for OD5RW-D (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
20170322161420OD5RW-D>APWW10,TCPIP*,qAC,T2MEXICO:@162004h0000.00N/00000.00ErPHG3090Voice 144.600 Mhz
20170322164420OD5RW-D>APWW10,TCPIP*,qAC,T2MEXICO:@165004h0000.00N/00000.00ErPHG3090Voice 144.600 Mhz
20170322171420OD5RW-D>APWW10,TCPIP*,qAC,T2MEXICO:@172004h0000.00N/00000.00ErPHG3090Voice 144.600 Mhz
20170322174420OD5RW-D>APWW10,TCPIP*,qAC,T2MEXICO:@175004h0000.00N/00000.00ErPHG3090Voice 144.600 Mhz
20170322181420OD5RW-D>APWW10,TCPIP*,qAC,T2MEXICO:@182004h0000.00N/00000.00ErPHG3090Voice 144.600 Mhz
20170322184420OD5RW-D>APWW10,TCPIP*,qAC,T2MEXICO:@185004h0000.00N/00000.00ErPHG3090Voice 144.600 Mhz
20170322191420OD5RW-D>APWW10,TCPIP*,qAC,T2MEXICO:@192004h0000.00N/00000.00ErPHG3090Voice 144.600 Mhz
20170322194420OD5RW-D>APWW10,TCPIP*,qAC,T2MEXICO:@195004h0000.00N/00000.00ErPHG3090Voice 144.600 Mhz
20170322201420OD5RW-D>APWW10,TCPIP*,qAC,T2MEXICO:@202004h0000.00N/00000.00ErPHG3090Voice 144.600 Mhz
20170322204420OD5RW-D>APWW10,TCPIP*,qAC,T2MEXICO:@205004h0000.00N/00000.00ErPHG3090Voice 144.600 Mhz
20170322211420OD5RW-D>APWW10,TCPIP*,qAC,T2MEXICO:@212004h0000.00N/00000.00ErPHG3090Voice 144.600 Mhz
20170322214420OD5RW-D>APWW10,TCPIP*,qAC,T2MEXICO:@215004h0000.00N/00000.00ErPHG3090Voice 144.600 Mhz