Motors jerk; but stop responding after that.

[Greg McKaskle]

Are there any messages or errors on the diagnostics page of the DS?

Greg Mckaskle

[Wildcats1378]

Originally Posted by Greg McKaskle

Are there any messages or errors on the diagnostics page of the DS?

Greg Mckaskle

Yes, the RobotDrive loop is not running fast enough, or has too much code...

I don't know how to get rid of this error either... It never affected the operation of our robot before this started happening...

[Greg McKaskle]

Can you post an image of the code that most likely contains the error?

Greg Mckaskle

[Wildcats1378]

Originally Posted by Greg McKaskle

Can you post an image of the code that most likely contains the error?

Greg Mckaskle

I do not have access to the code right now. I am away from the computer which contains our code. I will get the code to you as soon as possible.

[Wildcats1378]

We had reset the code back to a previous version that worked, and it still was doing that. I am at a complete loss as to why this is happening. Here is a photo of the code we have that works:

[Keyreaper]

Originally Posted by Wildcats1378

We had reset the code back to a previous version that worked, and it still was doing that. I am at a complete loss as to why this is happening. Here is a photo of the code we have that works:

Attempt putting a while loop around the arcade drive function vi, and the get axis vis.