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
20190717164731ED2ZAC>APZDMR,QTH,TCPIP*,qAU,T2BIO:)ED2ZAC-DP!4316.79N/-02-56.76rRNG0034 IPSC2-EA2Master MMDVM 438.2000@-7.6 MHz
20190717170410ED2ZAC>APZDMR,QTH,TCPIP*,qAU,T2BIO:)ED2ZAC-DP!4316.79N/-02-56.76rRNG0034 IPSC2-EA2Master MMDVM 438.2000@-7.6 MHz
20190717172049ED2ZAC>APZDMR,QTH,TCPIP*,qAU,T2BIO:)ED2ZAC-DP!4316.79N/-02-56.76rRNG0034 IPSC2-EA2Master MMDVM 438.2000@-7.6 MHz
20190717173730ED2ZAC>APZDMR,QTH,TCPIP*,qAU,T2BIO:)ED2ZAC-DP!4316.79N/-02-56.76rRNG0034 IPSC2-EA2Master MMDVM 438.2000@-7.6 MHz
20190717175412ED2ZAC>APZDMR,QTH,TCPIP*,qAU,T2BIO:)ED2ZAC-DP!4316.79N/-02-56.76rRNG0034 IPSC2-EA2Master MMDVM 438.2000@-7.6 MHz
20190717181050ED2ZAC>APZDMR,QTH,TCPIP*,qAU,T2BIO:)ED2ZAC-DP!4316.79N/-02-56.76rRNG0034 IPSC2-EA2Master MMDVM 438.2000@-7.6 MHz
20190717182729ED2ZAC>APZDMR,QTH,TCPIP*,qAU,T2BIO:)ED2ZAC-DP!4316.79N/-02-56.76rRNG0034 IPSC2-EA2Master MMDVM 438.2000@-7.6 MHz
20190717184408ED2ZAC>APZDMR,QTH,TCPIP*,qAU,T2BIO:)ED2ZAC-DP!4316.79N/-02-56.76rRNG0034 IPSC2-EA2Master MMDVM 438.2000@-7.6 MHz
20190717190051ED2ZAC>APZDMR,QTH,TCPIP*,qAU,T2BIO:)ED2ZAC-DP!4316.79N/-02-56.76WrRNG0034 IPSC2-EA2Master MMDVM 438.2000@-7.6 MHz
20190717191731ED2ZAC>APZDMR,QTH,TCPIP*,qAU,T2BIO:)ED2ZAC-DP!4316.79N/-02-56.76rRNG0034 IPSC2-EA2Master MMDVM 438.2000@-7.6 MHz
20190717193410ED2ZAC>APZDMR,QTH,TCPIP*,qAU,T2BIO:)ED2ZAC-DP!4316.79N/-02-56.76rRNG0034 IPSC2-EA2Master MMDVM 438.2000@-7.6 MHz
20190717195049ED2ZAC>APZDMR,QTH,TCPIP*,qAU,T2BIO:)ED2ZAC-DP!4316.79N/-02-56.76rRNG0034 IPSC2-EA2Master MMDVM 438.2000@-7.6 MHz
20190717200731ED2ZAC>APZDMR,QTH,TCPIP*,qAU,T2BIO:)ED2ZAC-DP!4316.79N/-02-56.76rRNG0034 IPSC2-EA2Master MMDVM 438.2000@-7.6 MHz
20190717202410ED2ZAC>APZDMR,QTH,TCPIP*,qAU,T2BIO:)ED2ZAC-DP!4316.79N/-02-56.76rRNG0034 IPSC2-EA2Master MMDVM 438.2000@-7.6 MHz
20190717204049ED2ZAC>APZDMR,QTH,TCPIP*,qAU,T2BIO:)ED2ZAC-DP!4316.79N/-02-56.76rRNG0034 IPSC2-EA2Master MMDVM 438.2000@-7.6 MHz
20190717205727ED2ZAC>APZDMR,QTH,TCPIP*,qAU,T2BIO:)ED2ZAC-DP!4316.79N/-02-56.76rRNG0034 IPSC2-EA2Master MMDVM 438.2000@-7.6 MHz
20190717211410ED2ZAC>APZDMR,QTH,TCPIP*,qAU,T2BIO:)ED2ZAC-DP!4316.79N/-02-56.76rRNG0034 IPSC2-EA2Master MMDVM 438.2000@-7.6 MHz
20190717213050ED2ZAC>APZDMR,QTH,TCPIP*,qAU,T2BIO:)ED2ZAC-DP!4316.79N/-02-56.76rRNG0034 IPSC2-EA2Master MMDVM 438.2000@-7.6 MHz
20190717214730ED2ZAC>APZDMR,QTH,TCPIP*,qAU,T2BIO:)ED2ZAC-DP!4316.79N/-02-56.76rRNG0034 IPSC2-EA2Master MMDVM 438.2000@-7.6 MHz
20190717220409ED2ZAC>APZDMR,QTH,TCPIP*,qAU,T2BIO:)ED2ZAC-DP!4316.79N/-02-56.76rRNG0034 IPSC2-EA2Master MMDVM 438.2000@-7.6 MHz
20190717222050ED2ZAC>APZDMR,QTH,TCPIP*,qAU,T2BIO:)ED2ZAC-DP!4316.79N/-02-56.76rRNG0034 IPSC2-EA2Master MMDVM 438.2000@-7.6 MHz
20190717223729ED2ZAC>APZDMR,QTH,TCPIP*,qAU,T2BIO:)ED2ZAC-DP!4316.79N/-02-56.76rRNG0034 IPSC2-EA2Master MMDVM 438.2000@-7.6 MHz