[FTC]: 35's Drive problem

[gdo]

There seems to always be a lag time in my experience.

just a question, are you using a "deadband" in your code like:

if (-10 < joystick.joy1_y1 < 10)
{
motor[motorD] = 0;
motor[motorE] = 0;
}

((I know its a robotC code, but it just to show an example))

I found that it reduced our lag, though did not make it go away. To really slim down the lag, the smaller the routines the robot has to go through, the faster you will get the code to run on the NXT. The NXT isn't extremely powerful, if you overload the processing power with many routines preforming at once, the cycle rate might be reduced.

Something else we found was that RobotC had the smallest lag time in the NXT, followed by LabView, and trailed by NXT-G. I'm not sure why this is, but it is one reason we stuck to the RobotC.

Just try the deadband, it might atleast help with makign sure your robot comes to a stop (because often if you don't have the deadband, the robot won't come to a stop completely).