APRS Packet Errors for F5ZMB (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
20180618193153F5ZMB>APRS,TCPIP*,qAS,PI1DMR-14:@181931z5017.100N/00355.34ErPHG4000MMDVM 439.5000/430.1000 CC1
20180618200147F5ZMB>APRS,TCPIP*,qAS,PI1DMR-14:@182001z5017.100N/00355.34ErPHG4000MMDVM 439.5000/430.1000 CC1
20180618203146F5ZMB>APRS,TCPIP*,qAS,PI1DMR-14:@182031z5017.100N/00355.34ErPHG4000MMDVM 439.5000/430.1000 CC1
20180618210019F5ZMB>APRS,TCPIP*,qAS,PI1DMR-14:@182100z5017.100N/00355.34ErPHG4000MMDVM 439.5000/430.1000 CC1
20180618213019F5ZMB>APRS,TCPIP*,qAS,PI1DMR-14:@182130z5017.100N/00355.34ErPHG4000MMDVM 439.5000/430.1000 CC1
20180618220020F5ZMB>APRS,TCPIP*,qAS,PI1DMR-14:@182200z5017.100N/00355.34ErPHG4000MMDVM 439.5000/430.1000 CC1
20180618223021F5ZMB>APRS,TCPIP*,qAS,PI1DMR-14:@182230z5017.100N/00355.34ErPHG4000MMDVM 439.5000/430.1000 CC1
20180618230022F5ZMB>APRS,TCPIP*,qAS,PI1DMR-14:@182300z5017.100N/00355.34ErPHG4000MMDVM 439.5000/430.1000 CC1
20180618233021F5ZMB>APRS,TCPIP*,qAS,PI1DMR-14:@182330z5017.100N/00355.34ErPHG4000MMDVM 439.5000/430.1000 CC1
20180619000022F5ZMB>APRS,TCPIP*,qAS,PI1DMR-14:@190000z5017.100N/00355.34ErPHG4000MMDVM 439.5000/430.1000 CC1