Weird Crio/Programming problem

[mattiej]

Hi! My team has been having a weird problem with our robot. We wanted to build a test chassis to test our drive train, but we have been running into issues. We fixed all of the electrical issues, but now I am having a new problem.

The issue is this: sometimes when driving, the current action of the robot will "stick". If we are driving forward at full speed, the robot will do that forever. Sometimes, jerking the joystick will fix this. Other times, the robot will drive correctly but immediately come to a stop, even if you are driving it forward.

So far, I have tried all that I can think of(and find). We first tried reformatting our crio and reimaging it. This didn't change the problem. I then tried using a default robot mecanum code (with some edits to references that didn't exist). This also did not change it. I then switched to a crossover, then an ethernet cable. Neither of those changed it.

As far as errors go, we get quite a few. We get a few different watchdog expiration codes (excluding the System 1 User 0 state switch code), a radio error code (we were tethered so I didn't think that this made a difference, a 44004 (note positive, not negative) Frc: No robot code (which seems like the problem to me, since we were running robot code), and a -44004 code because we don't have our camera plugged in.

Also, I notice that whenever we connected to the robot, the driver station graph for crio CPU would "dissapear" (I assume this meant 100%).

What are we doing wrong?