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
20171215155906PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@151600z5132.100N/00506.60EQPHG0300openSPOT 438.5250/438.5250 CC1
20171215155907PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@151600z5132.100N/00506.60EQPHG0300openSPOT 430.9250/430.9250 CC1
20171215162907PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@151630z5132.100N/00506.60EQPHG0300openSPOT 438.5250/438.5250 CC1
20171215162908PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@151630z5132.100N/00506.60EQPHG0300openSPOT 430.9250/430.9250 CC1
20171215165904PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@151700z5132.100N/00506.60EQPHG0300openSPOT 438.5250/438.5250 CC1
20171215165905PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@151700z5132.100N/00506.60EQPHG0300openSPOT 430.9250/430.9250 CC1
20171215172905PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@151730z5132.100N/00506.60EQPHG0300openSPOT 438.5250/438.5250 CC1
20171215172906PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@151730z5132.100N/00506.60EQPHG0300openSPOT 430.9250/430.9250 CC1
20171215175905PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@151800z5132.100N/00506.60EQPHG0300openSPOT 438.5250/438.5250 CC1
20171215175906PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@151800z5132.100N/00506.60EQPHG0300openSPOT 430.9250/430.9250 CC1
20171215185905PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@151900z5132.100N/00506.60EQPHG0300openSPOT 438.5250/438.5250 CC1
20171215185906PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@151900z5132.100N/00506.60EQPHG0300openSPOT 430.9250/430.9250 CC1
20171215192906PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@151930z5132.100N/00506.60EQPHG0300openSPOT 438.5250/438.5250 CC1
20171215192906PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@151930z5132.100N/00506.60EQPHG0300openSPOT 430.9250/430.9250 CC1
20171215195905PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@152000z5132.100N/00506.60EQPHG0300openSPOT 438.5250/438.5250 CC1
20171215195906PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@152000z5132.100N/00506.60EQPHG0300openSPOT 430.9250/430.9250 CC1
20171215202906PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@152030z5132.100N/00506.60EQPHG0300openSPOT 438.5250/438.5250 CC1
20171215202907PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@152030z5132.100N/00506.60EQPHG0300openSPOT 430.9250/430.9250 CC1
20171215205904PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@152100z5132.100N/00506.60EQPHG0300openSPOT 438.5250/438.5250 CC1
20171215205905PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@152100z5132.100N/00506.60EQPHG0300openSPOT 430.9250/430.9250 CC1
20171215212905PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@152130z5132.100N/00506.60EQPHG0300openSPOT 438.5250/438.5250 CC1
20171215212905PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@152130z5132.100N/00506.60EQPHG0300openSPOT 430.9250/430.9250 CC1