Quote:
Originally Posted by Chris_Elston
In my student's code, when a limit switch was hit, he has a true/false condition that "disable the motor" then it would "enable the motor".
What Omar is saying is inside this VI, it writes a SET Position of "0" each time this VI is called. Here is the screen shot Omar sent us to check. We will check this tonight.
Omar recommends NOT USING Motor Enable/Disable in this method because the VI write the SET POSITION in the back ground, I assume for safety reasons...it writes a set position of ZERO so the PID won't take off when the motor is enabled. You don't want a "run-a-away" motor condition on power up.
|
So we don't even have that vi in our code. We are just using the motor set. To make sure we have the same problem, the encoder counts up correctly but when we try to return to zero it doesn't return to the same point. This is the problem you guys are having right?