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
20260626024534SV9FBT-12>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 438.175000 TX: 438.175000
20260626030034SV9FBT-12>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 438.175000 TX: 438.175000
20260626031534SV9FBT-12>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 438.175000 TX: 438.175000
20260626033035SV9FBT-12>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 438.175000 TX: 438.175000
20260626034534SV9FBT-12>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 438.175000 TX: 438.175000
20260626040034SV9FBT-12>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 438.175000 TX: 438.175000
20260626041534SV9FBT-12>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 438.175000 TX: 438.175000
20260626043035SV9FBT-12>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 438.175000 TX: 438.175000
20260626044535SV9FBT-12>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 438.175000 TX: 438.175000
20260626050035SV9FBT-12>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 438.175000 TX: 438.175000
20260626051534SV9FBT-12>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 438.175000 TX: 438.175000
20260626053035SV9FBT-12>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 438.175000 TX: 438.175000
20260626054535SV9FBT-12>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 438.175000 TX: 438.175000
20260626060034SV9FBT-12>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 438.175000 TX: 438.175000
20260626061535SV9FBT-12>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 438.175000 TX: 438.175000
20260626063034SV9FBT-12>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 438.175000 TX: 438.175000
20260626064534SV9FBT-12>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 438.175000 TX: 438.175000
20260626070035SV9FBT-12>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 438.175000 TX: 438.175000
20260626071535SV9FBT-12>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 438.175000 TX: 438.175000
20260626073034SV9FBT-12>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 438.175000 TX: 438.175000
20260626074535SV9FBT-12>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 438.175000 TX: 438.175000
20260626080035SV9FBT-12>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 438.175000 TX: 438.175000
20260626081535SV9FBT-12>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 438.175000 TX: 438.175000
20260626083034SV9FBT-12>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 438.175000 TX: 438.175000