Shooter Aiming Methods

[jwakeman]

Originally Posted by Kusha

The people that are auto aiming:
Do you guys off put vision processing onto something else?

We had the camera streaming directly to the driver's station/class mate last year. We would do the vision processing there and send relevant coordinate info to the robot to make the position adjustments. Lots of teams did this last year, they gave an example last year that was setup for this.

[Lil' Lavery]

Originally Posted by z_beeblebrox

I'm thinking of putting vision processing into the operator's brain and combine the best of automatic and manual aiming. Instead of having the computer struggle to identify a target 50' away with different lighting, I want to have the operator look at the camera feed and click the center of the goal. Then, the computer uses that to figure out how much the robot needs to turn and how high to aim the shooter to hit the goal. The output from this will be fed to PID controllers for robot and shooter angles. When the robot has slewed to position and the shooter has spun up to speed, the operator fires a disc and makes corrections if it misses. Then, the operator rapidly fires their remaining 3 discs.

Certainly an interesting aiming concept. How will your computer know the range of an object based solely on the click of the operator? Are you assuming you're always firing from approximately the same distance from the goal? Are you going to have the operator click&drag a box that can be used to size the goal (and thus determine range)?

Additionally, you're then forcing one of your operators to either move his hands between two input devices (his typical input device and the computer), or be entirely dedicated to the computer (thus leaving both the driving and firing to the other driver). Forcing your operators to have to look at the controls rather than the robot* and move their hands between multiple devices are some of the cardinal sins of OI design for FRC.


*the obvious exception to this is when focusing on a camera feed on the OI.

[ctccromer]

Here's my PLANS for this year (final results may vary):

1) Auto-aiming system with a shooting system that does NOT move on a turret or anything. It can aim up/down slightly, but that's the only axis it moves on and only to an extent

2) I'm switching to a controller this year and my very first idea for coding the robot was to not only make the joysticks turn and move the robot, but also code it so that while I have the left trigger held down, make the joysticks turn and move the robot at 0.25 normal speed. This way you don't have to JUUUUUST BARELY NUDGE the turning joystick a bunch of times to line up the shot -- you can manually aim the whole ROBOT (not the shooter on a turret) at the goal, then use an algorithm to aim the shooter's motor speed and vertical height, NOT horizontal angle

[fb39ca4]

Last year, we had a slow mode button on our controller as well.

[falconmaster]

We had a great deal of success last year by locating landmarks on the field and then lining up with them and then launching the balls. We think we can do the same this year. To assist us though we are going to use a "photon cannon" aka flashlight http://www.amazon.com/8066-T6-Rechar...ts+1000+lumens
Like the three days robot builders guys. From our experience this is much faster and more reliable than computer vision processing. There are too many variables to account for that a human can adapt to that a computer without an extensive vision processing program can do as well or fast. Just my two cents...

[Anupam Goli]

Originally Posted by falconmaster

... There are too many variables to account for that a human can adapt to that a computer without an extensive vision processing program can do as well or fast.

This. Playing 20 minutes of Catalyst made me realize that within one hour of practice, a driver could find a sweet spot, sweet angle, and fire consistently. Granted, a very extensive vision processing system could do the same, but if your driver is confident enough, it'll most likely be faster for a human to line up to that sweet spot that is ingrained into the driver's mind.

[z_beeblebrox]

Originally Posted by Lil' Lavery

Certainly an interesting aiming concept. How will your computer know the range of an object based solely on the click of the operator? Are you assuming you're always firing from approximately the same distance from the goal? Are you going to have the operator click&drag a box that can be used to size the goal (and thus determine range)?

Additionally, you're then forcing one of your operators to either move his hands between two input devices (his typical input device and the computer), or be entirely dedicated to the computer (thus leaving both the driving and firing to the other driver). Forcing your operators to have to look at the controls rather than the robot* and move their hands between multiple devices are some of the cardinal sins of OI design for FRC.


*the obvious exception to this is when focusing on a camera feed on the OI.

Since you know the height of the goal and the angle from your shooter to its center, you can use simple trig to find the distance. I would give the operator a USB mouse for their right hand and a joystick (maybe a custom controls box) for their left.

[Dan Richardson]

Originally Posted by Wing

This. Playing 20 minutes of Catalyst made me realize that within one hour of practice, a driver could find a sweet spot, sweet angle, and fire consistently. Granted, a very extensive vision processing system could do the same, but if your driver is confident enough, it'll most likely be faster for a human to line up to that sweet spot that is ingrained into the driver's mind.

I think this is a great observation that is often overlooked. Having a good drive team is the keystone to a competitive robot. Great drivers need practice. Even good drivers get better with time at the sticks. Most teams seem not to make practice time a priority. Put this priority at top of the list and rethink resource strategies and your bot will instantly be more competitive.

Back on topic, I believe the photon cannon to be one of the most elegant targeting methods to date. I only wish we'd thought of it first.

[KrazyCarl92]

Using the pyramid as an alignment device and protection from interference by the opposing alliance seems like a great aiming method. Just back into the 30" horizontal bar and have the robot square up and you are in a known, consistent position relative to the target. And with the targets being so wide, the one degree of freedom this alignment method affords (translation short-ways across the field) also happens to be the largest dimension for the target. If a robot can score reliably from this position as well as one other defense will be rather difficult and aiming is REALLY easy from one of those positions.

[Lil' Lavery]

Originally Posted by z_beeblebrox

Since you know the height of the goal and the angle from your shooter to its center, you can use simple trig to find the distance. I would give the operator a USB mouse for their right hand and a joystick (maybe a custom controls box) for their left.

So you're assuming that as your distance from the target changes, so will its height in your camera's field of vision at a predictable rate? I'd recheck that assumption if I were you. If you're only moving in the axis orthogonal to the goal, this would be true. But does it hold true once you introduce the second (or third) axes of motion?

[Mr. Lim]

Originally Posted by Lil' Lavery

So you're assuming that as your distance from the target changes, so will its height in your camera's field of vision at a predictable rate? I'd recheck that assumption if I were you. If you're only moving in the axis orthogonal to the goal, this would be true. But does it hold true once you introduce the second (or third) axes of motion?

This is true, and we did it last year with EdgeWalker.

If the camera is kept at a fixed height, and a fixed angle, and you are directly in front of the goal, you've essentially limited your movement to the axis orthogonal to the goal. If you move left and right (perpendicular axis) the shape of the goal becomes trapezoidal, but if you use the centre of the bounding box of the trapezoid as your reference, you can compensate for the additional axis of movement.

The trick is finding a camera height and angle where there is enough change in the goal's height to give you meaningful information - AND where you can keep the goal in the field of view at every spot on the field you want to shoot from.

[jasp]

Last year our team tries vision processing with an non-axis camera and we never used it because it was not as accurate as we wanted and was very slow. If you do try vision processing I suggest using a raspberry pi or something similar.

[stingray27]

For anyone wanting a explanation of what the example code for vision processing is doing, I put up a youtube video here: https://www.youtube.com/watch?v=m2Pwdq30eSI last year where I explained to my mentor what it was doing. Please bear with it as it is toned down, slow and probably all not incorrect (and long). But I have gotten some good feedback in that my explanation made a lot of sense to even non-programmers. Check it out if your interested.

[jesusrambo]

Our plan for this year is to have extensive auto-targeting to align the turret on the fly as we move, but with only movable elevation. Azimuth will be handled by actual driving, though we're planning on having that automatically align too. The image processing will be offloaded to the driver station, though we're looking into using an onboard computer.