612's ball launcher - prototype

[jskene]

Early launch video.

We are spinning the spoked wheels with 2 CIM motors turning ~ 2700 rpm. Aerodynamic improvements in the design have now increased this to >5000 rpm.

We plan to slow it down a bit for the competition.

Chantilly Academy's ball launcher

[phrontist]

That's faster than is legal, right? Man, that's really nice, you'll be able to get it right up against the limit :-)

[Salik Syed]

Pretty cool, looks quite smooth.
the limit is actually really low, we thought we were going really slow (I estimated 4m/s from observing) but it turned out to be close to 10 m/s...
a ball shot vertical at 12 m/s only goes about 20 ft high!

[1574aviad]

Looks really cool. Although seems like you almost hit someone .

[Faith]

Looks pretty neat. How accurate is it?

[jskene]

We think that the speed is just about right actually. We angled the shooter at 30 degrees, and it lobbed the ball 35', just like the specs said. We plan to measure the speed with a police radar gun.

[Schneidie]

Originally Posted by jskene

Early launch video.

We are spinning the spoked wheels with 2 CIM motors turning ~ 2700 rpm. Aerodynamic improvements in the design have now increased this to >5000 rpm.

We plan to slow it down a bit for the competition.

Chantilly Academy's ball launcher

Have you built an aiming system yet?

[jskene]

Yes, we have designed and built the aiming system, and should be testing it this week.

We have a rotating turret, to which the camera is attached. The camera is queried by the robot controller, and the turret is turned one way or the other to keep the camera aimed at the green light, irrespective to the orientation of the robot chassis.

For elevation control, we use a curved deflector that changes the direction of the ball from vertical to horizontal - or some angle in between. This is controlled by the threaded shaft in the KOP. A modified Globe motor (5 x normal speed by bypassing one layer of its planetary gear train) rotates the shaft to change the elevation. The degree of elevation is computed by reading the target Y axis info from the camera's vertical servo, which we retain, in combination with the measured target area, which gives us an approximation of the range to the target. We ditched the X servo, as the turret rotation serves this function now. We plan to empirically generate a lookup table to correlate the camera elevation and target size to the required elevation of the curved deflector.

We are hoping that this will give us automatic, on-the-fly targeting capability, with no operator interaction. Of course, theory and practice seldom have anything to do with each other.

We'll find out more this week, and will post videos if things work out.

[Sachiel7]

Again (I've been saying this alot this year...) that sounds extremely familliar ^