Chief Delphi

Chief Delphi (http://www.chiefdelphi.com/forums/index.php)
-   Programming (http://www.chiefdelphi.com/forums/forumdisplay.php?f=51)
-   -   roboRIO 2017 update over ethernet / SSH (http://www.chiefdelphi.com/forums/showthread.php?t=154735)

michaelwm 04-02-2017 15:46

roboRIO 2017 update over ethernet / SSH
 
One of our roboRIO's fried one day last year during an upload over USB-B. The cable started burning and the USB controller in the rio is now bricked. The ethernet port still worked though, so we were able to set the rio aside as a backup & testbench rio.

But now 2017 is here and we can't write 2017 WPILib software without updating the rio to the new 2017 image. We can't connect over USB-B, and we tried using ethernet and the NI roboRIO tool but that didn't work either.

Is there something else we can try? A different ethernet solution? SSH? Or is the rio garbage now?

Bkeeneykid 04-02-2017 16:33

Re: roboRIO 2017 update over ethernet / SSH
 
Quote:

Originally Posted by michaelwm (Post 1640397)
One of our roboRIO's fried one day last year during an upload over USB-B. The cable started burning and the USB controller in the rio is now bricked. The ethernet port still worked though, so we were able to set the rio aside as a backup & testbench rio.

But now 2017 is here and we can't write 2017 WPILib software without updating the rio to the new 2017 image. We can't connect over USB-B, and we tried using ethernet and the NI roboRIO tool but that didn't work either.

Is there something else we can try? A different ethernet solution? SSH? Or is the rio garbage now?

What's your problem with the ethernet cord? That should work (it's what we used this year).

Also, if you have a fried RIO, contact NI. They are always extremely helpful to FIRST teams and will probably offer you a replacement at a reasonable cost.

euhlmann 04-02-2017 17:03

Re: roboRIO 2017 update over ethernet / SSH
 
Quote:

Originally Posted by michaelwm (Post 1640397)
One of our roboRIO's fried one day last year during an upload over USB-B. The cable started burning and the USB controller in the rio is now bricked. The ethernet port still worked though, so we were able to set the rio aside as a backup & testbench rio.

But now 2017 is here and we can't write 2017 WPILib software without updating the rio to the new 2017 image. We can't connect over USB-B, and we tried using ethernet and the NI roboRIO tool but that didn't work either.

Is there something else we can try? A different ethernet solution? SSH? Or is the rio garbage now?

1. Make sure you set your computer to a static IP. The roboRIO doesn't run DHCP! Make sure you can ping the roboRIO
2. If you can ping the rio but the imager tool still doesn't work, try setting the roboRIO's ethernet interface to a static IP of 172.22.11.2 through the web dashboard so it might be able to pretend it's over USB

Worst that can happen is you brick your whole rio, so make sure you're ok with that

RufflesRidge 05-02-2017 08:11

Re: roboRIO 2017 update over ethernet / SSH
 
Quote:

Originally Posted by euhlmann (Post 1640437)
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.

euhlmann 06-02-2017 03:42

Re: roboRIO 2017 update over ethernet / SSH
 
Quote:

Originally Posted by RufflesRidge (Post 1640631)
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 meant that the rio doesn't run a DHCP server - so your laptop will not be assigned an IP address automatically

Joe Ross 06-02-2017 15:55

Re: roboRIO 2017 update over ethernet / SSH
 
Quote:

Originally Posted by euhlmann (Post 1640949)
I meant that the rio doesn't run a DHCP server - so your laptop will not be assigned an IP address automatically

No, your laptop will self-assign a link local address, which is compatible with the link local address the roborio will self-assign. If you assign the computer a static ip address and the roborio uses a link local, it will never talk. If you assign both the roborio and computer compatible static ip addresses, it will work until the roborio reboots after loading the image, and assigns itself a link local address. This will probably show up as an imaging failure.


All times are GMT -5. The time now is 22:36.

Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Copyright © Chief Delphi