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
20180420120040PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@201200z5132.100N/00506.60EQPHG0300openSPOT 438.5250/438.5250 CC1
20180420120043PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@201200z5132.100N/00506.60EQPHG0300openSPOT 430.9250/430.9250 CC1
20180420123034PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@201230z5132.100N/00506.60EQPHG0300openSPOT 438.5250/438.5250 CC1
20180420123037PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@201230z5132.100N/00506.60EQPHG0300openSPOT 430.9250/430.9250 CC1
20180420130035PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@201300z5132.100N/00506.60EQPHG0300openSPOT 438.5250/438.5250 CC1
20180420130038PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@201300z5132.100N/00506.60EQPHG0300openSPOT 430.9250/430.9250 CC1
20180420133035PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@201330z5132.100N/00506.60EQPHG0300openSPOT 438.5250/438.5250 CC1
20180420133038PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@201330z5132.100N/00506.60EQPHG0300openSPOT 430.9250/430.9250 CC1
20180420140036PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@201400z5132.100N/00506.60EQPHG0300openSPOT 438.5250/438.5250 CC1
20180420140039PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@201400z5132.100N/00506.60EQPHG0300openSPOT 430.9250/430.9250 CC1
20180420143042PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@201430z5132.100N/00506.60EQPHG0300openSPOT 438.5250/438.5250 CC1
20180420143046PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@201430z5132.100N/00506.60EQPHG0300openSPOT 430.9250/430.9250 CC1
20180420150039PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@201500z5132.100N/00506.60EQPHG0300openSPOT 438.5250/438.5250 CC1
20180420150043PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@201500z5132.100N/00506.60EQPHG0300openSPOT 430.9250/430.9250 CC1
20180420153042PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@201530z5132.100N/00506.60EQPHG0300openSPOT 438.5250/438.5250 CC1
20180420153046PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@201530z5132.100N/00506.60EQPHG0300openSPOT 430.9250/430.9250 CC1
20180420160039PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@201600z5132.100N/00506.60EQPHG0300openSPOT 438.5250/438.5250 CC1
20180420160043PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@201600z5132.100N/00506.60EQPHG0300openSPOT 430.9250/430.9250 CC1
20180420163037PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@201630z5132.100N/00506.60EQPHG0300openSPOT 438.5250/438.5250 CC1
20180420163040PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@201630z5132.100N/00506.60EQPHG0300openSPOT 430.9250/430.9250 CC1
20180420170036PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@201700z5132.100N/00506.60EQPHG0300openSPOT 438.5250/438.5250 CC1
20180420170040PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@201700z5132.100N/00506.60EQPHG0300openSPOT 430.9250/430.9250 CC1
20180420173037PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@201730z5132.100N/00506.60EQPHG0300openSPOT 438.5250/438.5250 CC1
20180420173040PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@201730z5132.100N/00506.60EQPHG0300openSPOT 430.9250/430.9250 CC1