CRIO Rebooting woes

[DangitDrBob]

Hello, Team 4135 Beyer Robotics Representative here.

Our cRio is having issues currently. Our team is using WindRiver. We try to bring the cRio up to date with the most current image, v52. When we try to re-image it, the cRio gets stuck on the rebooting phase. We have searched the forums for solutions and have found nothing that works. We have tried:

-Setting the IP and subnet for the computer to: 10.41.35.5 and 255.255.255.0 respectively
-Turning the firewall off
-Running in safe mode, and reformatting
-Running not in safe mode
-Using a switch, then an ethernet cable directly to cRio
-Using a cross-over cable directly to cRio
-Using an ethernet cable directly to cRio
-Using the provided dlink wirelessly and wired
-Using the IP Reset, but it would not activate
-Reinstalling Windriver, Driver Station, and the imaging tool
-Using at least 4 different computers on various OS(XP,7,8) attempting all the methods above
-Test using last year's cRio and robot(Success)
-Repeatedly hit our heads against concrete pillars

Any suggestions would be greatly appreciated. We are at a loss. The only options we have left are switching cRios with last year's robot, buying another cRio, using Labview possibly, or blaming the wirers.

-Thanks
Fred C. Beyer Robotics Team 4135

[Greg McKaskle]

You didn't list contacting the support staff at NI. Have you done that? They are there to help.

Greg McKaskle

[eddie12390]

I'm not sure how C++ compares but at least for Java if you're getting a message about waiting for a server, you need to manually press the Reset button on the face of the cRIO. Also, some of the guides suggest using 255.0.0.0 as the subnet mask (such as the one for using NetConsole).

[dvanvoorst]

Try disabling all other network adapters other than the one you're using to communicate with the cRIO. That seems to be a common solution to this type of problem.

[DjScribbles]

I encountered this exact issue a couple times last season, to solve it, go into your IP Configuration, go to the advanced menu, and removed any alternate IP's (10.0.0.x is likely there, which is added by the Radio configuration utility and never removed).

Hope this helps.

[Sparkyshires]

Are you sure its stuck? That step just takes forever. give it like half an hour.

[eddie12390]

Originally Posted by Sparkyshires

Are you sure its stuck? That step just takes forever. give it like half an hour.

I've never seen a reboot take more than around a minute. The longest process is probably the cRIO Imaging process and even that only ever takes around 5 minutes (and includes multiple reboots)

[jwhite]

See this thread:
http://www.chiefdelphi.com/forums/sh...hreadid=124800

Long and the short: you must install LabView for it to work.

[MamaSpoldi]

We have had a similar issue this season with seeing the "Rebooting" message which never finishes while trying to re-image the cRIO. Although I understand that there are others who might disagree on the necessity of some of the steps in our method, this is what has reliably been successful for us this year. [Note that we had not seen these issues in previous years.]

1). Make sure you have your wireless turned off (disabled) on your laptop.
2). Make sure that you have your IP address configured to 10.xx.yy.5 and make sure that there are no other additional/alternate IP addresses setup. (You can check this and remove them by clicking on the Advanced button from the TCP/IPv4 Properties panel).
3). Reboot the laptop if you had to make any changes in the above settings. Not exactly sure why but it definitely makes a difference, perhaps there is residual connection otherwise.
4). Connect directly from the laptop to the cRIO using a CROSSOVER ethernet cable.
5). Use the cRIO imaging tool provided and follow the instructions for the configuration you want (ie. C++, netconsole, etc).

Hope this helps.

[billbo911]

Originally Posted by eddie12390

... Also, some of the guides suggest using 255.0.0.0 as the subnet mask (such as the one for using NetConsole).

+1

Subnet mask 255.0.0.0 is used for a Class "A" address, which 10.0.0.2 is.
It makes sense that 255.255.255.0 would also work but it does not.

If your Lappy is set up for 10.41.35.5, a subnet mask of 255.255.255.0 will force the default gateway to be used to reach a 10.0.0.2 address. Using 255.0.0.0 will allow it to talk directly on the same subnet, thus not need the default gateway.

Got the "Deer in the Headlights" look yet?

[DangitDrBob]

Thank you all for the replies. I believe most of them we did besides contacting NI support. We fixed the problem by switching to an older cRio and it worked perfectly. We believe that the cRio we were sent was faulty. Thanks for your time!