APRS Packet Errors for PA3DZW (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
20180419093011PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@190930z5132.100N/00506.60EQPHG0300openSPOT 430.9250/430.9250 CC1
20180419093016PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@190930z5132.100N/00506.60EQPHG0300openSPOT 438.5250/438.5250 CC1
20180419100013PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@191000z5132.100N/00506.60EQPHG0300openSPOT 430.9250/430.9250 CC1
20180419100018PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@191000z5132.100N/00506.60EQPHG0300openSPOT 438.5250/438.5250 CC1
20180419103012PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@191030z5132.100N/00506.60EQPHG0300openSPOT 430.9250/430.9250 CC1
20180419103017PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@191030z5132.100N/00506.60EQPHG0300openSPOT 438.5250/438.5250 CC1
20180419110014PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@191100z5132.100N/00506.60EQPHG0300openSPOT 430.9250/430.9250 CC1
20180419110019PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@191100z5132.100N/00506.60EQPHG0300openSPOT 438.5250/438.5250 CC1
20180419113013PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@191130z5132.100N/00506.60EQPHG0300openSPOT 430.9250/430.9250 CC1
20180419113017PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@191130z5132.100N/00506.60EQPHG0300openSPOT 438.5250/438.5250 CC1
20180419120013PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@191200z5132.100N/00506.60EQPHG0300openSPOT 430.9250/430.9250 CC1
20180419120017PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@191200z5132.100N/00506.60EQPHG0300openSPOT 438.5250/438.5250 CC1
20180419123013PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@191230z5132.100N/00506.60EQPHG0300openSPOT 430.9250/430.9250 CC1
20180419123017PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@191230z5132.100N/00506.60EQPHG0300openSPOT 438.5250/438.5250 CC1
20180419130016PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@191300z5132.100N/00506.60EQPHG0300openSPOT 430.9250/430.9250 CC1
20180419130020PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@191300z5132.100N/00506.60EQPHG0300openSPOT 438.5250/438.5250 CC1
20180419133015PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@191330z5132.100N/00506.60EQPHG0300openSPOT 430.9250/430.9250 CC1
20180419133020PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@191330z5132.100N/00506.60EQPHG0300openSPOT 438.5250/438.5250 CC1
20180419140013PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@191400z5132.100N/00506.60EQPHG0300openSPOT 430.9250/430.9250 CC1
20180419140017PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@191400z5132.100N/00506.60EQPHG0300openSPOT 438.5250/438.5250 CC1
20180419143041PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@191430z5132.100N/00506.60EQPHG0300openSPOT 438.5250/438.5250 CC1
20180419143043PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@191430z5132.100N/00506.60EQPHG0300openSPOT 430.9250/430.9250 CC1
20180419150039PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@191500z5132.100N/00506.60EQPHG0300openSPOT 438.5250/438.5250 CC1
20180419150042PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@191500z5132.100N/00506.60EQPHG0300openSPOT 430.9250/430.9250 CC1