Announcement

Collapse

Technology Forum Has Moved!

The FIRST Tech Challenge Technology forum has moved to a new location! Please take a look at our forum blog for links and instructions on how to access the new forum.

https://firsttechchallenge.blogspot....orum-blog.html

Note that volunteers (except for FTA/WTA/CSA will still access their role specific forum through this site. The blog also outlines how to access the volunteer forums.
See more
See less

Joystick does not connect to PushBot

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

  • Joystick does not connect to PushBot

    Hello everyone,

    I downloaded the new ftc sdk for android studio, and followed the tutorial to the letter, but I'm still encountering some issues.

    I redownloaded the ftc_app_master app several times in the course of the last three weeks, and only last week was I able to successfully compile the code.

    We ordered new phones, which are connecting fine, and the code I'm using is the PushBot Teleop sample code (I commented out "@Disabled"), and the robot configuration is correct to PushBot.

    The robot is wired correctly; we've had several people check the robot wiring.

    The driver station will register the movements of the joystick and its values, but despite all that, the motors will not rotate.

    When tested individually against with a battery, the motors move fine.

    Does this problem sound familiar to anyone? Is there an easy solution to driving the robot?

  • #2
    No null pointer exceptions are thrown?

    Comment


    • #3
      Originally posted by Kyled View Post
      Hello everyone,

      I downloaded the new ftc sdk for android studio, and followed the tutorial to the letter, but I'm still encountering some issues.

      I redownloaded the ftc_app_master app several times in the course of the last three weeks, and only last week was I able to successfully compile the code.

      We ordered new phones, which are connecting fine, and the code I'm using is the PushBot Teleop sample code (I commented out "@Disabled"), and the robot configuration is correct to PushBot.

      The robot is wired correctly; we've had several people check the robot wiring.

      The driver station will register the movements of the joystick and its values, but despite all that, the motors will not rotate.

      When tested individually against with a battery, the motors move fine.

      Does this problem sound familiar to anyone? Is there an easy solution to driving the robot?
      Opmode is active?: Check, because you can select it and it shows telemetry data.
      Gamepad is active?: Check, because you can see the values changing.
      Device Names OK?: Check because you aren't seeing any red errors or warning.
      Motors OK?: Check because you have powered them up independently.

      That's some really good diagnostics and reporting.....

      What's left:
      1) Power levels not being calculated correctly?

      Both of the PushBot Teleop samples show the power values being sent to the left and right motors as telemetry.
      If you are seeing these change then they are being calculated correctly.

      2) Power commands not getting to motor controllers?

      Is there ONLY one motor controller?
      If there are two or more controllers then perhaps you are sending the motor power commands to the wrong Motor Controller.
      If this is the case you can go into the Configuration tool, select the current motor controller and use the "SWAP" button to swap the current motor assignments to the other controller.

      Any luck?

      Comment


      • #4
        Does your Driver phone show a little gamepad icon over "User 1" or "User 2" (upper right of the Driver app)?

        Comment


        • #5
          I have encountered no null pointer exceptions during compilation, and Opmode, Gamepad, and motors are active.

          The device name is the team name followed by either "-RC" or "-DC".

          The robot is fully charged, and there is one motor controller and one servo controller.

          Both gamepads show up if I hit "start" + "A"/"B".

          Comment


          • #6
            Try running your opmode while feeling the motor. Does it vibrate a little?

            I tested ours with only a PDM and one motor controller and two motors, all this in a configuration file called "2Motor". All this gear was unmounted from the robot, and the motors were unloaded. No gamepads.

            Then I told Android Studio to build my opmode with fixed 5% power to the motors; about half stall and half move slowly. I can feel the vibration on a stalled motor. Testing with 35% power moves them all briskly.

            Comment

            Working...
            X