[Greg McKaskle]

If the Communications and Robot Code light are on, that means that the cRIO has a startup app and image that is self consistent, and that the code is running. If the PWMs aren't being updated, that could be due to a number of reasons.

The analog breakout in slow 1 needs to have power and a breakout in order to return something other than 0.0. I don't know of anything a cRIO can do alone to melt a breakout board, but I could see how a faulty breakout, one that had power and ground pins shorted together might build up enough heat to melt, and clearly wouldn't measure anything useful while that was going on.

If you did something to your cRIO so that it is no longer valid for competition, I'm not sure that sharing that approach with other teams is the most helpful thing to share. Swapping cRIOs actually swaps lots of stuff including FPGA images and other libraries. Did you check what error messages were on the Diagnostics screen? Did you verify that the versions of the cRIO image and FPGA image were as expected?

Finally, would you please explain what was done to the cRIO to "fix" it but make it illegal?

Greg McKaskle