APRS Packet Errors for EA1BCU (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
20190520084656EA1BCU>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1BCU-DP!4332.91N/-05-55.30rRNG0034 IPSC2-EA4Master MMDVM 435.1000 MHz
20190520090406EA1BCU>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1BCU-DP!4332.91N/-05-55.30rRNG0034 IPSC2-EA4Master MMDVM 435.1000 MHz
20190520092106EA1BCU>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1BCU-DP!4332.91N/-05-55.30rRNG0034 IPSC2-EA4Master MMDVM 435.1000 MHz
20190520093809EA1BCU>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1BCU-DP!4332.91N/-05-55.30rRNG0034 IPSC2-EA4Master MMDVM 435.1000 MHz
20190520095514EA1BCU>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1BCU-DP!4332.91N/-05-55.30rRNG0034 IPSC2-EA4Master MMDVM 435.1000 MHz
20190520101224EA1BCU>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1BCU-DP!4332.91N/-05-55.30rRNG0034 IPSC2-EA4Master MMDVM 435.1000 MHz
20190520102927EA1BCU>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1BCU-DP!4332.91N/-05-55.30rRNG0034 IPSC2-EA4Master MMDVM 435.1000 MHz
20190520104628EA1BCU>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1BCU-DP!4332.91N/-05-55.30rRNG0034 IPSC2-EA4Master MMDVM 435.1000 MHz
20190520110334EA1BCU>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1BCU-DP!4332.91N/-05-55.30rRNG0034 IPSC2-EA4Master MMDVM 435.1000 MHz
20190520112051EA1BCU>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1BCU-DP!4332.91N/-05-55.30rRNG0034 IPSC2-EA4Master MMDVM 435.1000 MHz
20190520113750EA1BCU>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1BCU-DP!4332.91N/-05-55.30rRNG0034 IPSC2-EA4Master MMDVM 435.1000 MHz
20190520115453EA1BCU>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1BCU-DP!4332.91N/-05-55.30rRNG0034 IPSC2-EA4Master MMDVM 435.1000 MHz
20190520121158EA1BCU>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1BCU-DP!4332.91N/-05-55.30rRNG0034 IPSC2-EA4Master MMDVM 435.1000 MHz
20190520122859EA1BCU>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1BCU-DP!4332.91N/-05-55.30rRNG0034 IPSC2-EA4Master MMDVM 435.1000 MHz
20190520124604EA1BCU>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1BCU-DP!4332.91N/-05-55.30rRNG0034 IPSC2-EA4Master MMDVM 435.1000 MHz
20190520130312EA1BCU>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1BCU-DP!4332.91N/-05-55.30rRNG0034 IPSC2-EA4Master MMDVM 435.1000 MHz
20190520132007EA1BCU>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1BCU-DP!4332.91N/-05-55.30rRNG0034 IPSC2-EA4Master MMDVM 435.1000 MHz
20190520133709EA1BCU>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1BCU-DP!4332.91N/-05-55.30rRNG0034 IPSC2-EA4Master MMDVM 435.1000 MHz
20190520135414EA1BCU>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1BCU-DP!4332.91N/-05-55.30rRNG0034 IPSC2-EA4Master MMDVM 435.1000 MHz
20190520141105EA1BCU>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1BCU-DP!4332.91N/-05-55.30rRNG0034 IPSC2-EA4Master MMDVM 435.1000 MHz
20190520142800EA1BCU>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1BCU-DP!4332.91N/-05-55.30rRNG0034 IPSC2-EA4Master MMDVM 435.1000 MHz