APRS Packet Errors for SM7TNO-2 (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
20260208195039	SM7TNO-2>APRSMC,TCPIP*,qAR,SM7TNO-4:!5747.35N/01414.88E-#JS/B=100/A=000217
20260208202056	SM7TNO-2>APRSMC,TCPIP*,qAR,SM7TNO-4:!5747.35N/01414.88E-#JS/B=100/A=000217
20260208205116	SM7TNO-2>APRSMC,TCPIP*,qAR,SM7TNO-4:!5747.35N/01414.88E-#JS/B=100/A=000217
20260208212129	SM7TNO-2>APRSMC,TCPIP*,qAR,SM7TNO-4:!5747.35N/01414.88E-#JS/B=100/A=000217
20260208215143	SM7TNO-2>APRSMC,TCPIP*,qAR,SM7TNO-4:!5747.35N/01414.88E-#JS/B=100/A=000217
20260208222200	SM7TNO-2>APRSMC,TCPIP*,qAR,SM7TNO-4:!5747.35N/01414.88E-#JS/B=100/A=000217
20260208225214	SM7TNO-2>APRSMC,TCPIP*,qAR,SM7TNO-4:!5747.35N/01414.88E-#JS/B=100/A=000217
20260208232232	SM7TNO-2>APRSMC,TCPIP*,qAR,SM7TNO-4:!5747.35N/01414.88E-#JS/B=100/A=000217
20260208235244	SM7TNO-2>APRSMC,TCPIP*,qAR,SM7TNO-4:!5747.35N/01414.88E-#JS/B=100/A=000217
20260209002259	SM7TNO-2>APRSMC,TCPIP*,qAR,SM7TNO-4:!5747.35N/01414.88E-#JS/B=100/A=000217
20260209005311	SM7TNO-2>APRSMC,TCPIP*,qAR,SM7TNO-4:!5747.35N/01414.88E-#JS/B=100/A=000217
20260209012329	SM7TNO-2>APRSMC,TCPIP*,qAR,SM7TNO-4:!5747.35N/01414.88E-#JS/B=100/A=000217