We have robot comm, robot code, and joysticks, why doesnt the robot move?

[cgranata]

Hey Chief Delphi, our team is having an issue and I'm hoping someone out there can lend us a hand.

Our 2013 robot has Robot communication, robot code and joysticks connection. In the driver station each of these displays a green light. However, whenever we move the joysticks or press any buttons on the joysticks, nothing happens.

We have tried different joysticks/usb ports on multiple computers. We have the latest version of everything from Driver Station to Windriver Workbench.

The electronics and cRio are connected properly and have been checked, double checked, triple checked, etc. This leads me to believe it is a programming error.

Anyone have an idea? Any help would be greatly appreciated and my team and I thank you in advance for your support.

[ferret_guy]

Couple things to check:

1. Is the robot enabled? (in tele-op mode)
2. Are you correctly using the safety VIs?
3. Is your joystick showing up as connected?
4. Have you correctly initialized all your motors ect...

[ekapalka]

Can you post your code?

[cgranata]

Originally Posted by ferret_guy

Couple things to check:

1. Is the robot enabled? (in tele-op mode)
2. Are you correctly using the safety VIs?
3. Is your joystick showing up as connected?
4. Have you correctly initialized all your motors ect...

1. Yes
2. What do you mean by VIs?
3. Yes
4. Yes

[Alan Anderson]

Originally Posted by cgranata

2. What do you mean by VIs?

VI stands for Virtual Instrument. It's the LabVIEW equivalent of a function. The question was probably meant to ask whether you were enabling any motor safeties, or disabling the drive safety. You'd be getting diagnostic error messages on the driver station if it were a motor safety issue.

A better question might be: what motor speed controllers are you using, and what do the status LEDs on them do when you try to run the robot? Also, what pattern is the orange Robot Signal Light blinking?

[nightpool]

Originally Posted by ferret_guy

Couple things to check:

1. Are you correctly using the safety VIs?

*cough* This IS the Windriver C++ forum...

[tomy]

Check the Diagnostics Tab on your driver station and see what errors you are getting there.

[ferret_guy]

Originally Posted by nightpool

*cough* This IS the Windriver C++ forum...

ya ya i know didn't see that when i skimmed the new posts

[cgranata]

Thanks guys for all your help. My team looked at the error messages in the driver station and it led them to check the code. Apparently, our lead programmer put the "compressor command" in the operator control section of the code which constantly repeats over and over. When it was enabled, the robot didn't move because the code was being overflowed with this one command and "shut off"

Excuse me for my lack of technical explanation concerning the problem, I'm not in the programming department.

But thanks again guys! My team and I greatly appreciate your help.