kF in new pid controller?

sargeanthost · February 13, 2020, 5:57pm

I would like to know how to add a kF in the pid command. It seems to be taken away for this year and I haven’t seen an alternative. Thanks

I thought of maybe adding + . 1 to the output in our drive train but I don’t think that would go well as I wouldn’t know how to copy the sign of the output

polyether · February 13, 2020, 6:05pm

(assuming you’re using Java or C++)

Because kF is just based on your setpoint, you should be able to just multiply your setpoint (goal velocity) by your kF (feedforward constant) and simply add it to the PID control signal. Assuming it ranges from [-1,1], you won’t need to copy the sign.

The new WPILib docs detail the usage of SimpleMotorFeedforward for this purpose, as well as how to combine it with PID.

sargeanthost · February 13, 2020, 6:06pm

We aren’t in percent but rather volts, we are also doing this based on a gyro value. The project is auto aim.

github.com

frc4123/2020/blob/master/src/main/java/frc/robot/commands/TurnToAngleCommand.java

/*----------------------------------------------------------------------------*/
/* Copyright (c) 2019 FIRST. All Rights Reserved.                             */
/* Open Source Software - may be modified and shared by FRC teams. The code   */
/* must be accompanied by the FIRST BSD license file in the root directory of */
/* the project.                                                               */
/*----------------------------------------------------------------------------*/

package frc.robot.commands;



import edu.wpi.first.wpilibj.controller.PIDController;
import edu.wpi.first.wpilibj.smartdashboard.SmartDashboard;
import edu.wpi.first.wpilibj2.command.PIDCommand;
import frc.robot.Constants;
import frc.robot.Constants.AutoAimConstants;
// import frc.robot.Constants.AutoAimConstants;
import frc.robot.subsystems.DriveSubsystem;

// NOTE:  Consider using this command inline, rather than writing a subclass.  For more

This file has been truncated. show original

polyether · February 13, 2020, 6:34pm

I believe you’ll want to end up passing output + feedforward to driveSubsystem.setOutput, where feedforward is calculated based on setpoint * kF (or, for a more rigorous approach, calculated from a frc-characterization model).

How exactly you structure this depends on your programming style. Hopefully someone more familiar with good code architecture can recommend specifics, as I’m not too familiar with command-based programming and OO style in general. The docs suggest handling the feedforward and feedback (PID) controllers separately:

Moreover, feedforward is a separate feature entirely from feedback, and thus has no reason to be handled in the same controller object, as this violates separation of concerns.

system · February 12, 2021, 6:34pm

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.