View Single Post
  #6   Spotlight this post!  
Unread 15-02-2013, 10:48
Phalanx's Avatar
Phalanx Phalanx is offline
Formerly Team 1089 (Mercury)
AKA: Michael Reffler
FRC #5431 (Titan Robotics)
Team Role: Mentor
 
Join Date: Jun 2005
Rookie Year: 1999
Location: Lewisville, TX (previously NJ)
Posts: 384
Phalanx has a reputation beyond reputePhalanx has a reputation beyond reputePhalanx has a reputation beyond reputePhalanx has a reputation beyond reputePhalanx has a reputation beyond reputePhalanx has a reputation beyond reputePhalanx has a reputation beyond reputePhalanx has a reputation beyond reputePhalanx has a reputation beyond reputePhalanx has a reputation beyond reputePhalanx has a reputation beyond repute
Re: VI - Get Encoder Rate in Engineering Units

We set the DistancePerCount property value to 1. That gave us the rate in Hz.

We only used it to measure the RPM of our shooter, so it works if you don't actually need the distance.

Quote:
Originally Posted by Alan Anderson View Post
Our "distance" is scaled to represent 60 times 1/250th of a revolution, so we get RPM directly from the rate output, and being an integer has never been an issue.
I actually like Alan's method better. Let the FPGA do the calculation.
For a 250 pulse encoder 1/250 * 60 = distanceperpusle.
GetRate will then yield RPM's direclly.
__________________
Don't just ask the experts, become one!
Leadership is not about ability. It's about responsibility!
Diagonally Parked in a Parallel Universe. It's okay we do Quantum Physics



Last edited by Phalanx : 15-02-2013 at 21:48.
Reply With Quote