cRIO won't reboot during imaging

[Zaque]

Hello,

I have been trying to reimage our cRIOs with the v52 image. I have tried with an FRC and an FRC II. I have tried with and without a router. I have tried changing the console out dipswitch. Every time, it gets to the point where it waits for a reboot. I usually wait about 5 minutes, but I did wait for a half hour or more one time. I have already searched the forums for help. If anyone could give assistance or direct me to a helpful thread, it would be much appreciated.

Thanks,
Zaque

[Zaque]

I also disabled the firewall and I have installed the 2014 NI FRC Update. I set my IP address to 10.33.52.6 and the subnet to 255.255.255.0. I have been using a standard Ethernet cord, not sure if I need to use a crossover.

[DavisC]

I recommend following the guide at this link every time you re-image the cRIO, every time that I have sat down and followed it exactly I have successfully re-imaged it.

http://www.chiefdelphi.com/forums/sh...44&postcount=9

If you are unsure about needing a crossover cable, have the cRIO and computer connected via a switch or a router (wired connection).

Hope this helps!

[rsisk]

Originally Posted by DavisC

I recommend following the guide at this link every time you re-image the cRIO, every time that I have sat down and followed it exactly I have successfully re-imaged it.

http://www.chiefdelphi.com/forums/sh...44&postcount=9

If you are unsure about needing a crossover cable, have the cRIO and computer connected via a switch or a router (wired connection).

Hope this helps!

Link doesn't work, could you fix it?

[wt200999]

Our team was having a problem similar to what you are describing. One thing that we noticed it that when you go to the command prompt and type "ipconfig" the LAN adapter connected to the robot had 2 IP address associated with it.

To change this and only have one IP address, go to your TCP/IPv4 Properties, and on the bottom select Advanced...

Delete the extra IP addresses.

When we did this it worked every time. It seems like the tool adds an IP address every time so if this also works for you, you may have to follow these steps every time.

Hope that helps

[DavisC]

http://www.chiefdelphi.com/forums/sh...44&postcount=9

Here the link works, fixed it above as well.

(evidently CD shortens the link with "..." so when you just copy the link from a different post, it copies the "..." link not the full one)

[Zaque]

I won't be able to try it until tomorrow, but isn't the subnet mask supposed to be 255.255.255.0?

Edit:I didn't try imaging with safe mode off, so hopefully that will fix the problem.

[wt200999]

The subnet mask is actually not that important in this context (as long as the team number is the same across the board)

[DavisC]

Originally Posted by Zaque

I won't be able to try it until tomorrow, but isn't the subnet mask supposed to be 255.255.255.0?

Edit:I didn't try imaging with safe mode off, so hopefully that will fix the problem.

Originally Posted by wt200999

The subnet mask is actually not that important in this context (as long as the team number is the same across the board)

I was imaging the 2014 Image on Saturday and believe the subnet mask was "255.255.255.0", looking back on the document I do not remember why i said "255.0.0.0" (I think an FRC guide said it someplace, not sure).

[joecloud]

I had the exact same problem the other day. The official guide says to wire the cRio to your PC directly. But what worked for me was connecting both to the d-link router.