APRS Packet Errors for KN6ODT (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
20261110015704KN6ODT>APBM1D,DMR*,qAR,n3fe-10:@015857h0000.00N/00000.00E[000/000Charles
20261110020006KN6ODT>APBM1D,DMR*,qAR,n3fe-10:@015857h0000.00N/00000.00E[000/000Charles
20261110020610KN6ODT>APBM1D,DMR*,qAR,n3fe-10:@015857h0000.00N/00000.00E[000/000Charles
20261110020912KN6ODT>APBM1D,DMR*,qAR,n3fe-10:@015857h0000.00N/00000.00E[000/000Charles
20261110021214KN6ODT>APBM1D,DMR*,qAR,n3fe-10:@015857h0000.00N/00000.00E[000/000Charles
20261110021517KN6ODT>APBM1D,DMR*,qAR,n3fe-10:@015857h0000.00N/00000.00E[000/000Charles
20261110021818KN6ODT>APBM1D,DMR*,qAR,n3fe-10:@015857h0000.00N/00000.00E[000/000Charles
20261110022121KN6ODT>APBM1D,DMR*,qAR,n3fe-10:@015857h0000.00N/00000.00E[000/000Charles
20261110022422KN6ODT>APBM1D,DMR*,qAR,n3fe-10:@015857h0000.00N/00000.00E[000/000Charles
20261110022724KN6ODT>APBM1D,DMR*,qAR,n3fe-10:@015857h0000.00N/00000.00E[000/000Charles
20261110023026KN6ODT>APBM1D,DMR*,qAR,n3fe-10:@015857h0000.00N/00000.00E[000/000Charles
20261110023328KN6ODT>APBM1D,DMR*,qAR,n3fe-10:@015857h0000.00N/00000.00E[000/000Charles