Hello guest, if you read this it means you are not registered. Click here to register in a few simple steps, you will enjoy all features of our Forum.
This forum uses cookies
This forum makes use of cookies to store your login information if you are registered, and your last visit if you are not. Cookies are small text documents stored on your computer; the cookies set by this forum can only be used on this website and pose no security risk. Cookies on this forum also track the specific topics you have read and when you last read them. Please confirm whether you accept or reject these cookies being set.

A cookie will be stored in your browser regardless of choice to prevent you being asked this question again. You will be able to change your cookie settings at any time using the link in the footer.

Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
FrSky R-XSR no communication with FC after crash
#1
I've crashed my quad through some trees and it fell at the edge of a lake. I found it sideways with both right motors slightly in water, but everything else was dried. Powered it on and my transmitter (X9d+) connects fine to the receiver but it seems like the FC does not get any signals from the receiver. I took it home, plugged in into PC and confirmed my suspicion, FC thinks that there is no transmitter but my Taranis connects fine to the R-XSR with maximum RSSI strength. Took it a bit apart, all the LED on the receiver seems fine, all the cables are connected properly to the FC, there is no obvious problem. Is there anything else I can do before I order a new receiver? Can it be the FC?
Reply
Login to remove this ad | Register Here
#2
Is there a blue LED on the R-XSR as well as the green LED when your transmitter is powered on? If not then your R-XSR has somehow switched over to CPPM mode. To switch it back you need to hold the bind button on it for 4 seconds until the blue LED flashed 3 times. Then power cycle the receiver.

If that isn't the issue then check your Betaflight Configuration settings. It's not been unknown for the configuration to reset itself to back to defaults in the event of a power issue.
Reply
#3
Yes, there is the blue LED as well as the green so it's not in CPPM mode. I have also checked (again) in Betaflight Configuration settings and I can't see anything wrong. Everything is as it was before. I am going to desolder and resolder the SBUS wire and see if that makes a difference, even though I can't see anything wrong with the connection.

UPDATE: Redone the wiring and also checked with a multimeter that there is a connection between FC pads and receiver pads. Not sure if I should just order a new receiver.
Reply
#4
It's difficult to say what the problem might be. You could have fried the UART that the receiver communicates through. Roll the dice. The cheapest item to get a replacement of is the receiver so that is probably the obvious thing to go for. Even if it turns out not to be the receiver then it's always handy to have a spare receiver in your spare parts bin, so it won't be a wasted purchase.
Reply
#5
Why not try a different UART?
Reply
#6
(07-Apr-2020, 06:00 PM)Birbal Wrote: Yes, there is the blue LED as well as the green so it's not in CPPM mode. I have also checked (again) in Betaflight Configuration settings and I can't see anything wrong. Everything is as it was before. I am going to desolder and resolder the SBUS wire and see if that makes a difference, even though I can't see anything wrong with the connection.

UPDATE: Redone the wiring and also checked with a multimeter that there is a connection between FC pads and receiver pads. Not sure if I should just order a new receiver.

It may be like they said a UART....... If you happen to have another that isn't being used it's worth a shot like Voodoo said.. What did you find with the multimeter? Did the 5V pad give the appropriate voltage?
'Ignore' is the route word of Ignorant. 
Reply
#7
Update: I have tried different UART and also bought a brand new receiver but still no luck at all. Measured with the multimeter the voltage on the receiver and is 5.13V steady. I am getting mad and running out of ideas.
Reply
#8
Have you tried a complete erase and reflash of the firmware?
Reply
#9
(16-Apr-2020, 07:08 PM)Birbal Wrote: Update: I have tried different UART and also bought a brand new receiver but still no luck at all. Measured with the multimeter the voltage on the receiver and is 5.13V steady. I am getting mad and running out of ideas.

You should check the voltages on the flight controller as well just in case. It wouldn't make sense that it's the issue with the flight controller given your description. But your issue not being resolved doesn't make much sense as it is... it's weird, it doesn't seem like there should be anything stopping you from connecting but something is.....
'Ignore' is the route word of Ignorant. 
Reply
#10
(16-Apr-2020, 08:45 PM)bLoWsMokE Wrote: You should check the voltages on the flight controller as well just in case. It wouldn't make sense that it's the issue with the flight controller given your description. But your issue not being resolved doesn't make much sense as it is... it's weird, it doesn't seem like there should be anything stopping you from connecting but something is.....

I did everything and nothing worked (even full erase and reflash the firmware as the previous post suggested). I gave up and just ordered a new FC...it will be the 3rd one I go through in 5 months since I've started FPV  Cry
Reply
#11
So in conclusion, old RX + new FC = problem solved. I keep wondering what happened to that FC that it won't read any SBUS signals  Thinking . Apart from this everything seems to work on that FC, camera, VTX so the UARTs are functional...ESC is responding normally, etc.
Reply
#12
it is odd that all you Uarts are not working.
Reply
#13
(22-Apr-2020, 03:11 PM)voodoo614 Wrote: it is odd that all you Uarts are not working.

UART is also the microUSB connector as well that I plug in into PC with BetaFlight. That is working...so I think UARTs are fine but for some reason does not read the SBUS protocol from the RX. Anyway when I get some more time, I'll play more with that old FC to see if I can still use it.
Reply


Possibly Related Threads...
Thread Author Replies Views Last Post
  GPS not in betaflight after Crash ToasterBox 0 53 19-Jun-2024, 03:38 AM
Last Post: ToasterBox
  Problem no rx led in meteor 75 pro frsky version arju 11 224 09-Jun-2024, 06:27 PM
Last Post: arju
  Cinelog20 just hovers after crash flaqfpv 14 446 05-May-2024, 06:22 PM
Last Post: SeismicCWave
  Recovering after crash and diagnostic mogadanez 19 594 26-Mar-2024, 02:23 PM
Last Post: Rob Axel
  No inputs after crash, still bound to reciver FPVManiac 5 249 03-Feb-2024, 10:05 PM
Last Post: Pathfinder075


Login to remove this ad | Register Here