APRS Packet Errors for W7DGS (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
20190616085417W7DGS>APZDMR,QTH,TCPIP*,qAU,T2BIO:)W7DGS-DP!4402.20N/-122-57.1rRNG0034 IPSC2-EA2Master MMDVM 434.5000 MHz
20190616091052W7DGS>APZDMR,QTH,TCPIP*,qAU,T2BIO:)W7DGS-DP!4402.20N/-122-57.1rRNG0034 IPSC2-EA2Master MMDVM 434.5000 MHz
20190616092726W7DGS>APZDMR,QTH,TCPIP*,qAU,T2BIO:)W7DGS-DP!4402.20N/-122-57.1rRNG0034 IPSC2-EA2Master MMDVM 434.5000 MHz
20190616094402W7DGS>APZDMR,QTH,TCPIP*,qAU,T2BIO:)W7DGS-DP!4402.20N/-122-57.1rRNG0034 IPSC2-EA2Master MMDVM 434.5000 MHz
20190616100038W7DGS>APZDMR,QTH,TCPIP*,qAU,T2BIO:)W7DGS-DP!4402.20N/-122-57.1rRNG0034 IPSC2-EA2Master MMDVM 434.5000 MHz
20190616101712W7DGS>APZDMR,QTH,TCPIP*,qAU,T2BIO:)W7DGS-DP!4402.20N/-122-57.1rRNG0034 IPSC2-EA2Master MMDVM 434.5000 MHz
20190616103349W7DGS>APZDMR,QTH,TCPIP*,qAU,T2BIO:)W7DGS-DP!4402.20N/-122-57.1rRNG0034 IPSC2-EA2Master MMDVM 434.5000 MHz
20190616105022W7DGS>APZDMR,QTH,TCPIP*,qAU,T2BIO:)W7DGS-DP!4402.20N/-122-57.1rRNG0034 IPSC2-EA2Master MMDVM 434.5000 MHz
20190616110701W7DGS>APZDMR,QTH,TCPIP*,qAU,T2BIO:)W7DGS-DP!4402.20N/-122-57.1rRNG0034 IPSC2-EA2Master MMDVM 434.5000 MHz
20190616112337W7DGS>APZDMR,QTH,TCPIP*,qAU,T2BIO:)W7DGS-DP!4402.20N/-122-57.1rRNG0034 IPSC2-EA2Master MMDVM 434.5000 MHz
20190616114011W7DGS>APZDMR,QTH,TCPIP*,qAU,T2BIO:)W7DGS-DP!4402.20N/-122-57.1rRNG0034 IPSC2-EA2Master MMDVM 434.5000 MHz
20190616115648W7DGS>APZDMR,QTH,TCPIP*,qAU,T2BIO:)W7DGS-DP!4402.20N/-122-57.1rRNG0034 IPSC2-EA2Master MMDVM 434.5000 MHz
20190616121324W7DGS>APZDMR,QTH,TCPIP*,qAU,T2BIO:)W7DGS-DP!4402.20N/-122-57.1rRNG0034 IPSC2-EA2Master MMDVM 434.5000 MHz
20190616123000W7DGS>APZDMR,QTH,TCPIP*,qAU,T2BIO:)W7DGS-DP!4402.20N/-122-57.1rRNG0034 IPSC2-EA2Master MMDVM 434.5000 MHz
20190616124636W7DGS>APZDMR,QTH,TCPIP*,qAU,T2BIO:)W7DGS-DP!4402.20N/-122-57.1rRNG0034 IPSC2-EA2Master MMDVM 434.5000 MHz
20190616130312W7DGS>APZDMR,QTH,TCPIP*,qAU,T2BIO:)W7DGS-DP!4402.20N/-122-57.1rRNG0034 IPSC2-EA2Master MMDVM 434.5000 MHz
20190616131950W7DGS>APZDMR,QTH,TCPIP*,qAU,T2BIO:)W7DGS-DP!4402.20N/-122-57.1rRNG0034 IPSC2-EA2Master MMDVM 434.5000 MHz
20190616133625W7DGS>APZDMR,QTH,TCPIP*,qAU,T2BIO:)W7DGS-DP!4402.20N/-122-57.1rRNG0034 IPSC2-EA2Master MMDVM 434.5000 MHz
20190616135301W7DGS>APZDMR,QTH,TCPIP*,qAU,T2BIO:)W7DGS-DP!4402.20N/-122-57.1rRNG0034 IPSC2-EA2Master MMDVM 434.5000 MHz
20190616140936W7DGS>APZDMR,QTH,TCPIP*,qAU,T2BIO:)W7DGS-DP!4402.20N/-122-57.1rRNG0034 IPSC2-EA2Master MMDVM 434.5000 MHz
20190616142613W7DGS>APZDMR,QTH,TCPIP*,qAU,T2BIO:)W7DGS-DP!4402.20N/-122-57.1rRNG0034 IPSC2-EA2Master MMDVM 434.5000 MHz
20190616144248W7DGS>APZDMR,QTH,TCPIP*,qAU,T2BIO:)W7DGS-DP!4402.20N/-122-57.1rRNG0034 IPSC2-EA2Master MMDVM 434.5000 MHz