Thread: Using a coprocessor for vision
View Single Post
  #1   Spotlight this post!  
Unread 16-12-2014, 16:52
jojoguy10's Avatar
jojoguy10 jojoguy10 is online now
Programming/Controls Mentor
AKA: Joe Kelly
FRC #0997 (Spartan Robotics) and FRC #2990 (Hotwire Robotics)
Team Role: Mentor
  
Join Date: Jan 2013
Rookie Year: 2010
Location: Corvallis, OR
Posts: 289
jojoguy10 has much to be proud ofjojoguy10 has much to be proud ofjojoguy10 has much to be proud ofjojoguy10 has much to be proud ofjojoguy10 has much to be proud ofjojoguy10 has much to be proud ofjojoguy10 has much to be proud ofjojoguy10 has much to be proud ofjojoguy10 has much to be proud of
Using a coprocessor for vision
Hi there!

Our team has never really had great success with vision. Specifically talking about this last year (Arial Assist), our code would work half of the time to find the "hot" goal.

I've heard that some people use a separate processor (like the NVIDIA TK1 Jetson (I think?)) to program the vision code. How would our team implement this?

We use Labview to program our robot. I'm wondering how we can use a different/better solution to using the cRIO or Drive Station to do the vision processing.

Thanks in advanced!
Joe
__________________

2013 and 2014 - Student (FRC#2990), Programmer (LabVIEW)
2015 and 2016 - Mentor (FRC#2990), Programming (LabVIEW)
2017-Current - Mentor (FRC#997), Controls/Programming (Java)
2015-Current - A/V Volunteer at Oregon events
Reply With Quote