Quote:
Originally Posted by davidthefat
I personally think it is more than doable; the teams just need to have a very expandable and scalable engine. That will take a long time. But once you have the engine, I believe it is doable in 6 weeks. My worry is using too much funds for such goals. I don't want to put a cap on how much the other departments can use for the robot. The sensors do not pay for themselves.
My other worry is: "Woop dee doo, you have a fully autonomous robot; what is the big deal?" Programmers would be impressed; no one else would be. It mostly is a public statement to even have autonomy. The drive team was mostly seniors, and a sophomore and I will be the only ones left next year. I don't think drive team would mind.
Third, it seems like a very selfish goal. I am purposely choosing NOT to be the team captain next year for the fear that I would turn out to be a dictator and drag the team down with me. I am nominating someone else on purpose.
Oh and BTW, I love your signature Mr. Mike
|
Haha thanks! It was my quote for my slot in the senior yearbook.
I definitely think it is possible in 6 weeks also, but there would be some requirements. First using almost an identical chassis. Second, a swerve or a mecanum would make the task a lot easier. Third, working libraries for each sensor (many could be a layer on top of wpiLib) and a working camera library on the driver station (I just got Open CV working in netbeans on my mac).
My list of absolute requirements for autonomous logomotion:
2 cameras
2 rangefinders
strafe (mecanum, swerve, drop strafe)
encoder on arm/lift
5 ft / s @ 90% on at least one speed (hopefully not the only speed)
ideal additions
a third camera for the robot (on board processing)
1 compass
1 gyro
encoders on everything
multi-speed transmission