Joystick:Joy FRC: RobotDrive error message

Dear CD,

I am receiving the following ERROR message on the Driver Station screen with the base RobotProject code when switching from Teleop enabled to AUton Enabled.

ERROR -44061 "Joystick.Joy"FRC: The loop that contains RobotDrive is not running fast enough. This error can occur if the loop contains too much code, or if one or more others loops are starting the RobotDrive loop.

I found this initially when beginning to work with some student code but went back to original RobotDrive project and received the same results.

Can anyone else duplicate this and does anyone have a fix?

It may not be a big deal but I know this error message will nag me for a while until fixed.


That’s just due to the transition time between modes taking more than a tenth of a second.
It’s normal and nothing to worry about.


Thanks. One less thing to worry about. However, I am surprised that it shows up more than once, multiple times. Is there some kind of watchdog timeout function I can add or modify to eliminate the multiple events?

If you really want to get rid of the message you can turn the Safety off (Disable) in
You’ll see it Enabled at the tail end of the default Open Motors code.

You might also mitigate it by adding a Set Motor to zero in the

I’m getting the same error but instead of just when switching modes I’m getting it constantly while driving. We had 200 errors in about a minute of tele-op. It has nothing to do with the code as I replicated it with an unchanged Robo-Rio project. No other programs are running as far as I can tell. I am at my wits end. Any ideas?

Continuous -44061 errors mean you’re not controlling the motors rapidly enough. Make sure you aren’t opening an extraneous RobotDrive in Begin. If you do that but never set the motor values, the motor safety will complain about it.

I don’t believe that opening an extra RobotDrive is the issue but I will attach both our begin and tele-op just in case. Again, it is recreate-able with stock code. In addition, It occurs on 2 separate computers. I also tried the update to the radio configuration utility and re-formatted the radio, which accomplished nothing. (16.9 KB) (21.2 KB) (16.9 KB) (21.2 KB)

Well, the good news is that I ran your Begin/Teleop and I don’t get a single error about the drive motors running too slow.

So, since you get the error with a fresh project, there seems to be something in your environment/PC causing the slow down.

Take a look at your Driver Station log file for one of the runs to see what kind of round-trip transit times you were getting and if packets were being dropped.

Packets are being dropped. I did find one of the threads about that issue in the control system forums and tried ending some of the tasks that were suggested. That seems to have fixed most of the problem, with packets dropping occasionally instead of continuously. I’m going to keep trying to improve that.

Can you please post a link to the thread which discussed solutions to dropped pkts?

Dropped packets are usually caused by unwanted background programs on the Driver Station computer or by interference with the Wi-Fi signal. Is your OM5P (“robot radio”) mounted high and away from motors and metal and other electronic devices?

I found help here. We had Autodesk installed on both computers.