Template:DCMotor Deadband: Difference between revisions
From Phidgets Support
No edit summary |
No edit summary |
||
Line 4: | Line 4: | ||
A small error can lead to the motor continually ''hunting'' for a target causing unwanted effects. A non-zero DeadBand can prevent this behavior. | A small error can lead to the motor continually ''hunting'' for a target causing unwanted effects. A non-zero DeadBand can prevent this behavior. | ||
The motor will | The motor will be disengaged when it enters the Deadband. If your application needs to hold position against an external force (e.g. gravity), a Deadband is likely to cause oscillations and should be avoided. | ||
| velocity = Phidget Velocity Controllers | | velocity = Phidget Velocity Controllers use trapezoidal motion profiling combined with a proportional-integral-derivative (PID) controller. The DeadBand only applies when the [[#Target Velocity|Target Velocity]] is set to 0. It allows your motor to move freely, up to a minimum Velocity, to prevent unwanted jitter around 0. It's also useful for applications where you want the motor to coast at zero velocity, since the motor will hold position at zero velocity without Deadband. | ||
| #default = Phidget Controllers | | #default = Phidget Position Controllers use trapezoidal motion profiling combined with a proportional-integral-derivative (PID) controller. | ||
}} | }} | ||
Revision as of 21:39, 29 November 2024
Phidget Position Controllers use trapezoidal motion profiling combined with a proportional-integral-derivative (PID) controller.
Documentation error