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
20180120030010PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@200300z5132.100N/00506.60EQPHG0300openSPOT 430.9250/430.9250 CC1
20180120030013PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@200300z5132.100N/00506.60EQPHG0300openSPOT 438.5250/438.5250 CC1
20180120033011PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@200330z5132.100N/00506.60EQPHG0300openSPOT 430.9250/430.9250 CC1
20180120033014PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@200330z5132.100N/00506.60EQPHG0300openSPOT 438.5250/438.5250 CC1
20180120040011PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@200400z5132.100N/00506.60EQPHG0300openSPOT 430.9250/430.9250 CC1
20180120040014PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@200400z5132.100N/00506.60EQPHG0300openSPOT 438.5250/438.5250 CC1
20180120043010PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@200430z5132.100N/00506.60EQPHG0300openSPOT 430.9250/430.9250 CC1
20180120043014PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@200430z5132.100N/00506.60EQPHG0300openSPOT 438.5250/438.5250 CC1
20180120050010PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@200500z5132.100N/00506.60EQPHG0300openSPOT 430.9250/430.9250 CC1
20180120050014PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@200500z5132.100N/00506.60EQPHG0300openSPOT 438.5250/438.5250 CC1
20180120053011PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@200530z5132.100N/00506.60EQPHG0300openSPOT 430.9250/430.9250 CC1
20180120053014PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@200530z5132.100N/00506.60EQPHG0300openSPOT 438.5250/438.5250 CC1
20180120060011PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@200600z5132.100N/00506.60EQPHG0300openSPOT 430.9250/430.9250 CC1
20180120060014PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@200600z5132.100N/00506.60EQPHG0300openSPOT 438.5250/438.5250 CC1
20180120063010PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@200630z5132.100N/00506.60EQPHG0300openSPOT 430.9250/430.9250 CC1
20180120063013PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@200630z5132.100N/00506.60EQPHG0300openSPOT 438.5250/438.5250 CC1
20180120070011PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@200700z5132.100N/00506.60EQPHG0300openSPOT 430.9250/430.9250 CC1
20180120070014PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@200700z5132.100N/00506.60EQPHG0300openSPOT 438.5250/438.5250 CC1
20180120073012PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@200730z5132.100N/00506.60EQPHG0300openSPOT 430.9250/430.9250 CC1
20180120073015PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@200730z5132.100N/00506.60EQPHG0300openSPOT 438.5250/438.5250 CC1
20180120080011PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@200800z5132.100N/00506.60EQPHG0300openSPOT 430.9250/430.9250 CC1
20180120080015PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@200800z5132.100N/00506.60EQPHG0300openSPOT 438.5250/438.5250 CC1
20180120083011PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@200830z5132.100N/00506.60EQPHG0300openSPOT 430.9250/430.9250 CC1
20180120083014PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@200830z5132.100N/00506.60EQPHG0300openSPOT 438.5250/438.5250 CC1