I had to also go in and redo the modes for the transmitter so that it actually worked with the RTF transmitter. Tinyhawk 2 not binding. You bind to D8 the same way. I've tried applying the factory cli dump from emax's website. I have tried putting the controller in bind mode first, after the drone is in on (since I cant get it into the green light bind mode), and all sorts of things. I am not only new to drones but to reddit...so congrats on popping my reddit cherry... that being said, I also cannot get my TH to bind to my RTF controller that came with it. # dump ###WARNING: NO CUSTOM DEFAULTS FOUND### # version # Betaflight / STM32F411 (S411) 4.1.0 Oct 16 2019 / 11:57:34 (c37a7c91a) MSP API: 1.42 # manufacturer_id: MTKS board_name: MATEKF411RX custom defaults: NO # start the command batch batch start board_name MATEKF411RX manufacturer_id MTKS # name: TinyHawk II # resources resource BEEPER 1 C15 resource MOTOR 1 B10 resource MOTOR 2 … Antenna is directly soldered to the board and looks good no issues. Flash the Betaflight MATEK411RX firmware for whichever version you have a CLI dump for. Press question mark to learn the rest of the keyboard shortcuts. Once hooked up th Betaflight it goes into DFU mode and you can update the firmware! I've tried holding the button while powering up the device as well as pressing it while it's already powered on but the lights aren't changing. After (4) CLI "bind_rx_spi", the BF replies with "Error: Unknown command". It even says on their product page for the Tinyhawk S replacement FC board that it's compatible with the Tinyhawk, Tinyhawk S, and Tinyhawk Freestyle. And Im' just starting out so I might be doing something wrong. The instructions did say that it does work on d16 but for best results to use d8. Mine isn't. So I have it working fully in Project Mockinbird CLI! It's like I decided to do exactly what you did a few months later...Ya get it figured out? Is there anything to verify in Betaflight since it won't even go into binding mode? Bind with the RTF transmitter by setting it to bind mode as well (hold both "down" trim buttons). If so make sure that is in binding mode too. Emax TinyHawk binding issues, no green light. I'm still figuring this out, but I'll have more info later. The Tinyhawk S is new, the Q X7 I got used. Shouldn't the bind on the TH change the colors? Its not plugged into the computer at the time and I know I'm holding the button down. Then go back into the CLI, and run: bind_rx_spi (If you are using BF 3.X.X the command is frsky_bind) Your quad will enter binding mode. I'm have the same problem and saintbob has been helpful. Trying both D8 and D16, nothing works. Yes its the RTF transmitter. That doesn*t work. Frsky Taranis X-Lite Pro Binding with Tinyhawk-S I can not bind the X-Lite Pro to the Tinyhawk-S in Frsky-X mode in Betaflight. The Taranis Frsky X-Lite Pro is flashed to Open-Tx 2.3.0 and the internal transmitter is flashed to the latest firmware available from Frsky. Does your T16 work fine with other quads bound in D16 mode?
For the tinyhawk, power on the quad. Right down to different firmware and the wrong targets. I guess Emax is doing this now? Hey All!I recently flashed my Tinyhawk RTF but now I'm unable to get the TinyHawk to enter bind mode. Now I need to fiddle with the betaflight settings, what I've noticed is the Project Mockingbird directions are all for an older betaflight. (For the rtf transmitter is holding same buttons then power cycling). I flashed my Tinyhawk with the latest Betaflight 4.0.6 firmware, for the MATEKF411RX target (NOT the MATEKF411) Then, I set the receiver mode to Frsky_D in Configuration. (If you are using BF 3.X.X the command is frsky_bind). Hold down the two down trims on either side to get into bind mode. I've tried it with the plastic on and off but same results. I've read that it's not possible to brick this flight controller, but it's starting to seem like it... Yea I haven't found if there's a configuration change that's required in Betaflight. I've had the two down trims and the transmitter in binding mode. Just out of curiosity, I looked up pictures of the Tinyhawk S board and the Tinyhawk board and compared them side-by-side. Now it flies and everything! Try updating the firmware on your T16 to the latest versions anyway and see if that solves the issue. Then, change the receiver protocol from FRSKY_D (It was on FRSKY_X by default, and this prevented it from binding). Take the radio out of binding mode by pressing and holding the throttle trim down and pitch trim down buttons for 2 seconds until the red lights turn off. Success!
But I hope to be flying tomorrow, New comments cannot be posted and votes cannot be cast, Press J to jump to the feed. There have been one or two cases on with similar issues here where a replacement Tinyhawk solved the issue. The jumper came with open tx firmware already on it 2.3.2 i updated to 2.3.4. I now get receiver signals and everything. So: I've got myself a betaflight configurator 4.1. The instructions says to power on the Tinyhawk, press the bind buttom for 2 secs, and then press bind on my transmitter. Ive also tried method 2 by typing in CLI command bind_rx and i get error saying command not supported i also tried Bind_rx_spi and it says unknown command.
My Tinyhawk RTF has a Tinyhawk S board in it. So to get rid of the red light make sure you are pressing the boot button and not the bind button! Just flashes red. Tinyhawk 2 not binding. I am following the emax steps but for some reason its just not working. Does your T16 work fine with other quads bound in D16 mode? Then, change the receiver protocol from FRSKY_D (It was on FRSKY_X by default, and this prevented it from binding). When the blue light goes from solid to blinking, it's bound. Make sure you select it appropriately in the radio. But jumper has their own firmware should i just stick with open tx or get the jumper firmware?
I know this is an old post but, yup having the same problem here. Flys good in about 10ft radius but outside of that it wont work. That worked not the thing falls out the sky and says rx fail or rx bad. I followed the steps from SnowLeopard´s post. 12-Jan-2020, 09:03 PM (12-Jan-2020, 08:59 PM) SnowLeopardFPV Wrote: The version of the pre-compiled firmware HEX files on the Jumper website just appear to be older versions of OpenTX (2.2.3 and 2.3.0). Loose antenna, very common for bad range and fail safe. If not then I would contact the supplier of the Tinyhawk and try to get a replacement under warranty. LvFPV Member. I did download bet flight but hesitant to start messing with any of that and ruin a new drone.... any suggestions or other options to bind? And that's when I had a strange thought. I get same result with new firmware rssi is 69-72 and failsafes shows warn message rxfail and badrx. I can go longer range and no failsafe. But i was not able to bind with d8 thats why i made this post lol. Power down the quad then leave bind mode on transmitter. Thank you, All the documentation seems to indicate I should be able to get the the TinyHawk RTF model into bind mode on it's own. Put tinyhawk into binding mode by pressing and holding the bind button while powering on tinyhawk. My other quad worked fine first day i tested it but today it fell out the sky due to receiver signal lost but wasn't far at all happened twice not sure whats the issue was until i took it apart at home, the antennas were loose. I don't know if this made any difference, but that's what I did. I used 4.0.2 because I was using the Project Mockinbird CLI dump I've pasted below. I hold down the button and plug in the power, it then does it's little beeps but then goes straight to flashing red. There have been one or two cases on with similar issues here where a replacement Tinyhawk solved the issue. I did the re-bind with d8 and it solved my issue. I used 4.0.2 because I was using the Project Mockinbird CLI dump I've pasted below. Then it should be receiving input signals from the radio!
Originally bound in D8, with Jumper T8SG transmitter. Found no solution so far. But the question is... why? Then press the bind button. Just got my Tinyhawk S in and want to bind it to my Q X7, but it seems I can't. Not sure where to go from here. so I tried to bind it but the green light never comes on while holding the bind button and plugging it in... and then if I hold the bind button after its on, the blue light stops flashing and nothing happens.
This shouldn't be the correct firmware for this FC. It started after I tried to tweak some Project Mockingbird settings. Always the same flashing red. No matter what, all I can get is a flashing red light.
Page 8: Trim 4. I'm still gathering info. If yes, then that will eliminate the transmitter as the source of the problem. After flashing the FC with new firmware yesterday, i am unable to get into bind mode. New to both reddit and fpv as well, one think is more info is need, and no matter what you will need betaflight. Good morning everyone 2 days ago, I've decided to update my tinyhawk to project mockingbird v4 Disclaimer: I am a totally newbie when it comes to upgrading the software..
And holy crap, it worked! I have similar issue with TH Freestyle.
Do you have the rtf transmitter? If yes, then that will eliminate the transmitter as the source of the problem. It's possible you have a lemon. Same problem here. Then I followed these instructions to bind it via CLI. It is what it is I guess, (This post was last modified: 11-Jan-2020, 10:17 PM by, (This post was last modified: 11-Jan-2020, 10:47 PM by, (This post was last modified: 11-Jan-2020, 11:45 PM by, https://intofpv.com/t-beta65-pro-2-and-f...5#pid75575, Replacement FC/ESC for Tinyhawk Freestyle. So i just received this thing today. Here's the PMB CLI dump I used.