APRS Packet Errors for R2DWL-15 (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
20260209090237R2DWL-15>APLRG1,TCPIP*,qAC,T2BC:!L2fVyX+Yu# GLoRa_APRS
20260209092237R2DWL-15>APLRG1,TCPIP*,qAC,T2BC:!L2fVyX+Yu# GLoRa_APRS
20260209094237R2DWL-15>APLRG1,TCPIP*,qAC,T2BC:!L2fVyX+Yu# GLoRa_APRS
20260209100237R2DWL-15>APLRG1,TCPIP*,qAC,T2BC:!L2fVyX+Yu# GLoRa_APRS
20260209102237R2DWL-15>APLRG1,TCPIP*,qAC,T2BC:!L2fVyX+Yu# GLoRa_APRS
20260209104237R2DWL-15>APLRG1,TCPIP*,qAC,T2BC:!L2fVyX+Yu# GLoRa_APRS
20260209110237R2DWL-15>APLRG1,TCPIP*,qAC,T2BC:!L2fVyX+Yu# GLoRa_APRS
20260209112238R2DWL-15>APLRG1,TCPIP*,qAC,T2BC:!L2fVyX+Yu# GLoRa_APRS
20260209114238R2DWL-15>APLRG1,TCPIP*,qAC,T2BC:!L2fVyX+Yu# GLoRa_APRS
20260209120238R2DWL-15>APLRG1,TCPIP*,qAC,T2BC:!L2fVyX+Yu# GLoRa_APRS
20260209122238R2DWL-15>APLRG1,TCPIP*,qAC,T2BC:!L2fVyX+Yu# GLoRa_APRS
20260209124238R2DWL-15>APLRG1,TCPIP*,qAC,T2BC:!L2fVyX+Yu# GLoRa_APRS
20260209130238R2DWL-15>APLRG1,TCPIP*,qAC,T2BC:!L2fVyX+Yu# GLoRa_APRS
20260209132238R2DWL-15>APLRG1,TCPIP*,qAC,T2BC:!L2fVyX+Yu# GLoRa_APRS
20260209134238R2DWL-15>APLRG1,TCPIP*,qAC,T2BC:!L2fVyX+Yu# GLoRa_APRS
20260209140238R2DWL-15>APLRG1,TCPIP*,qAC,T2BC:!L2fVyX+Yu# GLoRa_APRS
20260209142238R2DWL-15>APLRG1,TCPIP*,qAC,T2BC:!L2fVyX+Yu# GLoRa_APRS
20260209144238R2DWL-15>APLRG1,TCPIP*,qAC,T2BC:!L2fVyX+Yu# GLoRa_APRS