Quote:
Originally Posted by stinglikeabee
Have you reverted to the original configuration (plug everything back in) with a fully-charged battery yet? Set a baseline and work from there. Maybe your diagnostic messages also existed prior to unplugging the systems.
|
We immediately put everything back into place and used a fully-charged battery, but it has made no difference. I suspect the diagnostic errors were probably there, but I can't be sure, as I never checked before.
Quote:
Originally Posted by Secretspy97
Last year, week 5 of build season we had a similar problem happened to us. When the robot was enabled the cRIO wouldn't respond to inputs or print out data. We removed the cRIO and tried another one but had the same problem. Next we checked the digital sidecar. We went one by one removing the PWM cables to see if there was any small piece of metal shorting out the board. We eventually found the shaving and once it was removed the robot once again functioned properly.
|
The cRIO might be the problem, but I can't be sure. I thought that there might possibly be a shaving or other metal debris interfering, as I noticed quite an accumulation of dirt and dust. I'll check the PWM cables tomorrow, but I wouldn't be surprised if there's a short somewhere. I'm no expert, but it just seems odd to me that every motor controller would give the same signal if there was only one short.