Is anybody using Motor_LEDS?

I want to find out if anybody is actually using this code to control their LED lighting?  I am trying to work on a single, unified LED lighting program.  I am thinking about deleting or completely hijacking Motor_LEDs.

I just wanted to know if that will really mess anybody up?

You need to be a member of diydrones to add comments!

Join diydrones

Email me when people reply –

Replies

  • Is there documentation yet for the LED code built into the latest releases?  If so, can someone point me to it?

    I've searched high and low and can't find anything much that makes sense.

  • Where are the instructions for wiring up lights on a quad? I'm using the latest MP available firmware. I see I can just enable it in the MP but where are the instructions in the wiki for wiring up the lights to the APM1?

  • does anybody need gps status? i think the most important things are 1:armed/disarmed 2:battery 3:mode. i was thinking about something like this:

    armed: leds on

    disarmed: leds off

    mode 1: repeated pattern ----------_- (1 short off)

    mode 2: repeated pattern ----------_-_- (2 short offs)

    mode 3: repeated pattern ----------_-_-_- (3 short offs)

    mode 4: repeated pattern ----------_-_-_-_- (4 short offs)

    mode 5: repeated pattern ----------_-_-_-_-_- (5 short offs)

    battery first warning: repeated pattern ---___---___---___---___ (slow blink)

    battery second warning: repeated pattern -_-_-_-_ (fast blink)

    this way, theres only one output used for leds, they can be  driven by the relay on apm1 and also, they are mostly on so theres no need for other nav lights.

  • Ok guys, I'm going to start the work shortly.  I will try not to completely break this until it's working.

    Steven, the final result will probably look an awful lot like what you have already done.  That's along the lines of what I was already thinking.  But thanks for your example because it will help me.

    Really, the main point of this, is to make LEDS controllable from MP.  Default will be off, but then you just change a parameter to turn it on, and change different modes.

    I plan to use a couple of arrays and one parameter I will have add.  The code will be compiled by default, but won't be "active" until you set the parameter to something other than '0', and '0' will be the factory default.  Successive numbers will set various modes.  1 is just motor LEDS, all the pins will be used for motor leds (8 on the APM1, 3 on the APM2).  2 will be motors and GPS.  So 4 will be motors and 4 for GPS on APM1, and 2/1 for APM2.  Then '3' will be motors, GPS, and Aux.  4/2/2 for APM1, 1/1/1 for APM2.  Aux will be controlled by Ch7 sub-control that happens below the normal Ch7 switch PWM.  So currently Ch7 option "turns on" above 800.  But the Aux lighting will only turn on if the control_in is between 200-400.  This is easily done with some radio mixing.
  • Robert,

    With each release, I modify the code (UserCode,  UserVariable and one line of code in ArduCopter)  to control external LEDs via APM1’s relay to indicate the state of motor arming and battery voltage.  In my opinion, the Arducopter code should perform these basic functions out of the box.    Any other function (like blinky LEDs) is nice, but I would turn it off.

    Are you addressing these two indications (state of Motor Arming and Battery Voltage)? 

    Lloyd

     

  • No?  Ok, well I will be hijacking the existing code and changing the name to Copter_LEDS.  Will bring in some new functionality that people should like.

This reply was deleted.

Activity