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
20180523170048PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@231700z5132.100N/00506.60EQPHG0300openSPOT 430.9250/430.9250 CC1
20180523170050PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@231700z5132.100N/00506.60EQPHG0300openSPOT 438.5250/438.5250 CC1
20180523173052PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@231730z5132.100N/00506.60EQPHG0300openSPOT 430.9250/430.9250 CC1
20180523173054PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@231730z5132.100N/00506.60EQPHG0300openSPOT 438.5250/438.5250 CC1
20180523180050PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@231800z5132.100N/00506.60EQPHG0300openSPOT 430.9250/430.9250 CC1
20180523180051PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@231800z5132.100N/00506.60EQPHG0300openSPOT 438.5250/438.5250 CC1
20180523183048PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@231830z5132.100N/00506.60EQPHG0300openSPOT 430.9250/430.9250 CC1
20180523183049PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@231830z5132.100N/00506.60EQPHG0300openSPOT 438.5250/438.5250 CC1
20180523190048PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@231900z5132.100N/00506.60EQPHG0300openSPOT 430.9250/430.9250 CC1
20180523190050PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@231900z5132.100N/00506.60EQPHG0300openSPOT 438.5250/438.5250 CC1
20180523193048PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@231930z5132.100N/00506.60EQPHG0300openSPOT 430.9250/430.9250 CC1
20180523193049PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@231930z5132.100N/00506.60EQPHG0300openSPOT 438.5250/438.5250 CC1
20180523200047PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@232000z5132.100N/00506.60EQPHG0300openSPOT 430.9250/430.9250 CC1
20180523200048PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@232000z5132.100N/00506.60EQPHG0300openSPOT 438.5250/438.5250 CC1
20180523203046PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@232030z5132.100N/00506.60EQPHG0300openSPOT 430.9250/430.9250 CC1
20180523203047PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@232030z5132.100N/00506.60EQPHG0300openSPOT 438.5250/438.5250 CC1
20180523210047PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@232100z5132.100N/00506.60EQPHG0300openSPOT 430.9250/430.9250 CC1
20180523210049PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@232100z5132.100N/00506.60EQPHG0300openSPOT 438.5250/438.5250 CC1
20180523213043PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@232130z5132.100N/00506.60EQPHG0300openSPOT 430.9250/430.9250 CC1
20180523213045PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@232130z5132.100N/00506.60EQPHG0300openSPOT 438.5250/438.5250 CC1
20180523220047PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@232200z5132.100N/00506.60EQPHG0300openSPOT 430.9250/430.9250 CC1
20180523220048PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@232200z5132.100N/00506.60EQPHG0300openSPOT 438.5250/438.5250 CC1
20180523223039PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@232230z5132.100N/00506.60EQPHG0300openSPOT 430.9250/430.9250 CC1
20180523223041PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@232230z5132.100N/00506.60EQPHG0300openSPOT 438.5250/438.5250 CC1