Chicklet-issues

[354.FIRST]

You can also try to see if your speed controller is having problems. We had a similar problem and when we swapped out the speed controller it all worked fine.
good luck
-354

[Trav-O]

we had the same problem. Turns out i accidentally was hitting the trigger while calibrating the axises... be carful and take things slooow... it works

[tseres]

also, check your power supply. when we used a battery, and it was low, the chicklet would spit out insane values.

[WaterFreak]

When attacking a problem LIKE this, always use an analytical approach, will save you gray hair and high blood pressure.

#1 Check the values being reported by the joystick, using the dashboard (as per the procedure mentioned here). You should be able to SEE the values being reported by the joystick. If they are off, go back and try the calibration process again and repeat Step #1 before proceeding.

#2 Check the values at multiple steps INSIDE your code. Where are they read in? Where are they manipulated? Where are they written out? Ensure that you are operating on the right INPUT values and setting the right OUTPUT values. Are the outputs getting overwritten AFTER you write them? Search ALL the code for potential issues and examine your code flow.

#3 Use the dashboard again, but now in the RC mode to ensure that the values are being received and set at the RC output.

#4 Make sure you have the PWM cables plugged into the right things at BOTH ends of the cable.

#5 Check your electrical connections at the Vic/Spike. Loose connections make for erratic behavior.

I have done a LOT of programming and validation with just a OI & RC hooked up with some power. Seems the programmers never get to touch the real robot until the last minute