View Single Post
  #4   Spotlight this post!  
Unread 19-01-2006, 22:27
billbo911's Avatar
billbo911 billbo911 is offline
I prefer you give a perfect effort.
AKA: That's "Mr. Bill"
FRC #2073 (EagleForce)
Team Role: Mentor
 
Join Date: Mar 2005
Rookie Year: 2005
Location: Elk Grove, Ca.
Posts: 2,381
billbo911 has a reputation beyond reputebillbo911 has a reputation beyond reputebillbo911 has a reputation beyond reputebillbo911 has a reputation beyond reputebillbo911 has a reputation beyond reputebillbo911 has a reputation beyond reputebillbo911 has a reputation beyond reputebillbo911 has a reputation beyond reputebillbo911 has a reputation beyond reputebillbo911 has a reputation beyond reputebillbo911 has a reputation beyond repute
Re: CMUCam Servos not Responding on Robot

Quote:
Originally Posted by krigby
Well, We've read the code inside and out. We've read every thread, dealt with power issues, calibrated it in LabView, and have finally gotten it to recognize the target on the robot using the RC. However, we can't get the servos to move. We have loaded the no frills camera.hex file. In the terminal window it shows the processor commanding the servos but they won't move. We have them connected to the default PMW sources PMW1 and PMW2. Any ideas.

Kevin - Team 1734

Kevin Rigby
I have an idea, but it will take some explaining. I posted this information already once today in this thread, but so far no reply. If you did follow Kevin's instructions exactly, then you copied the camera, tracking, terminal and serial port .c and .h files into a copy of the default code. You also will have edited the appropriate files with the corresponding # include statements. So far so good. But, did you notice that in Kevin's code, he had commented out the user_routines.c/Default_Routine call. This would prevent mapping of the PWM 1 & 2 to their corresponding joystick inputs. Well... if you did follow Kevin's instructions, then you copied all these files into a clean copy of the default code which does not comment out the call to Default_Routine and the PWM mapping takes place after the cameras code and overwrites the values with 127. Now please do not mistake this as a bash on Kevin, far from it! Kevin is AWESOME . What I am saying is that a complete familiarity with how all these pieces of code fit together is crucial.
The alternative is to just load the camera.hex file Kevin included with his code and it should work. Then, just tweak the values in the terminal window.
__________________
CalGames 2009 Autonomous Champion Award winner
Sacramento 2010 Creativity in Design winner, Sacramento 2010 Quarter finalist
2011 Sacramento Finalist, 2011 Madtown Engineering Inspiration Award.
2012 Sacramento Semi-Finals, 2012 Sacramento Innovation in Control Award, 2012 SVR Judges Award.
2012 CalGames Autonomous Challenge Award winner ($$$).
2014 2X Rockwell Automation: Innovation in Control Award (CVR and SAC). Curie Division Gracious Professionalism Award.
2014 Capital City Classic Winner AND Runner Up. Madtown Throwdown: Runner up.
2015 Innovation in Control Award, Sacramento.
2016 Chezy Champs Finalist, 2016 MTTD Finalist