View Single Post
  #2   Spotlight this post!  
Unread 13-02-2011, 07:02
Greg McKaskle Greg McKaskle is offline
Registered User
FRC #2468 (Team NI & Appreciate)
 
Join Date: Apr 2008
Rookie Year: 2008
Location: Austin, TX
Posts: 4,753
Greg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond repute
Re: Xbox 360 Controller Triggers

You don't show what is in the other case frame, so I can't be sure whether you stop the motor or leave it running.

You also don't really describe what the buttons are supposed to do to the motor.

What I'd suggest is to put some joystick code into your disabled routine. If using LV, just drop the Joystick get into disabled and you can open it to see the values at runtime. Otherwise add some printfs or use some debugging features of the IDE to observe the joystick values while disabled.

Once you can run the robot, leave it disabled, and see what the XBox controller is sending. If that looks correct, the issue is with the code or possibly the HW.

With a programming buddy, think through what commands are being sent to the motor with different inputs. For example. If the last command told the motor to spin, and releasing the button is supposed to make it stop, show them the code that sets the speed to zero. If you can't find the code, you have found a problem.

Greg McKaksle
Reply With Quote