APRS Packet Errors for DF0MOT (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
20170819145810DF0MOT>APZCCS,TCPIP*,qAU,DMRAPRS:;DO7FE-9 *191458z5010.35N/ 0>HyteraDMR APRS-Server
20170819150015DF0MOT>APZCCS,TCPIP*,qAU,DMRAPRS:;DO7FE-9 *191500z5X08.03N/00858.70E>HyteraDMR APRS-Server
20170819153337DF0MOT>APZCCS,TCPIP*,qAU,DMRAPRS:;DB1FE-9 *191533z5011.14N/ 00900.E>HyteraDMR APRS-Server
20170819153351DF0MOT>APZCCS,TCPIP*,qAU,DMRAPRS:;DB1FE-9 *191533z5010.97N/ 00900.4E>HyteraDMR APRS-Server
20170819153515DF0MOT>APZCCS,TCPIP*,qAU,DMRAPRS:;DB1FE-9 *191535z5010.82N/00901.3E>HyteraDMR APRS-Server
20170819155756DF0MOT>APZCCS,TCPIP*,qAU,DMRAPRS:;DB1FE-9 *191557z5007.47N/ 00857. E>HyteraDMR APRS-Server
20170819155814DF0MOT>APZCCS,TCPIP*,qAU,DMRAPRS:;DB1FE-9 *191558z5007.29N/00857.19>HyteraDMR APRS-Server
20170819171016DF0MOT>APZCCS,TCPIP*,qAU,DMRAPRS:;DL6SIX-7 *191710z4953.91N/00831.8E[HyteraDMR APRS-Server
20170819171216DF0MOT>APZCCS,TCPIP*,qAU,DMRAPRS:;DL6SIX-7 *191712z 494N/00830.23E[HyteraDMR APRS-Server
20170819181303DF0MOT>APZCCS,TCPIP*,qAU,DMRAPRS:;DO7FE-9 *191813z5005.74N/00855.51>HyteraDMR APRS-Server