Quote:
Originally Posted by notmattlythgoe
Would this be better or more efficient than having your motor1, and a motor2 that just uses a positional PID controller and the setpoint is always the position of motor1?
|
...and the process variable for Motor2 is encoder2 position, like
this?
The problem I see with that is the transient response to large step changes in driver position command. Motor1 responds immediately to the large change, but Motor2's controller must wait for the error to form between encoder1 & encoder2. Granted, you could crank the P gain way up for Motor2, but it's not immediately clear how well that would work in practice.