You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/main/java/org/lasarobotics/drive/swerve/README.md
+52-12Lines changed: 52 additions & 12 deletions
Original file line number
Diff line number
Diff line change
@@ -1,4 +1,10 @@
1
-
# REV Swerve
1
+
# Swerve Drive template
2
+
3
+
Simply extend the [SwerveDrive](src/main/java/org/lasarobotics/drive/swerve/SwerveDrive.java) for your drive subsystem, and call the `super()` constructor with the appropriate arguments.
4
+
5
+
Use the [PurpleSwerve](https://github.com/lasarobotics/PurpleSwerve) repo as an example
6
+
7
+
## REV Swerve
2
8
3
9
In order to use Spark motor controllers, you MUST have a PWM absolute encoder directly connected to the Spark that controls the rotation motor.
At the current time, the CTRE CANCoder is the ONLY absolute encoder supported.
40
46
41
-
## MAXSwerve
47
+
Use of CANivore is HIGHLY recommended, as adjustment of status frame rates isn't easily possible while protecting the underlying sensor getter methods.
48
+
49
+
CANivore must be named "canivore" using Phoenix Tuner X.
50
+
51
+
To create an instance of a module, use the helper class for your module, and call the `create()` method for CTRE.
52
+
53
+
For example, here's how to create a Swerve X2i module:
SDS does not use a "calibration tool" or jig like MAXSwerve or WCP. As such, I have assumed that users will zero the modules to be straight ahead, aligned with the chassis. Therefore the "zero offset" for these modules is zero.
0 commit comments