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
20180223090028PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@230900z5132.100N/00506.60EQPHG0300openSPOT 430.9250/430.9250 CC1
20180223090029PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@230900z5132.100N/00506.60EQPHG0300openSPOT 438.5250/438.5250 CC1
20180223093027PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@230930z5132.100N/00506.60EQPHG0300openSPOT 430.9250/430.9250 CC1
20180223093027PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@230930z5132.100N/00506.60EQPHG0300openSPOT 438.5250/438.5250 CC1
20180223100025PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@231000z5132.100N/00506.60EQPHG0300openSPOT 430.9250/430.9250 CC1
20180223100026PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@231000z5132.100N/00506.60EQPHG0300openSPOT 438.5250/438.5250 CC1
20180223103029PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@231030z5132.100N/00506.60EQPHG0300openSPOT 430.9250/430.9250 CC1
20180223103029PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@231030z5132.100N/00506.60EQPHG0300openSPOT 438.5250/438.5250 CC1
20180223113023PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@231130z5132.100N/00506.60EQPHG0300openSPOT 438.5250/438.5250 CC1
20180223113024PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@231130z5132.100N/00506.60EQPHG0300openSPOT 430.9250/430.9250 CC1
20180223120024PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@231200z5132.100N/00506.60EQPHG0300openSPOT 438.5250/438.5250 CC1
20180223120025PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@231200z5132.100N/00506.60EQPHG0300openSPOT 430.9250/430.9250 CC1
20180223130024PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@231300z5132.100N/00506.60EQPHG0300openSPOT 438.5250/438.5250 CC1
20180223130024PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@231300z5132.100N/00506.60EQPHG0300openSPOT 430.9250/430.9250 CC1
20180223133024PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@231330z5132.100N/00506.60EQPHG0300openSPOT 438.5250/438.5250 CC1
20180223133024PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@231330z5132.100N/00506.60EQPHG0300openSPOT 430.9250/430.9250 CC1
20180223140026PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@231400z5132.100N/00506.60EQPHG0300openSPOT 438.5250/438.5250 CC1
20180223140026PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@231400z5132.100N/00506.60EQPHG0300openSPOT 430.9250/430.9250 CC1
20180223143025PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@231430z5132.100N/00506.60EQPHG0300openSPOT 438.5250/438.5250 CC1
20180223143025PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@231430z5132.100N/00506.60EQPHG0300openSPOT 430.9250/430.9250 CC1