APRS Packet Errors for MM0DXE (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
20190326170420MM0DXE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)MM0DXE-DP!5612.29N/-02-46.31rRNG0034 IPSC2-Scotland MMDVM 144.6000 MHz
20190326172116MM0DXE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)MM0DXE-DP!5612.29N/-02-46.31rRNG0034 IPSC2-Scotland MMDVM 144.6000 MHz
20190326172809MM0DXE>APDPRS,C4FM*,qAR,GB7SM-R:!5612.31N/00246.28W[ FT-1D via MMDVM
20190326172829MM0DXE>APDPRS,C4FM*,qAR,GB7SM-R:!5612.30N/00246.31W[ FT-1D via MMDVM
20190326172919MM0DXE>APDPRS,C4FM*,qAR,GB7SM-R:!5612.29N/00246.33W[ FT-1D via MMDVM
20190326173009MM0DXE>APDPRS,C4FM*,qAR,GB7SM-R:!5612.29N/00246.33W[ FT-1D via MMDVM
20190326173049MM0DXE>APDPRS,C4FM*,qAR,GB7SM-R:!5612.30N/00246.30W[ FT-1D via MMDVM
20190326173419MM0DXE>APDPRS,C4FM*,qAR,GB7SM-R:!5612.30N/00246.33W[ FT-1D via MMDVM
20190326173811MM0DXE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)MM0DXE-DP!5612.29N/-02-46.31rRNG0034 IPSC2-Scotland MMDVM 144.6000 MHz
20190326181959MM0DXE>APDPRS,C4FM*,qAR,GB7SM-R:!5612.29N/00246.33W[ FT-1D via MMDVM
20190326182009MM0DXE>APDPRS,C4FM*,qAR,GB7SM-R:!5612.29N/00246.32W[ FT-1D via MMDVM
20190326182039MM0DXE>APDPRS,C4FM*,qAR,GB7SM-R:!5612.30N/00246.32W[ FT-1D via MMDVM
20190326194349MM0DXE>APDPRS,C4FM*,qAR,GB7SM-R:!5612.29N/00246.32W[ FT-1D via MMDVM
20190326195419MM0DXE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)MM0DXE-DP!5612.29N/-02-46.31rRNG0034 IPSC2-Scotland MMDVM 144.6000 MHz
20190326201129MM0DXE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)MM0DXE-DP!5612.29N/-02-46.31rRNG0034 IPSC2-Scotland MMDVM 144.6000 MHz
20190326202827MM0DXE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)MM0DXE-DP!5612.29N/-02-46.31rRNG0034 IPSC2-Scotland MMDVM 144.6000 MHz
20190326204522MM0DXE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)MM0DXE-DP!5612.29N/-02-46.31rRNG0034 IPSC2-Scotland MMDVM 144.6000 MHz
20190326210237MM0DXE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)MM0DXE-DP!5612.29N/-02-46.31rRNG0034 IPSC2-Scotland MMDVM 144.6000 MHz
20190326212001MM0DXE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)MM0DXE-DP!5612.29N/-02-46.31rRNG0034 IPSC2-Scotland MMDVM 144.6000 MHz
20190326213657MM0DXE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)MM0DXE-DP!5612.29N/-02-46.31rRNG0034 IPSC2-Scotland MMDVM 144.6000 MHz
20190326215349MM0DXE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)MM0DXE-DP!5612.29N/-02-46.31rRNG0034 IPSC2-Scotland MMDVM 144.6000 MHz
20190326221055MM0DXE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)MM0DXE-DP!5612.29N/-02-46.31rRNG0034 IPSC2-Scotland MMDVM 144.6000 MHz
20190326222801MM0DXE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)MM0DXE-DP!5612.29N/-02-46.31rRNG0034 IPSC2-Scotland MMDVM 144.6000 MHz
20190326224508MM0DXE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)MM0DXE-DP!5612.29N/-02-46.31rRNG0034 IPSC2-Scotland MMDVM 144.6000 MHz