-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Current control tuning #690
Comments
During pid tuning I noticed that motor demeanor isn't very linear during real usage under load. So you may get good results during open loop testing or bench testing with a constant load, but then get inconsistent results in real world. Until today the best way I found for ground vehicle was to connect the vehicle vi internet and doing tests on track with one person providing "current steps" and the other evaluating and tuning from remote. |
Would be nice to have a current control tuning tool. For me, the computed PI gains from the characterization cause overcurrent faults. There seems to be a fairly narrow middle ground where lower gains cause overcurrent faults due to poor disturbance rejection, and higher gains cause overcurrent faults due to overshoot.
A tuning tool would input steps to the current command, and then provide sampled Id and Iq data for a period after each step.
A simple way to do this would be to add Iq, Id, and a "trigger on setpoint change" to the "Sampled data" interface.
The text was updated successfully, but these errors were encountered: