Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Power management doesn't account for historical data #39

Open
edelmanjm opened this issue Feb 9, 2018 · 2 comments
Open

Power management doesn't account for historical data #39

edelmanjm opened this issue Feb 9, 2018 · 2 comments

Comments

@edelmanjm
Copy link
Member

As of now, power management only considers the current tick while calculating how much to scale the power by. Using a PID (with probably a fairly hefty feed forward) seems like the correct solution.

  • Value: pdp.getTotalCurrent()
  • Setpoint: currentTarget
  • Multiply output by each motor?
@RobinsonZ
Copy link
Member

For possible reference, the CTRE Software Reference Manual contains an example of tuning a current-based PID in section 12.3. It's a) in LabVIEW and b) obviously for a single motor but may provide some help.

@edelmanjm
Copy link
Member Author

@RobinsonZ 👌 For now I'm leaving this though, motion profiling is probably a bigger priority.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants