This repository has been archived by the owner on Mar 4, 2019. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 1
Autonomous Update 1_11
arjunrao87 edited this page Jan 11, 2017
·
7 revisions
- Overview of what the design is gonna look like and how we will have subsystems ( mill, hood, drive, intake, shooter, peg, climber ), actuators( pneumatics, servos ) and sensors ( encoders, camera ) on those. These are open to change.
- There will be new feature branches for each of these subsystems and you need to take ownership as per table below
- Autonomous mode strategy
- We have some wiggle room until the other teams catchup, so lets perfect the drive subsystem.
- Status of v1.0.0
- Once the drive system current version is fixed per steps below, send pull request to merge into "Develop" [Mahim]
- Always look at Issues tab and Projects tab and move issues.
- Schedule :
- Now - 645 : Driver station + clean up v1.0.0
- 645-745 : PID
- Lets get the Driver station connected to the basic setup we have and see whats happening
- Fix the current iteration as per the following steps
- No need to have the joystick code in Robot.teleOpPeriodic(). Remove that!
- We will have 4 speed controllers, not 2
- Left side is non inverted, right is inverted
- No joystick in subsystem code
- Next steps for the drive subsystem
- Assign sensitivity to joystick
- PID
- Driving straight controller ( wheel optical encoders + NavX )
- RotateToAngle controller ( wheel optical encoders + NavX )
- Collision detection ( NavX )
- Push important driving data to the Smart Dashboard
- Add some logging to check drive system performance
- Monitor CPU usage ( once PID controllers are integrated )
- PID overview for Mahim, Arlenis
- P, I, D, F
- Difference between the theoretical PID and the programmatic PID
- Important classes and terminologies in WPI lib
- Using wheel encoders for the drive subsystem is the first task ( to determine 'distance' traversed )
- Using NavX is the next task ( to determine 'heading' )
- Not using "extends PIDSubsystem" and neither do I want to "implements PIDOutput" We will use our own PIDController objects
- Still deciding strategy of placement of PIDController thread.
- Using NavX ( Collision detection, AutoBalance and RotateToAngle ) [ http://www.kauailabs.com/public_files/navx-mxp/apidocs/java/com/kauailabs/navx/frc/AHRS.html ] ( Example code : https://github.com/frc4571/ExternalLibrarySampleCode )
- Drive( PID ) : Arlenis/Mahim
- Intake : Leslie
- Mill : Sharom
- Shooter ( Camera + PID ) : Mahim
- Peg ( PID ) : Arlenis
- Hood ( Math + PID ) : Mahim
- Climber : Sharom