As noted in the WPILib documentation, Motor Safety is an important feature for FRC.
Examples of mechanisms that should have motor safety enabled are systems like drive trains and arms. If these systems get latched on a particular value they could cause damage to their environment or themselves.
Motor safety is not enabled within the SDS library. Additionally, because DrivetrainSubsystem sets the module states regardless of whether or not drive() was called in the last iteration, the drive train will latch to the last set value.
For example, if a team takes the template and adds an autonomous command to drive forward 3-feet, but forgets to set the chassis speed to zero when the command ends, the robot will latch to the set speed and never stop until the robot is disabled. In this case, motor safety is an important feature to prevent this behavior.
As noted in the WPILib documentation, Motor Safety is an important feature for FRC.
Motor safety is not enabled within the SDS library. Additionally, because
DrivetrainSubsystemsets the module states regardless of whether or notdrive()was called in the last iteration, the drive train will latch to the last set value.For example, if a team takes the template and adds an autonomous command to drive forward 3-feet, but forgets to set the chassis speed to zero when the command ends, the robot will latch to the set speed and never stop until the robot is disabled. In this case, motor safety is an important feature to prevent this behavior.