APRS Packet Errors for ON7MOR-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
20260208163718ON7MOR-10>APLRG1,TCPIP*,qAC,T2CSNGRAD:!L4Mv(OZSH_ G.../...g...t048h..b10086LoRa APRS 433.775 - Heltec v3 + P280
20260208165218ON7MOR-10>APLRG1,TCPIP*,qAC,T2CSNGRAD:!L4Mv(OZSH_ G.../...g...t047h..b10087LoRa APRS 433.775 - Heltec v3 + P280
20260208170718ON7MOR-10>APLRG1,TCPIP*,qAC,T2CSNGRAD:!L4Mv(OZSH_ G.../...g...t045h..b10090LoRa APRS 433.775 - Heltec v3 + P280
20260208172218ON7MOR-10>APLRG1,TCPIP*,qAC,T2CSNGRAD:!L4Mv(OZSH_ G.../...g...t045h..b10091LoRa APRS 433.775 - Heltec v3 + P280
20260208173719ON7MOR-10>APLRG1,TCPIP*,qAC,T2CSNGRAD:!L4Mv(OZSH_ G.../...g...t045h..b10092LoRa APRS 433.775 - Heltec v3 + P280
20260208175219ON7MOR-10>APLRG1,TCPIP*,qAC,T2CSNGRAD:!L4Mv(OZSH_ G.../...g...t045h..b10092LoRa APRS 433.775 - Heltec v3 + P280
20260208180719ON7MOR-10>APLRG1,TCPIP*,qAC,T2CSNGRAD:!L4Mv(OZSH_ G.../...g...t045h..b10092LoRa APRS 433.775 - Heltec v3 + P280
20260208182219ON7MOR-10>APLRG1,TCPIP*,qAC,T2CSNGRAD:!L4Mv(OZSH_ G.../...g...t045h..b10093LoRa APRS 433.775 - Heltec v3 + P280
20260208183719ON7MOR-10>APLRG1,TCPIP*,qAC,T2CSNGRAD:!L4Mv(OZSH_ G.../...g...t045h..b10093LoRa APRS 433.775 - Heltec v3 + P280
20260208185219ON7MOR-10>APLRG1,TCPIP*,qAC,T2CSNGRAD:!L4Mv(OZSH_ G.../...g...t045h..b10095LoRa APRS 433.775 - Heltec v3 + P280
20260208190717ON7MOR-10>APLRG1,TCPIP*,qAC,T2CHILE:!L4Mv(OZSH_ G.../...g...t045h..b10094LoRa APRS 433.775 - Heltec v3 + P280
20260208192217ON7MOR-10>APLRG1,TCPIP*,qAC,T2CHILE:!L4Mv(OZSH_ G.../...g...t045h..b10095LoRa APRS 433.775 - Heltec v3 + P280
20260208193717ON7MOR-10>APLRG1,TCPIP*,qAC,T2CHILE:!L4Mv(OZSH_ G.../...g...t045h..b10096LoRa APRS 433.775 - Heltec v3 + P280
20260208195218ON7MOR-10>APLRG1,TCPIP*,qAC,T2CHILE:!L4Mv(OZSH_ G.../...g...t044h..b10095LoRa APRS 433.775 - Heltec v3 + P280
20260208200718ON7MOR-10>APLRG1,TCPIP*,qAC,T2CHILE:!L4Mv(OZSH_ G.../...g...t043h..b10095LoRa APRS 433.775 - Heltec v3 + P280
20260208202218ON7MOR-10>APLRG1,TCPIP*,qAC,T2CHILE:!L4Mv(OZSH_ G.../...g...t043h..b10094LoRa APRS 433.775 - Heltec v3 + P280
20260208203718ON7MOR-10>APLRG1,TCPIP*,qAC,T2CHILE:!L4Mv(OZSH_ G.../...g...t042h..b10093LoRa APRS 433.775 - Heltec v3 + P280
20260208205218ON7MOR-10>APLRG1,TCPIP*,qAC,T2CHILE:!L4Mv(OZSH_ G.../...g...t042h..b10094LoRa APRS 433.775 - Heltec v3 + P280
20260208210718ON7MOR-10>APLRG1,TCPIP*,qAC,T2CHILE:!L4Mv(OZSH_ G.../...g...t042h..b10093LoRa APRS 433.775 - Heltec v3 + P280
20260208212218ON7MOR-10>APLRG1,TCPIP*,qAC,T2CHILE:!L4Mv(OZSH_ G.../...g...t041h..b10094LoRa APRS 433.775 - Heltec v3 + P280
20260208213718ON7MOR-10>APLRG1,TCPIP*,qAC,T2CHILE:!L4Mv(OZSH_ G.../...g...t041h..b10094LoRa APRS 433.775 - Heltec v3 + P280
20260208215218ON7MOR-10>APLRG1,TCPIP*,qAC,T2CHILE:!L4Mv(OZSH_ G.../...g...t041h..b10094LoRa APRS 433.775 - Heltec v3 + P280
20260208220719ON7MOR-10>APLRG1,TCPIP*,qAC,T2CHILE:!L4Mv(OZSH_ G.../...g...t041h..b10092LoRa APRS 433.775 - Heltec v3 + P280
20260208222219ON7MOR-10>APLRG1,TCPIP*,qAC,T2CHILE:!L4Mv(OZSH_ G.../...g...t040h..b10092LoRa APRS 433.775 - Heltec v3 + P280