that cable is for programming the rx from the radio, using the radio to flash the rx. it works for that, the other wire harnes is the one intended to use for connection to FC
Lol and all these people thanking for the fix that ain't a real fix. Just hoping they remember to switch the pins back before trying to update the firmware.
OMG!!!!!! I was bonkers for 2 days in disbelief that the wiring was wrong.... Like you I finally tore the quad down to the individual components and you are SPOT ON!!! Geez! You have saved me from pulling all my hair out. It works now! SUBSCRIBED! Thank you!
I have two rxsr receiver and three quads. Recently decided to use this cable for one of the quads to connect to FC. This was the same problem. Thank you for sharing. Saved my day.
You sir, are a life saver, I ignore the manuals, because they provided the handy connector, little did I realise it's only for flashing firmware. They should put a warning sticker on it.
You are my hero! After 3hrs of figuring out the same problem (no signal from R-XSR on Pixhawk 2.4.8) and next to frustration i found this video. Exactly the same problem solved now by setting the signal cable from SBus to SBUS_OUT/CPPM). Lesson1: ALWAYS CHECK THIS THIS CHANNEL FIRST IN CASE OF PROBLEMS ;-) Lesson2: Check the damn wiring and connection points! Thank you very much for all your great videos. Would have given up this hobby already without all those detailed explanations for pixhawk and all around from you!
I spent hours trying to figure that out. Thank you so much for pointing this out! I thought I had a defective receiver or autopilot or controller or something. Moving that one wire over has completely solved the issue!
I managed to flash a newer firmware version by plugging into a mysterious port in the battery compartment of my Taranis X9D+ and selecting Flash SPort Device in the menus. Yet I STILL did not catch on! BTW, It was the second R-XSR--I tried hooking up the first R-XSR to the External Radio terminals bottom 3 pins and managed to quietly burn up something. No more blinky lights! I plugged the second R-XSR into my flight controller, bound it but it didn't work! I've moved the yellow wire as instructed here. There's the "inverted SBus" issue, brilliant video on that also, thanks!
I ordered 2 r-xsr receivers, before Christmas and was wondering why i also geht No Output Channels! I checked the Plug and das it! The Yellow Wire comes from the 3rd Pin/telemetry! Thank you👍 I build allready 7 Quads before and couldnt find out why this build is Not working! 😂 After 2 hours in get now smart of IT! Thx from GER
WOW thanks for this video!!! First i couldn't bind my R-XSR to my taranis and had to reflash a bug fix on the R-XSR ... Then i had no control... Wich i solved thanks to this vid.. FRSKy did it this time took my a whole evening... :(
THANKS!!! I had no clue what that "extra cable" was for! Relating said cable to the pinouts listed in the "manual" was the missing link! I've made the cable mod, can bind, but it's ACCESS, not ACCST like my Controller. I can't find a backward path for downgrading to ACCST firmware, OR a forward path for upgrading my Controller to ACCESS. Hoping someone's delved into that situation.
Andrew Dibbins it is very possible Andy it’s just the kind of thing that catches people out, no everyone will know to flash but most will look and goo ohh it’s ready to connect.
I agree Andrew, Ive seen a few videos where people have stated its wired incorrectly when actually its a dedicated programming cable which im actually please to finally see FRSKY start putting these in the packets instead of having to manually create them. I have just ordered two R-XSR's for some up coming builds so im going to have a look it the paperwork says anything about the cable or not.
Hi, really useful video. I have the r-xsr wired into my matek f405 fc via the green sbus cable going into the sbus pad on the fc board, however I still cannot get any receiver input signal at all in betaflight. The UART 2 port which it is wired into is selected as serial and I have the config set to SBUS yet still no change. Any ideas? Cheers, Phil
FPV Sketchy yes I did, but sorry to say it was just a bad part. The place i got it from took it back and sent me a replacement because it was apparently faulty.
ok thanks for replying. I will try updating my betaflight firmware on FC and if that don't work I will contact the seller. problem is I have had it in the packet 3-4months.
Hey guys, I´m having the same problem and it drives me crazy. The receiver is binded to my taranis in sbus mode (blue light is on) I tried the IO2 and the UART2, set the serial rx port in the ports tab and switched receiver to serial rx (SPEKSAT, SBUS etc.) + SBUS as serial receiver, but can´t get a signal in betaflight. :( Do you use the LBT or nonEU Firmware for the receiver?
It's so typical Chinese manufacturers throw everything and more into box but left out accurate documentation and common sense. I had hours and hours of confusion and detective work to try to get simple things working on Frsky equipment but eventually it works, kind of.
Mad RC so dumb question then. Do I need to use s.port to get telemetry. Not trying to use any additional equipment. Just rxsr to my fc. Would like to have Rssi in osd if possible but def get telemetry. Iv been looking around but nothing clear cut. I’m a complete noob so any additional details would be greatly appreciated.
It depends the flight controller, if yours supports direct SPORT then you can connect. If using Pixhawk for instance you need an sport to UART adapter.
By chance does anyone know why after binding successfully and receiving telemetry when I go to cycle the battery and then my taranis rebound I get a blue light alongside the green one on the receiver as well as constant beeping from the buzzer? If anyone can help please feel free to shoot me your ideas I am at a loss with my kopis one ? ? HELP!!!
Im having problems i have the beta95x v3 405 chinwhoop all clean build i have xm+ and t -lite i flash the receiver and bind it and i have green light its bind good but no sticks input in betaflight receiver the port im turning uar 4 for the caddix vista and for the xm+ uar 3 and in the last right im making vtx tbs smart audio and in con.. serial based and down its sbubs And just when i turn the quad on i have no stick input i try to see many videos i didnt get any help please if any one lnow something just tell me what to do guys i have this issue from month now i didnt even fly it lol 😕🚶
that cable is for programming the rx from the radio, using the radio to flash the rx. it works for that, the other wire harnes is the one intended to use for connection to FC
Yea that appears to be the case its just that people will automatically assume its a Sbus or RX cable IMO, thanks for the confirmation thats fantastic
Mad RC people will soon learn to verify pins and wiring for proper output- kinda important for avoiding smoke
Lol and all these people thanking for the fix that ain't a real fix. Just hoping they remember to switch the pins back before trying to update the firmware.
@@skypilot23 Channeling Captain Obvious here: The wiring errors that do NOT result in smoke, are far more difficult to detect. :D
OMG!!!!!!
I was bonkers for 2 days in disbelief that the wiring was wrong....
Like you I finally tore the quad down to the individual components and you are SPOT ON!!!
Geez! You have saved me from pulling all my hair out.
It works now!
SUBSCRIBED!
Thank you!
Caught me out too, spent days trying to suss this out only to realise that I should have read the wiring diagram first.... thanks for the vid mate.
I have two rxsr receiver and three quads. Recently decided to use this cable for one of the quads to connect to FC. This was the same problem. Thank you for sharing. Saved my day.
Nice 👍
Thank you for this video! I spent HOURS trying to figure out why I had no stick inputs in INAV. This was the problem!
You sir, are a life saver, I ignore the manuals, because they provided the handy connector, little did I realise it's only for flashing firmware. They should put a warning sticker on it.
You are my hero! After 3hrs of figuring out the same problem (no signal from R-XSR on Pixhawk 2.4.8) and next to frustration i found this video. Exactly the same problem solved now by setting the signal cable from SBus to SBUS_OUT/CPPM).
Lesson1: ALWAYS CHECK THIS THIS CHANNEL FIRST IN CASE OF PROBLEMS ;-)
Lesson2: Check the damn wiring and connection points!
Thank you very much for all your great videos. Would have given up this hobby already without all those detailed explanations for pixhawk and all around from you!
Thanks :)
I'm just going through this myself! About an 1.5 hours in like yourself. Oh what a nightmare... So glad to have found this video! Thank you Mad RC
Yea really threw me this one for a while so thought id do the video :)
I spent hours trying to figure that out. Thank you so much for pointing this out! I thought I had a defective receiver or autopilot or controller or something. Moving that one wire over has completely solved the issue!
Thanks glad you sorted it
Oh my gosh! That's it!
You just saved me a bunch of time! Thank you!
Spent days trying to figure this out when building my second frame. Thank you for pointing it out to me. It was driving insane!
Me too :)
how did you change the wire location? I don't want to break my casing
As others have already said, the harness with the servo wire is for programming the rx via a taranis smart port.
I managed to flash a newer firmware version by plugging into a mysterious port in the battery compartment of my Taranis X9D+ and selecting Flash SPort Device in the menus. Yet I STILL did not catch on!
BTW, It was the second R-XSR--I tried hooking up the first R-XSR to the External Radio terminals bottom 3 pins and managed to quietly burn up something. No more blinky lights!
I plugged the second R-XSR into my flight controller, bound it but it didn't work! I've moved the yellow wire as instructed here. There's the "inverted SBus" issue, brilliant video on that also, thanks!
Bless your heart. Same problem drove me crazy. Fixed now!
I’m glad your sorted.
Caught me off guard too. Saved me hours of frustration. Nice work!
I ordered 2 r-xsr receivers, before Christmas and was wondering why i also geht No Output Channels! I checked the Plug and das it! The Yellow Wire comes from the 3rd Pin/telemetry!
Thank you👍 I build allready 7 Quads before and couldnt find out why this build is Not working! 😂 After 2 hours in get now smart of IT! Thx from GER
That blk,red,yellow is for firmware upgrading and plugs direct to the taranis radio.
I changed it...my board went red and the green went off on the flight board...still knackered here.
Thank you ! Thank you! This drive me nuts!
i was almost ready to jump the cliff until i came across this post, thank God i did!!!
Thanks it drove me mad too :)
WOW thanks for this video!!! First i couldn't bind my R-XSR to my taranis and had to reflash a bug fix on the R-XSR ... Then i had no control... Wich i solved thanks to this vid.. FRSKy did it this time took my a whole evening... :(
Dude !! you saved me. Being messing around to fix this for a while. Thanks
Thank You so much, I have spent a lot more than 1.5 hours on this.
You safed my life
Im glad I helped
THANKS!!! I had no clue what that "extra cable" was for! Relating said cable to the pinouts listed in the "manual" was the missing link! I've made the cable mod, can bind, but it's ACCESS, not ACCST like my Controller. I can't find a backward path for downgrading to ACCST firmware, OR a forward path for upgrading my Controller to ACCESS. Hoping someone's delved into that situation.
That servo cord is for Doing Updates only!,, its wired for when u plug it into the back of the Taranis
Thank YOU! YOU ROCK BRO GGOD CALL!
Lifesaver vid!
thanks, you saved me today
Nice clarification, but 3min 40sec? It could have been done in 40seconds
Thanks a lot. Got the same bug
thanks
It's not wrong wiring, 3 wire cable is for programming... the multi wire cable is the wire you use to connect to fc
Yers we know this now but many assume like my self that get it mixed up.
Got a quick question... Mine binds and talks... But won't maintain a lock with the transmitter... Also have the issue with the XM+... any ideas?
You can get issues at close range in a few M but it should be fine once out of that overload range, are you using LBT firmware ?
You‘re my hero
Saweeeeeet thank u so much
Perhaps, the cable was wired for reflashing the Rx, as I think reflashing is performed thru the smart port, Just a thought. Andy
Andrew Dibbins it is very possible Andy it’s just the kind of thing that catches people out, no everyone will know to flash but most will look and goo ohh it’s ready to connect.
I agree Andrew, Ive seen a few videos where people have stated its wired incorrectly when actually its a dedicated programming cable which im actually please to finally see FRSKY start putting these in the packets instead of having to manually create them.
I have just ordered two R-XSR's for some up coming builds so im going to have a look it the paperwork says anything about the cable or not.
Hi, really useful video. I have the r-xsr wired into my matek f405 fc via the green sbus cable going into the sbus pad on the fc board, however I still cannot get any receiver input signal at all in betaflight. The UART 2 port which it is wired into is selected as serial and I have the config set to SBUS yet still no change. Any ideas? Cheers, Phil
Phil did you find a fix? I am currently having the same problem.
FPV Sketchy yes I did, but sorry to say it was just a bad part. The place i got it from took it back and sent me a replacement because it was apparently faulty.
ok thanks for replying. I will try updating my betaflight firmware on FC and if that don't work I will contact the seller. problem is I have had it in the packet 3-4months.
Hey guys, I´m having the same problem and it drives me crazy. The receiver is binded to my taranis in sbus mode (blue light is on) I tried the IO2 and the UART2, set the serial rx port in the ports tab and switched receiver to serial rx (SPEKSAT, SBUS etc.) + SBUS as serial receiver, but can´t get a signal in betaflight. :(
Do you use the LBT or nonEU Firmware for the receiver?
Mine is LBT (I'm in the UK) but as I said, for me it was exactly the same as you and it turned out to just be a faulty part.
no idea how frustrated i was.... thank you
That's the firmware flashing cable. used to plug into the TX
Yea that appears to be the case its just that people will automatically assume its a Sbus or RX cable. thanks for the confirmations though
? You mentioned nothing about the ppm function of the rx?
*"Bonkers!"* 🤣
It's so typical Chinese manufacturers throw everything and more into box but left out accurate documentation and common sense. I had hours and hours of confusion and detective work to try to get simple things working on Frsky equipment but eventually it works, kind of.
soldered the otehr cable and removed two wires...still zero....it is bound .
Thank you, thank you, thank you, thank you.........signed.....novice quad builder....
Thanks
i cant bind so do you bind in smart port then change
what is s.port for on the rx? i thought if i wired that to a uart it would provide telemetry? is that true?
Yea it’s custom telem output that can be connected to things like the Pixhawk Via an adapter to give info on taranis screen
Mad RC so dumb question then. Do I need to use s.port to get telemetry. Not trying to use any additional equipment. Just rxsr to my fc. Would like to have Rssi in osd if possible but def get telemetry. Iv been looking around but nothing clear cut. I’m a complete noob so any additional details would be greatly appreciated.
It depends the flight controller, if yours supports direct SPORT then you can connect. If using Pixhawk for instance you need an sport to UART adapter.
I did the same thing 😅
By chance does anyone know why after binding successfully and receiving telemetry when I go to cycle the battery and then my taranis rebound I get a blue light alongside the green one on the receiver as well as constant beeping from the buzzer? If anyone can help please feel free to shoot me your ideas I am at a loss with my kopis one ? ? HELP!!!
Consider yourself lucky I can’t get the blue led to come on if my life depend on it smh
I COULD KISS YOUR GODDAMN FEET.
Im having problems i have the beta95x v3 405 chinwhoop all clean build i have xm+ and t -lite i flash the receiver and bind it and i have green light its bind good but no sticks input in betaflight receiver the port im turning uar 4 for the caddix vista and for the xm+ uar 3 and in the last right im making vtx tbs smart audio and in con.. serial based and down its sbubs
And just when i turn the quad on i have no stick input i try to see many videos i didnt get any help please if any one lnow something just tell me what to do guys i have this issue from month now i didnt even fly it lol 😕🚶
I also solder in the board 2 points for the sbubs
I aslo flash my betafpv 405 board to the new version also didn’t help me
You could have just read the instructions or just google what you typed as title of this video
Probably. But as so many also had the same issue I felt it warranted highlighting. Sorry this was not to your approval.
wrong cable? give me a fucking break. I'm not getting sbus or ppm from an rxsr, and I'm using the correct cable.
PLEASE STOP SHAKING THINGS DURING FILMING.. THE connector, instructions etc...