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
20180520180104PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@201801z5132.100N/00506.60EQPHG0300openSPOT 430.9250/430.9250 CC1
20180520180106PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@201801z5132.100N/00506.60EQPHG0300openSPOT 438.5250/438.5250 CC1
20180520183054PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@201830z5132.100N/00506.60EQPHG0300openSPOT 430.9250/430.9250 CC1
20180520183056PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@201830z5132.100N/00506.60EQPHG0300openSPOT 438.5250/438.5250 CC1
20180520190051PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@201900z5132.100N/00506.60EQPHG0300openSPOT 430.9250/430.9250 CC1
20180520190053PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@201900z5132.100N/00506.60EQPHG0300openSPOT 438.5250/438.5250 CC1
20180520193057PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@201930z5132.100N/00506.60EQPHG0300openSPOT 430.9250/430.9250 CC1
20180520193106PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@201931z5132.100N/00506.60EQPHG0300openSPOT 438.5250/438.5250 CC1
20180520200049PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@202000z5132.100N/00506.60EQPHG0300openSPOT 430.9250/430.9250 CC1
20180520200050PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@202000z5132.100N/00506.60EQPHG0300openSPOT 438.5250/438.5250 CC1
20180520203045PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@202030z5132.100N/00506.60EQPHG0300openSPOT 430.9250/430.9250 CC1
20180520203047PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@202030z5132.100N/00506.60EQPHG0300openSPOT 438.5250/438.5250 CC1
20180520210043PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@202100z5132.100N/00506.60EQPHG0300openSPOT 430.9250/430.9250 CC1
20180520210044PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@202100z5132.100N/00506.60EQPHG0300openSPOT 438.5250/438.5250 CC1
20180520213044PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@202130z5132.100N/00506.60EQPHG0300openSPOT 430.9250/430.9250 CC1
20180520213045PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@202130z5132.100N/00506.60EQPHG0300openSPOT 438.5250/438.5250 CC1
20180520220042PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@202200z5132.100N/00506.60EQPHG0300openSPOT 430.9250/430.9250 CC1
20180520220043PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@202200z5132.100N/00506.60EQPHG0300openSPOT 438.5250/438.5250 CC1
20180520223040PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@202230z5132.100N/00506.60EQPHG0300openSPOT 430.9250/430.9250 CC1
20180520223042PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@202230z5132.100N/00506.60EQPHG0300openSPOT 438.5250/438.5250 CC1
20180520230039PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@202300z5132.100N/00506.60EQPHG0300openSPOT 430.9250/430.9250 CC1
20180520230041PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@202300z5132.100N/00506.60EQPHG0300openSPOT 438.5250/438.5250 CC1
20180520233037PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@202330z5132.100N/00506.60EQPHG0300openSPOT 430.9250/430.9250 CC1
20180520233039PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@202330z5132.100N/00506.60EQPHG0300openSPOT 438.5250/438.5250 CC1