Quote:
Originally Posted by Bluman56
The robot runs but can be intermittent at times, showing a "No Robot Code" error then going back to "Teleoperated Disabled" suggesting a power cycle occurred. At our regional, we had a CSA help us with it (I think he even asked Mark McLeod about the behavior) and ended up suggesting that the problem stemmed from our 10 amp red fuse slot being "jammed". We were issued a temporary replacement and all worked well with it.
If I'm not mistaken the two LEDs flash orange/green (it's been a while). We got in contact with CTRE after the regional and they said it was a software issue with the device ID being set too high last year (2015)? They told us to "Disconnect CAN bus between the robot controller and the missing-ID-device. Then power-cycle or reboot the roboRIO. Navigate to the roboRIO's webpage and wait until page fully renders. Now reconnect CAN bus and manually-refresh the browser until device appears."
That didn't solve it either.
|
According to the
user guide, orange/green LEDs indicate you need to upgrade the firmware, but you cannot do that if you cannot see it in the web dashboard.
Important things to check are that you have the wires stripped to the proper length before inserting them into the weidmuller connectors, the wires are going into the right ports based on high/low (yellow/green) and you have a terminating resistor. If this is all correct I would again contact CTRE.
I am doubtful that the issues with CAN communication are related to the odd behavior you saw from your robot. The 10 amp fuse and slot could cause the roboRIO to reboot if there was an intermittent connection. If you only saw "No Robot Code" but not "No Robot Communication" than I would evaluate your code for any place where an error would be thrown instead of looking for a case of the roboRIO rebooting.