View Single Post
  #3   Spotlight this post!  
Unread 16-10-2009, 00:44
EricVanWyk EricVanWyk is offline
Registered User
no team
 
Join Date: Jan 2007
Rookie Year: 2000
Location: Boston
Posts: 1,597
EricVanWyk has a reputation beyond reputeEricVanWyk has a reputation beyond reputeEricVanWyk has a reputation beyond reputeEricVanWyk has a reputation beyond reputeEricVanWyk has a reputation beyond reputeEricVanWyk has a reputation beyond reputeEricVanWyk has a reputation beyond reputeEricVanWyk has a reputation beyond reputeEricVanWyk has a reputation beyond reputeEricVanWyk has a reputation beyond reputeEricVanWyk has a reputation beyond repute
Send a message via AIM to EricVanWyk
Re: Team 2102 Problem With Control Interface

Quote:
Originally Posted by kevinbrice View Post
A programing mentor thinks it might be a timer on the first side of the crio programing which ran out, any similar problems? Any suggestions?
I'll start by stating that there is no such timer. If it worked before, it works now. He may be thinking of the license expiration - the LabVIEW environment expires after a little more than a year. However, this would just prevent you from loading the programming environment, it would not modify deployed code and it would not create bad code.


Quote:
Originally Posted by kevinbrice View Post
No driving control whatsoever through joysticks or gamepad, when autonomous switch is toggled, the robot does start auto mode. When set to teleop, it drives forward full speed, no other motors move except steering centering. Disable switch stops robot. Drivers station is fully updated. We checked wiring all seems correct. Cannot figure out problem! Please help!
Those symptoms tell me that the robot is doing exactly what you are telling it to do : the error is in your code, not in the system. Set some probes to figure out exactly what you are sending to the motor commands.
Reply With Quote