View Single Post
  #6   Spotlight this post!  
Unread 25-02-2015, 16:59
jman4747's Avatar
jman4747 jman4747 is offline
Just building robots
AKA: Josh
FRC #4080 (Team Reboot)
Team Role: CAD
 
Join Date: Apr 2013
Rookie Year: 2011
Location: Atlanta GA
Posts: 418
jman4747 has a reputation beyond reputejman4747 has a reputation beyond reputejman4747 has a reputation beyond reputejman4747 has a reputation beyond reputejman4747 has a reputation beyond reputejman4747 has a reputation beyond reputejman4747 has a reputation beyond reputejman4747 has a reputation beyond reputejman4747 has a reputation beyond reputejman4747 has a reputation beyond reputejman4747 has a reputation beyond repute
Re: Change in buttons and axes sub vi's

Quote:
Originally Posted by Ragingenferno View Post
We aren't using a controller from microsoft.
Don't matter. If your DS can see it than your computer can. All joysticks conform to a standard for USB devises called HID (Human Interface Devise). Mice, Keyboards, and joysticks fall under this and anything that can be recognized as an HID joystick devise you can follow Kevin Phan's advise to see the buttons/axis. We used this microprocessor before with custom buttons and even it can be seen as an HID joystick: https://www.pjrc.com/teensy/teensy31.html

The button/axis number you see corresponds to the element number for the array of buttons/axis you get out of the WPIlib joystick VI. Note when you go to program this the first element in an array and subsequently button #1 on the joystick will be the number zero. Things in programming count up starting at zero not one.
__________________
---------------------
Alumni, CAD Designer, machinist, and Mentor: FRC Team #4080

Mentor: Rookie FTC Team "EVE" #10458, FRC Team "Drewbotics" #5812

#banthebag
#RIBMEATS
#1620
Reply With Quote