Keyreaper
29-01-2012, 20:52
Pardon me if this isn't the right place to post this but I have an urgent matter regarding our robot.
Well yesterday around mid-afternoon our robot was completed and handed off to the programming team (me and my assistants) to get it up and running. All is good and dandy right? Well we loaded our code, got everything in set and ran teleop. As expected everything worked. But only for about 10 seconds. Then we decided to run our shooter (two banebot's 550 models hooked up to a 2.7:1 reduction CIM-U-LATOR), in which it spun up and then we lost connect to our cRIO. Upon further inspection our team discovered that our cRIO seemed to have fried. We didn't know how this was possible but none the less not something that was impossible. We tried everything to get it back and running making sure that our wires were properly connecting, as well as using an external power supply in attempt to get it working. No luck. We replaced the cRIO with our spare, which is also slightly nonfunctional as the first cRIO slot doesn't work, but can still run code.
After running the code and testing functions out on our robot for a good 5 minutes, the same thing happened as with our other one.
1.) We ran code for about 5 minutes, testing things to make sure our code and mechanical functions worked.
2.) After some use on the shooter we decided we'd test it one more time just to make sure everything was in check.
3.) Spinning the shooter up, we suddenly lose connection to the cRIO and everything on the bot shuts down and reboots.
4.) Upon inspection (once again) everything was fine except our cRIO, which happened to fry aswell. :eek:
We opened both cRIOs up to see if we could find anything wrong with them, or if we could spot any burnt marks but we could not.
Is there any advice to how to get these fixed or replaced? :confused:
And is there any reason that you guys might be able to come up with that could have caused this? And how to avoid it?
Well yesterday around mid-afternoon our robot was completed and handed off to the programming team (me and my assistants) to get it up and running. All is good and dandy right? Well we loaded our code, got everything in set and ran teleop. As expected everything worked. But only for about 10 seconds. Then we decided to run our shooter (two banebot's 550 models hooked up to a 2.7:1 reduction CIM-U-LATOR), in which it spun up and then we lost connect to our cRIO. Upon further inspection our team discovered that our cRIO seemed to have fried. We didn't know how this was possible but none the less not something that was impossible. We tried everything to get it back and running making sure that our wires were properly connecting, as well as using an external power supply in attempt to get it working. No luck. We replaced the cRIO with our spare, which is also slightly nonfunctional as the first cRIO slot doesn't work, but can still run code.
After running the code and testing functions out on our robot for a good 5 minutes, the same thing happened as with our other one.
1.) We ran code for about 5 minutes, testing things to make sure our code and mechanical functions worked.
2.) After some use on the shooter we decided we'd test it one more time just to make sure everything was in check.
3.) Spinning the shooter up, we suddenly lose connection to the cRIO and everything on the bot shuts down and reboots.
4.) Upon inspection (once again) everything was fine except our cRIO, which happened to fry aswell. :eek:
We opened both cRIOs up to see if we could find anything wrong with them, or if we could spot any burnt marks but we could not.
Is there any advice to how to get these fixed or replaced? :confused:
And is there any reason that you guys might be able to come up with that could have caused this? And how to avoid it?