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

4B: Throttle software simulation #32

Closed
3 tasks done
kkramer215 opened this issue Jan 7, 2023 · 0 comments · Fixed by #23
Closed
3 tasks done

4B: Throttle software simulation #32

kkramer215 opened this issue Jan 7, 2023 · 0 comments · Fixed by #23
Assignees

Comments

@kkramer215
Copy link
Contributor

kkramer215 commented Jan 7, 2023

This will be built on the foundation of the command line tool in VCU-4A. It’s purpose is to help characterize the throttle response by allowing us to create arbitrary waveforms in software without the need for a signal generator.

Refactor a little bit. Make it more object-oriented
Map real pedal value before: (apps, app2, bse) -> Mapped to a voltage
After: (footpedal angle) -> maps to throttle output

Checklist

  • Apps1
  • Apps2
  • BSE
@kkramer215 kkramer215 added this to In progress in VCU FW - Controls Jan 7, 2023
@rafguevara14 rafguevara14 linked a pull request Jan 20, 2023 that will close this issue
@kkramer215 kkramer215 moved this from In progress to Done in VCU FW - Controls Feb 22, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Development

Successfully merging a pull request may close this issue.

2 participants