View Single Post
  #3   Spotlight this post!  
Unread 28-03-2010, 20:22
Ether's Avatar
Ether Ether is offline
systems engineer (retired)
no team
 
Join Date: Nov 2009
Rookie Year: 1969
Location: US
Posts: 8,065
Ether has a reputation beyond reputeEther has a reputation beyond reputeEther has a reputation beyond reputeEther has a reputation beyond reputeEther has a reputation beyond reputeEther has a reputation beyond reputeEther has a reputation beyond reputeEther has a reputation beyond reputeEther has a reputation beyond reputeEther has a reputation beyond reputeEther has a reputation beyond repute
Re: Closed Loop Speed Control

Quote:
Originally Posted by kgzak View Post
I want to make a closed loop speed control VI to get a very accurate speed for the motors to run. I know how to calculate the speed using encoders but is there a different way to tell the victor what speed to set the motor to? I feel that the Se Motor Speed VI is not very accurate.
The Set Motor Speed VI is a mis-nomer. It doesn't set motor speed, it sets motor voltage (via PWM). Under certain idealized conditions motor speed will be proportional to motor voltage, but this is rarely the case with the motorized applications in FIRST. That's why it is not accurate.

If you want closed-loop speed control, you can run the encoder signal to the cRIO and create your own PID control or use a library function. Or, use the Jaguars instead of the Victors. The Jags have built-in closed-loop speed control if you command them via CAN bus and feed the encoder signal directly to them. Which raises the question: has there been a clear ruling from GDC whether or not this is permissible?


~
Reply With Quote