|
Re: Error-44061
This error can happen for a number of reasons. The first thing I'd do is to open the DS and on the right bar, click on the middle tab to show the chart traces. The red one is the CPU usage of the roboRIO. If this is low and you are getting this error, it is because the code has an explicit wait or series of blocks in the place where the robotDrive is normally updated.
If this line shows that the CPU usage is at 100% for periods of time, this is more likely caused by a lack of wait functions in other loops. They hog the CPU and the robotDrive updates are late.
Another way to gain insight into how your code is running is to use the Elapsed Times VI, located in the Support Files of the roboRIO project. If you place this in your teleOp function, and anywhere else you are interested in the rate of execution. If it is placed in the same place as RobotDrive, it will keep track of the timings of the calls. If you are running the VI, and you open the Elapsed Times subVI, you will see the delay between subsequent calls. You can further modify this VI is you want better statistics or a trace or other information.
Also pay better attention to when this error shows up. If it happens only when a specific button is pressed, and a specific piece of robot mechanism is running, this is commonly caused by putting code directly into TeleOp that takes more than 100ms to complete -- either because of complexity, or more likely because of wait statements. You may choose to ignore those if the robot behaves normally, or you can move that code out of TeleOp and use a communication mechanism for TeleOp to start/stop the mechanism code.
Finally, if you want, you can disable the safety mechanism, typically in Begin. But this may only mask the problem -- which is that the code is taking over 100ms to update the drive motors.
Greg McKaskle
|
...I've changed my position. I'm fully supportive of Joe's suggestion... - Chris Hibner [more] 
16-01-2016, 21:15
Linear Mode
