Thread: Motor Testing
View Single Post
  #21   Spotlight this post!  
Unread 15-10-2008, 13:47
Kevin Sevcik's Avatar
Kevin Sevcik Kevin Sevcik is online now
(Insert witty comment here)
FRC #0057 (The Leopards)
Team Role: Mentor
 
Join Date: Jun 2001
Rookie Year: 1998
Location: Houston, Texas
Posts: 3,761
Kevin Sevcik has a reputation beyond reputeKevin Sevcik has a reputation beyond reputeKevin Sevcik has a reputation beyond reputeKevin Sevcik has a reputation beyond reputeKevin Sevcik has a reputation beyond reputeKevin Sevcik has a reputation beyond reputeKevin Sevcik has a reputation beyond reputeKevin Sevcik has a reputation beyond reputeKevin Sevcik has a reputation beyond reputeKevin Sevcik has a reputation beyond reputeKevin Sevcik has a reputation beyond repute
Send a message via AIM to Kevin Sevcik Send a message via Yahoo to Kevin Sevcik
Re: Motor Testing

Quote:
Originally Posted by IKE View Post
I know hitting the overpass at 10 fps added a lot of stiction (it really should be a word) to our elevator.
Rejoice! Stiction might not be in Webster's, but it's a fairly common term in MechE papers.

Anyways, the Labview System ID Toolkit would definitely do most of the heavy lifting for you, but you should be careful in applying it. Waving about mathematical tools you don't have a good understanding of can leave you looking much like the Sorcerer's Apprentice.

Also, as to ignoring friction effects and swamping the rotor inertia with a larger load inertia..... Again, if you don't care about a 5-10% error, why don't you trust the datasheets? If this is a learning project as IKE proposes, then simply hooking up motors to loads and monitoring them would be fine for exploring the dynamics of how motors work, without worrying about the headaches or expense of trying to exactly model the motors.
__________________
The difficult we do today; the impossible we do tomorrow. Miracles by appointment only.

Lone Star Regional Troubleshooter