Problem with cRIO Imaging Tool

[DocWu]

Our team has purchased a second cRIO-FRC for the upcoming season. In preparing to use it to teach our programmers and develop code, we breadboarded the control system temporarily to work with off a robot.

I am trying to load the image to the cRIO, but am not able to get the FRC cRIO Imaging Tool to recognize the cRIO. I am connected to the cRIO with a crossover cable to a laptop (we have tried two laptops.) But we keep getting the "No Compact RIO devices found." message.

I can run MAX and set the IP address or load software to the cRIO, so it IS connected and is not a network problem - cable, laptop setup, etc. I can also ping the cRIO from a command line.

I can run LabView and deploy projects. I haven't tried them out with a driver station and most of the hardware doesn't exist on the breadboard at the moment, but it appears to be functional.

But, I am not sure the correct image is on the cRIO and want to be sure in case there is a problem later. I also need to be able to update the image if updates are issued.

I've read several postings here and elsewhere about similar problems, but have not been able to resolve this. Is it a problem, or should I leave well enough alone for now? Any ideas how to fix this?

[sciencewhiz]

Can you post the results of ipconfig /all

If you ftp to the cRio, there is a file called frcimageversion.ini that will tell you what image is on it. This was implemented part way through the 2009 build season, so if that file doesn't exist, you do not have the latest cRIO image.

Have you installed LabVIEW update 3.0a to make sure you have the latest image and imaging tool?

Message was edited by: sciencewhiz

[DocWu]

I believe we have update 3.0 installed. The image file is the _11 version.

I don't know about FTPing or using the serial interface. We haven't tried either of them.

Anyway, the imaging tool started working today after many tries and I've got the image loaded.

[User002]

We had this problem, too. The fix was to set the cRIO's "console out" bit switch back to "on" then reboot the cRIO.

This point is not mentioned in the instructions http://decibel.ni.com/content/docs/DOC-2872

BTW it works to connect both the laptop and the cRIO to the router by (non-crossover) ethernet cables.

[DocWu]

"Note: You have not assigned any helpful or correct points. To do this,go back to your question and click on "helpful" or "correct" next to each message. Awarding points is an important way to encourage people to answer your questions in the future."

Can't say I see the way to do that... Oh well.

The problem has been resolved. Don't really know how or why. No one response was particularly helpful and Chief Delphi is full of posts from teams experiencing similar problems. At this time, close to ship date, I assume most everyone has solved this.