Hi,
I have been reading studying and pouring over articles and videos for weeks prior to my parts arriving, and I have just started putting the electronics together for testing.
I am using the Turnigy X9rPlus, to the FrSky X8r and Acro Naze32 v6 FC. All are new.
I am running Cleanflight and Baseflight via iMac.
I cannot get any inputs to the Turnigy registering on either CF or BF.
I will run through what I have done so far.
Set up the X9r according to the manual. Set up a new model and set to D18 Ch 1-8.
Powered up the X8r and paired successfully with solid green light. So far so good.
I have connected one motor and Esc and connected to the Naze32 to provide power. After messing about with various USB connectors I got one that worked and made connection to cleanflight.
Wanting to connect via SBUS to eventually have access to more than 8 channels, I ran a cable from ground, power and signal, to ground power and pin 4 UART2 on the naze32, which I believe is correct for an SBUS setup. So far so good. Turnigy and X8 paired, X* and Naze32 connected in SBUS, and Cleanflight opening port and reading the Naze, as I can move the board about and quad image on CF moves about etc. This is where my issues begin.
I have calibrated the Accelerometeron the setup page. Then, on the Ports page, I run into problem one.
UART1 is appearing switched on by default. I then switch on UART2 at 11500 baud and Serial RX. When I save, the switched for UART2 and Serial RX bothe revert to off. I cannot get this setting to stick. If i select UART2 and save its fine, but UART2 and Serial RX together will not save. (I read that the Serial RX must be on for UART2?) This may be the core of my problem but moving on
In Configuration, I set mixer for Hex X as that is what I am building. I select Receiver mode as RX_Serial, and in the Serial receiver Provider box I select SBUS. Thats all I set then try to save.
The Sbus line stays the same in the Provider box, but the Receiver mode shows nothing selected?
In Modes, I have set a switch on the X9 as the arm switch but not sure how to set it up in the mode section of cleanflight. I any event, its not arming and the switch shows no reaction on CF.
If I go to Motors, I have motor control from the Cleanflight sliders.
However, when I go to Receiver and move the joysticks around on the X9, nothing happens.
This is what I am seeing
I should add that the Naze 32 has been acting a bit strange (I think!) When I power it up the blue light is steady, and the Green light flashes, which I think is normal. However, on quire a few occasions when connected to CF, and particularly if connected to CF and one ESC at the same time, it seems to freeze. CF cannot read the Naze, and there is a solid green and red light along with the blue one. It has done this at least a dozen times while working on this yesterday. Sometimes disconnecting and reconnecting gets it going again for a while. On 3 occasions it would not come on properly and I had to use the firmware flasher on CF. I have also tried with 2 or 3 different firmware versions (all pretty recent) but its still doing this. I am concerned if this locks up like that in flight.
So can anyone offer advice on this? I haven't tried via pin to pin connection rather than SBUS, but this has me tearing my hair out. Every video I have watched makes the process look very easy, and I am wondering is there a step I am missing, or a wrong connection, or an issue with this NAze32.
Thanks
I have been reading studying and pouring over articles and videos for weeks prior to my parts arriving, and I have just started putting the electronics together for testing.
I am using the Turnigy X9rPlus, to the FrSky X8r and Acro Naze32 v6 FC. All are new.
I am running Cleanflight and Baseflight via iMac.
I cannot get any inputs to the Turnigy registering on either CF or BF.
I will run through what I have done so far.
Set up the X9r according to the manual. Set up a new model and set to D18 Ch 1-8.
Powered up the X8r and paired successfully with solid green light. So far so good.
I have connected one motor and Esc and connected to the Naze32 to provide power. After messing about with various USB connectors I got one that worked and made connection to cleanflight.
Wanting to connect via SBUS to eventually have access to more than 8 channels, I ran a cable from ground, power and signal, to ground power and pin 4 UART2 on the naze32, which I believe is correct for an SBUS setup. So far so good. Turnigy and X8 paired, X* and Naze32 connected in SBUS, and Cleanflight opening port and reading the Naze, as I can move the board about and quad image on CF moves about etc. This is where my issues begin.
I have calibrated the Accelerometeron the setup page. Then, on the Ports page, I run into problem one.
UART1 is appearing switched on by default. I then switch on UART2 at 11500 baud and Serial RX. When I save, the switched for UART2 and Serial RX bothe revert to off. I cannot get this setting to stick. If i select UART2 and save its fine, but UART2 and Serial RX together will not save. (I read that the Serial RX must be on for UART2?) This may be the core of my problem but moving on
In Configuration, I set mixer for Hex X as that is what I am building. I select Receiver mode as RX_Serial, and in the Serial receiver Provider box I select SBUS. Thats all I set then try to save.
The Sbus line stays the same in the Provider box, but the Receiver mode shows nothing selected?
In Modes, I have set a switch on the X9 as the arm switch but not sure how to set it up in the mode section of cleanflight. I any event, its not arming and the switch shows no reaction on CF.
If I go to Motors, I have motor control from the Cleanflight sliders.
However, when I go to Receiver and move the joysticks around on the X9, nothing happens.
This is what I am seeing
I should add that the Naze 32 has been acting a bit strange (I think!) When I power it up the blue light is steady, and the Green light flashes, which I think is normal. However, on quire a few occasions when connected to CF, and particularly if connected to CF and one ESC at the same time, it seems to freeze. CF cannot read the Naze, and there is a solid green and red light along with the blue one. It has done this at least a dozen times while working on this yesterday. Sometimes disconnecting and reconnecting gets it going again for a while. On 3 occasions it would not come on properly and I had to use the firmware flasher on CF. I have also tried with 2 or 3 different firmware versions (all pretty recent) but its still doing this. I am concerned if this locks up like that in flight.
So can anyone offer advice on this? I haven't tried via pin to pin connection rather than SBUS, but this has me tearing my hair out. Every video I have watched makes the process look very easy, and I am wondering is there a step I am missing, or a wrong connection, or an issue with this NAze32.
Thanks
