APRS Packet Errors for IW3BRC-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
20260208163002IW3BRC-2>TLM,TCPIP*,qAC,T2SPAIN:=4640.29N/01109.86EEmyPi23-CPU-Temp
20260208170001IW3BRC-2>TLM,TCPIP*,qAC,T2ERFURT:=4640.29N/01109.86EEmyPi23
20260208173001IW3BRC-2>TLM,TCPIP*,qAC,T2CSNGRAD:=4640.29N/01109.86EEmyPi23-CPU-Temp
20260208180002IW3BRC-2>TLM,TCPIP*,qAC,T2SPAIN:=4640.29N/01109.86EEmyPi23
20260208183001IW3BRC-2>TLM,TCPIP*,qAC,T2BIO:=4640.29N/01109.86EEmyPi23-CPU-Temp
20260208190002IW3BRC-2>TLM,TCPIP*,qAC,T2UK:=4640.29N/01109.86EEmyPi23
20260208193001IW3BRC-2>TLM,TCPIP*,qAC,T2DENMARK:=4640.29N/01109.86EEmyPi23-CPU-Temp
20260208200002IW3BRC-2>TLM,TCPIP*,qAC,T2SPAIN:=4640.29N/01109.86EEmyPi23
20260208203001IW3BRC-2>TLM,TCPIP*,qAC,T2CSNGRAD:=4640.29N/01109.86EEmyPi23-CPU-Temp
20260208210002IW3BRC-2>TLM,TCPIP*,qAC,T2SPAIN:=4640.29N/01109.86EEmyPi23
20260208213001IW3BRC-2>TLM,TCPIP*,qAC,T2CZECH:=4640.29N/01109.86EEmyPi23-CPU-Temp
20260208220002IW3BRC-2>TLM,TCPIP*,qAC,T2GB:=4640.29N/01109.86EEmyPi23