We had a similar issue last year getting a No Code error. This happened because we did not pack the data correctly to send to the dashboard. I think there was a specific sequence used and the dashboard won’t accept the data packets if it’s not correct…
If this issue persists, one might want to try taking out the data packing code altogether and try to get it to run.
Hi Joe, I was starting to suspect that…I had another mentor reimage the Crio and he asssured me it was complete but I am starting to have my doubts…Is there an easy way to check the version that is running in the Crio?
I am also not sure that he installed the labview update. Since we are running wind river he may have thought we didn’t need it…What would be the effect of not updating that?
thanks again…
Brian
If you didn’t update LabVIEW, you didn’t get the v19 image that comes with the updated imaging tool.
The cRIO image version is displayed on the Driver Station at the bottom of the Diagnostics tab.
So it’s easy to double check.
Like Mark said… Driver Station Diagnostics tab.
You can tell if the update worked by looking at the version of the image that the imaging tool is trying to send to the cRIO when you enable formatting the controller.
I ended up figuring out the issue on mine, hopefully this helps others:
My target install machine is running Windows 7. According to a Windows guy I know, Microsoft changed the security API for a few different things going from Vista to 7, especially concerning a feature called UAC. UAC does not allow programs to write directly to the C: drive, so certain programs will not function properly.
One of these programs that fails (silently) is the WindRiver installer.
The solution? Log into an adminstrator account, go to Control Panel -> User Accounts and Family Safety -> User Account. Choose “User Account Control” settings (the infamous UAC). Slide the bar to the bottom, and restart your computer. You have now disabled UAC; you can enable it later (probably after build season).
Now for the fun part. Remove WindRiver entirely (i.e. blow away the C:\WindRiver directory). Pop in the WindRiver install DVD and run the setup program. It should install significantly faster. After that, run the update program on the same disk, then install the latest WPI updates. Once you’ve done that, everything should work properly.
Hope that helps!
Yippeee!! everything is finally working…We re-imaged the Crio, made sure ‘ALL’ the updates were applied to the driver station and the development laptop, compiled then downloaded the BuiltinDefaultCode.out file. Then we added Joe’s accelerometer code and fixed the I2C.cpp file. and all still worked.
We had some problems with the IterativeDemo but I we’ll revisit that later. The BuiltinDefaultcode is what we will base our robot code on.
Thanks to all especially Joe Hersch for all the info and his patience…They don’t pay you enough…Every one should send Joe a Starbucks gift card so he can buy enough coffee to keep him awake when he sending those responses at 3 AM…:ahh:
Brian C
We are having i believe, the same issue. We installed Wind River Workbench 3.0 and LabView on 3 separate computers and our atom we received this year in our kickoff kit. All of the computers are updated with the following…
WorkbenchUpdate20100107.exe
WPILibSource20100107.zip
NetConsoleClient_1.0.0.4.zip
FRCLabVIEWUpdate2.0for2010.zip
FRCLabVIEWUpdate1.0for2010.zip
DSUpdate1.0for2010.zip
The cRIO was successfully imaged with v19 on a wired connection. We used “VxWorks Downloadable Kernal Module Sample Project” named “Default Robot Main Program” as the code to test our connection with though our router we received in our kickoff kit last year as a rookie team. It built fine and we had set our team number correct in workbench options as well. When we downloaded the .out file onto our cRIO using a wired connection through the router it said it was successful and went fast. When we logged into our driver staion in the atom it said the cRIO image was v19 and everything was green expect it said “No Robot Code.” Last year we had a similar issue when the downlao to the cRIO would say done successfully wasn’t actually. The way we fixed it last year was by another team’s programmer working on it and doing a couple, more updates.
Did we miss some updates? How can we fix it? Did we use the wrong build in workbench?
Also, what does the atom’s static IP have to be to run the driver station. And what are all of the other IP’s we need for other components like the cRIO (just to double check).
Ad finally, Do we have to use the blue router from last years kit to run the station or is it possible/allowed to set up ad-hoc or something o nthe atom to host the single to the robot?
Thanks! Love the forum!
I love Windows 7 and Vista (call me a Micro$oft fanboy; I don’t care), but UAC was the one thing I couldn’t stand on both Vista and 7. It’s the first thing I shut off when I get a new computer with either OS on it. It fixes so many problems instantly…
