Error -44061

[Mr.Trips]

When i try to run the robot this error comes up saying that the Left and Right motor can not run fast enough suffitiently or another loop is starving the code, but there is no other loop besides the tank drive and the compressor. Any ideas?

[Suitster]

Are you experiencing side effects when running your robot?

Our team struggled through this error, which accompanied a delay in response from the robot. When we would move the joysticks to drive it, the robot would have a delay, then move at full speed, which was dangerous, to say the least.

The way that we solved the problem was we remade the code, copying in global data, teleop, and autonomous. We could not find anything that was causing the errors (dashboard maybe?), but it fixed it.

[Greg McKaskle]

The error indicates that the safety config is turned on for the RobotDrive VIs. When on, it measures the time between calls and reports the error that it has been more than 100ms since the last update. It also sets the motors to 0 in case the reason is that your code is wrong or at a breakpoint. As soon as they are set again, the robot will resume.

If you have the time and curiosity, and I hope you do, I'd suggest debugging to determine why this is happening. If you don't, and you are happy with how the robot drives, you can turn off the safetyConfig in Begin. It is in the RobotDrive palette. Wire it up and set it to disable.

If you choose to debug, I'd suggest opening the support code folder in the project. In it there should be an elapsed times VI that you can drop in Teleop or other loops in order to observe the typical update rate. You can further instrument code by placing millisecond nodes and subtracts and even wire them to charts to see what can cause the delays.

Feel free to post results to the forum if you have questions about what you find.

Greg McKaskle

[Mr.Trips]

It worked! The robot is working as it should thank you for the help guys!

[whcirobotics]

Dear Greg,

Would you consider posting the VI code that does what you have suggested to do to find out what is wrong.

It would sure make for some very good learning,

[Greg McKaskle]

I don't have LV 2011 on my computer any longer, but I can show you images of what I was describing.

The first image shows where to get the support code VI.
The second shows that you simply drop it into TeleOp.vi.
If you then open it while running, you can see the time between any given calls. If you call it more than once from the same subVI or want to change the name to be more informative, just wire up your own string to Call Name.

The typical offenders are when teams put length delays or other lengthy code into teleop. Often the amount of the teleop and the pattern of when it misses will remind the programmer of something in their code. They will say -- "0.5 seconds, but that is how long we run our gripper motor", and they will dive into some code and find that they are doing it inline and causing the next teleop to be late, causing the safety config to send the error and shutdown the motors until the code is back in control.

Greg McKaskle