The "dreaded" Error -44061 Joystick:Joy Loop not running fast enough RobotDrive Loop

[Chris_Elston]

Trying to help troubleshoot the dreaded Error -44061 in Labview.

Of course there are alot of threads about this in this forum, and it could be alot of things. In our case, we mostly get this error when Autonomous RUNS. I think it’s related to our drive station laptop actually maybe. And this is the part I am wondering if someone can explain how this works. I don’t quite understand how we are getting a Joystick error Loop in Autonomous mode when there should be no joystick inputs.

Sometimes we reboot the drive station software and then we don’t have this problem for awhile, then it will start acting up again in Auto mode. We get this occasionally in teleop as well, but not as bad in auto mode.

Is there anything to look for when getting this error in Auto mode that causes jerky robot movement? Other than what some of the other threads are saying about wifi or tasks running on your driver station computer?

[Mark_McLeod]

For the case where you get the error just once when entering/leaving Auto…
The time the code transition takes can exceed the watchdog time when it doesn’t matter.
(Sorry, got off on to joysticks for some reason instead of drivetrain.)

The error -44061 is for RobotDrive not being updated fast enough
The thread title mentions Joysticks (a separate error that generally occurs once in Auto because of the timing of the code transition, e.g., joysticks reads over and over in Disable, then the last watchdog set in Disable expires in Auto because no more reads are taking place).

[Ryan_Blue]

@Chris_Elston

I don’t quite understand how we are getting a Joystick error Loop in Autonomous mode when there should be no joystick inputs.

Are you using the RobotDruve vis in auto? I’m pretty sure that error comes from that set of vis.

[Chris_Elston]

Here is how it’s coded so far, what do you mean?

[JeffB]

It looks like you enable the safety in begin (as you should).

In auto, you’ll need to either disable this and enable it at the end (I’m not a huge fan of this method) or run the loop more often. There’s not enough code visible to tell if you’re doing either of those options from the pictures.

If you do neither, the safety sees that the motors aren’t getting a new value within a brief period and are stopping the motors for safety reasons (it’s essentially a protection if your motors are full steam ahead and you lose connectivity to your robot. After that brief period, they get set to zero)

[Ryan_Blue]

How are you driving the drivetrain motors in autonomous? never mind, just saw it

It looks like you should disable the RobotDrive safety function during autonomous, since you’re using the rev provided set functions. The robotdrive functions will see that they aren’t being updated (since you aren’t calling them during auto) and print that message as well as attempting to disable the motors

[Chris_Elston]

In position control as a state machine.
Writing a Position value to the LEFT motor and RIGHT motor as shown.
The same as declared in Begin.

[Ryan_Blue]

Sorry, edited my post.

[Chris_Elston]

@JeffB

It looks like you enable the safety in begin (as you should).

In auto, you’ll need to either disable this and enable it at the end (I’m not a huge fan of this method) or run the loop more often. There’s not enough code visible to tell if you’re doing either of those options from the pictures.

If you do neither, the safety sees that the motors aren’t getting a new value within a brief period and are stopping the motors for safety reasons (it’s essentially a protection if your motors are full steam ahead and you lose connectivity to your robot. After that brief period, they get set to zero)

Did not know that was required to disable the RobotDrive safety. Will add that.

Where is the based place to turn Safety Back on? At the end of the Autonomous while still in Auto or inside Disable.VI it seems like?

[Chris_Elston]

@Ryan_Blue

How are you driving the drivetrain motors in autonomous? never mind, just saw it

It looks like you should disable the RobotDrive safety function during autonomous, since you’re using the rev provided set functions. The robotdrive functions will see that they aren’t being updated (since you aren’t calling them during auto) and print that message as well as attempting to disable the motors

Will give that a try and see. Never noticed this one before. Maybe it was turned off always before and the kids previous never said anything about it. lol.