Re: Robot Arm Victor Motor
 

An object only exists when in scope. For instance if you declare a variable in a method it is created and destroyed when the method is entered and exited.
I usually declare a motor in a class and call that classes constructor from my top level class (I use SimpleRobot usually) that way the motor exists from when the class is first instantiated and never goes away until exit.

The scenario I mentioned in the previous post only occurs when you do something like

public void motorStuff(){
motor = new Jaguar(1);
Jaguar.set(0.5);
}

The motor controller object will go away before it has time to do anything. Even if you call it repeatedly it won't last long enough to run for more than microseconds.

It doesn't seem to be the problem from the code you posted, but it doesn't hurt to ask.

Re: Robot Arm Victor Motor
 

To me, this remains the most conspicuous clue. A blinking orange speed controller is one that does not have a working connection to a properly configured PWM port on the digital sidecar. Be absolutely, positively sure your PWM connector is fully seated at both ends.

Re: Robot Arm Victor Motor
 

Our mechanical team is tinkering with it now. I'll let you guys know what happens in the end. Thanks for all the advice.

Re: Robot Arm Victor Motor
 

Try connecting the arm to a pwm port with an address less than 9 (ie. 1 to 8). I have not personally used so many motors in the past but the schematics show that channels 9 and 10 are wired slightly differently than 1 - 8. You should try using a higher pulse duty cycle. Finally check to make sure that the black wire in the WRB cable is in the correct position. Victors allow the wire header to be inserted backwards.