APRS Packet Errors for MM0EFI-3 (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
20260209092638	MM0EFI-3>APLRG1,WIDE1-1,qAR,MM0RFN-10:=L1ZVWMdZh# !GLoRa APRS Batt=0.28V
20260209095639	MM0EFI-3>APLRG1,WIDE1-1,qAR,MM0RFN-10:=L1ZVWMdZh# !GLoRa APRS Batt=0.28V
20260209102639	MM0EFI-3>APLRG1,WIDE1-1,qAR,MM0RFN-10:=L1ZVWMdZh# !GLoRa APRS Batt=0.28V
20260209105639	MM0EFI-3>APLRG1,WIDE1-1,qAR,MM0EFI-10:=L1ZVWMdZh# !GLoRa APRS Batt=0.28V
20260209112639	MM0EFI-3>APLRG1,WIDE1-1,qAR,MM0EFI-10:=L1ZVWMdZh# !GLoRa APRS Batt=0.29V
20260209115639	MM0EFI-3>APLRG1,WIDE1-1,qAR,MM0RFN-10:=L1ZVWMdZh# !GLoRa APRS Batt=0.28V
20260209122640	MM0EFI-3>APLRG1,WIDE1-1,qAR,MM0RFN-10:=L1ZVWMdZh# !GLoRa APRS Batt=0.28V
20260209125638	MM0EFI-3>APLRG1,WIDE1-1,qAR,MM0EFI-10:=L1ZVWMdZh# !GLoRa APRS Batt=0.28V
20260209132639	MM0EFI-3>APLRG1,WIDE1-1,qAR,MM0RFN-10:=L1ZVWMdZh# !GLoRa APRS Batt=0.28V
20260209135639	MM0EFI-3>APLRG1,WIDE1-1,qAR,MM0EFI-10:=L1ZVWMdZh# !GLoRa APRS Batt=0.29V
20260209142639	MM0EFI-3>APLRG1,WIDE1-1,qAR,MM0RFN-10:=L1ZVWMdZh# !GLoRa APRS Batt=0.28V
20260209145638	MM0EFI-3>APLRG1,WIDE1-1,qAR,MM0RFN-10:=L1ZVWMdZh# !GLoRa APRS Batt=0.28V