APRS Packet Errors for HA9MJ-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
20260208153318HA9MJ-10>APLRG1,TCPIP*,qAC,T2CSNGRAD:!L67$1ShDt_ G.../...g...t060h40b10082LoRa APRS Batt=4.20V
20260208163318HA9MJ-10>APLRG1,TCPIP*,qAC,T2CSNGRAD:!L67$1ShDt_ G.../...g...t060h40b10085LoRa APRS Batt=4.14V
20260208163324HA9MJ-10>APLRG1,WIDE1-1,qAR,HA9OZD-17:!L67$1ShDt_ G.../...g...t060h40b10085LoRe0A@qs {#
20260208173318HA9MJ-10>APLRG1,TCPIP*,qAC,T2CSNGRAD:!L67$1ShDt_ G.../...g...t059h40b10087LoRa APRS Batt=4.12V
20260208183318HA9MJ-10>APLRG1,TCPIP*,qAC,T2CSNGRAD:!L67$1ShDt_ G.../...g...t059h40b10094LoRa APRS Batt=4.22V
20260208193318HA9MJ-10>APLRG1,TCPIP*,qAC,T2CSNGRAD:!L67$1ShDt_ G.../...g...t059h41b10098LoRa APRS Batt=4.07V
20260208203319HA9MJ-10>APLRG1,TCPIP*,qAC,T2CSNGRAD:!L67$1ShDt_ G.../...g...t059h41b10101LoRa APRS Batt=4.40V
20260208203324HA9MJ-10>APLRG1,WIDE1-1,qAR,HA9OZD-17:!L67$1ShDt_ G.../...g...t059h41b10101LoRa APY;3Fjp