View Single Post
  #15   Spotlight this post!  
Unread 06-07-2016, 07:36
GeeTwo's Avatar
GeeTwo GeeTwo is online now
Technical Director
AKA: Gus Michel II
FRC #3946 (Tiger Robotics)
Team Role: Mentor
 
Join Date: Jan 2014
Rookie Year: 2013
Location: Slidell, LA
Posts: 3,565
GeeTwo has a reputation beyond reputeGeeTwo has a reputation beyond reputeGeeTwo has a reputation beyond reputeGeeTwo has a reputation beyond reputeGeeTwo has a reputation beyond reputeGeeTwo has a reputation beyond reputeGeeTwo has a reputation beyond reputeGeeTwo has a reputation beyond reputeGeeTwo has a reputation beyond reputeGeeTwo has a reputation beyond reputeGeeTwo has a reputation beyond repute
Re: Vision co-processor Location

Completely agree that the robot side is preferable due to significant expansion of data speed, and reduced latency. In recent years, we've used USB cameras directly connected to a pi for vision processing. If you want to take it to the extreme, only the extracted information (e.g. height, width, and center of goal) needs to go on the network at all.

If you do opt to put vision code on the driver station side, it may be just as effective and much more convenient to install it directly on the driver station computer, especially if you're using a laptop significantly more powerful than the classmate.
__________________

If you can't find time to do it right, how are you going to find time to do it over?
If you don't pass it on, it never happened.
Robots are great, but inspiration is the reason we're here.
Friends don't let friends use master links.
Reply With Quote