APRS Packet Errors for DL1BIR-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
20251016122008	DL1BIR-10>APLRG1,WIDE1-1,qAR,DB0BHV-L4:!LoRa APRS Uwe I56 on tour Batt=4.18V
20251016123509	DL1BIR-10>APLRG1,WIDE1-1,qAR,DB0BHV-L4:!LoRa APRS Uwe I56 on tour Batt=4.18V
20251016132009	DL1BIR-10>APLRG1,WIDE1-1,qAR,DB0BHV-L4:!LoRa APRS Uwe I56 on tour Batt=4.18V
20251016133509	DL1BIR-10>APLRG1,WIDE1-1,qAR,DB0BHV-L4:!LoRa APRS Uwe I56 on tour Batt=4.18V
20251016140509	DL1BIR-10>APLRG1,WIDE1-1,qAR,DB0BHV-L4:!LoRa APRS Uwe I56 on tour Batt=4.18V
20251016145010	DL1BIR-10>APLRG1,WIDE1-1,qAR,DB0BHV-L4:!LoRa APRS Uwe I56 on tour Batt=4.18V
20251016152010	DL1BIR-10>APLRG1,WIDE1-1,qAR,DB0BHV-L4:!LoRa APRS Uwe I56 on tour Batt=4.18V
20251016153510	DL1BIR-10>APLRG1,WIDE1-1,qAR,DB0BHV-L4:!LoRa APRS Uwe I56 on tour Batt=4.18V
20251016165010	DL1BIR-10>APLRG1,WIDE1-1,qAR,DB0BHV-L4:!LoRa APRS Uwe I56 on tour Batt=4.18V
20251016172011	DL1BIR-10>APLRG1,WIDE1-1,qAR,DB0BHV-L4:!LoRa APRS Uwe I56 on tour Batt=4.18V
20251016180511	DL1BIR-10>APLRG1,WIDE1-1,qAR,DB0BHV-L4:!LoRa APRS Uwe I56 on tour Batt=4.18V