We've noticed something weird about the processes which run when we debug a simple program (just Talons and an ArcadeDrive with joystick).
Our main problem is that the code runs the first time very well, but then when we terminate the code (in the debug window) and debug again the same code - without rebooting the cRio - it doesn't work.
We thought it was a problem with the cRio - like an unproper deleting of memory from the cRio between uploading the two (same) codes.
We're are about to replace the cRio and try the code with an other (but an old version) cRio.
Anyway, we've found an other clue about this problem.
When we run the code for the first time, the processes on the debug window are as seen in this picture:
normal
In the times after that, when we ran the code without rebooting, there was the same error of
ERROR: A timeout has been exceeded: RobotDrive... Output not updated often enough. ...in Check() in C:/WindRiver/workspace/WPILib/MotorSafetyHelper.cpp at line 117
As you can see in the following picture, only one process run in the debug code.
error
Also, we located a breakpoint in the operator control function and we saw that the code doesn't even get to the while loop, somehow it stucks before it.
(In the first time it did get to the while loop in the operator control)
What are those processes and how does the lack of processes in the debug window related to the not updating the motors to often problem?
Maybe two codes run together because the last code wasn't deleted, or is there another reason?
We would thank you if you'd give us advices.
GreenBlitz 4590