Robot doesn't drive when code is deployed.

[swaglord2000]

We actually found our issue! The modules on the cRIO were opposite what they needed to be so when we put them in the right order we were able to get a response.

[geomapguy]

Originally Posted by swaglord2000

We actually found our issue! The modules on the cRIO were opposite what they needed to be so when we put them in the right order we were able to get a response.

Great!!

[DaboRoss]

This is happening to us, except for it only happens when in game mode, and it stops responding around 10 seconds after autonomous ends. It doesn't happen when just enabling practice-teleop. It's pretty much the exact same error as posted above, which is why I responded to this thread.

Do you think that this error could be caused by the same stuff, even if it works when not in game mode.

[Greg McKaskle]

What is game mode?

Pretty much the same errors is probably a different error. Please post your error messages.

If your robot moves in teleop and auto, then it is not an issue with swapped modules -- unless something is swapping them on the robot while code is executing.

Greg McKaskle

[ekapalka]

Originally Posted by swaglord2000

We actually found our issue! The modules on the cRIO were opposite what they needed to be so when we put them in the right order we were able to get a response.

Did the imaging tool indicate that they were in the correct location before fixing it, though? My team's off-season robot is having unexplainable issues similar to the ones mentioned here in this thread, except the robot shows absolutely no indication of functionality other than printing button states (not axis states) from the controller to the DriverStation. The imaging tool says that all of the modules are green (in the correct location, I assume), and reformatting / re-imaging it doesn't help in the slightest. We've reduced our code down to the absolute minimum, but nothing has worked...

[xXhunter47Xx]

Originally Posted by ekapalka

Did the imaging tool indicate that they were in the correct location before fixing it, though? My team's off-season robot is having unexplainable issues similar to the ones mentioned here in this thread, except the robot shows absolutely no indication of functionality other than printing button states (not axis states) from the controller to the DriverStation. The imaging tool says that all of the modules are green (in the correct location, I assume), and reformatting / re-imaging it doesn't help in the slightest. We've reduced our code down to the absolute minimum, but nothing has worked...

Don't assume just because it's green that it's in the right location. Check connections physically please, software fails too (something I hate hearing when we're working on the robot, it's always easy to point the finger at the programmer ), make sure Analog is in port 1, ribbon cable module is in port 2, and solenoid module is in port 3. Can't wait for the roboRIO, when all these problems will vanish and new ones will arise.