Thread: Error -44061
View Single Post
  #3   Spotlight this post!  
Unread 01-11-2012, 07:36
Greg McKaskle Greg McKaskle is offline
Registered User
FRC #2468 (Team NI & Appreciate)
 
Join Date: Apr 2008
Rookie Year: 2008
Location: Austin, TX
Posts: 4,751
Greg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond repute
Re: Error -44061

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
Reply With Quote