Announcement

Collapse
No announcement yet.

Difficulty in recognizing the Game Pad Right stick( Y) for the Robot Controller Prog

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Difficulty in recognizing the Game Pad Right stick( Y) for the Robot Controller Prog

    We are using MIT App Inventor for Robot Controller Program. which uses the Game Pad.
    We followed the exact same steps given in the FTC sample programs.
    But the Program is not recognizing the right stick Y.
    can anyone provide any input for this issue?

    Thanks

  • #2
    Welcome to the forums!

    Just a few quick checks:
    Are you using Logitech F130 as your gamepad?
    Is the driver station set to logitech? If not, change you change it to that and test it?
    Is the back of the game pad set to X? If not, can you change it to that and test it?
    Is your Driver Station using Marshmallow with a usb hub? If so, have you tried the steps outlined at http://ftcforum.usfirst.org/showthre...-3rd-Gen-users.

    Comment


    • #3
      We had the same issue after upgrading to Marshmallow. The latest SDK at the time included an older appliance (v1.77). It was said in one of the posts that the game controller mapping changed with Marshmallow and a new SDK was required to correct it. We downloaded and imported the new appliance (v2.2), loaded the latest driver station app on the driver station, and all is working now. There's a sticky with a link to the new SDK.

      Comment


      • #4
        Originally posted by joe_mallory View Post
        We had the same issue after upgrading to Marshmallow. The latest SDK at the time included an older appliance (v1.77). It was said in one of the posts that the game controller mapping changed with Marshmallow and a new SDK was required to correct it. We downloaded and imported the new appliance (v2.2), loaded the latest driver station app on the driver station, and all is working now. There's a sticky with a link to the new SDK.
        I can confirm that one of my teams had this issue and the latest version of the software for App Inventor fixed this issue as well.

        Comment

        Working...
        X