Errors

[WizenedEE]

I'm pretty sure that that is this year's equivalent to the watchdog, so try speeding up the loop somehow.

If you still can't get it to work, try having the vi to run the motors in periodic tasks and have all the joystick processing in teleop and use global variables.

[Greg McKaskle]

Before changing the code, determine how long between subsequent calls to update the motors. You can do this with a millisecs and a feedback node, or you may be able locate a subVI called Loop Timing and place that near the motor updates.

According to the Safety manager, you are updating the motor setpoints pretty slowly. Determine why and resolve that issue.

If you are having trouble tracking down the slow code, you may also want to turn on the profiler and run your app.

Greg McKaskle

[randalcr]

Thank you both for replying quickly! . I have tried to look for the loop that the error seems to be referring to, but I can never find it. But, I will look again!

I'm still curious as to how many other people are getting this error, because it happens to us even if we use the default code.

[Mark McLeod]

By "RobotDrive" it is referring to anything that uses the motors opened with "Open 2 Motors" or "Open 4 Motors."

That just means anywhere you use the Arcade Drive, Tank Drive, or Holonomic Drive vis.

[randalcr]

Thanks Mark!