APRS Packet Errors for PA3GYK-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
20260208163939PA3GYK-10>APLRG1,WIDE1-1,qAO,PI6SHB-10:=L4AH1OnDN& !GLoRa APRS test
20260208165839PA3GYK-10>APLRG1,WIDE1-1,qAO,PI6SHB-10:=L4AH1OnDN& !GLoRa APRS test
20260208171739PA3GYK-10>APLRG1,WIDE1-1,qAO,PI6SHB-10:=L4AH1OnDN& !GLoRa APRS test
20260208173639PA3GYK-10>APLRG1,WIDE1-1,qAO,PI6SHB-10:=L4AH1OnDN& !GLoRa APRS test
20260208175539PA3GYK-10>APLRG1,WIDE1-1,qAO,PI6SHB-10:=L4AH1OnDN& !GLoRa APRS test
20260208191139PA3GYK-10>APLRG1,WIDE1-1,qAO,PI6SHB-10:=L4AH1OnDN& !GLoRa APRS test
20260208194939PA3GYK-10>APLRG1,WIDE1-1,qAO,PI6SHB-10:=L4AH1OnDN& !GLoRa APRS test
20260208200839PA3GYK-10>APLRG1,WIDE1-1,qAO,PI6SHB-10:=L4AH1OnDN& !GLoRa APRS test
20260208202739PA3GYK-10>APLRG1,WIDE1-1,qAO,PI6SHB-10:=L4AH1OnDN& !GLoRa APRS test
20260208204639PA3GYK-10>APLRG1,WIDE1-1,qAO,PI6SHB-10:=L4AH1OnDN& !GLoRa APRS test
20260208210539PA3GYK-10>APLRG1,WIDE1-1,qAO,PI6SHB-10:=L4AH1OnDN& !GLoRa APRS test
20260208212439PA3GYK-10>APLRG1,WIDE1-1,qAO,PI6SHB-10:=L4AH1OnDN& !GLoRa APRS test
20260208214339PA3GYK-10>APLRG1,WIDE1-1,qAO,PI6SHB-10:=L4AH1OnDN& !GLoRa APRS test
20260208220239PA3GYK-10>APLRG1,WIDE1-1,qAO,PI6SHB-10:=L4AH1OnDN& !GLoRa APRS test
20260208222139PA3GYK-10>APLRG1,WIDE1-1,qAO,PI6SHB-10:=L4AH1OnDN& !GLoRa APRS test