View Single Post
  #14   Spotlight this post!  
Unread 01-06-2011, 11:00
Chris Hibner's Avatar Unsung FIRST Hero
Chris Hibner Chris Hibner is offline
Eschewing Obfuscation Since 1990
AKA: Lars Kamen's Roadie
FRC #0051 (Wings of Fire)
Team Role: Engineer
 
Join Date: May 2001
Rookie Year: 1997
Location: Canton, MI
Posts: 1,488
Chris Hibner has a reputation beyond reputeChris Hibner has a reputation beyond reputeChris Hibner has a reputation beyond reputeChris Hibner has a reputation beyond reputeChris Hibner has a reputation beyond reputeChris Hibner has a reputation beyond reputeChris Hibner has a reputation beyond reputeChris Hibner has a reputation beyond reputeChris Hibner has a reputation beyond reputeChris Hibner has a reputation beyond reputeChris Hibner has a reputation beyond repute
Re: Hibner: Software Testing Via Simulation

Quote:
Originally Posted by ajlapp View Post
We typically use potentiometers for feedback. Any modeling recommendations for a potentiometer? It seems fairly straightforward to me.
I don't do anything to model potentiometers - I just use the angle calculated by the simple model as my sensor feedback. I do usually use a noise model (if you have your cRIO handy, use the noise testing method in my last post. If not, 2 degrees of noise is a good starting point).

Quote:
Can you test for equivalent motor command? I.e. I could put the actual robot arm into a know position, say parallel with the ground.....then apply a known PWM to it's motor until it is held in place and not falling. Would this value then be equal to the equivalent motor command to simulate gravity??
If your arm is already built, that is exactly how we do it. You only need to do the test in one position, and the rest is proportional to the sine of the angle from vertical. If you do the test with the arm horizontal, then the equivalent motor command is EquivAtHoriz * sin(angleFromVertical). If you look at the arm model example, this is exactly what was done.

If you don't have the arm already build, you can do some rough calculations to get a good starting point. If you don't feel like rough calculations, using 0.2 seems to work pretty well for getting your software debugged.
__________________
-
An ounce of perception is worth a pound of obscure.