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
20191121134232ED2ZAC>APZDMR,QTH,TCPIP*,qAU,T2BIO:)ED2ZAC-DP!4316.78N/-02-56.76rRNG0034 IPSC2-EA2Master MMDVM 438.2000@-7.6 MHz
20191121135743ED2ZAC>APZDMR,QTH,TCPIP*,qAU,T2BIO:)ED2ZAC-DP!4316.78N/-02-56.76rRNG0034 IPSC2-EA2Master MMDVM 438.2000@-7.6 MHz
20191121141254ED2ZAC>APZDMR,QTH,TCPIP*,qAU,T2BIO:)ED2ZAC-DP!4316.78N/-02-56.76rRNG0034 IPSC2-EA2Master MMDVM 438.2000@-7.6 MHz
20191121142803ED2ZAC>APZDMR,QTH,TCPIP*,qAU,T2BIO:)ED2ZAC-DP!4316.78N/-02-56.76rRNG0034 IPSC2-EA2Master MMDVM 438.2000@-7.6 MHz
20191121144312ED2ZAC>APZDMR,QTH,TCPIP*,qAU,T2BIO:)ED2ZAC-DP!4316.78N/-02-56.76rRNG0034 IPSC2-EA2Master MMDVM 438.2000@-7.6 MHz
20191121145820ED2ZAC>APZDMR,QTH,TCPIP*,qAU,T2BIO:)ED2ZAC-DP!4316.78N/-02-56.76rRNG0034 IPSC2-EA2Master MMDVM 438.2000@-7.6 MHz
20191121151333ED2ZAC>APZDMR,QTH,TCPIP*,qAU,T2BIO:)ED2ZAC-DP!4316.78N/-02-56.76rRNG0034 IPSC2-EA2Master MMDVM 438.2000@-7.6 MHz
20191121152846ED2ZAC>APZDMR,QTH,TCPIP*,qAU,T2BIO:)ED2ZAC-DP!4316.78N/-02-56.76rRNG0034 IPSC2-EA2Master MMDVM 438.2000@-7.6 MHz
20191121154355ED2ZAC>APZDMR,QTH,TCPIP*,qAU,T2BIO:)ED2ZAC-DP!4316.78N/-02-56.76rRNG0034 IPSC2-EA2Master MMDVM 438.2000@-7.6 MHz
20191121155904ED2ZAC>APZDMR,QTH,TCPIP*,qAU,T2BIO:)ED2ZAC-DP!4316.78N/-02-56.76rRNG0034 IPSC2-EA2Master MMDVM 438.2000@-7.6 MHz
20191121161416ED2ZAC>APZDMR,QTH,TCPIP*,qAU,T2BIO:)ED2ZAC-DP!4316.78N/-02-56.76rRNG0034 IPSC2-EA2Master MMDVM 438.2000@-7.6 MHz
20191121162924ED2ZAC>APZDMR,QTH,TCPIP*,qAU,T2BIO:)ED2ZAC-DP!4316.78N/-02-56.76rRNG0034 IPSC2-EA2Master MMDVM 438.2000@-7.6 MHz
20191121164433ED2ZAC>APZDMR,QTH,TCPIP*,qAU,T2BIO:)ED2ZAC-DP!4316.78N/-02-56.76rRNG0034 IPSC2-EA2Master MMDVM 438.2000@-7.6 MHz
20191121165941ED2ZAC>APZDMR,QTH,TCPIP*,qAU,T2BIO:)ED2ZAC-DP!4316.78N/-02-56.76rRNG0034 IPSC2-EA2Master MMDVM 438.2000@-7.6 MHz
20191121171453ED2ZAC>APZDMR,QTH,TCPIP*,qAU,T2BIO:)ED2ZAC-DP!4316.78N/-02-56.76rRNG0034 IPSC2-EA2Master MMDVM 438.2000@-7.6 MHz
20191121173004ED2ZAC>APZDMR,QTH,TCPIP*,qAU,T2BIO:)ED2ZAC-DP!4316.78N/-02-56.76rRNG0034 IPSC2-EA2Master MMDVM 438.2000@-7.6 MHz
20191121174512ED2ZAC>APZDMR,QTH,TCPIP*,qAU,T2BIO:)ED2ZAC-DP!4316.78N/-02-56.76rRNG0034 IPSC2-EA2Master MMDVM 438.2000@-7.6 MHz
20191121180020ED2ZAC>APZDMR,QTH,TCPIP*,qAU,T2BIO:)ED2ZAC-DP!4316.78N/-02-56.76rRNG0034 IPSC2-EA2Master MMDVM 438.2000@-7.6 MHz
20191121181554ED2ZAC>APZDMR,QTH,TCPIP*,qAU,T2BIO:)ED2ZAC-DP!4316.78N/-02-56.76rRNG0034 IPSC2-EA2Master MMDVM 438.2000@-7.6 MHz
20191121183103ED2ZAC>APZDMR,QTH,TCPIP*,qAU,T2BIO:)ED2ZAC-DP!4316.78N/-02-56.76rRNG0034 IPSC2-EA2Master MMDVM 438.2000@-7.6 MHz
20191121184614ED2ZAC>APZDMR,QTH,TCPIP*,qAU,T2BIO:)ED2ZAC-DP!4316.78N/-02-56.76rRNG0034 IPSC2-EA2Master MMDVM 438.2000@-7.6 MHz
20191121190124ED2ZAC>APZDMR,QTH,TCPIP*,qAU,T2BIO:)ED2ZAC-DP!4316.78N/-02-56.76rRNG0034 IPSC2-EA2Master MMDVM 438.2000@-7.6 MHz
20191121191637ED2ZAC>APZDMR,QTH,TCPIP*,qAU,T2BIO:)ED2ZAC-DP!4316.78N/-02-56.76rRNG0034 IPSC2-EA2Master MMDVM 438.2000@-7.6 MHz
20191121193147ED2ZAC>APZDMR,QTH,TCPIP*,qAU,T2BIO:)ED2ZAC-DP!4316.78N/-02-56.76rRNG0034 IPSC2-EA2Master MMDVM 438.2000@-7.6 MHz