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
20260524140033SV9FBT-12>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 438.175000 TX: 438.175000
20260524141533SV9FBT-12>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 438.175000 TX: 438.175000
20260524143033SV9FBT-12>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 438.175000 TX: 438.175000
20260524144533SV9FBT-12>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 438.175000 TX: 438.175000
20260524150033SV9FBT-12>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 438.175000 TX: 438.175000
20260524151533SV9FBT-12>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 438.175000 TX: 438.175000
20260524153033SV9FBT-12>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 438.175000 TX: 438.175000
20260524154533SV9FBT-12>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 438.175000 TX: 438.175000
20260524160033SV9FBT-12>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 438.175000 TX: 438.175000
20260524161533SV9FBT-12>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 438.175000 TX: 438.175000
20260524163033SV9FBT-12>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 438.175000 TX: 438.175000
20260524164533SV9FBT-12>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 438.175000 TX: 438.175000
20260524170033SV9FBT-12>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 438.175000 TX: 438.175000
20260524171533SV9FBT-12>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 438.175000 TX: 438.175000
20260524173033SV9FBT-12>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 438.175000 TX: 438.175000
20260524174533SV9FBT-12>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 438.175000 TX: 438.175000
20260524180033SV9FBT-12>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 438.175000 TX: 438.175000
20260524181533SV9FBT-12>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 438.175000 TX: 438.175000
20260524183033SV9FBT-12>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 438.175000 TX: 438.175000
20260524184533SV9FBT-12>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 438.175000 TX: 438.175000
20260524190033SV9FBT-12>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 438.175000 TX: 438.175000
20260524191533SV9FBT-12>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 438.175000 TX: 438.175000
20260524193033SV9FBT-12>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 438.175000 TX: 438.175000
20260524194533SV9FBT-12>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 438.175000 TX: 438.175000