[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?