Cleanflight, LED's on Nano

I am building a Y6 for AP.

I want to install LED’s to help with orientation, and CleanFlight has a great utility to graphically lay out the LED locations and program different modes. I tried to hook up the Nano, but CleanFlight failed to open the serial port (Comm5, 115200 Baud). I believe I read somewhere CleanFlight wouldn’t work with the Nano, and was wondering if anyone knows of an easier way to program LED’s than using the CLI line…

Thanks!
Gary

Hi Gary,

The Quadrino Nano is not CleanFlight compatible as it require a 32bit processor which is not Arduino compatible.
At the moment we didn’t explore the LED under MultiWii but it’s something we would like to have. We did found THIS and we want to start from there.

Let us know if you get something working …!

:slight_smile:

Hi, Eric!
Would it be possible to program a channel or 2 activated by a switch on my 9Extreme to turn on the lights? I could maybe have a off / on switch of the color scheme, and (hopefully) either a low battery activated flash routine, or different color scheme (like front arms change to yellow on a set battery voltage?
I have a bunch of 5050 WS2812 RGB single LED’S, and have been wiring them up into 8 LED strips.


I just need a signal to tell them what color and how bright to light up… That signal is the problem, isn’t it?
My fall back position is to get solid color LED’s, and power them through the ECS BEC’s (and use the telemetry on the TX to tell me about low battery state)!!!

Thanks!
Gary

The MultiWii software can monitor battery and trigger a buzzer or a LED but it’s momentary.
You can have a look at the “Lynxmotion Quadrino Nano - Battery Monitoring & Alarms” tutorial.

There is an option in the code for a X-Aircraft Pilot Lamp, look bellow for the code in config.h

/********************************************************************/ /**** Buzzer ****/ /********************************************************************/ #define BUZZER #define RCOPTIONSBEEP // uncomment this if you want the buzzer to beep at any rcOptions change on channel Aux1 to Aux4 //#define ARMEDTIMEWARNING 330 // (*) Trigger an alarm after a certain time of being armed to save you lipo (if your TX does not have a countdown) //#define PILOTLAMP //Uncomment if you are using a X-Arcraft Pilot Lamp

Hi, Eric!
Not being a programmer, I’ll default to lights set up to Tx switches. I look forward to learning how to program, but have a TON of stuff to learn just to get flying !! Biggest study subject right now is configuring the 9Xtreme Tx and XJT Rx I want to use…
I know it’d be a TON of work, but I really think a set-up vid like this [font=Roboto, Arial, Helvetica, sans-serif][highlight=#NaN1c1c]https://youtu.be/rc-VC9CIel0?list=PL_UNjO94bqmUy2-3oGdahcCpIV6lAYFqH[/highlight][/font] (my next build!!) for a Quadrino recommended Tx and Rx would tremendously decrease the learning curve for Noobies like me, and most likely, increase sales of the Nano!!
I emailed Colin about the Rx wiring question, and he very graciously pointed out that I was getting myself confused over legacy Zoom wiring diagrams and setup instructions, so I am now very confident that I will be able to set up the SBus Rx once the inverter arrives… He told me your advice is rock-solid and should be followed to the “tee”. Will the pin-out of the XJT to the Spektrum port be the same as the Spektrum Rx (per your post rcgroups.com/forums/showpost … ostcount=4 ) once the inverter is installed on the signal wire?
Thanks for all the great help!!
Gary

We agree that a video like that would be nice, are you actually proposing for doing one (HaHa) ?

The connection for SBus and Spektrum are on the same “Serial” port and it’s Serial3 on an ATmega 2560 controller like the Quadrino Nano.
You could in fact, connect it on the Serial3 port on the side, if you do not have the available space underneath. The bottom connector is mostly to connect a Spektrum satellite as it’s using the OEM (spektrum) type of connector.

We found a little error in the TX and RX naming on the pinout sheet and we will correct it.
But you can base yourself on the picture attached.

:slight_smile:

Hi, Eric! Thanks for the reply and the attached drawing. Unfortunately, I don’t have a clue which way is up regarding how to wire it. I think this is the way…

Please verify the correct pin-outs I have run for the Rx and Motors?

And just to be sure, I am now not needing to use the radio connection header at all?

I will post a tutorial for SBus with pics once I figure out all the proper Tx and Rx settings in WinGUI, and on my 9Extreme menus…:mrgreen:

Thanks!
Gary

This seems to be a good connection. You have the TX of the receiver connected to the RX pin of the serial port on the Quadrino Nano.
For the motors, you inverted the Purple and the Blue wires but they are still labeled right so you should be fine without doing any modifications.

You need to enable the SBus receiver in the FCT and flash your board with this configuration.

:slight_smile:

Thanks, Eric!
I set the Tx protocol to SBus, but now the channel order box is grey’ed out and cannot be changed. I do not know what channel order to program into my Tx (9X w/ 9Xtreme upgrade board) model. :blush:Is the channel order set by the SBus protocol? That would be cool, I think?!:?
The Tx is currently set to RETA. Is that correct?

Thanks!
Gary

We’ve not tested your particular setup (FrSky) but once in the WinGUI, do you have movement on your RX channels ?
You will be able to change the channel assignation if needed in your transmitter but for now, make sure they work.

The setting by default in MultiWii for SBus is:

#define SBUS PITCH,YAW,THROTTLE,ROLL,AUX1,AUX2,AUX3,AUX4// ,8,9,10,11,12,13,14,15,16,17 // dsm2 orangerx

Eric,
Just tried to bind the Tx (XJT module on 9X with 9Xtreme upgrade board) with Tx (X8R with jumpers on channels 1&2, 3&4 to set Tx’s mode to (PXX?) channels 1 - 8, and channels 9 - 16 to PWM), but no joy. Have a post to a very helpful guy on OpenRCForums to try to debug, but currently getting close to 100% Tx signal strength on Telemetry, but about 20% from Rx… and won’t bind. Tried to hold bind button on XJT module, then power up Rx while holding F/S button (plug FC SBus cables into SBus port on Rx), both beep, no bind. Tried to select “Bind” on model setup in 9Xtreme V.218 firmware on Tx, then power up Rx with F/S button down, both beeping, no bind. Tried powering on Tx while holding bind button on back of XJT module, bind beep, powered up Rx while holding F/S button on Rx, it beeps, no bind. Then went into FW, selected “Bind” on “Model Setup”, Tx, Rx, AND module beep, no bind.
I powered up the aircraft with only the motor 3 ESC plugged into the Nano, then plugged the SBus connector to the Rx SBus port. Got power - on LEDs to the Rx. LEDs indicate it’s in bind mode, but seems to not be hearing the Tx.
I must be doing something wrong here!!:frowning:
Without a connection, I am not going to get any readings from WinGUI, am I?
Thanks!
Gary

The bind process do not involve the flight controller, it must be done before.
I would suggest you to connect a power source (ESC) directly to the receiver with nothing else connected to it and do the bind process. This would avoid any interaction.

Cool, will do it tonight!
Gary

Eric,
Still the same behavior as described before when plugging the Rx straight into an ESC cable. Tried SBus port, PWM port, Smart Port, no change in green LED ON, red flashing, and beeping sound from Rx no matter where I plug the cable in while holding the F/S button down… The Rx goes into bind mode, beeping and showing correct LED colors, but it seems to have a problem gettin’ along with the Tx!!!:frowning: Tried bind setting in Rx Model Setup, same deal. Tried pushing Bind button on XJT module, power up (Tx starts beeping), then hold F/S button on Rx and power up with ESC cable, still no joy :unamused:
Do you have any ideas of what to try? I have cables and adapters on the way to re-flash the Tx module and Rx with the latest firmware; maybe that’d help?
I know that Tx and Rx problems aren’t really your responsibility, and really appreciate the help you have been. I am definitely going to do a Tutorial on this build once it all comes together and post it on the forum to help others who want all the Wizz-Bang features available, and are willing to spend insane amounts of time and $$$$ to achieve it!!!:lol:
Thanks again; 3 thumbs up!!
Gary

Eric,
The Rx and Tx may be bound, but the LED’s on the Rx are not matching it’s instructions. I’ll have to check it on the computer to verify stick movements.
Thanks!
Gary

Eric,
Got the new Nano, installed it, and viola! GPS works, Rx reads Tx commands (although I had to completely remap the Tx channels to TAER) and motors spin up!!
I did the Advanced ESC calibration, then re-flashed the Nano with the latest firmware. A concern; bottom motors don’t start to spin until @ 20% throttle - is that a problem? I had to spin the motors to check proper direction, and had to switch ESC wires on 3 out of 6 to get them spinning correctly. Now all spinning as per diagram in Nano User’s Guide.
Looks like I am about ready to maiden… and scared as hell to do it after all this work!! :confused:
Gary

Great news…!!

Usually they should all start to spin at the same time, the other 3 who start earlier spin very slowly ?
If so you can increase the MinThrottle in the WinGUI. This is the minimum signal sent to ESC’s when they start to spin. (WinGUI / FC Config / Min Throttle)

Eric,
When I checked, WinGUI showed Thr at 978. I reset the limits in my 9Xtreme Tx, and got it to 999. The motor starting problem hasn’t improved:

10% Thr, upper right and left motors spin slowly. 11% or 12% Thr, lower rear motor spins. 52% Thr, lower right motor starts. 60% Thr, upper rear motor goes. 65% Thr lower left finally kicks in. At 100% Thr, it sounds like the 3 lagging motors are running at 1/2 or less speed…

This does NOT sound like a calibration problem, does it? Any other ideas?

I have 2 spare brand new ESC’s; I’ll install them on the lagging motors and see if those motors improve…
Gary

Are you relying only on reading the outputs in WinGUI without propeller?

Eric,
Yes. Not good?
Gary