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

Add option to disable HFI when stopped in duty cycle and speed modes #183

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

lgeek
Copy link

@lgeek lgeek commented Jun 13, 2020

This introduces the HFI "Min ERPM with no input" option. It dynamically
disables HFI in the duty cycle or speed modes when 0 duty cycle /
speed is commanded and the ERPM of the motor is lower than the set
value.

A value of 0 will behave the same as before, while a value of typically
a few hundred ERPM will cause HFI to turn off when the motor is stopped.

The idea is to keep HFI enabled as long as the motor is moving even if
the input is 0, to allow it to respond immediately to a different input,
for example to accelerate an inertial load which was braking down but
still in motion.

On the other hand, just enabling and disabling HFI at 0 speed can
induce some movement, so the threshold can't be 0 ERPM - turning off
HFI would make the motor move slightly, which would turn on HFI, which
would move the motor again and so on. The minimum ERPM threshold which
works as intended depends on the HFI configuration and the motor.
Value around 600 seem to be a good starting point for outrunners.

Matching vesc_tool pull request here: vedderb/vesc_tool#86

Video of this in action: https://www.youtube.com/watch?v=9_7IR2sysUI

This introduces the HFI "Min ERPM with no input" option. It dynamically
disables HFI in the duty cycle or speed modes when 0 duty cycle /
speed is commanded and the ERPM of the motor is lower than the set
value.

A value of 0 will behave the same as before, while a value of typically
a few hundred ERPM will cause HFI to turn off when the motor is stopped.

The idea is to keep HFI enabled as long as the motor is moving even if
the input is 0, to allow it to respond immediately to a different input,
for example to accelerate an inertial load which was braking down but
still in motion.

On the other hand, just enabling and disabling HFI at 0 speed can
induce some movement, so the threshold can't be 0 ERPM - turning off
HFI would make the motor move slightly, which would turn on HFI, which
would move the motor again and so on. The minimum ERPM threshold which
works as intended depends on the HFI configuration and the motor.
Value around 600 seem to be a good starting point for outrunners.
@Teslafly
Copy link
Contributor

Teslafly commented Nov 6, 2022

probably want to remove the fw version change, but i see no inherent problem with this?

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

Successfully merging this pull request may close these issues.

2 participants