Loss of all motor control

This issue is occuring several times a day for me during alpa testing.

I have reported it and posted videos here https://github.com/wpilibsuite/SystemcoreTesting/discussions/246#discussioncomment-17344376

The symptoms are that the system core loses any ability to move motors on the Motion Core.

According to the driver station, everything is being enabled/disabled correctly but the A301s show a "disabled" state.

I usually notice this after deploying a code change, but this may just be that the robot has been sitting there a while during coding and the fault has occured, but not been noticed until the new code is deployed and I try to test it.

The only waty to recover is the power cycle the system. Re-deploying the code or soft restarting the code has no effect.

The video shows one interesting thing, the MotionCore diagnostics show no CAN activity or motor data BUT the system knows which motors are installed.

This may be related so I mention it here. A few times I have had just ONE drive motor get disabled and not respond. Again, it required a power cycle to fix it. This happens less often (maybe only 3 times)

Start with the linked discussion and video, then reproduce the loss of motor control during alpha testing. Compare Driver Station state with MotionCore diagnostics, including CAN activity, motor data, and the single-motor failure case. Done means the failure is characterized and a fix or reliable recovery path is verified without requiring a power cycle.