Motor only responds to one way

We are programming with the Attack 3 controller and the motor only goes down.

What should the program be to have the motors go back up?

Key points:

We are using the Y axis
We can only get the motors to go down
Using NetBeans

Are you doing anything before calling the motor controller’s set() method? (deadband check, scaling, etc)

When you move the joystick in the up direction, does your motor controller show it is receiving a signal to move in that direction? If so, there may be a mechanical reason that the motor isn’t moving rather than software/electrical.

No deadband check or scaling.

The upward motion of the robot has worked before when on buttons, just not through the axis.

This is what the part of the program is currently.


Problems with this?

Code-wise that is fine.

Does the motor controller LED react to movement on the joystick?

Also, if you’re using Jaguars: I know they have a feature where you can have it handle checking for limit switch stops. I haven’t used Jags since 2011, but based on the guide ( you should have two vertical jumpers on the far right pins.

Both LED lights stay solid.

We have the jumpers on brake, if that’s what you are saying.

Make sure there are 2 jumpers set as such in this picture. If so, re-seat them:](

They can be turned 180° (automatic ramp mode), but they need to be there.

What do you mean by “both” LED lights? There is one LED and it can be one of three colors - Red, yellow or green. yellow is neutral (break in your case). When you say solid, do you mean you get a solid red in one direction and solid green in the other? I believe if it thinks it hit a limit switch, it will blink the direction color. If you only see one color, there is an issue with your commanded value. If you square the joystick value, remember to do joyY * abs(joyY) to preserve the sign.

Oops that was a mistake.

The jaguars color doesn’t actually change. It stays a solid scarlet color the entire time even when in moves in the one direction and doesn’t move in the other.

I do not square the joystick value, should I?

Some drivers find that this increases responsiveness, but it is definitely not required (nor will it fix your issue, I think it was mentioned because it will cause the symptoms you are experiencing). If you do, though, make sure you either square it as gpetilli mentioned, or cube it, to allow for negative values.

Is this an issue with the one joystick, or do you guys have extra joysticks to use instead?


We always use it like this:


I just cannot get the program to work on the Y axis. The program for the buttons work fine on the same controller. I thought the code was fine, but obviously not since it isn’t working.

Show us your program if you want us to look it over.

Would the Joystick be replaced as “operator” and AxisType replaced as “Y”?

In other words, is this how the code would look? What would need to be replaced?

Here is the some of the operator control period:

public void operatorControl()
double joyL, joyR, joyF;
joyL = joyR = 0;
double speed, Fspeed;
while ( isOperatorControl() && isEnabled() )
speed = 0.88;
else if(LeftDriver.getRawButton(5))
speed = 0.88;
speed = 0.88;

        joyL = 0.7*LeftDriver.getRawAxis(2) + 0.3*joyL;
        joyR = 0.7*LeftDriver.getRawAxis(4) + 0.3*joyR;
        //DriverStationLCD.getInstance().println(DriverStationLCD.Line.kUser1, 1, "Left: " + joyL*speed + "                       ");
        //DriverStationLCD.getInstance().println(DriverStationLCD.Line.kUser2, 1, "Right: " + joyR*speed + "                       "); 
          **Pulley.set(operator.getY()); **