APRS Packet Errors for CT2HIB-10 (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
20260208143438	CT2HIB-10>APLRG1,TCPIP*,qAC,T2BC:!L:y(9L1Q:a !GLoRa APRS Batt=4.27V
20260208150438	CT2HIB-10>APLRG1,TCPIP*,qAC,T2BC:!L:y(9L1Q:a !GLoRa APRS Batt=4.27V
20260208153438	CT2HIB-10>APLRG1,TCPIP*,qAC,T2BC:!L:y(9L1Q:a !GLoRa APRS Batt=4.26V
20260208160438	CT2HIB-10>APLRG1,TCPIP*,qAC,T2BC:!L:y(9L1Q:a !GLoRa APRS Batt=4.27V
20260208163438	CT2HIB-10>APLRG1,TCPIP*,qAC,T2BC:!L:y(9L1Q:a !GLoRa APRS Batt=4.28V
20260208170439	CT2HIB-10>APLRG1,TCPIP*,qAC,T2BC:!L:y(9L1Q:a !GLoRa APRS Batt=4.27V
20260208173439	CT2HIB-10>APLRG1,TCPIP*,qAC,T2BC:!L:y(9L1Q:a !GLoRa APRS Batt=4.27V
20260208180439	CT2HIB-10>APLRG1,TCPIP*,qAC,T2BC:!L:y(9L1Q:a !GLoRa APRS Batt=4.28V
20260208183439	CT2HIB-10>APLRG1,TCPIP*,qAC,T2BC:!L:y(9L1Q:a !GLoRa APRS Batt=4.26V
20260208190439	CT2HIB-10>APLRG1,TCPIP*,qAC,T2BC:!L:y(9L1Q:a !GLoRa APRS Batt=4.29V
20260208193439	CT2HIB-10>APLRG1,TCPIP*,qAC,T2BC:!L:y(9L1Q:a !GLoRa APRS Batt=4.25V
20260208200439	CT2HIB-10>APLRG1,TCPIP*,qAC,T2BC:!L:y(9L1Q:a !GLoRa APRS Batt=4.28V