APRS Packet Errors for BH5HSJ-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
20260208131039	BH5HSJ-2>APFMO2,TCPIP*,qAC,T2CS:=3009.11NF12004.93EiE1[Hello FMO]
20260208134045	BH5HSJ-2>APFMO2,TCPIP*,qAC,T2CS:=3009.11NF12004.93EiE1[Hello FMO]
20260208141018	BH5HSJ-2>APFMO2,TCPIP*,qAC,T2CS:=3009.11NF12004.93EiE1[Hello FMO]
20260208144021	BH5HSJ-2>APFMO2,TCPIP*,qAC,T2CS:=3009.11NF12004.93EiE1[Hello FMO]
20260208151023	BH5HSJ-2>APFMO2,TCPIP*,qAC,T2CS:=3009.11NF12004.93EiE1[Hello FMO]
20260208154027	BH5HSJ-2>APFMO2,TCPIP*,qAC,T2CS:=3009.11NF12004.93EiE1[Hello FMO]
20260208161054	BH5HSJ-2>APFMO0,TCPIP*,qAC,T2YANTAI:=3009.11NF12004.93EiFMO-CLIENT,ONLINE,159,447,F5000KM,NN70gc,甘肃集群中继,SIGN:FZZ/tl1LdrxO5jP3hZfKyA==
20260208164048	BH5HSJ-2>APFMO2,TCPIP*,qAC,T2YANTAI:=3009.11NF12004.93EiE1[Hello FMO]
20260208171021	BH5HSJ-2>APFMO2,TCPIP*,qAC,T2YANTAI:=3009.11NF12004.93EiE1[Hello FMO]
20260208174024	BH5HSJ-2>APFMO2,TCPIP*,qAC,T2YANTAI:=3009.11NF12004.93EiE1[Hello FMO]
20260208181027	BH5HSJ-2>APFMO2,TCPIP*,qAC,T2YANTAI:=3009.11NF12004.93EiE1[Hello FMO]
20260208184030	BH5HSJ-2>APFMO2,TCPIP*,qAC,T2YANTAI:=3009.11NF12004.93EiE1[Hello FMO]