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
20260209133318	HA9MJ-10>APLRG1,TCPIP*,qAC,T2CSNGRAD:!L67$1ShDt_ G.../...g...t060h41b10121LoRa APRS Batt=4.32V
20260209143318	HA9MJ-10>APLRG1,TCPIP*,qAC,T2CSNGRAD:!L67$1ShDt_ G.../...g...t067h36b10122LoRa APRS Batt=4.29V
20260209153318	HA9MJ-10>APLRG1,TCPIP*,qAC,T2CSNGRAD:!L67$1ShDt_ G.../...g...t071h35b10124LoRa APRS Batt=4.26V
20260209163318	HA9MJ-10>APLRG1,TCPIP*,qAC,T2CSNGRAD:!L67$1ShDt_ G.../...g...t074h33b10123LoRa APRS Batt=4.27V
20260209173319	HA9MJ-10>APLRG1,TCPIP*,qAC,T2CSNGRAD:!L67$1ShDt_ G.../...g...t076h33b10123LoRa APRS Batt=4.29V
20260209183319	HA9MJ-10>APLRG1,TCPIP*,qAC,T2CSNGRAD:!L67$1ShDt_ G.../...g...t077h33b10123LoRa APRS Batt=4.10V