|
cRIO Solenoid Module Getting Stuck On
We have been having some trouble with our cRIO and getting it to run our code without errors. In the past we were unable to reimage the cRIO so we opened it and removing little pieces of metal. After this our cRIO can be reimaged but it does not work with the solenoid module. When we do not use our solenoid code, or put in the solenoid module, we do not get any errors. If we run the solenoid code without the module being in we get some errors but everything else on the robot works. When we first turned on the robot without any code on it with the solenoid module in, it turned on output 3 and the output 3 LED on the solenoid module, and it dimly flickered the output 7 LED. After turning the robot on and off several times we were able to power on the module without activating any solenoids. The same problem occurs with the LEDs with the solenoid breakout removed. When we deployed code onto it, we had control of the solenoid module momentarily and set two solenoid outputs on but were unable to control them after the code started. We are using code that we know works. Then when we used our robot with the solenoid module in, all of the control signals coming from the cRIO would drop out every few seconds which made the robot twitch. Whenever the robot twitched all of the lights on the victors went back to flashing, all of our spikes that were on turned off, and the lights on the solenoid module turned off. Also during the twitches we have watchdog errors which happen at the same time as the twitch. We did not get these watchdog errors when the solenoid module was removed. We think that when all of the control signals turn off it causes a watchdog error. When we have the errors our CPU usage is at 60%. Before we cleaned and reimaged our cRIO we had watchdog errors constantly when we ran any code, including the default new project code. We think that the twitching was caused by the cRIO turning off the power to the digital and solenoid modules. Another issue is that the solenoid module continued to output power on two channels when we disabled the robot. When we restarted the robot the two channels remained on even though no code was running and we unplugged and plugged back in the modules several times. The twitching and loss of signal only occurred when the solenoid module was being used. We think that the solenoid module may be shorting out the cRIO's internal power supply for the modules.
Last edited by apples000 : 16-03-2012 at 19:35.
Reason: typo
|
One wondered why they couldn't practice in the gym that day - because the robotics team had it reserved was the answer. "Oh, we have a robotics team?"
Sigh. This is a team with a low number. They've been around for at least a dozen years. There's still a lot more culture-changing to do. - GaryVoshol [more] 
16-03-2012, 19:45
Linear Mode
