we’ve had a new problem with our accelerometers that have only recently appeared. Using labVIEW:
- On our first run of the robot, the accelerometers will read infinity for all axes
- We then stop the code and re-run it. This time, the accelerometers work correctly for a few reads - three to five readings - and then stops altogether. other sensors still read values
- We then stop the code and re-run it again. This time, accelerometers work fine.
It repeats this pattern over and over again. we haven’t changed any accelerometer initialization/reading code for a while, although we did have to re-sodder the PWM wires a few days ago. I would consider this to be the cause of the problem, but how would a hardware/wiring problem create a deterministic loop?
Obviously this indicates that your robot has zero mass.
Sorry, I know you were looking for a more helpful answer than that. Have you tried using a multimeter to read the voltage on the accellerometer leads? That might help determine whether the problem is in the accellerometer or in the cRio software.
Jason
In addition to seconding Jason’s advice, I would suggest posting your code here. It sounds to me like software.
Are you traveling at or near the speed of light?
What is your scaling factor or rate set to? Could there be a divide by zero somewhere?
Are you dividing by zero anywhere in your code?
haha fixed the problem. the protons were going too fast
Whenever you have a problem and a solution, please make an effort to post them both. This will help other teams in your position later.
ahh, apologies. the problem was just a low battery :o… what protons?!