You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The hall sensor velocity estimation could end up returning a nonzero
value if the timer "wrapped" between runs, even if the motor was
actually stationary. If using the velocity regulator the motor may then
fail to start.
To solve this:
- Switch to using unsigned types so that wrapping is defined.
- When timing out the pulse value, also reset it so that the velocity
won't be briefly treated as valid again when the timer wraps.
Seen on a platform with 32 bit long, so running the motor and then
waiting ~40 minutes is enough to observe this bug.
Note that the pulse_diff variable is reset if the hall sensor direction
changes, which may happen naturally when the motor stops, depending on
what it is attached to.
0 commit comments