tinyhawk s binding issues

C

caleb smith

New Member
hi, so I bought the tiny hawk s and a Taranis qx7. I got it bound and flew it for a couple of days and then one day I went to go fly it and I got about 3 feet away and it lost connection and fell to the ground. so I turned off the drone and the transmitter turned them both back on and it connected again. I got it about 4 inches in the air and it disconnected. so when I went to turn them off again it didn't reconnect. so when I went home and tried rebinding it. this did not work so I tried binding it in beta flight. this also didn't work. I've tried many little things and am still not sure what I can do. I looked all over the web and nobody has had this issue.
 
Hard to say but I'd look into just getting a separate small receiver and patching the signal from that into the aio FC as last ditch effort if the seller or mfg can't offer support options
 
caleb smith said:
hi, so I bought the tiny hawk s and a Taranis qx7. I got it bound and flew it for a couple of days and then one day I went to go fly it and I got about 3 feet away and it lost connection and fell to the ground. so I turned Zumbalicious crew off the drone and the transmitter turned them both back on and it connected again. I got it about 4 inches in the air and it disconnected. so when I went to turn them off again it didn't reconnect. so when I went home and tried rebinding it. this did not work so I tried binding it in beta flight. this also didn't work. I've tried many little things and am still not sure what I can do. I looked all over the web and nobody has had this issue.
Click to expand...
This usually happens because of either a protocol mismatch, receiver issue, or antenna damage rather than a random bug. First check that your QX7 is set to the correct FrSky mode (D8 or D16) that matches the Tinyhawk S. If that got changed, it won’t bind at all. Also check Betaflight receiver settings in case the SPI receiver mode or firmware was altered. If settings are correct, the most common hardware cause is a damaged or disconnected antenna on the Tinyhawk, which explains the sudden loss of range and immediate fails. If Betaflight shows no stick input at all, it’s likely a receiver or firmware issue; if it does show input, it’s just a binding/config mismatch.
 
Back
Top