Nice. I do like the LED rings around motors. I think they look cool.

You’re welcome

Thanks Pete. I’m trying my best. I just try to think if the videos or information that I couldn’t find easily when I first started. Then try to make it easy to understand. If there are any topics you’d like covered, please feel free to drop me a message, and I’ll add it to the list.

Thank you 🙂

Thanks Sergio

No problem. I’m glad it was helpful.

Thank you, I really appreciate that. But more so, glad the video helped.

Thanks Arthur 👍🏻

Light it up Silvio 🙂

You’re welcome Ralph.

It is a little inconvenient. But I did it with my S1100. I think for most things going forward, if I want nav lights, I’ll just use the flytron strobon LEDs. They’re really bright and switchable.

Sorry I don’t have one of those yet. I believe the PnP and kit versions had different LED setups. One needed an extra board that HeeWing sell to work in some cases. But I don’t really know much details. You’d be best asking in a HeeWing or T1 group.

Approximately 1.34A per hour. Without knowing the exact LEDs this is approximate; based on the standard 5050 LED boards or strips. 32 LEDs at 0.21 W each = 6.72 watts Running at 5v = 1.344Ah Running at 12v = 0.56Ah This is of course, with all LEDs on all the time. I’d they are fading or alternating, they will use less energy.

@@MrD thanks

You’re welcome

No, you can start anywhere on the grid. I usually like to lay them out on the grid as they are on the plane. Then it’s easier to know where you are.

Yeah, it kind of helps if they have power 😄

It shows the state of autolaunch in the system messages.

Try reflashing. Make sure you’re selecting the correct target. I have an F405-WING as my test flight controller. It’s been fine on 2.6.1.

Sorry for the late reply. It should be exactly the same as in the video. You would just add the 16 LEDs for the circle instead of the 8 that I have used.

Thanks Mike. Unfortunately not. You would need a blink circuit between the power for the LEDs and the LEDs themselves. The iNav LED feature is only for addressable LEDs.

@@MrD Thanks for your reply Mr.D! It's crazy that a flight controller can't make a couple LEDs blink! On my (H743-WING V2) I believe it has a switchable 5V output on the Vsw pin. I think switchable means that the Flight Controller can switch the voltage on/off? Maybe I could connect my LEDs to this Vsw output and set up some logic in the programming tab to blink the LEDs when armed? Do you think that can be done?

No problem. The flight controllers can make LEDs blink. They just need to be the right kind on LEDs ;) Unfortunately the logic conditions won't help either. There is no timer logic that could do this. If you're using OpenTX, EdgeTX, or ETHOS; you could use the logical switches and timer on there to change a channel from -100 to 100. Then have that channel operate the USER mode that switches the Vsw on and off. But I honestly think a little timer circuit or even ESP32 or nano Arduino would be the better solution. Depending on the LEDs, they may pull more amps than the Vsw pad can handle.

Yeah, I would like the extra functions addressable LEDs would give, and I have some of those LEDs lying about. I just didn't want to tear apart the preinstalled wiring and LEDs or install extra hardware. I now have the arming channel also controlling the USER mode to switch the Vsw on/off (but doesn't blink LEDs). I could put it on a different channel and setup the timer circuit in EdgeTX. I have two channels still free (until I purchase and install a Pan/Tilt camera setup.) I might do that if the programming logic can't control Vsw. I appreciate your help!

Using inspiration from your suggestions, I was able to get INAV to blink the LEDs without any more hardware. I checked the current draw of the 4 LEDs, and it was less than .2 Amps, so I opted to power it off the Vsw output. In INAV, under Programming I set up timer logic (using your above video and a video from Pawel kzfaq.info/get/bejne/odOChqyXrsXMZ4E.html). When armed, the timer overrides CH16. Under Modes/USER, I setup CH16 to control the Vsw output. Here's a link to how it works: photos.app.goo.gl/R7i6KkTzyvxXVsYT8 Thanks again for taking some time to help me with this!

Honestly, I don’t really know. I guess it would be based on the compass. It’s not really something I could see being useful for fixed wing, so I’ve never really investigated it.

Thank You Emile. Unfortunately not. Well, not just by using iNav. You could possibly do it by making your own firmware target and reassigning something to be an LED output. But I’ve not really looked deeply in to this.

@@MrD Thx for answering! It'll be a plane without led's 😅. I don't have the know-how to make my own firmware.

The other option is to use an external LED controller, like the MudDart MudLED module.

Yes, you can connect as many strips as you like in parallel. Just be wary of the power requirements, as it may be better to use a separate 5v BEC if the amp draw gets high.

No, it is just using the WS2812 standard.

@@MrD thanks bro, you saved me

To be honest, I don’t know. I don’t even know if arduplane can control LEDs. I would imagine if it can, the wiring would be the same, and there would be some settings in that giant parameters list. I am looking to try arduplane at some point. As I think it will be worth learning. But last time I gave up as the MissionPlanner UI is badly designed, and the guide on the ardu wiki was wrong. But I will try again.

Arduplane is real good now you should give it another try. I am glad I took my time to learn it and the new firmware is a breath of fresh air. I do not look at inav anymore. However this led thing is tempting. I have some leds lying around) But there is no information if those leds can be supported and controlled via Arduplane

I honestly can’t remember now. It was a while ago. Possibly eBay or Etsy?