You can't break it, they said. Try, they said.

[KeeganP]

Quick disclaimer: I am not a programmer on the team, but I do some electrical work. 5 years FRC experience. And yes, I know the NI number to call -- I plan to have the programmers call during tonight's meeting since they know more about it than I do.

The problem:
Basically, we bought a roboRIO back a month ago or so, and that one works just fine. The brand new one in the KOP worked fine for two nights of testing (and driving on a 2013 robot), but then last night we ran into a bug. It stopped working

Copy pasted from the programmers:
-Imaging doesn't work.
-22 is closed, and 80 & 443 don't work (hangs in browser).

-Holding reset starts it back in "safe mode."
-Then, 22 works, but 80 & 443 still don't (presents an error).
-Updating firmware doesn't work.

- In both modes, web-based control doesn't work, and you have to use the USB cable.
- FTP rejects all users in both modes.

Any help is greatly appreciated -- have any other teams run in to a similar issue? To our knowledge, the RIO hasn't been set on any motors/magnets, and there are no metal shavings anywhere near it at all. We've checked the wiring, and it all *should* be correct according to diagrams, but we forgot to check the actual voltage coming into the RIO with a multimeter (but it worked fine exactly as it is setup for 2 nights, then randomly stopped...). Also, all of the above testing is with only power connected to it -- no sensors/Talons/etc.

Fortunately we have a backup roboRIO, but since we don't know what happened to the first one, we can't really prevent the same from happening to our second one... Thanks!