Quote:
Originally Posted by carrillo694
But chances are you might not have enough time to implement these fancier control techniques. I would try driving your robot backwards for a set time interval, and seeing if that accomplishes what you need for going to the bridge in autonomous. While you are right that this is not the most "robust" solution, have you tried it?
|
Yeah, thats a big part of the problem. We have 6 hours of out of the bag time to use, I have a feeling I'll get 1 or 2 of those. This is my first year on the team as a programming mentor, and the first year the team has used any sensors (as far as I know) and had any strong direction for programming. I feel we're going to have a pretty good robot, and have only a little tuning to do on our shooting automation PIDs. However, we don't have any encoders on our wheels, and haven't really done any steering correction before (I was planning to save it for an off-season project as I try to get some of the kids more involved in programming).
To implement something that will do more than drive backwards for x seconds seems out of reach, but we're about an hour away from kinect completion, which could fill that gap.
My concern is that the motion control could be unreliable (we're going to use default gestures with kinect stick) and we end up floundering in hybrid autonomous when a standard autonomous would have worked fine, simply because the kinect doesn't work as well as I'm counting on...