APRS Packet Errors for F1FFS-10 (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
20251216114418F1FFS-10>APLRG1,TCPIP*,qAC,T2PANAMA:!LoRa APRS Batt=4.17V
20251216121418F1FFS-10>APLRG1,TCPIP*,qAC,T2PANAMA:!LoRa APRS Batt=4.14V
20251216122919F1FFS-10>APLRG1,TCPIP*,qAC,T2PANAMA:!LoRa APRS Batt=4.14V
20251216124419F1FFS-10>APLRG1,TCPIP*,qAC,T2PANAMA:!LoRa APRS Batt=4.14V
20251216132919F1FFS-10>APLRG1,TCPIP*,qAC,T2PANAMA:!LoRa APRS Batt=4.13V
20251216142922F1FFS-10>APLRG1,TCPIP*,qAC,T2PANAMA:!LoRa APRS Batt=4.12V
20251216145921F1FFS-10>APLRG1,TCPIP*,qAC,T2PANAMA:!LoRa APRS Batt=4.12V