Quote:
Originally Posted by pfreivald
Right. We checked for that, and the powered gyro was drifting at that speed.
|
any more information on what happened here? I'm hoping to take a look at an issue that was reportedly like what you are describing. We used the gyro in 2011 with no issues, but I've never personally worked on it.
To anyone, how does the gyro temp feedback work in the code? (I don't usually get into the programming so you should talk to me like I'm 6) I'm poking through the java API and didn't notice temp anywhere in the gyro class. Since the temp is obviously going to a different channel than the gyro, it seems i would need to also set temp up as a separate sensor, but that too i didn't see in the sensorbase class. ??
Also to add 2 cents on the general mecanum talk: We've used mecanum since 2011 and never seen the "forward command equals horrible spin result" described all the time on CD. This is without gyro or encoder feedback. We have never been accused of having really fantastically designed and constructed drivetrains and have never given much (or any) time to weight distribution. This year a test drivebase was made which exhibited something
kinda like the "forward command equals spin", but it was very minor and the driver was able to compensate for it without much trouble. Just looking at it everyone figured the problem was the fact that the electronics board thrown on top had the battery cantilevered outside of the frame. At this point the battery had to be 25-50% of the total weight.
THEN it was discovered that the 8020 frame was assembled incorrectly causing the frame to be warped.
The combination of the 2 had one wheel taking almost none of weight. And
still the driving behavior was not
that bad. This leads me to the hypothesis that "forward command equals horrible spin result" behavior reported frequently is almost always caused by incorrect use or poor functionality of the gyro...