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.
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
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.
16-Dec-2019, 01:43 PM (This post was last modified: 25-Dec-2019, 03:22 AM by SnowLeopardFPV. Edit Reason: Added footnote reference. )
@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:-
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.
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.
(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:-
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.
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...
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.
(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. ;-)
16-Dec-2019, 06:49 PM (This post was last modified: 16-Dec-2019, 06:54 PM by SnowLeopardFPV.)
(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.
(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...
(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