Indicate Systemcore boot status using RSL, instead of it being off during boot.

[FletcherS7]

Currently during the first 20 seconds of boot the Systemcore RSL is completely off.
In contrast the roboRIO turns on the RSL within one to two seconds of it being powered on.

From a usability and troubleshooting perspective, it would be helpful to teams, CSA's, and Field Staff to either have a custom blink pattern during boot or at least have feature parity with the roboRIO and have the RSL be solid once the Systemcore is powered on.

[rzblue]

Thank you for posting this- I meant to post this several months ago and forgot. The RSL start delay is definitely a big usability regression for field staff; it makes it impossible to tell if the systemcore is powering on if the front panel isn't visible.

[stevep001]

With the Vivid robot radio, my standard workflow is to wait for RSLs visible for every robot (showing power on), and then signal the MC to begin the team introductions. The RSL check is done from outside the field, I'm not looking into the robot. We don't require the roboRIO lights to be visible outside of the robot and many teams mount it underneath the robot.

This would effectively add 20 seconds to cycle times. Accumulated over a 75 match event, that's about 3 matches worth of time. Half a round for a 36 team event.

[juchong]

+1 to the concerns @FletcherS7 and @stevep001 highlighted.

Today, FTAs rely on the RSL for more than simply monitoring the robot's enable state. Based on discussions in other forums, the original requirement appears to have been scoped too narrowly, omitting the robot's power-on state as an additional use case for this indicator. This gap in the requirements likely reflects a missed opportunity to incorporate real-world operational context during the definition phase. Earlier engagement with field support staff, who depend on these indicators when supporting teams during events, would have helped surface this need before it became a limitation in practice.