APRS Packet Errors for HP2NIC-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
20260209131717HP2NIC-10>APLRG1,TCPIP*,qAC,T2PANAMA:=LItpc:Dp%a !GLoRa APRS iGate ADC Prueba 433.775 Mhz
20260209134717HP2NIC-10>APLRG1,TCPIP*,qAC,T2PANAMA:=LItpc:Dp%a !GLoRa APRS iGate ADC Prueba 433.775 Mhz
20260209141717HP2NIC-10>APLRG1,TCPIP*,qAC,T2PANAMA:=LItpc:Dp%a !GLoRa APRS iGate ADC Prueba 433.775 Mhz
20260209144723HP2NIC-10>APLRG1,TCPIP*,qAC,T2PANAMA:=LItpc:Dp%a !GLoRa APRS iGate ADC Prueba 433.775 Mhz
20260209151723HP2NIC-10>APLRG1,TCPIP*,qAC,T2PANAMA:=LItpc:Dp%a !GLoRa APRS iGate ADC Prueba 433.775 Mhz
20260209154723HP2NIC-10>APLRG1,TCPIP*,qAC,T2PANAMA:=LItpc:Dp%a !GLoRa APRS iGate ADC Prueba 433.775 Mhz
20260209161723HP2NIC-10>APLRG1,TCPIP*,qAC,T2PANAMA:=LItpc:Dp%a !GLoRa APRS iGate ADC Prueba 433.775 Mhz
20260209164724HP2NIC-10>APLRG1,TCPIP*,qAC,T2PANAMA:=LItpc:Dp%a !GLoRa APRS iGate ADC Prueba 433.775 Mhz
20260209171724HP2NIC-10>APLRG1,TCPIP*,qAC,T2PANAMA:=LItpc:Dp%a !GLoRa APRS iGate ADC Prueba 433.775 Mhz
20260209174724HP2NIC-10>APLRG1,TCPIP*,qAC,T2PANAMA:=LItpc:Dp%a !GLoRa APRS iGate ADC Prueba 433.775 Mhz
20260209181724HP2NIC-10>APLRG1,TCPIP*,qAC,T2PANAMA:=LItpc:Dp%a !GLoRa APRS iGate ADC Prueba 433.775 Mhz
20260209184724HP2NIC-10>APLRG1,TCPIP*,qAC,T2PANAMA:=LItpc:Dp%a !GLoRa APRS iGate ADC Prueba 433.775 Mhz