I have had no such program but make sure you don’t have the motors set to move according to the ACCEL_X and ACCEL_Y values, those are the accelerometer. It took us roughly an hour and a half to figure it out and were about to switch back to robot c when we realized.
Now that is one of our “alternative drive modes” which can be activated through a series of button presses.
It seems to be working again, double checked that I am indeed on 2b08 as per James’ instructions. I’ve currently been running on 40 minutes now without an issue. It just occurred after 47:30 minutes, I’m not concerned about that - I’d bet ROBOTC would have the same issue with the same cortex/joystick. Thanks all!
Also, I’m not entirely confident that the issue Silly Robot has is a result of PROS firmware… I had this issue with ROBOTC early last year, and fixed it by physically removing the IMEs we had and it could be a VexNet, battery, or a multitude of other issues. Point is, I wouldn’t start investigating any PROS firmware as a result of Silly Robot’s problem yet, Jabibi.