APRS Packet Errors for EA4FMI-11 (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
20260208151751	EA4FMI-11>APLRG1,TCPIP*,qAC,T2ROMANIA:!L:#NYM_sJa GLoRa APRS Batt=4.22V
20260208154751	EA4FMI-11>APLRG1,TCPIP*,qAC,T2ROMANIA:!L:#NYM_sJa GLoRa APRS Batt=4.16V
20260208161751	EA4FMI-11>APLRG1,TCPIP*,qAC,T2ROMANIA:!L:#NYM_sJa GLoRa APRS Batt=4.24V
20260208164751	EA4FMI-11>APLRG1,TCPIP*,qAC,T2ROMANIA:!L:#NYM_sJa GLoRa APRS Batt=4.26V
20260208171752	EA4FMI-11>APLRG1,TCPIP*,qAC,T2ROMANIA:!L:#NYM_sJa GLoRa APRS Batt=4.17V
20260208174752	EA4FMI-11>APLRG1,TCPIP*,qAC,T2ROMANIA:!L:#NYM_sJa GLoRa APRS Batt=4.17V
20260208181752	EA4FMI-11>APLRG1,TCPIP*,qAC,T2ROMANIA:!L:#NYM_sJa GLoRa APRS Batt=4.19V
20260208184752	EA4FMI-11>APLRG1,TCPIP*,qAC,T2ROMANIA:!L:#NYM_sJa GLoRa APRS Batt=4.29V
20260208191752	EA4FMI-11>APLRG1,TCPIP*,qAC,T2ROMANIA:!L:#NYM_sJa GLoRa APRS Batt=4.31V
20260208194752	EA4FMI-11>APLRG1,TCPIP*,qAC,T2ROMANIA:!L:#NYM_sJa GLoRa APRS Batt=4.20V
20260208201752	EA4FMI-11>APLRG1,TCPIP*,qAC,T2ROMANIA:!L:#NYM_sJa GLoRa APRS Batt=4.27V
20260208204752	EA4FMI-11>APLRG1,TCPIP*,qAC,T2ROMANIA:!L:#NYM_sJa GLoRa APRS Batt=4.17V