Another Can't Download Code Thread

[rjn]

Here's the situation. We have updated the DS with the DS update, Labview update, imaged the crio for with v19 for windriver, and on our programming laptop, we freshly installed Windriver, and applied all of the patches. The workbench update was just fine and unpacked everything. I can ping the cRIO and the Dashboard can receive communication, and we can even download LAbview code onto our robot and it will work. In the network tab in Windriver I can see all of the processes running on the crio, and sometimes when I download the code the bar will fill up, and at other times it will error out with an "IO error while downloading...".

Another note is that I created a new remote registry for our IP address, however it won't connect. We have configured our FIRST download preferences and all of our IP stuff has been set up. We have gone through that gosh darned getting started with c manual a million times.

[ehochstein]

Try going through all of the Getting Started manual again! That worked for our team! I'll have exact instructions on how we fixed ours tomorrow if you would like, pm me.

[rjn]

We have gone through the manual over more than once. Fresh installs, what else?

[ehochstein]

Just checking, but you are going through the benchtop test correct? and i know it has something to do with that error you are getting, but i can't remember exactly what we did to fix it after that... all i know is we went to (in windriver)
window -> preferences
there is something there that should fix it. i'll try to get better information for you today around 240

[heydowns]

Originally Posted by rjn

Here's the situation. We have updated the DS with the DS update, Labview update, imaged the crio for with v19 for windriver, and on our programming laptop, we freshly installed Windriver, and applied all of the patches. The workbench update was just fine and unpacked everything. I can ping the cRIO and the Dashboard can receive communication, and we can even download LAbview code onto our robot and it will work. In the network tab in Windriver I can see all of the processes running on the crio, and sometimes when I download the code the bar will fill up, and at other times it will error out with an "IO error while downloading...".

Another note is that I created a new remote registry for our IP address, however it won't connect. We have configured our FIRST download preferences and all of our IP stuff has been set up. We have gone through that gosh darned getting started with c manual a million times.

You mentioned having success with downloading LabVIEW code, but are having trouble with C++ programs from Windriver. Did you re-image for C++ after trying it with LabVIEW? A cRIO imaged for LabVIEW will not run C++ programs and interact with WindRiver properly.

The preference that Wiifi is mentioning controls to what IP address the FIRST->Download tool will attempt to download code to. If you are getting timeouts downloading code, double check the FIRST Downloader preferences: Window->Preferences->FIRST Downloader; ensure your team number is correct and that the path to the binary file to download is correct.

[rjn]

Yes, we formatted more thabn once even, it is v19 and it is for windriver, the DS confrims it. And we are 100% sure that our download preferences are correct.

[ehochstein]

Yes, that is what I could not remember the
Window -> Preferences -> FIRST Downloader

Then you have to enter the information included in section 2.8.2 of this manual: http://usfirst.org/uploadedFiles/Com...ed-Rev-0.7.pdf

[rjn]

Well, I don't know where to go from here, so I'll just try another clean wipe all over and see how that goes. Wait, C++ binaries work on the Labview cRIO image?

[heydowns]

Originally Posted by rjn

Well, I don't know where to go from here, so I'll just try another clean wipe all over and see how that goes. Wait, C++ binaries work on the Labview cRIO image?

No, typo! Sorry and corrected

[Bryan Herbst]

We got it working. The only thing we did was turn off the laptop. As soon as it began shutting down, the DS recognized the robot code. From then on, everything worked as it should.

Apparently we did not restart the laptop after reinstalling windriver, which may have been the problem.