2025:Programming: Difference between revisions
Programming (talk | contribs) (→1/7/25) |
Programming (talk | contribs) No edit summary |
||
| Line 17: | Line 17: | ||
*Discussed need for interviews and intervening with different mechanical groups to make sure they align with Strategies goals and are achievable | *Discussed need for interviews and intervening with different mechanical groups to make sure they align with Strategies goals and are achievable | ||
*Split into different groups for different mechanisms to interview/intervene what the design does and if it is reasonable | *Split into different groups for different mechanisms to interview/intervene what the design does and if it is reasonable | ||
*Eleanor- Elevator | *Eleanor- Elevator | ||
*Ben- Game Piece | *Ben- Game Piece | ||
| Line 29: | Line 28: | ||
*Submodule where things are distinct from the rest of the robot code- Reusable every year | *Submodule where things are distinct from the rest of the robot code- Reusable every year | ||
= 1/9/25 = | |||
Today we talked about swerve drive and the code to make it work. We didn't talk about trajectory nor any of the specific code required for pose estimation and field-centric driving. We took note that the swerve module class will need to be updated and modified to work with kracken x60s, as they use a TalonFx and should work with the CTRE libraries. Later in the night we began to implement the Drive class but did not get far, only starting the h file. When programming the drive class we discussed the functions from 2024:<code class="mwt-code" >manualControlRelRotation</code> and <code class="mwt-code" >manualControlAbsRotation.</code>We discovered that these functions did different things and had discussed what the Abs rotation accomplished. It was concluded that Abs rotation accomplishes matching the robots angle with the angle that the rotation joystick is making while the rel rotation will continue rotating in the direction that the joystick is pointing. In the 2025 we plan to combine these 2 functions into one and use the flags argument to mark this functionality. | |||
== Programming Archives == | == Programming Archives == | ||
Revision as of 09:09, 10 January 2025
1/7/25
- Discussed future programming activities
- Talked about vision and what to do with potential libraries to prevent unnecessary work year after year
- Planned out tomorrow activities with Limelight, Swerve building, and organizing groups for different parts of the program
1/8/25
- Updated a Limelight on the TestBoard
- Able to detect all 22 Apriltags using our 4 Limelights
- Found potential for object detection for Auto
- Reviewed vision
- Trajectory needs to be reviewed
- Reviewed Strategy Mind Map requirements (however couldn't find the Mind Map)
- Discussed automating elements of game play such as aligning to branches and possibly automated driving during Teleop
- Current top objective for vision is to align to the target and drive towards it; see here
- Discussed need for interviews and intervening with different mechanical groups to make sure they align with Strategies goals and are achievable
- Split into different groups for different mechanisms to interview/intervene what the design does and if it is reasonable
- Eleanor- Elevator
- Ben- Game Piece
- Mason- Drive
- Yaqoub- Hang
- Team- LED/Robot Control (dashboard)
- Team- Auto
- Discussed reusing coding and making things less about the year and more about the abstraction for future years
- Vision- Changes every year
- Game Piece- Changes each year
- Submodule where things are distinct from the rest of the robot code- Reusable every year
1/9/25
Today we talked about swerve drive and the code to make it work. We didn't talk about trajectory nor any of the specific code required for pose estimation and field-centric driving. We took note that the swerve module class will need to be updated and modified to work with kracken x60s, as they use a TalonFx and should work with the CTRE libraries. Later in the night we began to implement the Drive class but did not get far, only starting the h file. When programming the drive class we discussed the functions from 2024:manualControlRelRotation and manualControlAbsRotation.We discovered that these functions did different things and had discussed what the Abs rotation accomplished. It was concluded that Abs rotation accomplishes matching the robots angle with the angle that the rotation joystick is making while the rel rotation will continue rotating in the direction that the joystick is pointing. In the 2025 we plan to combine these 2 functions into one and use the flags argument to mark this functionality.
