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
20190719195358ED2ZAC>APZDMR,QTH,TCPIP*,qAU,T2BIO:)ED2ZAC-DP!4316.79N/-02-56.76rRNG0034 IPSC2-EA2Master MMDVM 438.2000@-7.6 MHz
20190719201038ED2ZAC>APZDMR,QTH,TCPIP*,qAU,T2BIO:)ED2ZAC-DP!4316.79N/-02-56.76rRNG0034 IPSC2-EA2Master MMDVM 438.2000@-7.6 MHz
20190719202721ED2ZAC>APZDMR,QTH,TCPIP*,qAU,T2BIO:)ED2ZAC-DP!4316.79N/-02-56.76rRNG0034 IPSC2-EA2Master MMDVM 438.2000@-7.6 MHz
20190719204407ED2ZAC>APZDMR,QTH,TCPIP*,qAU,T2BIO:)ED2ZAC-DP!4316.79N/-02-56.76rRNG0034 IPSC2-EA2Master MMDVM 438.2000@-7.6 MHz
20190719210054ED2ZAC>APZDMR,QTH,TCPIP*,qAU,T2BIO:)ED2ZAC-DP!4316.79N/-02-56.76rRNG0034 IPSC2-EA2Master MMDVM 438.2000@-7.6 MHz
20190719211736ED2ZAC>APZDMR,QTH,TCPIP*,qAU,T2BIO:)ED2ZAC-DP!4316.79N/-02-56.76rRNG0034 IPSC2-EA2Master MMDVM 438.2000@-7.6 MHz
20190719213419ED2ZAC>APZDMR,QTH,TCPIP*,qAU,T2BIO:)ED2ZAC-DP!4316.79N/-02-56.76rRNG0034 IPSC2-EA2Master MMDVM 438.2000@-7.6 MHz
20190719215100ED2ZAC>APZDMR,QTH,TCPIP*,qAU,T2BIO:)ED2ZAC-DP!4316.79N/-02-56.76rRNG0034 IPSC2-EA2Master MMDVM 438.2000@-7.6 MHz
20190719220743ED2ZAC>APZDMR,QTH,TCPIP*,qAU,T2BIO:)ED2ZAC-DP!4316.79N/-02-56.76rRNG0034 IPSC2-EA2Master MMDVM 438.2000@-7.6 MHz
20190719222424ED2ZAC>APZDMR,QTH,TCPIP*,qAU,T2BIO:)ED2ZAC-DP!4316.79N/-02-56.76rRNG0034 IPSC2-EA2Master MMDVM 438.2000@-7.6 MHz
20190719224106ED2ZAC>APZDMR,QTH,TCPIP*,qAU,T2BIO:)ED2ZAC-DP!4316.79N/-02-56.76rRNG0034 IPSC2-EA2Master MMDVM 438.2000@-7.6 MHz
20190719225747ED2ZAC>APZDMR,QTH,TCPIP*,qAU,T2BIO:)ED2ZAC-DP!4316.79N/-02-56.76rRNG0034 IPSC2-EA2Master MMDVM 438.2000@-7.6 MHz
20190719231429ED2ZAC>APZDMR,QTH,TCPIP*,qAU,T2BIO:)ED2ZAC-DP!4316.79N/-02-56.76rRNG0034 IPSC2-EA2Master MMDVM 438.2000@-7.6 MHz
20190719233109ED2ZAC>APZDMR,QTH,TCPIP*,qAU,T2BIO:)ED2ZAC-DP!4316.79N/-02-56.76rRNG0034 IPSC2-EA2Master MMDVM 438.2000@-7.6 MHz
20190719234751ED2ZAC>APZDMR,QTH,TCPIP*,qAU,T2BIO:)ED2ZAC-DP!4316.79N/-02-56.76rRNG0034 IPSC2-EA2Master MMDVM 438.2000@-7.6 MHz
20190720000431ED2ZAC>APZDMR,QTH,TCPIP*,qAU,T2BIO:)ED2ZAC-DP!4316.79N/-02-56.76rRNG0034 IPSC2-EA2Master MMDVM 438.2000@-7.6 MHz
20190720002113ED2ZAC>APZDMR,QTH,TCPIP*,qAU,T2BIO:)ED2ZAC-DP!4316.79N/-02-56.76rRNG0034 IPSC2-EA2Master MMDVM 438.2000@-7.6 MHz
20190720003753ED2ZAC>APZDMR,QTH,TCPIP*,qAU,T2BIO:)ED2ZAC-DP!4316.79N/-02-56.76rRNG0034 IPSC2-EA2Master MMDVM 438.2000@-7.6 MHz
20190720005433ED2ZAC>APZDMR,QTH,TCPIP*,qAU,T2BIO:)ED2ZAC-DP!4316.79N/-02-56.76rRNG0034 IPSC2-EA2Master MMDVM 438.2000@-7.6 MHz
20190720011113ED2ZAC>APZDMR,QTH,TCPIP*,qAU,T2BIO:)ED2ZAC-DP!4316.79N/-02-56.76rRNG0034 IPSC2-EA2Master MMDVM 438.2000@-7.6 MHz
20190720012758ED2ZAC>APZDMR,QTH,TCPIP*,qAU,T2BIO:)ED2ZAC-DP!4316.79N/-02-56.76rRNG0034 IPSC2-EA2Master MMDVM 438.2000@-7.6 MHz
20190720014438ED2ZAC>APZDMR,QTH,TCPIP*,qAU,T2BIO:)ED2ZAC-DP!4316.79N/-02-56.76rRNG0034 IPSC2-EA2Master MMDVM 438.2000@-7.6 MHz