APRS Packet Errors for VE7LTN-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
20250911221539	VE7LTN-10>APMI04,TCPIP*,qAS,VE7LTN:@000000z0000.00N/00000.00EMWX3in1Mini U=12.7V
20250911224539	VE7LTN-10>APMI04,TCPIP*,qAS,VE7LTN:@000000z0000.00N/00000.00EMWX3in1Mini U=12.7V
20250911231539	VE7LTN-10>APMI04,TCPIP*,qAS,VE7LTN:@000000z0000.00N/00000.00EMWX3in1Mini U=12.7V
20250911234539	VE7LTN-10>APMI04,TCPIP*,qAS,VE7LTN:@000000z0000.00N/00000.00EMWX3in1Mini U=12.7V
20250912001539	VE7LTN-10>APMI04,TCPIP*,qAS,VE7LTN:@000000z0000.00N/00000.00EMWX3in1Mini U=12.7V
20250912004539	VE7LTN-10>APMI04,TCPIP*,qAS,VE7LTN:@000000z0000.00N/00000.00EMWX3in1Mini U=12.7V
20250912011539	VE7LTN-10>APMI04,TCPIP*,qAS,VE7LTN:@000000z0000.00N/00000.00EMWX3in1Mini U=12.7V
20250912014539	VE7LTN-10>APMI04,TCPIP*,qAS,VE7LTN:@000000z0000.00N/00000.00EMWX3in1Mini U=12.7V
20250912021539	VE7LTN-10>APMI04,TCPIP*,qAS,VE7LTN:@000000z0000.00N/00000.00EMWX3in1Mini U=12.7V
20250912024538	VE7LTN-10>APMI04,TCPIP*,qAS,VE7LTN:@000000z0000.00N/00000.00EMWX3in1Mini U=12.7V
20250912031538	VE7LTN-10>APMI04,TCPIP*,qAS,VE7LTN:@000000z0000.00N/00000.00EMWX3in1Mini U=12.7V
20250912034538	VE7LTN-10>APMI04,TCPIP*,qAS,VE7LTN:@000000z0000.00N/00000.00EMWX3in1Mini U=12.7V