Template:DCBLDCMotor Acceleration: Difference between revisions
From Phidgets Support
(Created page with "Acceleration directly controls how quickly your controller will adjust its Velocity. ====Examples==== {| class="wikitable" style="margin:auto;width:75%;text-align:center" |+ style="text-align: center;" | '''Acceleration = 1.0''' ! style="text-align: center;" | Initial Velocity<br>(duty cycle) ! style="text-align: center;" | Target Velocity<br>(duty cycle) ! style="text-align: center;" | Time to Reach Target Velocity |- | 0.0 || 1.0 || 1 second |- | 1.0 ||...") |
(No difference)
|
Latest revision as of 19:34, 18 November 2024
Acceleration directly controls how quickly your controller will adjust its Velocity.
Examples
| Initial Velocity (duty cycle) |
Target Velocity (duty cycle) |
Time to Reach Target Velocity |
|---|---|---|
| 0.0 | 1.0 | 1 second |
| 1.0 | -1.0 | 2 seconds |
| Initial Velocity (duty cycle) |
Target Velocity (duty cycle) |
Time to Reach Target Velocity |
|---|---|---|
| 0.0 | 1.0 | 10 seconds |
| 1.0 | -1.0 | 20 seconds |
| Initial Velocity (duty cycle) |
Target Velocity (duty cycle) |
Time to Reach Target Velocity |
|---|---|---|
| 0.0 | 1.0 | 0.01 seconds |
| 1.0 | -1.0 | 0.02 seconds |
Other Considerations
Increasing your Acceleration will result in faster response times from your motor as shown in the examples above. A high Acceleration will produce larger current swings in your motor when suddenly stopping or changing directions. These swings can be managed by setting an appropriate Current Limit, Surge Current Limit, and by using a Power Guard Phidget.
