Ok so this is the first year we’re using Wind River, after using LabView last year. We have all updates and can connect to the robot. We used an example provided by the FRC, the Simple Robot one i think, and can download it to the robot. But when we reboot the robot with the diver station plugged in we get green lights on ‘Communication’, ‘Code’, and ‘Stop Button’ but cant control the robot with the joystick. If anyone can help we would appreciate it.
cRIO Image: v19
Driver Station: Up to Date
If you are receiving green lights across the board it probably means that it is your code or hardware. Are you loading for release or debug? Also are you clicking the enable tab?(I have to ask) What port does the joystick/gamepad show up on? Are you using Victors or Jaguars?
Silly question: did you click “Enable” on the Driver Station? What does the status message in the bottom left corner of the display say?
Are you downloading the correct executable in Window->Preferences->FIRST Downloader Preferences?
Make sure hardware is set up, for some reason the USB Hub must be plugged into the left side of the Classmate.
You can use the right one… just have to use the black connector.
For ‘Team Number:’ we have 587
For ‘File to download’ we have
<our workspace>/SimpleRobot/Debug/<whatevers here.>/SimpleRobot.out
I then build the project and click FIRST -> Download
We then restart the robot and again get green lights, and yes we do enable the robot…:rolleyes:
Any ideas? Maybe a step-by-step tutorial?
-James
Another post details the process:
http://usfirst.org/uploadedFiles/Community/FRC/Game_and_Season__Info/2010_Assets/2-2010FRCControl%20System-Getting%20Started-Rev-0.7.pdf
http://first.wpi.edu/Images/CMS/First/GettingStartedWithC.pdf
As it always happens we figured it out at the end of the day.:rolleyes:
It had nothing to do with Wind River or the computer. What happened was when we were getting the cRIO ready for the move to it’s new robot body we unplugged the HUGE cable that goes to the little blue PWM control board and plugged it back into the cRIO in the wrong port:o …but we got it working now… finally…
It’s always the engineers’ fault.
One thing to put on your checklist when you are having complete lack of functionality problems like that is the /load_out.txt file that is now generated on the cRIO when it boots. It basically tells you if you’ve forgotten a required module or plugged it into the wrong slot. It even will tell you if you accidentally bent one of the DB15 pins over (on the backplane) and the module LOOKS like it’s plugged in, but there is no connection (rather difficult to debug otherwise).
You can look here for detailed information: http://firstforge.wpi.edu/sf/wiki/do/viewPage/projects.wpilib/wiki/Loadout
This reminds me of a really bad joke a student told me once.
Q. How many programmers does it take to screw in a light bulb?
A. None. Clearly this is a hardware problem.
Thats’s great to know. I never knew that.