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
HELP! Betaflight Not Picking Up sticks In reciever
#1
Hello all! New to this game, 
I have purchased an Iflight Nazgul 5 
With Iflight Succex F4 Fc

Purchased an fr sky R-Xsr Receiver and have soldered too 5v gnd and nr2 pad.

I have successfully Bound it to my transmitter. 
However once in betaflight the tab for receiver wont pick up any stick inputs. 
I have tried turning on serial rx in all uarts one by one and tested the sticks but still nothing. 

I have a battery connected and the receiver is powered.

Can anyone help me please
[-] The following 1 user Likes puckacostello's post:
  • Aelex
Reply
Login to remove this ad | Register Here
#2
There is a few problems with the nR2 from a few other members here. The sure way is to solder the tiny "B" on the R-XSR to the normal R2.

Can you post a dump, so we can help you with the settings after you rewire.
Reply
#3
Hey, I have exactly the same problem, but I don't quite understand the solution, because I am a total beginner...
What do I have to solder exactly to where? 
Thank you very much!
Enclosed a picture of the wiring


Attached Files Thumbnail(s)
   
Reply
#4
You only need to to this if wiring the regular way doesn't work.  Wire the Uninverted SBUS (B label) to the R2 on the FC.

[Image: lPSCpFal.jpg]

[Image: VAOjOixl.jpg]
[-] The following 1 user Likes voodoo614's post:
  • Aelex
Reply
#5
Thank you very much, I will test your suggested solution as soon as possible and give you feedback on how it worked.

Nevertheless I would be interested to know why this way is so necessary, because after all the Nazgul should work out of the box? Thanks in advance!

greetz
Alex
Reply
#6
You didn't buy a BNF or RTF Nazgul, so it is not working out of the box. You bought a separate receiver to wire to the FC. Yes, what you did should have worked, but unfortunately it is not working. Either you can keep on trying with the same wiring or try something different. I have seen it many times that the inverter circuit for some reason doesn't work. That is why I suggest you bypass it and hope it will work.
Reply
#7
I actually bought an RTF Nazrul 5 from Banggood. The R-XSR receiver was chosen by me and already installed with the delivery.

That's why the troubleshooting is so difficult now, because everything should work without problems ready to fly. Which unfortunately is not the case.  Huh
Reply
#8
@Aelex - Is it correct to assume that you haven't touched any of the wiring at all on the Nazgul? (i.e the R-XSR is soldered in as it came from the supplier and you haven't messed with any of the solder connections).

Have you actually successfully bound your transmitter to the R-XSR? (you should get a blue LED and green LED on the R-XSR when the receiver is powered up and your transmitter is switched on).

If your transmitter is successfully bound to the R-XSR, then can you please do the following:-
  1. Post some pictures of how the R-XSR has been wired to the flight controller which show the wiring connections at both ends in case someone at the factory made a mistake with the soldering.

  2. Run up Betaflight Configurator, connect to the flight controller, go to the CLI tab, run the "dump" command, then copy/paste the results from that back here.

Footnote Reference: iFlight SucceX-E F4 flight controller.
[-] The following 1 user Likes SnowLeopardFPV's post:
  • Aelex
Reply
#9
(16-Dec-2019, 01:43 PM)SnowLeopardFPV Wrote: @Aelex - Is it correct to assume that you haven't touched any of the wiring at all on the Nazgul? (i.e the R-XSR is soldered in as it came from the supplier and you haven't messed with any of the solder connections).

Have you actually successfully bound your transmitter to the R-XSR? (you should get a blue LED and green LED on the R-XSR when the receiver is powered up and your transmitter is switched on).

If your transmitter is successfully bound to the R-XSR, then can you please do the following:-
  1. Post some pictures of how the R-XSR has been wired to the flight controller which show the wiring connections at both ends in case someone at the factory made a mistake with the soldering.

  2. Run up Betaflight Configurator, connect to the flight controller, go to the CLI tab, run the "dump" command, then copy/paste the results from that back here.

Dear SnowLeopardFPV,
first of all many thanks for the willingness to help me!

I have now made pictures and the protocol from Betaflight, which I also enclose.

The connections are as they come from the packaging. If you need any other pictures, please let me know and I will deliver new ones.

The bind connection between Taranis x q7 and the R-XSR is green as you can see on the pictures. But in Betaflight there are no control commands...

Here is the link to the pictures:
https://drive.google.com/drive/folders/1...sp=sharing

The protocol from Betaflight is attached.


THANX!!!


Attached Files
.txt   BTFL_cli_SL5_20191216_172618.txt (Size: 23.61 KB / Downloads: 136)
Reply
#10
Unless you've been trying to reconfigure things yourself, it looks like whoever configured Betaflight at the factory mixed up the serial port settings. Run the following commands in the CLI and see if you then get stick movements in the Receiver tab.

Code:
serial 0 8192 115200 57600 0 115200
serial 1 64 115200 57600 0 115200
save

Also, are you seeing a blue LED on the R-XSR as well as a green LED? It's not easy to see from your photos.

BTW, you appear to have a Cidora SL5 and not a Nazgul5.
Reply
#11
(16-Dec-2019, 06:18 PM)SnowLeopardFPV Wrote: Unless you've been trying to reconfigure things yourself, it looks like whoever configured Betaflight at the factory mixed up the serial port settings. Run the following commands in the CLI and see if you then get stick movements in the Receiver tab.

Code:
serial 0 8192 115200 57600 0 115200
serial 1 64 115200 57600 0 115200
save

Also, are you seeing a blue LED on the R-XSR as well as a green LED? It's not easy to see from your photos.

BTW, you appear to have a Cidora SL5 and not a Nazgul5.

Entering the codes does not lead to any changes. I have attached a protocol again.
Can I undo this to be on the safe side? How?

Only the green lamp appears on the R-XSR, not the blue one. Is this normal?

So I packed another picture into the folder, it should already be a Nazgul5. ;-)

Slowly I despair.
Reply
#12
(16-Dec-2019, 06:43 PM)Aelex Wrote: Only the green lamp appears on the R-XSR, not the blue one. Is this normal?

Your R-XSR is in CPPM mode. You need to change it to SBUS mode. Power up the receiver then hold the bind button in for 4 seconds. The blue LED should then flash 3 times to indicate that the mode switching was successful. Power cycle the R-XSR and the blue LED should come on and remain lit.

Leave the CLI changes that I previously got you to run because those new settings are correct for an R-XSR wired to the nR2 pad, with SmartAudio configured on UART1.
[-] The following 2 users Like SnowLeopardFPV's post:
  • mirdep, Aelex
Reply
#13
Haha. I just realized the Aelex is not the OP. I was all confused by Aelex when I was referring to the OP.
[-] The following 1 user Likes voodoo614's post:
  • Aelex
Reply
#14
(16-Dec-2019, 06:49 PM)SnowLeopardFPV Wrote: Your R-XSR is in CPPM mode. You need to change it to SBUS mode. Power up the receiver then hold the bind button in for 4 seconds. The blue LED should then flash 3 times to indicate that the mode switching was successful. Power cycle the R-XSR and the blue LED should come on and remain lit.

Leave the CLI changes that I previously got you to run because those new settings are correct for an R-XSR wired to the nR2 pad, with SmartAudio configured on UART1.

Great, thank you very much! That solved my problem! How can you know that?

This forum is already very valuable for me now, I will hopefully be able to contribute my part in the future...
Reply
#15
(16-Dec-2019, 09:08 PM)Aelex Wrote: Great, thank you very much! That solved my problem! How can you know that?

That's great news. It's all part of the learning curve and comes with experience. As time goes on you get to know and understand how a lot of this stuff works and how it all hangs together Smile
[-] The following 1 user Likes SnowLeopardFPV's post:
  • Aelex
Reply


Possibly Related Threads...
Thread Author Replies Views Last Post
  Cannot clear CALIB arming flag in betaflight necbot 16 361 26-Jun-2024, 06:04 PM
Last Post: necbot
  GPS not in betaflight after Crash ToasterBox 0 73 19-Jun-2024, 03:38 AM
Last Post: ToasterBox
  Receiver doesn't show up in Betaflight asdvcd 3 191 10-Jun-2024, 11:22 PM
Last Post: asdvcd
Exclamation FAO: Member AM35 -> RE: Unable to connect GPS in betaflight SnowLeopardFPV 6 278 07-Jun-2024, 02:04 PM
Last Post: mstc
  Betaflight help Please Tsquared44 9 340 24-May-2024, 04:43 AM
Last Post: wizofwires


Login to remove this ad | Register Here