APRS Packet Errors for LU3MCV-7 (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
20251013151559LU3MCV-7>APLRG1,WIDE1-1,qAR,LU3MCV-10:!LoRa Tracker LU3MCV San Rafael Mza. Batt=3.56V
20251013153101LU3MCV-7>APLRG1,WIDE1-1,qAR,LU3MCV-10:!LoRa Tracker LU3MCV San Rafael Mza. Batt=3.55V
20251013154601LU3MCV-7>APLRG1,WIDE1-1,qAR,LU3MCV-10:!LoRa Tracker LU3MCV San Rafael Mza. Batt=3.48V
20251013160101LU3MCV-7>APLRG1,WIDE1-1,qAR,LU3MCV-10:!LoRa Tracker LU3MCV San Rafael Mza. Batt=3.52V
20251013171602LU3MCV-7>APLRG1,WIDE1-1,qAR,LU3MCV-10:!LoRa Tracker LU3MCV San Rafael Mza. Batt=3.53V
20251013180106LU3MCV-7>APLRG1,WIDE1-1,qAR,LU3MCV-10:!LoRa Tracker LU3MCV San Rafael Mza. Batt=3.56V
20251013190107LU3MCV-7>APLRG1,WIDE1-1,qAR,LU3MCV-10:!LoRa Tracker LU3MCV San Rafael Mza. Batt=3.56V
20251013200108LU3MCV-7>APLRG1,WIDE1-1,qAR,LU3MCV-10:!LoRa Tracker LU3MCV San Rafael Mza. Batt=3.56V