Quote:
Originally Posted by bcieslak
You can add us to the no code error issue too.
we are running the wind river tools
We tried deploying the default code and it seemed to download ok but the driver station said no robot code..
Crio has the v19 image...we updated the workbench to the latest update 20100107 . we cant check error messages via the serial port because the crio is not talking back to the laptop for some reason.
Here's the catch..we also tried using a laptop with last years tools on it and we were able down load and run the default program
Any Clues??? I sure didn't plan spending the first three weeks of build season getting the tools to work... 
Brian
Team 1714
Sr Firmware Engineer
Rockwell Automation |
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!