APRS Packet Errors for KE6ULE-Y (last 24 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
20250402004630KE6ULE-Y>APDPRS,C4FM*,qAR,KE6ULE-N:!0000.00N/00000.00E- 0x34 via MMDVM
20250402004730KE6ULE-Y>APDPRS,C4FM*,qAR,KE6ULE-N:!0000.00N/00000.00E- 0x34 via MMDVM
20250402004830KE6ULE-Y>APDPRS,C4FM*,qAR,KE6ULE-N:!0000.00N/00000.00E- 0x34 via MMDVM
20250402004910KE6ULE-Y>APDPRS,C4FM*,qAR,KE6ULE-N:!0000.00N/00000.00E- 0x34 via MMDVM
20250402005254KE6ULE-Y>APDPRS,C4FM*,qAR,KE6ULE-N:!0000.00N/00000.00E- 0x34 via MMDVM
20250402005659KE6ULE-Y>APDPRS,C4FM*,qAR,KE6ULE-N:!0000.00N/00000.00E- 0x34 via MMDVM
20250402005759KE6ULE-Y>APDPRS,C4FM*,qAR,KE6ULE-N:!0000.00N/00000.00E- 0x34 via MMDVM
20250402005939KE6ULE-Y>APDPRS,C4FM*,qAR,KE6ULE-N:!0000.00N/00000.00E- 0x34 via MMDVM
20250402010050KE6ULE-Y>APDPRS,C4FM*,qAR,KE6ULE-N:!0000.00N/00000.00E- 0x34 via MMDVM
20250402010130KE6ULE-Y>APDPRS,C4FM*,qAR,KE6ULE-N:!0000.00N/00000.00E- 0x34 via MMDVM
20250402010250KE6ULE-Y>APDPRS,C4FM*,qAR,KE6ULE-N:!0000.00N/00000.00E- 0x34 via MMDVM
20250402010330KE6ULE-Y>APDPRS,C4FM*,qAR,KE6ULE-N:!0000.00N/00000.00E- 0x34 via MMDVM
20250402153206KE6ULE-Y>APDPRS,C4FM*,qAR,KE6ULE-N:!0000.00N/00000.00E- 0x34 via MMDVM