I suspected there is an ongoing issue with neopixels and some firmware version, but I cant find a reference to that now so I’ll keep searching. Maybe I’m wrong about that too.
Just to cover off the basics, do you have:
a 5vdc supply for the LEDs
a common ground between the LED strip, the 5v power supply and the Cube servo negative pins
Also what other Main and Aux outputs are in use?
Maybe a photo or even hand-drawn diagram of your wiring…
You should be able to use this modified script “My workaround (strobes work upon arming):” from the discussion below. It’s not a permanent fix, but should keep you out of trouble for a while
@xfacta@Ronald The reason that NeoPixel LEDs don’t function on Cube is because they require > 0.7*Vcc signal line, Aux pins put out 3.3V and generally power tends to be solid 5V.
Regarding NeoPixels, to make them work you need to place a Pullup (around 5K Ohm to 5V) on the signal pin to drive the signals to meet the specification for them. Once you do that I believe they should start functioning. If you are still having issues please let us know.
I know that there is a fix here NeoPixel — Copter documentation but for Cubes the fix that I recommend is the one to take, and is a clean solution that works for cubes as we have Protection Circuit, which allows us to safely place a pull-up on the signal end.
Could we use BRD_PWM_VOLT_SEL to 5v in ardupilot ? On cube orange plus mini should that affect all outputs ? Or is there on mini carrier distinction between main and aux output ?
I am getting the same result Selenita is getting. If I plug in my Neopixel into chan8 the light does not work. When on aux chan9 it works. I found this out when using a lua script first. Anytime I tried to drive the led from main my script would fail to setup the led. The Aux channels worked. Could this be a firmware issue. I am running Arducopter 4.4.4