APRS Packet Errors for I2RIT-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
20260208151229I2RIT-10>APLRG1,WIDE1-1,qAR,IW2DPO-10:=L7R*DPm2G& !GLoRa APRS Batt=4.26V
20260208155229I2RIT-10>APLRG1,WIDE1-1,qAR,IW2DPO-10:=L7R*DPm2G& !GLoRa APRS Batt=4.25V
20260208165229I2RIT-10>APLRG1,WIDE1-1,qAO,IW2HUZ-10:=L7R*DPm2G& !GLoRa APRS Batt=4.25V
20260208171229I2RIT-10>APLRG1,WIDE1-1,qAR,IW2DPO-10:=L7R*DPm2G& !GLoRa APRS Batt=4.26V
20260208175230I2RIT-10>APLRG1,WIDE1-1,qAO,IW2HUZ-10:=L7R*DPm2G& !GLoRa APRS Batt=4.26V
20260208181230I2RIT-10>APLRG1,WIDE1-1,qAO,IW2HUZ-10:=L7R*DPm2G& !GLoRa APRS Batt=4.25V
20260208185230I2RIT-10>APLRG1,WIDE1-1,qAO,IW2HUZ-10:=L7R*DPm2G& !GLoRa APRS Batt=4.26V
20260208191230I2RIT-10>APLRG1,WIDE1-1,qAO,IW2HUZ-10:=L7R*DPm2G& !GLoRa APRS Batt=4.25V
20260208195234I2RIT-10>APLRG1,WIDE1-1,qAO,IU2SKJ-10:=L7R*DPm2G& !GLoRa APRS Batt=4.25V
20260208201230I2RIT-10>APLRG1,WIDE1-1,qAR,IW2DPO-10:=L7R*DPm2G& !GLoRa APRS Batt=4.25V