View Single Post
  #4   Spotlight this post!  
Unread 05-02-2017, 08:11
RufflesRidge RufflesRidge is offline
Registered User
no team
 
Join Date: Jan 2012
Location: USA
Posts: 992
RufflesRidge has a brilliant futureRufflesRidge has a brilliant futureRufflesRidge has a brilliant futureRufflesRidge has a brilliant futureRufflesRidge has a brilliant futureRufflesRidge has a brilliant futureRufflesRidge has a brilliant futureRufflesRidge has a brilliant futureRufflesRidge has a brilliant futureRufflesRidge has a brilliant futureRufflesRidge has a brilliant future
Re: roboRIO 2017 update over ethernet / SSH

Quote:
Originally Posted by euhlmann View Post
1. Make sure you set your computer to a static IP. The roboRIO doesn't run DHCP!
Only if your roboRIO is set static...otherwise you are setting your computer to a 10. while the roboRIO has a self assigned 169 address.

I would try placing a network switch between the roboRIO and the computer, especially if the roboRIO is set to DHCP. When the roboRIO reboots as part of the imaging process many computers will take too long to bring the network back up because they are trying to get an address.

It is also possible that you may see a failure near the very end of imaging even if the image has loaded. If the tool rescans and says that the image is 2017_v8 but the team number is blank, try just setting the team number and clicking Apply.
Reply With Quote