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
20260208144915SV9FBT-12>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 438.175000 TX: 438.175000
20260208150415SV9FBT-12>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 438.175000 TX: 438.175000
20260208151916SV9FBT-12>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 438.175000 TX: 438.175000
20260208153415SV9FBT-12>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 438.175000 TX: 438.175000
20260208154915SV9FBT-12>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 438.175000 TX: 438.175000
20260208160415SV9FBT-12>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 438.175000 TX: 438.175000
20260208161915SV9FBT-12>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 438.175000 TX: 438.175000
20260208163415SV9FBT-12>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 438.175000 TX: 438.175000
20260208164915SV9FBT-12>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 438.175000 TX: 438.175000
20260208170415SV9FBT-12>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 438.175000 TX: 438.175000
20260208171916SV9FBT-12>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 438.175000 TX: 438.175000
20260208173415SV9FBT-12>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 438.175000 TX: 438.175000
20260208174915SV9FBT-12>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 438.175000 TX: 438.175000
20260208180415SV9FBT-12>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 438.175000 TX: 438.175000
20260208181915SV9FBT-12>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 438.175000 TX: 438.175000
20260208183415SV9FBT-12>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 438.175000 TX: 438.175000
20260208184915SV9FBT-12>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 438.175000 TX: 438.175000
20260208190415SV9FBT-12>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 438.175000 TX: 438.175000
20260208191915SV9FBT-12>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 438.175000 TX: 438.175000
20260208193415SV9FBT-12>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 438.175000 TX: 438.175000
20260208194915SV9FBT-12>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 438.175000 TX: 438.175000
20260208200416SV9FBT-12>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 438.175000 TX: 438.175000
20260208201915SV9FBT-12>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 438.175000 TX: 438.175000
20260208203416SV9FBT-12>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 438.175000 TX: 438.175000