APRS Packet Errors for SV9FBT-12 (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
20251104100246	SV9FBT-12>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 438.175000 TX: 438.175000
20251104101746	SV9FBT-12>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 438.175000 TX: 438.175000
20251104103247	SV9FBT-12>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 438.175000 TX: 438.175000
20251104110246	SV9FBT-12>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 438.175000 TX: 438.175000
20251104111746	SV9FBT-12>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 438.175000 TX: 438.175000
20251104113247	SV9FBT-12>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 438.175000 TX: 438.175000
20251104114746	SV9FBT-12>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 438.175000 TX: 438.175000
20251104120246	SV9FBT-12>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 438.175000 TX: 438.175000
20251104121747	SV9FBT-12>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 438.175000 TX: 438.175000
20251104123246	SV9FBT-12>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 438.175000 TX: 438.175000
20251104124746	SV9FBT-12>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 438.175000 TX: 438.175000
20251104130246	SV9FBT-12>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 438.175000 TX: 438.175000
20251104131747	SV9FBT-12>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 438.175000 TX: 438.175000
20251104133246	SV9FBT-12>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 438.175000 TX: 438.175000
20251104134746	SV9FBT-12>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 438.175000 TX: 438.175000
20251104140247	SV9FBT-12>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 438.175000 TX: 438.175000
20251104141746	SV9FBT-12>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 438.175000 TX: 438.175000
20251104143246	SV9FBT-12>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 438.175000 TX: 438.175000
20251104144747	SV9FBT-12>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 438.175000 TX: 438.175000
20251104150247	SV9FBT-12>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 438.175000 TX: 438.175000
20251104151746	SV9FBT-12>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 438.175000 TX: 438.175000
20251104153246	SV9FBT-12>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 438.175000 TX: 438.175000