APRS Packet Errors for KR4PI (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
20181209152201KR4PI>APBM1S,TCPIP*,qAS,N3FE-15:@091522z263513.26N/815023.47E-KR4PI Pi-Star MMDVM hotspot 441.3500/441.3500 CC1
20181209162202KR4PI>APBM1S,TCPIP*,qAS,N3FE-15:@091622z263513.26N/815023.47E-KR4PI Pi-Star MMDVM hotspot 441.3500/441.3500 CC1
20181209165206KR4PI>APBM1S,TCPIP*,qAS,N3FE-15:@091652z263513.26N/815023.47E-KR4PI Pi-Star MMDVM hotspot 441.3500/441.3500 CC1
20181209172230KR4PI>APBM1S,TCPIP*,qAS,N3FE-15:@091722z263513.26N/815023.47E-KR4PI Pi-Star MMDVM hotspot 441.3500/441.3500 CC1
20181209175338KR4PI>APBM1S,TCPIP*,qAS,N3FE-15:@091753z263513.26N/815023.47E-KR4PI Pi-Star MMDVM hotspot 441.3500/441.3500 CC1
20181209182333KR4PI>APBM1S,TCPIP*,qAS,N3FE-15:@091823z263513.26N/815023.47E-KR4PI Pi-Star MMDVM hotspot 441.3500/441.3500 CC1
20181209185311KR4PI>APBM1S,TCPIP*,qAS,N3FE-15:@091853z263513.26N/815023.47E-KR4PI Pi-Star MMDVM hotspot 441.3500/441.3500 CC1
20181209192303KR4PI>APBM1S,TCPIP*,qAS,N3FE-15:@091923z263513.26N/815023.47E-KR4PI Pi-Star MMDVM hotspot 441.3500/441.3500 CC1
20181209205426KR4PI>APBM1S,TCPIP*,qAS,N3FE-15:@092054z263513.26N/815023.47E-KR4PI Pi-Star MMDVM hotspot 441.3500/441.3500 CC1