APRS Packet Errors for LU4CMD-2 (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
20251014000203LU4CMD-2>AESPT4,LU1CJM-10*,qAR,LU2APR-2:!3434.70S
20251014001619LU4CMD-2>AESPT4,LU1CJM-10*,qAR,LU2APR-2:!3434.65S
20251014002937LU4CMD-2>AESPT4,LU1CJM-10*,qAR,LU2APR-2:!3434.64S
20251014011118LU4CMD-2>AESPT4,LU1CJM-10*,qAR,LU2APR-2:!3434.66S
20251014011215LU4CMD-2>AESPT4,LU1CJM-10*,qAR,LU2APR-2:!3434.65S
20251014011643LU4CMD-2>AESPT4,LU7AA-10,WIDE1*,qAR,LU2APR-2:!3434.63S
20251014011906LU4CMD-2>AESPT4,LU7AA-10,WIDE1*,qAR,LU2APR-2:!3434.64S
20251014012915LU4CMD-2>AESPT4,LU7AA-10,WIDE1*,qAR,LU2APR-2:!3434.63S
20251014013919LU4CMD-2>AESPT4,LU1CJM-10*,qAR,LU2APR-2:!3434.63S
20251014015654LU4CMD-2>AESPT4,LU7AA-10,WIDE1*,qAR,LU2APR-2:!3434.64S
20251014020608LU4CMD-2>AESPT4,LU7AA-10,WIDE1*,qAR,LU2APR-2:!3434.64S