Quote:
Originally Posted by michaelwm
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.