APRS Packet Errors for DL7EE-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
20260208145903DL7EE-10>APLRG1,TCPIP*,qAC,T2CHILE:=L4LeLP7d(& !GLoRa APRS IGate
20260208152903DL7EE-10>APLRG1,TCPIP*,qAC,T2CHILE:=L4LeLP7d(& !GLoRa APRS IGate
20260208155903DL7EE-10>APLRG1,TCPIP*,qAC,T2CHILE:=L4LeLP7d(& !GLoRa APRS IGate
20260208162903DL7EE-10>APLRG1,TCPIP*,qAC,T2CHILE:=L4LeLP7d(& !GLoRa APRS IGate
20260208164321DL7EE-10>APLRG1,TCPIP*,qAC,T2TAS:=L4LeLP7d(& !GLoRa APRS IGate
20260208171321DL7EE-10>APLRG1,TCPIP*,qAC,T2SPAIN:=L4LeLP7d(& !GLoRa APRS IGate
20260208174321DL7EE-10>APLRG1,TCPIP*,qAC,T2SPAIN:=L4LeLP7d(& !GLoRa APRS IGate
20260208181322DL7EE-10>APLRG1,TCPIP*,qAC,T2SPAIN:=L4LeLP7d(& !GLoRa APRS IGate
20260208184323DL7EE-10>APLRG1,TCPIP*,qAC,T2SPAIN:=L4LeLP7d(& !GLoRa APRS IGate
20260208191323DL7EE-10>APLRG1,TCPIP*,qAC,T2SPAIN:=L4LeLP7d(& !GLoRa APRS IGate
20260208194323DL7EE-10>APLRG1,TCPIP*,qAC,T2SPAIN:=L4LeLP7d(& !GLoRa APRS IGate
20260208201323DL7EE-10>APLRG1,TCPIP*,qAC,T2SPAIN:=L4LeLP7d(& !GLoRa APRS IGate
20260208204323DL7EE-10>APLRG1,TCPIP*,qAC,T2SPAIN:=L4LeLP7d(& !GLoRa APRS IGate