Allow LED pin to be reassigned as MOTOR or SERVO

[mmosca]

This is a continuation of timer output mapping, adding led pins to the pool.

• Add led option to timer_output_mode
• Show led option in diff
• Correctly set outputs as led
• Update MSP messages to send full 32bit timer usageFlags
• Verify LED behavior when assigning random output as LED (LED pin has priority. Only 1 pin (first) gets to play led)
• Verify Servo assigned to LED works. Needs changing light_ws2811strip.c to pick: IO_TAG(WS8211_PIN) if not remmaped, or first available pin tagged as TIM_USE_LED
• Check all targets to make sure LED declaration in target.c comes after PWM outputs.
• Add special label info to MSP message (uint8_t/uint16_t?)
• Flag Led pin in MSP message (use IO_TAG to check which pin is led)

[rmaia3d]

This will be a GREAT feature! 👍

[mmosca]

Looks like led initialization happens beffore servo/motor outputs, causing later, when overriding the led output with led enabled.

[MrD-RC]

It would be great if the LED pad could be assigned to PINIO too.

[sensei-hacker]

It would be great if the LED pad could be assigned to PINIO too.

There's a another recent PR which allows the LED pin to be user-controlled PWM from 0% to 100%. Which includes 0 and 100, so functionally a PINIO*, but only controllable from Programming.

I wasn't able to confirm that other PR, which was merged, actually works - but maybe I don't know how to use my new oscilloscope.

• Where "PINIO" actually means "PIN_O" - I wish we had "I" (input).

[mmosca]

That might be possible, but will certainly be a bit complicated as it needs to handle user modes which may already be there. []s,Marcelo Bezerra ***@***.***>On 24 May 2024, at 18:32, Darren Lines ***@***.***> wrote: It would be great if the LED pad could be assigned to PINIO too. —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>