View Single Post
  #24   Spotlight this post!  
Unread 26-04-2016, 10:55
pmangels17's Avatar
pmangels17 pmangels17 is offline
Mechanical Marauders - Alumnus
AKA: Paul Mangels
FRC #0271 (Mechanical Marauders)
Team Role: Mechanical
 
Join Date: Jan 2012
Rookie Year: 2011
Location: Bay Shore, NY
Posts: 399
pmangels17 has a reputation beyond reputepmangels17 has a reputation beyond reputepmangels17 has a reputation beyond reputepmangels17 has a reputation beyond reputepmangels17 has a reputation beyond reputepmangels17 has a reputation beyond reputepmangels17 has a reputation beyond reputepmangels17 has a reputation beyond reputepmangels17 has a reputation beyond reputepmangels17 has a reputation beyond reputepmangels17 has a reputation beyond repute
Re: Integrating Computer Vision with Motion Control - FIRST Championship Conference

I think it will be addressed, but I would be curious to hear exactly how much control on 254 is done by drivers vs with vision. What are your failsafes if the vision board suddenly crashes/shorts/explodes?

Also, what other sensors do you combine with vision for a more complete picture of your control system. For example, if you want to know distance to a target, are you using only a camera for that, or are there other sensors that you use to crosscheck your measurements.

And, specifically on your robot, how do you relay to the drivers that everything is in position for a shot? Is there a giant green check mark, does the system just not let you fire until it's ready, is the firing also controlled autonomously, or do you have a different solution?
__________________
Junior at the University of Notre Dame, Mechanical Engineering

Got questions (about Notre Dame, robots, college, etc), don't hesitate to ask.

**Bang Boom Pop!** "Was that the robot?" "I don't know, do it again"
**BANG BOOM POP** "Oh, now it's on fire."
Reply With Quote