I can’t seem to connect to the cRIO, I don’t get a task list like the manual says. I can ping the cRIO in the command promt and the DriverStation says there is communication to the robot. The setting for WindRiver looks identical to what the manual says it looks like but I dont get a task list, I use the FIRST -> Download and it appears to be doing something but when i reboot the cRIO the Driverstation reports “No Code”
cRIO is updated to v19… I just updated WindRiver to the latest update on WPI. I also updated the DS yesterday and the mandatory Labview updates.
I am going to do a reinstall on WindRiver tonight and see if that works.
we are a rookie team and any help would be appriciated, we need all the time we have.
After the target is set up (under options) There is a menu item or a right click menu that says “connect to target”? Did you try that option several times?
Brian
We had a similar problem in that we thought everything was up to date and had success in loading the new C++ to the cRio but still got the no code light on the dashboard.
After reading around and looking through the Getting Started till my eyes bled, I noticed that my Windriver examples list did not include the 2010 Vision Demo or any of the other new examples. It turned out that the update I was running for Windriver did unpack the code to a temporary directory but it was not then moving the files to their proper places in the Windriver folder. I was using the default directory but the batch file that moves the update was corrupted or something.
Long story short, I did what another thread mentioned and renamed my Windriver update to .zip and then extracted the files myself straight into the Windriver directory overwriting any files. Once I put the code on the robot from there it worked fine. So beware that even if you update, it still maybe failing somewhere prior to completion.
Also we found that you had to install the Labview update on the Driver Station before running the Driver station update or it would not work either. The process for getting things to work is still kind of flaky and I hope they get it worked out soon. Our team feels your pain in that it took us 3 days to get to sample code after we started tackling programming.
Another tidbit is that most of the C++ samples do NOT work as is straight from the examples. If you want the dashboard to reflect what your robot is doing, then you have to uncomment some code in the DashboardFormat.cpp file. The 2010 Vision Demo is doing bad stuff with its Watchdog calls, you need to move them around and make sure they’re called properly. Welcome to FIRST where torpedoing you is a way of life. I hope any of this may help you.