swerve improvement checklist#2
Conversation
…ed most states, and combined the state and superstructure files
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| private static final int ROLLER_MOTOR_ID = 20; | ||
| private static final int ARM_MOTOR_ID = 19; | ||
| private static final int INDEXER_MOTOR_ID = 17; | ||
| private static final double ROLLER_GEAR_RATIO = 3.0; | ||
| private static final double ARM_GEAR_RATIO = 1; // 248/9 | ||
| private static final double INDEXER_GEAR_RATIO = 3.0; |
There was a problem hiding this comment.
The real intake IO uses ARM_GEAR_RATIO = 1 even though the comment notes a 248/9 reduction, so MotionMagic targets and telemetry are scaled as if the arm were directly coupled. Commands such as deployArm()/stowArm() therefore request ~28× less motor rotation than the mechanism requires, meaning the arm will never reach the intended angles and atGoal() will remain false on the real robot.
Useful? React with 👍 / 👎.
2 participants
No description provided.