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
20171020012904PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@200130z5132.100N/00506.60EQPHG0300openSPOT 430.9250/430.9250 CC1
20171020012909PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@200130z5132.100N/00506.60EQPHG0300openSPOT 438.5250/438.5250 CC1
20171020015905PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@200200z5132.100N/00506.60EQPHG0300openSPOT 430.9250/430.9250 CC1
20171020015910PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@200200z5132.100N/00506.60EQPHG0300openSPOT 438.5250/438.5250 CC1
20171020022905PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@200230z5132.100N/00506.60EQPHG0300openSPOT 430.9250/430.9250 CC1
20171020022910PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@200230z5132.100N/00506.60EQPHG0300openSPOT 438.5250/438.5250 CC1
20171020025905PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@200300z5132.100N/00506.60EQPHG0300openSPOT 430.9250/430.9250 CC1
20171020025910PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@200300z5132.100N/00506.60EQPHG0300openSPOT 438.5250/438.5250 CC1
20171020032905PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@200330z5132.100N/00506.60EQPHG0300openSPOT 430.9250/430.9250 CC1
20171020032910PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@200330z5132.100N/00506.60EQPHG0300openSPOT 438.5250/438.5250 CC1
20171020035905PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@200400z5132.100N/00506.60EQPHG0300openSPOT 430.9250/430.9250 CC1
20171020035909PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@200400z5132.100N/00506.60EQPHG0300openSPOT 438.5250/438.5250 CC1
20171020042905PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@200430z5132.100N/00506.60EQPHG0300openSPOT 430.9250/430.9250 CC1
20171020042910PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@200430z5132.100N/00506.60EQPHG0300openSPOT 438.5250/438.5250 CC1
20171020045905PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@200500z5132.100N/00506.60EQPHG0300openSPOT 430.9250/430.9250 CC1
20171020045910PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@200500z5132.100N/00506.60EQPHG0300openSPOT 438.5250/438.5250 CC1
20171020052905PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@200530z5132.100N/00506.60EQPHG0300openSPOT 430.9250/430.9250 CC1
20171020052910PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@200530z5132.100N/00506.60EQPHG0300openSPOT 438.5250/438.5250 CC1
20171020055905PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@200600z5132.100N/00506.60EQPHG0300openSPOT 430.9250/430.9250 CC1
20171020055912PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@200600z5132.100N/00506.60EQPHG0300openSPOT 438.5250/438.5250 CC1
20171020062906PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@200630z5132.100N/00506.60EQPHG0300openSPOT 430.9250/430.9250 CC1
20171020062910PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@200630z5132.100N/00506.60EQPHG0300openSPOT 438.5250/438.5250 CC1
20171020065905PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@200700z5132.100N/00506.60EQPHG0300openSPOT 430.9250/430.9250 CC1
20171020065911PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@200700z5132.100N/00506.60EQPHG0300openSPOT 438.5250/438.5250 CC1