View Single Post
  #6   Spotlight this post!  
Unread 10-01-2013, 14:33
Lil' Lavery Lil' Lavery is online now
TSIMFD
AKA: Sean Lavery
FRC #1712 (DAWGMA)
Team Role: Mentor
 
Join Date: Nov 2003
Rookie Year: 2003
Location: Philadelphia, PA
Posts: 6,636
Lil' Lavery has a reputation beyond reputeLil' Lavery has a reputation beyond reputeLil' Lavery has a reputation beyond reputeLil' Lavery has a reputation beyond reputeLil' Lavery has a reputation beyond reputeLil' Lavery has a reputation beyond reputeLil' Lavery has a reputation beyond reputeLil' Lavery has a reputation beyond reputeLil' Lavery has a reputation beyond reputeLil' Lavery has a reputation beyond reputeLil' Lavery has a reputation beyond repute
Send a message via AIM to Lil' Lavery
Re: Shooter Aiming Methods

Quote:
Originally Posted by z_beeblebrox View Post
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.
Reply With Quote