APRS Packet Errors for EB3FMU (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
20190819192039EB3FMU>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB3FMU-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA1Master MMDVM 438.8000 MHz
20190819193730EB3FMU>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB3FMU-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA1Master MMDVM 438.8000 MHz
20190819195420EB3FMU>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB3FMU-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA1Master MMDVM 438.8000 MHz
20190819201106EB3FMU>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB3FMU-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA1Master MMDVM 438.8000 MHz
20190819202752EB3FMU>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB3FMU-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA1Master MMDVM 438.8000 MHz
20190819204442EB3FMU>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB3FMU-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA1Master MMDVM 438.8000 MHz
20190819210132EB3FMU>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB3FMU-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA1Master MMDVM 438.8000 MHz
20190819211822EB3FMU>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB3FMU-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA1Master MMDVM 438.8000 MHz
20190819213514EB3FMU>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB3FMU-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA1Master MMDVM 438.8000 MHz
20190819215208EB3FMU>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB3FMU-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA1Master MMDVM 438.8000 MHz
20190819220902EB3FMU>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB3FMU-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA1Master MMDVM 438.8000 MHz
20190819222549EB3FMU>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB3FMU-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA1Master MMDVM 438.8000 MHz
20190819224238EB3FMU>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB3FMU-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA1Master MMDVM 438.8000 MHz
20190819225926EB3FMU>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB3FMU-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA1Master MMDVM 438.8000 MHz
20190819231614EB3FMU>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB3FMU-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA1Master MMDVM 438.8000 MHz
20190819233300EB3FMU>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB3FMU-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA1Master MMDVM 438.8000 MHz
20190819234947EB3FMU>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB3FMU-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA1Master MMDVM 438.8000 MHz
20190820000636EB3FMU>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB3FMU-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA1Master MMDVM 438.8000 MHz
20190820002332EB3FMU>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB3FMU-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA1Master MMDVM 438.8000 MHz