Got to love tutorials where the tutor learns as we go. Notice that Bind mode last about 4 seconds on the Tx16s (red dot). The correct process is to set the radio internal module into low power mode (checkbox), have the Rx close to the Tx, then put the Rx into Bind mode (button pressed and connect power), then select the Bind mode on the Tx. That will bind it. Then once bound, tune it. I've seen some people rebind after tuning. Not sure if that achieves anything. Note, if you mess about with the protocol setting on the Tx, you will need to rebind the Rx.
I can't thank you enough for you video! Two for two - because of you - for me finishing my drone build and anothers repair this wk! I bought a cheap radiomaster Rx with D8 protocol and it wouldn't bind. I'm new to all this and thought I might have to do lbt flash or something..or I hadn't soldered correctly. A wee Google search before bed gave offered up your video; I gave it a go and now I'm bound. I went to 25. I'll do the fine tune when I get up in a few hours. Nice end to the evening. Cheers man. Saved me sooo much hassle👍👌
Thanks Bill, I just think that he binds because last you put the receiver on binding first and then the transmitter. When you first set the transmitter to binding, you have little time to set the receiver to bind. So always put the receiver on binding first.
Hi, I have had problems with the old V8 FrSky receivers that I have two in particular would not bind because the frequency find tune number was to far away from the default 0. I also had a viewer who had the same problem. I will keep in mind what you have said. Thanks.
@Wallace McSwank I have tested the fine frequency tune close in and at a distance of around 10 metres and it makes no difference to the results. This process is not about power but, as I understand, it is correcting for a difference in the frequency due to an electronic component difference between the module and FrSky receivers. To give you an example one of my FrSky V8 receivers would not bind to my T16. I tried with the FrSky module in my Turnigy TGY9X and it bound no problem went back to the T16 and no go! This was because at a fine frequency default setting of 0 it was not able to connect technically failsafe? The figures were - 1 and -69 therefore 0 would not connect and therefore not bind. The fine frequency number is -35 for that receiver and I have had no problems with range. I hope that helps.
@Wallace McSwank I have heard that sometimes you can have problems close in but I have never experienced it. I have just started using TBS Crossfire and they give the same warning that this can happen on the high power settings but I normally turn down the power when binding Crossfire receivers. I will test the receiver I mentioned and see what happens. Thanks for your feed back.
If the option is shown you need to proceed with the fine frequency tuning process. Please search my playlists if you need assistance with this process.
It does appear that way but if, with that particular receiver, if the fine frequency tune is set to 0 the receiver will not bind at all setting it to bind mode first or second. To give you an example try going in to one of you receivers and set the fine frequency turn to -200 and try and bind it will not bind. It is just an anomaly of that particular receiver.
You are correct Keith! Also trying to plug in a receiver battery while holding down a bind button is an exercise in frustration only persisted in by folks with 3 hands or fools. Get an in-line switch power cable! 😜 The protocols that may need the fine tuning option are noted in Pascal's Multi Protocol Module list.
@@theoztreecrasher2647 The fine frequency tune is needed for any FrSky protocols whatever brand of receiving you are binding to the multiprotocol module. If you see the option RF Freq. fine tune you need to complete the fine tuning procedure. There are a few sceptics out there so I did a follow up video showing the problem: ruclips.net/video/CQ6C6rGopGc/видео.html Just because you have not come across the problem does not mean it does not exist. Must say I have only come across two other pilots who had the problem and changing the value to - worked the receiver then bound. Fine frequency range -1 to - 50 means 0 is not in the range so 0 would failsafe and not bind as there is no link between the receiver and the transmitter.
@@the-happy-RC-flyer No argument that the fine tuning option may be needed for Frsky receivers and a whole raft of others which use other protocols. The likely candidates (mostly using the NRF24L01 chip on the 4-in-1 module) are noted in Pascal's Github lists. By selecting the "Freq Tuning" option - it will appear in the OpenTx "Model" menu if it is available for the selected protocol - you switch from using the NRF24L01 chip to using the CC2500 chip (normally used for FRSky, Futaba S-FHSS etc) which allows you to center the frequency to that required for the out-of-tolerance components on your gear. Not "always" required out of the box but probably best done even if you get a normal bind first time up to ensure maximum performance.
Hi Bill I was writing to you to ask you if you would change the color of your screen from yellow and green to med blue or red? All others use red for video purpose or maybe a darker blue? It is really hard to see, your explanation is really great but I want to see your screen!
You are letting it fall out of bind mode - it has nothing to do with the fine tune since it stayed bound from -17 to +50 which means zero, the default, would have been sufficient. You're making something very simple a lot more difficult by not following protocol and putting the receiver in bind mode first, then click bind on the receiver and it will bind almost immediately. If you put the receiver in bind mode and it takes too long to set the receiver up, the transmitter never detects it and the little red dot in the bind circle goes away.
Tom in this video I was just explaining what can happen and did not use the receiver with the anomaly. I then clarified this in a revisited video later to show the problem this particular receiver will not bind at 0 because the frequency range is in the negative range. I have had other subscribers have the same problem but it is very rare. Please see this later video on the anomaly. ruclips.net/video/CQ6C6rGopGc/видео.html
Hi Bob, sorry to hear you had problems with your T16. Mine has been used a lot for filming and fly, more for filming I think! Luckily I have had no problems but my T16 scroll wheel is not working as it should I think because of the use and I now need to get a new one which is difficult to fine here in South Africa. Out of interest which switch is giving you problems?
@@the-happy-RC-flyer If it's any consolation Bill my scroll wheel lost it's clicks on most of its rotation after about five minutes programming. Someone suggested using a bit of Velcro under the roller which I've done and it has helped a bit. RM needs to improve this particular item in my opinion.
Pls guide , Before binding my receiver found this , Module update recommended?? What's that's mean . Also can bind turnigy 9x8c V2 receiver and HK TRGA V2 RECEIVER ?? If try bind so what protocol ?
You can update your multi protocol module in your radio please search the TX16s playlist for help with doing so. No you cannot bind the receivers to the multi protocol module. I still have HK receivers but you need to plug in the HK external module into your TX16s to use the receivers.
It lowers the power when doing a range test. You do not have to walk so far! If I remember correct over 30 metres would be a good distance but do not forget to turn it off before flying!
my screen does not look like that, i have no fine tune option. this radio sertainly behaves bad from time to time. still cant connect my flysky mini reciever. thanks for the video tho.
If you do not see the Fine Frequency Tune option then it is not needed for the protocol you have selected. If you have the 4 in 1 module the FlySky receiver should bind to your radio.
I can’t bind my iflight 65s to my jumper t18 pro and it is frsky d16. Please help I have tried this and this doesn’t work either. I have no problem binding with my tinyhawk 2 with frsky d8
George it sounds like the firmware. What firmware does your receiver have? If it was newly purchased it could be a ACCESS version and only ACCST will bind to the multi protocol module. There are 2 versions of the ACCST firmware for your D16 you will need to try both if you do not know what firmware your receiver was supplied with or you will have to flash compatible firmware. FrSky as not made it easy for newcomers to our hobby.
Gilles are you sure the protocol you have chosen is correct and matched with the receiver because D16 has version 1 and 2 ACCST. Please try FrSky X and FrSkyX2 I think my R168 was shipped with Version 1 FrSky X
Hi Bill, In the Radiomaster multi-protocol list I find S-FHHS and that is Futaba language. I tried everything with my RS2008SB but there is no binding. Do you have a hint.
Guus, I do not have a Futaba RS2008SB receiver to test for you but I noticed it does have the RF Freq. fine tune option as it will not bind try both a figure of 20 and then -20 and see if it then binds. If it does complete the fine tuning as in my video. ruclips.net/video/RDICdD4QpUk/видео.html
Hi Bill. Is there a way to assign a switch so that my Eachine E010 can bind using a switch versus having to go through the menu to get it to bind. I've looked around and can't find any video on it. Thank you in advance.
@@the-happy-RC-flyer Hi Bill. Thank you for the link. I had to play around with the settings and I'm not really sure what I did, but I got it to work. I used your video as a guide because the settings were not exactly the same. I wish I knew how I got it to bind but it works! thank you for the help.
Seems like XT16S and the FRSky RXs are just problematic to begin with. Regardless whether its RadioMaster or FRSky branded. Which RX have you tried that are more simple or proven to bind with no issues? I have my XT16S bound to some Spektrum DSMX recievers. But even these give RSSI LOW callouts even at close range. I have disabled the Warnings as MULTIPLE SOURCES have stated that XT16S doesnt know how to interpret DSMX Telemetry which causes the system to call out LOW RSSI even though it may not be a connection problem at all. This is something that i dont wish to continually risk on my planes.
Firstly sorry I have no experience with Spektrum products. I have tested all RadioMaster receivers and videoed the results and all bound perfectly. Question I need to ask did you fine frequency tune the FrSky receivers? This is very important if you see the fine frequency tune feature in the binding section you must do the process or you can get range problems. ruclips.net/video/jdM_JcKzwCc/видео.html
Hi, I m almost to order this radio because my old Frsky Taranis DX9 needs go to pension, so, I have a lot of models flying well with the old Frsky (international version) DR8-II PLus receiver, my Question is : Just with this Tx should I bind this old DR8-Plus and the same time I could to bind another news one recivers with the ACCESS D16 protocoll too ? thank you for your video and waiting for answers... greetings form Sweden.
Greetings from South Africa to you TV LG. FrSky ACCESS protocol will not bind to the multiprotocol module in the TX16S. If the DR8-Plus is D8 it should bind to the TX16S but I do not have one of these receivers to check for you. I bind even older receivers, the V8 FrSky receivers to my TX16S so I think you should be fine but ACCESS a no go.
@@the-happy-RC-flyer Hi Bill Clark and thank you to answer me fast !!, so, hmmm, I was thinking about what you said , so, my other alternative is buy one new Taranis X9D Plus 2019 (NON-EU) plus a external module XJT compatible with the DR8 as NON-EU right ? could work ? thank you ! I really appreciate it. From Sweden Hugo.
Hi Oak, The figures are +51 -17 = 34 / 2 = 17 As far as I under stand you add the figures together so a - 17 is taken off the +51 we are looking for the mid point in a linear line then this is divided by 2
Hi Bill, have a question for you. I bought the radio Master TX16S about a year ago. We'll just receive a mobula 6 FrSky, which I thought was going to be easy to bind to this radio. At least that's what the vendor told me. I'm having nothing but problems trying to get this thing bound to my radiomaster radio. I've got the protocol set for FrSky D D8. I'm not sure if that's the correct protocol for that mobula 6 or not but I can't get anything to bind. I think I'm doing everything I supposed to be doing but can't get the props to turn. Any ideas?
I think you maybe choosing the incorrect protocol option FrSky receivers can me tricky to bind because of the different protocols. FrSky X FrSkyX2 and then FCC & LBT-EU versions. If you are in Europe then you must use the LBT-EU version. The firmware on the receiver must be ACCST and not ACCESS which will not bind to the multiprotocol module I am almost certain yours will be ACCST. So try X and if will not bind try X2 and I am sure you will come right. I see the Mobula 6 can be shipped with a FlySky receiver too maybe check the vendor shipped the correct version to you.
@@the-happy-RC-flyer thanks for your input Bill. I'll try your remedies and see if they don't work. I'll let you know if they do. But the dealer told me this Frsky binds with my radio master.
Hi Bill. Thank you so much for your extensive tutorial videos on this Radiomaster Tx16s! If I may, I have two questions: 1) When binded to DSMX receiver, the radio calls out low rssi on a short distance. Would you know why would that be? 2) is it required to rebind the receiver after setting frecuency tuning number on any radiomaster receivers? Thank you in advance for your help🙏
Hi Don, 2) first no, once the receiver is bound you can do ahead and fine frequency tune and will not need to rebound your receiver. In the video you posted your question this problem is very rare but your receiver is binding ok just low RSSI. 1) if your receive and transmitter are close together the RF signals can overwhelm the link and failsafe. If this is happening over a metre away then I suggest doing a range test first. If you are not sure how to do this this video may help you: ruclips.net/video/-7_YfRSoXik/видео.html RSSI problems can be caused by a few things please complete the range test and come back to me for further help. I have no experience of DSMX receivers but will try to assist you.
@@the-happy-RC-flyer thank you so much for your help and very much appreciated! I have rebound and fine tuned the frequency on my receivers R86c. So far both receivers once I set to range test, the radio starts calling low rssi after 12 paces. 50 pases the signal is lost. I am not getting near as far as your range test video. But I will try at my flying club next week as I live in a very condensed area. On the other hand, the DSMX receiver performed much better than before and compared to the R86Cs! I checked the box to Disable Telemetry and I was able to go 60 to 70 paces and no issues! Now I am just concerned about these Radiomaster receivers...
@@donj8263 the results in my video were very unusual it could have been because of the location. I have been getting no RSSI warnings with the RadioMaster receiver I have in my wing but I am flying no more than 200 metres away. As for the range check as I mentioned in my videos the manufacturers do not give range check distances but from what I have researched over 30 meters is ok. In one test I did the range test went, if I remember correctly, only around 17 metres but the receiver is not going to failsafe at normal flying distances in a fixed wing. I would suggest fly with your RadioMaster receivers but heed any RSSI warnings and fly back towards yourself.
Your rx # understanding is off. If "you take out the rx and move to a different model", of course you don't have to rebind it's the same rx. Rx# has nothing to do with that. It's a protection between different receiver's and Opentx model selection. Sine both receivers are bond to the TX, you will not have to rebind, but the RX # maps the rx to the model in OpenTX. Other wise you could select a heli model by mistake and possibly send undesired commands to your plain.
Hi Nick, I am not sure what angle you are coming from. I do not think I said in this video if you remove a receiver from one model to another you have to rebind it because of cause that is incorrect it is the TX and RX which are bound. This video caused a bit of a stir because of the particular receiver I was using would not bind with the fine frequency tune set to the default of 0. I have not come across another receiver that acts this way, if I remember correctly I had 2 views come back to me and say they had receivers that acted the same way. I have just watched my video again and I think you misunderstood what I was trying to get across. If you give the receiver a receiver number you can then take the RX out and put it in another model go to the Model Setup and set up your new model, turn on the Internal RF select the correct protocol and select the receiver number and you are ready to go without binding.
That's strange Tony, are you Setting your Internal RF Mode to Multi, press enter and then you should be able to select the following FrSky protocols: FrSkyRX FrSky X FrSkyX2 FrSky L You will know if you have turned on your internal module if you see FlySky Std which comes up first.
@@the-happy-RC-flyer yes i see those options. but it doesnt seem to allow me to bind my XM+. all the videos i see are "FrSky" only. none of the other FrSkyRX,X,X2, or L.
@@carcomp101 that can be tricky because we have no way to see what firmware is in the receiver and FrSky have different versions for the same receiver! But you solved the problem.
I allready find it Bill, finetuning on 40 and it worked.
Got to love tutorials where the tutor learns as we go. Notice that Bind mode last about 4 seconds on the Tx16s (red dot). The correct process is to set the radio internal module into low power mode (checkbox), have the Rx close to the Tx, then put the Rx into Bind mode (button pressed and connect power), then select the Bind mode on the Tx. That will bind it. Then once bound, tune it. I've seen some people rebind after tuning. Not sure if that achieves anything. Note, if you mess about with the protocol setting on the Tx, you will need to rebind the Rx.
This worked, thanks.
I can't thank you enough for you video! Two for two - because of you - for me finishing my drone build and anothers repair this wk! I bought a cheap radiomaster Rx with D8 protocol and it wouldn't bind. I'm new to all this and thought I might have to do lbt flash or something..or I hadn't soldered correctly. A wee Google search before bed gave offered up your video; I gave it a go and now I'm bound. I went to 25. I'll do the fine tune when I get up in a few hours. Nice end to the evening. Cheers man. Saved me sooo much hassle👍👌
I recommended this video to folks in the RadioMaster TX16S TX User Group on Facebook. Very helpful.
Thank you very much that is kind of you.
Would have never figured it out without this video,thanks man, you're a lifesaver
Thanks for this I’ll be trying again tomorrow to get my frsky r-xsr to bind
Thanks Bill,
I just think that he binds because last you put the receiver on binding first and then the transmitter.
When you first set the transmitter to binding, you have little time to set the receiver to bind.
So always put the receiver on binding first.
Hi, I have had problems with the old V8 FrSky receivers that I have two in particular would not bind because the frequency find tune number was to far away from the default 0. I also had a viewer who had the same problem. I will keep in mind what you have said. Thanks.
@Wallace McSwank I have tested the fine frequency tune close in and at a distance of around 10 metres and it makes no difference to the results. This process is not about power but, as I understand, it is correcting for a difference in the frequency due to an electronic component difference between the module and FrSky receivers. To give you an example one of my FrSky V8 receivers would not bind to my T16. I tried with the FrSky module in my Turnigy TGY9X and it bound no problem went back to the T16 and no go! This was because at a fine frequency default setting of 0 it was not able to connect technically failsafe? The figures were - 1 and -69 therefore 0 would not connect and therefore not bind. The fine frequency number is -35 for that receiver and I have had no problems with range. I hope that helps.
@Wallace McSwank I have heard that sometimes you can have problems close in but I have never experienced it. I have just started using TBS Crossfire and they give the same warning that this can happen on the high power settings but I normally turn down the power when binding Crossfire receivers. I will test the receiver I mentioned and see what happens. Thanks for your feed back.
Exactly. You set the receiver to bind first, then click bind on the radio second. You will not have to do any of that frequency tuning just to bind.
@@jamesl.9552 Exactly James!
I got 5 of these receivers gifted to me they were set for the bin before I found this thank you so much . lets fly
Thank you very much. Perfectly imperfect. 😂 I Love it.
Thanks for this Bill! I managed to finally bind my Boxer to my new R88 bu increasing the frequency by 30.
Glad to help!
Thank you for taking the time to say what happens when it doesn’t work.
You are very welcome.
Or you need to put the receiver into bind mode before you press bind on your transmitter.
TY! :)
Good video tip, but I would like to know why the fine tuning adjustment is in the binding area. It might have to do with variations in the receiver.
If the option is shown you need to proceed with the fine frequency tuning process. Please search my playlists if you need assistance with this process.
Very great info friend thank you all together,very informative content great work,,yes GreaAT work, thnk you.
Excellent Thank you.
Looks like the transmitter had already stopped its bind attempt before power was applied to the receiver.
It does appear that way but if, with that particular receiver, if the fine frequency tune is set to 0 the receiver will not bind at all setting it to bind mode first or second. To give you an example try going in to one of you receivers and set the fine frequency turn to -200 and try and bind it will not bind. It is just an anomaly of that particular receiver.
You are correct Keith! Also trying to plug in a receiver battery while holding down a bind button is an exercise in frustration only persisted in by folks with 3 hands or fools. Get an in-line switch power cable! 😜
The protocols that may need the fine tuning option are noted in Pascal's Multi Protocol Module list.
@@theoztreecrasher2647 The fine frequency tune is needed for any FrSky protocols whatever brand of receiving you are binding to the multiprotocol module. If you see the option RF Freq. fine tune you need to complete the fine tuning procedure.
There are a few sceptics out there so I did a follow up video showing the problem:
ruclips.net/video/CQ6C6rGopGc/видео.html
Just because you have not come across the problem does not mean it does not exist. Must say I have only come across two other pilots who had the problem and changing the value to - worked the receiver then bound. Fine frequency range -1 to - 50 means 0 is not in the range so 0 would failsafe and not bind as there is no link between the receiver and the transmitter.
@@the-happy-RC-flyer No argument that the fine tuning option may be needed for Frsky receivers and a whole raft of others which use other protocols. The likely candidates (mostly using the NRF24L01 chip on the 4-in-1 module) are noted in Pascal's Github lists. By selecting the "Freq Tuning" option - it will appear in the OpenTx "Model" menu if it is available for the selected protocol - you switch from using the NRF24L01 chip to using the CC2500 chip (normally used for FRSky, Futaba S-FHSS etc) which allows you to center the frequency to that required for the out-of-tolerance components on your gear. Not "always" required out of the box but probably best done even if you get a normal bind first time up to ensure maximum performance.
@@theoztreecrasher2647 "Exercise in frustration." You nailed it! lol
Hi Bill
I was writing to you to ask you if you would change the color of your screen from yellow and green to med blue or red? All others use red for video purpose or maybe a darker blue?
It is really hard to see, your explanation is really great but I want to see your screen!
No problem I will do that in the future.
@@the-happy-RC-flyer iam looking forward for that✌🏾😎.
Very helpfull video rite there
Very good video ! Thank you ! 👍
You are letting it fall out of bind mode - it has nothing to do with the fine tune since it stayed bound from -17 to +50 which means zero, the default, would have been sufficient. You're making something very simple a lot more difficult by not following protocol and putting the receiver in bind mode first, then click bind on the receiver and it will bind almost immediately. If you put the receiver in bind mode and it takes too long to set the receiver up, the transmitter never detects it and the little red dot in the bind circle goes away.
Tom in this video I was just explaining what can happen and did not use the receiver with the anomaly. I then clarified this in a revisited video later to show the problem this particular receiver will not bind at 0 because the frequency range is in the negative range. I have had other subscribers have the same problem but it is very rare.
Please see this later video on the anomaly.
ruclips.net/video/CQ6C6rGopGc/видео.html
Problem was you hit bind on the transmitter before powering up receiver.
Wow you legend, I loved this advice, well done and a big thank you, like this comment if you agree
Thank you.
I hope the radiomaster t16s is better than the jumper t16 switch I have. Been nothing but trouble.
Hi Bob, sorry to hear you had problems with your T16. Mine has been used a lot for filming and fly, more for filming I think! Luckily I have had no problems but my T16 scroll wheel is not working as it should I think because of the use and I now need to get a new one which is difficult to fine here in South Africa. Out of interest which switch is giving you problems?
@@the-happy-RC-flyer If it's any consolation Bill my scroll wheel lost it's clicks on most of its rotation after about five minutes programming. Someone suggested using a bit of Velcro under the roller which I've done and it has helped a bit. RM needs to improve this particular item in my opinion.
Thank you, Very helpful
You are very welcome.
Pls guide ,
Before binding my receiver found this ,
Module update recommended??
What's that's mean .
Also can bind turnigy 9x8c V2 receiver and
HK TRGA V2 RECEIVER ??
If try bind so what protocol ?
You can update your multi protocol module in your radio please search the TX16s playlist for help with doing so. No you cannot bind the receivers to the multi protocol module. I still have HK receivers but you need to plug in the HK external module into your TX16s to use the receivers.
Very helpful.
Hello bill. Thanks for the video. Can you do a video showing how to set up the SD function on open TX? So that it backs automatically. Thanks
I will add it to my schedule.
Specktrum recivers how to dsm and dsmx 1f and 2f
Hi Bill do you know how to bind a Flysky Fgr12B to the Radiomaster TX16S
I do not think you can because it uses AFHDS3 protocol which is not supported by the Multiple Protocol Module at this time.
What is the range option next to the bind option?
It lowers the power when doing a range test. You do not have to walk so far! If I remember correct over 30 metres would be a good distance but do not forget to turn it off before flying!
Great video, I have a ar620 spekrum receiver can it be bound with the tx16s? What protocol? Thx
I cannot check this for you as I do not have Spektrum receivers. The protocols available are Spektrum DSM2 and DSMX.
If im not mistaken, the AR620 is running on DSM2 protocol.
Correct me if im wrong😅
@@mohdfadlyarifin2433 looks that way from the website.
Hi Bill , I am not able to bind my Radio link receiver R9DS , would you be able to help ?
Does tx16s bind to a futaba r30006sb?
Hi Jason, I am not sure. I have checked your receiver protocol and it is T-FHSS and the MPM can bind to S-FHSS. So I do not think so.
I am facing issue with Radiolink receiver. Could you please help me with that.
Please email me with your issue and I will try to assist you. triplemadventures@gmail.com
my screen does not look like that, i have no fine tune option. this radio sertainly behaves bad from time to time. still cant connect my flysky mini reciever.
thanks for the video tho.
If you do not see the Fine Frequency Tune option then it is not needed for the protocol you have selected. If you have the 4 in 1 module the FlySky receiver should bind to your radio.
I can’t bind my iflight 65s to my jumper t18 pro and it is frsky d16. Please help I have tried this and this doesn’t work either. I have no problem binding with my tinyhawk 2 with frsky d8
George it sounds like the firmware. What firmware does your receiver have? If it was newly purchased it could be a ACCESS version and only ACCST will bind to the multi protocol module. There are 2 versions of the ACCST firmware for your D16 you will need to try both if you do not know what firmware your receiver was supplied with or you will have to flash compatible firmware. FrSky as not made it easy for newcomers to our hobby.
It doesn't want to work with the R168 that I use. EU LBT is what I use for firmware and also in model set-up but it doesn't want to bind.
Gilles are you sure the protocol you have chosen is correct and matched with the receiver because D16 has version 1 and 2 ACCST. Please try FrSky X and FrSkyX2 I think my R168 was shipped with Version 1 FrSky X
@@the-happy-RC-flyer Thanks for the feedback. I will try that later on.
Hi Bill, In the Radiomaster multi-protocol list I find S-FHHS and that is Futaba language. I
tried everything with my RS2008SB but there is no binding. Do you have a hint.
Guus, I do not have a Futaba RS2008SB receiver to test for you but I noticed it does have the RF Freq. fine tune option as it will not bind try both a figure of 20 and then -20 and see if it then binds. If it does complete the fine tuning as in my video. ruclips.net/video/RDICdD4QpUk/видео.html
Hi Bill. Is there a way to assign a switch so that my Eachine E010 can bind using a switch versus having to go through the menu to get it to bind. I've looked around and can't find any video on it. Thank you in advance.
Hopefully this video will help you.
ruclips.net/video/QrpGOKP8dqg/видео.html
@@the-happy-RC-flyer Hi Bill. Thank you for the link. I had to play around with the settings and I'm not really sure what I did, but I got it to work. I used your video as a guide because the settings were not exactly the same. I wish I knew how I got it to bind but it works! thank you for the help.
Seems like XT16S and the FRSky RXs are just problematic to begin with. Regardless whether its RadioMaster or FRSky branded. Which RX have you tried that are more simple or proven to bind with no issues? I have my XT16S bound to some Spektrum DSMX recievers. But even these give RSSI LOW callouts even at close range. I have disabled the Warnings as MULTIPLE SOURCES have stated that XT16S doesnt know how to interpret DSMX Telemetry which causes the system to call out LOW RSSI even though it may not be a connection problem at all. This is something that i dont wish to continually risk on my planes.
Firstly sorry I have no experience with Spektrum products. I have tested all RadioMaster receivers and videoed the results and all bound perfectly. Question I need to ask did you fine frequency tune the FrSky receivers? This is very important if you see the fine frequency tune feature in the binding section you must do the process or you can get range problems.
ruclips.net/video/jdM_JcKzwCc/видео.html
Hi, I m almost to order this radio because my old Frsky Taranis DX9 needs go to pension, so, I have a lot of models flying well with the old Frsky (international version) DR8-II PLus receiver, my Question is : Just with this Tx should I bind this old DR8-Plus and the same time I could to bind another news one recivers with the ACCESS D16 protocoll too ? thank you for your video and waiting for answers... greetings form Sweden.
Greetings from South Africa to you TV LG. FrSky ACCESS protocol will not bind to the multiprotocol module in the TX16S. If the DR8-Plus is D8 it should bind to the TX16S but I do not have one of these receivers to check for you. I bind even older receivers, the V8 FrSky receivers to my TX16S so I think you should be fine but ACCESS a no go.
@@the-happy-RC-flyer Hi Bill Clark and thank you to answer me fast !!, so, hmmm, I was thinking about what you said , so, my other alternative is buy one new Taranis X9D Plus 2019 (NON-EU) plus a external module XJT compatible with the DR8 as NON-EU right ? could work ? thank you ! I really appreciate it. From Sweden Hugo.
Thanks Bill. Shouldn't that be 51 - (-17) = 68/2=34?
Hi Oak,
The figures are +51 -17 = 34 / 2 = 17
As far as I under stand you add the figures together so a - 17 is taken off the +51 we are looking for the mid point in a linear line then this is divided by 2
Sorry Bill, I subtracted the 17. My mistake.
@@oak3076 No problem.
Hi Bill, have a question for you. I bought the radio Master TX16S about a year ago. We'll just receive a mobula 6 FrSky, which I thought was going to be easy to bind to this radio. At least that's what the vendor told me. I'm having nothing but problems trying to get this thing bound to my radiomaster radio. I've got the protocol set for FrSky D D8. I'm not sure if that's the correct protocol for that mobula 6 or not but I can't get anything to bind. I think I'm doing everything I supposed to be doing but can't get the props to turn. Any ideas?
I think you maybe choosing the incorrect protocol option FrSky receivers can me tricky to bind because of the different protocols.
FrSky X
FrSkyX2
and then FCC & LBT-EU versions.
If you are in Europe then you must use the LBT-EU version.
The firmware on the receiver must be ACCST and not ACCESS which will not bind to the multiprotocol module I am almost certain yours will be ACCST.
So try X and if will not bind try X2 and I am sure you will come right.
I see the Mobula 6 can be shipped with a FlySky receiver too maybe check the vendor shipped the correct version to you.
@@the-happy-RC-flyer thanks for your input Bill. I'll try your remedies and see if they don't work. I'll let you know if they do. But the dealer told me this Frsky binds with my radio master.
@@JH-zc8xe FrSky D & D8 is the correct kombination. It worked for me.
Hi Bill can you bind radiolink r7eh receiver to this radio??
It looks like you can only bind the Radiolink R7FG.
Hi Bill. Thank you so much for your extensive tutorial videos on this Radiomaster Tx16s!
If I may, I have two questions:
1) When binded to DSMX receiver, the radio calls out low rssi on a short distance. Would you know why would that be?
2) is it required to rebind the receiver after setting frecuency tuning number on any radiomaster receivers?
Thank you in advance for your help🙏
Hi Don, 2) first no, once the receiver is bound you can do ahead and fine frequency tune and will not need to rebound your receiver. In the video you posted your question this problem is very rare but your receiver is binding ok just low RSSI. 1) if your receive and transmitter are close together the RF signals can overwhelm the link and failsafe. If this is happening over a metre away then I suggest doing a range test first. If you are not sure how to do this this video may help you:
ruclips.net/video/-7_YfRSoXik/видео.html
RSSI problems can be caused by a few things please complete the range test and come back to me for further help. I have no experience of DSMX receivers but will try to assist you.
@@the-happy-RC-flyer thank you so much for your help and very much appreciated! I have rebound and fine tuned the frequency on my receivers R86c. So far both receivers once I set to range test, the radio starts calling low rssi after 12 paces. 50 pases the signal is lost. I am not getting near as far as your range test video. But I will try at my flying club next week as I live in a very condensed area.
On the other hand, the DSMX receiver performed much better than before and compared to the R86Cs! I checked the box to Disable Telemetry and I was able to go 60 to 70 paces and no issues! Now I am just concerned about these Radiomaster receivers...
@@donj8263 the results in my video were very unusual it could have been because of the location. I have been getting no RSSI warnings with the RadioMaster receiver I have in my wing but I am flying no more than 200 metres away. As for the range check as I mentioned in my videos the manufacturers do not give range check distances but from what I have researched over 30 meters is ok. In one test I did the range test went, if I remember correctly, only around 17 metres but the receiver is not going to failsafe at normal flying distances in a fixed wing. I would suggest fly with your RadioMaster receivers but heed any RSSI warnings and fly back towards yourself.
@@the-happy-RC-flyer thank you once again. I will give them a try at the field again. Much appreciated! Have a wonderful weekend.
0db at rssi why
Could you please clarify your question.
Hi bill...
Can tx16s bind to receiver redcon?
It should do but I do not have a Redcon receiver to test for you but the multi protocol module does support DSM2 / DSMX protocols.
@@the-happy-RC-flyer ok thank bill
Hi Bill does this bind to frsky xm+, /FrSky R-XSR , ? cheers
Peter, yes you can bind them with the correct firmware ACCST as far as I understand not the ACCESS protocol.
@@the-happy-RC-flyer how do you change the protocol ?
@@mr.j-rcs822 I do not think it is possible to switch receivers between ACCST and ACCESS
Your rx # understanding is off. If "you take out the rx and move to a different model", of course you don't have to rebind it's the same rx. Rx# has nothing to do with that. It's a protection between different receiver's and Opentx model selection. Sine both receivers are bond to the TX, you will not have to rebind, but the RX # maps the rx to the model in OpenTX. Other wise you could select a heli model by mistake and possibly send undesired commands to your plain.
Hi Nick, I am not sure what angle you are coming from. I do not think I said in this video if you remove a receiver from one model to another you have to rebind it because of cause that is incorrect it is the TX and RX which are bound. This video caused a bit of a stir because of the particular receiver I was using would not bind with the fine frequency tune set to the default of 0. I have not come across another receiver that acts this way, if I remember correctly I had 2 views come back to me and say they had receivers that acted the same way.
I have just watched my video again and I think you misunderstood what I was trying to get across. If you give the receiver a receiver number you can then take the RX out and put it in another model go to the Model Setup and set up your new model, turn on the Internal RF select the correct protocol and select the receiver number and you are ready to go without binding.
i do not have FRSky on my internal module. could you please explain on how i can add this in?
That's strange Tony, are you Setting your Internal RF Mode to Multi, press enter and then you should be able to select the following FrSky protocols:
FrSkyRX
FrSky X
FrSkyX2
FrSky L
You will know if you have turned on your internal module if you see FlySky Std which comes up first.
@@the-happy-RC-flyer yes i see those options. but it doesnt seem to allow me to bind my XM+. all the videos i see are "FrSky" only. none of the other FrSkyRX,X,X2, or L.
@@the-happy-RC-flyer in other words i dont know what protocal works
@@the-happy-RC-flyer i was thinking maybe i needed to add Access to the Internal Module, but i cant figure out how to do that either. lol
@@the-happy-RC-flyer :-(
or use FrSkyX2.
What makes you say that Mitch?
Mitch Thompson
Tried today to bind my Tx16s to a brand new XM+. Wouldn't bind. Switched to the X2 protocol and it bound right up!
@@carcomp101 that can be tricky because we have no way to see what firmware is in the receiver and FrSky have different versions for the same receiver! But you solved the problem.
Pp qq