-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Advanced Swerve Improvements #24
Comments
|
Fix singleton class issue. Only use SwerveSubsystem.getInstance() to get the subsytem |
This equation was added into the ChassisSpeed object to account for skew: Example for using the ChassisSpeed to account for skew: https://github.com/wpilibsuite/allwpilib/blob/6a2d3c30a6df21b841d3bce11c4e3d48f0282189/wpilibjExamples/src/main/java/edu/wpi/first/wpilibj/examples/swervebot/Drivetrain.java#L62 |
|
|
Run setCANTimeout(500) after factory defaults but before doing any settings. Then run setCANTimeout(0) after all settings are completed but before burn flash. Example here: https://github.com/Mechanical-Advantage/RobotCode2023/blob/9884d13b2220b76d430e82248fd837adbc4a10bc/src/main/java/org/littletonrobotics/frc2023/subsystems/gripper/GripperIOSparkMax.java#L45 |
Super stretch goal for way later, prob after comp. Setup the swerve code ecosystem to transfer EASILY to students in future years who aren't as proficient in code. My ideas right now are to just add all the different gear ratios of SDS modules into the config, add code to handle inverted SDS modules, and put comments explaining certain necessary changes per year, stuff like the Translation2d for each module, etc. |
There are some advanced swerve improvements that I have been researching for awhile now. The first list will be very important because they are related to prevent carpet damage:
Some less critical ideas and improvements:
The text was updated successfully, but these errors were encountered: