Announcement

Collapse
No announcement yet.

Part Of Remote Randomly Doesn't Work During Tele-Op

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

  • Part Of Remote Randomly Doesn't Work During Tele-Op

    Sometimes when beginning Tele-Op or in the middle of Tele-Op our drivetrain will not respond. However, all of the other buttons on the same remote perform the functions they are supposed to. We have replaced both remote controls and the USB hub. What seems to work is if the drive team unplugs and then replugs in the controller. It then picks up the drive train and starts again. Has anyone had this issue or have any suggestions?

  • #2
    It sounds like your drivers may be accidentally pressing the "mode" button on the front of the controller.
    This causes the red LED to light up (if there is one).

    This has the effect of remapping the left joystick and DPAD controls. So the joystick won't work the way it usually does.
    In fact you can probably drive by using the DPAD controls.

    Unplugging and re-plugging would correct this problem as you describe.

    This one is probably fixed by educating the drivers.

    Comment


    • #3
      I had my drivers try to purposefully hit the mode button this last match and the left joystick stops driving the one side of the robot but the other joystick still allows the other side of the robot to be driven. When the issue occurs for us both sides of our drive train stop working.

      Comment


      • #4
        We had this occur at a tournament two matches in a row this weekend after pressing play on the drivers station after autonomous. The drive train would not work but all other buttons on both controllers worked. The mode button was not pressed and the only way to solve it was to unplug the remote and plug it back in. Our alliance partner experienced this same issue during one our matches as well and the same solution resolved it.

        Comment


        • #5
          I suggest trying to narrow down whether the robot is receiving the wrong commands from the gamepads or is interpreting the commands incorrectly. Run this op mode to see what the gamepads are reporting:

          Code:
          package org.firstinspires.ftc.teamcode;
          
          import com.qualcomm.robotcore.eventloop.opmode.OpMode;
          import com.qualcomm.robotcore.eventloop.opmode.TeleOp;
          import com.qualcomm.robotcore.util.ElapsedTime;
          
          @TeleOp(name = "Joystick Debug", group = "Concept")
          public class JoystickDebug extends OpMode {
          
            private ElapsedTime runtime = new ElapsedTime();
          
            @Override
            public void init() {
              telemetry.addData("Status", "Initialized");
            }
          
            @Override
            public void start() {
              runtime.reset();
            }
          
            @Override
            public void loop() {
              telemetry.addData("G1: ", gamepad1.toString());
              telemetry.addData("G2: ", gamepad2.toString());
              telemetry.addData("Status", "Run Time: " + runtime.toString());
            }
          }
          Or you can add these lines to your existing op mode:
          Code:
              telemetry.addData("G1: ", gamepad1.toString());
              telemetry.addData("G2: ", gamepad2.toString());
          John McDonnell
          Volunteer, former mentor

          Comment


          • #6
            We ran it today and when it would stop receiving drive train commands the Robot Controller would still receive the commands from the remote control but the drive train would not run. Unplugging and plugging the remote in would take care of it though.

            Comment

            Working...
            X