I am a new programmer and I was using the Getting Started Manual and so I wired the robot and by accident burned out the Analog Breakout board in Slot 1, I know quiite n00bish. anyway I am ordering a new one. I went through the cRIO image tool image tool to set it up for LabVIEW and it completed it right, I rebooted and still all seemed ok. I tried downloading the example Tank Drive hitting run when i open the VI. It loaded the program into the cRIO and it was succesfull. Though when I moved the joysticks nothing happened. Then i discoved the meaning of the Digital Sidecar’s LED light… it was blinking rapid 200ms on 200ms off which in the manual says System error: No driver’s station
communication, bad cRIO Image, bad team ID, extensive communication errors. I connected it to the driver station and the robot, and joysticks and everything were green except Robot Code. I had a Vet. of the team look at it and he ran a relay test and said it wasn’t getting the code correctly. I tried re-imaging again and rebooting it and still got the rapid LED Blinking. So now i am lost and have no idea. I have tried using 2 computers one being the classmate and the other being my HP Pavilion running Windows 7. HELP HELP HELP!
What version did you image the cRIO with? v19 is the latest, and the behavior you describe is consistent with an older version of the image being used with a newer version of the libraries. Sorry that the error info isn’t more explicit.
Greg McKaskle
according to the image tool it is using FRC_2009_v19.zip so yes it is using Verion 19.
Do you have any red status lights showing on the Diagnostics tab?
E-stop is plugged in, for instance?
Nope, Just Robot Code is red. and I have put code in it.
I tried using the Tank Drive example and could not get it to work either.
It’s croaking on the System Watchdog every few seconds.
We may have issues trying to Deploy/Run it from the same machine we are running the Driver Station on.
P.S. I was able to Run the default robot project without trouble, so it seems to be something with the Tank Drive program. However, you have to run the Driver Station program from the Developer account rather than from the Driver account to keep the robot Enabled.
Try picking a program you can “Run as startup” or set it up to do so.
The obvious example is to create a Robot project then Build & Run as startup.
I shall attempt this, thank you good sir 
I used “Run” on the default robot project and it worked fine on the same machine (Classmate) as the Driver station, so that does work okay.
It might be something out of date in the Tank Drive example.
There is a big difference between No Code and a System Watchdog once code is running. There is another thread covering the system watchdogs, and if you have feedback on how the joystick example seems to cause the watchdog, that will be useful since I can’t get anything done towards it until Monday.
The No Code message indicates that the communication task is not being updated by user code. Some reasons for that error include mixed up versions of WPI code and cRIO version image, formatting the controller for one language and using another, and finally code on the controller really isn’t running (at least not updating the communications task).
Greg McKaskle
Ok this seems to be the same everyone got the examples don’t work, though i do have a question while editing the Teleop.vi do i need to put a while loop in to run all the code in the tank drive.vi it hase a case structure with enable, int, and disabled. I put my code in enabled does the case structure act like a while loop?
Thank you for all your help:)
John Fogarty
No, don’t add a While loop. It’s already setup to do the looping it needs.
Everything inside the big case statement gets executed 50 times a second.
Just replace all the camera/gyro controlled Arcade Drive inside the outside case statement with the Tank Drive vi and add the extra joystick.
Ok thanks, i’ll try this tommorow.