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
20180526180006PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@261800z5132.100N/00506.60EQPHG0300openSPOT 438.5250/438.5250 CC1
20180526180017PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@261800z5132.100N/00506.60EQPHG0300openSPOT 430.9250/430.9250 CC1
20180526183006PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@261830z5132.100N/00506.60EQPHG0300openSPOT 438.5250/438.5250 CC1
20180526183016PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@261830z5132.100N/00506.60EQPHG0300openSPOT 430.9250/430.9250 CC1
20180526190006PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@261900z5132.100N/00506.60EQPHG0300openSPOT 438.5250/438.5250 CC1
20180526190015PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@261900z5132.100N/00506.60EQPHG0300openSPOT 430.9250/430.9250 CC1
20180526193007PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@261930z5132.100N/00506.60EQPHG0300openSPOT 438.5250/438.5250 CC1
20180526193017PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@261930z5132.100N/00506.60EQPHG0300openSPOT 430.9250/430.9250 CC1
20180526200008PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@262000z5132.100N/00506.60EQPHG0300openSPOT 438.5250/438.5250 CC1
20180526200017PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@262000z5132.100N/00506.60EQPHG0300openSPOT 430.9250/430.9250 CC1
20180526203007PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@262030z5132.100N/00506.60EQPHG0300openSPOT 438.5250/438.5250 CC1
20180526203015PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@262030z5132.100N/00506.60EQPHG0300openSPOT 430.9250/430.9250 CC1
20180526210007PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@262100z5132.100N/00506.60EQPHG0300openSPOT 438.5250/438.5250 CC1
20180526210015PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@262100z5132.100N/00506.60EQPHG0300openSPOT 430.9250/430.9250 CC1
20180526213007PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@262130z5132.100N/00506.60EQPHG0300openSPOT 438.5250/438.5250 CC1
20180526213014PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@262130z5132.100N/00506.60EQPHG0300openSPOT 430.9250/430.9250 CC1
20180526220008PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@262200z5132.100N/00506.60EQPHG0300openSPOT 438.5250/438.5250 CC1
20180526220015PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@262200z5132.100N/00506.60EQPHG0300openSPOT 430.9250/430.9250 CC1
20180526223006PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@262230z5132.100N/00506.60EQPHG0300openSPOT 438.5250/438.5250 CC1
20180526223014PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@262230z5132.100N/00506.60EQPHG0300openSPOT 430.9250/430.9250 CC1
20180526230007PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@262300z5132.100N/00506.60EQPHG0300openSPOT 438.5250/438.5250 CC1
20180526230013PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@262300z5132.100N/00506.60EQPHG0300openSPOT 430.9250/430.9250 CC1
20180526233006PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@262330z5132.100N/00506.60EQPHG0300openSPOT 438.5250/438.5250 CC1
20180526233014PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@262330z5132.100N/00506.60EQPHG0300openSPOT 430.9250/430.9250 CC1