Closed Podcakero closed 5 years ago
The whole rationale behind the changes in MoveElevator is to utilise the built-in logic with PID to control the elevator's up and down movements. This will dynamically adjust speed to reach the target the most efficient way possible and minimise over/under shooting. It also decomplicates the code. requiring little logic and only tuning of PID values
So the MoveElevator Command as it is now just sets the targets, the PID code in ElevatorSubSystem.java handles the logic of moving the elevator? If that's the case could you set the target point whereever you're initializing MoveElevator now? Maybe break out the constructor into a RobotMap method? It seems a bit hacky to have a command that doesn't do anything when executed
thats how pid commands work. its the way wpi has in their example.
we need the command for its is finished and initialise methods to actually initiate and stop the pid
All that needs to be done is testing and fine-tuning of the PID values.