View Single Post
  #9   Spotlight this post!  
Unread 16-09-2013, 08:14
protoserge's Avatar
protoserge protoserge is offline
CAD, machining, circuits, fun!
AKA: Some call me... Tim?
FRC #0365 (MOE) & former 836 Mentor)
Team Role: Mentor
 
Join Date: Jan 2012
Rookie Year: 2002
Location: Wilmington, DE
Posts: 754
protoserge has a reputation beyond reputeprotoserge has a reputation beyond reputeprotoserge has a reputation beyond reputeprotoserge has a reputation beyond reputeprotoserge has a reputation beyond reputeprotoserge has a reputation beyond reputeprotoserge has a reputation beyond reputeprotoserge has a reputation beyond reputeprotoserge has a reputation beyond reputeprotoserge has a reputation beyond reputeprotoserge has a reputation beyond repute
Re: Image Processing with 2 cameras

Quote:
Originally Posted by magnets View Post
Our team had massive success with our vision system this year. We just ran a labview program on the driver station that grabbed images straight from the camera. We limited the framerate to 20fps (we actually could get higher), and the laptop (core 2 duo) stayed below 40% CPU usage. This works with two cameras too (we played around with the new and old models of the axis cams at the same time).

However, I don't really see why you'd need 2 cameras on a competition robot, unless you have one pointing forward and one back.
You'd have two cameras for stereo vision. This is very useful for aiming.

We had a system for Rebound Rumble that allowed us to aim effectively by indicating which direction the operator needed to adjust the turret. Although we never had auto-aim in competition, it did function in practice and worked quite well. We later discovered we had been using a blocked port!

I'm not sure if the Arduino Due has enough processing power to handle image processing at the rates we would need, but the CMUCam5 (Pixy) is using an ARM Cortex M4 with Cortex M0 as a coprocessor (LPC4300). Definitely something to look into.