Look into driving LEDs using RoboRio directly

[BrownGenius]

In the interest of simplifying the robot complexity/wiring, we need to understand if we really need a separate Arduino to control the addressable LEDs on our robot, or if we can use the RoboRio directly as demonstrated in this example: https://github.com/wpilibsuite/allwpilib/tree/main/wpilibjExamples/src/main/java/edu/wpi/first/wpilibj/examples/addressableled

[ParkerMeyers]

Same issue with running vision on the roborio, the roborio is not very strong and if we add more tasks for the CPU to run each cycle, it will slow down more essential code such as the driving or arm code

[ParkerMeyers]

The LEDs need to be updated each cycle in order to use effects instead of setting the lights staticly, and the ardruino connection is quite simple and does not add much wiring complexity, using only 2 extra wires as compared to running off of the roborio

[BrownGenius]

It's surprising that a dual-core ARM Cortex-A9 @ 667 Mhz can't handle a task that drives LEDs. Is our RoboRio older?

https://www.ni.com/docs/en-US/bundle/roborio-frc-specs/page/specs.html

[ParkerMeyers]

It probably can, I just dont think that its worth the extra usage with a task that updates every cycle. The ardruino is quite simple anyways. Also our RIO may be older, we can check