View Single Post
  #3   Spotlight this post!  
Unread 04-02-2017, 17:03
euhlmann's Avatar
euhlmann euhlmann is offline
CTO, Programmer
AKA: Erik Uhlmann
FRC #2877 (LigerBots)
Team Role: Leadership
 
Join Date: Dec 2015
Rookie Year: 2015
Location: United States
Posts: 410
euhlmann has much to be proud ofeuhlmann has much to be proud ofeuhlmann has much to be proud ofeuhlmann has much to be proud ofeuhlmann has much to be proud ofeuhlmann has much to be proud ofeuhlmann has much to be proud ofeuhlmann has much to be proud of
Re: roboRIO 2017 update over ethernet / SSH

Quote:
Originally Posted by michaelwm View Post
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
__________________
Creator of SmartDashboard.js, an extensible nodejs/webkit replacement for SmartDashboard


https://ligerbots.org
Reply With Quote