APRS Packet Errors for HG9MFT-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
20260209093640HG9MFT-10>APLRG1,TCPIP*,qAC,T2HUN:!L61KqSe+?_ xGLoRa iGate Batt=4.12V
20260209094839HG9MFT-10>APLRG1,TCPIP*,qAC,T2CSNGRAD:!L61KqSe+?_ xGLoRa iGate Batt=4.12V
20260209101740HG9MFT-10>APLRG1,TCPIP*,qAC,T2CSNGRAD:!L61KqSe+?_ xGLoRa iGate Batt=4.12V
20260209104640HG9MFT-10>APLRG1,TCPIP*,qAC,T2CSNGRAD:!L61KqSe+?_ xGLoRa iGate Batt=4.12V
20260209111540HG9MFT-10>APLRG1,TCPIP*,qAC,T2CSNGRAD:!L61KqSe+?_ xGLoRa iGate Batt=4.12V
20260209114440HG9MFT-10>APLRG1,TCPIP*,qAC,T2CSNGRAD:!L61KqSe+?_ xGLoRa iGate Batt=4.12V
20260209121340HG9MFT-10>APLRG1,TCPIP*,qAC,T2CSNGRAD:!L61KqSe+?_ xGLoRa iGate Batt=4.12V
20260209124240HG9MFT-10>APLRG1,TCPIP*,qAC,T2CSNGRAD:!L61KqSe+?_ xGLoRa iGate Batt=4.12V
20260209131140HG9MFT-10>APLRG1,TCPIP*,qAC,T2CSNGRAD:!L61KqSe+?_ xGLoRa iGate Batt=4.12V
20260209134040HG9MFT-10>APLRG1,TCPIP*,qAC,T2CSNGRAD:!L61KqSe+?_ xGLoRa iGate Batt=4.12V
20260209140940HG9MFT-10>APLRG1,TCPIP*,qAC,T2CSNGRAD:!L61KqSe+?_ xGLoRa iGate Batt=4.12V
20260209143841HG9MFT-10>APLRG1,TCPIP*,qAC,T2CSNGRAD:!L61KqSe+?_ xGLoRa iGate Batt=4.12V
20260209150741HG9MFT-10>APLRG1,TCPIP*,qAC,T2CSNGRAD:!L61KqSe+?_ xGLoRa iGate Batt=4.12V