The Unfortunate Lack of Robot Code

[Eric Caldwell]

My team was having this problem a week ago, and re-imaging the crio fixed the problem for us.

[linuxboy]

Originally Posted by Eric Caldwell

My team was having this problem a week ago, and re-imaging the crio fixed the problem for us.

That would definitely be what I would try. You may also want to check and make sure that the NO APP (and similar) DIP Switches are not set to on. The DIP switches are the things being pointed to in this image.

Good luck
Oliver

[Beave]

Thanks again, the NO APP switch is off.

is there a specific process to reimaging the cRIO beyond just pressing the reset button and/or extracting the latest image via FTP? I have read about a "cRIO Imaging Tool," but apparently that requires LabVIEW, and, characteristic of our team, I can not find the installation disk from last year's KoP. Any further suggestions?

[Greg McKaskle]

The imaging tool was written in LV, but that is irrelevant. If the tool is installed on the computer, it will run independently. I'm not positive, but I believe you will find the tools in the Start menu >> National Instruments>>"not sure" >> FRC cRIO Imaging Tool.

If you don't find it there, look in the installed SW tools to see what is there from National Instruments.

Greg McKaskle

[linuxboy]

I'm fairly certain the cRIO imaging tool requires the LabView runtimes that come on the LabView disk teams get at kickoff (in the "Install FRC tools and utilities option). There is a way to download those run times but I wouldn't suggest doing that. If you have access to the Classmate that should have the imaging tool and the runtimes on it. Make sure to do all the Utilities updates available that aren't already installed on your classmate.

[Greg McKaskle]

Yes. I should have said that better. Be sure to install the imaging tool, as that will include the dependencies such as the LabVIEW runtime DLLs. If you copy it to a computer, it will not run successfully.

Greg McKaskle