I really wish i found this video a week ago im fairly new to the fpv part of drone flying so finding the right information not knowing much is a little rough. This video was clear and right to the point thank you !
Here are the steps in the video written out: In Betaflight: Open Betaflight Plug USB cable into Tinyhawk Click "Connect" if Betaflight does not automatically connect Click "Configuration" tab Scroll to "Receiver" section "Receiver Mode" needs to be "SPI RX support" Change "SPI Bus Receiver Provider" from "FRSKY_D" (D8 mode) to "FRSKY_X" (D16 mode) Click "Save and Reboot" You might need to click "Disconnect" and then "Connect" and double check that "FRSKY_X" saved Click "CLI" tab Type "bind_rx_spi" to put receiver into bind mode On transmitter: Select the model for the Tinyhawk Go to "MODEL SETUP" page Scroll to "Mode" for the "Internal RF" Change "Mode" to "D16" Take note of "Receiver No." Move Tinyhawk and transmitter apart to prevent binding issues Select "[Bind]" Select "Ch1-8 Telem OFF" Stop binding in the transmitter In Betaflight: In "CLI" type "get frsky_x_rx_num" The "CLI" should say "frsky_x_rx_num = XX" where "XX" is the same as "Receiver No." on the transmitter and this shows it is bound correctly Type "save" into "CLI" Click "Disconnect" and unplug Tinyhawk Go fly!
I love you. For those also searching, I was able to bind my Taranis Qx7 ACCESS to this setup, under the ACCST D16 setting. It took a long time. As of right now it's bound, but my receiver settings are all wonky. Working on fixing those.
Can you describe what was “wonky” about your receiver settings? Once you bind in ACCST D16 mode was it able to fly ? I’m on the same boat as you with the QX7 ACCESS.
Denis Ebner I don’t own the tinyhawk, I did a lot of research and If I was to get a micro quad I would get Beta75x or 85x. You can bind tinyhawk to QX7 through the CLI command in betaflight
Iv been trying this but my rx num is just 00 it never chages. Driving me crazy lol this is the first time trying the internal tx module. I got it and started using crsf from the beginning.
I managed to bind my Tinyhawk Freestyle to my Taranis QX7 Access in ACCST D16 mode, but while flying it randomly failsafes and drops to the ground. I've discovered that other people have had that problem, but I haven't seen any solution to it. I have an XJT module and a regular non-Access QX7 transmitter on the way, so I hopefully will be able to fly it in D8 mode.
I am having a issue binding my ELRS E8 and my Tinyhawk S. From my research, these should be compatible. Any tips or ideas? Struggling majorly and have no one for advice
This is not working for me in 2024...followed instructions exactly. it does not update the rx number in the CLI and I cant get it to bind to my taranis x9d.. any ideas?
Hi Ian, Thanks for this well explained video. I'm trying to bind a Tinyhawk S with the Taranis X9 lite and it doesen't work. I do all the steps, but it won't bind and when I type in the "get frsky_x_rx_num" I get a 0 (zero) even though I'm not trying to bind to 0 (zero). Do I need another radio or what? Best, Thomas
I was able to get the tiny hawk freestyle working with the x9 lite after following this. Keep at it, I’m sure there’s something in there keeping it from binding. I wish I could help but I’m new to fpv quads lol
You sir are a life saver! Been spending an hour watching a video on how to bind on D8 but it wasn't working. One problem though, for some reason the sticks are inverted, right stick is throttle/yaw and left is pitch/roll. How do I set it the normal way? Nevermind that, I got it! But this video is the only reason my Tinyhawk S is bound to my Taranis Qx7 so for that, you earned a like and subscriber!
Glad the video helped! Just a point of info since you already figured it out, you can switch your channels on your Taranis, or in Betaflight and it is fairly simple to do it in either place. Have fun flying!
I can’t get my frsky taranis qx7 access to connect to the tiny hawks s. Also I saw the pinned comment that said to do bind_rx instead of bind_rx_spy, but only bind_rx_spi worked for me as of 6/23/22. Does anyone know what to do?
Hy Ian, I live in the Netherlands (EU) So I got my drone reviver in X_LBT or something, dont know if thats ok? But it workt! I got my drone bind to my X-lite pro. But here is the problem, if I go to the tab in betaflight transmitter or something, I can see the chanels moving the right way. But the signal dropt out sometime's.... And I don't know how to set up the drone so it can fly... But I have looked on the internet and saw that it is a really big bug or something. Do you know the problem? So yes, do you have a way to fix it? Let me know, thx
If LBT firmware works, use it. I have never used it, but I live in the U.S. and I think you are supposed to use LBT in Europe if I understand correctly. Unfortunately I have also heard that the Tinyhawk sometimes has range issues in D16 mode, but you must use D16 with the X-Lite Pro unless you get a multiprotocol module for your X-Lite that has FrSky D8 mode. One easy way I have found to get more range is to change the location of the antennas, so they are higher and further away from other parts of the Tinyhawk. I just made a video for you about how to do this: th-cam.com/video/ONSjU0eaBik/w-d-xo.html Good luck!
Are you doing it on a stock Tinyhawk S or Tinyhawk Freestyle flight controller board? Are you using the original stock version of Betaflight that came with the Tinyhawk S or Tinyhawk Freestyle? If you are using a different flight controller, or if you flashed a new version of Betaflight, this setting may have changed or may not work. If you are still using the original version of Betaflight, make sure you type exactly "bind_rx_spi" and then hit the Enter key. If you are using an older version of Betaflight try the "frsky_bind" command and I also just read a that you could try “bind_rx” because some versions of Betaflight might use that. Also double check in the "Configuration" tab in the "Receiver" section that you have "SPI RX support" and "FRSKY_D" selected. Good luck!
I have heard that on the Tinyhawk that D8 works better than D16. I heard people say you get more range with D8, but that only applies to the Tinyhawk specifically. Normally D16 is better. The only reason I would use D16 mode on a Tinyhawk is if it is not possible for your transmitter to bind in D8 mode. On other quads I would use D16 instead of D8.
You might want to double check that you put the correct target of Betaflight on your flight controller. You might have put a version that does not support the SPI receiver. I have heard of people contacting Emax to help them reinstall the original version and its settings. You can always go back to the version that was working.
man I can't get it bound... I have a taranis qx7 Acces and a tinyhawk1 original. I do all the steps but i get a "0" on rx num, what do i do? gosh im desperate
Unfortunately the newer FrSky ACCESS protocol is not compatible with the older FrSky ACCST protocol. FrSky did this on purpose so that other companies could not use their newer technology. Because Emax made the receiver in the Tinyhawk it is ACCST. I think your best options are either to get a different transmitter that has ACCST built in such as an older FrSky, or even better get a Jumper or Radiomaster transmitter than has a built-in multiprotocol module that can bind to almost anything, or you can also get a separate multiprotocol module that plugs into the back of your QX7. The cheapest option is to solder a new ultra light FrSky ACCESS receiver into the Tinyhawk, but that adds some weight reducing your flight time and control.
@@IanBeaty Well Exactly I have a Taranis qx7, the box says the following: Model: X7 ACCESS RF Mode: ACCESS & ACCST D16 Firmware: LBT Could it work if I buy an external multiprotocol module to plug in the qx7? How do I know which one will work for me? I'm very new to this, any tips would help a lot! thanks!
Hi Ian I need some help with trying to bind my tinyhawk 2. I have a Frsky Xlite s lbt and I have spent ages trying to bind them together using an xjt lite module set on D8 but I never manage to bind successfully. So today I have done what you did on Beta flight and when I check to see if the bind has worked I get this message. warning no custom defaults found betaflight. Have you any idea what I have done wrong.
Hey Paul. I do not yet have a Tinyhawk 2 so I am not sure if they have changed anything on its flight controller. I also live in the U.S. and have not worked with lbt firmware, nor have I used an XJT module. With all of that said, I have a couple ideas. First, do you have a version of OpenTX on your Xlite that has the multiprotocol module enabled? You may need to flash a new version of the firmware to be able to do that. If that part works, does you Tinyhawk Receiver have lbt firmware on it? I don't know how the built-in receiver works with EU or non-EU firmware variants, but that could possibly be the issue. Maybe there is a way to flash EU firmware, but if not you can also solder on an external receiver with lbt firmware, a small one like the XM which would really improve your range. There are even smaller ones too. Also, you might find helpful information in this thread: support.betafpv.com/support/solutions/articles/27000051569-how-to-bind-to-spi-frsky-receiver-a-guide-for-eu-lbt-radio-controller-users Good luck!
@@IanBeaty Hi Thanks for getting back to me. I will have a look tomorrow when I have some time and try those things out. I am new at this hobby so at the moment Im still learning all this. Its just bad luck that my first attempt at this I end up buying a xlite that does not talk to tinyhawk lol. But I think its maybe a problem with the xlite I must have messed something up when I was updating the radio. Maybe I should have bought a Jumper T16 pro than I would not have the problem with D8.
@@paulb9015 I have another friend who is new to the hobby and bought the X-Lite Pro to go with his new Tinyhawk Freestyle and could not figure it out. That is why I made this video. A T16 would make some of this easier, but you might still be able to get this working by updating firmware again.
@@IanBeaty Still not having much luck with binding anything to my x lite. Today I bought a XSR- usb Sim which is EU LBT and guess what that wont bind either lol. What I know now is it must be my x lite were the problem lies since it wont bind to my hawk or the new xsr sim I just got. I have done another factory reset on it and again flashed the latest firmware to it version 2.3.5 and I have done the bootloader too plus sd card. I think it must be the internal xjt module but saying that my external xjt lite module wont bind either but it lights up at the back. I never thought I would have such a hard time trying to get this to bind. I wont give up but its getting me down now because its just a nightmare sometimes feel like getting rid of the lot and just fly my Mavic but I really want to try this hobby but this Frsky X lite is a big mistake. I dont know what to do now so I will have to give it some more thought how to get this thing to bind.
Hi Ian I am happy now after spending many hours trying to sort my radio out I have finally managed to bind to the usb sim. I should hopefully be ok binding to the hawk now so I will try that tomorrow and see how it goes but the main thing is im getting there now. Thanks again
Sorry about that. FrSky ACCESS protocol is a different newer protocol that is not compatible with the older FrSky ACCST protocol that comes on Emax Tinyhawks and many other drones and receivers. FrSky created ACCESS on purpose this way so that companies such as Emax would be locked out of their new ACCESS protocol ecosystem. It is very unfortunate and frustrating that they stabbed their customers and the industry in the back in that way. You can still use the Tinyhawk with a different transmitter that has a multiprotocol module or you could get a receiver that has ACCESS and solder it onto the Tinyhawk flight controller.
Thanks! This worked for my Freestyle 2, but I have a question. Is the range the same as it would be in D8 mode? Are there any limitations because you're in D16 instead of D8 mode? If so, it might be a good idea for me to get a D8 module for my X9 Lite. My goggles say low RSSI a lot, even when I'm not very far away.
Yes, I have noticed and heard from other people that D16 mode on these sometimes has worse range. D8 should give you better range so I would use D8 if possible. You can do some minor antenna adjustments on the Tinyhawk to help with the range, but that may or may not help a lot with the range. It is worth a try and does not cost anything and would also help give you more range in D8 mode. I have a short video about repositioning the antennas for more range if you want to try it.
been trying for over an hour now, im getting really, really annoyed! I have a taranis x9 lite.. i've tried every single option now except for flashing the firmware on the drone or updating my firmware on my controller.. Could that be the problem here?
Thanks for the tutorial! Only thing I noticed is that the power occasionally quits on the drone (I don’t loose video feed though). I’m using the X9 lite and the tiny hawk freestyle if anyone could help that would be much appreciated :) Again thanks a million for the tutorial XD
Hello, I hope you can help me .... I'm Italian and I can't understand the steps to pair freestyle with frsky lite pro. I can't see the video of the radio settings well. Can you write them so I try to follow them? thanks, Mauro.
My problem is to connect betaflight with the tinyhawk s .... it says: failed to open serial port. What can I do? I use betaflight 10.6.0 thx for supporting!
There are quite a few reasons that might be happening, but it is not specific to the Tinyhawk. That applies to connecting Betaflight to anything. Here is what I would try, in this order: 1) Try using different COM ports in Betaflight when you try to connect 2) Try the ImpulseRC Driver Fixer (a google search will find it) 3) Try different USB ports 4) Try different USB cables I am sure there are more in depth things to try, but one of these things typically works for me. If all else fails, you can use the SpeedyBee Betaflight app on a phone or tablet with a USB OTG adapter. Good luck!
Ian Beaty it was a wrong cable but now only.... and the bindig didn’t work your way. My Tinyhawk has to be powered before binding. I flashed an update to my taranis without a EU version to get D8 too. Finally I changed things in betaflight and now everything is working. Thx
The original Tiny Hawk only works in D8 mode. It does not have D16 mode capability. Just bind it the normal way in D8 mode. In this video description I have a link for how to bind a Tinyhawk S in D8 mode and that is pretty much how you do it for the original white Tiny Hawk. Good luck!
D16 mode on a Tinyhawk is known to have range issues and the best way to help that I know of is to move the antenna to a better position. I think I made a video about that a while back. I do not know why the D8 mode would not be working though unless something is set up wrong in Betaflight. I have not used a Jumper radio before so I am not sure what could cause that issue from the transmitter end of the system.
If you are talking about in Betaflight, make sure you save any settings before you switch to a new page of betaflight. To be safe, save each change immediately after making any change. You also needs to save any changes if you make changes from your OSD.
Hi if anyone could help me I'd really appreciate it! I have a FRSKY Taranis Lite and I've updated it for D16 support. I am trying to get it to bind to my Tinyhawk freestyle but it isn't working like shown in your video. When I check the rx number is always 00 regardless what number is on the transmitter. If anyone has any tips to get this working i'd be so grateful! Thanks
I have not used a Jumper T16, but I would really like to. The frsky_x_rx_num is the model number in your radio that the Tinyhawk binds to. Change it to a number that is different from any other models in your radio and also change it to a number other than 0 so you know if it bound correctly when you look in Betaflight. Because you have a Jumper, you should be able to simply bind it in D8 mode like the Tinyhawk instructions explain how to do, unless you have the need to use D16 mode, but I have heard that the signal is better in D8 mode if your transmitter can do that. Have you tried D8 mode yet?
Ian Beaty hi Ian...I have 3 drone , 1st bound is TH with old board BF 3.5.1 with D8 and numbe receiver 01 2nd is eachine uk65 is bound with D8 too and number receiver 02 3rd is cannot bound with T16 and already try D8 D16 number receiver 03 but the TH only bind mode in without bound. Any suggest to make my 3rd drone bound? Help me please
@@gatot150 Is the Tinyhawk that will not bind the new black Tinyhawk S? I don't quite understand what you mean by "but the TH only bind mode in without bound," could you explain more about what you mean by that?
@@IanBeaty i am sorry about my english, I have 3 drones, 2 drone succed bound with my jumpert16 but only one cannot bound. i have tried D8 , D16 and flash firmware to the newest 4.10
@@gatot150 No problem. I just want to make sure I understand so that I can help better. I need to understand what you know or don't know. Do you know how to change between D8 and D16 mode in the Jumper? Do you know how to change between D8 and D16 mode in Betaflight on the drone?
@@guk771 Sorry to hear that you are having trouble with this. I know it works for Freestyle because it was on a Tinyhawk Freestyle that I first used this to bind to my friend's FrSky X-Lite Pro. I also tested it later on a Tinyhawk S. You might double check the spelling of the CLI commands, or make sure you typed "save" after doing the CLI commands. Good luck!
@@guk771 That's too bad that it didn't work, but D8 mode tends to work better on a Tinyhawk than D16, so you are better off now. You should have a bit more range with D8. Just curious though, I did not know you could change the software on the transmitter to have D8 mode if D8 was not already on there. What upgrade did you do?
It's bind_rx not bind_rx_spi in latest version of betaflight
Thank you for making note of this.
Ian Beaty thank YOU for posting the video!
I was getting an error msg with the bind rx spi
OMG, you just saved me from pulling my hair out!
I really wish i found this video a week ago im fairly new to the fpv part of drone flying so finding the right information not knowing much is a little rough. This video was clear and right to the point thank you !
Here are the steps in the video written out:
In Betaflight:
Open Betaflight
Plug USB cable into Tinyhawk
Click "Connect" if Betaflight does not automatically connect
Click "Configuration" tab
Scroll to "Receiver" section
"Receiver Mode" needs to be "SPI RX support"
Change "SPI Bus Receiver Provider" from "FRSKY_D" (D8 mode) to "FRSKY_X" (D16 mode)
Click "Save and Reboot"
You might need to click "Disconnect" and then "Connect" and double check that "FRSKY_X" saved
Click "CLI" tab
Type "bind_rx_spi" to put receiver into bind mode
On transmitter:
Select the model for the Tinyhawk
Go to "MODEL SETUP" page
Scroll to "Mode" for the "Internal RF"
Change "Mode" to "D16"
Take note of "Receiver No."
Move Tinyhawk and transmitter apart to prevent binding issues
Select "[Bind]"
Select "Ch1-8 Telem OFF"
Stop binding in the transmitter
In Betaflight:
In "CLI" type "get frsky_x_rx_num"
The "CLI" should say "frsky_x_rx_num = XX" where "XX" is the same as "Receiver No." on the transmitter and this shows it is bound correctly
Type "save" into "CLI"
Click "Disconnect" and unplug Tinyhawk
Go fly!
I love you. For those also searching, I was able to bind my Taranis Qx7 ACCESS to this setup, under the ACCST D16 setting. It took a long time. As of right now it's bound, but my receiver settings are all wonky. Working on fixing those.
Can you describe what was “wonky” about your receiver settings? Once you bind in ACCST D16 mode was it able to fly ? I’m on the same boat as you with the QX7 ACCESS.
Cosmic Scenes Are you able to bind the qx7 with the tinyhawk?
Denis Ebner I don’t own the tinyhawk, I did a lot of research and If I was to get a micro quad I would get Beta75x or 85x. You can bind tinyhawk to QX7 through the CLI command in betaflight
does this work if my taranis qx7 only has access and accst D16? I can't seem to get the controller to bind to my Tinyhawk 3
did you ever figure this out?
Iv been trying this but my rx num is just 00 it never chages. Driving me crazy lol this is the first time trying the internal tx module. I got it and started using crsf from the beginning.
In the CLI tab I get an error message in red when I enter the code?
I managed to bind my Tinyhawk Freestyle to my Taranis QX7 Access in ACCST D16 mode, but while flying it randomly failsafes and drops to the ground. I've discovered that other people have had that problem, but I haven't seen any solution to it. I have an XJT module and a regular non-Access QX7 transmitter on the way, so I hopefully will be able to fly it in D8 mode.
Trying to bind mine now, and have been legit all day. What have you discovered?
I am having a issue binding my ELRS E8 and my Tinyhawk S. From my research, these should be compatible. Any tips or ideas? Struggling majorly and have no one for advice
This is not working for me in 2024...followed instructions exactly. it does not update the rx number in the CLI and I cant get it to bind to my taranis x9d.. any ideas?
Thanks for this amazing video! Thought my Tinyhawk Freestyle was garbage with the new Taranis X9D+ SE 2019. You saved the day. Cheers!
So glad it helped!
Hi Ian, Thanks for this well explained video.
I'm trying to bind a Tinyhawk S with the Taranis X9 lite and it doesen't work. I do all the steps, but it won't bind and when I type in the "get frsky_x_rx_num" I get a 0 (zero) even though I'm not trying to bind to 0 (zero).
Do I need another radio or what?
Best, Thomas
I was able to get the tiny hawk freestyle working with the x9 lite after following this. Keep at it, I’m sure there’s something in there keeping it from binding. I wish I could help but I’m new to fpv quads lol
TheLoganatorz I’m currently struggling to connect my x9 lite to my tiny hawk freestyle
Very helpful, first time I used cli to bind. Thanks for the video
You sir are a life saver! Been spending an hour watching a video on how to bind on D8 but it wasn't working. One problem though, for some reason the sticks are inverted, right stick is throttle/yaw and left is pitch/roll. How do I set it the normal way? Nevermind that, I got it! But this video is the only reason my Tinyhawk S is bound to my Taranis Qx7 so for that, you earned a like and subscriber!
Glad the video helped! Just a point of info since you already figured it out, you can switch your channels on your Taranis, or in Betaflight and it is fairly simple to do it in either place. Have fun flying!
When typing bind_rx_spi getting an unknown error message. Followed all of the steps up until this point
Yeah same, Is there anyway to fix this?
what if the drone doesn't connect to betaflight?
many thanks. have the white tiny but with the board of tiny s. worked. thank you again . d16 Word. Transmitter is x9 light
Fantastic news!
I can’t get my frsky taranis qx7 access to connect to the tiny hawks s. Also I saw the pinned comment that said to do bind_rx instead of bind_rx_spy, but only bind_rx_spi worked for me as of 6/23/22. Does anyone know what to do?
This is giving me an error message saying Unknown Command try HELP when doing this to my Tinyhawk 2. It worked on my Freestyle 2. Any idea why?
Hy Ian, I live in the Netherlands (EU) So I got my drone reviver in X_LBT or something, dont know if thats ok? But it workt! I got my drone bind to my X-lite pro. But here is the problem, if I go to the tab
in betaflight transmitter or something, I can see the chanels moving the right way. But the signal dropt out sometime's.... And I don't know how to set up the drone so it can fly... But I have looked on the internet and saw that it is a really big bug or something. Do you know the problem? So yes, do you have a way to fix it?
Let me know, thx
If LBT firmware works, use it. I have never used it, but I live in the U.S. and I think you are supposed to use LBT in Europe if I understand correctly.
Unfortunately I have also heard that the Tinyhawk sometimes has range issues in D16 mode, but you must use D16 with the X-Lite Pro unless you get a multiprotocol module for your X-Lite that has FrSky D8 mode. One easy way I have found to get more range is to change the location of the antennas, so they are higher and further away from other parts of the Tinyhawk. I just made a video for you about how to do this:
th-cam.com/video/ONSjU0eaBik/w-d-xo.html
Good luck!
@@IanBeaty Thx for the tip, I will look futher for a solution
When i type in bind_rx_spi my betaflight says "error unknown command"?? What do I do??
Are you doing it on a stock Tinyhawk S or Tinyhawk Freestyle flight controller board? Are you using the original stock version of Betaflight that came with the Tinyhawk S or Tinyhawk Freestyle? If you are using a different flight controller, or if you flashed a new version of Betaflight, this setting may have changed or may not work. If you are still using the original version of Betaflight, make sure you type exactly "bind_rx_spi" and then hit the Enter key. If you are using an older version of Betaflight try the "frsky_bind" command and I also just read a that you could try “bind_rx” because some versions of Betaflight might use that. Also double check in the "Configuration" tab in the "Receiver" section that you have "SPI RX support" and "FRSKY_D" selected. Good luck!
Depends on betaflight version command is different: brushlesswhoop.com/spi-bind-via-betaflight/
try just bind_rx
I have heard that on the Tinyhawk that D8 works better than D16. I heard people say you get more range with D8, but that only applies to the Tinyhawk specifically. Normally D16 is better. The only reason I would use D16 mode on a Tinyhawk is if it is not possible for your transmitter to bind in D8 mode. On other quads I would use D16 instead of D8.
I had this working then update the Tinyhawk freestyle to 4.1 and now this doesn't seam to work. whenever I try to bind, nothing happens.
You might want to double check that you put the correct target of Betaflight on your flight controller. You might have put a version that does not support the SPI receiver. I have heard of people contacting Emax to help them reinstall the original version and its settings. You can always go back to the version that was working.
have you been able to get your Tinyhawk to bind with d16 with the 4.1? I got a xd9+se2019 and the tinyhawk 2 freestyle isn't binding :(
Has anyone gotten this bound to a FrSky Taranis X9D Plus SE. I cant get this to work at all...
Excellent video, got me bound to my tinyhawk II. thanks
Is d16 better than d8?
man I can't get it bound... I have a taranis qx7 Acces and a tinyhawk1 original. I do all the steps but i get a "0" on rx num, what do i do? gosh im desperate
Unfortunately the newer FrSky ACCESS protocol is not compatible with the older FrSky ACCST protocol. FrSky did this on purpose so that other companies could not use their newer technology. Because Emax made the receiver in the Tinyhawk it is ACCST. I think your best options are either to get a different transmitter that has ACCST built in such as an older FrSky, or even better get a Jumper or Radiomaster transmitter than has a built-in multiprotocol module that can bind to almost anything, or you can also get a separate multiprotocol module that plugs into the back of your QX7. The cheapest option is to solder a new ultra light FrSky ACCESS receiver into the Tinyhawk, but that adds some weight reducing your flight time and control.
@@IanBeaty Well Exactly I have a Taranis qx7, the box says the following:
Model: X7 ACCESS
RF Mode: ACCESS & ACCST D16
Firmware: LBT
Could it work if I buy an external multiprotocol module to plug in the qx7? How do I know which one will work for me? I'm very new to this, any tips would help a lot! thanks!
Thanks you really helped me i was struggling and Noone else said to check the bind or save it
So glad to help!
Hi Ian I need some help with trying to bind my tinyhawk 2. I have a Frsky Xlite s lbt and I have spent ages trying to bind them together using an xjt lite module set on D8 but I never manage to bind successfully. So today I have done what you did on Beta flight and when I check to see if the bind has worked I get this message. warning no custom defaults found betaflight. Have you any idea what I have done wrong.
Hey Paul. I do not yet have a Tinyhawk 2 so I am not sure if they have changed anything on its flight controller. I also live in the U.S. and have not worked with lbt firmware, nor have I used an XJT module. With all of that said, I have a couple ideas.
First, do you have a version of OpenTX on your Xlite that has the multiprotocol module enabled? You may need to flash a new version of the firmware to be able to do that. If that part works, does you Tinyhawk Receiver have lbt firmware on it? I don't know how the built-in receiver works with EU or non-EU firmware variants, but that could possibly be the issue. Maybe there is a way to flash EU firmware, but if not you can also solder on an external receiver with lbt firmware, a small one like the XM which would really improve your range. There are even smaller ones too. Also, you might find helpful information in this thread: support.betafpv.com/support/solutions/articles/27000051569-how-to-bind-to-spi-frsky-receiver-a-guide-for-eu-lbt-radio-controller-users Good luck!
@@IanBeaty Hi Thanks for getting back to me. I will have a look tomorrow when I have some time and try those things out. I am new at this hobby so at the moment Im still learning all this. Its just bad luck that my first attempt at this I end up buying a xlite that does not talk to tinyhawk lol. But I think its maybe a problem with the xlite I must have messed something up when I was updating the radio. Maybe I should have bought a Jumper T16 pro than I would not have the problem with D8.
@@paulb9015 I have another friend who is new to the hobby and bought the X-Lite Pro to go with his new Tinyhawk Freestyle and could not figure it out. That is why I made this video. A T16 would make some of this easier, but you might still be able to get this working by updating firmware again.
@@IanBeaty Still not having much luck with binding anything to my x lite. Today I bought a XSR- usb Sim which is EU LBT and guess what that wont bind either lol. What I know now is it must be my x lite were the problem lies since it wont bind to my hawk or the new xsr sim I just got. I have done another factory reset on it and again flashed the latest firmware to it version 2.3.5 and I have done the bootloader too plus sd card. I think it must be the internal xjt module but saying that my external xjt lite module wont bind either but it lights up at the back.
I never thought I would have such a hard time trying to get this to bind. I wont give up but its getting me down now because its just a nightmare sometimes feel like getting rid of the lot and just fly my Mavic but I really want to try this hobby but this Frsky X lite is a big mistake.
I dont know what to do now so I will have to give it some more thought how to get this thing to bind.
Hi Ian I am happy now after spending many hours trying to sort my radio out I have finally managed to bind to the usb sim. I should hopefully be ok binding to the hawk now so I will try that tomorrow and see how it goes but the main thing is im getting there now. Thanks again
Cant bind to my taranis X7 Access.
Followed all the steps
Sorry about that. FrSky ACCESS protocol is a different newer protocol that is not compatible with the older FrSky ACCST protocol that comes on Emax Tinyhawks and many other drones and receivers. FrSky created ACCESS on purpose this way so that companies such as Emax would be locked out of their new ACCESS protocol ecosystem. It is very unfortunate and frustrating that they stabbed their customers and the industry in the back in that way. You can still use the Tinyhawk with a different transmitter that has a multiprotocol module or you could get a receiver that has ACCESS and solder it onto the Tinyhawk flight controller.
Got it to bind but can’t fly it. Bad RSSI and RX loss. It sucks cause get fpv told me it would work. Reaching out to them I guess
Thanks! This worked for my Freestyle 2, but I have a question. Is the range the same as it would be in D8 mode? Are there any limitations because you're in D16 instead of D8 mode? If so, it might be a good idea for me to get a D8 module for my X9 Lite. My goggles say low RSSI a lot, even when I'm not very far away.
Yes, I have noticed and heard from other people that D16 mode on these sometimes has worse range. D8 should give you better range so I would use D8 if possible. You can do some minor antenna adjustments on the Tinyhawk to help with the range, but that may or may not help a lot with the range. It is worth a try and does not cost anything and would also help give you more range in D8 mode. I have a short video about repositioning the antennas for more range if you want to try it.
been trying for over an hour now, im getting really, really annoyed! I have a taranis x9 lite.. i've tried every single option now except for flashing the firmware on the drone or updating my firmware on my controller.. Could that be the problem here?
UPDATE: Nevermind!! I set the reciever to FRSKY_X_LBT mode, worked first try! Thank you so so so so much dude!
Thanks for the tutorial!
Only thing I noticed is that the power occasionally quits on the drone (I don’t loose video feed though). I’m using the X9 lite and the tiny hawk freestyle if anyone could help that would be much appreciated :)
Again thanks a million for the tutorial XD
Hello,
I hope you can help me .... I'm Italian and I can't understand the steps to pair freestyle with frsky lite pro.
I can't see the video of the radio settings well.
Can you write them so I try to follow them? thanks, Mauro.
Hello Mauro. I just wrote out all of the instructions for you in the top pinned comment. I hope this helps!
@@IanBeaty ..thanks!!!👍
My problem is to connect betaflight with the tinyhawk s .... it says: failed to open serial port. What can I do? I use betaflight 10.6.0 thx for supporting!
There are quite a few reasons that might be happening, but it is not specific to the Tinyhawk. That applies to connecting Betaflight to anything. Here is what I would try, in this order:
1) Try using different COM ports in Betaflight when you try to connect
2) Try the ImpulseRC Driver Fixer (a google search will find it)
3) Try different USB ports
4) Try different USB cables
I am sure there are more in depth things to try, but one of these things typically works for me. If all else fails, you can use the SpeedyBee Betaflight app on a phone or tablet with a USB OTG adapter. Good luck!
Ian Beaty it was a wrong cable but now only.... and the bindig didn’t work your way. My Tinyhawk has to be powered before binding. I flashed an update to my taranis without a EU version to get D8 too. Finally I changed things in betaflight and now everything is working. Thx
@@davenow1017 Glad to hear everything is working!
I have a original white tiny hawk and the same radio you got on your video but I can't bind them, why?
The original Tiny Hawk only works in D8 mode. It does not have D16 mode capability. Just bind it the normal way in D8 mode. In this video description I have a link for how to bind a Tinyhawk S in D8 mode and that is pretty much how you do it for the original white Tiny Hawk. Good luck!
I have a original white hawk not the S but it cant bind even in d8 mode
@@paulwrobel2994 I fly my original white Tinyhawk the most. If it is not binding in D8 mode, something else must be wrong.
Awesome. Thank you. Great clear directions.
Thank you for the feedback!
I’m getting a lot of dropouts in d 16 mode I tried to bind in d8 mode and it won’t bind I’m using jumper t8sg v2
D16 mode on a Tinyhawk is known to have range issues and the best way to help that I know of is to move the antenna to a better position. I think I made a video about that a while back. I do not know why the D8 mode would not be working though unless something is set up wrong in Betaflight. I have not used a Jumper radio before so I am not sure what could cause that issue from the transmitter end of the system.
Thank you so much! Couldn't find anything to help me bind and was getting very frustrated.
Glad it helped! Have fun flying now!
when i try to change somthing i doesnt change y reconect and changes dont stay
If you are talking about in Betaflight, make sure you save any settings before you switch to a new page of betaflight. To be safe, save each change immediately after making any change. You also needs to save any changes if you make changes from your OSD.
Hi! Is this can work on the tinyhawk 2?
I do not know for sure, but I think it does.
Hi if anyone could help me I'd really appreciate it!
I have a FRSKY Taranis Lite and I've updated it for D16 support. I am trying to get it to bind to my Tinyhawk freestyle but it isn't working like shown in your video. When I check the rx number is always 00 regardless what number is on the transmitter.
If anyone has any tips to get this working i'd be so grateful! Thanks
Hello bro...i get problem TH cannot bind to my jumper T16 , what is mean no in frsky_rx_num ???
Default is 0
I have not used a Jumper T16, but I would really like to. The frsky_x_rx_num is the model number in your radio that the Tinyhawk binds to. Change it to a number that is different from any other models in your radio and also change it to a number other than 0 so you know if it bound correctly when you look in Betaflight. Because you have a Jumper, you should be able to simply bind it in D8 mode like the Tinyhawk instructions explain how to do, unless you have the need to use D16 mode, but I have heard that the signal is better in D8 mode if your transmitter can do that. Have you tried D8 mode yet?
Ian Beaty hi Ian...I have 3 drone , 1st bound is TH with old board BF 3.5.1 with D8 and numbe receiver 01
2nd is eachine uk65 is bound with D8 too and number receiver 02
3rd is cannot bound with T16 and already try D8 D16 number receiver 03 but the TH only bind mode in without bound.
Any suggest to make my 3rd drone bound? Help me please
@@gatot150 Is the Tinyhawk that will not bind the new black Tinyhawk S? I don't quite understand what you mean by "but the TH only bind mode in without bound," could you explain more about what you mean by that?
@@IanBeaty i am sorry about my english, I have 3 drones, 2 drone succed bound with my jumpert16 but only one cannot bound.
i have tried D8 , D16 and flash firmware to the newest 4.10
@@gatot150 No problem. I just want to make sure I understand so that I can help better.
I need to understand what you know or don't know. Do you know how to change between D8 and D16 mode in the Jumper? Do you know how to change between D8 and D16 mode in Betaflight on the drone?
heck yes. buying a new remote that only does 16 so gonna try this for my s and freestyle. thanks
Does this work for TinyHawk other than S?
Yes, this works for both the Tinyhawk S and Tinyhawk Freestyle. It does not work for the original Tinyhawk.
No it does not work for a freestyle been on it hours now
@@guk771 Sorry to hear that you are having trouble with this. I know it works for Freestyle because it was on a Tinyhawk Freestyle that I first used this to bind to my friend's FrSky X-Lite Pro. I also tested it later on a Tinyhawk S. You might double check the spelling of the CLI commands, or make sure you typed "save" after doing the CLI commands. Good luck!
@@IanBeaty nope never did work on my qx7 :( in the end upgraded software on qx7 so had d8 mode
@@guk771 That's too bad that it didn't work, but D8 mode tends to work better on a Tinyhawk than D16, so you are better off now. You should have a bit more range with D8. Just curious though, I did not know you could change the software on the transmitter to have D8 mode if D8 was not already on there. What upgrade did you do?
Thank's, man! Now Tiny works great with new Taranix X9D SE 2019.
So glad it helped!
I LOVE YOU! SUBBED!!!
Thank you!
Kick ass thanks!
super helpful thanks
Glad it helped!
thank you!
Definitely!
Thanks a lot!!
Definitely!
Nice
Sweet videos with your cinewhoop! Keep it up. Your shots will only get better!
👍🏼👍🏼
For those, who this wont bind, try tu use FRSKY_X_LBT reciever option in the configuration
Wow how did you all this complete confusion