APRS Packet Errors for ED2ZAC (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
20191117035642ED2ZAC>APZDMR,QTH,TCPIP*,qAU,T2BIO:)ED2ZAC-DP!4316.78N/-02-56.76rRNG0034 IPSC2-EA2Master MMDVM 438.2000@-7.6 MHz
20191117041153ED2ZAC>APZDMR,QTH,TCPIP*,qAU,T2BIO:)ED2ZAC-DP!4316.78N/-02-56.76rRNG0034 IPSC2-EA2Master MMDVM 438.2000@-7.6 MHz
20191117042728ED2ZAC>APZDMR,QTH,TCPIP*,qAU,T2BIO:)ED2ZAC-DP!4316.78N/-02-56.76rRNG0034 IPSC2-EA2Master MMDVM 438.2000@-7.6 MHz
20191117044236ED2ZAC>APZDMR,QTH,TCPIP*,qAU,T2BIO:)ED2ZAC-DP!4316.78N/-02-56.76rRNG0034 IPSC2-EA2Master MMDVM 438.2000@-7.6 MHz
20191117045746ED2ZAC>APZDMR,QTH,TCPIP*,qAU,T2BIO:)ED2ZAC-DP!4316.78N/-02-56.76rRNG0034 IPSC2-EA2Master MMDVM 438.2000@-7.6 MHz
20191117051304ED2ZAC>APZDMR,QTH,TCPIP*,qAU,T2BIO:)ED2ZAC-DP!4316.78N/-02-56.76rRNG0034 IPSC2-EA2Master MMDVM 438.2000@-7.6 MHz
20191117052812ED2ZAC>APZDMR,QTH,TCPIP*,qAU,T2BIO:)ED2ZAC-DP!4316.78N/-02-56.76rRNG0034 IPSC2-EA2Master MMDVM 438.2000@-7.6 MHz
20191117054322ED2ZAC>APZDMR,QTH,TCPIP*,qAU,T2BIO:)ED2ZAC-DP!4316.78N/-02-56.76rRNG0034 IPSC2-EA2Master MMDVM 438.2000@-7.6 MHz
20191117055833ED2ZAC>APZDMR,QTH,TCPIP*,qAU,T2BIO:)ED2ZAC-DP!4316.78N/-02-56.76rRNG0034 IPSC2-EA2Master MMDVM 438.2000@-7.6 MHz
20191117061340ED2ZAC>APZDMR,QTH,TCPIP*,qAU,T2BIO:)ED2ZAC-DP!4316.78N/-02-56.76rRNG0034 IPSC2-EA2Master MMDVM 438.2000@-7.6 MHz
20191117062848ED2ZAC>APZDMR,QTH,TCPIP*,qAU,T2BIO:)ED2ZAC-DP!4316.78N/-02-56.76rRNG0034 IPSC2-EA2Master MMDVM 438.2000@-7.6 MHz
20191117064357ED2ZAC>APZDMR,QTH,TCPIP*,qAU,T2BIO:)ED2ZAC-DP!4316.78N/-02-56.76rRNG0034 IPSC2-EA2Master MMDVM 438.2000@-7.6 MHz
20191117065941ED2ZAC>APZDMR,QTH,TCPIP*,qAU,T2BIO:)ED2ZAC-DP!4316.78N/-02-56.76rRNG0034 IPSC2-EA2Master MMDVM 438.2000@-7.6 MHz
20191117071450ED2ZAC>APZDMR,QTH,TCPIP*,qAU,T2BIO:)ED2ZAC-DP!4316.78N/-02-56.76rRNG0034 IPSC2-EA2Master MMDVM 438.2000@-7.6 MHz
20191117072959ED2ZAC>APZDMR,QTH,TCPIP*,qAU,T2BIO:)ED2ZAC-DP!4316.78N/-02-56.76rRNG0034 IPSC2-EA2Master MMDVM 438.2000@-7.6 MHz
20191117074507ED2ZAC>APZDMR,QTH,TCPIP*,qAU,T2BIO:)ED2ZAC-DP!4316.78N/-02-56.76rRNG0034 IPSC2-EA2Master MMDVM 438.2000@-7.6 MHz
20191117080018ED2ZAC>APZDMR,QTH,TCPIP*,qAU,T2BIO:)ED2ZAC-DP!4316.78N/-02-56.76rRNG0034 IPSC2-EA2Master MMDVM 438.2000@-7.6 MHz
20191117081526ED2ZAC>APZDMR,QTH,TCPIP*,qAU,T2BIO:)ED2ZAC-DP!4316.78N/-02-56.76rRNG0034 IPSC2-EA2Master MMDVM 438.2000@-7.6 MHz
20191117083034ED2ZAC>APZDMR,QTH,TCPIP*,qAU,T2BIO:)ED2ZAC-DP!4316.78N/-02-56.76rRNG0034 IPSC2-EA2Master MMDVM 438.2000@-7.6 MHz
20191117084542ED2ZAC>APZDMR,QTH,TCPIP*,qAU,T2BIO:)ED2ZAC-DP!4316.78N/-02-56.76rRNG0034 IPSC2-EA2Master MMDVM 438.2000@-7.6 MHz
20191117090054ED2ZAC>APZDMR,QTH,TCPIP*,qAU,T2BIO:)ED2ZAC-DP!4316.78N/-02-56.76rRNG0034 IPSC2-EA2Master MMDVM 438.2000@-7.6 MHz
20191117091603ED2ZAC>APZDMR,QTH,TCPIP*,qAU,T2BIO:)ED2ZAC-DP!4316.78N/-02-56.76rRNG0034 IPSC2-EA2Master MMDVM 438.2000@-7.6 MHz
20191117093112ED2ZAC>APZDMR,QTH,TCPIP*,qAU,T2BIO:)ED2ZAC-DP!4316.78N/-02-56.76rRNG0034 IPSC2-EA2Master MMDVM 438.2000@-7.6 MHz
20191117094620ED2ZAC>APZDMR,QTH,TCPIP*,qAU,T2BIO:)ED2ZAC-DP!4316.78N/-02-56.76rRNG0034 IPSC2-EA2Master MMDVM 438.2000@-7.6 MHz