Error: a timeout has been exceeded

[Cody Trey]

it repeats over and over in the diagnostics messages box. it funtions in autonomous but not in teleop

[RufflesRidge]

Originally Posted by Cody Trey

it repeats over and over in the diagnostics messages box. it funtions in autonomous but not in teleop

Saw your code after I posted. You shouldn't have a semicolon after your while statement in teleop, your code is looping doing nothing.

[makahn64]

The above code looks fine to me...the brackets all balance and I do not see an out of place semicolon.

I am having the exact same problem, but only with the old CRIO. The new CRIO works fine. No idea what is causing it yet. Even happens with just the raw, unmodified, SimpleRobot template.

[RufflesRidge]

Originally Posted by makahn64

The above code looks fine to me...the brackets all balance and I do not see an out of place semicolon.

This line is definitely not fine

while (IsOperatorControl());

[makahn64]

You're right, didn't see the semi before the bracket.

Nonetheless, the problem seems to come from not turning off the robot safety. Worked for me.

[petet4]

Cody, your issue might be that the expiration time has not been set.

Use the motorsafty member GetExpiration() to see what the time is set too and the member SetExpiration(float timeout) to set a time.

See if this helps.

-pete

[enrique]

Originally Posted by petet4

Cody, your issue might be that the expiration time has not been set.

Use the motorsafty member GetExpiration() to see what the time is set too and the member SetExpiration(float timeout) to set a time.

See if this helps.

-pete

Yes, the error suggests the code was run even with the semicolon problem, but it expired during that command. Starting to wonder if the command based stuff is that much better.

[Bongle]

My team had this problem last night - we declared a robotdrive, but only used it some of the time. If the trigger was down, we drove the drive motor Jaguar instances directly by calling Jaguar::Set. We assume that the RobotDrive instance didn't like that IT wasn't getting called for a period of time, even though we were in fact updating the motors.

We fixed it by adjusting our direct-set code to run through RobotDrive instead.

It looks like this isn't the same as your problem since (aside from the semicolon after the while loop) your code always calling the RobotDrive functions.

Suggestion: Maybe try RobotDrive::TankDrive or RobotDrive::ArcadeDrive just to rule out it being a problem with the RobotDrive::MecanumDrive_Cartesian function?