roboRIO Command Based Problems

[kylelanman]

What are the steps you are using to deploy your code to the RoboRio?

It is also possible that you are not initializing something properly in robotinit which runs before the robot is enabled.

It is entirely possible that the code is getting deleted as you have suggested but the Robot Code light is indicative of whether or not your program is running oppose to if your program actually exists on the RoboRio.

[King Nerd III]

Originally Posted by kylelanman

What are the steps you are using to deploy your code to the RoboRio?

It is also possible that you are not initializing something properly in robotinit which runs before the robot is enabled.

It is entirely possible that the code is getting deleted as you have suggested but the Robot Code light is indicative of whether or not your program is running oppose to if your program actually exists on the RoboRio.

We're going to reformat it again, that helped last time. Its annoying, though, as everytime we reformat it something else breaks.

[Ben Wolsieffer]

Are you sure your code is not crashing? When your code crashes, the robot code light will turn off and a stack trace should be printed to the log window in the DS. I doubt it is actually being deleted.

[King Nerd III]

Originally Posted by lopsided98

Are you sure your code is not crashing? When your code crashes, the robot code light will turn off and a stack trace should be printed to the log window in the DS. I doubt it is actually being deleted.

We fixed the problem by reformatting it 20 or so times. We also had a problem with a roboRIO where some kid turned it off WHILE IT WAS FORMATTING. Of course we fixed it, but it took a bunch of formatting.
Long story short the lesson here is when in doubt reformat until it works!

[Alan Anderson]

Originally Posted by King Nerd III

Long story short the lesson here is when in doubt reformat until it works!

I doubt that is good advice. Unless there is something physically wrong with the system, reimaging a roboRIO a bunch of times can't do anything that reimaging it once will do. The class of problems that can be solved with a single reimage step is very small, and they are very rare.

Instead of going for the reimaging/reformatting voodoo, you should troubleshoot your original problem using the tools suggested here by the people trying to help you.

[King Nerd III]

Originally Posted by Alan Anderson

I doubt that is good advice. Unless there is something physically wrong with the system, reimaging a roboRIO a bunch of times can't do anything that reimaging it once will do. The class of problems that can be solved with a single reimage step is very small, and they are very rare.

Instead of going for the reimaging/reformatting voodoo, you should troubleshoot your original problem using the tools suggested here by the people trying to help you.

It's usually all that works for us. The troubleshooting will help with minor things, but when the robot is turned off mid format? Nothing else would help. Heck, the troubleshooting tools wouldn't even detect the roboRIO.

[solopilot]

Could it be that you are taking too long in a command's execute() function?

[King Nerd III]

Originally Posted by solopilot

Could it be that you are taking too long in a command's execute() function?

We do occasionally and randomly get an error that says something about MotorSafetyHelper.h not updating fast enough on line 117, but there are two problems. One is that MotorSafetyHelper.h has no line 117, and we start running it. Any ideas?

[Ben Wolsieffer]

Originally Posted by King Nerd III

We do occasionally and randomly get an error that says something about MotorSafetyHelper.h not updating fast enough on line 117, but there are two problems. One is that MotorSafetyHelper.h has no line 117, and we start running it. Any ideas?

You are getting the MotorSafetyHelper error because you are not updating the motor outputs fast enough so the watchdog timer is expiring. If any execute method blocks for a long time, it will prevent all commands from running, therefore causing a watchdog timeout.

[King Nerd III]

Originally Posted by lopsided98

You are getting the MotorSafetyHelper error because you are not updating the motor outputs fast enough so the watchdog timer is expiring. If any execute method blocks for a long time, it will prevent all commands from running, therefore causing a watchdog timeout.

That's what we thought, but it doesn't happen every single time, which confused me. How would we fix that?

[Alan Anderson]

Originally Posted by King Nerd III

How would we fix that?

That depends on what is making it take too long. We can guess at possible causes, but unless you show us your code we can't give confident help.

Post your code, as Kyle suggested in his first response.

[King Nerd III]

Originally Posted by Alan Anderson

That depends on what is making it take too long. We can guess at possible causes, but unless you show us your code we can't give confident help.

Post your code, as Kyle suggested in his first response.

I added the DriveBase subsystem, and the drive command to the post. Tell me what you think.